Live-backend hardening: Supabase retry, test isolation, laptop launcher - #3
Merged
Merged
Conversation
…s from developer .env - supabase_client._request now retries connect-phase errors (request never sent, so safe for non-idempotent calls); observed intermittent httpx.ConnectTimeout surfacing as 500s during live testing. - conftest pins SUPABASE_JWT_SECRET="" so a real secret in a developer's .env can't break the mocked-auth tests. - scripts/start-live-backend.ps1: one-command launcher for laptop hosting (uvicorn in production mode + ngrok tunnel on a static domain). Co-Authored-By: Claude Fable 5 <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.
🤖 Generated with Claude Code