Skip to content
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

Closed
52 tasks done
individual-it opened this issue Apr 18, 2019 · 12 comments
Closed
52 tasks done

10.2 - Changelog Test Results - Fixed #35054

individual-it opened this issue Apr 18, 2019 · 12 comments
Labels
Milestone

Comments

@individual-it
Copy link
Member

individual-it commented Apr 18, 2019

Part of #35020

Fixed

@skshetry
Copy link
Member

skshetry commented Apr 23, 2019

#34971
Location of "Expire after" changed from 10.1.1 which was as below:
Screenshot from 2019-04-23 11-51-02

And, when expiration date is unenforced and default share is removed on public link share, no expiration date is set.

@skshetry
Copy link
Member

skshetry commented Apr 24, 2019

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 v10.1.1). The uploading message does disappear after the file is uploaded.

See test video here: https://cloud.owncloud.com/index.php/s/1psr6GzChn3u83L

EDIT: Issue created here: #35086

@paurakhsharma
Copy link
Member

paurakhsharma commented Apr 24, 2019

Regarding #34427
I the exception is shown in the log but I am not sure if it is the expected error message.(according to this PR)

These are the steps I followed.

  1. Change appinfo.xml to an invalid XML
  2. Run the command ./occ app:check-code <app_name>
  3. I see an InvalidArgumentException\ thrown in owncloud.log with message Could not convert XML to array (which is expected)

But, I cannot produce an error with the message as in https://github.com/owncloud/core/pull/30457/files#diff-1e7169b61c01f1c8a31c364b3a217135R128
How do I produce such a message?

Note I am marking this fix as checked as I was able to produce InvalidArgumentException in the log

@skshetry
Copy link
Member

Fix chunking infinite loop in some environment-related issues was tested using the How this has been tested section in #34489

@individual-it
Copy link
Member Author

after #34089 headers can be set twice in 4xx responses if already defined in apache config - raised #35093

@sharidas
Copy link
Contributor

I have verified #34506 with 10.2.0 RC1.
Verified it by by creating a local share within oC users and enabled recovery key for the recipient of share user. Used debugger to verify the recovery keys are not added for recipient share user.

@patrickjahns
Copy link
Contributor

I see the following open points:

I believe #34769 was agreed that this can not be manually confirmed and is fine - what about #34467 ?

@skshetry
Copy link
Member

skshetry commented Apr 26, 2019

Repair subshares earlier to avoid errors - #34462 - was also skipped as it cannot be reproduced (as per the discussion).

@PVince81
Copy link
Contributor

PVince81 commented Apr 26, 2019

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.

@PVince81
Copy link
Contributor

for "Store quota overrides in preferences table - #34467" it is likely that LDAP will be required.
manual test would be fine for RC but consider automating it as part of owncloud/user_ldap#368 (comment)

@individual-it
Copy link
Member Author

updated the list above with changes in RC2 listed in e801e4e

@individual-it
Copy link
Member Author

I think we are done here for now
list for tests to be automated here #35207

@lock lock bot locked as resolved and limited conversation to collaborators May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants