From: Ada Stevenson <adanskana@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Error handling when 'guix substitute' dies
Date: Sun, 17 Mar 2024 06:18:51 +0000 [thread overview]
Message-ID: <1843db1b-0ed0-7e77-5a31-de8ee9ca56a5@gmail.com> (raw)
Hi Guix,
I have this gripe with usability regarding using substitutes.
Sometimes, usually when I'm on an enterprise network like my
university's of library's wifi, the `guix substitute` process dies with
a "TLS error in procedure 'write_to_session_record_port': Error in the
push function" error message. My connection is rock-solid otherwise, and
sometimes it doesn't happen at all.
I'm not sure if this is a fault in the actual Guix code, or there's some
Guile library somewhere that has this bug. Anyway, I think it would be a
useful feature to have a way to automatically restart the `guix
substitute` process or otherwise recover from this error. Some sort of
`--restart=no.restarts.permitted` flag. Whenever I'm updating my system
I tend to leave and do something else, and when this happens I come back
and nothing's actually been done, and the error is transient so I don't
gain anything from seeing this message.
I workaround could potentially be wrapping `guix upgrade` and the like
in a script that keeps on restarting the commands until they exit with
0. This seems a little clunky and fragile, especially if there's an
actually fatal error, eg. my config is not valid.
What do you guys think? Would this be something that people would be
interested in? Or would it be better to try and find out why there's
these transient errors (a way more time-consuming effort, I fear). Does
anyone else have this issue?
Warmly,
Ada
next reply other threads:[~2024-03-17 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 6:18 Ada Stevenson [this message]
2024-03-17 11:45 ` Error handling when 'guix substitute' dies Ekaitz Zarraga
2024-03-24 11:15 ` Ludovic Courtès
2024-03-25 10:12 ` Ada Stevenson
2024-03-29 15:10 ` Ludovic Courtès
2024-04-02 4:13 ` Philip McGrath
2024-04-10 13:47 ` Ludovic Courtès
2024-04-10 14:37 ` Christopher Baines
2024-04-02 8:42 ` Lars Bilke
2024-04-02 8:45 ` Ada Stevenson
2024-04-10 13:49 ` Ludovic Courtès
2024-03-26 8:32 ` Lars Bilke
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 1:02 Richard Sent
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=1843db1b-0ed0-7e77-5a31-de8ee9ca56a5@gmail.com \
--to=adanskana@gmail.com \
--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 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.