test(e2e): Migrate Express 5 and MCP to span streaming - #24157
Conversation
size-limit report 📦
|
Co-Authored-By: GPT-6 <codex@openai.com>
551379e to
ab67b74
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ab67b74. Configure here.
| const initializeSegmentPromise = waitForStreamedSpan( | ||
| 'node-express-v5', | ||
| segment => segment.is_segment && segment.name === 'initialize', | ||
| ); |
There was a problem hiding this comment.
SSE MCP streamed spans will time out
High Severity
The Express 5 MCP suite now waits for streamed handler segments over SSE. The sibling streaming app still skips that path because those MCP spans never arrive in the envelope, so this wait times out instead of recording initialize or later tool, resource, and prompt segments.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit ab67b74. Configure here.
There was a problem hiding this comment.
hmm, they reliably pass both locally and on CI, so i think this is a false positive


Exercise Express 5 and MCP v2 instrumentation with span streaming, including low-cardinality span names and database query attributes.
part of #23800