feat: add priority pools to prevent high-priority task starvation (#702) #704
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows high-priority tasks to execute immediately even when all default threads are busy with lower-priority work. Includes capacity-aware fallback routing and comprehensive test coverage.
🤖 Generated with Claude Code
Brief, plain english overview of your changes here
As described in #702 we had a need for "fast lane" pools for high priority tasks, so I spent the weekend working with Claude and ended up with a solution that uses multiple executors with separate thread pools. Open for feedback and alternative solutions!
Also, I added guidelines for Claude and also Jetbrains Junie.
Fixes
#702
Reminders
mvn spotless:applycc @kagkarlsson