metrics/status on missing/failed libraries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Metrics for libraries that pass are great - but analysts don't get information on missing libraries. If the database is queried for libraries which have failed, could these be reported, ideally with the reason. This would help clarify if libraries just haven't been processed yet
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
No files or tests are named. Start by locating the database query and existing metrics for successfully processed libraries, then trace how missing and failed libraries are represented. Done means analysts can query those libraries and see whether processing is incomplete or failed, with the failure reason when available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100