Issue with self-update API limit

dwaynelarose · May 3, 2024, 1:32pm

I seem to be hitting a wall with restic

I keep getting the following issue when I try to self-update restic

API rate limit exceeded for (But here’s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

It appears that there was some talk here:

github.com/restic/restic

self-update could recognize a personal GitHub token for higher rate limits

opened 03:10PM - 04 May 22 UTC

n8henrie

type: feature enhancement

Output of `restic version` -------------------------- ``` restic 0.13.0 compi…led with go1.18 on linux/amd64 ``` What should restic do differently? Which functionality do you think we should add? ---------------------------------------------------------------------------------- `restic self-update` should optionally accept a personal GitHub token (via flag or env var) to increase the rate limit and avoid users getting the inability to update. Apparently someone sharing my IP has made enough requests that I can't update from 0.13 to 0.13.1 with the built-in mechanism. What are you trying to do? What problem would this solve? --------------------------------------------------------- ```console ./restic self-update writing restic to /home/restic/bin/restic find latest release of restic at GitHub Fatal: unable to update restic: unexpected status 403 (403 Forbidden) returned, message: API rate limit exceeded for 2XX.REDACTED. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) ``` Did restic help you today? Did it make you happy in any way? ------------------------------------------------------------ Absolutely! Found more silent corruption issues (#1999) that otherwise would have gone unnoticed, and now it looks like `debug examine` is (maybe?) merged into master and available in `0.13.1` (https://github.com/restic/restic/commit/af3de702c782a72cb90804f8f86a41f3f4f61408) so I don't have to do my own debug build this time! This kind of silent corruption might have just gone noticed with a less meticulous program -- thank you restic devs!

Is there any word on a fix or work around?

I have tried this with restic versions lower the 0.13 and get the same issue unless I try early in the morning

Thanks