feat: add IUserFolder similar to IRootFolder - #53048
Conversation
2013bba to
89350ae
Compare
|
I do not understand these last 4 errors and how to get rid of them 😿 |
ec338d9 to
ec59b84
Compare
9e6edb7 to
9526491
Compare
9526491 to
a3dfd4c
Compare
|
The remaining failure comes from the fact that when a user folder exists on disk but not in oc_filecache, it fails to be scanned correctly. Previous code did not have the issue because it did not try to create /user but directly /user/files, I think. @icewind1991 I’m interested by your input on this and whether you think commit d9df76e is a good idea. |
|
s3 tests are now failing 😭 |
386c7d3 to
0c006ff
Compare
|
I rebased on master and now there are new failures in trashbin tests. I’m unable to reproduce those so far. |
|
The failure in files_sharing is related to trashbin as well, so the current issue is related to trashbin. I could not find a way to reproduce the issue locally. |
a63b255 to
52b7207
Compare
3044db1 to
a53ad52
Compare
fixed see last commit, this was caused as the trashbin was never unpaused if the error occurred after the pause |
|
(bumped the version numbers to 36 and rebased on master) |
* Implements #52896 Similar to the root folder this represents the users home folder, it allows to group user based methods on the folder like the user quota. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
…etUserFolder Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
bf1f534 to
b6e35e0
Compare
|
/backport b6e35e0 to stable35 |
|
Documentation: nextcloud/documentation#15605 |
#53048 added an in_array() call without $strict after the InArrayStrictChecker psalm rule had landed, so static analysis now fails on every pull request. dirname() always returns a string, so strict comparison does not change behaviour. Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
|
Hey @susnux I think there may be an issue with the changes in this PR and the test that is now failing on master seems to have been skipped in the PR (https://github.com/nextcloud/server/actions/runs/34460275752/job/102816738456) The code was clearing two caches before, while now it is only clearing one, while the others are still in use and get the outdated quota values. Any PR on top of this fails with the same 2 webdav-related.feature tests getting a -3 instead of the right quota. |
Summary
TBD
Checklist