[v3-0-test] Unify connection not found exceptions between AF2 and AF3 (#52968) #53093
Conversation
This file contains hidden or 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
…ache#50371) (apache#52698) * Add back dag parsing pre-import optimization (apache#50371) Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> * Apply suggestions from code review --------- Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com> Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…pache#52902) (apache#52925) (cherry picked from commit 1996171) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
…mmit's (apache#52931) (apache#52942) We are still waiting for release of the Lucas's pre-commit after the Lucas-C/pre-commit-hooks#103 has been merged - and for now we need to use `bleeding-edge` for the repo. Also upgrades zizmor and solves using "env." in shell commands that might lead to security issues. (cherry picked from commit 535d71d)
…lient to re matches (apache#52960) (apache#52961) (cherry picked from commit 8e5c284) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
Follow up after apache#52967 -> from later discussions it turned out that it's not really the ~= that is wrong and ambiguous, but that just upper-binding of Python version is generally considered as a bad idea - and it's not Astral's view but it's general consensus that upper-binding of "python-requires" is bad. Since ~= implies upper-binding, simply replacing it with >= is likely the best option we can choose. (cherry picked from commit e9eb481)
) (apache#52987) Follow up after apache#52980 - there are still few more places where the ~= was used in requires-python. (cherry picked from commit 3f6f1db)
(cherry picked from commit 64d87e5) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
…apache#52988) (apache#53007) (cherry picked from commit a30bd70) Co-authored-by: Jun Jeong <121210928+givemechocopy@users.noreply.github.com>
…3005) * fix rollback from airflow3 * use fab for test * amend * fix test * revert condition fix and add shortcut if revisions are same * updating revision to 2.10.3 in condition * remove fab from tests (cherry picked from commit d458554) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
…apache#52297) (apache#53011) * docs: Update public interface documentation for Airflow 3.0+ for metadata direct access change * docs: replace direct metadata model imports in how-to examples with airflow.sdk * Make Public interface for Airflow 3 and add link for Airflow 2.11 * Fix PR comments * Update airflow-core/docs/public-airflow-interface.rst * Fix PR comments * Remove duplicates and remove RuntimeTaskInstanceProtocol as it is not public * Fix PR comments --------- (cherry picked from commit e8767b6) Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com> Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
* [v3-0-test] Fix log for skipped taks (apache#53024) (cherry picked from commit 0d6e417) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> * Fix CI --------- Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
…pache#53081) (apache#53086) (cherry picked from commit 3eaf4e9) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
(cherry picked from commit 5c2a2ec)
amoghrajesh
changed the title
amoghrajesh
changed the title
Contributor
Author
|
Intended for 3.0.4, do not merge for 3.0.3 |
kaxil
requested review from
Fokko,
bolkedebruin,
dstandish,
gopidesupavan,
jason810496,
jedcunningham and
potiuk
as code owners
kaxil
requested review from
bbovenzi,
bugraoz93,
eladkal,
ephraimbuddy,
hussein-awala,
josh-fell,
jscheffl,
mik-laj,
mobuchowski,
o-nikolas,
pierrejeambrun,
rawwar,
ryanahamilton,
shubhamraj-git and
vincbeck
as code owners
jscheffl
approved these changes
Jul 9, 2025
bugraoz93
approved these changes
Jul 10, 2025
kaxil
pushed a commit
that referenced
this pull request
Jul 11, 2025
kaxil
pushed a commit
that referenced
this pull request
Jul 11, 2025
82 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
(cherry picked from commit 5c2a2ec)
^ 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 airflow-core/newsfragments.