Skip to content

Modularize negotiation tests and fix client doc links#1591

Merged
oferchen merged 1 commit into
masterfrom
optimize-code-for-production-release
Oct 29, 2025
Merged

Modularize negotiation tests and fix client doc links#1591
oferchen merged 1 commit into
masterfrom
optimize-code-for-production-release

Conversation

@oferchen
Copy link
Copy Markdown
Owner

Summary

  • split the giant negotiation test suite into chunked modules so each file stays below the hygiene ceiling
  • wire the new tests module through a lightweight mod.rs shim that re-exports the existing helper imports
  • update feature matrix and gaps documentation to point at crates/core/src/client/mod.rs

Testing

  • cargo test -p rsync-transport --lib

https://chatgpt.com/codex/tasks/task_e_69028b4e34a88323a677becc1236576c

@oferchen oferchen merged commit 3ada1ac into master Oct 29, 2025
@oferchen oferchen deleted the optimize-code-for-production-release branch October 29, 2025 22:02
oferchen added a commit that referenced this pull request May 5, 2026
Design note for #1591. Proposes a TransferChannel trait that exposes
both sync and async send/recv surfaces, with flume as the recommended
backing for sync-async bridge sites and crossbeam retained for the
pure-sync hot paths. Documents the five migration sites, backpressure
and fairness semantics, cancellation footguns, and follow-up work.

Wire-compat impact: zero. Channels are internal coordination only.
oferchen added a commit that referenced this pull request May 5, 2026
…ine (#3647)

Design note for #1591. Proposes a TransferChannel trait that exposes
both sync and async send/recv surfaces, with flume as the recommended
backing for sync-async bridge sites and crossbeam retained for the
pure-sync hot paths. Documents the five migration sites, backpressure
and fairness semantics, cancellation footguns, and follow-up work.

Wire-compat impact: zero. Channels are internal coordination only.
oferchen added a commit that referenced this pull request May 5, 2026
)

Specifies a hybrid model where a tokio async accept loop hands off
accepted connections to a fixed-size pool of synchronous worker
threads via a bounded channel. Transfer state machine and wire format
are unchanged; the design only replaces the accept-and-dispatch layer.

Tracking #1674. References #1591 (async-channel abstraction),
#1934/#1935 (async-daemon feature gate), #2052 (TLS termination).
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.
oferchen added a commit that referenced this pull request May 18, 2026
…ine (#3647)

Design note for #1591. Proposes a TransferChannel trait that exposes
both sync and async send/recv surfaces, with flume as the recommended
backing for sync-async bridge sites and crossbeam retained for the
pure-sync hot paths. Documents the five migration sites, backpressure
and fairness semantics, cancellation footguns, and follow-up work.

Wire-compat impact: zero. Channels are internal coordination only.
oferchen added a commit that referenced this pull request May 18, 2026
)

Specifies a hybrid model where a tokio async accept loop hands off
accepted connections to a fixed-size pool of synchronous worker
threads via a bounded channel. Transfer state machine and wire format
are unchanged; the design only replaces the accept-and-dispatch layer.

Tracking #1674. References #1591 (async-channel abstraction),
#1934/#1935 (async-daemon feature gate), #2052 (TLS termination).
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 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant