Fix uv export missing --no-emit-workspace in CI entrypoint#64020
Merged
potiuk merged 1 commit intoapache:mainfrom Mar 21, 2026
Merged
Fix uv export missing --no-emit-workspace in CI entrypoint#64020potiuk merged 1 commit intoapache:mainfrom
uv export missing --no-emit-workspace in CI entrypoint#64020potiuk merged 1 commit intoapache:mainfrom
Conversation
…l lock issues Without `--no-emit-workspace`, the constraint file generated by `uv export` included workspace packages which forced installation of newer versions of dependencies like pyiceberg into the shared UV cache. When multiple parallel CI tasks ran simultaneously, this caused installation lock contention in the distributed UV cache. Adding `--no-emit-workspace` ensures only external dependencies are emitted in the constraint file, avoiding unnecessary package resolution that interferes with parallel task execution.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
amoghrajesh
approved these changes
Mar 21, 2026
fat-catTW
pushed a commit
to fat-catTW/airflow
that referenced
this pull request
Mar 22, 2026
…l lock issues (apache#64020) Without `--no-emit-workspace`, the constraint file generated by `uv export` included workspace packages which forced installation of newer versions of dependencies like pyiceberg into the shared UV cache. When multiple parallel CI tasks ran simultaneously, this caused installation lock contention in the distributed UV cache. Adding `--no-emit-workspace` ensures only external dependencies are emitted in the constraint file, avoiding unnecessary package resolution that interferes with parallel task execution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--no-emit-workspaceflag touv exportinentrypoint_ci.shWithout
--no-emit-workspace, the constraint file generated byuv exportincluded workspace packages, which forced installation of newer versions of
dependencies (e.g. pyiceberg) into the shared UV cache. When multiple parallel
CI tasks ran simultaneously, this caused installation lock contention in the
distributed UV cache, leading to intermittent failures.
Adding
--no-emit-workspaceensures only external dependencies are emittedin the constraint file, avoiding unnecessary package resolution that
interferes with parallel task execution.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.6 following the guidelines