You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/06/13 19:32:10 UTC

[GitHub] [airflow] josh-fell commented on pull request #24401: handle exception when resolving XComArg

josh-fell commented on PR #24401:
URL: https://github.com/apache/airflow/pull/24401#issuecomment-1154349332

   > Since the downstream should not run if any of its depended upstream XCom values fail to resolve ... It would be OK if you modify resolve instead and return None from them when the referred upstream is SKIPPED.
   
   I think these points are key. A [similar issue](https://github.com/apache/airflow/issues/23942) was raised earlier, but this related issue involves an upstream task _succeeding_ and returning no `XComs` to resolve. We shouldn't discount this scenario during any accounting here. @uranusjr I'm curious to hear your thoughts on #23942.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org