You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cd54396
Browse filesBrowse the repository at this point in the historyBrowse files
fix(execution): finish the removal sweep's edge cases
- The removal stop handler loads both job queues independently and sweeps
whichever loaded, so a primary queue that fails to load no longer skips the
database queue's sweep. The failure is still rethrown for the outbox to retry.
- A claimed resume is found under a parent log row in the legacy `paused`
status too, one of the statuses a resume claims from.
- The database queue re-checks for a matching active job after a short batch,
since a selected job that finished before the update reached it shrinks the
batch while later jobs still match.
- The ban's completion log no longer reports its runs stopped when recording
their stops failed.
`[${requestId}] Disabled resources for user ${userId}: archived ${ownedWorkspaces.length} workspaces, deleted API keys, stopped their runs`
380
+
`[${requestId}] Disabled resources for user ${userId}: archived ${ownedWorkspaces.length} workspaces, deleted API keys, ${stopFailed ? 'failed to stop some of their runs' : 'stopped their runs'}`
0 commit comments