[maxmad64bis]

⚠️ base-red inherited: #15306

Summary

Quota fetcher reads go out as direct fetches instead of using the proxy assigned to the connection. A shared helper now resolves the assigned proxy and runs each read inside that proxy context, reporting an unknown reading instead of fetching directly when the proxied read fails. Without an assigned proxy the fetch runs unchanged.

Related Issues

• Related to fix(providers): Codex quota auto-ping bypasses the connection proxy — warm-up ping and its usage read leave from the server IP #14997 (closed by fix(quota): keep Codex auto-ping on the connection proxy #15084 for auto-ping alone) — this change extends the same pattern to the fetcher class

Target Branch

• Base is the active release/v3.8.x branch (the highest open release/v*), not main
• New feature? From 3.8.55 on it is held with the v4-feature label for the v4 channel

Validation

• Change type: other
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/quota-fetchers-connection-proxy.test.ts — 17 cases: helper routing, passthrough, missing identifier, failures, and one case per fetcher inside the proxy context.
• tests/unit/bailian-usage.test.ts — 4 cases: known entries pass an identifier; a no-identifier entry fetches nothing.

Coverage Notes

• open-sse/services/qwenTokenPlanQuotaFetcher.ts — covered by "qwen token plan quota reads the dashboard and gateway inside the proxy context".
• open-sse/services/agentrouterQuotaFetcher.ts — covered by "agentrouter quota reads inside the proxy context".
• open-sse/services/alibabaFreeTierQuotaFetcher.ts — covered by "alibaba free tier quota reads inside the proxy context".
• open-sse/services/bailianQuotaFetcher.ts — covered by "bailian quota retries the fallback host inside the proxy context".
• open-sse/services/codexQuotaFetcher.ts — covered by "codex quota reads inside the proxy context".
• open-sse/services/context7QuotaFetcher.ts — covered by "context7 quota reads inside the proxy context".
• open-sse/services/deepseekQuotaFetcher.ts — covered by "deepseek quota reads inside the proxy context".
• open-sse/services/firecrawlQuotaFetcher.ts — covered by "firecrawl quota reads inside the proxy context".
• open-sse/services/grokCliQuotaFetcher.ts — covered by "grok cli quota reads inside the proxy context".
• open-sse/services/grokQuotaFetcher.ts — covered by "grok web billing reads inside the proxy context".
• open-sse/services/xaiOauthQuotaFetcher.ts — covered by "getUsageForProvider without a connection id reports no reading instead of fetching directly" in tests/unit/bailian-usage.test.ts (empty-identifier guard shared with the threaded call).

Reviewer Notes

• Behavior: quota readings now use the assigned egress path; without an assigned proxy the fetch runs unchanged, and a failed proxied read reports an unknown reading instead of fetching directly.
• Merge: lands before fix(quota): route remaining console quota reads through the connection proxy #16344, which extends the same helper to the nine remaining readers.
• Follow-up: routing the remaining direct console quota reads (jina, llmgateway, lyceum, moonshot, new-api aggregator, opencode, openrouter, tavily and v0) through the assigned proxy is left for a later change.

[diegosouzapw]

Hi @maxmad64bis — closing this pull request to clear the open queue. The branch fix/quota-fetchers-through-connection-proxy is kept, so the commits stay. Comment here if it should be reopened.

[diegosouzapw]

Hi @maxmad64bis — reopening this pull request. The close was a mistake, and it is back in the merge queue. The branch fix/quota-fetchers-through-connection-proxy was kept.