-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync v2-9-stable with v2-9-test to release 2.9.3 #40546
Conversation
* Improve trigger UI for string array format validation The schema argument in a Param definition is used to detemine the relevant UI element. When the type of a Param is `array` a simple textarea is rendered. When additionally a schema for the items of the array is provided, the UI element previously switched to a CodeMirror box that expects pure JSON inputs. For strings a textarea is presented now, to keep the same behaviour than without a format definition. Besides that the jinja template now accesses the `items` member of the schema correctly to avoid problems with empty `items` arrays. * Add details about the attribute `items` for the type `array` (cherry picked from commit 914bccc)
Remove the word "docker-compose" in PyPI section. (cherry picked from commit 32cf8cf)
(cherry picked from commit 9bcf665)
(cherry picked from commit 16e0182)
* Fix grammer dags.rst To say "add Operator/Task to the DAG" even though DAG is an argument of Operator constructor, and use the word "with statement" explicitly instead of context manger to be friendly to Python beginner. * Fix grammer in dags.rst Because there is a direction in relationship, it's somehow confuse to say that they depend on each other. * Fix grammer in dags.rst (cherry picked from commit b03aa6c)
(cherry picked from commit a31b10e)
(cherry picked from commit 4723dbe)
Codecov3 uses deprecated node version and generates warnings. (cherry picked from commit 27579cb)
highlight task_group decorator and dependency between task and task group. (cherry picked from commit 340d6b0)
Signed-off-by: Kacper Muda <mudakacper@gmail.com> (cherry picked from commit 072c63b)
(cherry picked from commit e9e3c93)
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 1533ba6)
* Ensures DAG params order regardless of backend Fixes #40154 This change adds an extra attribute to the serialized DAG param objects which helps us decide the order of the deserialized params dictionary later even if the backend messes with us. I decided not to limit this just to MySQL since the operation is inexpensive and may turn out to be helpful. I made sure the new test fails with the old implementation + MySQL. I assume this test will be executed with MySQL somewhere in the build actions? * Removes GitHub reference Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> * Serialize DAG params as array of tuples to ensure ordering Alternative to previous approach: We serialize the DAG params dict as a list of tuples which _should_ keep their ordering regardless of backend. Backwards compatibility is ensured because if `encoded_params` is a `dict` (not the expected `list`) then `dict(encoded_params)` still works. * Make backwards compatibility more explicit Based on suggestions by @uranusjr with an additional fix to make mypy happy. --------- Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> (cherry picked from commit 2149b4d)
Co-authored-by: raphaelauv <raphaelauv@users.noreply.github.com> (cherry picked from commit 205ad57)
(cherry picked from commit d5a7544)
(cherry picked from commit 2587295)
(cherry picked from commit bffb7b0)
--------- Signed-off-by: merobi-hub <merobi@gmail.com> (cherry picked from commit 16b17f7)
(cherry picked from commit f5079db)
* Change httpx to requests in file_task_handler - httpx does not support CIDRs in NO_PROXY - simply, convert httpx to requests, issues done - related issue: #39794 * Add cidr no_proxy test test_log_handlers.py * Apply monkeypatch fixture --------- Co-authored-by: scott-py <scott.py@kakaocorp.com> (cherry picked from commit 1ddadf5)
(cherry picked from commit 5690439)
BTW. Depending how much we are in a hurry, but it might be worth to wait for the wave of providers being currently voted to be released and regenerate constraints after that, to get the latest providers - there are a few important fixes there. |
Yeah. Makes sense. We can wait. |
117d275
to
b55aaa4
Compare
(cherry picked from commit b49db97)
--------- Co-authored-by: Jacob Lee <seungmin_lee3@apple.com> (cherry picked from commit 2f9b23d)
* Further clarify triage process * update * update (cherry picked from commit 90a6d7f)
- minor rephrase of example (cherry picked from commit 5b2becb)
(cherry picked from commit ed6849e)
(cherry picked from commit a8c4830)
Fix import statement for DatasetOrTimetable example (cherry picked from commit a984d97)
Mention that ``serialize`` cannot return bytes (cherry picked from commit 49ded9f)
(cherry picked from commit 77a9850)
* Skip checking subdagslist if taskinstance state is skipped * linter fixes (cherry picked from commit ec5da92)
PostgresOperator's reference page says it's deprecated. I am not knowledgeable enough to write a tutorial. I think if someone reads the guide (I linked to in my change) they will be able to use this tutorial as well. (cherry picked from commit a10ac28)
Providers are released |
Thanks @eladkal we'll start the release process for rc1. |
Update release notes Update RELEASE_NOTES.rst Update release notes Update RELEASE_NOTES Fix static checks Update RELEASE_NOTES.rst Updated release date Fix static check update release notes
(cherry picked from commit 97b88fd)
Time for 2.9.3rc1!