gitmodimo commented on issue #47248: URL: https://github.com/apache/arrow/issues/47248#issuecomment-3144423153
I dug a little deeper. It turns out that 1. case was not actual error. I was me not completing the `PushGenerator` that caused deadlock. However the second case still stands. My dirty fix does solve use-after-free issue but causes new `Check failed: !IsFutureFinished(state_) Future already marked finished` in AsyncTaskSchedulerImpl due to error returned from StopProducing that coused another abort while aborting. I am not sure whether we can remove the check. Right now I am leaning towards total removal of return value in StopProducing, but there are probably more implications since downstream nodes also can stop upstream ones. LMK what path to follow. -- 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]
