pleroma/config
rinpatch 4286a383df Improve user deletion consistency
An attempt to ensure something like
https://git.pleroma.social/pleroma/pleroma/-/issues/1415 does not happen
or is at least debuggable.

- Deactivate the user before deletion to ensure no new posts/follows
can be made during it
- Run the deletion in a transaction. This should reduce performance
impact of a deletion since it will only use a single connection. Also
makes sure an account cannot get stuck in a weird state between deleted
and active. Made it possible to disable though, in case someone hits
the issue mentioned above.
- Log more errors
2021-02-24 18:52:39 +03:00
..
benchmark.exs web push http_client fix 2020-10-01 13:32:11 +03:00
config.exs Improve user deletion consistency 2021-02-24 18:52:39 +03:00
description.exs Improve user deletion consistency 2021-02-24 18:52:39 +03:00
dev.exs Enable strict validation mode in dev and test environments 2020-05-04 22:35:28 +04:00
docker.exs Remove dynamic config as default, add healthcheck 2019-09-03 09:31:52 -04:00
dokku.exs CI: Add auto-deployment via dokku. 2019-05-31 10:55:35 +02:00
emoji.txt Load an emoji.txt specific to the test env 2021-02-03 16:40:59 -06:00
prod.exs Set Logger level to :info in prod 2019-12-09 19:11:54 +07:00
test.exs Improve user deletion consistency 2021-02-24 18:52:39 +03:00