Collectri Download is Unpredictable via Zenodo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 294
- Forks
- 38
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 3
Description
Report
See:
https://github.com/scverse/liana/actions/runs/34322201595/job/102371160845
Is it possible to move the databases under some github release, lamin, or AW3 @PauBadiaM
This has been quite stable for metalinks (and is versioned):
https://github.com/scverse/liana/blob/d4211373692e7b9c10210488ccb1efe06452b097/src/liana/resource/get_metalinks.py#L10
Versions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked GitHub Actions job to reproduce or inspect the unpredictable Collectri download, then trace the database download entry point in the decoupler repository. Compare it with the versioned metalink handling shown in src/liana/resource/get_metalinks.py; done means the databases are hosted through a stable, versioned source and the workflow completes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100