Name and Version
I see two index db databases
llamacppwebui (~500mb of messages!)
llamaui (has all conversations, none of the messages)
My best guess is that some point between (current latest) 9518 7c158fb and the build I was on the conversion code was added - it flipped out somehow and didn't copy messages over. Conversations show, messages do not appear.
Unfortunately I don't have an error output After seeing chats missing my first instinct was to do a browser refresh - and a delete of the new indexdb does not trigger the import code again, so I just got an empty history after that.
Workaround:
Using IDB manager on firefox - extension - I was able to backup both indexed db's - deleting the new db entirely - refreshing llama cpp to rebuild it from scratch, then manually changing the idb file to reflect Llamacpp as the db name brought the chats back.
Operating systems
Linux
Which llama.cpp modules do you know to be affected?
llama-server
Command line
Problem description & steps to reproduce
I don't know how to reproduce - I don't know what version I was on before upgrading or what in my messages would have caused this issue - I should have updated ~gemma 4 release time and then updated again recently.
Problem description is in the main comment - brief: conversations converted over to new indexdb, messages were not. Indexdb conversion to new name failed.
First Bad Commit
No response
Relevant log output
No response
Name and Version
I see two index db databases
llamacppwebui (~500mb of messages!)
llamaui (has all conversations, none of the messages)
My best guess is that some point between (current latest) 9518 7c158fb and the build I was on the conversion code was added - it flipped out somehow and didn't copy messages over. Conversations show, messages do not appear.
Unfortunately I don't have an error output After seeing chats missing my first instinct was to do a browser refresh - and a delete of the new indexdb does not trigger the import code again, so I just got an empty history after that.
Workaround:
Using IDB manager on firefox - extension - I was able to backup both indexed db's - deleting the new db entirely - refreshing llama cpp to rebuild it from scratch, then manually changing the idb file to reflect Llamacpp as the db name brought the chats back.
Operating systems
Linux
Which llama.cpp modules do you know to be affected?
llama-server
Command line
Problem description & steps to reproduce
I don't know how to reproduce - I don't know what version I was on before upgrading or what in my messages would have caused this issue - I should have updated ~gemma 4 release time and then updated again recently.
Problem description is in the main comment - brief: conversations converted over to new indexdb, messages were not. Indexdb conversion to new name failed.
First Bad Commit
No response
Relevant log output
No response