github/sub2api
4
0
Fork 0
mirror of https://github.com/Wei-Shaw/sub2api.git synced 2026-10-29 16:20:27 +00:00
Code Issues Packages Projects Releases Wiki Activity
6,553 Commits 49 Branches 65 Tags
d2f87c612e1820f6d4900a71fda1248c5b3544ed
Commit Graph
6553 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
ice breaker b6a7b8b7df fix(repository): allow eight transient database retries 2026-08-31 17:10:31 +08:00
li 1dc0a09009 fix(openai): ctx_pool WS ingress 下发前改写上游容量降载错误码 
上游容量降载（server_is_overloaded / slow_down）被 ctx_pool 的 ingress 直写路径
原样转发给客户端。Codex CLI 按闭集判定，这两个码属致命集，客户端打印
"Selected model is at capacity" 并直接终止会话，不退避重试。

仓库已有 sanitizeOpenAICapacityShedErrorCodeForClient 处理这件事，且注释写明了
Codex 的闭集判定与"账号状态判定使用改写前原始 payload"的前提。它此前只在
HTTP/SSE（openai_gateway_response_handling.go）与 http_bridge
（openai_ws_http_bridge.go）两条路径被调用，ctx_pool ingress 直写路径是唯一漏掉
的一条——同一账号同一时刻切到 http_bridge 就能正常退避重试。

改写结果写入独立的 clientMessage，不动 upstreamMessage：写出点之后的
markOpenAIWSClientVisibleFailure 与 handleOpenAIWSTerminalTransientFailure
仍按原始 payload 判定账号状态，与 http_bridge 的写法一致。

新增用例覆盖改写生效与改写范围两侧（非容量类错误码必须原样下发）。
 2026-08-31 16:53:57 +08:00
Wesley Liddick e98ef32eb2 Merge pull request #6414 from fengshao1227/fix/anthropic-responses-stream-lifecycle 
fix(apicompat): Anthropic→Responses 流式转换丢失助手文本（thinking 块顶掉未关闭的 message item + content_index 从不推进）
v0.1.184 		2026-08-31 16:43:40 +08:00
ice breaker 863667ce67 fix: retry transient database startup errors 2026-08-31 16:25:13 +08:00
li 8f5451587e fix(apicompat): Anthropic→Responses 流式转换在 thinking 块前关闭 message item 并推进 content_index 
thinking 块开始时不关闭已打开的 message item，直接覆盖 CurrentItemType/
CurrentItemID，累积的助手文本既不进 state.Outputs 也拿不到 output_item.done，
response.completed 只带 reasoning——客户端收到「成功但无输出」。同 switch 的
tool_use 分支本来就先调 closeCurrentResponsesItem，只有 thinking 漏了。

content_index 只在 item 打开时置 0，从不推进。同一 message item 里第二个 text
块会再发一次 content_part.added(content_index=0)，与第一个 part 撞在同一下标，
SDK 累积式 helper 按 content[content_index] 写入时后者覆盖前者。反方向
responses_to_anthropic.go 有三处 ContentBlockIndex++，正方向一处都没有。

新增用例覆盖两条坏顺序，外加一条生命周期不变式用例（output_item.added 与
output_item.done 必须配平、terminal 事件按announce 顺序逐项携带）。
 2026-08-31 16:15:08 +08:00
Wesley Liddick 85b593fd2f Merge pull request #6411 from Wei-Shaw/fix/openai-ttft-setting-ui 
fix(openai): move TTFT metric mode to admin settings
 2026-08-31 15:39:12 +08:00
shaw 0fcec63b68 test(openai): isolate visible TTFT fixture 2026-08-31 15:15:44 +08:00
shaw 8553c91c1a test(api): update settings contract fixture 2026-08-31 15:05:39 +08:00
shaw c66e700f05 fix(openai): move TTFT metric mode to admin settings 2026-08-31 14:52:07 +08:00
Wesley Liddick fdf9751c12 Merge pull request #6378 from Ritel-T/fix/codex-oauth-service-tier-billing 
fix(openai): preserve Codex OAuth Fast billing tier
 2026-08-31 13:56:00 +08:00
