Skip to content

HTTP/2 stream errors aren't considered spurious network failures #6788

@alexcrichton

Description

@alexcrichton

First discovered in these logs, it looks like Cargo isn't correctly detecting a spurious network failure:

error: failed to download from `https://crates.io/api/v1/crates/docopt/1.0.2/download`

Caused by:
  [92] Stream error in the HTTP/2 framing layer (HTTP/2 stream 11 was not closed cleanly: INTERNAL_ERROR (err 2))

That's one that Cargo should automatically restart and attempt to redownload!

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-networkingArea: networking issues, curl, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions