pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2023-03-27T10:05:48Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3073Previous reactions no longer shown2023-03-27T10:05:48ZcptnPrevious reactions no longer shownAfter upgrading to latest develop (Backend version 2.5.51-78-gbf9db784-develop Frontend version fa532b1f) previous emoji reactions are no longer shown in Pleroma-FE or Husky. Adding this issue here since they first disappeared after upgr...After upgrading to latest develop (Backend version 2.5.51-78-gbf9db784-develop Frontend version fa532b1f) previous emoji reactions are no longer shown in Pleroma-FE or Husky. Adding this issue here since they first disappeared after upgrading just BE. They didn't come back after upgrading FE.https://git.pleroma.social/pleroma/pleroma/-/issues/3059Report content incorrectly cached2023-02-09T19:52:04ZtusooaReport content incorrectly cachedThe activity id is always rendered as "pleroma:fake" so it's messing up with the cache. Should use the ap id as clue.The activity id is always rendered as "pleroma:fake" so it's messing up with the cache. Should use the ap id as clue.https://git.pleroma.social/pleroma/pleroma/-/issues/1861[stable] CSP broken when mediaproxy disabled2020-06-14T09:41:07Zfeld[stable] CSP broken when mediaproxy disabledCommit a51284b60a broke CSP when mediaproxy is disabled. `img-src` used to be set to `"img-src 'self' data: blob: https:",` but now it's set to `"img-src 'self' data: blob:"`Commit a51284b60a broke CSP when mediaproxy is disabled. `img-src` used to be set to `"img-src 'self' data: blob: https:",` but now it's set to `"img-src 'self' data: blob:"`2.0.7rinpatchrin+pleroma@patch.cxrinpatchrin+pleroma@patch.cxhttps://git.pleroma.social/pleroma/pleroma/-/issues/1269Instance name not showing up in chrome tabs2019-09-26T19:16:20ZPastyInstance name not showing up in chrome tabsI updated to latest develop on pikachu.rocks. Without touching the settings, the tab name (tab label) of my instance changed to "Elixir.Pleroma", when it previously was "Lili's instance".
This is what it looks like:
![image](/uploads/4...I updated to latest develop on pikachu.rocks. Without touching the settings, the tab name (tab label) of my instance changed to "Elixir.Pleroma", when it previously was "Lili's instance".
This is what it looks like:
![image](/uploads/49a52260dfd0a7934905473f45988a3c/image.png)https://git.pleroma.social/pleroma/pleroma/-/issues/983Ecto migration logs get rejected after default log level got changed to warn2019-06-19T10:33:34Zrinpatchrin+pleroma@patch.cxEcto migration logs get rejected after default log level got changed to warnThe solution is to override the log level, but even though Ecto migrator supports it, ecto.migrate task does not expose it, so this should probably be fixed on ecto's side.The solution is to override the log level, but even though Ecto migrator supports it, ecto.migrate task does not expose it, so this should probably be fixed on ecto's side.Alexander StrizhakovAlexander Strizhakovhttps://git.pleroma.social/pleroma/pleroma/-/issues/838Horrible search/tag query performance2019-06-04T16:12:25Zrinpatchrin+pleroma@patch.cxHorrible search/tag query performanceSince merging database compaction a lot of people, myself included started noticing search queries on stuff older than 2-3 weeks timing out quite often
Benchmark code:
```elixir
defmodule Mix.Tasks.Pleroma.Benchmark do
use Mix.Task
...Since merging database compaction a lot of people, myself included started noticing search queries on stuff older than 2-3 weeks timing out quite often
Benchmark code:
```elixir
defmodule Mix.Tasks.Pleroma.Benchmark do
use Mix.Task
alias Mix.Tasks.Pleroma.Common
def run(["search"]) do
Common.start_pleroma()
Benchee.run(%{
"search" => fn ->
Pleroma.Web.MastodonAPI.MastodonAPIController.status_search(nil, "cofe")
end
})
end
def run(["tag"]) do
Common.start_pleroma()
Benchee.run(%{
"tag" => fn ->
%{"type" => "Create", "tag" => "cofe"}
|> Pleroma.Web.ActivityPub.ActivityPub.fetch_public_activities()
end
})
end
end
```
This is probably not ideal because postgres caches queries etc. The difference may not even sound convincing, but this is the best I could do to prove it instead of just "it feels slower", if you have any better ideas how to benchmark it, please do tell
All databases have been VACUUM FULLed and ANALYZEd before benchmarking
Results on non-compacted db with old search queries (commit cc93775ebf539598075c0b9afb96c60c8bede6b5):
```shell
$ mix pleroma.benchmark search
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking search...
Name ips average deviation median 99th %
search 2.42 414.06 ms ±7.64% 413.14 ms 444.82 ms
$ mix pleroma.benchmark tag
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking tag...
Name ips average deviation median 99th %
tag 7.20 138.81 ms ±110.84% 78.94 ms 532.96 ms
```
Results on non-compacted db with new search queries (commit 9da8b287f8a2c1fda2ca05351d5418321510472b):
```shell
$ mix pleroma.benchmark search
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking search...
Name ips average deviation median 99th %
search 1.82 548.64 ms ±8.33% 559.37 ms 593.72 ms
$ mix pleroma.benchmark tag
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking tag...
Name ips average deviation median 99th %
tag 0.77 1.31 s ±25.98% 1.19 s 1.79 s
```
Results on compacted db with new search queries (commit 9da8b287f8a2c1fda2ca05351d5418321510472b):
```shell
$ mix pleroma.benchmark search
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking search...
Name ips average deviation median 99th %
search 2.06 485.65 ms ±10.12% 480.92 ms 605.03 ms
$ mix pleroma.benchmark tag
Operating System: Linux
CPU Information: Unrecognized processor
Number of Available Cores: 4
Available memory: 1.88 GB
Elixir 1.8.1
Erlang 21.2.6
Benchmark suite executing with the following configuration:
warmup: 2 s
time: 5 s
memory time: 0 ns
parallel: 1
inputs: none specified
Estimated total run time: 7 s
Benchmarking tag...
Name ips average deviation median 99th %
tag 1.49 672.48 ms ±15.58% 694.68 ms 777.66 ms
```
cc: @lambadalambda @kaniini @mloftislainlain