-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
docker compose failing at pip install due to missing dependencies #3314
Comments
It could be solved in two ways:
|
Thanks for reporting this and performing some preliminary analysis, @dikwickley @kgodey I've assigned this to you since I figure you would be the best person to make the decisions required to fix this. I've not yet attempted to reproduce this, but assuming it is reproducible, this looks to be a high-priority issue since it has the potential to affect the workflow of all devs. |
We are no longer using |
@kgodey sure! |
Great thanks, I've assigned it to you! |
@kgodey i removed the package from requirement.txt and it installed fine. Next I ran tests for backend and here are few which failed
You did say that we are no longer using
Which is ultimately used in mathesar/db/records/operations/select.py Lines 21 to 52 in 08743e6
Till we are using the apply_transformations_deprecated i don't think we should get rid of |
Ugh, I did not know we were still using it in one place, thanks for finding this @dikwickley. @mathemancer or @Anish9901, is this usage of the package easy to remove? Otherwise, I'll move the |
The package should be easy to remove @kgodey, mathesar/db/records/operations/relevance.py Lines 21 to 24 in cf92053
|
Description
When running
docker compose -f docker-compose.yml -f docker-compose.dev.yml up dev-service
It is failing because in the requirements .txt there is :
mathesar/requirements.txt
Line 26 in 08743e6
and there does not exist any https://github.com/mathesar-foundation/sqlalchemy-filters
(there is though https://github.com/centerofci-archive/sqlalchemy-filters)
This is probably because of recent changes to the org name.
Expected behavior
Dependencies should be resolved with no issue.
To Reproduce
Clone a fresh repo or even try to rebuild the image by
docker compose -f docker-compose.yml -f docker-compose.dev.yml up dev-service --force-recreate --build dev-service
Environment
Additional context
The text was updated successfully, but these errors were encountered: