-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Sync v2-6-stable with v2-6-test to release 2.6.1 #31133
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
Conversation
(cherry picked from commit 817f846)
The Airflow models have been accidentally removed from the docs when #28300 was implemented. The whole models documentation have been removed accidentally, even if there were references to the actual classes and packages used as the models package was entirely excluded. This PR fixes it by selectively including the models that should be included and by linking the package indexes directly in the public interface documentation. (cherry picked from commit 6720a90)
* Add missing changelog in 2.6.0 * Update RELEASE_NOTES.rst Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> * fixup! Add missing changelog in 2.6.0 --------- Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> (cherry picked from commit ea18edb)
(cherry picked from commit 070ecbd)
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I have one doubt about #30352 - it has new configuraiton param on one hand, but it does solve a problem where redis sentinel configuration was broken. So I would be in getting it in as it looks pretty safe/
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I have one doubt about #30352 - it has new configuraiton param on one hand, but it does solve a problem where redis sentinel configuration was broken. So I would be in getting it in as it looks pretty safe/
|
#31125 is missing from the release |
|
Let me move it to 2.7.0. since it added a config. I accessed it by the issue it closed and didn't look the code change. It should be 2.7.0 |
This comment was marked as resolved.
This comment was marked as resolved.
👑 |
|
(Hmmm, no guillotine emoji. Shame) |
|
I just merged #31101 and set its milestone back to 2.6.1 fyi |
|
Here's my PR #31149 |
…in (#31149) The current published plugin calls `_redact_all` directly, so when we added the `max_depth` parameter in 2.6 (precisely so it didn't need to call this private function directly!) we broke that. This change leads to some worrying logs appearing in task logs for anyone with the plugin installed: ``` [2023-05-05, 11:56:17 BST] {utils.py:490} WARNING - Unable to redact []Error was: TypeError: SecretsMasker._redact_all() missing 1 required positional argument: 'max_depth' [2023-05-05, 11:56:17 BST] {utils.py:490} WARNING - Unable to redact []Error was: TypeError: SecretsMasker._redact_all() missing 1 required positional argument: 'max_depth' [2023-05-05, 11:56:17 BST] {utils.py:490} WARNING - Unable to redact NoneError was: TypeError: SecretsMasker._redact_all() missing 1 required positional argument: 'max_depth' ``` This patch makes that previous change backwards compatible for that with no change in behaviour for new code. (cherry picked from commit 25e3159)
(cherry picked from commit 433ed2c)
…s found (#31101) Generally speaking when a task is done we should not read from logs server, because we assume for log persistence that users will either set up shared drive or enable remote logging. But if they don't do that, and therefore we don't find remote or local logs, we'll check worker for served logs as a fallback. Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> (cherry picked from commit 672ee7f)
this is not in release notes yet, or it shouldn't? |
pygithub now requires to specify if a search is for pull request or issues and not both. Also, a fix on searching old rc versions after removing the asf svn repo (cherry picked from commit 3d6ad50)
If you run a task via the cli with `cfg_path`, we also run `configure_vars` again so that the globals built from the config file can be updated. We were also initializing pluggy in that function, however, which was effectively removing any user provided hooks. We will move the initializing of pluggy out of that function, making it safe to run again by the task command. This primarily impacted KPOs, as they wouldn't have been passed through any `pod_mutation_hooks`. (cherry picked from commit 71c2627)
(cherry picked from commit 2890652)
1938aed to
05d8d93
Compare
(cherry picked from commit 86d62d3)
Time for
2.6.1rc1!