fix(auth): resolve Vercel 504 timeout by optimizing middleware queries#99
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
This PR resolves the
MIDDLEWARE_INVOCATION_TIMEOUT(504 Gateway Timeout) on Vercel production by optimizing the auth middleware logic.🔍 RCA
The middleware was performing up to 3 sequential Supabase network calls per protected request. Given the cross-region latency between Vercel Edge and the Supabase DB (Brazil), this often exceeded the Edge Runtime execution limit.
⚡ Fix
Consolidated the employee existence check and role fetching into a single query.
select('id')query.Type of Change
perf— Performance improvementfix— Bug fixRelated Documents
docs/process/sentinel-log.mdChecklist
npm run typecheck— zero errorsnpm run lint— zero errorsnpm run format:check— no formatting issuesnpm test src/lib/auth.test.ts— all tests pass