wucm667 1be69e56aa fix(openai): accept delegation bootstrap without call id 2026-08-31 12:57:06 +08:00
qiujunandClaude Opus 5 e7c029875c test(billing): 图片输出按 output 子集计价 
上一条改用统一定价管线后，TestTryModelFilePricing_WithImageOutput 挂在 0.3 vs
0.28：原算式把 ImageOutputTokens 当 OutputTokens 之外的额外量叠加，等于按文本
output 价和图片价各收一次，测试固化了这个重复计费。

ImageOutputTokens 本就是 OutputTokens 的子集（Gemini 取自 candidatesTokensDetails
的 IMAGE 档，OpenAI 取自 output_tokens_details），统一管线先扣除再按图片单价计，
未配图片价时回退到 output 价、总额不变，正是这个语义。期望改为 0.28。

影响：涉及图片输出的模型，账号统计成本会降低"图片 token × 文本 output 单价"。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-31 12:33:06 +08:00
Wesley Liddick 0678b24d58 Merge pull request #6283 from okbexx/feat/usage-compaction-kind 
feat(usage): track native compaction requests
 2026-08-31 11:19:37 +08:00
Wesley Liddick b369fbca15 Merge pull request #6395 from lylelllll/fix/account-expiry-timezone 
fix(frontend): clarify local timezone for expiry inputs
 2026-08-31 11:18:55 +08:00
Wesley Liddick 36ee193e3c Merge pull request #6367 from qiujun8023/fix/usage-stats-cards-mobile-horizontal-scroll 
fix(frontend): prevent hidden cache tooltip from causing horizontal scroll on mobile
 2026-08-31 11:18:03 +08:00
Wesley Liddick 1dd0f2e5dc Merge pull request #6384 from alfadb/fix/unify-usage-window-style 
fix(frontend): unify usage window rendering and tighten alert thresholds
 2026-08-31 11:17:09 +08:00
Wesley Liddick f34735f462 Merge pull request #6388 from alfadb/feature/ollama-usage-cn-platforms 
feat(ollama): 用量窗口支持挂在国产三家平台下的 Ollama Cloud 账号
 2026-08-31 11:16:25 +08:00
Wesley Liddick a2d7d41185 Merge pull request #6325 from 251392463/fix/grok-responses-vision-tool-output 
fix(grok): preserve Responses vision tool output images
 2026-08-31 11:15:33 +08:00
Wesley Liddick 03ab687686 Merge pull request #5866 from wucm667/fix/issue-5863-scope-monitor-groups 
fix: scope channel monitor groups by user access
 2026-08-31 11:15:13 +08:00
Wesley Liddick 2e756b71f2 Merge pull request #6198 from xuhaihan/fix/openai-reauth-refresh-token 
fix(accounts): reauthorize OpenAI with refresh token
 2026-08-31 11:14:12 +08:00
Wesley Liddick fbc69322af Merge pull request #6254 from wucm667/fix/issue-6249-configurable-image-cooldown 
feat(openai): configure image tool cooldown
 2026-08-31 11:13:52 +08:00
Wesley Liddick 414489d152 Merge pull request #5469 from wucm667/fix/issue-5467-passthrough-http-bridge 
fix(openai-ws): bridge oversized passthrough requests
 2026-08-31 11:13:35 +08:00
Wesley Liddick 50a9dd7a64 Merge pull request #6386 from wucm667/fix/issue-6383-isolate-passthrough-ws 
fix(openai): isolate passthrough websocket sessions
 2026-08-31 11:13:16 +08:00
Wesley Liddick a4156eea10 Merge pull request #6385 from wucm667/fix/issue-6381-preserve-quota-limits 
fix(admin): preserve quota limits on partial group updates
 2026-08-31 11:12:56 +08:00
Wesley Liddick e0ecb55d4b Merge pull request #4872 from wucm667/fix/issue-4845-reset-scheduler-rate-limit 
fix(account): clear rate limit on quota reset
 2026-08-31 11:12:35 +08:00
