Repository navigation
Conversation
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Oct 9, 2026
- 合入上游 Wei-Shaw#7933:运维请求明细弹窗新增账号列,按 lite 账号列表缓存 id 到名称的映射,缺失时显示 #id 测试:随整合分支统一验证(unit 全量、golangci-lint、前端检查)。
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Oct 9, 2026
- 合入上游已合并的 Wei-Shaw#7618:平台改为数据驱动,接入 Command Code 与 Cline,Go 升级到 1.27.2,golangci-lint 升级到 v2.14.0。 - 合入开放 PR Wei-Shaw#7920 Wei-Shaw#7924 Wei-Shaw#7928 Wei-Shaw#7930 Wei-Shaw#7931 Wei-Shaw#7933 Wei-Shaw#7935 Wei-Shaw#7936 Wei-Shaw#7939 Wei-Shaw#7941 Wei-Shaw#7947 Wei-Shaw#7951 Wei-Shaw#7954 Wei-Shaw#7956 Wei-Shaw#7960。 - 新增 Decisions 决策接口(Wei-Shaw#7922)及其与 TypeSafe System One 的双向互转(Wei-Shaw#7948),上游 404 时切换账号。 - Haiku 5.5 的 top_p 违规请求在网关直接拒绝,OAuth 伪装不再在 top_p 旁补 temperature,工具集 beta 过滤覆盖 Haiku 5.5。 - 修正新增代码的静态检查告警。 全量 unit 测试、golangci-lint、前端全量 vitest 均已通过;集成测试本机无 Docker,待 CI 验证。
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
问题
运维监控的请求明细(TTFT / 耗时弹窗)只能看到平台和模型,看不到请求走的是哪个账号。排查慢 TTFT 时需要判断是哪几个账号(不同账号可能来自不同 provider/上游)比较慢,目前无从下手。
关闭 #7926。
修复
纯前端实现,不改后端(明细接口本来就返回
account_id,ops_repo_request_details.go两个分支都已 SELECT,只是前端没展示):accountNameMap工具:用现有 lite 账号列表接口(lite=1,page_size=1000,分页拉全量)构建 id→名称映射,模块级缓存避免每次打开弹窗都拉全量;明细里出现缓存缺失的账号 id 时强制刷新一次(覆盖新建账号场景)。OpsRequestDetailsModal桌面表格在「模型」后新增「账号」列,移动端卡片视图同步展示;映射缺失时降级显示#id,加载失败静默降级不影响明细本身。admin.ops.requestDetails.table.account。issue 中"按账号/按模型统计过滤"的部分本 PR 未做(明细接口已支持
account_id筛选参数,后续可在弹窗加筛选器),先交付主诉求的账号列。验证
npx vitest run src/views/admin/ops/components/__tests__/OpsRequestDetailsModal.spec.ts— 5/5 通过(含新增用例:账号名渲染、缺失 id 回退#999、触发缓存强刷)npx vue-tsc --noEmit— 通过