fix: recover DB pool after Railway disconnects - #93
Merged
Conversation
Warm serverless isolates kept a rejected ensureSchema promise after Railway dropped Postgres, so every request resurfaced the same digest even after the database came back. Clear the sticky promise, recreate the pool, and retry once on transient disconnects. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
14 tasks
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
ERROR 2206690639was a Next.js digest forConnection terminated unexpectedlyafter the Railway Postgres outage.ensureSchemapromise, so every request failed even after the DB was healthy again.Test plan
www.agentnote.dev)2206690639after merge deployMade with Cursor