fix(dashboard): compact run labels#1337
Merged
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
7e89f2e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ba182b95.agentv.pages.dev |
| Branch Preview URL: | https://fix-av-a15-compact-run-label.agentv.pages.dev |
cc2a886 to
7e89f2e
Compare
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
benchmark.jsonmetadata.display_namein the run list so remote and local rows use the same friendly-name convention when the artifact provides one.titletext.Root Cause
Remote run metadata can surface timestamp-only
display_name/ run IDs such as2026-03-27T05-00-00-000Z. The old formatter trusted that as the primary run name and then appended the formatted timestamp again, producing crowded labels like the reported remote screenshot while local runs with human display names looked fine.The remote git-listing path also forced
display_nameto the run directory basename, so a remote artifact withmetadata.display_namecould still lose its friendly label before the Dashboard formatter saw it.Reported evidence:
Validation
bun test packages/core/test/evaluation/results-repo.test.ts(11 pass)bun test apps/dashboard/src/lib/run-label.test.ts apps/dashboard/src/components/RunList.mobile.spec.tsx(12 pass)bunx biome check packages/core/src/evaluation/results-repo.ts packages/core/test/evaluation/results-repo.test.ts apps/dashboard/src/lib/run-label.ts apps/dashboard/src/lib/run-label.test.ts apps/dashboard/src/components/RunList.tsx apps/dashboard/src/components/RunList.mobile.spec.tsx apps/dashboard/src/components/Sidebar.tsxbun --filter @agentv/core buildbun --filter @agentv/dashboard buildbun --filter agentv buildAGENTV_HOME/AGENTV_DATA_DIRand a throwaway local+remote fixture. API had a localdisplay_name: local fixture runand a remotemetadata.display_name: remote fixture rununder a timestamp-only remote run directory; screenshots confirmed friendly primary labels for both, separate source badges, no horizontal overflow, and tooltip raw-ID auditability.Private Evidence
av-a15EntityProcess/agentv-privatedogfood/av-a15-compact-run-labelsc6381597d0649374674c6a6679f501b3421133189dogfood/av-a15/dashboard-friendly-run-labels-desktop.pngdogfood/av-a15/dashboard-friendly-run-labels-mobile-scrolled.png2093088c1e499f3af520a6889d5634fd963d2039