github/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-09 22:34:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: don't consume replyPlan reference eagerly for streaming check

Browse Source 
The streaming check was calling replyPlan.nextThreadTs() at setup time
to determine if a thread_ts existed, which consumed the first reference
before the deliver callback ran. Use incomingThreadTs/statusThreadTs
directly for the streaming eligibility check instead.
This commit is contained in:
nathandenherder
2026-02-05 19:03:26 -05:00
parent 06efbd231f
commit 878a13d215
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/slack/monitor/message-handler/dispatch.ts
View File

@@ -138,11 +138,13 @@ export async function dispatchPreparedSlackMessage(prepared: PreparedSlackMessag
// Slack native text streaming state // Slack native text streaming state
// ----------------------------------------------------------------------- // -----------------------------------------------------------------------
const streamingEnabled = account.config.streaming === true; const streamingEnabled = account.config.streaming === true;
const replyThreadTs = replyPlan.nextThreadTs();
// Peek at the thread target without consuming it (for streaming check only).
const streamThreadHint = incomingThreadTs ?? statusThreadTs;
const useStreaming = shouldUseStreaming({ const useStreaming = shouldUseStreaming({
streamingEnabled, streamingEnabled,
threadTs: replyThreadTs ?? incomingThreadTs ?? statusThreadTs, threadTs: streamThreadHint,
}); });
let streamSession: SlackStreamSession | null = null; let streamSession: SlackStreamSession | null = null;