From: Xinglu Chen <public@yoctocell.xyz>
To: Maxime Devos <maximedevos@telenet.be>, 52577@debbugs.gnu.org
Subject: bug#52577: ‘guix lint’ throws an ugly backtrace if the GitHub updater receives “rate limit exceeded” error
Date: Tue, 21 Dec 2021 22:49:20 +0100 [thread overview]
Message-ID: <878rwdy6fz.fsf@yoctocell.xyz> (raw)
In-Reply-To: <c1d5275a6668fa6fca16eb6707091deb67905ab3.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On Tue, Dec 21 2021, Maxime Devos wrote:
> Xinglu Chen schreef op di 21-12-2021 om 18:17 [+0100]:
>> O[...]
>> Yeah, the catch/throw system doesn’t really work well with ‘raise’.
>> Here is what I found after some digging: [...]
>
> My point was that a raise-style exception shouldn't be wrapped in a
> (%exception ...) and then again in an &exception-with-kind-and-args,
> this wrapping should ‘collapse’. Seems like a bug in Guile.
OK, thanks for the clarification.
> Anyway, your patch to Guix looks reasonable to me, though it would be a
> good idea to look into fixing the double-wrapping in Guile.
Cool, fixing the issue in Guile itself would be great, I might look into
it in the future. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-12-21 21:50 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 [this message]
2022-05-14 14:18 ` 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=878rwdy6fz.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=52577@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.