Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Memory is not generated or saved #44

Open
thecookingsenpai opened this issue Aug 9, 2023 · 3 comments
Open

Memory is not generated or saved #44

thecookingsenpai opened this issue Aug 9, 2023 · 3 comments

Comments

@thecookingsenpai
Copy link

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
Copy link

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
Copy link
Author

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
Copy link

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants