From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 63634@debbugs.gnu.org
Subject: bug#63634: nar 404 leads to hard ‘guix substitute’ crash
Date: Mon, 22 May 2023 13:54:45 +0200 [thread overview]
Message-ID: <87mt1wy41m.fsf@gnu.org> (raw)
In-Reply-To: <87fs7ofx3v.fsf@cbaines.net> (Christopher Baines's message of "Mon, 22 May 2023 11:59:28 +0100")
Christopher Baines <mail@cbaines.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> So it seems that bordeaux.guix did advertise zstd at some point (and
>> that narinfo is still in cache) but no longer does.
>>
>> Chris, can you confirm?
>
> Yeah, this would have been a consequence of reducing the cache size [1].
>
> 1: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=ce8d3000fda6b80c0cf3e6f8204e0ee293024e6b
As discussed on IRC, I think nar-herder should honor the TTL it
advertises for all the URLs of the narinfo (lzip, zstd, etc.) because
that’s how ‘guix substitute’ currently interprets the TTL.
Eventually it would be nice for ‘guix substitute’ to interpret the TTL
as applying to one of the URLs (not necessarily all of them), but this
kind of change takes months if not years to be widely deployed because
users rarely (if ever) update guix-daemon.
Ludo’.
next prev parent reply other threads:[~2023-05-22 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 22:12 bug#63634: nar 404 leads to hard ‘guix substitute’ crash Ludovic Courtès
2023-05-22 8:00 ` Ludovic Courtès
2023-05-22 8:19 ` Simon Tournier
2023-05-22 9:36 ` Ludovic Courtès
2023-05-22 11:02 ` Christopher Baines
2023-05-22 11:51 ` Ludovic Courtès
2023-05-22 9:32 ` Ludovic Courtès
2023-05-22 10:59 ` Christopher Baines
2023-05-22 11:54 ` Ludovic Courtès [this message]
2023-05-22 15:35 ` Ludovic Courtès
2023-05-22 15:16 ` 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=87mt1wy41m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=63634@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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).