search

wawawario2 / long_term_memory

A gradio web UI for running Large Language Models like GPT-J 6B, OPT, GALACTICA, LLaMA, and Pygmalion.
GNU Affero General Public License v3.0
307 stars 15 forks source link

Memory is not generated or saved #44

Open thecookingsenpai opened 1 year ago

thecookingsenpai commented 1 year ago

After installing and following the procedure, i can't see any output in the console pointing to the memory system and the user data folder is still empty, on a macboox max with macOS 17 and python 3.10

mindrages commented 1 year ago

I have the same issue both under Win11 and WSL2 (Ubuntu).

Requirements are all installed properly under the correct environment. 'python -m pytest -v extensions/long_term_memory/' returns 'passed' for all tests. The extension seems to load properly when starting the WebUI, including working buttons in gradio. It just won't create a new db, or read/write from an old, copied over one.

I am a big fan of this extension and it was working perfectly for me after it received its last update about 3 months ago, until recently. Unfortunately I am not quite sure which Oobabooga update presumably introduced a breaking change.

After having messed (literally, and amateurishly) with the code for a while I actually got it to run (create and actually write to the db) with the latest Oobabooga Version, but messed up right after and couldn't recreate what I had done to get there...

thecookingsenpai commented 1 year ago

I have the same issue both under Win11 and WSL2 (Ubuntu).

Requirements are all installed properly under the correct environment. 'python -m pytest -v extensions/long_term_memory/' returns 'passed' for all tests. The extension seems to load properly when starting the WebUI, including working buttons in gradio. It just won't create a new db, or read/write from an old, copied over one.

I am a big fan of this extension and it was working perfectly for me after it received its last update about 3 months ago, until recently. Unfortunately I am not quite sure which Oobabooga update presumably introduced a breaking change.

After having messed (literally, and amateurishly) with the code for a while I actually got it to run (create and actually write to the db) with the latest Oobabooga Version, but messed up right after and couldn't recreate what I had done to get there...

I manage the creation of the db too, but it seems nothing happens anyway : (

mindrages commented 1 year ago

I found that long_term_memory is conflicting with the only other extension I used: 'dynamic_context', presumably because both can inject strings into the context. Whichever one of the two is loaded last (through --extensions dynamic_context long_term_memory) will not work.