raulcd commented on issue #49061: URL: https://github.com/apache/arrow/issues/49061#issuecomment-3819683334
Hi! I am not an expert on this area but as you have pinged me this is what I think, again as a non-expert so take this with a grain of salt as I might be wrong on the assessment. This reads like it was generated by an LLM that grep'd for "deadlock" in the codebase and wrapped the results in a proposal template. Part of the proposal like: > Implement compile-time detection of nested parallelism patterns and potential deadlock scenarios are not clear actionable items and is not clear to me what are the real steps to be taken. Part of this looks like implementing TSAN on Arrow which we already run on our jobs. The actual deadlock bugs referenced (like #41862) are specific issues that need specific fixes, a framework seems over-engineering and would heavily penalize performance. Without a specific proposal (code with benchmarks) I don't think the proposed plan is achievable. -- 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]
