-
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
Moving FutureFile after chunk assembly logs warning #31631
Comments
Edited first post: this also happens in core, not isolated to guest app. Need to run
|
Same when uploading a big file (more than 10 MB) with the web UI on the same stable10 commit:
|
Leaving in backlog to be scheduled |
GitMate.io thinks possibly related issues are #25493 (New chunking API assembly very slow), #25682 (New chunking: etags on the final MOVE), #18575 (Warning when moving two files to different storages.), #7887 (Warnings in logs on master), and #10358 (possibility to omit warnings about symbolic links in activity log). |
@PVince81 probably this filter needs to be adjusted to ignore |
I hope this warning will not appear also for regular files in case of a move that requires copy + delete |
@PVince81 #31890 reduces mention of |
that's a good start. we should get rid of those completely as they are misleading and admins will think something is wrong: find out how to prevent MiscCustomPropertiesBackend to complain about deleted nodes (or exclude IFutureFile?) |
@PVince81 The rest is not related to
|
Oh... can you still look into the QuotaPlugin then ? Let me know if the fix would be too complex. |
@PVince81 these failures seems to be expected:
|
I agree, there are acceptance tests that verify that if the client sends "wrong stuff" that the upload will fail with a reasonable 4nn code. Internally the code might do whatever while responding to such "naughty" clients. |
failing is ok but does it log additional bogus entries ? if not then the current fix is enough |
it's a pita to play detective trying to relate 800+ log entries to 75 test cases 😢 |
From a users perspective I want to note that when uploading from Mac with Client 2.4.2 (rev 10200) to an ownCloud instance 10.0.9 with apache and mysql, I regularly receive the above mentioned error log entry: Hopefully the supplied fix will resolve the log spam in 10.9.10. Am I correct in assuming the fix will be included in that upcoming release? partial
|
the log spamming fix will be in 10.0.10 |
Steps
Run acceptance test from Test for chunking upload guests#212 with name features/apiGuests/guests.feature:44cd tests/acceptance; ./run.sh features/apiWebdav/webdav-related-new-endpoint.feature:497
EDIT vicdeo:
since a55ce77#diff-4ab58a91bb1ef5af35805d89e6475100 it's
cd tests/acceptance; ./run.sh ./run.sh features/apiWebdav/webdav-related-new-endpoint.feature:38
Observe output then search for ".file"
Expected
No warning
Actual
Warning appears:
Version
With stable10 5114289 and guests PR which adds a new test owncloud/guests#212.
TODO
@VicDeo I believed you touched this logic recently as part of #31093 and might understand it better.
The code states that this is supposed to be a "rare" situation here: https://github.com/owncloud/core/blob/stable10/apps/dav/lib/DAV/AbstractCustomPropertiesBackend.php#L245
But the reason the node is not found is because it was already moved (actually copied + deleted) after chunk assembly.
Would it be safe to ignore the exception here and prevent the log entry or is there some bigger issue hidden in there ?
Should this code also be covered by some logic grabbing the nodes beforehand like in #31093 ?
The text was updated successfully, but these errors were encountered: