Skip to content

Make project and interpreter lock acquisition non-fatal#14404

Merged
charliermarsh merged 3 commits intomainfrom
charlie/nf
Jul 2, 2025
Merged

Make project and interpreter lock acquisition non-fatal#14404
charliermarsh merged 3 commits intomainfrom
charlie/nf

Conversation

@charliermarsh
Copy link
Member

@charliermarsh charliermarsh commented Jul 2, 2025 •
edited
Loading

Summary

If we fail to acquire a lock on an environment, uv shouldn't fail; we should just warn. In some cases, users run uv with read-only permissions for their projects, etc.

For now, I kept any locks acquired in the cache as hard failures, since we always need write-access to the cache.

Closes #14411.

@charliermarsh charliermarsh added the enhancement New feature or improvement to existing functionality label Jul 2, 2025
@charliermarsh charliermarsh marked this pull request as ready for review July 2, 2025 01:19
@charliermarsh charliermarsh temporarily deployed to uv-test-registries July 2, 2025 01:21 — with GitHub Actions Inactive
@charliermarsh charliermarsh temporarily deployed to uv-test-registries July 2, 2025 01:26 — with GitHub Actions Inactive
zanieb
zanieb approved these changes Jul 2, 2025
View reviewed changes
Copy link
Member

@zanieb zanieb left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these be real user-facing warnings instead of tracing? It might be step too far to go from an error to only showing failures with -v though it might be nice to wait until we add a hint to resolve the problem

@zanieb
Copy link
Member

zanieb commented Jul 2, 2025 •
edited
Loading

You probably could write a test for this, e.g., by setting TMP to a tmpdir without write permissions? It'd be nice to have coverage for when we add more messaging on how to resolve the problem.

@zanieb zanieb mentioned this pull request Jul 2, 2025
Closed
@charliermarsh
Copy link
Member Author

charliermarsh commented Jul 2, 2025

Added a test, but per Discord, agreed to keep these non-user-facing for now.

@charliermarsh
Copy link
Member Author

charliermarsh commented Jul 2, 2025

