caldempsey commented on PR #152: URL: https://github.com/apache/spark-connect-go/pull/152#issuecomment-3067101270
@grundprinzip Hey! I worked out the panic. It looks like the error I mentioned before only occurs when running the Databricks ODBC driver adjacent to it. There has to be some kind of signal handling collision between Spark Connect and that instance. Removing the Databricks ODBC driver instance from my main thread (a pretty big testing app) resolved the issue. ``` signal 13 received but handler not on signal stack mp.gsignal stack [0xc000584000 0xc00058c000], mp.g0 stack [0x7fffb07f9280 0x7fffb0ff8e80], sp=0xc000815e20 fatal error: non-Go code set up signal handler without SA_ONSTACK flag ``` The introduction of context cancellation to Spark Connect only came in at about v40, and I was running v34 before, which means I think it might be worth testing the combination of cancelled context in Spark Connect on v40 with ODBC running adjacent. A pretty rare edge case, I know, but you seem to work at Databricks and might want to shout at the guys at Sigma to make sure they are handling [Signal](https://go.dev/pkg/os/signal/?m=old) gracefully. Tagging @alexott onto this one. I think we can unblock this PR right now. I'll see if I can get a core dump to prove out the issue being related to Sigma Spark ODBC, but the problem cannot be reproduced without it, and the PR otherwise seems feature complete. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
