-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
fix: file quota was not applied in all cases #21894
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
I guess this needs backporting to 19, 18 and 17? @korelstar |
Also, do you mind rebasing to show green CI? |
d741f8f
to
0bc5c25
Compare
@nickvergessen I've rebased the branch, but since there are CI errors on all commits on master, I don't think this will make this PR green ...
Yes! :-) |
Ping @rullzer |
0bc5c25
to
d8a80cd
Compare
Rebased to trigger CI again. |
🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 32099: failureacceptance-app-files
Show full log
|
Drone error seems to be unrelated since it's in all current PRs. Can this be merged, now? |
Backports to be triggered after the maintenance round on thursday |
/backport to stable19 |
/backport to stable18 |
/backport to stable17 |
Since 70906a3, the file quota was not applied in all cases (see discussion with @nickvergessen on Talk). You can see the problem in the test case for the notes app's API tests: https://github.com/nextcloud/notes/runs/881221664
It looks like the problem is that by calling
$homeMount->getStorageRootId()
, the storage cache is created before the mount was actually added. Movingself::getMountManager()->addMount($homeMount)
before that call fixes this issue. However, I don't know if this has any side-effects./cc @icewind1991 @rullzer
Since the original PR #21489 was backported to stable19, stable18 and stable17, this PR should also be backported to those branches.