(And verified that the test fails on main with the same trace as in #14411.)

@charliermarsh charliermarsh added bug Something isn't working and removed enhancement New feature or improvement to existing functionality labels Jul 2, 2025
@charliermarsh charliermarsh temporarily deployed to uv-test-registries July 2, 2025 17:51 — with GitHub Actions Inactive
@charliermarsh charliermarsh temporarily deployed to uv-test-registries July 2, 2025 17:54 — with GitHub Actions Inactive
@charliermarsh charliermarsh merged commit 743260b into main Jul 2, 2025
89 checks passed
@charliermarsh charliermarsh deleted the charlie/nf branch July 2, 2025 18:03
@BrewTestBot BrewTestBot mentioned this pull request Jul 2, 2025
Merged
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Jul 6, 2025
@tmeijn
build(deps): update astral-sh/uv to v0.7.19
db7b32f 
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [astral-sh/uv](https://github.com/astral-sh/uv) | patch | `0.7.16` -> `0.7.19` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>astral-sh/uv (astral-sh/uv)</summary>

### [`v0.7.19`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0719)

[Compare Source](astral-sh/uv@0.7.18...0.7.19)

The **[uv build backend](https://docs.astral.sh/uv/concepts/build-backend/) is now stable**, and considered ready for production use.

The uv build backend is a great choice for pure Python projects. It has reasonable defaults, with the goal of requiring zero configuration for most users, but provides flexible configuration to accommodate most Python project structures. It integrates tightly with uv, to improve messaging and user experience. It validates project metadata and structures, preventing common mistakes. And, finally, it's very fast — `uv sync` on a new project (from `uv init`) is 10-30x faster than with other build backends.

To use uv as a build backend in an existing project, add `uv_build` to the `[build-system]` section in your `pyproject.toml`:

```toml
[build-system]
requires = ["uv_build>=0.7.19,<0.8.0"]
build-backend = "uv_build"
```

In a future release, it will replace `hatchling` as the default in `uv init`. As before, uv will remain compatible with all standards-compliant build backends.

##### Python

- Add PGO distributions of Python for aarch64 Linux, which are more optimized for better performance

See the [python-build-standalone release](https://github.com/astral-sh/python-build-standalone/releases/tag/20250702) for more details.

##### Enhancements

- Ignore Python patch version for `--universal` pip compile ([#&#8203;14405](astral-sh/uv#14405))
- Update the tilde version specifier warning to include more context ([#&#8203;14335](astral-sh/uv#14335))
- Clarify behavior and hint on tool install when no executables are available ([#&#8203;14423](astral-sh/uv#14423))

##### Bug fixes

- Make project and interpreter lock acquisition non-fatal ([#&#8203;14404](astral-sh/uv#14404))
- Includes `sys.prefix` in cached environment keys to avoid `--with` collisions across projects ([#&#8203;14403](astral-sh/uv#14403))

##### Documentation

- Add a migration guide from pip to uv projects ([#&#8203;12382](astral-sh/uv#12382))

### [`v0.7.18`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0718)

[Compare Source](astral-sh/uv@0.7.17...0.7.18)

##### Python

- Added arm64 Windows Python 3.11, 3.12, 3.13, and 3.14

  These are not downloaded by default, since x86-64 Python has broader ecosystem support on Windows.
  However, they can be requested with `cpython-<version>-windows-aarch64`.

See the [python-build-standalone release](https://github.com/astral-sh/python-build-standalone/releases/tag/20250630) for more details.

##### Enhancements

- Keep track of retries in `ManagedPythonDownload::fetch_with_retry` ([#&#8203;14378](astral-sh/uv#14378))
- Reuse build (virtual) environments across resolution and installation ([#&#8203;14338](astral-sh/uv#14338))
- Improve trace message for cached Python interpreter query ([#&#8203;14328](astral-sh/uv#14328))
- Use parsed URLs for conflicting URL error message ([#&#8203;14380](astral-sh/uv#14380))

##### Preview features

- Ignore invalid build backend settings when not building ([#&#8203;14372](astral-sh/uv#14372))

##### Bug fixes

- Fix equals-star and tilde-equals with `python_version` and `python_full_version` ([#&#8203;14271](astral-sh/uv#14271))
- Include the canonical path in the interpreter query cache key ([#&#8203;14331](astral-sh/uv#14331))
- Only drop build directories on program exit ([#&#8203;14304](astral-sh/uv#14304))
- Error instead of panic on conflict between global and subcommand flags ([#&#8203;14368](astral-sh/uv#14368))
- Consistently normalize trailing slashes on URLs with no path segments ([#&#8203;14349](astral-sh/uv#14349))

##### Documentation

- Add instructions for publishing to JFrog's Artifactory ([#&#8203;14253](astral-sh/uv#14253))
- Edits to the build backend documentation ([#&#8203;14376](astral-sh/uv#14376))

### [`v0.7.17`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0717)

[Compare Source](astral-sh/uv@0.7.16...0.7.17)

##### Bug fixes

- Apply build constraints when resolving `--with` dependencies ([#&#8203;14340](astral-sh/uv#14340))
- Drop trailing slashes when converting index URL from URL ([#&#8203;14346](astral-sh/uv#14346))
- Ignore `UV_PYTHON_CACHE_DIR` when empty ([#&#8203;14336](astral-sh/uv#14336))
- Fix error message ordering for `pyvenv.cfg` version conflict ([#&#8203;14329](astral-sh/uv#14329))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC42Mi4xIiwidXBkYXRlZEluVmVyIjoiNDAuNjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
@Fogapod Fogapod mentioned this pull request Jul 9, 2025
Closed
@EliteTK EliteTK mentioned this pull request Dec 15, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zanieb zanieb zanieb approved these changes

@oconnor663 oconnor663 Awaiting requested review from oconnor663

Assignees

No one assigned

Labels

bug Something isn't working

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Since 0.7.14, uv tries to write to .venv, even when frozen

2 participants

@charliermarsh @zanieb