Open ygaeon opened 3 months ago
Sorry that happened to you.
I can at least confirm it for you. All the chats get loaded at the start and saved again in the end. Ideally, it should not crash in between.
That's because the user has no Save Chat Now button to click on; it's like important operations like OK/Cancel/DoSomethingNow/ForgetIt are purely ignored due to hatred for buttons, it seems, or for symbols that would act like buttons. Anyway, Escape key acts both as Cancel and OK (it should not), so there we are however one spins it.
We now save chats more eagerly than before. @cebtenzzre can we close this?
@manyoso In what version are "chats saved more eagerly"? I still use 3.4.1 and it's not saving after each generation as far as I can see .. (which would be necessary to retain chats if a crash occur mid-response-generation)
@ygaeon i misspoke. we made some changes in 3.4.x that will enable us to fix this properly in future, but the fixes haven't been made yet so reopening
Bug Report
If the UI crashes while using it, all prompts and chats generated since starting the UI are lost when the UI is restarted. This is still an issue in release 3.1.1 (Linux).
The option "Save Chat Context" doesn't help with the issue (the UI has crashed).
The crashes happens while answers are generated, never while typing prompts etc.
This has been reported in comments before but I've not seen a clear separate issue.
727 have several comments
Closest clear issue reported in #1311 but it was closed by the author without any clear instructions on how to workaround (only referencing #727).
Steps to Reproduce
Expected Behavior
@dannystaple put it perfectly in #1311: "The crash wouldn't be expected. However, also I would expect that chat sessions are retained to be continued when starting the app later."
Your Environment