fix: preserve route-bound direct thread events · openclaw/openclaw@0d8c9ca
steipete
·
2026-05-22
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -119,9 +119,13 @@ describe("event session routing", () => {
|
119 | 119 | } as unknown as OpenClawConfig; |
120 | 120 | const sessionKey = "agent:main:telegram:work:direct:123"; |
121 | 121 | const policy = resolveEventSessionRoutingPolicy({ cfg, sessionKey }); |
| 122 | +const threadSessionKey = `${sessionKey}:thread:1712345678.123`; |
| 123 | +const threadPolicy = resolveEventSessionRoutingPolicy({ cfg, sessionKey: threadSessionKey }); |
122 | 124 | |
123 | 125 | expect(policy.preserveSessionKey).toBe(true); |
124 | 126 | expect(resolveEventSessionKeyForPolicy(sessionKey, policy)).toBe(sessionKey); |
| 127 | +expect(threadPolicy.preserveSessionKey).toBe(true); |
| 128 | +expect(resolveEventSessionKeyForPolicy(threadSessionKey, threadPolicy)).toBe(threadSessionKey); |
125 | 129 | }); |
126 | 130 | |
127 | 131 | it("keeps cron-run remapping behavior unchanged", () => { |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
