Taragolis commented on issue #27307: URL: https://github.com/apache/airflow/issues/27307#issuecomment-1293149873
@samsudinde this is not first time when issue with `Negsignal.SIGSEGV` appear: - https://github.com/apache/airflow/issues/16243 - https://github.com/apache/airflow/issues/20309 - https://github.com/apache/airflow/discussions/24463 It is very hard to debug segmentation violation error. You might [try to debug](https://github.com/apache/airflow/issues/20309#issuecomment-1288320601) what actually cause SIGSEGV error in your case. > One thing you can try. Can you set the PYTHONFAULTHANDLER variable before running airlfow ? > > ``` > export PYTHONFAULTHANDLER="true" > ``` > > Setting this variable before running your airlfow might provide more information on what caused the problem - it will not make it possible to handle it better, but at least might save you the guesswork. Or you could try to run [Airflow on macOs in docker](https://airflow.apache.org/docs/apache-airflow/stable/howto/docker-compose/index.html#running-airflow-in-docker) in this case this kind of of error should disappear. Be aware that if you choose this path you need to have some knowledge about docker I can add some just simple stuff which might help: 1. M1 it is ARM64 architecture (aka armv8 aka AArch64) but ARM support in Airflow is Experimental (some of the packages not built for this architecture) 2. If you build docker image on mac with M1/M2 by default it build for `linux/arm64` architecture. As I mention previously not everything might work on ARM in this case you could also build and run image for `linux/amd64` architecture by adding flag `--platform linux/amd64` unfortunately it will greatly affect performance -- 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]
