feat(e2e): add rate-limit retry for backend API calls#8081
feat(e2e): add rate-limit retry for backend API calls#8081jacekradko wants to merge 6 commits intomainfrom
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds a new rate-limited retry module 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Comment |
Summary
withRateLimitRetry) around theClerkClientused in integration test setup/teardownRetry-Afterheaders (capped at 30s), max 5 retriescreateClerkClientcall site intestUtils/index.ts— zero changes to individual service files or testsMotivation
Multiple concurrent CI runs share the same Clerk development instances, causing 429 rate limit errors that fail integration tests several times a day. Instead of failing, tests will now automatically retry with backoff, logging
[Rate Limit] Retry 1/5 for users.createUser, waiting 1234msfor CI observability.Test plan
pnpm buildpasses[Rate Limit] Retrymessages to confirm the wrapper activates on real 429sSummary by CodeRabbit