-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(settings): Delete settings when a user is deleted #1583
fix(settings): Delete settings when a user is deleted #1583
Conversation
Signed-off-by: Joas Schilling <coding@schilljs.com>
/backport to stable27 |
/backport to stable26 |
/backport to stable25 |
The backport to stable25 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable25
git pull origin stable25
# Create the new backport branch
git checkout -b fix/foo-stable25
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
/backport to stable25 |
The backport to stable25 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable25
git pull origin stable25
# Create the new backport branch
git checkout -b fix/foo-stable25
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
I confirm that after applying the fix manually, I can't find any entry related to to the test user in the database anymore as far as Comparing with the result of a test performed before applying the fix, I actually I see that references to the same test user have also disappeared in other tables:
Could they be related to that fix as well (which would a good thing I believe)? Here are for reference the remaining entries in the DB found after a new test:
|
No, but as per server ticket some apps queued clean up jobs and you now basically waited long enough for the background jobs to be executed |
Stable25 in #1592 |
Fix #1572
cc @oleole39 in case you want to review