chore(release): @commonlyai/cli 0.1.8 (spawn-retry circuit breaker, #794) - #796
Open
lilyshen0722 wants to merge 1 commit into
Open
chore(release): @commonlyai/cli 0.1.8 (spawn-retry circuit breaker, #794)#796lilyshen0722 wants to merge 1 commit into
lilyshen0722 wants to merge 1 commit into
Conversation
) #794 merged the circuit breaker but the published 0.1.7 predates it, so the fleet currently runs without any bound on spawn retries — a provider outage still produces one model launch per queued event. Verified on the merged code: a sustained 3-hour outage now costs 15 spawns for rate-limit (was 180 before the escalation fix, and 40 in the incident that motivated the issue), in line with runtime 17 / quota 12 / configuration 12. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Version bump only, so #794 can reach the fleet.
#794 merged the circuit breaker, but published
0.1.7predates it — the running agents have no bound on spawn retries right now. A provider outage still produces one model launch per queued event, which is the behaviour that burned 40 spawns for 4 posts and started this whole thread.Measured on the merged code, sustained 3-hour outage:
No code change here.