Skip to content
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

[stable24] fix: use own workspace endpoint instead of PROPFIND properties #2682

Merged
merged 2 commits into from
Jul 7, 2022

Conversation

backportbot-nextcloud[bot]
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Jul 6, 2022

backport of #2677

@mejo-
Copy link
Member

mejo- commented Jul 6, 2022

/rebase

With a lot of subdirectories the depth=1 PROPFIND will take quite a long time.
It has to look for workspace files in all the subdirectories.

Stop overloading the PROPFIND and rely on our own workspace endpoint
for that particular directory instead.

Signed-off-by: Max <max@nextcloud.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@nextcloud-command nextcloud-command force-pushed the backport/2677/stable24 branch from f6ca3df to bc23086 Compare July 6, 2022 21:40
@mejo-
Copy link
Member

mejo- commented Jul 6, 2022

/compile

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
Copy link
Collaborator

@max-nextcloud max-nextcloud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@juliusknorr juliusknorr merged commit 1aaaf74 into stable24 Jul 7, 2022
@delete-merged-branch delete-merged-branch bot deleted the backport/2677/stable24 branch July 7, 2022 08:40
@skjnldsv skjnldsv mentioned this pull request Jul 7, 2022
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working performance 🚀
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants