Skip to content

[Bug] 会话粘性 routingSticky 完全不生效:stickyHit 恒为 false,会话映射从未记录(上游 #443) #2

Open

Description

@xiarunjie

@xrj-dsh-agent 请修复这个 bug。

上游 issue: aimod-cc#443(完整复现细节与全部受控实验可用 gh api repos/aimod-cc/Agent2API/issues/443 读取,本仓库是其 fork,版本同为 v3.0.8)

现象

  • 路由配置 routingStrategy = rotate + routingSticky = session(6h)时,同一会话的连续请求在多个账号间逐次乒乓,requests 表 route JSON 里 stickyHit 全部为 false(上游 655 条请求 0 次命中)。
  • 把策略切到 order(本就会固定选同一账号),结果账号一致但 stickyHit 仍全为 false —— 说明会话→账号映射从未被记录或从未被查询(写入/查找至少一侧是死代码),不是"匹配条件不对"。
  • logs 表没有任何粘性失效(account-switch / identity-changed / evicted-*)记录。

本仓库已确认的相关文件

  • desktop-tauri/src-tauri/server/src/server/core/upstream/rotate.rs(rotate 策略与粘性逻辑)
  • desktop-tauri/src-tauri/server/src/server/request_stats/record.rs(route JSON 记录,含 stickyHit 字段)
  • desktop-tauri/src-tauri/server/src/server/config/types.rs 与 config/mod.rs(routingSticky 配置)
  • desktop-tauri/src-tauri/server/src/server/db/schema.rs(会话映射存储相关表)

修复要求

  1. 让 routingSticky = session 真正生效:会话→账号映射被记录、后续请求能命中(stickyHit=true),并在映射失效时留下对应 log 记录;
  2. 顺带排查二进制里出现过的候选会话键(ah-thread-idx / opencode-session / x-session-idx / session-affinity / prompt_cache_key / codex-turn-metadata 等)哪些在写入或查找侧被遗漏,修复键的提取逻辑;
  3. 不改变 order / rotate 策略本身的选择行为;
  4. PR 描述说明:选用的会话键、写入与查找路径、以及如何验证粘性命中(可参照上游 issue 的受控实验方法)。

Activity

  1. xiarunjie commented on Nov 3, 2026

    @xiarunjie
    OwnerAuthor

    @xrj-dsh-agent 开始修复。注意:仓库 main 已同步到 v3.3.0-beta.6(3239d12f),请基于该版本工作;本 issue 与 #1 修改不同文件,可并行。

  2. xrj-dsh-agent commented on Nov 3, 2026

    @xrj-dsh-agent
    Collaborator

    开始修复 routingSticky = session 不生效的问题,让会话→账号映射被记录、能命中并留下失效日志。

  3. xrj-dsh-agent commented on Nov 3, 2026

    @xrj-dsh-agent
    Collaborator

    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.

  4. xiarunjie commented on Nov 3, 2026

    @xiarunjie
    OwnerAuthor

    @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 再推。

  5. xrj-dsh-agent commented on Nov 3, 2026

    @xrj-dsh-agent
    Collaborator

    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.

  6. xrj-dsh-agent commented on Nov 3, 2026

    @xrj-dsh-agent
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions