Repository navigation
ssh:// URLs for current repositories - #10417
Merged
ThomasWaldmann merged 3 commits intoSep 24, 2026
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #10417 +/- ##
==========================================
+ Coverage 88.36% 88.38% +0.02%
==========================================
Files 103 103
Lines 19021 19029 +8
Branches 2959 2961 +2
==========================================
+ Hits 16807 16819 +12
+ Misses 1545 1538 -7
- Partials 669 672 +3 ☔ View full report in Codecov by Harness. |
ThomasWaldmann
force-pushed
the
ssh-scheme-9765
branch
2 times, most recently
from
September 24, 2026 13:24
97e95fd to
70b145f
Compare
ThomasWaldmann
force-pushed
the
ssh-scheme-9765
branch
from
September 24, 2026 13:52
70b145f to
34639e1
Compare
ssh:// now addresses a current repository via REST over stdio over ssh (served by a remote "borg serve --rest"); with --from-borg1, it still addresses a legacy borg 1.x repository via the legacy RPC protocol. The testsuite uses ssh://__testsuite__/path (like the legacy client) to run "borg serve --rest" locally instead of via ssh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
If the first request to the remote "borg serve" fails (e.g. a borg 1.x borg serve does not know --rest, or borg is not installed there), raise an Error showing the server's stderr and a hint (BORG_REMOTE_PATH, --from-borg1) instead of a "Local Exception" traceback. Repository.close() does not raise from closing the store while unwinding an error anymore (like the lock release before it): a dead store fails to close, too, which masked the original error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Describe ssh:// repository URLs for current repositories (served by a remote "borg serve --rest") and for legacy borg 1.x repositories (with --from-borg1, served by a remote "borg serve") and add a change log entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThomasWaldmann
force-pushed
the
ssh-scheme-9765
branch
from
September 24, 2026 13:55
34639e1 to
db0c4ac
Compare
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
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 #9765.
ssh://URLs for current repositoriesssh://[user@]host[:port]/pathnow addresses a current repository: borg runsborg serve --rest --backend FILE:<path>on the remote host via ssh and talks REST (HTTP over stdio) to it.--from-borg1,ssh://addresses a legacy borg 1.x repository via the legacy RPC protocol, as before: the remote runs plainborg serve, which may also be a borg 1.xborg serve.borg serveitself is unchanged:borg serve --restserves current repositories, plainborg serveserves legacy ones. Forced commands for current repositories must useborg serve --rest.ssh://__testsuite__/path(like the legacy client) to runborg serve --restlocally instead of via ssh.Clearer error if the remote
borg servefails to startE.g. a borg 1.x
borg servedoes not know--rest, or borg 2 is not installed remotely. Instead of a "Local Exception" traceback:Repository.close()no longer raises from closing a dead store while unwinding an error (like the lock release before it), which masked the original error.Docs
ssh://repository URLs everywhere (quickstart, FAQ, deployment, security internals, usage),borg serveepilog, change log entry. Generated usage docs / man pages are not regenerated.Testing
test_migrate_lock_alive, which fails identically on master (local macFUSE issue).ssh://URL parsing,get_repositoryrouting (ssh://with and without--from-borg1),borg serve --restcommand line, remote serve startup failure.borg serve.🤖 Generated with Claude Code