Fix failing "build-test (windows-latest)" CI job: add cargo network retry#104
Merged
Conversation
Copilot
AI
changed the title
safe_resize_handles_wide_glyph_at_new_right_edge
Fix failing "build-test (windows-latest)" CI job: add cargo network retry
Jun 25, 2026
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.
The
build-test (windows-latest)GitHub Actions job was failing due to a transient network error when Cargo tried to update the crates.io sparse registry index on a cold cache start.Root Cause
When the Cargo registry cache is cold (cache miss), Cargo fetches index metadata for all packages referenced in
Cargo.lock— including platform-specific transitive dependencies likewayland-backend(pulled in by the optionalgpuicrate). On Windows GitHub-hosted runners this registry download occasionally fails with a TCP connection reset ([56] Recv failure: Connection was reset), causing the entire job to exit with code 101.Fix
Added
[net] retry = 3to.cargo/config.toml. This tells Cargo to automatically retry failed network operations up to 3 times before giving up, handling transient connectivity resets without any manual intervention.Once a successful run populates the Windows Cargo registry cache, subsequent runs skip the registry download entirely and are unaffected by this class of failure.