6 Commits

Author	SHA1	Message	Date
Côme Chilliet	1ab09ec753	chore: Apply new coding standard to all files ... The diff can be checked using: git diff --ignore-all-space --ignore-blank-lines To see only the changes not related to blank lines. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>	2026-06-01 13:46:39 +02:00
Ferdinand Thiessen	e0ba4d71b6	chore: add missing Override attribute to OC ... Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>	2026-04-28 21:29:27 +02:00
Carl Schwan	7b6078875b	refactor: Run rector on lib/private ... Signed-off-by: Carl Schwan <carl.schwan@nextcloud.com>	2026-02-06 13:50:18 +01:00
provokateurin	54ec472d9a	fix(BackgroundJobs): Adjust intervals and time sensitivities ... Signed-off-by: provokateurin <kate@provokateurin.de>	2024-10-08 11:26:53 +02:00
Ferdinand Thiessen	d57a2dd465	fix: Skip users that still exist in backend ... Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>	2024-09-26 20:48:45 +02:00
Ferdinand Thiessen	16833aff86	fix: Make user removal more resilient ... Currently there is a problem if an exception is thrown in `User::delete`, because at that point the user is already removed from the backend, but not all data is deleted. There is no way to recover from this state, as the user is gone no information is available anymore. This means the data is still available on the server but can not removed by any API anymore. The solution here is to first set a flag and backup the user home, this can be used to recover failed user deletions in a way the delete can be re-tried. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>	2024-09-26 20:48:37 +02:00