sdebruyn opened a new issue, #28499: URL: https://github.com/apache/airflow/issues/28499
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened Airflow 2.4.3 Just like in issue #26599 I get a lot of warnings saying I'm registering dependencies multiple times. With a little bit of debugging, I found the culprit:. Some of my tasks have multiple outputs, which are then used by other tasks. These are TaskFlow-based tasks. The task dependency is added when it detects the first XComArg and then it's added again with every following XComArg, generating these warnings. Call stack: <img width="319" alt="image" src="https://user-images.githubusercontent.com/963413/208720058-bf66a57c-8849-4fda-9bd4-b570eac4ce93.png"> ### What you think should happen instead You should not see the warnings if the cause is that you're using multiple outputs from the same upstream task. ### How to reproduce Create a function that returns a `dict[str, str]` and make it a task with `@task(multiple_outputs=True)`. Then create another task that takes multiple of these outputs as input. ### Operating System Debian GNU/Linux 11 (bullseye) ### Versions of Apache Airflow Providers not relevant ### Deployment Official Apache Airflow Helm Chart ### Deployment details You can get this with unit tests just by creating a `DagBag` instance with your DAGs. ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
