test(e2e): Port the TanStack Start React E2E app to span streaming - #24172
test(e2e): Port the TanStack Start React E2E app to span streaming#24172RulaKhaled wants to merge 2 commits into
Conversation
Co-Authored-By: Cursor Grok 4.6 <cursoragent@cursor.com>
size-limit report 📦
|
…st leak Co-Authored-By: Cursor Grok 4.6 <cursoragent@cursor.com>
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.
Reviewed by Cursor Bugbot for commit 9979f3f. Configure here.
| // at startup and never emit this span. | ||
| if (tunnelRouteMode === 'custom') { | ||
| await waitForServerHttpSpan(pathnameMatchesTunnelRoute); | ||
| } |
There was a problem hiding this comment.
Flaky leftover tunnel span wait
Medium Severity
The custom-route leftover wait starts after the previous test already posted to the tunnel, but waitForStreamedSpan only sees envelopes that arrive after that call. The first leaked span is often already buffered, so this wait can hang until timeout. Flagged because the review rules call out waiting for telemetry after the action that produced it.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 9979f3f. Configure here.


Makes span streaming the only path in the TanStack Start React E2E app. The
E2E_TEST_STREAMED_SPANSternary is gone, and the specs wait on streamed spans instead of transaction envelopes.Why
Unparameterized
http.servernames fall back to the method only, so those waits matchurl.path(andhttp.routeonce a route is known). Redis handshake commands and mysql query-summary names (SELECT) are told apart withdb.query.text. Thetunnel-streamedvariant is dropped because it is now identical totunnel-generated. Static-lifecycle coverage moves totanstackstart-react-static.Part of #23805