always select next before making calls for propfinds #4560
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
butonic
force-pushed
the
next-before-making-calls-for-propfind
branch
2 times, most recently
from
323f11f
to
efc4f04
Compare
dragonchaser
approved these changes
Jul 25, 2024
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
butonic
force-pushed
the
next-before-making-calls-for-propfind
branch
from
efc4f04
to
f9b64b2
Compare
This was referenced Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now select the next client more often to spread out load
see owncloud/ocis#8578
I don't expect a huge impact from this PR.