Got duplicate entry (didn't check if any other)

datalad / datalad-usage-dashboard

Dashboard of detected usages of DataLad

MIT License

4 stars 2 forks source link

Got duplicate entry (didn't check if any other) #37

Closed yarikoptic closed 9 months ago

yarikoptic commented 9 months ago

https://github.com/datalad/datalad-usage-dashboard/blob/5191f339b55e50db16bab17f9b08a24da1b6afe5/READMEs/cryo-data.md has

1 cryo-data/cryo-data 1 ✔️
2 cryo-data/cryo-data 1 ✔️

which shouldn't happen AFAIK

jwodder commented 9 months ago

@yarikoptic That repository is listed twice in datalad-repos.json with two different IDs. I'm guessing that the repository was created, the script found it, the repository was deleted & recreated between runs of the script, and then the script found the new repository, but the old one wasn't marked as "gone" because a repository with the given name existed.

yarikoptic commented 9 months ago

Thanks for the analysis! I think we should just then let RiP (delete record, not to move into Gone) those (IDs) for which there is a new (larger ID?) repo under that name.