diag(minting): include err.cause + PG fields in webhook 500#522
Merged
Conversation
TEMP smoke diagnostic — extends prior patch to include err.cause (postgres-js wraps the driver error under "Failed query:") plus PG fields (code, severity, detail, etc.) so we can see the actual cause of the processed_events insert failure. Revert after smoke. 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
err.causeand surface postgres-js PG fields (code, severity, detail, hint, etc.)"Failed query: insert into processed_events ..."— the underlying driver error is hidden undererr.causeWhy
End-to-end smoke is currently 500ing on the first DB write. Local query against the same
processed_eventstable succeeds and schema is correct, so the cause is likely a connection-level error (SSL, auth, or pooler) only visible in the wrapped cause.Test plan
🤖 Generated with Claude Code