Sync v2-10-stable with v2-10-test(sync_v2_10_test) to release 2.10.4 #44641
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
…43205) (#43623) The scripts to update pip and uv version were not complete - they did not replace a few of our scripts and documentation. This was especially troublesome for doc replacement, because updating versions manually led to misalignments of tables in markdown. Lack of completeness of the upgrade caused #43197 and #43135 manual PRs to bump all references. Also an earlier upgrade caused the markdown table to be broken - with UV row table offset by 1. This PR fixes it: * all the scripts and docs are updated now * when markdown is updated, the table structure is not broken (cherry picked from commit 7ede73c)
…3587) (#43624) Breeze sometimes creates "internal" virtualenvs in local ".build" directory when it needs - for example in order to run k8s tests or for release management commands. This PR adds capability to switch breeze to use `uv` instead of `pip` to install depdendencies in those envs. You can now switch breeze to use uv by `breeze setup config --use-uv` and switch back to pip by `breeze setup config --no-use-uv`. (cherry picked from commit a2a0ef0)
…43607) (#43626) So far `breeze` fully supported only `pipx` installation. For example it would reinstall itself automatically with pipx if you attempted to run it from another workspace/checked out repository of Airflow, and it only provided instructions for pipx. With this PR: * the `uv tool` is preferred way to install breeze * the `pipx` is PSF-governance managed alternative * breeze will reinstall itself using uv if it has been installed with uv before when it is run from a different workspace or different airflow repo checked out in another folder Also documentation is updated to make `uv` the recommended tool and describing how to install it - with `pipx` provided as an alternative. Warning is printed in case pre-commit-uv is not installed with the pre-commit (pre-commit-uv significantly speeds up installation of the venvs by pre-commit). This warning also provides instructions how to install it. (cherry picked from commit ddc5670)
…#43683) (#43687) After some checks it turned out that reproducibility of produced packages depends not only on the build backend configured for the project but also on the build front-end used - because frontend is the one to modify meta-data in prepared packages - including the build tool used, it's version and metadata version supported by the front-end. That's why in order to maintain reproducibility for anyone who builds the packages, we have to pin not only the build backend in pyproject.toml (flit-core) but also build fronted used (flit). Since package preparation is done with breeze, we can do it by pinning flit (and just in case also flit-core) so that anyone who builds specific version of the package will use exactly the same flit as the person who built the original packages. This way we will avoid reproducibility problems experienced with 1.5.0 release of FAB. (cherry picked from commit 18ea01c)
) (#43695) When breeze is installed with both - pipx and uv, we do not know which version is available first on the path and self-upgrading breeze might not upgrade the one that is first. Therefore we detect that situation and fail self upgrade with appropriate instructions what to do (recommending leaving uv as faster) (cherry picked from commit ccd6586)
utkarsharma2
requested review from
eladkal,
potiuk,
ashb,
jedcunningham,
kaxil,
o-nikolas,
uranusjr,
ryanahamilton,
bbovenzi,
pierrejeambrun,
ephraimbuddy,
dstandish,
hussein-awala and
XD-DENG
as code owners
boring-cyborg
bot
added
area:API
This removes the whole section about helm, as it really isn't directly related to the XCom concept at all. I also simplified the section about containers as well - this one is a bit more practical, so I've left it. (cherry picked from commit 3747c91) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
…44457) * Fix Logs/utils * Fix test for Logs/utils * Fix by Review Comment - Added red color styling to lines based on the `currentLevel` - Added comments for new regExp * Refactor Logs/utils test cases
* [v2-10-test] Fix tests badge in README.md (#44505) (cherry picked from commit a242ff6) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com> * Adjust badge to `v2-10-test` branch * Update README.md * Fix PYPI README.md --------- Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
(cherry picked from commit b4f4ba8)
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
04d2dbc to
895a993
Compare
ephraimbuddy
reviewed
Dec 9, 2024
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
e328eb3 to
c3f6e1b
Compare
potiuk
approved these changes
Dec 9, 2024
ephraimbuddy
reviewed
Dec 9, 2024
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
7930d2a to
1fbdeca
Compare
ephraimbuddy
approved these changes
Dec 9, 2024
#43063) * Double-check TaskInstance state if it differs from Executor. * Update airflow/jobs/backfill_job_runner.py * Update airflow/jobs/backfill_job_runner.py * Update airflow/jobs/backfill_job_runner.py * Update airflow/jobs/backfill_job_runner.py * Update airflow/jobs/backfill_job_runner.py * Update airflow/jobs/backfill_job_runner.py --------- Co-authored-by: Utkarsh Sharma <utkarsharma2@gmail.com> (cherry picked from commit 90d6332)
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
1fbdeca to
a8e7e76
Compare
* Random doc typos * Update contributing-docs/testing/unit_tests.rst * Update contributing-docs/testing/unit_tests.rst --------- (cherry picked from commit 909ff71) Co-authored-by: D. Ferruzzi <ferruzzi@amazon.com> Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com> (cherry picked from commit b5f033a)
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
a8e7e76 to
625677d
Compare
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
625677d to
ea9bbd6
Compare
utkarsharma2
force-pushed
the
sync_2-10-test
branch
from
ea9bbd6 to
c083e45
Compare
kaxil
reviewed
Dec 10, 2024
| """""""""""""""" | ||
| - Update XCom docs around containers/helm (#44570) (#44573) | ||
|
|
||
| Miscellaneous |
There was a problem hiding this comment.
I see the changes related to #44184 in this PR but don't see its entry in changelog -- did you purposely remove it as a non-user facing change?
Making sure there isn't a bug in generation of the above changes
There was a problem hiding this comment.
Ya, since it was not a user facing change, I added a label - changelog:skip due which it got skipped from changelog.
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.
Time for 2.10.4rc1!