mirror of
https://github.com/openclaw/openclaw.git
synced 2026-10-04 10:10:01 +00:00
test(channels): track the inlined Synology context builder call
#160639 (5ddcce60fa) inlined resolveSynologyChatInboundRoute, so the
Synology inbound event now calls rt.channel.inbound.buildContext on the
same getSynologyRuntime() handle instead of resolved.rt. The caller
inventory still expected the old text and failed build-artifacts on main
and in 2026.9.7 Full Release Validation (CI 36496123315).
Update only the expected call text; the runtime provenance is unchanged.
Proof: context-builder-callers.test.ts fails 1/6 on main before, passes
6/6 after (3 s, one worker).
This commit is contained in:
parent
7c1838a418
commit
c4845a61b4
1 changed files with 1 additions and 1 deletions
|
|
@ -96,7 +96,7 @@ const HOST_BUILDERS = [
|
|||
"ctx.buildContext ?? buildChannelInboundEventContext",
|
||||
],
|
||||
["extensions/sms/src/inbound.ts", "params.channelRuntime.inbound.buildContext"],
|
||||
["extensions/synology-chat/src/inbound-event.ts", "resolved.rt.channel.inbound.buildContext"],
|
||||
["extensions/synology-chat/src/inbound-event.ts", "rt.channel.inbound.buildContext"],
|
||||
[
|
||||
"extensions/telegram/src/bot-message-context.session.ts",
|
||||
"sessionRuntime.buildChannelInboundEventContext",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue