Skip to content

fix: disable ssh multiplex on native Windows#20

Merged
RedFox20 merged 1 commit into
masterfrom
fix/windows-skip-mux
May 7, 2026
Merged

fix: disable ssh multiplex on native Windows#20
RedFox20 merged 1 commit into
masterfrom
fix/windows-skip-mux

Conversation

@battlesnake
Copy link
Copy Markdown
Collaborator

Summary

Why

After #19 / v0.11.29, Jorma still saw on Windows:

mux_client_request_session: read from master failed: Connection reset by peer
ControlSocket C:\Users\jorma/.ssh/cm\... already exists, disabling multiplexing

The OpenSSH_for_Windows_<ver> banner heuristic isn't catching every broken-mux configuration in practice. Per Jorma's instruction: "If you can't figure this out, just disable ssh mux entirely on Windows (natively only, wsl is probably fine)."

Test plan

  • pytest tests/test_ssh_multiplex/ — 38 passed
  • Bumped _version.py to 0.11.30 to trigger deploy on merge

🤖 Generated with Claude Code

Banner-based detection in v0.11.29 still leaves multiplex enabled
for the very Microsoft OpenSSH it tried to skip — Jorma reports
ongoing `mux_client_request_session: read from master failed:
Connection reset by peer` and `ControlSocket ... already exists,
disabling multiplexing` mid-fetch. Per Jorma's instruction, drop
detection and disable multiplex on native Windows entirely. WSL,
Cygwin and Git-Bash run as Linux from Python's POV (System.windows
is False) so they keep multiplex.

Also drops merge_stderr from execute_piped — added in #19 only for
the now-removed `ssh -V` banner probe, no other callers.
@battlesnake battlesnake requested a review from RedFox20 May 7, 2026 16:07
@RedFox20 RedFox20 merged commit 8a19ab4 into master May 7, 2026
1 check passed
@RedFox20 RedFox20 deleted the fix/windows-skip-mux branch May 7, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants