question about where to file bug reports

136 views
Skip to first unread message

miccs

unread,
Oct 3, 2022, 9:19:29 AM10/3/22
to Chrome Updates Development
hello
as the title says i want to ask where should i file bugs against the updater?

but how do i file new one? that normal bug reporting 'tool' found here: 
doesnt let me choose in any way that i want to file it against the updater component itself rather than the browser not working.

am i missing something?

Joshua Pawlicki

unread,
Oct 3, 2022, 9:32:11 AM10/3/22
to miccs, Chrome Updates Development
If you note somewhere in the bug report that it ought to be triaged to Internals>Updater, it should find its way through Chromium's regular bug triage process.

You can also post here, linking to the bug, to bring it to our attention earlier.

Either way, thanks for reporting!

--
You received this message because you are subscribed to the Google Groups "Chrome Updates Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-updates-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-updates-dev/68d61989-9865-4b3b-99bd-ca002e328847n%40chromium.org.

miccs

unread,
Oct 4, 2022, 8:59:34 AM10/4/22
to Chrome Updates Development, waf...@chromium.org, Chrome Updates Development
i did as you told. here is the link: https://bugs.chromium.org/p/chromium/issues/detail?id=1370538

however maybe its worth to 'do smth' about a more 'reliable' way for users to interact with this project than posting it here on the groups.
as for posting to chrome bugs alone - ea thats a possibility - but theres a ton of bug reports there - would be nice to be possible to post it somehow to the 'updater' component.

it was ok in the omaha3 times (i mean github - there were pull-requests / bug reports) - but since omaha4 is a chromium component i guess thats not an option anymore.

well i dunno - just a suggestion from me.
thanks

Joshua Pawlicki

unread,
Oct 4, 2022, 9:09:46 AM10/4/22
to miccs, Chrome Updates Development
Thanks, confirming we've got the bug.

Yes, I agree that it would be nice to have something that more reliably goes directly to the updater component. I wonder if it's possible to get some options added to the bug wizard for that. I'll investigate.
Reply all
Reply to author
Forward
0 new messages