⚡ Bolt: Concurrent Telegram broadcasts in workflows#477
Conversation
In `maintenance.py` and `reflection.py`, Telegram messages to allowed users were previously sent sequentially in a loop. This commit replaces the loop with `asyncio.gather(*coros, return_exceptions=True)` to execute the requests concurrently, eliminating an N+1 network latency bottleneck. Error handling behavior is preserved via `return_exceptions=True` and the outer try/except block. Co-authored-by: miclaldogan <232061685+miclaldogan@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Refactored sequential Telegram notification API calls to execute concurrently using
asyncio.gather.🎯 Why: In
maintenance.pyandreflection.py, sending Telegram summary messages to multiple allowed users was previously done sequentially in aforloop, creating an N+1 network latency bottleneck.📊 Impact: Significantly speeds up the workflow termination phase when multiple Telegram users are configured. Reduces total API notification time from O(N) to roughly O(1) by parallelizing the requests.
🔬 Measurement: Verify that notifications still send properly after a workflow concludes, and observe that total notification time is bounded by the slowest single request rather than the sum of all requests.
PR created automatically by Jules for task 14669125375984968968 started by @miclaldogan