Ingester: reject checkouts without commit_hash
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Even though all checkouts should have a commit hash by default, it is still possible for maintainers to submit such results, and the database allows this case. The commit_hash is a very important field since it is used for accessing the treeDetails page and also navigating between commits, it should be enforced to be not null and wrong data should be rejected.
Comes from a [comment](https://github.com/kernelci/dashboard/issues/1436#issuecomment-3265900088) on another issue, but was born from wanting group builds and tests with some key fields (https://github.com/kernelci/dashboard/issues/1454)
Contributor guide
Research direction
Start by tracing the Ingester checkout submission path and the database schema for commit_hash, then inspect existing validation and tests around checkout results. Done means submissions without commit_hash are rejected and the database no longer permits null values for this field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100