gerlowskija commented on PR #4189: URL: https://github.com/apache/solr/pull/4189#issuecomment-4012617281
> Are there any tooling type things that could help us identify these situations ahead of time? Not that I'm aware of? There are linters, IDE integrations, etc. that try to detect trouble spots, but those usually rely really heavily on `@NotThreadSafe` and similar annotations that we're not very good about putting in place. I imagine agents / LLMs could do some of this, but I don't think you could point them at the Solr codebase broadly and say "find me race conditions to fix". You'd need more specifics for them to go off of...at which point you're not really "in advance" anymore because you'd need to have a specific issue in mind. -- 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]
