You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-running the same command with no other changes seems to fix the issue. See this issue for context.
In my testing I was able to reproduce this error, also on my first run. Then on a second run of the command it worked without error. Before starting the test I ran docker system prune -f --all --volumes to be sure I was starting fresh.
After the initial test I pruned the system and tried again. This time fides push demo_resources/ worked on the first try without error.
Sometimes this step will error, and sometimes it will work.
Expected behavior
Command should run without error.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Version:
OS:
Python Version:
Docker Version:
Additional context
The error {'detail': {'error': 'a database query failed'}} provides enough to know it is an issue interacting with the database, but doesn't contain enough to know what the problem is.
The text was updated successfully, but these errors were encountered:
Bug Description
Sometimes when running
fides push demo_resources/
it will fail with an error.Re-running the same command with no other changes seems to fix the issue. See this issue for context.
In my testing I was able to reproduce this error, also on my first run. Then on a second run of the command it worked without error. Before starting the test I ran
docker system prune -f --all --volumes
to be sure I was starting fresh.After the initial test I pruned the system and tried again. This time
fides push demo_resources/
worked on the first try without error.Steps to Reproduce
Expected behavior
Command should run without error.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
The error
{'detail': {'error': 'a database query failed'}}
provides enough to know it is an issue interacting with the database, but doesn't contain enough to know what the problem is.The text was updated successfully, but these errors were encountered: