Subject: Re: bug#52577: ‘guix lint’throws an ugly backtrace if the GitHub updater receives“rate limit exceeded” error

From: Maxime Devos <[email-masked]>
Date: Fri, 17 Dec 2021 16:29:35 +0000

Xinglu Chen schreef op vr 17-12-2021 om 15:03 [+0100]:
> (guard (c ((and (http-get-error? c)
>                 (string=? "rate limit exceeded"
>                           (http-get-error-reason c)))
>            (warning (G_ "GitHub rate limit exceeded"))
>            #f))
>   (with-networking-fail-safe ...))

Shouldn't this be wrapped the other way around?
Or maybe even move the http-get-error?+string=?+warning inside
call-with-networking-fail-safe?

If you do the latter, you'll have to check the 'uri' field of the
&http-get-error to determine if it's GitHub, and not, say,
SWH or the CVE database or something.

Greetings,
Maxime.