Repository navigation
Conversation
…h updates a row With auto-refresh on, the accounts page replaces a row only when OpenAI or Grok usage inputs change, and AccountUsageCell watches only the OpenAI usage key, so Claude OAuth, setup-token and Gemini bars stay at what they loaded until the refresh button is clicked. Add usage refresh keys for Claude (session window columns, passive samples in extra, last_used_at) and Gemini (updated_at, last_used_at), replace a row when either changes, and have the cell watch one key across the three platforms. A change asks the batch loader for a forced refetch, or outside batch mode drops the cached entry and reloads, passive for Claude. Both backend paths read local data only, so a refetch per changed row sends no upstream request.
…nges The usage refresh key has no Gemini quota input. When a Gemini account's tier changes, as when the token refresher re-detects the Google One tier, auto refresh replaces the row but the key is unchanged: the tier badge shows the new tier, the quota bars keep the old limits until the account is used, Refresh is clicked or the page is reloaded. An API key account moved from a third-party base URL to the official one gets no bars for the same reason. The Gemini key now carries credentials.oauth_type, project_id, tier_id and base_url, the credentials geminiQuotaTierKeyForAccount depends on. Gemini usage is read from local usage logs, so the refetch sends nothing upstream, and a token refresh that leaves these four fields alone keeps the key.
riofutab
added a commit
to riofutab/sub2api
that referenced
this pull request
Nov 21, 2026
- 带入上游安全修复:同名字段重复且取值不一致的请求体在白名单之后统一拒绝,覆盖全部网关分组链 - 同步上游 v0.2.24 新合并的 PR:联网搜索 Exa 与来源回填、alpha/search 403 不罚账号、DeepSeek thinking 续接、System One 模型映射等;Wei-Shaw#8858 取代 fork 带的 Wei-Shaw#8860 - Wei-Shaw#8868、Wei-Shaw#8870、Wei-Shaw#8979 冲突处保留 fork 的等价实现并带入上游测试;Wei-Shaw#8900 与 fork 带的 Wei-Shaw#7935 重叠,未合入 - 合入开放 PR Wei-Shaw#8994 Wei-Shaw#8987 Wei-Shaw#8990 Wei-Shaw#8997,其中 Wei-Shaw#8997 截断 Gemini 泄漏的下一轮用户消息 测试:后端全量 unit 与 golangci-lint、前端 lint/typecheck/vitest 通过,CI 含 integration 全绿
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.
Follow-up to #8858.
After a Gemini account's tier changes, auto refresh updates the tier badge but the quota bars keep the old limits, because the usage refresh key has no Gemini quota input. An API key account moved from a third-party base URL to the official one gets no bars for the same reason.
The Gemini key now includes
credentials.oauth_type,project_id,tier_idandbase_url. Gemini usage comes from local usage logs, so the refetch sends nothing upstream.