dosubot[bot]
commented
6 months ago Hey @shyamshyre, long time no see! Back at it with another brain-teaser, I see. Hope you've been well amidst all these digital conundrums.
Based on the information you've provided, it seems like the issue you're encountering is related to the database schema. The error messages suggest that the application is trying to access tables or relations in the database that do not exist. This could be due to a few reasons:
-
The database has not been correctly initialized with the required schema. Ensure that all necessary migrations or schema setups have been applied. You can check the supabase/seed.sql file in the Quivr repository for the initial database setup.
-
The application is pointing to the wrong database or schema. Check the application's database connection configuration to ensure it's targeting the correct database and schema.
-
There might be a version mismatch between the application code and the database schema. Ensure that both the application and the database schema are up to date and compatible with each other.
To resolve the HTTP error codes you're encountering, you can follow these steps:
-
HTTP/1.1 404 Not Found: Double-check the URLs you are using in your API calls against the API documentation. Ensure that any dynamic segments of the URL (like IDs) are correctly populated.
-
HTTP/1.1 400 Bad Request: Review the payload of your requests, especially when creating or updating resources (like brains or prompts), to ensure they match the expected format and data types defined in the API documentation. Also, validate that all required fields are included.
-
500 Internal Server Error: Check if you're sending requests that the server might not handle correctly (e.g., passing invalid data that causes an error in the server's processing logic). If the issue persists, consider contacting the API provider for support.
For the postgrest.exceptions.APIError exceptions, it suggests that the database schema expected by the API does not match the actual database schema. You can check the backend/models/sqlalchemy_repository.py file in the Quivr repository for the expected database schema.
If the issue persists after trying these steps, it would be helpful to provide more details about your setup and any changes you've made to the codebase. This could include information about your development environment, the exact steps you took to set up the project, any modifications you made to the code or configuration, and the full error messages and stack traces you're seeing. This additional context can help identify potential causes of the issue that might not be immediately apparent.
Sources
- [Bug]: Can't Create Brain
- frontend/lib/context/BrainProvider/hooks/useBrainProvider.ts
- backend/models/sqlalchemy_repository.py
StanGirard
shyamshyre
zulfaiflakhul
powderblock
github-actions[bot]
What happened?
Post setup, unable to create brain. Following is the logtrace below. Made numerous attempt's this looks to like an database issue. Tried updating to latest , deleted images , docker volumes freshly downloaded everything from start still the issue prevails.
Relevant log output
Twitter / LinkedIn details
No response