fix: check for mountpoint conflict before rename in api#4271
Merged
provokateurin merged 1 commit intomasterfrom Jan 23, 2026
Merged
fix: check for mountpoint conflict before rename in api#4271provokateurin merged 1 commit intomasterfrom
provokateurin merged 1 commit intomasterfrom
Conversation
provokateurin
approved these changes
Jan 20, 2026
CarlSchwan
approved these changes
Jan 21, 2026
provokateurin
force-pushed
the
setmountpoint-api-check
branch
from
5e11ac2 to
e49b64c
Compare
Member
|
/backport to stable33 |
Member
|
/backport to stable32 |
Member
|
/backport to stable31 |
Signed-off-by: Robin Appelman <robin@icewind.nl>
provokateurin
force-pushed
the
setmountpoint-api-check
branch
from
e49b64c to
c7de16e
Compare
This was referenced Jan 23, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Else it doesn't actually block a conflicting rename, and will always give an error.
Note that the webui uses a different endpoint, so the issue only happens for manual api usage.