Marco Castelluccio

Thanks, that's good to hear!

I'd be happy to accept a PR if anybody wants to help. It sounds relatively easy to move to ESM (see https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c#how-can-i-move-my-commonjs-project-to-esm).

I'm not sure to be honest, I'm not familiar enough with ESM.

What if we simply call `setGCMAPIKey` and `setVapidDetails` with `null` as a way to reset the state?

> @sylvestre noticed that the model tends to wrongly classify bugs into the `Core::Widget: Gtk` component. Here are some examples: > > * https://bugzilla.mozilla.org/show_bug.cgi?id=1902245#c2 > > * https://bugzilla.mozilla.org/show_bug.cgi?id=1853497#c1 I bet...

Another option for improving the model is to use a ML classifier (e.g. using https://github.com/mozilla/bugbug/pull/3761) and then an ensemble of the ML classifier and the xgboost classifier.

Usually, bugs by external users (which we care about the most for the component model) are filed in the "Untriaged" component.

We'd happily accept a PR to implement this!

Thanks for the PR @jayvdb! Could you only submit your own commit so we can merge it independently?

Since master is broken too, we can still merge things that are clearly OK.