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 3dc14a4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(oauth): guard revocation records against in-flight reconnects
- Record a revocation only when the row's updated_at has not moved since
the leader read it, so a reconnect that keeps the same refresh token
while a rejected refresh is in flight is not undone.
- Reread the row under the refresh lock, so a revocation another process
just recorded is honored instead of calling the provider again.
- A re-probe whose transient failure meets a moved chain reports no
revocation.
- Slack fan-out clears the record only for a chain the provider just
issued, not when re-spreading a stored one.
- A reconnect whose cleanup fails now fails the callback.
- Revocation rejections log at WARN in oauth.ts too; the pure refresh
error classifiers move to refresh-error-codes.ts so that client-reachable
module can use them.
- The connector path leaves the revocation log to executeSync.
0 commit comments