emit per-call jsRpcCall spans and propagate stub origin for trace continuity - #7006
Conversation
|
APIError: Invalid Anthropic API Key |
2 similar comments
|
APIError: Invalid Anthropic API Key |
|
APIError: Invalid Anthropic API Key |
|
@apeacock1991 Bonk workflow failed. Check the logs for details. View workflow run · To retry, trigger Bonk again. |
Merging this PR will degrade performance by 1.97%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ | JsString_Utf8Length_Utf16_Invalid_NonFlat_256 |
9.4 µs | 10.7 µs | -12.74% |
| ⚡ | bm_Promise_Fib10 |
20.3 µs | 18.5 µs | +10.12% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing apeacock/jsrpcTracing-gitlab (fca229f) with main (c15dd17)
Footnotes
-
129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
|
APIError: Invalid Anthropic API Key |
5 similar comments
|
APIError: Invalid Anthropic API Key |
|
APIError: Invalid Anthropic API Key |
|
APIError: Invalid Anthropic API Key |
|
APIError: Invalid Anthropic API Key |
|
APIError: Invalid Anthropic API Key |
JSRPC promises and returned stubs retained span parents directly on JavaScript heap objects. Process sandbox span observers own Cap’n Proto clients tied to the request I/O context, causing a use-after-free when the objects are collected after request teardown. Store retained span parents through IoOwn so they are destroyed with their owning context.
Imported from #6750. Dupe of #6966 but named correctly (branch matching internal).
Summary
Add per-call tracing for JavaScript RPC.
Changes
Testing
Screenshots