potiuk commented on PR #40141: URL: https://github.com/apache/airflow/pull/40141#issuecomment-2156640300
Here again, I'd say, we should aim for giving a lot more self-help options for the users. Users will not understand what it means and effectively they will come-back to our issues/discussions when they see such message. Which - if they do - it does not matter if it says 'killed externally' or 'changed state' because we will know where in the code the message is generated. So if I'd like to improve this one, rather than only stating what happened, I'd link to a documentation page (troubleshooting) where users (but also other committers) could read more about the are that is affected here and what could be possible reasons for such problems. Not only that would be more helpful but it could be a good start to add more possible reasons as we find them. For example if we find a reason for similar issue which was unexpected, it makes it easy to just add a new "possible cause and remediations" to the list of those issues. Over time it might become helpful also for non-committers - and users helping each other. Even if somoene will not follow such link or not understand consequences, another person looking at the discussion or slack, might actually do it (we've seen it multiple times in the past that when we had "common" problems and documented them, over time more and more people looked at the documentation and helped each other pointing to the docs. -- 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]
