From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 52577-done@debbugs.gnu.org
Subject: bug#52577: ‘guix lint’ throws an ugly backtrace if the GitHub updater receives “rate limit exceeded” error
Date: Sat, 14 May 2022 16:18:26 +0200 [thread overview]
Message-ID: <87v8u8fb9p.fsf@gnu.org> (raw)
In-Reply-To: <87bl1fjpl3.fsf@disroot.org> (Xinglu Chen's message of "Fri, 17 Dec 2021 15:03:36 +0100")
Hi,
Xinglu Chen <public@yoctocell.xyz> skribis:
> When running ‘guix lint -c refresh’ on a package hosted on GitHub, I get
> an ugly backtrace when the GitHub rate limit has been reached.
>
> $ guix lint pipewire
[...]
> 1428:5 5 (check-for-updates #<package pipewire@0.3.29 gnu/packag…>)
> 771:2 4 (call-with-networking-fail-safe _ _ _)
> In ice-9/boot-9.scm:
> 1752:10 3 (with-exception-handler _ _ #:unwind? _ # _)
> 1685:16 2 (raise-exception _ #:continuable? _)
> 1683:16 1 (raise-exception _ #:continuable? _)
> 1685:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> ERROR:
> 1. &http-get-error:
> uri: #<<uri> scheme: https userinfo: #f host: "api.github.com" port: #f path: "/repos/PipeWire/pipewire/releases" query: #f fragment: #f>
> code: 403
> reason: "rate limit exceeded"
> 2. &message: "https://api.github.com/repos/PipeWire/pipewire/releases: HTTP download failed: 403 (\"rate limit exceeded\")"
This was fixed in March with commit
55e8e283ae398cc476e50e822383797c5f43db4c.
Closing!
Ludo’.
prev parent reply other threads:[~2022-05-14 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:03 bug#52577: ‘guix lint’ throws an ugly backtrace if the GitHub updater receives “rate limit exceeded” error Xinglu Chen
2021-12-17 16:29 ` Maxime Devos
[not found] ` <87sfurhru8.fsf@disroot.org>
2021-12-19 11:58 ` Maxime Devos
2021-12-21 17:17 ` Xinglu Chen
2021-12-21 17:32 ` Maxime Devos
2021-12-21 21:49 ` Xinglu Chen
2022-05-14 14:18 ` Ludovic Courtès [this message]
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=87v8u8fb9p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52577-done@debbugs.gnu.org \
--cc=public@yoctocell.xyz \
/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).