Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Out of GitHub API rate limit

    Release Bell
    3
    5
    463
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • SmartFinn
      SmartFinn last edited by

      Hi,
      after upgrade Release Bell to v1.7.0 I faced with GitHub API limit exceeded:

      $ > date +%s
      1622226172  # Fri, 28 May 2021 21:22:52 +0300
      $ > curl -v -H "Authorization: token ${GITHUB_TOKEN}" https://api.github.com/
      ...
      < x-ratelimit-limit: 5000
      < x-ratelimit-remaining: 0
      < x-ratelimit-reset: 1622229106  # Fri, 28 May 2021 22:11:46 +0300
      < x-ratelimit-used: 5005
      < x-ratelimit-resource: core
      ...
      

      I have starred 177 repos of which only 130 have tags/releases
      (see https://github.com/SmartFinn?tab=stars)

      Is it possible to reduce API calls?

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @SmartFinn last edited by girish

        @smartfinn Indeed, we have been seeing this in our installation as well. Debugging. It seems something related to the latest release 1.7.0.

        nebulon 1 Reply Last reply Reply Quote 0
        • nebulon
          nebulon Staff @girish last edited by

          I've tried to fix it now, it is currently deployed to our internal instance to see how it behaves, before we make a package release.

          SmartFinn 1 Reply Last reply Reply Quote 3
          • nebulon
            nebulon Staff last edited by

            The latest package release now has a few fixes to workaround the rate-limits (5000 requests per hour):

            • Remove unnecessary extra requests by using the local database better
            • Randomize request order to eventually catch all releases if
            • Less parallel requests
            • Take rate-limit reset time into account when to retry

            Hope this improves the situation.

            1 Reply Last reply Reply Quote 0
            • SmartFinn
              SmartFinn @nebulon last edited by

              @nebulon thank you, the API calls are dramatically reduced.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Powered by NodeBB