Repository navigation
Conversation
No source changes. The isolated browser check failed before running tests because the GitHub-hosted runner could not download libvpx7 and libx264-163 from the Ubuntu mirrors (apt exit 100).
Contributor
Author
|
CI rerun note for reviewers: the previous I do not have permission to rerun the upstream workflow directly, so I pushed an empty-tree commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements #407, the conversation-wide Agent Trace view requested by @FayeSpica in the approved review of #374:
A single Trace page now groups all executed turns for the selected conversation, with per-turn expansion and lazy-loaded native/model logs and the linked generation Jobs introduced in #374.
Changes
GET .../assistant/conversations/{id}/tracereturns turns in conversation order, including a bounded user-text preview, runtime, model and status. It resolves active and archived conversations and existingreusedCreateIdsaliases without activating a conversation, taking an edit lease or loading JSONL bodies.GET .../assistant/traces/{turn}/conversationlocates the conversation associated with an old single-turn link. If no conversation is found, the previous single-turn view remains available.uuid5(user_id, 'assistant'), rather than assuming messages always alternate. Queued/unexecuted messages and orphan replies are not presented as executed turns.The existing
TraceEntries,TraceRow,TraceJobs, normalizers and #374 job-lineage endpoint remain unchanged.Screenshots
The screenshots use DEMO data from a local provider double, not live model execution.
Narrow viewport checks: EN · 中文
Verification
Reported against fork HEAD
2de2acc0:lint-imports;tsc --noEmit;check:i18n(3,244 keys, 0 issues);git diff --check.npm test(upstream GitHub Actions, verified from raw job logs): 932/932 passed, 0 failed on PR head2de2acc0(PR frontend job). The same command (node --test tests/*.test.ts) passed 929/929, 0 failed on upstream baseab3f0585(base frontend job). These match the three added frontend tests. A separate earlier local run reported 930/932, but its failing test names/stack traces were not supplied; the failures are not reproduced in GitHub CI and have not been established as pre-existing baseline failures. No code change is warranted on that evidence alone.Scope and compatibility
The change is limited to the read-only conversation Trace experience. It does not modify generation, editing leases, accepted Job execution, recovery, or the execution behavior being developed in #375 (edit/resend), #379 / #381 (queued messages), and #402 / #403 (in-turn insertion). The open PR data shapes were not individually exercised in this branch.
Fixes #407
Refs #374, #372, #261.