Uh oh!
There was an error while loading. Please reload this page.
Show pending runs as gray animated stripes in trace viewer - #2520
Conversation
Pending was incorrectly using the blue running indicator; it now has its own segment status and gray stripe styling. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
🦋 Changeset detectedLatest commit: b3e068f The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Uh oh!
There was an error while loading. Please reload this page.
No backport to All non-changeset changes are confined to To override, re-run the Backport to stable workflow manually via |
…testing * origin/main: perf(core): decouple workflow VM seed/clock from startedAt (#2525) [world-local] [core] Cache local dev server port per process (#2522) Show pending runs as gray animated stripes in trace viewer (#2520) [world-vercel] Route v4 event requests through global fetch (#2514) [core] Send workflowName with step events (#2511) Stamp run IDs on world spans (#2508) Reject empty-string hook tokens in createHook() (#2490) perf(core): cache compiled workflow-bundle vm.Script across replays (#2471) perf(core): drain consumable replay events synchronously (#2473) perf(core): lazy inline step start (save one world round-trip per step) (#2478)
Summary
pendingsegment status for workflow runs in the new trace viewerTest plan
pnpm vitest run packages/web-shared/src/components/new-trace-viewer/utils.test.tsWORKFLOW_LOCAL_QUEUE_CONCURRENCY=1Made with Cursor