Repository navigation
fix: restore page loading and remove completed history importer - #169
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The new concurrent token reads exposed Postgres.js query pipelining incompatibility with Supabase transaction pooling, leaving dynamic pages waiting until Vercel returned a 504. Use the Supabase session endpoint in the shared database client, keeping one connection per instance and the existing idle timeout. Share the token read across views within each render.
Validated with 289 passing tests, lint, both Knip passes, typecheck, and a production build. Reproduced the hang against the production transaction pooler using read-only queries; the session endpoint completed all queries, including 12 mixed reads/transactions. Locally rendered /, /work, and /tokens against production data with empty caches; subsequent requests completed in 70–190 ms.
Remove the completed one-time history import script and return db:migrate to Drizzle only. Fresh databases initialize GitHub history on their first normal publication. No schema changes or data migration. Session pooling reserves one backend connection per active instance, released after the existing 20-second idle timeout.