divyanshus2404 commented on issue #76992: URL: https://github.com/apache/airflow/issues/76992#issuecomment-6856533678
Hi, I'd like to work on this. My read of the fix direction from the report: with multi-team on, make the trigger-reuse lookup team-aware, and scope each parse's add/remove of watchers to its own team (with the cross-team stand-in only while that team still schedules on the asset). I'll start with a failing test reproducing the two-team shared-watcher case and post my plan here before the PR. (Previously contributed the SparkSubmitHook masking fix, #71711.) -- 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]
