-
-
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
Unify/cleanup filesystem setup #31431
Conversation
c54aa00
to
42f9368
Compare
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.
👍 overall it looks fine, see minor comments
$this->setupForUser($user); | ||
} | ||
|
||
public function tearDown() { |
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.
does it make sense to also have a tear down for a single user or is it too complicated ?
use case could be when running bkg jobs that iterate over lots of users and needs the FS
or as a middle group, one that only tears down the users, not the root ? (but root setup is likely cheap, isn't it?
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.
Root setup is generally cheap yes so I'm not sure if there is much to gain there.
Additionally, background jobs can probably be adjusted to not teardown the filesystem but instead setup for an additional user
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
42f9368
to
917c74e
Compare
Since 22875bf the integration tests in Talk fail. When a conversation is associated to a file (a conversation opened in the Chat tab in the Files app) and a participant gets the possible mentions the list includes the current participants of the conversation as well as other users with access to that file but that are not in the conversation yet. To do that the node for the file id is got using If @icewind1991 Should that be changed in Talk because the code is wrong and it just happened to work until now? Or is the code in Talk fine and it is a regression that should be fixed in the server? Thanks! |
Similar thing on forms - Unittests fail on tearDown with server masterbranch. Seems to me to be connected to this PR? And still consists after the mentioned PR... Do you have any idea on this, @icewind1991?
https://github.com/nextcloud/forms/runs/5618838041 |
} | ||
|
||
$current = dirname($current); | ||
if ($current === '.' || $current === '/') { | ||
$current = ''; | ||
} | ||
} | ||
|
||
throw new NotFoundException("No mount for path " . $path . " existing mounts: " . implode(",", array_keys($this->mounts))); |
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.
@icewind1991 The throw should be highlighted in #37039 as it change how you would use the API.
Already got bitten in activity: nextcloud/activity#1165
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.
Issue happened only after @come-nc cleanup in View.php
: https://github.com/nextcloud/server/pull/36836/files#diff-64a02ee1149d33d0747360694c2abf4ef1bdbfc379b4bb40f76c22b5b1fc06d9R203
OC_Util
/OC\Files\Filesystem
functions to it's own classRequires
Part of #31265