chore(diag): expose hasDatabaseUrl + instanceId in _proxy_debug#318
Merged
Conversation
The Phase 3 rate limit is partially working in production — 12 streaming requests resulted in 7 DB inserts but no 429s. Theory: some Vercel function instances cold-start without DATABASE_URL populated and silently fail-open for their lifetime. This commit adds three fields to the /api/_proxy_debug response so we can confirm: - hasDatabaseUrl: whether the env var is visible at runtime - rateLimitConfigured: whether the proxy was wired with the hook - instanceId: a per-instance random id, so multiple curls can show whether they hit the same instance or different ones Once verified, this commit can stay (cheap) or be reverted as preferred — the cost is 4 lines in the debug response. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Phase 3 rate-limit is partially working in production. 12 streaming requests inserted 7 rows but never returned 429. The most likely cause is some Vercel function instances cold-start without `DATABASE_URL` populated and silently fail-open for their lifetime.
This PR adds three diagnostic fields to `/api/_proxy_debug`:
By hitting `/api/_proxy_debug` repeatedly, we can confirm whether multiple instances are running and whether DATABASE_URL is consistently set on all of them.
Stays in production after diagnosis (cheap, 4 lines).
Test plan