Skip to content

make sure streaming query handle invalid sequence error#4307

Merged
jgao54 merged 1 commit into
mainfrom
mysql-streaming-error
May 14, 2026
Merged

make sure streaming query handle invalid sequence error#4307
jgao54 merged 1 commit into
mainfrom
mysql-streaming-error

Conversation

@jgao54

@jgao54 jgao54 commented May 14, 2026

Copy link
Copy Markdown
Contributor

Invalid sequence error is a known issue in the go-mysql-org client that needs to be classified. Previously fixed for cdc (#4197) but missing for snapshot during ExecuteSelectStreaming.

Fixes: DBI-743

@jgao54 jgao54 requested a review from a team as a code owner May 14, 2026 11:21
@claude

claude Bot commented May 14, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@codecov

codecov Bot commented May 14, 2026

Copy link
Copy Markdown

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
2212 2 2210 189
View the top 2 failed test(s) by shortest run time
github.com/PeerDB-io/peerdb/flow/e2e::TestApiPg
Stack Traces | 0.01s run time
=== RUN   TestApiPg
=== PAUSE TestApiPg
=== CONT  TestApiPg
--- FAIL: TestApiPg (0.01s)
github.com/PeerDB-io/peerdb/flow/e2e::TestApiPg/TestResyncCompleted
Stack Traces | 0.12s run time
=== RUN   TestApiPg/TestResyncCompleted
=== PAUSE TestApiPg/TestResyncCompleted
=== CONT  TestApiPg/TestResyncCompleted
2026/05/14 11:33:15 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/05/14 11:33:15 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/05/14 11:33:15 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mychcl_glwcpegl.test_bit
2026/05/14 11:33:15 INFO fetched schema x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN} table=e2e_test_mychcl_e6ktn7rz.test_blobs
    api_test.go:1302: 
        	Error Trace:	.../flow/e2e/api_test.go:1302
        	Error:      	Received unexpected error:
        	            	failed to get workflow_id for flow resync_completed_api_air4qkqt: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
        	Test:       	TestApiPg/TestResyncCompleted
    api_test.go:49: begin tearing down postgres schema api_air4qkqt
--- FAIL: TestApiPg/TestResyncCompleted (0.12s)

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Flaky Test Detected

Analysis: TestApiPg/TestResyncCompleted failed because a Postgres connection was forcibly terminated mid-query (SQLSTATE 57P01 admin_shutdown) — an infrastructure/connection issue unrelated to the PR's mysql-streaming-error scope, characteristic of a flaky failure rather than a real bug.
Confidence: 0.9

✅ Automatically retrying the workflow

View workflow run

@jgao54 jgao54 force-pushed the mysql-streaming-error branch from b13296a to b318c33 Compare May 14, 2026 17:44
@jgao54 jgao54 requested review from Jeremyyang920 and pfcoperez May 14, 2026 17:44
@jgao54 jgao54 merged commit e441f6a into main May 14, 2026
15 checks passed
@jgao54 jgao54 deleted the mysql-streaming-error branch May 14, 2026 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants