Repository navigation
fix(mothership): close the scheduled-job review gaps - #9345
Conversation
- dispatch one attempt at a time per occurrence, so a skip or block never closes a live run's record - brief each occurrence with the run number fixed at its claim, not the job's moving count - report an automatic turn-off only when this failure turned the job off, not one a person already turned off - mark a deadline stop after it is delivered, so a crash before then delivers it again - state the run's spend cap only where hosted billing enforces it - recover an invalid index left by an interrupted build in the job migration, as 0435 does - give PlanUsageLimitDisplay a props interface
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
All reported issues were addressed across 9 files
Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.
Turn on auto-fix | Re-trigger cubic
[Medium impact] The PR appears safe to merge; no new blocking issue was found. SummaryThis PR closes scheduled-job review gaps:
The latest changes separate a requested deadline Stop from completed delivery. They retry unfinished delivery before finalizing, addressing the previous unnumbered finding. No new actionable issues were found.
|
…nd redeliver one an earlier pass did not finish
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 9 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.
Turn on auto-fix | Re-trigger cubic
Summary
Fixes the review findings on the v0.9.33 release PR (#9339) that hold up, all in the scheduled-jobs lane from #9331. Findings that are not defects are answered on their threads.
IF NOT EXISTS. 0437 has not reachedmain.PlanUsageLimitDisplaygets a props interface.Type of Change
Testing
lane.integration.tsagainst real Postgres and Redis, provisioned through the versioned migrations (INTEGRATION_DB_PROVISION=migrate bun run test:integration lane.integration): 18 pass. The three new tests (manual turn-off sends no auto-disable email, a retried occurrence keeps its run number, a held dispatch lock leaves the occurrence alone) fail on the pre-fix code; the streak test now also asserts the email is sent exactly once.tsc --noEmitis clean,check:migrationspasses.Checklist