Retry insertion errors on ingester
Open
Nobody has claimed this yet.
Backend
Database
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
The ingester is one of the most important tool, and with upcoming changes some unexpected errors could happen. Even still, we are currently simply not dealing with insertion errors (cf kcidbng_ingester L384) and this should be addressed.
Contributor guide
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 backend/kernelCI_app/management/commands/helpers/kcidbng_ingester.py around line 384 and trace how insertion errors are currently handled. Determine which insertion failures should be retried and what the expected retry behavior is; the work is done when those errors are no longer simply left unhandled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100