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 99b4119
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): a redeemed reset continues only threads whose limit it refilled
Review of the first commit found that a redemption continued every
waiting thread of the account, whatever limit the credit refilled, and
that a client could set the mark itself.
- Redemption moves from the ws.ts handler into a ResetCredits service.
It reads the account's limits after the redemption and leaves alone
threads due at or after the reset of a limit that is still used up.
An unconfirmed redemption continues nothing. A retry answered with
alreadyRedeemed counts as the reset. A caller that disconnects once
the credit is spent no longer interrupts the follow-up.
- The mark is set by a server-only command, thread.limit-recovery.reset,
so it is off the client's metadata update.
- Each redemption uses its own command id, so a recovery refused once
can be marked by a later redemption. A pending approval or question
no longer refuses the mark.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
0 commit comments