wucm667 897faea333 fix(account): reset quota cooldown atomically 2026-08-31 09:12:09 +08:00
feeeei 0e08c39999 fix(openai-ws): remember rejected encrypted content across turns 
invalid_encrypted_content 恢复此前只清理当次请求体：同一失效密文随客户
端维护的会话历史在后续每一轮重新出现，反复触发"整包被拒→剥离→重试/
重连"（#6382 生产观测 2h 内 251 次 recovery、273 次 WS 重连），既是
QoS 放大器也是内存压力放大器。

按会话记录被上游拒绝过的 encrypted_content SHA-256 摘要（lineage）：
- OpenAIWSStateStore 新增会话级摘要绑定，TTL 复用 session sticky，
  单会话 512 摘要为存储自保护，超出仅退化为既有单次 recovery
- 写点覆盖 forward WSv2 recovery、forward 非 WS 400 重试、ingress
  error 事件、bridge 400/流内 error；读点在 forward 进场与 ingress/
  bridge turn 循环入口按摘要预剥离，新密文摘要不同不受影响
- 只收剥离端可处理的项类型（reasoning/compaction/compaction_summary），
  避免记入永远剥不掉的摘要后每轮空转解码
- replay 历史序列同步剥离，避免与已剥离的当前 input 项错位导致
  prefix 复用失配

含端到端集成测试：turn1 上游拒绝即记录，turn2 上游收到的请求不再携带
失效密文且 reasoning 骨架保留。
 2026-08-31 01:02:13 +08:00
feeeei ca9b4d73f2 fix(openai-ws): share immutable replay bodies to stop O(T²) copying 
OpenAI Responses WS/HTTP-bridge 的 replay 历史此前每轮对全部正文做多次
深拷贝（构建、双份序列、保存点各一遍），长会话累计分配 O(T²)，实测
128 turn x 10KiB 达 160MB+，是 #6382 内存持续增长直至 OOM 的主因。

改为共享不可变正文所有权：
- extract 经零拷贝 string 视图 + gjson Index 直接切 payload 子切片，
  并以 json.Valid 保持对断裂数组的既有错误语义
- 序列构建/sanitize/collector/保存点全部只传引用；跨持有者保存经
  combineOpenAIWSReplayItems 新建头数组，正文不复制
- bridge 每轮一次解析，正常 replay 与 account-failover 序列共享正文
- 前缀比较增加字节级快路径，避免逐轮全历史 decode+encode
- strict 状态可用时不再整包保留上一轮 payload

新增 128 turn 分配回归测试锚定上界（实测 2.5MB，深拷贝回归会击穿），
以及正文共享的所有权断言。
 2026-08-31 01:01:20 +08:00
lylelllll 94edcd5d81 chore: remove second misplaced component copy 2026-08-30 23:31:59 +08:00
lylelllll 3673702af5 chore: remove misplaced uploaded component copy 2026-08-30 23:27:08 +08:00
lylelllll 5778739cdb fix(frontend): use strict local expiry parsing for redeem codes 2026-08-30 23:20:59 +08:00
lylelllll 81e461f651 fix(frontend): parse local expiry datetimes strictly 2026-08-30 23:19:45 +08:00
lylelllll b7aca87fd0 test(frontend): cover local datetime parsing across timezones 2026-08-30 23:17:11 +08:00
lylelllll ae1bcdc25d fix(frontend): clarify expiry timezone in Chinese labels 2026-08-30 23:15:54 +08:00
lylelllll 263605779c fix(frontend): clarify expiry timezone in English labels 2026-08-30 23:13:52 +08:00
qiujunandClaude Opus 5 9eabd2a5b7 fix(billing): apply model pricing policies to account stats cost 
resolveAccountStatsCost 的优先级 3 维护了第二份"单价 × token 数"实现，每加一个
定价特性都要手工镜像：service tier 与长上下文分别由 9261dd77、25e6688a 补齐，
而 b5827cfd 引入的 DeepSeek 官方峰谷一直没有生效，高峰时段账号成本最多低估一半。

