CI: remove unsupported windows aarch64 target#1593
Merged
Conversation
9 tasks
oferchen
added a commit
that referenced
this pull request
May 1, 2026
Document the scope of #1593 (async at the transport-level) versus the parallel #1411 (async runtime adoption). Defer the Linux pipe-FD path to #1859, recommend status quo on macOS / BSD / Windows / older Linux, and articulate why the rsync wire-protocol pipeline single-threading caps the win regardless of mechanism.
oferchen
added a commit
that referenced
this pull request
May 5, 2026
Document the scope of #1593 (async at the transport-level) versus the parallel #1411 (async runtime adoption). Defer the Linux pipe-FD path to #1859, recommend status quo on macOS / BSD / Windows / older Linux, and articulate why the rsync wire-protocol pipeline single-threading caps the win regardless of mechanism.
oferchen
added a commit
that referenced
this pull request
May 5, 2026
#3720) Static analysis of whether the SSH transport path warrants an async runtime. Maps every spawn, pipe, and I/O site in the subprocess and russh-embedded paths; lays out where async helps (multi-host fan-out, runtime co-location) versus where it does not (KEX, auth, single transfer); and gives four falsifiable decision criteria for adopting a runtime in the subprocess path.
This was referenced May 5, 2026
oferchen
added a commit
that referenced
this pull request
May 7, 2026
Document the current synchronous SSH transport, the network-vs-disk overlap bottleneck, and two async candidates (tokio::process and embedded russh). Recommend staging behind a --features async-ssh flag, default off until benchmarks show > 10% gain.
This was referenced May 7, 2026
4 tasks
oferchen
added a commit
that referenced
this pull request
May 16, 2026
Expand the placeholder async migration plan into a comprehensive, opinionated design covering: current synchronous threading model per subsystem, per-subsystem cost/benefit, a phased incremental adoption strategy, tokio runtime choice with rejected alternatives, sync/async bridge patterns, backward-compat strategy, risk register, and open questions. Cross-references existing async-related tasks (#1367, #1411, #1591, #1593, #1595, #1674, #1751, #1779, #1780, #1782, #1796, #1797, #1805, #1806, #1889, #1890, #1891, #1892, #1934, #1935, #2136) and related design notes so future planners have a single anchor.
oferchen
added a commit
that referenced
this pull request
May 16, 2026
Expand the placeholder async migration plan into a comprehensive, opinionated design covering: current synchronous threading model per subsystem, per-subsystem cost/benefit, a phased incremental adoption strategy, tokio runtime choice with rejected alternatives, sync/async bridge patterns, backward-compat strategy, risk register, and open questions. Cross-references existing async-related tasks (#1367, #1411, #1591, #1593, #1595, #1674, #1751, #1779, #1780, #1782, #1796, #1797, #1805, #1806, #1889, #1890, #1891, #1892, #1934, #1935, #2136) and related design notes so future planners have a single anchor.
This was referenced May 16, 2026
oferchen
added a commit
that referenced
this pull request
May 17, 2026
Expand the brief async-runtime-ssh-eval note into a full evaluation focused on the runtime-shape question left open by prior docs: multi-thread vs current-thread runtime ownership, AsyncFd vs tokio::process vs russh::ChannelStream bridge constructions, latency-sensitive paths inside the SSH protocol, quantified workload predictions, and a five-step sequencing plan with trigger conditions for default promotion.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
#3720) Static analysis of whether the SSH transport path warrants an async runtime. Maps every spawn, pipe, and I/O site in the subprocess and russh-embedded paths; lays out where async helps (multi-host fan-out, runtime co-location) versus where it does not (KEX, auth, single transfer); and gives four falsifiable decision criteria for adopting a runtime in the subprocess path.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Document the current synchronous SSH transport, the network-vs-disk overlap bottleneck, and two async candidates (tokio::process and embedded russh). Recommend staging behind a --features async-ssh flag, default off until benchmarks show > 10% gain.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Expand the placeholder async migration plan into a comprehensive, opinionated design covering: current synchronous threading model per subsystem, per-subsystem cost/benefit, a phased incremental adoption strategy, tokio runtime choice with rejected alternatives, sync/async bridge patterns, backward-compat strategy, risk register, and open questions. Cross-references existing async-related tasks (#1367, #1411, #1591, #1593, #1595, #1674, #1751, #1779, #1780, #1782, #1796, #1797, #1805, #1806, #1889, #1890, #1891, #1892, #1934, #1935, #2136) and related design notes so future planners have a single anchor.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Expand the brief async-runtime-ssh-eval note into a full evaluation focused on the runtime-shape question left open by prior docs: multi-thread vs current-thread runtime ownership, AsyncFd vs tokio::process vs russh::ChannelStream bridge constructions, latency-sensitive paths inside the SSH protocol, quantified workload predictions, and a five-step sequencing plan with trigger conditions for default promotion.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Expand the placeholder async migration plan into a comprehensive, opinionated design covering: current synchronous threading model per subsystem, per-subsystem cost/benefit, a phased incremental adoption strategy, tokio runtime choice with rejected alternatives, sync/async bridge patterns, backward-compat strategy, risk register, and open questions. Cross-references existing async-related tasks (#1367, #1411, #1591, #1593, #1595, #1674, #1751, #1779, #1780, #1782, #1796, #1797, #1805, #1806, #1889, #1890, #1891, #1892, #1934, #1935, #2136) and related design notes so future planners have a single anchor.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Expand the brief async-runtime-ssh-eval note into a full evaluation focused on the runtime-shape question left open by prior docs: multi-thread vs current-thread runtime ownership, AsyncFd vs tokio::process vs russh::ChannelStream bridge constructions, latency-sensitive paths inside the SSH protocol, quantified workload predictions, and a five-step sequencing plan with trigger conditions for default promotion.
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.
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_6902935ff2c08323ade0c80362199c0e