astral-sh/uv

Loop on `EINTR` on file lock acquisition

Open

#15,996 opened on Sep 22, 2025

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

Repository metrics

Stars
 (84,934 stars)
PR merge metrics
 (Avg merge 6d 16h) (222 merged PRs in 30d)

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

Research direction
Find all locations in the codebase where file locks are acquired using flock or similar syscalls, and ensure that the call is retried on EINTR (interrupted system call).
Tech stack
rust
Domain
backendtooling
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustfile locking concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60