potiuk commented on issue #26042: URL: https://github.com/apache/airflow/issues/26042#issuecomment-1230871968
> I've been having signal 11-related problems lately (ever since I started messing around with providers). Probably the core of this has something to do with a provider and is not a core airflow bug. Still, I think we should be a little more verbose when it comes to communicating this error. Surely. Signal 11 is SIGSEGV which generally means that there is a serious error with your installed libraries. I.e. we have completely no idea what is the error because likely your deployment is messed up (for example you have broken libraries installed. It's generally rather bad error indicating that you have done something, airflow maintainers could not foresee and generally it crashes python interpreter, so in-general there is no way to provide any information, because at the moment it crashes, we have no way to handle it. But If you think there is a better way and you would like to submit a fix to make a bettter message in this case - we are absolutely open to accept a fix. Since we do not know what is the root cause (somewhat broken environment in the way that crashes C-level library) you are probably one of the best people to be able to provide the fix - because you have the unique environment that generates this error. And since Airflow is created by > 2100 contributors - people like you who often contributed a fix when they had problem, you are most welcome to join the team. I will convert it to discussion and if you will be able to provide a fix that will provide a better description, that would be fantastic. -- 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]
