Repository navigation
fix: md/raw switch alignment, and effect 4.0.4 span changes breaking CI - #1450
Conversation
ViewSwitch defaults to self-center, which is right in one-line header rows but floats it halfway down a tall items-start body, away from the copy button beside it.
Maple review🟢 Confidence 10/10 · safe to merge Passes
What was checked
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
effect 4.0.2+ names HTTP spans by method alone ("GET", not "http.server GET")
and fails a 5xx server span itself with HttpServerError(ResponseError). The
SDK only stamped its HttpServerErrorResponse marker on a successful exit, so
rendered 5xx responses would land in error tracking as a generic
HttpServerError. It now treats effect's response failure the same way.
Tests that found server and client spans by name now match on span kind
(and http.request.method for client spans, since database spans are clients
too), which also keeps the warehouse "no http.client span" check from
passing vacuously.
Maple review🟢 Confidence 8/10 · likely safe to merge Two unrelated threads:
What was checked
|
What
1. MD/RAW switch alignment. The switch on the agent session System prompt card (and the span expansion's system message panel) now sits at the top of the body, next to the copy button.
ViewSwitchdefaults toself-center, which is right in one-line header rows but put it halfway down a tallitems-startbody.2. effect 4.0.4 span changes (main CI has been red since #1449). Effect 4.0.2+ changed two things about HTTP spans:
GET, nothttp.server GET/http.client GET).HttpServerError(ResponseError).The second one changes production behavior. The SDK tracer only added its
HttpServerErrorResponseexception marker when the span's exit succeeded, so after the bump, 5xx responses rendered by the Worker bridge would show up in error tracking as a genericHttpServerErrorinstead of the marker thatUNEXPECTED_IDENTITY_MARKERShandles.flushable-tracer.tsnow treats effect's response failure the same as a 5xx rendered on a successful exit. It checks the failure's shape rather than importing effect's error class, so the SDK still works with any effect in its^4.0.0peer range. A changeset bumps@maple-dev/effect-sdk(patch).The span name change needs no production fix:
normalizedSpanNameExprand the rollup SQL already handle bareGET/POSTnames.Tests that found spans by name now match on span kind instead (plus
http.request.methodfor client spans, since the warehouse's database span is a client span too). This also fixes the warehouse "no http.client span" check, which would otherwise have passed vacuously after the rename.Verified locally
worker-bridge, apiworker-bridge, aiworker/http, backendWarehouseQueryService, infraisolate-age, effect-sdkflushable-tracerall pass.tscis clean in the five packages touched.🤖 Generated with Claude Code
Summary by CodeRabbit