potiuk commented on issue #39717: URL: https://github.com/apache/airflow/issues/39717#issuecomment-2269784776
@scaoupgrade - @trlopes1974 . Yes. We actually discuseed it few comments above in case you missed it: > > It's a good idea and would solve at least one of the issues that can lead to that log message. I'm okay with the solution. Other issues can also lead to the scheduler sending thise log. > > Yeah - but one less is good :) And yes - as long as we have more details that we can diagnose it, we might also in the future address other similar issues - one thing at a time. I am actually proposing to close that issue here and if someone can open another similar issue with details that explain other issues of the same type with "related to THIS ISSUE" - it would be great. It's extremely hard to discuss and reason when multiple different issues are mixed in a single huge thread. Closing that one and opening new one seeing that it happens after fixing part of the issue seems like the best thing that we can dol Generally speaking - unless we see enough evidences that point to some issue that can be diagnosed and/or repreoduced, there is not much anyone can do about it. With the stack-trace from @trlopes1974, it was quite easy to figure out. PROPOSAL: maybe anyone who experiences this one, applies the patch from my PR and then see if they can still see the issue and if they do - open a new issue - hopefully with some details that will allow someone to diagnose it/ reproduce, once it's known that at last this one is already patched. The patch should be asy to apply on any version of Airflow. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
