Repository navigation
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request reverts the Cargo updater container’s Rust base image from 1.94.0-bookworm back to 1.93.1-bookworm to help confirm whether the newer Cargo/libcurl stack is responsible for the observed flaky sparse-index download failures in production.
Changes:
- Downgrade the
docker.io/library/rustbase image used by the Cargo updater Dockerfile from1.94.0-bookwormto1.93.1-bookworm.
Show a summary per file
| File | Description |
|---|---|
cargo/Dockerfile |
Reverts the Rust base image tag to restore the previous Cargo toolchain stack for regression isolation. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
v-kbukum1
marked this pull request as draft
June 8, 2026 19:11
v-kbukum1
marked this pull request as ready for review
June 8, 2026 19:32
v-kbukum1
changed the title
v-abhishekbhaskar
approved these changes
Jun 8, 2026
v-kbukum1
force-pushed
the
revert-14383-dependabot/docker/cargo/library/rust-1.94.0-bookworm
branch
from
June 8, 2026 22:32
e957f23 to
1bb2da1
Compare
Contributor
Author
|
Fixed through dependabot/proxy#138 |
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.
Summary
Pins the Cargo updater image back from the current Rust/Cargo image line to Rust 1.93.1-bookworm for a controlled diagnostic revert.
We started seeing repeated Cargo sparse-index failures after the Rust/Cargo image updates, where Cargo fails while downloading crates.io index entries with: [8] Weird server reply (Invalid status line).
The suspected regression window includes the Cargo/libcurl stack introduced after 1.93.1. Cargo has had a related upstream issue with that curl stack while updating the crates.io index, which was mitigated upstream by downgrading curl-sys.
Why
This revert is intended to confirm whether the newer Cargo/libcurl stack is causing the flaky sparse-index failures in Dependabot production jobs. If the errors stop after reverting, we can follow up with Cargo/upstream using the narrower regression range. If they continue, that points investigation back toward crates.io/CDN, Dependabot proxying, or surrounding infrastructure.
Links