hterik commented on issue #43171: URL: https://github.com/apache/airflow/issues/43171#issuecomment-2425691353
I can recommend this guide from Google about writing good error messages: https://developers.google.com/tech-writing/error-messages. The rest of the courses in that book are also really good btw. > an error like `Celery command failed on host` can be transformed or displayed with something like "`Please check your DAG processor timeout variable for this`". Actionable errors are good, but has to be done very carefully, because if it gives misleading advice it will lead users down chasing the wrong rabbit hole. For example this log in `standard_task_runner.py` is most of the time not due to memory running out: `"Job %s was killed before it finished (likely due to running out of memory)",`. I've seen our engineers chasing memory issues in vain countless of times because of that message. (yes we should have filed a PR :smile:) -- 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]
