fix(inference): default scenario to 8K/1K instead of Agentic Traces / 默认场景改为 8K/1K,不再是 Agentic Traces#552
Merged
Conversation
The bare /inference landing (and any page without an explicit ?i_seq=) now defaults the Scenario selector to the 8K/1K fixed-sequence scenario instead of Agentic Traces. Explicit ?i_seq= links, per-route initialSequence seeds (/compare pages), and the availability fallback ordering (selection → 8k/1k → first available) are unchanged. Agentic e2e specs now pin ?i_seq=agentic-traces explicitly, and a new e2e asserts the 8K/1K default holds even when the model has agentic data. 中文:将默认场景从 Agentic Traces 改为 8K/1K。未携带 ?i_seq= 参数的 /inference 页面现在默认选中 8K/1K 固定序列场景;显式 ?i_seq= 链接、 /compare 页面的 initialSequence 预设以及可用性回退顺序保持不变。 agentic 相关的 E2E 测试改为显式指定 ?i_seq=agentic-traces,并新增 E2E 用例验证即使模型有 agentic 数据,默认场景仍为 8K/1K。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
/inference(and any page without an explicit?i_seq=) now defaults the Scenario selector to 8K / 1K instead of Agentic Traces: theselectedSequencedefault inGlobalFilterContext.tsxflips fromSequence.AgenticTracestoSequence.EightK_OneK.?i_seq=share links still win (includingagentic-traces).initialSequenceseeds (/comparepages) still win.resolveEffectiveSequence(keep selection → prefer8k/1k→ first available) is untouched, so agentic-only models still resolve to their agentic scenario.PARAM_DEFAULTS.i_seqstays''(not a strippable'8k/1k'): per-routeinitialSequenceseeds make the no-param resolution route-dependent, so stripping an explicit 8K/1K pick would revert it to the route's seeded scenario on reload.default-sequence.ts,InferenceContext.tsx,url-state.ts,chart-selectors.tsx, test comments). The scenario dropdown's group order (Agentic listed first) is unchanged — display order only.Tests
bare /inference defaults to 8K / 1K even when the model has agentic data(ttft-x-axis-toggle.cy.ts) — availability contains both agentic and fixed-seq rows, and the selector must still land on 8K/1K./inferencedefault resolving to agentic; they now pin?i_seq=agentic-tracesexplicitly (including the overlay-path suite).pnpm typecheck,pnpm lint,pnpm fmt,pnpm test:unit(2560 passed), and e2e specsttft-x-axis-toggle(13/13),inference-chart,gpu-compare-agentic-detail,agentic-point-time-seriesagainst anE2E_FIXTURES=1server.Overlay support
Works for both official runs and
?unofficialrun=overlays: the default applies before any data loads, and unofficial-run availability still participates inavailableSequences/auto-switch exactly as before. The overlay-path e2e suite passes with the expliciti_seq=agentic-tracespin.中文说明
/inference(以及所有未携带?i_seq=参数的页面)的 Scenario 选择器默认值从 Agentic Traces 改为 8K / 1K:GlobalFilterContext.tsx中selectedSequence的默认值由Sequence.AgenticTraces改为Sequence.EightK_OneK。?i_seq=分享链接仍然优先(包括agentic-traces)。/compare页面的initialSequence预设仍然优先。resolveEffectiveSequence的可用性回退顺序(保留用户选择 → 优先8k/1k→ 第一个可用项)未改动,因此仅有 agentic 数据的模型仍会解析到 agentic 场景。PARAM_DEFAULTS.i_seq保持为'':由于各路由的initialSequence预设不同,若把'8k/1k'作为可剥离默认值,显式选择 8K/1K 后重新加载会回退到路由预设场景。测试:新增 E2E 用例验证即使模型有 agentic 数据,裸
/inference默认仍为 8K/1K;原依赖默认 agentic 的 E2E 套件改为显式指定?i_seq=agentic-traces(含 unofficial-run overlay 套件)。本地已通过pnpm typecheck、pnpm lint、pnpm fmt、pnpm test:unit(2560 个用例)及相关 E2E 测试。🤖 Generated with Claude Code
Note
Medium Risk
Default scenario affects first paint, benchmark fetches, and share-link behavior on
/inference, though explicit URL/route seeds and availability resolution are preserved; regression risk is mainly UX and wrong data path on load.Overview
Bare
/inference(no?i_seq=) now opens on 8K / 1K instead of Agentic Traces. The main behavioral change is inGlobalFilterContext:selectedSequenceinitializes toSequence.EightK_OneKrather thanSequence.AgenticTraces. Explicit?i_seq=, per-routeinitialSequence, andresolveEffectiveSequencefallback rules are unchanged.Comments and docs across
default-sequence.ts,InferenceContext,url-state, andchart-selectorsnow describe 8K/1K as the app default (Agentic still listed first in the dropdown for display only).PARAM_DEFAULTS.i_seqstays empty so share URLs keep explicit scenario picks.E2E: Agentic x-axis and overlay suites visit with
?i_seq=agentic-tracesinstead of relying on the old default. A new test asserts bare/inferenceshows 8K / 1K even when availability includes both agentic and fixed-seq data.Reviewed by Cursor Bugbot for commit 014bf30. Bugbot is set up for automated code reviews on this repo. Configure here.