改为复用 CalculateCostWithServiceTier。channelPricing 仍为 nil，优先级 3 的语义
不变：只取模型定价文件、不引入渠道自定义定价；低谷时段结果与原算式完全一致。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-30 22:57:53 +08:00
lylelllll d66bc88e68 fix(frontend): apply expiry input changes in source paths 2026-08-30 22:11:22 +08:00
lylelllll 8177f27aa3 fix(frontend): clarify local timezone for expiry inputs 2026-08-30 22:10:15 +08:00
wucm667 d5a0124637 fix(openai): isolate passthrough websocket sessions 2026-08-30 16:49:01 +08:00
alfadb 30b29e51e8 feat(ollama): 用量窗口支持挂在国产三家平台下的 Ollama Cloud 账号 
Ollama Cloud 用量窗口（浏览器会话、5h/7d 快照、自动刷新、同 key 组共享）此前
只认 platform ∈ {openai, anthropic} 的 apikey 账号。但网关对 kimi/zhipu/deepseek
的 apikey 账号同样按 credentials.base_url 转发，用户把 Ollama Cloud 的 key 挂在
这三个平台下跑 Ollama Cloud 托管的 glm/kimi/deepseek 模型时，请求转发正常，用量
窗口却完全不可用。

- 平台白名单放开到 {openai, anthropic, kimi, zhipu, deepseek}；type='apikey'
  与官方 ollama.com base_url 的限制不变
- Go 侧收敛为 isOllamaCloudUsagePlatform，SQL 侧收敛为
  ollamaCloudUsagePlatformsSQL，6 处白名单只引用单一来源，并补两侧互为镜像的
  漂移守卫测试
- CN 周期余额/额度探测跳过 ollama 用量账号：其探测端点由 base_url 衍生，对
  ollama.com 会被出站 URL 白名单拒绝，每轮都白跑并产生噪声
- 前端账号列表 CN 分支在 eligible 时改渲染 Ollama 用量窗口，并跳过 CN 额度/
  余额子单元格（同上，渲染出来只会是一行探测报错）
 2026-08-30 16:38:11 +08:00
wucm667 9f1effd71c fix(admin): preserve quota limits on partial group updates 2026-08-30 16:36:13 +08:00
alfadb 6532d5b61e fix(frontend): unify usage window rendering and tighten alert thresholds 
CN provider accounts (Kimi/Zhipu/DeepSeek) and the monitor quota view each
hand-rolled their own usage bar, so the same account column rendered three
different label styles, bar widths and threshold palettes. Both now reuse
UsageProgressBar, the component the other five platforms already share.

Also move the default utilization thresholds from >=100 red / >=80 amber to
>=90 / >=75. Turning red only once the quota is exhausted is an after-the-fact
notice rather than a warning. The remainingCapacity mode keeps its 20/50 pair,
which is already a warning semantic.

- UsageProgressBar: add labelWidth 'fixed' | 'auto' so the monitor view can
  render composite labels ("Pro/7d") without breaking column alignment; the
  fixed branch is byte-identical, so the existing platforms are untouched
- drop the superseded utilizationColor/utilizationTextColor/formatReset copies
- shorten CN window labels to 5h / 7d and remove the now-dead resetSoon keys
 2026-08-30 15:34:21 +08:00
Long Li 57c76584a6 fix(codex): advertise priority tier for fast models 2026-08-30 14:21:08 +09:00
Ritel-T 82105f260a fix(billing): resolve shadow credential tier contract 2026-08-30 13:40:37 +09:00
Ritel-T 50ad6e2e50 fix(billing): narrow Codex OAuth default exception 2026-08-30 13:40:19 +09:00
Ritel-T f323d84644 test(billing): cover Codex OAuth usage pricing 2026-08-30 13:07:33 +09:00
Ritel-T 3a9070359b fix(billing): scope Codex OAuth tier trust 2026-08-30 13:07:21 +09:00
Ritel-T d39fc491ec test(openai): cover websocket tier separation 2026-08-30 13:07:07 +09:00
Ritel-T 2b8cb628b6 fix(openai): preserve tiers in messages chat fallback 2026-08-30 13:06:45 +09:00
Ritel-T 8b4b3f4a94 fix(openai): preserve tiers in responses chat fallback 2026-08-30 13:06:32 +09:00