Skip to content

Route the three Core :: Machine Learning components to #smart-window-bug-triage - #6789

Open
msujaws wants to merge 1 commit into
mozilla:masterfrom
msujaws:frontend-triage-machine-learning
Open

Route the three Core :: Machine Learning components to #smart-window-bug-triage#6789
msujaws wants to merge 1 commit into
mozilla:masterfrom
msujaws:frontend-triage-machine-learning

Conversation

@msujaws

@msujaws msujaws commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Smart Window work is filed under three Core Machine Learning components the agent has no channel or trees for, so those bugs report to nobody. moz.build assigns browser/components/aiwindow/models/ to the General component while the bugs about that directory are filed under Models, so both claim it and the registry reads the identical claim as co-ownership.

Deploy before the matching bugbot change: channel_for fails closed, so the reverse order posts unattended analyses with nobody told.

…bug-triage so Smart Window bugs get triaged instead of arriving in a component the agent has no trees for

`Frontend` takes `browser/components/genai/` and `browser/components/aiwindow/ui/`,
`Models` takes `browser/components/aiwindow/models/`, and `General` takes the rest of
`browser/components/aiwindow/` plus `dom/modelcontext/`; `Models` and `General` both
declare the models directory, because `moz.build` assigns it to `General` while the bugs
about it are filed under `Models`, and the registry reads an identical claim as
co-ownership rather than a tie. All three name each other in `related`, since a chat-UI
bug filed under `Frontend` routinely localizes into `models/Chat.sys.mjs` and
`component_guidance_hook` would otherwise refuse the comment.

None of the three gets a doc link: the only `SPHINX_TREES` registration near this code is
`toolkit/components/ml/`, which is `Machine Learning: On Device` and not triaged here.
Deploy before the matching bugbot change, and confirm #smart-window-bug-triage exists and
is public first, since `channel_for` fails closed and a wrong name still lets the comment
land with nobody told. 114 tests pass, and 16 more with SOURCE_REPO pointed at a real
checkout.

@crythms crythms left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants