Closed PaulinDeuxTrois closed 4 months ago
@PaulinDeuxTrois the --no-experimental-fetch for node is on the frontend, while migrations are managed exclusively by the backend, so I guess there is no link between the flag and your problem. Here are a few questions:
@eric-intuitem I have 1.2.3 version but i'll try with the latest today. When i launch docker-compose. sh i always use docker compose down + docker system prune -a + rm db/ciso-assistant.sqlite3
Well, I tried with 1.3.5 and its the same errors
@PaulinDeuxTrois can you reach us on our discord or by mail at contact@intuitem.com so that we can organise a session to understand your specific situation?
ok this is very likely related to race condition @eric-intuitem that we've talked about over the weekend; since @PaulinDeuxTrois is using the standard compose, we can slow things down on the startup file
Describe the bug When i start the script docker-deploy.sh, migrations can't be completed because either " UNIQUE constraint failed: core_storedlibrary.urn, core_storedlibrary.locale, core_storedlibrary.version" or "django.db.utils.OperationalError: no such table: core_securityfunction"
To Reproduce Steps to reproduce the behavior: Execute ./docker-compose.sh
Expected behavior Migrations used to be ok but i ended up with a 500 internal error due to fetch failed because of experimental fetch. I added --no-experimental-fetch to node start and migrations started to fail. (I tried to remove the flag but it still were failing) Screenshots
OR