Switch flate2 to the Rust backend for cross builds by oferchen · Pull Request #1595 · oferchen/rsync

oferchen · 2025-10-29T22:27:15Z

Summary

configure the compression crate to use flate2's pure Rust backend
regenerate Cargo.lock to drop the libz-sys toolchain dependencies

Testing

cargo check

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

…3716) Static-analysis audit recording the runtime model decision for the io_uring integration. Recommends keeping io_uring synchronous and routing async callers through tokio::task::spawn_blocking (#1751) rather than adopting tokio-uring or building a custom poll-driven SQE submitter, on the grounds that fast_io must remain tokio-free and the session ring pool design (#1937) stays simpler when leases are synchronous.

…3867) Capture the current sync-over-fd pattern, the spawn_blocking vs tokio-uring integration trade-off, alignment with the #1751 blocking-pool plan, and the soundness risks (kernel ring fd ownership across .await, registered buffer lifetime). Recommend keeping io_uring synchronous behind fast_io and dispatching from async via spawn_blocking.

Compare tokio-uring crate vs native fast_io::io_uring + spawn_blocking bridge. Recommend staying on the native path, bridging via tokio::task::spawn_blocking from async daemon tasks per #1751.

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.

) Evaluate the four candidate shapes for integrating io_uring with the async daemon runtime and recommend keeping io_uring synchronous, with session-granularity spawn_blocking as the only async/sync boundary.

…3716) Static-analysis audit recording the runtime model decision for the io_uring integration. Recommends keeping io_uring synchronous and routing async callers through tokio::task::spawn_blocking (#1751) rather than adopting tokio-uring or building a custom poll-driven SQE submitter, on the grounds that fast_io must remain tokio-free and the session ring pool design (#1937) stays simpler when leases are synchronous.

…3867) Capture the current sync-over-fd pattern, the spawn_blocking vs tokio-uring integration trade-off, alignment with the #1751 blocking-pool plan, and the soundness risks (kernel ring fd ownership across .await, registered buffer lifetime). Recommend keeping io_uring synchronous behind fast_io and dispatching from async via spawn_blocking.

Compare tokio-uring crate vs native fast_io::io_uring + spawn_blocking bridge. Recommend staying on the native path, bridging via tokio::task::spawn_blocking from async daemon tasks per #1751.

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.

) Evaluate the four candidate shapes for integrating io_uring with the async daemon runtime and recommend keeping io_uring synchronous, with session-granularity spawn_blocking as the only async/sync boundary.

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.

) Evaluate the four candidate shapes for integrating io_uring with the async daemon runtime and recommend keeping io_uring synchronous, with session-granularity spawn_blocking as the only async/sync boundary.

Use pure Rust backend for flate2

e454ab3

oferchen added the codex label Oct 29, 2025 — with ChatGPT Codex Connector

oferchen merged commit 9a6cf41 into master Oct 29, 2025

oferchen deleted the fix-dlltool-error-in-compilation branch October 29, 2025 22:27

This was referenced May 5, 2026

docs(audits): daemon thread-per-connection scalability audit (#1673) #3705

Merged

docs(audits): async runtime impact on io_uring integration (#1595) #3716

Merged

This was referenced May 5, 2026

docs(design): async migration plan for transfer pipeline #3725

Merged

docs(design): async migration plan with incremental adoption #3811

Merged

docs(audits): async runtime impact on io_uring integration (#1595) #3867

Merged

This was referenced May 7, 2026

docs(design): async migration plan with incremental adoption (#1594) #3940

Merged

docs(design): evaluate async impact on io_uring (#1595) #3945

Merged

oferchen added a commit that referenced this pull request May 13, 2026

docs(design): evaluate async impact on io_uring (#1595) (#3945) (#3967)

ed62828

oferchen mentioned this pull request May 16, 2026

docs(design): async migration plan with incremental adoption strategy (#1594) #4186

Merged

4 tasks

oferchen mentioned this pull request May 17, 2026

docs(design): async daemon impact on io_uring integration (#1595) #4217

Merged

3 tasks

oferchen added a commit that referenced this pull request May 18, 2026

docs(design): evaluate async impact on io_uring (#1595) (#3945) (#3967)

4e9bd0a

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Switch flate2 to the Rust backend for cross builds#1595

Switch flate2 to the Rust backend for cross builds#1595
oferchen merged 1 commit into
masterfrom
fix-dlltool-error-in-compilation

oferchen commented Oct 29, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

oferchen commented Oct 29, 2025

Summary

Testing

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant