[GitHub] [airflow] potiuk commented on pull request #27381: Additional info about Segmentation Violation in LocalTaskJob

[GitBox <gi...@apache.org>]

potiuk commented on PR #27381:
URL: https://github.com/apache/airflow/pull/27381#issuecomment-1297103029

   @Taragolis - maybe we should also add a link to https://stackoverflow.com/questions/16731115/how-to-debug-a-python-segmentation-fault (or copying advice to it)  and explanation that it's on user's discretion. Some of the previous discussions I had were that the users have an expectation that "airflow" will be better in diagnosing it, but there is really not much we can do in Airflow 
   
   Some users apparently had hard time to believe us when we tell them that we can't provide any more useful information on the root cause of the problem and they have to perform their own trial/error or deep C-level debugging. I think that messaging we do here might be great in setting expectations here and giving the users information (that otherwise can be googled) actually "written" by someone rather than "told" by people commenting on the issues is necessary. Especially in this issue https://github.com/apache/airflow/discussions/24463
   
   Question: @binary-signal - would it be more believable if you saw those proposed messages written in the logs and the message that you need to do your own investigation to find a root cause? I believe this way we can at least avoid unnecesayr discussions when there are unrealistic expectations.


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org