ChatMessageList: do not remove the connection button on error - tradeoff: less removal on 404, but not removal on network error

This commit is contained in:
Enrico Ros
2026-04-22 17:40:04 -07:00
parent 44d05181f4
commit 1e70a59ad6
+5 -4
View File
@@ -149,10 +149,11 @@ export function ChatMessageList(props: {
// Manual reattach is one-shot: on failure (e.g. upstream 404 from expired or already-consumed handle),
// drop the upstreamHandle so the Resume button doesn't keep luring the user into the same error.
// On 'aborted' we keep it so the user can try again later; on 'completed' the reassembler already cleared it.
if (result.outcome === 'failed' && result.generator?.upstreamHandle)
conversationHandler.messageEdit(messageId, {
generator: { ...result.generator, upstreamHandle: undefined },
}, false /* messageComplete */, true /* touch */);
// 2026-04-22: disabled; it was removing the connect button on a connection error (e.g. wifi drop)
// if (result.outcome === 'failed' && result.generator?.upstreamHandle)
// conversationHandler.messageEdit(messageId, {
// generator: { ...result.generator, upstreamHandle: undefined },
// }, false /* messageComplete */, true /* touch */);
}, [conversationHandler, conversationId]);