Skip to content

Fix Windows PATHEXT parsing for fallback binary search#1818

Merged
oferchen merged 2 commits into
masterfrom
fix-split-method-error-in-rsync-core
Nov 1, 2025
Merged

Fix Windows PATHEXT parsing for fallback binary search#1818
oferchen merged 2 commits into
masterfrom
fix-split-method-error-in-rsync-core

Conversation

@oferchen
Copy link
Copy Markdown
Owner

@oferchen oferchen commented Nov 1, 2025

Summary

  • replace PATHEXT parsing with a UTF-16 aware splitter to avoid OsString::split usage
  • continue filtering empty PATHEXT entries while preserving default fallbacks

Testing

  • cargo fmt
  • cargo test -p rsync-core

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

@oferchen oferchen merged commit f484a58 into master Nov 1, 2025
@oferchen oferchen deleted the fix-split-method-error-in-rsync-core branch November 1, 2025 00:23
oferchen added a commit that referenced this pull request May 1, 2026
…feature (#1934) (#3524)

Adds docs/audits/daemon-async-listener-rfc.md sketching a feature-gated
tokio-based async accept loop for the daemon. The accept loop and
greeting/module-select phase run on the tokio runtime; the transfer
hot path stays synchronous behind a spawn_blocking hand-off, keeping
tokio scoped to the daemon crate per the #1779 / #1818 policy. Design
only - implementation lands in #1935.
oferchen added a commit that referenced this pull request May 5, 2026
…feature (#1934) (#3524)

Adds docs/audits/daemon-async-listener-rfc.md sketching a feature-gated
tokio-based async accept loop for the daemon. The accept loop and
greeting/module-select phase run on the tokio runtime; the transfer
hot path stays synchronous behind a spawn_blocking hand-off, keeping
tokio scoped to the daemon crate per the #1779 / #1818 policy. Design
only - implementation lands in #1935.
oferchen added a commit that referenced this pull request May 5, 2026
Re-checks the tokio scope established by audit #1779 against the
current Cargo.toml set after #1732 (async became default) and
#1818. Documents drift to seven allowed consumers (daemon, core,
engine, transfer, bandwidth, protocol, rsync_io), proves the
public async surface stays in those crates, and proposes a CI
guardrail script to pin the boundary.
oferchen added a commit that referenced this pull request May 18, 2026
Re-checks the tokio scope established by audit #1779 against the
current Cargo.toml set after #1732 (async became default) and
#1818. Documents drift to seven allowed consumers (daemon, core,
engine, transfer, bandwidth, protocol, rsync_io), proves the
public async surface stays in those crates, and proposes a CI
guardrail script to pin the boundary.
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