Conversation
amotl
changed the title
QueryStatement Bind: received unexpected message type *pgproto3.CommandComplete
amotl
changed the title
QueryStatement Bind: received unexpected message type *pgproto3.CommandComplete
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
2 participants
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.
About
Trying to catch another signal where updating to pgx v5.9 goes south when integration testing on GHA, while the same test succeeds on both Jenkins (Linux) and my workstation (macOS).
-- CI run #23465313608
Details
The same signal was first caught on the cratedb-examples repository, and we also observed integration tests on cratedb-prometheus-adapter go south, displaying a different discrepancy. All the details have been recorded in the tracking ticket CRATEDB-CLIENTS-306.
References