vandonr-amz commented on PR #29051: URL: https://github.com/apache/airflow/pull/29051#issuecomment-1397739480
> Can we maybe also split the watcher and what happens after to a separate table (indicating this is a teardown?). We have enough of a convention to know it I think and that would be even more explicit. I thought about that be couldn't find a nice way to "detect" whether a task was part of the teardown or not... Is the watcher supposed to be the "separator" ? Because in that case, `disable_job_queue` is part of the teardown and apparently executed before the watcher (I sort by end_date, maybe that's wrong ?) Also, trying this on example_lambda for instance, there is a teardown, but the watcher is marked as skipped ? > Also a nice idea could be to add colors to status. Yes, I'd love to, but very personal reason not to: the log collector we use keeps the escape codes uninterpreted, so it actually makes the output less readable, but maybe it's something we should fix on our end, idk. -- 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]
