Skip to content

Fix MCP SSE fixture readiness before v0.7 release - #4

Merged
simpcl merged 1 commit into
mainfrom
dev
Oct 13, 2026
Merged

simpcl merged 1 commit into
mainfrom
dev

Conversation

@simpcl

@simpcl simpcl commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

The main release gate exposed an intermittent MCP reconnect timeout: the SSE fixture flushed HTTP headers before registering its response channel, allowing an immediate initialize POST to lose its response. Failed-test cleanup could also race WaitGroup.Wait against a newly starting handler's Add.

Register the fixture response channel before announcing readiness and let httptest.Server.Close wait for handlers after cancellation. Apply the same ordering to the progress fixture. Production MCP code is unchanged.

Validation: MCP SSE/session tests pass with go test -race ./pkg/mcp/service -run 'TestManager(SSE|GatewaySession|ListGatewaySessions)' -count=100. Full release gates and Linux CI run before v0.7.0 tagging.

Clean candidate cfc7f16c6805897560752ef5df519d895aeff9ed also passes make verify-release, make smoke-release, the immutable independent consumer gate and the paired independent consumer gate (Go 1.26.3). Tagging still waits for PR and main Linux CI.

@simpcl
simpcl merged commit 3d04b7a into main Oct 13, 2026
1 check passed
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.

1 participant