Skip to content

uv publish can panic after a network failure #17090

@konstin

Description

@konstin

I can reliable get uv to panic by toggling network on and off during publishing a large wheel.

$ UV_HTTP_TIMEOUT=3 uv publish debug/dist/* --token ferris
Publishing 2 files to https://upload.pypi.org/legacy/
Uploading debug-0.0.4-py3-none-any.whl (854.7MiB)
warning: Transient failure while handling response for https://upload.pypi.org/legacy/; retrying after 0s...

thread 'main2' (501447) panicked at crates/uv/src/commands/reporters.rs:300:35:
no entry found for key
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main2' (501447) panicked at crates/uv/src/commands/reporters.rs:221:38:
called `Result::unwrap()` on an `Err` value: PoisonError { .. }

thread 'main' (501446) panicked at /home/runner/work/uv/uv/crates/uv/src/lib.rs:2540:10:
Tokio executor failed, was there a panic?: Any { .. }

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions