You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated dependency
Any — the failing package is non-deterministic across runs. Observed: serde_spanned, futures-util, futures-task, crossterm_winapi, regex, allocator-api2, reqwest, crossterm.
What you expected to see, versus what you actually saw
Expected: Dependabot opens a group update PR for Cargo dependencies.
Actual: Every run fails with dependency_file_not_resolvable. The root cause is curl error [8] Weird server reply (Invalid status line) when cargo attempts to download sparse registry index entries through Dependabot's proxy during lockfile resolution:
Updating crates.io index
error: failed to get `serde_spanned` as a dependency of package `toml v1.1.2`
Caused by:
download of se/rd/serde_spanned failed
Caused by:
failed to download from `https://index.crates.io/se/rd/serde_spanned`
Caused by:
[8] Weird server reply (Invalid status line)
Reproduced on two unrelated repositories on the same day:
LLM disclosure: This issue was drafted with AI assistance. I have personally verified the failure on two separate repositories and confirmed the logs and links are accurate.
Is there an existing issue for this?
Package ecosystem
cargo
Package manager version
N/A
Language version
N/A
Manifest location and content before the Dependabot update
Workspace root
/Cargo.toml: https://github.com/LilDojd/late-sh/blob/main/Cargo.tomldependabot.yml content
https://github.com/LilDojd/late-sh/blob/main/.github/dependabot.yml
Updated dependency
Any — the failing package is non-deterministic across runs. Observed:
serde_spanned,futures-util,futures-task,crossterm_winapi,regex,allocator-api2,reqwest,crossterm.What you expected to see, versus what you actually saw
Expected: Dependabot opens a group update PR for Cargo dependencies.
Actual: Every run fails with
dependency_file_not_resolvable. The root cause is curl error[8] Weird server reply (Invalid status line)when cargo attempts to download sparse registry index entries through Dependabot's proxy during lockfile resolution:Reproduced on two unrelated repositories on the same day:
Native package manager behavior
cargo updateruns successfully locally with no errors.Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
Any large Cargo workspace appears sufficient to trigger this. The helix workspace (https://github.com/LilDojd/helix/blob/master/Cargo.toml) reproduces it with a minimal dependabot.yml:
Note
LLM disclosure: This issue was drafted with AI assistance. I have personally verified the failure on two separate repositories and confirmed the logs and links are accurate.