Flaky e2e test: API key rate limiting #74

Open
opened 2026-10-26 10:46:07 -04:00 by vmanne-poc · 0 comments
Owner

Follow-up to #29 (Phase 13.1, v0.15.1).

#29 requires per-key rate limiting. The e2e test covering it is flaky (timing/shared limiter state between tests).

Plan

  • Make the test deterministic: isolate limiter state per test/key and avoid wall-clock dependence.

Done when

  • The rate-limit e2e test passes reliably across repeated runs.
Follow-up to #29 (Phase 13.1, v0.15.1). #29 requires per-key rate limiting. The e2e test covering it is flaky (timing/shared limiter state between tests). **Plan** - Make the test deterministic: isolate limiter state per test/key and avoid wall-clock dependence. **Done when** - The rate-limit e2e test passes reliably across repeated runs.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
vmanne-poc/Postak#74
No description provided.