Closed AllenDowney closed 1 week ago
@AllenDowney mmm, this is related to some new features I started adding to LlamaBot. It may be prudent to pin to an older version of LlamaBot, I think. Can you revert back to version 0.8.2 please?
Meanwhile, I'm going to introduce a few more tests related to this bug.
For context, I added functionality to automatically log messages sent (including prompts) + responses in a local database that exists in a code repository. The way this is implemented is by writing to a sqlite database locally. I may need to change the default behaviour of how we access the database, as there may be concurrent writes happening that need to be staggered.
@AllenDowney I merged in and released a new version of llamabot that I think addresses this issue. It is version 0.8.8. Could you give that a try and see whether this helps address the SQL error?
Running
llamabot docs write
on Azure, I'm getting a gigantic traceback that ends with a SQL error trying to create a table for the message_log.Here are the parts of the traceback that seem most likely to be useful.
Maybe something went wrong installing sqlite?