paleolimbot commented on PR #14250: URL: https://github.com/apache/arrow/pull/14250#issuecomment-1297119973
Ok, I checked this again, and the errors that I get are: ``` /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/status.cc:134: Invalid: Signal stop source was not set up /Users/dewey/Desktop/rscratch/arrow/cpp/src/arrow/status.cc:134: Invalid: Signal stop source was not set up ``` In the code in the R package, I'm careful not error (but instead warn) on the result of `RegisterCancellingSignalHandler()`, and so I wonder if this is coming from C++ instead? I would still prefer to not mess with signal handling in the R package since I have a limited ability to debug this myself. I'm aware that I have a poor understanding of the constraints here, but the R package could probably provide a thread-safe callable like `bool (*should_we_stop)(void)` and avoid imposing the constraints of R on this section of Arrow C++. -- 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]
