From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: "Mathieu Othacehe" <othacehe@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 52866@debbugs.gnu.org
Subject: [bug#52866] maintenance: Add a crash dump service.
Date: Fri, 07 Jan 2022 12:16:36 +0100 [thread overview]
Message-ID: <87sftzdcdn.fsf@jpoiret.xyz> (raw)
In-Reply-To: <871r1lw9wx.fsf@gnu.org>
Hello Mathieu and Ludovic,
Mathieu Othacehe <othacehe@gnu.org> writes:
> 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?
While looking at the code for the crash dump page in the installer, I
didn't see any special handling of user and root passwords. I've just
tested it at https://dump.guix.gnu.org/download/installer-dump-c9deb88f,
and you can see that the passwords end up in the results at the end
(both are `TEST` in capitals in my case). I think this might require
more thought. I'm not sure we have to include the result alist in the
dump report, as the installer log should provide enough information in
the case of a failure.
Concerning Ludo's objection to syslog being in the dump, this was one of
the reasons behind the new logging facilities at [1], which provide a
clean installer-only log file. We could add some checkboxes to choose
which files to include, eg:
[X] Installer log
[ ] Syslog
[ ] Dmesg
Along with an option to view them in a pager.
WDYT?
[1] https://issues.guix.gnu.org/53063
Josselin Poiret
next prev parent reply other threads:[~2022-01-07 12:46 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
2022-01-07 11:16 ` Josselin Poiret via Guix-patches via [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sftzdcdn.fsf@jpoiret.xyz \
--to=guix-patches@gnu.org \
--cc=52866@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.