Protect against missing .uv cache #45605
Merged
Conversation
This file contains 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
potiuk
requested review from
shahar1,
jscheffl,
eladkal,
hussein-awala,
jedcunningham,
ephraimbuddy and
utkarsharma2
|
At this moment canary builds are failing in v2-10-test because of that. |
potiuk
added
the
canary
In v2-10-test for now we have no uv used to install static checks because we cannot use latest uv version and pre-commit-uv with python 3.8.
potiuk
force-pushed
the
protect-against-uv-cache-missing
branch
from
17eabb6 to
f50daa9
Compare
jedcunningham
approved these changes
Jan 13, 2025
shahar1
approved these changes
Jan 13, 2025
hussein-awala
approved these changes
Jan 13, 2025
40 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In v2-10-test for now we have no uv used to install static checks because we cannot use latest uv version and pre-commit-uv with python 3.8.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.