Problem writing to the cache

[Art-S-D]

Describe the bug

Since v1.8.0 conversations are not saved and I get an error message saying there was a problem writing to the cache.

Setup

Please complete the following information along with version numbers, if applicable.

• OS: macOs
• Shell: zsh
• Terminal Emulator: alacritty
• Terminal Multiplexer: none
• Model: gemini-2.0-flash

[quidnu]

The problem seems to be Gemini specific. If title is not specified explicitly it is constructed from the last prompt. This is done by retrieving the messages from the API provider (through the Messages generic function). However Gemini does not support that functionality as noted in google.go:Messages and returns nil instead. This causes title to be empty and to violate the database check constraint.

[TPhakisi]

The problem seems to be Gemini specific. If title is not specified explicitly it is constructed from the last prompt. This is done by retrieving the messages from the API provider (through the Messages generic function). However Gemini does not support that functionality as noted in google.go:Messages and returns nil instead. This causes title to be empty and to violate the database check constraint.

@quidnu My issue is worse, I can't even run any prompt at all. And looking at everyone else who submitted issues, they are getting the same problem:

mods "test"

ERROR Could not open database.

could not ping db: unable to open database file: out of memory (14): Unable to open the database file (SQLITE_CANTOPEN)

[Art-S-D]

@quidnu That looks like it, I tried re running my example with a title set manually and it worked

[TPhakisi]

@Art-S-D Try using "mods -l" and scroll to that same conversation and use 'mods -c conversation code "prompt" ' and please let me know if it continues the conversation. Mine fails to recall the conversation

[Art-S-D]

@TPhakisi Nope, the conversation isn's saved so I can't even get the conversation id

[TPhakisi]

@caarlos0 hey Carlos, it seems this cache issue is still persistent