-
Notifications
You must be signed in to change notification settings - Fork 5
Public link share strays side effects #439
Comments
More data here:
publicshares contents:
publicshares:
|
redis state after second test:
|
after third run, publicshares:
redis:
|
managed to reproduce it by clickytty-clacking around, these are the server logs:
The main reason is that when querying redis with an opaqueid from a stray share (stray share = share that points to a dead resource) redis entry is |
so this means that as soon as there is one stray share, the "not found" error bubbles up and causes the "shares.go" to return an empty set |
okay, so this matches cs3org/reva#1087 |
open PR: cs3org/reva#1090 |
after running all tests, the number of failures got down to 2.
and
I'll rerun everything again with a clean env to see if they still happen. |
the second failure could be related to the versions... |
first test case is a demonstration of https://github.com/owncloud/ocis-reva/issues/389, so we can adjust the test as this is fixed. |
these were bug demonstration tests, I've now adjusted them here: owncloud/web#3948 |
Steps
Expected
All passing
Actual
Passes the first time, fails every subsequent times
Tasks
@individual-it @refs
The text was updated successfully, but these errors were encountered: