Prod::Comp - Fallback on main component when confidence is spread over the subcomponents
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
For example:
https://bugzilla.mozilla.org/show_bug.cgi?id=1732466
is stuck in Firefox::Untriaged because the max confidence is 20% for Core::Audio/Video: cubeb and very likely other confidences are spread over Core::Audio/Video: XXX.
In this case we should fallback on Core::Audio/Video.
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 by tracing the component-confidence handling described in the issue and compare it with the linked Bugzilla example. Done means cases whose confidence is distributed across subcomponents fall back to their main component, such as Core::Audio/Video, instead of remaining in a subcomponent queue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100