Skip to content

fix(accounts): keep Gemini usage bars visible during refetch - #8740

Merged
Wei-Shaw merged 1 commit into
Wei-Shaw:mainfrom
r266-tech:codex/gemini-usage-refetch
Nov 16, 2026
Merged

Wei-Shaw merged 1 commit into
Wei-Shaw:mainfrom
r266-tech:codex/gemini-usage-refetch

Conversation

@r266-tech

Copy link
Copy Markdown
Contributor

Fixes #8720

Gemini 用量刷新时,组件保留了旧 usageInfo,但模板会立即把已有用量条替换成更短的骨架屏,造成表格行跳动。骨架屏现在只在 loading && !usageInfo 时显示;已有用量条在刷新期间继续展示,取得新数据后更新,与现有 Claude 分支的条件一致。

验证:pnpm 9.15.9 冻结锁文件安装;现有 AccountUsageCell.spec.ts 64 项通过;CI 的 make test-frontend 通过全仓 ESLint、TypeScript 和 30 文件/586 项 critical Vitest;git diff --check 通过。仅一行模板条件改动。

项目当前的 Go 安全基线升级由 #8670 单独处理。实现与验证由 AI agent 完成,未调用真实 Gemini。

riofutab added a commit to riofutab/sub2api that referenced this pull request Nov 13, 2026
riofutab added a commit to riofutab/sub2api that referenced this pull request Nov 13, 2026
- Claude 链路:令牌轮换后 401 同账号重试,per-turn beta 保留轮次输出配置,Stainless 版本头与抬升后的 UA 对齐(Wei-Shaw#8737 Wei-Shaw#8742 Wei-Shaw#8731 Wei-Shaw#8726 Wei-Shaw#8724 Wei-Shaw#8698)。
- Codex/OpenAI 链路:Desktop 独立上下文原样转发并删除 fork 的 bootstrap 扫描器,分叉会话沿用父会话缓存键,刷新后的令牌在补充信息超时时仍保存(Wei-Shaw#8680 Wei-Shaw#8664 Wei-Shaw#8671 Wei-Shaw#8735 Wei-Shaw#8682 Wei-Shaw#8703)。
- 构建:Go 升到 1.27.4 修复 GO-2026-6859(Wei-Shaw#8670);前端 Gemini 用量条刷新不再跳动(Wei-Shaw#8740)。
- fork 带的 Wei-Shaw#8034 测试改为断言轮换后的凭据被保存,并为测试桩补齐 CAS 方法。
- 后端全量 unit、golangci-lint、前端 lint/typecheck/账号组件测试通过;repository 集成测试未跑。
@Wei-Shaw
Wei-Shaw merged commit 0563176 into Wei-Shaw:main Nov 16, 2026
8 of 9 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] AccountUsageCell: Gemini usage bars turn into a skeleton on every refetch

2 participants