You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Session sticky routing now records the session→account mapping on every success path (including custom providers) and logs binding invalidation, so later requests in the same session hit the same account and report stickyHit=true; the PR describes the session-key chain and how to verify it. Bindings remain in-memory and reset on restart, and since no CI runs on PRs and the change is above the auto-merge size limit, it needs a manual review and merge.
On it: rebasing agent/fix-sticky-routing-0c9e9cb8d18c onto the new main (aimod-cc#434/aimod-cc#449), resolving the provider_loop.rs / pipeline.rs / tests.rs conflicts, re-running cargo test, then force-pushing PR #4.
Activity
xiarunjie commentedon Nov 3, 2026
@xrj-dsh-agent 开始修复。注意:仓库 main 已同步到 v3.3.0-beta.6(3239d12f),请基于该版本工作;本 issue 与 #1 修改不同文件,可并行。
xrj-dsh-agent commentedon Nov 3, 2026
开始修复
routingSticky = session不生效的问题,让会话→账号映射被记录、能命中并留下失效日志。修复:会话粘性写入收成唯一出口 + 失效日志(issue #2 / 上游 aimod-cc#443)
修复:会话粘性写入收成唯一出口 + 失效日志(issue #2 / 上游 aimod-cc#443)
xrj-dsh-agent commentedon Nov 3, 2026
This is by an automated agent, not a human.
PR #4 is ready for review: #4
Session sticky routing now records the session→account mapping on every success path (including custom providers) and logs binding invalidation, so later requests in the same session hit the same account and report
stickyHit=true; the PR describes the session-key chain and how to verify it. Bindings remain in-memory and reset on restart, and since no CI runs on PRs and the change is above the auto-merge size limit, it needs a manual review and merge.xiarunjie commentedon Nov 3, 2026
@xrj-dsh-agent 注意:main 分支刚同步了上游的多个修复(aimod-cc#434/aimod-cc#449 等),与你 PR 分支修改的
provider_loop.rs、pipeline.rs、provider_loop/tests.rs产生冲突。请把你的分支变基到最新 main(git fetch origin main && git rebase origin/main,或合并 main 进你的分支),解决冲突后强推更新 PR。冲突大概率在send_with_retry新增的 images 参数与 telemetry Arc 包装处,注意 main 上现在已改为&Arc<RequestTelemetry>+ 第 7 个 images 参数 + CodeArts 走插件投影分类。改完跑一遍cargo test再推。xrj-dsh-agent commentedon Nov 3, 2026
On it: rebasing
agent/fix-sticky-routing-0c9e9cb8d18conto the new main (aimod-cc#434/aimod-cc#449), resolving theprovider_loop.rs/pipeline.rs/tests.rsconflicts, re-runningcargo test, then force-pushing PR #4.修复:会话粘性写入收成唯一出口 + 失效日志(issue #2 / 上游 aimod-cc#443)
修复:会话粘性写入收成唯一出口 + 失效日志(issue #2 / 上游 aimod-cc#443)
xrj-dsh-agent commentedon Nov 3, 2026
This is by an automated agent, not a human.
PR #4 is rebased onto the latest main with the conflicts resolved, and tests pass. It is ready for review again: #4. It still needs a manual merge.
修复:会话粘性写入收成唯一出口 + 失效日志(issue #2 / 上游 aimod-cc#443)