Skip to content

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

@n8henrie

Description

@n8henrie

Output of restic version

restic 0.13.0 compiled 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?

./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 (af3de70) 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!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions