Skip to content
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

Closed
sdondley opened this issue Jun 29, 2022 · 14 comments
Closed

"Error accessing GitHub API. HTTP Code: 401" #606

sdondley opened this issue Jun 29, 2022 · 14 comments

Comments

@sdondley
Copy link
Contributor

sdondley commented Jun 29, 2022

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.

@JJ
Copy link
Contributor

JJ commented Jun 29, 2022

Some expired certificate?

@patrickbkr
Copy link
Member

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.)

@sdondley
Copy link
Contributor Author

@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.

@JJ
Copy link
Contributor

JJ commented Jun 29, 2022

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...

@sdondley
Copy link
Contributor Author

Seems like @lizmat should know.

@lizmat
Copy link
Contributor

lizmat commented Jun 29, 2022

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?

@sdondley
Copy link
Contributor Author

sdondley commented Jun 29, 2022

@lizmat that won't solve the bigger problem which is that zef is loading trying to install stale modules.

@sdondley
Copy link
Contributor Author

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.

@lizmat
Copy link
Contributor

lizmat commented Jun 30, 2022

Hmmm... it is not being picked up for some reason... will investigate tomorrow.

@sdondley
Copy link
Contributor Author

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.

@sdondley
Copy link
Contributor Author

sdondley commented Jul 5, 2022

Any luck @lizmat? Curious to know.

@lizmat
Copy link
Contributor

lizmat commented Jul 5, 2022

A lot of life intervened in the past days. And am pretty tired today, so it'll be tomorrow.

@lizmat
Copy link
Contributor

lizmat commented Jul 6, 2022

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.

@lizmat lizmat closed this as completed Jul 6, 2022
@sdondley
Copy link
Contributor Author

sdondley commented Jul 6, 2022

zef info Digest reports correct version now. 0.7.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants