-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create alembic to migrate current agents memory to new memory block #2117
Comments
hi @mattzh72 , do you have any update on this? thank you |
Could you please share the version of letta you were previously using, and also share your data if possible? We only support automated migrations for postgres (you can see details on using letta+docker here: https://docs.letta.com/server/docker) |
hi @sarahwooders , it's 0.5.4 I'm referring to the alembic migration 5987401b40ae, which deletes the column memory inside agents, where it's stored the block id of the memory of an agent. Please let me know if you need further information, thank you! |
Hi! You're using postgres right? We're looking into this issue right now. |
hi @mattzh72, correct, thanks a lot! |
Is your feature request related to a problem? Please describe.
Hi, as the title suggests, in order to not lose the current agents memory, create an alembic script to migrate the current column "memory" in agents table to the new block_agents table
Thank you!
The text was updated successfully, but these errors were encountered: