c3df5d1f10
When git-annex-shell p2pstdio fails with 255, it's because the ssh server is not reachable. Avoid running the fallback action in this case, since it would just try a second time to connect, and presumably fail. Note that the closed P2PSshConnection will not be stored in the pool, so the next request tries again to connect. This is just the right behavior; when the remote becomes reachable again, the same git-annex process will start using it. This commit was sponsored by Ole-Morten Duesund on Patreon.
22 lines
963 B
Markdown
22 lines
963 B
Markdown
Some things to do with the [[design/P2P_protocol]]
|
|
are works in progress, needing a future flag day to complete.
|
|
|
|
## VERSION over tor
|
|
|
|
Old versions of git-annex, before 6.20180312, which speak the P2P protocol
|
|
over tor, don't support VERSION, and attempting to negotiate a version
|
|
will cause the server to hang up the connection. To deal with this
|
|
historical bug, the version is not currently negotiated when using the
|
|
protocol over tor. At some point in the future, when all peers can be
|
|
assumed to be upgraded, this should be changed.
|
|
|
|
## git-annex-shell fallbacks
|
|
|
|
When using git-annex-shell p2pio, git-annex assumes that if it exits 1,
|
|
it does not support that, and falls back to the old sendkey/rerecvkey,
|
|
etc.
|
|
|
|
At some point in the future, once all git-annex and git-annex-shell
|
|
can be assumed to be upgraded to 6.20180312, this fallback can be removed.
|
|
It will allows removing a lot of code from git-annex-shell and a lot of
|
|
fallback code from Remote.Git.
|