Skip to content

Conversation

allozaur
Copy link
Collaborator

Close #16133

Introduces granular loading state management for individual conversations, allowing concurrent message processing which prevents UI lockup and improves user experience when multiple conversations are active.

@ggerganov
Copy link
Member

Would it be possible to push the new index?

@allozaur
Copy link
Collaborator Author

@ggerganov here you go (17e80c5) 😉

@ggerganov
Copy link
Member

Noticed 2 issues:

  • The "regenerate" button stops working after I switch to another conv
  • The displayed stats do not correspond to the selected conv while another conv is being generated

@ServeurpersoCom
Copy link
Collaborator

LLama-Svelte-Parallel-4-AVC500Kbps.mp4

@allozaur
Copy link
Collaborator Author

Noticed 2 issues:

* The "regenerate" button stops working after I switch to another conv

* The displayed stats do not correspond to the selected conv while another conv is being generated

Yep. Will fix these

@ggerganov
Copy link
Member

I have a small feature request about this feature if possible:

The list of conversation on the left should have some indicator about which conversations are currently being generated.

@allozaur
Copy link
Collaborator Author

I have a small feature request about this feature if possible:

The list of conversation on the left should have some indicator about which conversations are currently being generated.

Ah, of course, that's a very reasonable request :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Misc. bug: The model can no more continue answering while switching to another message (for example, to read it).
3 participants