- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 874
 
fix: release concurrency token exhaustion no longer happens on batchTriggerAndWait #1937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
          
WalkthroughThe changes update the concurrency release logic in the  Changes
 Sequence Diagram(s)sequenceDiagram
    participant ParentTask as batchTriggerAndWaitReleaseConcurrency
    participant ChildTask as batchTriggerAndWaitChildTask
    loop 3 times
        ParentTask->>ChildTask: Trigger with waitSeconds=1
        ChildTask-->>ParentTask: Complete after 1s
    end
    ParentTask-->>ParentTask: Finish after all children complete
    Possibly related PRs
 Poem
 Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
 🚧 Files skipped from review as they are similar to previous changes (2)
 ⏰ Context from checks skipped due to timeout of 90000ms (7)
 🪧 TipsChatThere are 3 ways to chat with CodeRabbit: 
 Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
 Other keywords and placeholders
 CodeRabbit Configuration File (
 | 
    
          
 | 
    
Summary by CodeRabbit