Hi, Xinglu Chen <pub...@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’.
