Skip to content

Add rust-toolchain manifest with required cross targets#1675

Merged
oferchen merged 1 commit into
masterfrom
fix-ci-build-failures
Oct 30, 2025
Merged

Add rust-toolchain manifest with required cross targets#1675
oferchen merged 1 commit into
masterfrom
fix-ci-build-failures

Conversation

@oferchen
Copy link
Copy Markdown
Owner

Summary

  • add a rust-toolchain.toml manifest that pins Rust 1.87.0 for the workspace
  • install the components and targets needed by coverage and cross-compilation jobs so std is available during CI builds

Testing

  • not run (configuration change only)

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

@oferchen oferchen merged commit 9c0d9ca into master Oct 30, 2025
@oferchen oferchen deleted the fix-ci-build-failures branch October 30, 2025 12:13
oferchen added a commit that referenced this pull request Apr 29, 2026
…3437)

Documentation-only audit of the daemon's accept-loop and per-connection
threading model. Compares three paths (raw mio event loop, full tokio
async accept, status quo thread-per-connection) against upstream rsync
3.4.1's select+fork model and against the existing async_session
scaffold. Recommends extending the in-tree async path behind the
existing async Cargo feature rather than introducing a new mio variant
alongside the synchronous loop.
oferchen added a commit that referenced this pull request May 1, 2026
…3437)

Documentation-only audit of the daemon's accept-loop and per-connection
threading model. Compares three paths (raw mio event loop, full tokio
async accept, status quo thread-per-connection) against upstream rsync
3.4.1's select+fork model and against the existing async_session
scaffold. Recommends extending the in-tree async path behind the
existing async Cargo feature rather than introducing a new mio variant
alongside the synchronous loop.
oferchen added a commit that referenced this pull request May 1, 2026
Adds a docs-only RFC at docs/audits/async-daemon-listener.md proposing
a feature-gated tokio-based async accept loop for the daemon. The
design holds tokio at the accept boundary only and delegates per-
session work to the existing synchronous handle_session via
spawn_blocking, satisfying the workspace tokio dependency-scope
policy. Complements the prior event-loop multiplexing audit (#1675)
without superseding it. Phase 1 only - no implementation, no Cargo
or Rust changes.
oferchen added a commit that referenced this pull request May 5, 2026
…3437)

Documentation-only audit of the daemon's accept-loop and per-connection
threading model. Compares three paths (raw mio event loop, full tokio
async accept, status quo thread-per-connection) against upstream rsync
3.4.1's select+fork model and against the existing async_session
scaffold. Recommends extending the in-tree async path behind the
existing async Cargo feature rather than introducing a new mio variant
alongside the synchronous loop.
oferchen added a commit that referenced this pull request May 5, 2026
Adds a docs-only RFC at docs/audits/async-daemon-listener.md proposing
a feature-gated tokio-based async accept loop for the daemon. The
design holds tokio at the accept boundary only and delegates per-
session work to the existing synchronous handle_session via
spawn_blocking, satisfying the workspace tokio dependency-scope
policy. Complements the prior event-loop multiplexing audit (#1675)
without superseding it. Phase 1 only - no implementation, no Cargo
or Rust changes.
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