Repository navigation
SFTP: keep unchanged CIFS mounts connected during Apply - #28
Merged
Merged
Conversation
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
1 participant
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.
Fixes the physical busy-mount failure observed when enabling a new SFTP template point while an unchanged existing CIFS target is open in Midnight Commander.
The batch now derives affected targets from remove/recreate, new mounts and queued share closes, unmounts/remounts only those targets, and keeps unrelated mounted CIFS targets connected. Adds regression coverage for existing
tmp+ newvarand for the selective unmount syscall.Documents the selective transaction contract in
sftp/AGENTS.mdso later changes do not restore the old all-mount unmount behavior.JBLibs package version remains 1.2.30 because the existing version-check workflow is pinned and the repository App cannot safely update workflow files; the exact hotfix commit will be pinned by the SysApps submodule.
Supersedes draft PR #27, closed only because the connector's Draft → Ready mutation currently fails on an incompatible GraphQL response field.