Skip to content

fix(log): preserve quota in usage statistics - #7108

Merged
Calcium-Ion merged 2 commits into
QuantumNous:mainfrom
jimmyleocn:fix/preserve-usage-quota-stat
Aug 31, 2026
Merged

Calcium-Ion merged 2 commits into
QuantumNous:mainfrom
jimmyleocn:fix/preserve-usage-quota-stat

Conversation

@jimmyleocn

@jimmyleocn jimmyleocn commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Agent

  • Tool: Codex
  • Tool version: 0.150.1
  • Model (full id): gpt-5.6-sol
  • Host (CLI / IDE / GitHub coding agent / other): IDE
  • Date (UTC): 2026-08-31
  • AI assistance disclosure: 本变更由 AI 辅助定位、实现和验证,提交者已审阅代码及本 PR 描述,并对其准确性负责。

Links

User request

修复使用日志统计中 quota 始终为 0、但消费日志明细和 RPM/TPM 正常的问题,并确认问题存在于未修改的上游代码。

Out of scope — refuse

  • Matched: no
  • If yes, what was told to the user (stop here; do not open a PR): not applicable

本变更不涉及 Coding Plan、逆向渠道、第三方 API wrapper、Codex 协议、透传模式或第三方托管服务。

Kind

  • Bug fix
  • New feature
  • Performance / refactor
  • Docs
  • Other:

Issue facts

  • Actual behavior: /api/log/stat 返回的 quota 为 0,但 RPM/TPM、消费日志明细以及数据库中的 logs.quota 均为非零。
  • Impact: 管理员和用户会看到错误的用量汇总,可能误判为没有产生消费。底层消费日志和实际扣费数据没有丢失。
  • Frequency: 在当前 GORM v1.25.12 下,只要 quota 聚合结果非零并继续执行 RPM/TPM 扫描,该问题即可稳定复现。
  • Evidence that the problem is in new-api rather than the client or upstream:
    • 未修改的 upstream main 仍将两个不同投影的查询结果扫描到同一个 Stat。
    • 数据库直接汇总 logs.quota 为非零,但统计接口返回的 data.quota 为 0。
    • 独立 GORM 最小复现证明第二次 Scan 会将第一次扫描得到的 Quota 清零。
    • 该统计流程不涉及上游模型请求。
  • Applicable types and their fields:
    • Relay: not applicable。
    • Billing: 消费日志和扣费记录正常,错误仅发生在只读统计结果。
    • Frontend: 前端直接显示统计接口返回的错误 quota;本 PR 不修改前端。
    • Deployment: 问题已在 PostgreSQL 部署中复现;回归测试使用 SQLite。

Change

SumUsedQuota 原先依次将 quota 查询和 RPM/TPM 查询扫描到同一个 Stat:

tx.Scan(&stat)
rpmTpmQuery.Scan(&stat)

第一个查询只返回 quota,第二个查询只返回 rpm 和 tpm。GORM v1.25.12 初始化第二次结构体扫描时会清零目标值,因此第一次查询写入的 Quota 被重置为 0。

本 PR 将 RPM/TPM 查询扫描到独立的局部结构体,然后只把 Rpm 和 Tpm 赋回最终结果:

var rateStat struct {
    Rpm int
    Tpm int
}
rpmTpmQuery.Scan(&rateStat)
stat.Rpm = rateStat.Rpm
stat.Tpm = rateStat.Tpm

这样可以保留第一次聚合得到的 quota,同时维持原有 RPM/TPM 查询及最近 60 秒统计规则。

新增回归测试,验证一次统计请求能够同时返回正确的 quota、RPM 和 TPM。

Research

Duplicate / prior art

Docs and code

  • https://docs.newapi.ai/ : 未发现将使用日志 quota 汇总配置为 0 的选项或预期行为。
  • https://deepwiki.com/QuantumNous/new-api : 日志统计由后端接口提供 quota、RPM 和 TPM,没有要求存在消费记录时 quota 返回 0。
  • README / repo docs: 项目将用量统计和成本核算列为支持场景,没有与该现象对应的配置说明。
  • Code paths and what they imply for this change:
    • controller/log.go:GetLogsStat 和 GetLogsSelfStat 调用 model.SumUsedQuota。
    • model/log.go:quota 查询和 RPM/TPM 查询原先扫描到同一个 Stat。
    • web/src/features/usage-logs/api.ts:使用日志统计请求 /api/log/stat 或 /api/log/self/stat。
    • 前端直接使用接口返回的 quota,因此根因位于后端统计结果映射。

