-
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
10.2 - Changelog Test Results - Fixed #35054
Comments
#34971 And, when expiration date is unenforced and default share is removed on public link share, no expiration date is set. |
Regarding #34097: Canceling upload in files_drop did not work correctly if it is canceled after waiting for a few sec. But, this does work if it is canceled immediately (which didn't work on See test video here: https://cloud.owncloud.com/index.php/s/1psr6GzChn3u83L EDIT: Issue created here: #35086 |
Regarding #34427 These are the steps I followed.
But, I cannot produce an error with the message as in https://github.com/owncloud/core/pull/30457/files#diff-1e7169b61c01f1c8a31c364b3a217135R128 Note I am marking this fix as checked as I was able to produce |
Fix chunking infinite loop in some environment-related issues was tested using the |
I have verified #34506 with 10.2.0 RC1. |
I see the following open points:
I believe #34769 was agreed that this can not be manually confirmed and is fine - what about #34467 ? |
Repair subshares earlier to avoid errors - #34462 - was also skipped as it cannot be reproduced (as per the discussion). |
For "Prevent concurrent updates in group shares to avoid duplicate entries - #34769" we should check that we have acceptance tests that cover the general cases with subshares (but not this one specific case about duplicates). There is already some coverage on unit test level but would be good to have some on higher level. |
for "Store quota overrides in preferences table - #34467" it is likely that LDAP will be required. |
updated the list above with changes in RC2 listed in e801e4e |
I think we are done here for now |
Part of #35020
Fixed
The text was updated successfully, but these errors were encountered: