Repository navigation
Update server and CLI Tokio for I/O safety - #18
Merged
Merged
Conversation
Co-Authored-By: opencode/gpt-6-astra <noreply.kfactory@kittymail.me>
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
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.
Update both Tokio locks from 1.53.1 to patched 1.53.3 for RUSTSEC-2026-0386. No application AsyncFd call needs migration. Cargo normalizes existing Windows dependency edges.
Six pinned format/lint/clippy/firmware checks and server, CLI and Docker builds pass. An initial build hits disk exhaustion; automatic Nix collection recovers space and the bounded single-job retry passes. Both structured server/CLI audits clear the Tokio warning. Generated-lock review and comment hygiene preserve the generated headers.
The unchanged firmware locks still report crypto-bigint RUSTSEC-2026-0387. Current upstream constraints still exclude its patched line. Local VM checks lack KVM; hosted integration CI must pass before merge. No firmware flash, database migration or deployment occurs.