豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

[cargo] "Weird server reply (Invalid status line)" from proxy when downloading sparse index entries #14743

@LilDojd

Description

@LilDojd

Is there an existing issue for this?

  • I have searched the existing issues

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.toml

dependabot.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:

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:

Native package manager behavior
cargo update runs 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:

version: 2
updates:
  - package-ecosystem: "cargo"
    directory: "/"
    schedule:
      interval: "weekly"
    groups:
      rust-dependencies:
        update-types:
          - "minor"
          - "patch"

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.

Metadata

Metadata

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions