-
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
feat: orm passage migration #2180
Conversation
* Test cases for PassageManager * Additional mixins for File, User * Better `list` method in SQLAlchemyBase * Pydantic Passage model uses ORMBase
* Adding Messages migration
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
* Passage has a relationship with organization, not user * Fixed filtering bug for None columns in Chroma connector filtering * Removed outdated test cases for archival memory
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
* Fixed passage-file foreign key constraint * Phased out schemas/Passage
5796a06
to
51b36df
Compare
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
* Additional alembic migration * Updated test managers, passing
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
* renamed PassageModel to PassageModelLegacy * modified load_data to take agent_id * deleted passages before deleting agent_id * debugged server::test_load_data, removed extraneous AgentMixin
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
📦 Dependencies Alert:
Please review these changes carefully to ensure they are intended (cc @sarahwooders @cpacker). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work!
Please describe the purpose of this pull request.
Migrating passages to ORM, phasing out archival memory
How to test
How can we test your PR during review? What commands should we run? What outcomes should we expect?
Have you tested this PR?
Have you tested the latest commit on the PR? If so please provide outputs from your tests.
Related issues or PRs
Please link any related GitHub issues or PRs.
Is your PR over 500 lines of code?
If so, please break up your PR into multiple smaller PRs so that we can review them quickly, or provide justification for its length.
Additional context
Add any other context or screenshots about the PR here.