From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52866@debbugs.gnu.org
Subject: [bug#52866] maintenance: Add a crash dump service.
Date: Thu, 06 Jan 2022 09:22:38 +0100 [thread overview]
Message-ID: <871r1lw9wx.fsf@gnu.org> (raw)
In-Reply-To: <87v8yxj37p.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 05 Jan 2022 22:13:30 +0100")
Hey Ludo!
> I’m also unsure about the idea of having admins of Guix infrastructure
> be in a privileged position collecting that debugging info. There’d
> have to be a privacy policy in place.
Yeah I would prefer the debug info to be public as they can be useful
for any potential bug hunter.
> Or, dump.guix.gnu.org could relay everything as-is to bug-guix@gnu.org
> *if* we know users are aware of what data is being reported.
That's something that also crossed my mind, but I chose instead to make
the web-server publish the bug reports here: https://dump.guix.gnu.org.
They can then be downloaded with this URL:
https://dump.guix.gnu.org/download/<id>.
Of course the next step it to use this API in a command line tool or
so. I don't feel like working on another web interface.
Regarding the installer integration, you can have a look to:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=wip-harden-installer&id=22158d407af89d2f3df3abd8005ec2321df45c74.
There's already a window asking before uploading the crash dump. I think
that if we make the warning message even more explicit it could be fine.
WDYT?
Thanks,
Mathieu
next prev parent reply other threads:[~2022-01-06 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 9:16 [bug#52866] maintenance: Add a crash dump service Mathieu Othacehe
2021-12-29 17:37 ` zimoun
2022-01-05 21:13 ` Ludovic Courtès
2022-01-06 8:22 ` Mathieu Othacehe [this message]
2022-01-07 11:16 ` Josselin Poiret via Guix-patches via
2022-01-11 13:10 ` Ludovic Courtès
2022-02-02 16:33 ` bug#52866: " Mathieu Othacehe
2022-02-08 9:53 ` [bug#52866] " Ludovic Courtès
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=871r1lw9wx.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=52866@debbugs.gnu.org \
--cc=ludo@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).