Sync v2-8-stable with v2-8-test to release 2.8.0 #36065
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
No need to have trigger running -- will just run them async. (cherry picked from commit 7b37a78)
* change max box height in ActionModal.tsx * changed max box height in ActionModal.tsx (cherry picked from commit 9a1dceb)
(cherry picked from commit 3b3ebaf)
* Relax mandatory requirement for start_date when schedule=None * Updated run_type in unit tests * Added check for empty start_date and non empty schedule * Fix the build failures * Fix the build failures * Update based on review comments (cherry picked from commit 930f165)
* Add a public interface for custom weight_rule implementation * Remove _weight_strategy attribute * Move priority weight calculation to TI to support advanced strategies * Fix loading the var from mapped operators and simplify loading it from task * Update default value and deprecated the other one * Update task endpoint API spec * fix tests * Update docs and add dag example * Fix serialization test * revert change in spark provider * Update unit tests (cherry picked from commit 3385113)
…5924) Recent Cython release caused pymssql package failures when they were installed on ARM platform. This had been workarounded in the #32748, but since pymssql as of 2.1.8 supports new Cython, we can remove the workaround and bump the minimum version of pymsssql. This also makes it possible to remove the whole MSSQL client section from the image if we decide to - because this section will only install the odbc client that has been pre-installed to support MSSQL as metadata DB for Airflow core. (cherry picked from commit 4f060a4)
(cherry picked from commit d37b91c)
(cherry picked from commit 7594b7a)
(cherry picked from commit cbb9c4f)
(cherry picked from commit 9bcee9d)
When we build on ci a pre-release version of provider, and we want to include packages that have >= CURRENTLY_RELEASED_VERSION we have to make sure that those packages are built from sources during building of PROD image. Otherwise they will not be installable on CURRENT_VERSION.dev0, CURRENT_VERSION.rc* etc. Until we "Actually" release a provider we should have a way to build such provider from sources. This is the CI version of it, once we have it working we can also apply it to the workflow that releases images to dockerhub. (cherry picked from commit cf052dc)
This enables an alternative ObjectStoragePath init syntax, using the auth section in the URI to supply conn ID instead of a separate keyword argument. The explicit keyword argument is honored if supplied. (cherry picked from commit ab87cd0)
…6003) Following the lazy consensus to change the "latest" image to point to "newest" Python version, we are changing the release method to follow it. https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3 (cherry picked from commit 4117f1b)
(cherry picked from commit c26aa12)
* Add multiselect to run state in grid view * Fix tests * Multiselect for run types, UI nits, refactor * Fix tests, refactor * Simplify multiselect value * Nits and refactor * Use arrays instead of serializing to csv * Fix tests and global axios paramsSerializer to null (cherry picked from commit 9e28475)
* Change Trigger UI to use HTTP POST in web ui, GET always shows trigger form * Adjust tests to changed behavior of trigger handling, expects data submitted in POST (cherry picked from commit f5d8027)
…n log tab (#36025) * Use dropdown instead of buttons when there are more than 10 retries in log tab. * Update airflow/www/static/js/dag/details/taskInstance/Logs/index.tsx Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com> --------- Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com> (cherry picked from commit fd09883)
(cherry picked from commit 549fac3)
Seems that pytest-asyncio 0.23.1 break our asyncio tests. We are temporarily limiting it until pytest-dev/pytest-asyncio#703 is solved or answered. (cherry picked from commit 9845b40)
…ies (#36022) * Add the section describing the security model of DAG Author capabilities This change codifies and explains assumptions and decisions made by Airflow maintainers with regards to capabilities of DAG Authors. While DAG authors are pretty powerful and capable actors in Airflow, they cannot do everything and Deployment Managers haw ways to restrict their potential capabilities, especially in the context of influencing other tasks and common components such as Scheduler, Webserver and Triggerer. This PR adds a chapter explaining those assumptions and decisions and tell the Deployment Managers what responsibilities they have with that regardsm and what mechanismes they currently have available to limit capabilities of DAG Authors. * Update docs/apache-airflow/security/security_model.rst Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> * Update docs/apache-airflow/security/security_model.rst Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> --------- Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> (cherry picked from commit 395ac46)
Thahnks to our report and bisecting the reason (it was caused by bad handling of the "test*.txt" handling) we can now remove the upper-binding for pytest-asyncio as 0.23.2 version has been released (cherry picked from commit 55eac5e)
* Add XCom tab to Grid * Combine showLogs and showXcom logic evaluation to isIndividualTaskInstance * Remove link to /xcom page from UI grid view * Use consistent naming to distinguish XcomCollection and XcomEntry * Refactor boolean vars (cherry picked from commit 77c0103)
I think the date 14.19.2023 is wrong--should it be 14.09.2023 (= September 14, 2023)? (cherry picked from commit 55d8137)
boring-cyborg
bot
added
area:production-image
ephraimbuddy
force-pushed
the
v2-8-test
branch
from
786ae6b to
e71373a
Compare
eladkal
reviewed
Dec 5, 2023
Cluster Activity UI shows `FAILED TO FETCH DATA` error in pools section. Users with Viewer role do not have permission to read pools. (cherry picked from commit 8ae67a0)
Co-authored-by: Daniel Standish <15932138+dstandish@users.noreply.github.com> (cherry picked from commit c4549d7)
(cherry picked from commit 58e264c)
ephraimbuddy
force-pushed
the
v2-8-test
branch
from
e71373a to
9176c28
Compare
ephraimbuddy
force-pushed
the
v2-8-test
branch
from
9176c28 to
454add4
Compare
potiuk
force-pushed
the
v2-8-test
branch
2 times, most recently
from
c5edc24 to
f7b6699
Compare
The change #35856 optimized waiting time before PROD image builds start - rather than waiting for full constratints generation, the PROD image building just used source constraints generated right after building the CI image quickly. This is fine for main because there we install airflow and packages using constraints from sources, but for release branches we use the provider constraints - in order to be able to install providers from PyPI rather than from sources. This means that we have to wait for constraints generation to complete before we start building PROD images - because we need to download the constraints generated there to use them. Unfortunately GitHub Actions do not have conditional dependencies depending on where the workflow is run - so instead we have to effectively duplicate PROD build steps and skip steps in them instead.
ephraimbuddy
force-pushed
the
v2-8-test
branch
from
f7b6699 to
f819449
Compare
|
I'd really prefer #35820 to be in, as otherwise we would have to deal with backwards compatibility |
eladkal
approved these changes
Dec 9, 2023
potiuk
approved these changes
Dec 10, 2023
ephraimbuddy
force-pushed
the
v2-8-test
branch
2 times, most recently
from
b167d36 to
558e965
Compare
ephraimbuddy
force-pushed
the
v2-8-test
branch
from
558e965 to
d0c1c45
Compare
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.8.0rc1!