Skip to content

Conversation

@phil-opp
Copy link
Collaborator

@phil-opp phil-opp commented Sep 3, 2025

We often see uv hanging at this line https://github.com/astral-sh/uv/blob/d178e453684437889a30b3ffd17e56d695fba60d/crates/uv-fs/src/lib.rs#L677-L680 . By enabling debug output, we can hopefully see where the lock was acquired before.

See #1090

We often see `uv` hanging at this line https://github.com/astral-sh/uv/blob/d178e453684437889a30b3ffd17e56d695fba60d/crates/uv-fs/src/lib.rs#L677-L680 . By enabling debug output, we can hopefully see where the lock was acquired before.
@phil-opp phil-opp merged commit f23bb6d into main Sep 3, 2025
154 of 158 checks passed
@phil-opp phil-opp deleted the debug-log-ci branch September 3, 2025 16:16
haixuanTao added a commit that referenced this pull request Sep 16, 2025
## Description

Prior to this PR, `run_build_command` contains wrong implementation
which calls `cmd.spawn()` and `cmd.status()` sequentially, and since
both invocations execute the command, each build command is **executed
twice**. The issue is uncovered during my investigation of issue #1090 .

This PR addresses the issue by replacing `cmd.status()` with
`child.wait()`. Additionally, it also changes the process backend from
`std` to `tokio` to improve concurrency.

Since the issue has been resolved, #1137 is reverted to reduce verbosity
of CI logs.

## Related

Fixes #1090
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants