令牌搜索适配MySQL，MJ日志增加图生文 图生图 - #5
Merged
Merged
Conversation
Calcium-Ion
pushed a commit
that referenced
this pull request
Jan 8, 2024
seefs001
pushed a commit
that referenced
this pull request
Oct 10, 2025
Fork Sync: Update from parent repository
This was referenced Jan 23, 2026
Closed
DeJeune
added a commit
to DeJeune/new-api
that referenced
this pull request
Jan 27, 2026
* feat: implement oauth * chore: modify image * fix: make error message consistent add avoid magic number * chore: clean unused env * chore: clean again * feat(oauth): oauth client * feat(ui): oauth test * feat(oauth): implement oauth clients * fix: clean local yaml
quqi1599
pushed a commit
to quqi1599/new-api
that referenced
this pull request
Apr 6, 2026
stratosphere-ai
pushed a commit
to stratosphere-ai/new-api
that referenced
this pull request
Apr 12, 2026
Critical fixes: - QuantumNous#1+QuantumNous#10: Wire hourly/daily cap checking into channel selection via ChannelShouldSkip hook + listing cache for hot-path lookups. IncrementHourlyDailyCaps now called after successful trade. - QuantumNous#2: Capture RecordTrade error in relay handler and log it - QuantumNous#3+QuantumNous#4+QuantumNous#6: Wrap RecordTrade in GORM DB.Transaction for atomicity (trade record + seller credit + token count in single tx, rollback on any failure) Important fixes: - QuantumNous#5: Add seller self-service withdrawal request endpoint POST /seller/withdrawal/request with CriticalRateLimit + withdraw button on earnings page - QuantumNous#7: Admin suspend now collects and reports listing disable errors instead of silently ignoring them - QuantumNous#8: Anthropic key validation changed from POST /v1/messages to GET /v1/models (lightweight, read-only, no token consumption) - QuantumNous#9: CriticalRateLimit added to seller register, create listing, create API token, and withdrawal request endpoints https://claude.ai/code/session_01VUyzgwX29o57mjURxJvYiN
x22x22
pushed a commit
to x22x22/new-api
that referenced
this pull request
Apr 24, 2026
令牌搜索适配MySQL，MJ日志增加图生文 图生图
QQhuxuhui
added a commit
to QQhuxuhui/new-api
that referenced
this pull request
May 7, 2026
- GET history items now include operator_admin_username (LEFT JOIN users) and topup_count (subquery COUNT) per spec - POST response includes topup_count so success toast can show "覆盖 N 笔充值" instead of dollar total - Add TestRebindAfterPayout regression test for spec acceptance QuantumNous#5 Known limitation: InviteeRechargesTab is rendered inside UserDetailModal's {data ?} analytics-data guard. If analytics fetch fails, the entire modal (including this tab) shows Empty. This is consistent with the existing behavior of the other tabs and out of scope for this feature. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
JAYotta
added a commit
to GraylightCN/new-api
that referenced
this pull request
May 8, 2026
Squashed cherry of the PR QuantumNous#5 review feedback train (private fork). Generic-only files; graylight-specific callback wiring is left out. Key changes: - service/task_billing.go: settle now wraps task.Quota persistence, funding adjustment, used_quota / channel.used_quota updates and billing log in a single DB transaction. RowsAffected guard on the targeted UPDATE so a phantom task ID aborts the settle without applying side effects. Subscription updated_at now reuses the settle timestamp. Cache invalidation moved out-of-tx to keep the primary commit fast. - service/task_polling.go: SettleTaskBillingOnComplete is exported, accepts a nil adaptor (token fallback path), prefers TotalTokens but falls back to CompletionTokens when only the latter is reported. - model/task.go: TieredVolcFlags grows resolution / duration / service_tier fields so the tiered_expr settle path can evaluate param() lookups even on callback-only deployments where task.Data is just {"id":"..."}. - controller/relay.go: extractVolcFlags refactored to call the new parseVolcDuration helper. parseVolcDuration accepts float64, int, int64, json.Number and string forms; rejects negative, non-integer and out-of-int-range values. The decoder uses json.Decoder.UseNumber so numeric JSON values arrive as json.Number rather than float64. - relay/channel/task/volcadapter/adaptor.go: buildSynthesizedBody reads resolution / duration / service_tier from TieredVolcFlags first, falling back to task.Data only when flags are absent — fixes settle on callback-only deployments. AdjustBillingOnComplete comment updated to reflect exported SettleTaskBillingOnComplete name. Tests: - service/task_billing_test.go: regression tests for the targeted UPDATE persistence, RowsAffected==0 guard, funding rollback, CAS win/lose on both refund and settle, nil-adaptor token fallback, PerCallBilling skip with nil adaptor, effectiveTokenCount fallback. - controller/relay_volc_flags_test.go: parseVolcDuration string / json.Number / oversized / non-integer cases. - relay/channel/task/volcadapter/adaptor_test.go: two new cases for callback-path flags carrying resolution and flags taking priority over task.Data in buildSynthesizedBody. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
本地 Agent 已接管，开始处理 #5... |
Closed
k272314374
pushed a commit
to k272314374/hmrouter
that referenced
this pull request
May 16, 2026
另一窗口页面评审发现 5 处，逐条修复： QuantumNous#1 TASKS M1 任务数 74→104（实质 bug） - 燃尽快报表 / 章节标题 / 关键指标 / 变更日志 四处 74 → 104 - 74 是 9 通道拆分前的旧数；9 通道实际 = DB13+BA10+BB14+BC10+BD13 +FA11+FB13+FC11+OP4+基础设施5 = 104（工作量汇总总计 117 = 9+104+4 反证） - STATE "共 100 任务" → 燃尽 130（M0 12+Spec 5+Phase0 9+M1 104） - 新增 CHK-15：燃尽 M1 数 == M1 章节实际任务行数（防再次失配） QuantumNous#2 PRD §3 "员工账户偏好"行勾选不一致 - 5 管理角色裸 ✅ → 统一 "✅自己"（管理员只能改自己偏好） QuantumNous#3 PAGES §1 命名图例漏 AA 域码 - 补 "AA=Admin-action Audit 元审计" QuantumNous#4 STATE 未记录 5/16 改动 - 头部日期 5/15→5/16；新增 "S-003 续（2026-05-16）" session 记录 （coding-principles / 四层对齐修补 / 仓库重组） - 顺修：第三处编辑误删的 S-002 标题已还原 QuantumNous#5 /admin→/enterprise 路由迁移跨文档残留 - ARCHITECTURE §7 features 树：admin/{announcements,skills,courses} → enterprise/{announcements,skills,courses} - agent-collaboration.md §1 表 + §8 CODEOWNERS 同步 （health/dept-model-acl/system-settings 仍归 admin/ 系统域） - CODEOWNERS 加 enterprise/{announcements,skills,courses} → frontend-c 具体行 一致性 15/15 ✅ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jiutubaba
pushed a commit
to jiutubaba/fx-api
that referenced
this pull request
May 17, 2026
…ectness Backend fixes: - QuantumNous#1: doSub subscription idempotency via audit log check - QuantumNous#2: markFailed only when status=RECHARGING (prevents overwriting COMPLETED) - QuantumNous#3: ExpireTimedOutOrders checks upstream payment before expiring - QuantumNous#4: Public verify endpoint for payment result page (no auth required) - QuantumNous#5: EasyPay QueryOrder returns amount, confirmPayment handles zero amount - QuantumNous#6: WxPay notifyUrl priority: request-first, config-fallback - QuantumNous#7: EasyPay remove double URL decode in VerifyNotification - QuantumNous#8: checkPaid/cancelUpstreamPayment use order's provider instance - QuantumNous#9: Amount NaN/Inf/negative validation in order creation and refund - QuantumNous#10: Refund amount comparison uses tolerance instead of float64 == - QuantumNous#11: Skip balance deduction on retry when previous rollback failed - QuantumNous#12: checkPaid logs fulfillment errors instead of silently ignoring - QuantumNous#13: WxPay certSerial added to required config fields Frontend fixes: - Payment result page no longer requires authentication - Public verify API fallback for expired sessions
yujipeng
pushed a commit
to yujipeng/new-api
that referenced
this pull request
May 21, 2026
Round 2 sync per architect's evidence closure (TES-69 comment 87c3958d): - Rewrite 99-pending-items.md: all 12 grey-zone items closed-2026-05-21 with evidence chains + handling outcome; appendix lists 5 known improvements (audio/task gate parity, svip default, three frontend guards, RPM/TPM tooltip, quota_data cleanup) tracked by PJM separately - 03-billing.md #1: add 3.1.4 explaining text-path two gates (SelfUseMode + AcceptUnsetRatioModel) vs audio/task path no-gate asymmetry for unregistered models - 03-billing.md QuantumNous#2 (in 02): rewrite TopupGroupRatio as topup-side discount/markup multiplier, not billing-side; document formula, four payment paths, fallback 1.0 behavior - 03-billing.md QuantumNous#9: rewrite OtherRatios as active dynamic billing multiplier for task/image paths (seconds/size/n), list adapters, clarify text-path no-op semantics; remove "reserved field" wording - 01/02 QuantumNous#3 QuantumNous#4 QuantumNous#5 QuantumNous#6 QuantumNous#7: operational hints planted (group ref check, FixAbility low-peak single-instance, double-write reminder w/ note that automatic linkage check is not yet implemented, svip default workaround, ip log default-false with compliance rationale) - 05-faq QuantumNous#8 errata: actual error message is MsgDistributorTokenModelForbidden ("该 token 不允许使用模型 X"), not "token model limit is empty"; FAQ scene 4 rewritten as full troubleshooting chain - 05-faq QuantumNous#10 QuantumNous#11 QuantumNous#12: planted hints for usingGroup-only logs.group (open other.user_group / other.token_group after schema extension), RPM/TPM as 60s snapshot, quota_data cleanup via DBA - README, 5.2 summary table, 5.3 troubleshooting matrix, and inline anchors updated to match new 99-pending-items.md headings Co-authored-by: multica-agent <github@multica.ai>
Lyianu
pushed a commit
to Lyianu/new-api
that referenced
this pull request
Jul 21, 2026
语义统一（QuantumNous#5）：上游 new-api 中同一个 TopupGroupRatio 在不同通道含义 相反 —— 易支付/Waffo 只作用于收款侧（付 额度×倍率，入账足额），而 Stripe 双边乘（付款和入账都放大，倍率实际不起加价作用）。以 new-api 最老的充值路径（收款侧加价）为准收敛：GetChargedAmount 不再乘倍率， 入账恒为请求额度，getStripePayMoney 保持 gross-up(额度×倍率×折扣)。 新增回归测试锁定该语义。 报价一致（QuantumNous#6）：GetTopUpInfo 下发用户分组的 topup_group_ratio， 前端预设金额卡片的"Pay ¥X"乘上该倍率（Stripe 与易支付路径均修）， 消除倍率≠1 分组下卡片报价与确认弹窗/实际扣款不符的问题。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Merged
zer0Black
added a commit
to Agents-Zone/sili-smart-api
that referenced
this pull request
Aug 1, 2026
Co-Authored-By: Claude <noreply@anthropic.com>
Luckylos
pushed a commit
to Luckylos/new-api
that referenced
this pull request
Aug 14, 2026
Fixes "no available channel" errors where healthy channels were never tried before the request failed. Three root causes addressed: 1. Retry no longer re-selects failed channels (QuantumNous#1) GetRandomSatisfiedChannel / GetChannel now take an excludeChannels set (channel IDs already tried this request). Selection is rewritten to be exclude-driven: group non-excluded candidates by priority, pick the highest tier that still has channels, weighted-random within it. Returns (nil,nil) when the pool is exhausted so the caller stops cleanly. The relay loop populates the set after each attempt. 2. Same-priority channels are all exhausted before descending (QuantumNous#6) Previously retry was a priority index, so same-priority siblings were skipped. Now every channel in a tier is tried first. 3. 504/524 timeouts fail over instead of aborting (QuantumNous#2) Removed the hardcoded always-skip guard from the sync relay path; AutomaticRetryStatusCodeRanges is now authoritative and defaults to the full 5xx range. The async task relay keeps its own timeout protection to avoid duplicate submits. 4. Adaptive retry budget (QuantumNous#5) Retry cap = max(RetryTimes, availableChannels-1) via new CountAvailableChannels, so every channel can be tried even when RetryTimes is smaller than the pool. Pinned-channel requests stay at 1. Tests: channel_failover_test.go + updated status_code_ranges_test.go. go build + vet + all package tests pass.
9 tasks
leikaiwei
added a commit
to leikaiwei/new-api
that referenced
this pull request
Aug 19, 2026
7 tasks
Firesuiry
pushed a commit
to Firesuiry/tako-newapi
that referenced
this pull request
Aug 27, 2026
fix(catfk): refresh expired merchant sessions
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
3 participants
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.
使用MySQL时候 key搜索是关键字，图生文 图生图的指令是prompt_en，内容过长增加了弹窗显示