feat(queue): durable local close queue with rate-limit retry (RUSH-2308) - #35
Merged
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Contributor
Author
|
Non-author review (recorded as comment — formal approve blocked since the codex agent opened this under my GH identity, but I did NOT author the code). VERDICT: PASS. Independently validated: ran 95 tests OK incl. durable-queue coverage; HTTP-status transient detection (429/502/503/504); idempotent backoff drain; bounded per-issue queue; API key never persisted. Merged on green. |
muqsitnawaz
added a commit
that referenced
this pull request
Aug 9, 2026
PR #35 shipped the core rate-limit queue under RUSH-2308. This closes the remaining RUSH-2307 acceptance gaps: - fcntl.flock serializes concurrent drains on one machine - linear queue list (explicit) + drain --once - gql surfaces Retry-After; drain prefers it over exponential backoff - rate-limit runbook in skill.md / README - tests: lock, once, Retry-After, list (100 total green) - install pin + SHA for v0.18.0
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
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.
Linear close operations now survive rate limits and transient API failures via a durable local queue.
What changed
linear update <id> --done --proof ...persists a close intent to~/.linear-cli/queue/before calling Linear. On a 429/transient error the intent is retained and retried later instead of being dropped.linear queueandlinear queue drain(--dry-run) to inspect and apply queued closes.gqlnow surfaces HTTP status codes in GraphQL error extensions so callers can detect 429 vs permanent failures.Links
Verification
python3 -m unittest -v→ 95 tests pass (full output)