From: Ian Eure <ian@retrospec.tv>
To: guix-devel <guix-devel@gnu.org>
Subject: Reducing "You found a bug" reports
Date: Sat, 08 Jun 2024 20:04:44 -0700 [thread overview]
Message-ID: <87frtmu7ov.fsf@meson> (raw)
There’s a steady number of bug reports generated by the "You found
a bug" message which happens during `guix pull's. The
overwhelming majority of these reports are caused by networking
problems or the Guix infrastructure being unreliable or
overloaded. Many of these were submitted during the recent
guix.gnu.org downtime.
Some of these that I see:
55066
62023
62830
61520
58309
...I’m sure there are many more.
Is there some way for this code to be smarter about when it prints
the "report a bug" message, so it doesn’t tell users to report
bugs when none exist? Is there a way for it to notice that the
problem is related to networking, and tell the users to try again
in a little while? Is it worth removing the "report a bug"
message entirely?
It doesn’t feel great to tell users to report a bug for things
that aren’t bugs. They’re either closed, or never followed up on;
it’s a poor experience on both ends.
Thanks,
— Ian
next reply other threads:[~2024-06-09 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 3:04 Ian Eure [this message]
2024-06-17 12:59 ` Reducing "You found a bug" reports Ludovic Courtès
2024-06-17 16:09 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-17 20:40 ` Ricardo Wurmus
2024-07-22 20:48 ` Attila Lendvai
2024-07-17 18:24 ` Simon Tournier
2024-07-21 13:16 ` Ludovic Courtès
2024-07-22 11:30 ` Simon Tournier
2024-07-22 17:43 ` Suhail Singh
2024-09-10 14:51 ` toward a plan? (was Re: Reducing "You found a bug" reports) Simon Tournier
2024-09-11 0:20 ` Suhail Singh
-- strict thread matches above, loose matches on Subject: below --
2024-07-23 20:45 Reducing "You found a bug" reports chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frtmu7ov.fsf@meson \
--to=ian@retrospec.tv \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).