-
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.0.0alpha] skeleton throws error, if files exists via share #27375
Comments
Argh, maybe the code changes in a way that changed the symptoms. Increasing to sev-high unless there is a good workaround. @owncloud/qa can you add a test for this ? |
The problem is that this test pass in integration tests. I've just tried this on current master: Scenario: Sharing something from the skeleton
Given user "user0" exists
And user "user1" exists
And file "/textfile0.txt" of user "user0" is shared with user "user1"
Then user "user1" should see following elements
| /FOLDER/ |
| /PARENT/ |
| /PARENT/parent.txt |
| /textfile0.txt |
| /textfile1.txt |
| /textfile2.txt |
| /textfile3.txt |
| /textfile4.txt |
| /welcome.txt |
| /textfile0%20(2).txt | It passes without any problem, I guess some step counts as login. |
Ok it passes because every new user logs in when being created: https://github.com/owncloud/core/blob/master/tests/integration/features/bootstrap/Provisioning.php#L84-L89 |
I've run tests about sharing (just sharing-v1.feature) and removing that piece of code these tests fail: features/sharing-v1.feature:255 I think it is better to keep it as it is. And test this manually. |
Can't reproduce this on master by sharing "welcome.txt", even in read-only mode. Also cannot reproduce on 10.0 beta. I tried creating users both with the users page and also on the CLI, same result. |
The integration tests do fail with the trick from @SergioBertolinSG, but not because of a permission issue. I'm not able to get an error login page. Maybe the permission on the user's data folder were wrong ? |
Closing due to lack of feedback, not reproducible and possibly obsolete |
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. |
-> login fails with error page
Logging:
Related issue describes different behavior: #16450
The text was updated successfully, but these errors were encountered: