-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Shares not removed on file deletion #20908
Comments
It feels like a regression. But no bisect tonight for me... it is on the list for tomorrow. |
Existing behavior (until 8.2):
Not really because it is a repairable state and then we should auto repair it. |
Ah mmm. starting to remember now. Do you remember what was the reason we did not install a hook to listen for the delete events? |
Because the repair step is fine... but it should not happen any more. |
@rullzer the reason for not using hooks: the delete hook only fires for the deleted folder, not its children. We didn't want to have recursive logic to find the file id of all children and delete the matching parents as it would be too expensive and would delay the delete operation for too long for the user/client. |
Ai... I get it... but we need some way to solve this if we are going to allow 3rdparty shareproviders. |
So this bit me again today.. We really should think how to fix this.. |
Ok so this can haunt us now that we have lazy shares... let me fix the OCS endpoint to not crash on this... |
Since we have lazy shares it can happen that a share is actually invalid. See #20908 This add checks for the get methods to handle the NotFound exception.
Also think about accidently deletion of a folder... |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I came across this when debugging the smashbox tests for the new share creation code. However it is also happening on master.
Steps:
foo
with user2foo
Now of course we would expect to have the share also removed since the file is explicitly deleted. This can lead to a lot of pollution in the sharing table.
I'm not sure if it will lead to problems since the file id no longer exists. But I can't be certain.
@MorrisJobke another one for the health app
@cmonteroluque FYI
CC: @schiesbn @PVince81
The text was updated successfully, but these errors were encountered: