Bug: duplicate versions/tags of components exist in the data #123
Comments
JakeChampion
added
bug
notlee
added a commit
that referenced
this issue
Apr 20, 2021
This will delete 621 duplicates across 217 versions, plus releases made today. Some duplicates are caused by a fixed ingestion error: #321 Others due to multiple tags of the same version (not fixed, with automated tagging this is less likely to happen, and we may decommission repo data): #123 Rollback plan: restore from manual backup. I created a manual backup this morning which we can restore from (see heroku > resources).
notlee
added a commit
that referenced
this issue
Apr 20, 2021
This will delete 621 duplicates across 217 versions, plus releases made today. Some duplicates are caused by a fixed ingestion error: #321 Others due to multiple tags of the same version (not fixed, with automated tagging this is less likely to happen, and we may decommission repo data): #123 Rollback plan: restore from manual backup. I created a manual backup this morning which we can restore from (see heroku > resources).
|
We're deleting duplicate records but should keep this issue open as the problems outlined here still exist. We haven't prioritised a fix as this particular issue is less likely to happen now components have an automatic tag and release workflow, based on Github labels, and we're chatting about possibly decommissioning repo data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think component versions are being duplicated because of a bug in the ingestion model saving --
origami-repo-data/models/ingestion.js
Line 87 in b6894aa
I also think that component authors sometimes delete a tag and then recreate the same tag, which causes origmai-repo-data to reingest. Perhaps origami-repo-data should listen to delete tag events and remove the tag/version from it's data?
Also, component authors tag sometimes with a
vand then again withoutv(v13.0.0,13.0.0), which seems to cause duplications to appear in the data.The text was updated successfully, but these errors were encountered: