-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error accessing GitHub API. HTTP Code: 401" #606
Comments
Some expired certificate? |
There was quite some discussion on IRC. The current best guess is, that REA and modules.raku.org somehow use the API outside of it's limits. Which I don't really understand, because I would have guessed, that these two projects do simple downloads of files on GitHub and don't use the actual API directly at all. (But I might just be wrong about that.) |
@JJ if you mean an expired cert on github, not likely. This problem has been around at least 2 weeks. Unlikely GH would let a problem like that linger. |
Then it might be that we're becoming popular and went over the minimum rate. As Raku, we can create API tokens; we would have to use it, I guess. But not totally sure whose responsibility is that, other than whoever decides to do it first... |
Seems like @lizmat should know. |
I don't know anything about modules.raku.org, unfortunately. Maybe it's time to change modules.raku.org into a redirect to raku.land? |
@lizmat that won't solve the bigger problem which is that zef is |
Found another P6C module with the same problem: https://raku.land/github:grondilu/Digest It's been updated to 0.7.1 but zef info reports 0.7.0. |
Hmmm... it is not being picked up for some reason... will investigate tomorrow. |
I think it's because of all the 401 errors: https://modules.raku.org/update.log I think it's affecting all P6C modules. Granted, I could be out to lunch on this. That's just my best guess. |
Any luck @lizmat? Curious to know. |
A lot of life intervened in the past days. And am pretty tired today, so it'll be tomorrow. |
I'm still not sure where modules.raku.org gets all of these 401's from. Meanwhile, I've uncovered an issue in the REA harvester of the git ecosystem, that has now been corrected. I'm not sure whether a similar issue is in the zef harvester of the git ecosystem. Please either reopen this issue if you find other problems, or more generally disagree with closing this issue now. |
|
I'm trying to track down the source of a problem with zef serving up a stale version of Raku::Pod::Render
Please see: finanalyst/raku-pod-render#11 (comment)
And see https://modules.raku.org/update.log. There are a ton of modules with a "Error accessing GitHub API. HTTP Code: 401" error.
The text was updated successfully, but these errors were encountered: