fix(api): avoid worker-hanging db reuse#25
Merged
Conversation
This was referenced May 20, 2026
risu729
added a commit
that referenced
this pull request
May 20, 2026
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
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
Why
Live tail logs still showed 1101 cancellations on
/api/realtime, and live curls showed the same cancellation on DB-backed public routes like/api/pois. Cloudflare's runtime can cancel requests when a Promise is tied to global or stale request-context I/O and can never settle. The previous DB singleton kept the Postgres client in module scope across Worker requests; realtime auth also hit that DB path before upgrading the socket.Verification
bun run checkGET /api/poisreturns Cloudflare 1101 on current deployment