-
Notifications
You must be signed in to change notification settings - Fork 52
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
[BUG] - IntegrityError upon startup #852
Comments
Going by the trace it seems this originates within
but I am unsure why duplicated entries are being added (or try to) since this seems to be at configuration time |
I was looking into this issue some but was unable to reproduce it from a clean clone of the repo and running Digging into the error a bit more, I notice these lines in the debug output:
The task_update_conda_channel is defined here. This should be looking at the repodata for each configured channel and inserting any new packages into the postgres db.
This line I believe comes from the package updater. It's going to try to insert a bunch of packages, which makes sense as this is the first run and the database should be empty. Though, this seems like maybe a small amount if the
This part is the error coming from the orm package updater. There is this little piece of logic here looks like it should be stopping any situation where duplicates get inserted into the database. Looks like this in particular is failing. @peytondmurray in order to continue debugging this problem can you share:
|
This is maybe fixed by #961. Would be sweet to try it out to confirm (I'm not able to reproduce this bug specifically). You may need to reset the data in your db? |
Just tried this out after a
|
Looks like it's still trying to insert |
Sweet, thanks for the additional log output. I'm now able to consistently reproduce the issue by following the steps:
So, this issue arises because part of the environment build process is to execute the There are a couple options to resolve this:
I think (2) is the better option. edit it looks like there are some endpoints for listing packages. So, removing the functionality described in option (1) will change some user facing behaviour. This is probably not the option we want to go with. |
Yep, seems like option 2 is the way to go here, though we should be careful about the impact on performance of moving away from |
Describe the bug
Whenever I start the conda-store services with
docker compose up --build
, I get integrity errors:Even with fresh containers, this error always appears. It doesn't seem to affect anything, but getting error messages immediately upon starting up isn't helpful.
Expected behavior
No error appears.
How to Reproduce the problem?
docker compose up --build
. I'm running Linux 6.6.39-1-lts x86_64.Here's the output of
pip list
Here's the output of
python -VV
:Python 3.10.0 | packaged by conda-forge | (default, Nov 20 2021, 02:24:10) [GCC 9.4.0]
The text was updated successfully, but these errors were encountered: