wangxuming/NianToB
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(chat): prevent aborted runs from reactivating conversation state (#916)

Browse Source
This commit is contained in:
paisley
2026-04-25 15:09:14 +08:00
committed by GitHub
parent 89dd765fd6
commit 9a360eb43f
4 changed files with 109 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/pages/Chat/index.tsx
View File

@@ -82,6 +82,7 @@ export function Chat() {
const streamingMessage = useChatStore((s) => s.streamingMessage);
const streamingTools = useChatStore((s) => s.streamingTools);
const pendingFinal = useChatStore((s) => s.pendingFinal);
const activeRunId = useChatStore((s) => s.activeRunId);
const sendMessage = useChatStore((s) => s.sendMessage);
const abortRun = useChatStore((s) => s.abortRun);
const clearError = useChatStore((s) => s.clearError);
@@ -280,8 +281,12 @@ export function Chat() {
);
});
const runStillExecutingTools = hasToolActivity && !hasFinalReply;
// runStillExecutingTools bridges the brief gap between tool rounds when
// Gateway temporarily clears sending. However, after an explicit abort
// (which clears activeRunId), we must NOT keep the run "open" — so we
// gate it on activeRunId being present.
const isLatestOpenRun = nextUserIndex === -1
&& (sending || pendingFinal || hasAnyStreamContent || runStillExecutingTools);
&& (sending || pendingFinal || hasAnyStreamContent || (runStillExecutingTools && !!activeRunId));
const replyIndexOffset = findReplyMessageIndex(segmentMessages, isLatestOpenRun);
const replyIndex = replyIndexOffset === -1 ? null : idx + 1 + replyIndexOffset;