You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by "pitrou (via GitHub)" <gi...@apache.org> on 2026/06/01 09:29:24 UTC

Re: [PR] GH-47642: [C++] Catch exceptions from initial_task in AsyncTaskSchedu… [arrow]

pitrou commented on PR #49860:
URL: https://github.com/apache/arrow/pull/49860#issuecomment-4591278241

   > The failure mode is asymmetric with the rest of Arrow: everywhere else a buggy user callable surfaces as a `Status`, but here it silently hangs forever in release builds (`running_tasks_` stays at 1, the plan's `finished` future never completes). The `ThreadPool` comparison doesn't quite apply either — a throwing task there calls `std::terminate`, so the user gets a stack trace. Here they get silence.
   
   Hmm, that's a good point.


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org