Skip to content

Conversation

@Tomass673
Copy link
Collaborator

@Tomass673 Tomass673 assigned Tomass673 and veliseev93 and unassigned Tomass673 Dec 10, 2025
@Tomass673
Copy link
Collaborator Author

@veliseev93 please take a look

@veliseev93
Copy link
Contributor

@Tomass673 I see the patch applied to the handleContinueResponsePress method, but what are the other changes for? As far as I understand, it should work without them.

@veliseev93 veliseev93 assigned Tomass673 and unassigned veliseev93 Dec 11, 2025
@Tomass673 Tomass673 assigned veliseev93 and unassigned Tomass673 Dec 12, 2025
@Tomass673
Copy link
Collaborator Author

@Tomass673 I see the patch applied to the handleContinueResponsePress method, but what are the other changes for? As far as I understand, it should work without them.

I left them there as is, because commit from child branch will overwrite this changes


const history = chat?.chat.history;
const isResponseGenerating = !history?.messages[history.currentId].done;
const isResponseGenerating = history?.lastAssistantMessage?.done !== true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes related to lastAssistantMessage cause a bug when switching message history. If we return to an old chat thread, the input becomes disabled.

Untitled.mov.zip

if (!modelId) return;

// mark message as not completed
patchChatQueryData(chatId, {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this change is enough to fix the original bug, why do we need the rest of the changes?

@veliseev93 veliseev93 assigned Tomass673 and unassigned veliseev93 Dec 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants