astral-sh/uv

Loop on `EINTR` on file lock acquisition

Open

#15996 opened on Sep 22, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
help wanted

Description

We should loop on EINTR, and probably in the blocking cases too, unless I'm missing something that already does that.

Originally posted by @geofft in https://github.com/astral-sh/uv/pull/15992#discussion_r2370330069

Contributor guide

Tech stack
rust
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic RustUnderstanding of file locking and EINTR
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the file lock acquisition code in the uv repository, likely in crates/uv fs or similar. The issue references PR #15992 and a discussion comment; look at that PR to understand the current code. The fix involves wrapping lock acquisition in a loop that retries on EINTR. Check the relevant file locking functions to ensure all blocking lock calls handle EINTR correctly.