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
refactor(rate-limit): scope the per-IP bucket by resource id, not by bucket name
The chat call interpolated the deployment id into `bucketName`, which produces
a correct key but puts a per-deployment value into the field both log lines
emit as `bucket` — high cardinality on a label meant to name a bucket family,
and asymmetric with the `enforceResourceRateLimit` call beside it that takes
the id as its own argument.
`enforceIpRateLimitWithIndependentBackstop` now takes an optional `resourceId`,
so the pair reads the same way and `resourceId` is logged as its own field.
The unscoped key shape is unchanged for the existing callers, with a test
pinning both shapes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QWh9WFMYNZ6uTFQFUzF8Bj
0 commit comments