Update conda-package-build causes an integrity error on conda_package_build table #961
+438
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related to #852
Description
Previously, whenever the packages for a channel would get updated, duplicated packages across channels would cause an sql error.
The root of the issue was that
conda_package_builds
were not getting the correct package/channel reference. For example, see the state of the db after a package update was run. In particular, thepackage_id
with differentchannel_id
's. This is incorrect, thechannel_id
should match the package's channel id. So, for thepackage_id
5618, that should bechannel_id
1.Pull request checklist