Alternatives considered

  • Option A: 使用独立的 RPM/TPM 结果结构体,再将两个字段赋回最终结果。
  • Option B: 使用条件聚合,将 quota 和最近 60 秒 RPM/TPM 合并为一条 SQL。
  • Why this approach: Option A 是最小、直接且跨数据库的正确性修复,不改变过滤条件和 RPM/TPM 最近 60 秒的业务语义。单查询性能优化应在独立 PR 中处理。

Files

Path Why
model/log.go 防止 RPM/TPM 查询覆盖已经聚合得到的 quota
model/log_stat_test.go 验证 quota、RPM 和 TPM 可以在同一次统计中正确返回

Behavior

Verification

Only what was actually run.

  • Commands and results:
    • go test ./model -run TestSumUsedQuotaPreservesQuotaWhenLoadingRateStats -count=1 -p 1 -parallel 1
      • PASS
    • go test ./model -count=1 -p 1 -parallel 1
      • PASS
    • go test ./controller -count=1 -p 1 -parallel 1
      • PASS
    • git diff --cached --check
      • PASS
    • GitNexus impact analysis:
      • Risk: LOW
      • Direct callers: GetLogsStat, GetLogsSelfStat
      • No affected execution flows detected
  • Manual steps and observed result:
    • 使用相同扫描结构分别测试 GORM v1.25.2 和 v1.25.12。
    • v1.25.2 第二次扫描后保留 Quota: 12345。
    • v1.25.12 第二次扫描后将其重置为 Quota: 0。
    • 改用独立 RPM/TPM 结构体后,回归测试得到 Quota: 12345、Rpm: 1、Tpm: 30。
  • UI: 本 PR 不包含前端变更;问题及根因证据已记录在 bug: 使用日志顶部用量显示 ¥0,但消费明细 quota 非零 #7106。
  • Tests added or updated, or why none:
    • 新增 TestSumUsedQuotaPreservesQuotaWhenLoadingRateStats。
  • Databases / providers / platforms exercised:
    • SQLite:自动化回归测试。
    • PostgreSQL:Issue 中的实际问题复现环境。
    • Provider: not applicable。
    • Platform: Windows amd64 开发环境。

Risks

Scope check

  • Single focused change: yes
  • Secrets included: no
  • Out of scope (Coding Plan / reverse-engineered channel / third-party wrapper / Codex): no

Summary by CodeRabbit

  • Bug Fixes

    • Fixed quota reporting so logged quota values are preserved while request and token usage metrics are calculated.
    • Improved accuracy of aggregate usage statistics for matching consumption records.
  • Tests

    • Added coverage to verify quota, request, and token metrics are reported together correctly.

@coderabbitai

coderabbitai Bot commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d534e23b-9887-4be0-8576-4297e4111c09

📥 Commits

Reviewing files that changed from the base of the PR and between 2b6f1df and 96daf7a.

📒 Files selected for processing (2)
  • model/log.go
  • model/log_stat_test.go

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.


Walkthrough

SumUsedQuota now loads RPM and TPM into a separate structure, preserving the quota from the earlier query. A regression test verifies quota, RPM, and TPM values for matching consumption logs.

Changes

Quota statistics

Layer / File(s) Summary
Preserve quota during rate aggregation
model/log.go, model/log_stat_test.go
SumUsedQuota copies RPM and TPM from a local structure without overwriting quota. The test verifies all three returned values.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 96daf

This change corrects usage statistics so quota is preserved while RPM and TPM remain available, without changing billing, authorization, logging, API shape, or deployment behavior. No actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: calcium-ion

Poem

A rabbit checked the quota stack
RPM and TPM came hopping back
The saved total stayed in sight
A test kept every number right
“No more zero,” whispered the night

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 2 files. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the primary change: preserving quota in usage statistics.
Linked Issues check ✅ Passed The changes address issue #7106 by preventing the RPM/TPM query from overwriting the aggregated quota. The regression test verifies that quota, RPM, and TPM remain available together.
Out of Scope Changes check ✅ Passed The changes are limited to the usage-statistics aggregation fix and its regression test. No unrelated code changes are present.
  • Fix all pre-merge checks with AI
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Calcium-Ion
Calcium-Ion merged commit 8c8c415 into QuantumNous:main Aug 31, 2026
1 check was pending
ChinaToyHunter added a commit to ChinaToyHunter/new-api that referenced this pull request Sep 1, 2026
…tions

Upstream picks: quota preservation in usage stats (QuantumNous#7108), legacy token
key constraint migration, README Video API link fixes.

Conflict resolutions:
- model/log.go: combine both halves of the same double-Scan fix (fork
  scans quota into quotaStat, upstream scans rpm/tpm into rateStat)
- 6x README: keep fork condensed version (ours); upstream link fix
  targets the upstream doc list section that the fork README replaced

Co-Authored-By: Claude <noreply@anthropic.com>
drwoodck pushed a commit to drwoodck/new-api that referenced this pull request Sep 2, 2026
* fix(log): preserve quota in usage statistics
yiranxiaohui pushed a commit to yiranxiaohui/new-api that referenced this pull request Sep 2, 2026
* fix(log): preserve quota in usage statistics

(cherry picked from commit 8c8c415)
salem-2007 added a commit to salem-2007/new-api that referenced this pull request Sep 10, 2026
* fix(log): preserve quota in usage statistics
lazzman pushed a commit to lazzman/new-api that referenced this pull request Sep 14, 2026
* fix(log): preserve quota in usage statistics
piexian added a commit to piexian/new-api that referenced this pull request Oct 4, 2026
…s 77-80 (#16)

* fix: purge authentication data on hard user deletion (QuantumNous#6168)

* fix: purge authentication data on hard user deletion

* fix: fail closed when 2FA status lookup fails

* fix: reject stale Telegram login callbacks

* fix(twofa): prevent concurrent backup code and lockout bypasses

* fix(auth): harden user deletion and Telegram verification

(cherry picked from commit b6b97a6)

* fix: infer MiniMax vendor for MiniMax models (QuantumNous#6164)

* fix: infer MiniMax vendor for MiniMax models

* Delete model/pricing_default_test.go

---------

Co-authored-by: duanxufu <duanxufu@rededa.com>
(cherry picked from commit a63364d)

* fix(data-table): update table body immediately when toggling columns (QuantumNous#6253)

DataTableRow's React.memo did not depend on columnVisibility.
TanStack row references stay stable when visible columns change, so the
table body did not refresh after View -> Toggle columns until another
action rebuilt the column definitions.

Capture a visible column id signature (visibleColumnIds) outside the
memo and compare it, matching the existing isSelected snapshot pattern.
All tables that use DataTableRow pick up the fix.

(cherry picked from commit dc9aeab)

* fix: prevent duplicate tool calls in Responses-to-Chat streaming (QuantumNous#6225)

When a function call was already registered under its output_index key
via response.output_item.added, the synthetic events built from the
terminal response.completed output carry no output_index and resolve to
a different item-based key. ensureToolForEvent then created a second
tool index and resent the full arguments, so Chat Completions clients
received the same tool call twice.

Reuse the tool registered under itemIDToKey/callIDToKey before creating
a new one, and alias the new key to the existing tool.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
(cherry picked from commit 1086038)

* fix: drop realtime beta header for ga models and register new ones (QuantumNous#6032)

(cherry picked from commit 16bfae1)

* fix: prevent duplicate suno task refunds via cas status update (QuantumNous#6074)

* fix: prevent duplicate suno task refunds via cas status update

* fix: reconcile failed task refunds

---------

Co-authored-by: CaIon <i@caion.me>
(cherry picked from commit e0d5156)

* fix: log response body when parsed upstream error message is empty

When an upstream error response parses as valid JSON but yields no usable
error message (e.g. an aggregator gateway returning {"error":{"message":""}}),
RelayErrorHandler previously produced a bare "bad response status code N"
error with no trace of the original body, making the failure undiagnosable.
Log the body preview in that case, mirroring the existing behavior for
unparseable bodies.

(cherry picked from commit 84a79b6)

* feat: add gemini-3-pro-image and gemini-3.1-flash-image GA models (QuantumNous#6371)

(cherry picked from commit 8b41def)

* fix: 慢查询/错误 SQL 日志参数化 (QuantumNous#6493)

* fix: parameterize slow/error SQL logs to avoid leaking credentials

* fix: validate SQL_SLOW_THRESHOLD_MS range

* fix: sanitize database driver error messages in SQL logs

* refactor: sanitize at gorm log writer seam to keep caller attribution

(cherry picked from commit c3db414)

* feat: support zstd request decompression (QuantumNous#6545)

(cherry picked from commit 0f9f668)

* fix(aws): cancel Bedrock requests on client disconnect (QuantumNous#6589)

* fix(aws): cancel Bedrock requests on client disconnect

* fix(billing): log effective usage billing path

(cherry picked from commit bd585d7)

* feat(rate-limit): add user critical rate limit middleware for access token and aff transfer routes

(cherry picked from commit 1da23d6)

* fix(ali): stop injecting top_p into requests that omit it (QuantumNous#6674)

(cherry picked from commit 2399de9)

* fix(ollama): preserve reasoning and tool-call context (QuantumNous#6605)

(cherry picked from commit 8ad159a)

* fix: backend length validation (QuantumNous#5548)

(cherry picked from commit d49160f)

* fix: 修复 Gemini 风格 /v1/models 列表请求 (QuantumNous#6199)

* fix: support Gemini model listing on v1 route

* test: cover Gemini query key model listing

(cherry picked from commit 3d5dc36)

* fix(topup): settle recharge orders atomically

(cherry picked from commit 50e5377)

* fix(billing): 异步任务退款时同步减少 used_quota (QuantumNous#6795)

* fix(billing): 异步任务退款时同步减少 used_quota
退款时仅恢复了 quota(剩余额度),但未同步减少 used_quota(已用额度),
导致"总额度"(quota + used_quota)随退款次数持续虚增,超出用户实际充值金额。

修复三处退款路径:
- RefundTaskQuota:任务失败完整退款
- RecalculateTaskQuota:差额结算退款分支
- controller/midjourney.go:Midjourney 任务失败退款

新增 model.UpdateUserUsedQuota 公开函数,仅调整 used_quota 不影响 request_count。

* fix(billing): 任务退款时同步扣减渠道 used_quota

* fix(billing): complete async task refund accounting

* style(model): group internal Midjourney fields

---------

Co-authored-by: CaIon <i@caion.me>
(cherry picked from commit 58d4e9b)

* fix(ali): 修复阿里图片模型映射后仍使用原始模型名判断协议的问题 (QuantumNous#6772)

* feat(ali): support Qwen Image 3 requests

* refactor(ali): narrow Qwen Image 3 support

* fix(ali): focus image model mapping fix

(cherry picked from commit 93d2df8)

* fix(topup): reject uncreditable orders before payment (QuantumNous#6845)

* fix(topup): reject uncreditable orders before payment

* fix(topup): align zero-ratio Stripe validation

* fix(topup): mirror settlement conversions in validation

(cherry picked from commit 2a0ce34)

* fix: settle Responses cached token usage (QuantumNous#6892)

(cherry picked from commit f116414)

* fix(billing): 修复时间规则恒真表达式导致倍率全天生效 (QuantumNous#6934)

(cherry picked from commit ac381ac)

* fix(relay): 请求参数校验错误返回 HTTP 400 (QuantumNous#6774)

* fix(relay): return 400 for invalid request parameters

(cherry picked from commit 0f2a207)

* fix(ali): honor image response format (QuantumNous#5513) (QuantumNous#7048)

(cherry picked from commit 0bee5d4)

* fix(sqlite): enable WAL + working busy timeout + _txlock=immediate to stop concurrent write lockouts (QuantumNous#7030)

* fix(sqlite): enable WAL + working busy timeout + _txlock=immediate to stop concurrent write lockouts

(cherry picked from commit 1751f43)

* fix(relay): bound the wait for upstream response headers (fixes unbounded heap growth → OOM) (QuantumNous#6949)

* fix(relay): bound the wait for upstream response headers (fixes unbounded heap growth)

The relay transport sets a dial timeout, a TLS handshake timeout and an expect-continue
timeout, but nothing bounds how long it waits for the upstream *response headers* after
the request has been written. An upstream that accepts the connection and then never
answers -- without sending FIN/RST, which is what happens when a NAT/firewall silently
drops the flow or the provider hangs -- parks the goroutine in
net/http.(*persistConn).roundTrip forever.

That goroutine keeps the whole request alive, which in practice means three copies of the
request body stay reachable for the lifetime of the process: the raw bytes from
io.ReadAll in CreateBodyStorageFromReader, the decoded messages held as json.RawMessage,
and the re-marshalled upstream body from common.Marshal. BodyStorageCleanup cannot help
here: it runs after c.Next() returns, and for these requests c.Next() never returns.

Measured on v1.0.0-rc.23 in production (see QuantumNous#6947 for the full evidence):

  - 23 goroutines stuck in persistConn.roundTrip on a single 40h-old instance,
    blocked between 353 and 1894 minutes (5.9h to 31.5h)
  - 96.9% of the live heap, sampled after a forced GC, attributable to those three
    body copies (HeapAlloc 892 MiB surviving three GC cycles; HeapObjects dropping
    30x while bytes dropped only 25%)
  - the live floor grows with uptime: 33.7 MiB at 0.1h, 89.2 at 13.8h, 510.0 at 40.1h,
    955.2 at 146.8h, OOMKilled at 172.9h -- same image, same config, same load

Doubling the memory limit and adding GOMEMLIMIT only moved the OOM from 132h to 172.9h.

RELAY_TIMEOUT (http.Client.Timeout) cannot be used for this: it covers the whole response
read and would cut legitimate long streaming calls, which is why it defaults to 0.
ResponseHeaderTimeout only bounds the wait for the headers; streaming after they arrive is
unaffected.

The default is deliberately generous. Non-streaming upstreams usually send the response
headers only once generation has finished, so the value has to leave room for a long
completion. 1800s is 12x shorter than the shortest hang observed here while leaving
several times the headroom a normal non-streaming request needs; 0 restores the previous
unbounded behaviour.

The assignment goes next to the other transport.* lines rather than inside the else
branch: newRelayHTTPTransport() normally takes the http.DefaultTransport.Clone() path,
and DefaultTransport does not set ResponseHeaderTimeout either.

This repo already sets ResponseHeaderTimeout on its other outbound transports
(controller/model_sync.go, controller/ratio_sync.go); the relay path appears to have
been missed.

Refs QuantumNous#6947. Likely also the root cause of QuantumNous#6731, which reported the same symptom
(production OOM on /v1/responses after ~64h) but was closed for template reasons.

* review: clamp overflowing timeout values and switch the test to testify

Addresses the two CodeRabbit findings on this PR.

Overflow (common/init.go:113): a RELAY_RESPONSE_HEADER_TIMEOUT beyond ~9.2e9 seconds
overflows time.Duration and can wrap into a *tiny positive* timeout, which would cut
every relay request instead of only the stuck ones. The value is now clamped before the
conversion, with regression tests for both the negative and the overflowing input.

I did not add fail-on-startup validation for negative values, for two reasons: the
existing `if seconds > 0` guard already treats them as "disabled", and the neighbouring
env-driven timeouts in this file are less strict still -- RelayIdleConnTimeout is
converted with no guard at all. Failing startup on a bad value would be a behaviour
change out of step with the rest of the file; happy to add it if you'd prefer that
direction repo-wide.

Test style: switched to testify (require.Equal / require.Zero / require.Positive), which
is what every other test under service/ uses.

go build, go vet and go test ./common/... ./service/... pass.
(`go build ./...` fails on the `web/dist` embed both with and without this change -- the
frontend bundle is not checked in.)

(cherry picked from commit b518d00)

* fix: adapt relaykit hosttypes to types and add missing errors import

* fix(log): preserve quota in usage statistics (QuantumNous#7108)

* fix(log): preserve quota in usage statistics

(cherry picked from commit 8c8c415)

* fix(model): do not treat no-op system task state writes as lock loss (QuantumNous#7135)

(cherry picked from commit b7017c2)

* perf(common): 批量复制 RawMessage,优化请求深拷贝 (QuantumNous#7221)

* perf(relay): bulk-copy Responses raw JSON fields

* perf(common): share RawMessage deep-copy optimization

---------

Co-authored-by: CaIon <i@caion.me>
(cherry picked from commit 2cf177a)

* fix(audio): normalize file extension case in GetAudioDuration (QuantumNous#7321)

Uppercase or mixed-case extensions (e.g. .MP3, .WAV) fell through to the
default branch and returned "unsupported audio format", so audio token
usage could not be measured. Lowercase the extension before the switch.

Closes QuantumNous#7319

(cherry picked from commit 76f7daf)

* fix(ollama): preserve tool calls from final stream frame | 保留流式末尾帧的 tool calls (QuantumNous#7376)

(cherry picked from commit 8e5e091)

* fix(gemini): reject :countTokens as an unknown route instead of relaying it as generateContent (QuantumNous#7388)

(cherry picked from commit 81336fc)

* fix(relay): request stream usage on every cross-protocol conversion to OpenAI chat (QuantumNous#7389)

(cherry picked from commit 610334d)

* fix(billing): count upstream images by payload instead of data length

OpenaiImageHandler and the JSON-to-SSE fallback billed the gjson data.#
element count. An object-shaped data yielded 0 and kept the requested n
while the SSE fallback dropped the image and sent only [DONE]; one image
split into a url entry and a b64_json entry billed twice; entries carrying
only revised_prompt billed as images.

Count images by payload: an object with url or b64_json is one image and
arrays bill max(url entries, b64_json entries). The SSE fallback forwards
one completed event per image payload for both shapes. xAI inherits the
fix through OpenaiImageHandler.

(cherry picked from commit 07578fa)

* fix(relay): map Images output_tokens_details into img_o billing (QuantumNous#7410)

(cherry picked from commit e2bb05f)

* fix(task): accept any 2xx upstream status on task submission (QuantumNous#7478)

(cherry picked from commit d61d6be)

* fix(auth): reject non-standard roles when creating a user (QuantumNous#7531)

(cherry picked from commit 2506e1b)

* fix: isolate TLS configs across HTTP transports (QuantumNous#7627)

(cherry picked from commit feefe09)

* fix(model): migrate database constraints, options primary key, and avoid redundant migrations

* feat(channel): add Sub2API, NewAPI, vLLM, and SGLang channels (77-80) and Tencent TokenHub

---------

Co-authored-by: Seefs <40468931+seefs001@users.noreply.github.com>
Co-authored-by: fuxdev <15846422264@163.com>
Co-authored-by: duanxufu <duanxufu@rededa.com>
Co-authored-by: DawnMoon1542 <160485532+DawnMoon1542@users.noreply.github.com>
Co-authored-by: Niku <nikuliu@foxmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: feitianbubu <feitianbubu@qq.com>
Co-authored-by: CaIon <i@caion.me>
Co-authored-by: bigsong <35025755+bigsongeth@users.noreply.github.com>
Co-authored-by: ENCHIGO <38551565+ENCHIGO@users.noreply.github.com>
Co-authored-by: zhibisora <73344387+zhibisora@users.noreply.github.com>
Co-authored-by: wans10 <51012039+wans10@users.noreply.github.com>
Co-authored-by: Scott <908181134@qq.com>
Co-authored-by: Shawn Wang <32839114+enwaiax@users.noreply.github.com>
Co-authored-by: Qi <108174052+LiaoQi98@users.noreply.github.com>
Co-authored-by: zcxads666 <128150298+zcxads666@users.noreply.github.com>
Co-authored-by: Alex Xiang <ax2@zicode.com>
Co-authored-by: PuppetKL <154485567+PuppetKL@users.noreply.github.com>
Co-authored-by: Xayinn <129403670+LinineTy@users.noreply.github.com>
Co-authored-by: txgo <tianxi.liu@gmail.com>
Co-authored-by: jimmyleocn <42566991+jimmyleocn@users.noreply.github.com>
Co-authored-by: mingisrookie <99650899+mingisrookie@users.noreply.github.com>
Co-authored-by: Vladimir Babin <vovababin@gmail.com>
Co-authored-by: sxhstc <406739419@qq.com>
leicanxi pushed a commit to leicanxi/flowbee-api that referenced this pull request Oct 5, 2026
* fix(log): preserve quota in usage statistics

(cherry picked from commit 8c8c415)
cha-eunho pushed a commit to attodev/new-api that referenced this pull request Oct 14, 2026
* fix(log): preserve quota in usage statistics

Upstream: QuantumNous@8c8c415
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
NaturalSelect pushed a commit to NaturalSelect/new-api that referenced this pull request Nov 5, 2026
* fix(log): preserve quota in usage statistics

(cherry picked from commit 8c8c415)
timwenx pushed a commit to timwenx/new-api that referenced this pull request Nov 18, 2026
* fix(log): preserve quota in usage statistics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: 使用日志顶部用量显示 ¥0,但消费明细 quota 非零

2 participants