feat: 支持配置渠道被禁用后是否清空渠道粘性

[GuangYiDing]

⚠️ 提交说明 / PR Notice

Important

• 请提供人工撰写的简洁摘要，避免直接粘贴未经整理的 AI 输出。

📝 变更描述 / Description

(简述：做了什么？为什么这样改能生效？请基于你对代码逻辑的理解来写，避免粘贴未经整理的内容)
支持配置渠道被禁用后是否清空渠道粘性，默认行为为 渠道被禁用后清空

🚀 变更类型 / Type of change

• 🐛 Bug 修复 (Bug fix) - 请关联对应 Issue，避免将设计取舍、理解偏差或预期不一致直接归类为 bug
• ✨ 新功能 (New feature) - 重大特性建议先通过 Issue 沟通
• ⚡ 性能优化 / 重构 (Refactor)
• 📝 文档更新 (Documentation)

🔗 关联任务 / Related Issue

• Closes # (如有)

✅ 提交前检查项 / Checklist

• 人工确认: 我已亲自整理并撰写此描述，没有直接粘贴未经处理的 AI 输出。
• 非重复提交: 我已搜索现有的 Issues 与 PRs，确认不是重复提交。
• Bug fix 说明: 若此 PR 标记为 Bug fix，我已提交或关联对应 Issue，且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。
• 变更理解: 我已理解这些更改的工作原理及可能影响。
• 范围聚焦: 本 PR 未包含任何与当前任务无关的代码改动。
• 本地验证: 已在本地运行并通过测试或手动验证，维护者可以据此复核结果。
• 安全合规: 代码中无敏感凭据，且符合项目代码规范。

📸 运行证明 / Proof of Work

(请在此粘贴截图、关键日志或测试报告，以证明变更生效)

[coderabbitai]

Walkthrough

Adds ClearCurrentChannelAffinityCache and a setting KeepOnChannelDisabled; distributor now only uses affinity when the preferred channel is enabled and clears affinity otherwise. Frontend and system settings are updated with the new option and i18n entries; unit test validates cache deletion and retry-flag reset.

Changes

Channel Affinity Cache Clearing

Layer / File(s)	Summary
Affinity service helper & test service/channel_affinity.go, service/channel_affinity_template_test.go	Adds ClearCurrentChannelAffinityCache and ShouldKeepChannelAffinityOnChannelDisabled; test TestClearCurrentChannelAffinityCache verifies cache deletion and resets the skip-retry flag.
Distributor integration middleware/distributor.go	Distributor preferred-channel logic now only uses affinity when the preferred channel is enabled; otherwise marks affinity unusable and clears the current channel-affinity cache instead of returning 403.
Backend setting additions setting/operation_setting/channel_affinity_setting.go	Adds KeepOnChannelDisabled boolean to ChannelAffinitySetting with default false.
Classic UI: settings + i18n web/classic/src/pages/Setting/Operation/SettingsChannelAffinity.jsx, web/classic/src/i18n/locales/*	Expose channel_affinity_setting.keep_on_channel_disabled in classic settings UI, hydrate options, render new switch and help text; add translation entries for multiple locales.
Default web app settings & system-settings web/default/src/features/..., web/default/src/i18n/locales/*	Add default model setting key, extend system-settings component/state/types to include keep_on_channel_disabled, persist changes on save, and add translations across locales.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• QuantumNous/new-api#2809: Related changes to channel affinity configuration defaults and settings shape.
• QuantumNous/new-api#4453: Touches the distributor preferred/disabled-channel handling and related i18n strings.
• QuantumNous/new-api#3333: Also modifies preferred-channel disabled handling and channel-affinity retry behavior.

Suggested reviewers

• seefs001

Poem

🐰 I hopped through cache and setting tree,
Cleared an affinity so services roam free,
A switch in the UI, locales sing along,
Cache wiped, retries reset — the flow moves on.

🚥 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%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately summarizes the main change: adding configuration to control whether channel affinity is cleared when a channel becomes disabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@service/channel_affinity.go`:
- Around line 654-659: The early return after cache.DeleteMany leaves
ginKeyChannelAffinitySkipRetry set and prevents retries; ensure
c.Set(ginKeyChannelAffinitySkipRetry, false) always runs even if
cache.DeleteMany returns an error by moving the reset before the error check or,
better, use a defer right after obtaining the context (so the flag is reset
unconditionally). Update the block around cache.DeleteMany (referencing
DeleteMany, ginKeyChannelAffinitySkipRetry, c.Set and shouldRetry) to guarantee
the flag is cleared on both success and error paths.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2325113e-48aa-4dd5-8e14-c11089287470

📥 Commits

Reviewing files that changed from the base of the PR and between 00d23ab and 090694e.

📒 Files selected for processing (3)

• middleware/distributor.go
• service/channel_affinity.go
• service/channel_affinity_template_test.go

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Reset retry-skip state even when cache deletion errors.

On Line 655, the early return on DeleteMany error skips resetting ginKeyChannelAffinitySkipRetry. That can keep retries disabled for this request (shouldRetry exits early when the skip flag is true), which weakens fallback resilience on transient cache failures.

💡 Suggested fix

 func ClearCurrentChannelAffinityCache(c *gin.Context) bool {
 	if c == nil {
 		return false
 	}
 	cacheKey, _, ok := getChannelAffinityContext(c)
 	if !ok || cacheKey == "" {
 		return false
 	}
 
+	// Always clear request-level skip-retry state for this request path.
+	c.Set(ginKeyChannelAffinitySkipRetry, false)
+
 	cache := getChannelAffinityCache()
 	deleted, err := cache.DeleteMany([]string{cacheKey})
 	if err != nil {
 		common.SysError(fmt.Sprintf("channel affinity cache delete current failed: err=%v", err))
 		return false
 	}
-	c.Set(ginKeyChannelAffinitySkipRetry, false)
 	for _, ok := range deleted {
 		if ok {
 			return true
 		}
 	}
 	return false
 }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@service/channel_affinity.go` around lines 654 - 659, The early return after
cache.DeleteMany leaves ginKeyChannelAffinitySkipRetry set and prevents retries;
ensure c.Set(ginKeyChannelAffinitySkipRetry, false) always runs even if
cache.DeleteMany returns an error by moving the reset before the error check or,
better, use a defer right after obtaining the context (so the flag is reset
unconditionally). Update the block around cache.DeleteMany (referencing
DeleteMany, ginKeyChannelAffinitySkipRetry, c.Set and shouldRetry) to guarantee
the flag is cleared on both success and error paths.

[seefs001]

我需要改一下，这个需要加入配置。
另外下次提交PR请遵守PR模版来。