Uh oh!
There was an error while loading. Please reload this page.
AIP-72: Gracefully handle 'not-found' XCOMs in task sdk API client - #45344
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jscheffl
left a comment
There was a problem hiding this comment.
Looks good, just one comment. But not critical to move ahead.
8862d7d to
f8e4be0CompareUh oh!
There was an error while loading. Please reload this page.
potiuk
commented
Jan 2, 2025
@amoghrajesh - can you please rebase that one -> we found and issue with @jscheffl with the new caching scheme - fixed in #45347 that would run "main" version of the tests. I am asking in all affected PRs to rebase. |
Uh oh!
There was an error while loading. Please reload this page.
amoghrajesh
commented
Jan 2, 2025
Oh ok, let me rebase this one |
amoghrajesh
commented
Jan 3, 2025
Hi @uranusjr are you ok with the reply on this comment? #45344 (comment) |
7c807b7 to
482fab5Compare…pache#45344) * AIP-72: Gracefully handle not-found XCOMs in task sdk API client * re raising exception for non 404
…pache#45344) * AIP-72: Gracefully handle not-found XCOMs in task sdk API client * re raising exception for non 404
closes: #45341
Testing results
DAG used:
Legacy
Task 1 XCom pushed:

Task 2 XCom consumed as None when absent:

Task SDK
Task 1 XCom pushed:

Task 2 XCom consumed as None when absent:

^ 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 newsfragments.