Closed coolaj86 closed 2 months ago
{ "message": "API rate limit exceeded for 128.199.9.106. (But here's the good news: Authentic ated requests get a higher rate limit. Check out the documentation for more details.)", "documentation_url": "https://docs.github.com/rest/overview/re sources-in-the-rest-api#rate-limiting" }
This is unexpected as the adjacent logs also indicates the username, which implies that the token was being used.
Also strange that a restart of the server "fixed" it.
Typo in the authorization header.
Problem
17 minutes of downtime today June 5th from 18:39 to 18:56 UTC.
Retrospective
What happened:
Authorization
header, so authorization was not correctly sentsystemctl
to abort relaunchingWhat to do about:
fetch
(#852) in order to solve #850, #851. Even thought the commits were distinct, the process was not. If I had waited for a truly separate review on that change, the error would certainly have been more likely to be caught (i.e. review fatigue).Status Updates
Not sure why yet. Investigating.
Possibly related to the change in fetching github releases and a difference between the staging and production environment.