After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796458 - Please disable bugbot on all channels or fix it to not print bogus results
Please disable bugbot on all channels or fix it to not print bogus results
Product: sysadmin
Classification: Infrastructure
Component: IRC
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Reported: 2018-05-30 19:22 UTC by Michael Catanzaro
Modified: 2018-06-18 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Michael Catanzaro 2018-05-30 19:22:34 UTC
bugbot is no longer interesting. Could we remove it from all channels, please?

Nowadays it just posts broken links in response to gitlab-bot:

gitlab-bot: Engagement bug 32 in Social-Media-and-PR "PR and call for testing for Fractional Scaling in GNOME Shell" (comments: 1) [Opened]
bugbot: Bug was not found.
Comment 1 Edward E. 2018-05-30 21:00:27 UTC
For consideration: bugbot may not be _totally_ useless until all bugs are read-only.
For example, for a while I have been keeping one eye on #bzbot, where bugbot shows all bug status changes.
Admittedly there is not much activity after the recent migration, and I make no claim that this is actually useful.

For reference, bugbot is currently on 39 channels:

banshee, bugbot, bugs, bzbot, conduit, contacts, docs, documents, evolution, geary, gegl, gitg, gnome-br, gnome-builder, gnome-calculator, gnome-calendar, gnome-cz, gnome-flashback, gnome-it, gnome-mud, gnome-nl, gnome-todo, gnomefr, gtk+, gtksourceview, i18n, monodev, monodevelop, monogame, nautilus, newcomers, pdfmod, photos, pygtk, release-team, seahorse, sysadmin, vala, webhackers
Comment 2 Andrea Veri 2018-05-31 08:24:52 UTC
I agree with you Edward, I feel we should keep bugbot around until BZ is around for historical purposes, the best solution here would be adding ignores against GitLab bots nicknames. I've just added one for gitlab-bot, please let me know if there's more of them I should include on the list.
Comment 3 Michael Catanzaro 2018-05-31 13:07:13 UTC
The other problem is that most of the remaining use of Bugzilla links will be for other Bugzilla instances, e.g. It's always annoying when I post a Bugzilla link in #gnome-hackers and bugbot posts BS information by using the bug ID from a separate Bugzilla instance to look up some unrelated bug on GNOME Bugzilla. So I'd prefer to get rid of it anyway. Or make it ignore everything except
Comment 4 Andrea Veri 2018-05-31 14:25:02 UTC
There's a default Bugzilla instance flag we can pass on a per channel basis, we used to set that when a new channel requested bugbot in the past. Did we miss any probably? What channel are you seeing this behavior on?
Comment 5 Michael Catanzaro 2018-05-31 14:56:27 UTC
Comment 6 Andrea Veri 2018-05-31 15:01:46 UTC
bgo seems to be default on that channel already:

<av> channel #gnome-hackers supybot.plugins.Bugzilla.defaultBugzilla
<bugbot> bgo
Comment 7 Michael Catanzaro 2018-05-31 16:00:49 UTC
I don't understand what you're saying.

The problem is it takes links from unrelated Bugzilla instances, replaces the hostname with, and prints a bogus result. For example, in #gnome-hackers:

mcatanzaro	Company: Thanks for your help in!
bugbot	Bug 126907: Gnumeric, major, High, ---, jody, RESOLVED FIXED, manual recalc breaks redraw, and is not exported

I'd like it to either stop doing that, or go away, at least from #gnome-hackers and #gtk+. It's negative value.
Comment 8 Andrea Veri 2018-06-01 08:02:20 UTC
Michael, seems we misunderstood each other on this last item :)

I've CCed Teemu who should be able to land a definition in bugbot's configuration files, that way whenever the URL is mentioned bugbot will query the correct BZ instance.
Comment 9 Michael Catanzaro 2018-06-01 14:15:18 UTC
That would, of course, be an improvement.

Still, no configuration should be required to avoid it posting obviously-wrong information. Why is it following links to unknown hosts anyway? That should be fixed.
Comment 10 Andrea Veri 2018-06-01 14:25:44 UTC

if a specific BZ instance is not defined, bugbot fallbacks to the GNOME's one as per By landing the webkit URL on the configuration the problem will get fixed automatically.
Comment 11 Michael Catanzaro 2018-06-01 14:51:18 UTC
(In reply to Andrea Veri from comment #10)
> Michael,
> if a specific BZ instance is not defined, bugbot fallbacks to the GNOME's
> one as per

Yes, but I complain because that's broken and makes no sense. Why would that ever be desirable? Bugbot already knows the link is not a link to GNOME Bugzilla, it knows it is not a GNOME bug, so why form a bogus link and treat it as such?
Comment 12 Michael Catanzaro 2018-06-17 15:34:23 UTC
bugbot is still a problem in #gtk+, at least.
Comment 13 Michael Catanzaro 2018-06-17 17:36:13 UTC
(In reply to Michael Catanzaro from comment #12)
> bugbot is still a problem in #gtk+, at least.

Actually, it followed a link I posted to WebKit Bugzilla... so I suppose that was the right thing to do. I just didn't notice because I'm so used to ignoring bugbot. :P
Comment 14 Andrea Veri 2018-06-18 09:55:13 UTC
Also asked gitlab-bot's maintainer to drop the 'bug' word from the bot's output and rename it to issue to avoid bugbot and gitlab-bot to get in conflict. Thanks!