-
Notifications
You must be signed in to change notification settings - Fork 24
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 when attempting to access private repo #30
Comments
Interesting... Can you post the output of |
Here's
|
Huh, now I'm super confused. I nuked my pyenv and started fresh. Now the I had this debugging output when I was working on the change: It previously output Here's my latest
Possibly user error due to a bad environment? No idea. I'm going to see if I can replicate it and if not, maybe we can close this. |
Thanks for the additional information @jfredrickson5 . FWIW, you're not crazy... I've seen very similar behavior. I think there is a package in the dependency chain that is changing it's behavior... I've thought about trying to add some exception handling there to "do the right thing" but haven't gotten that all the way yet. If you're interested in adding that, I'd welcome the addition! |
@jfredrickson5 - I see you closed the MR, are you thinking that this is resolved too? Or did we still need to fix something? |
@IanLee1521 I'm not sure what notification GitHub sent you, but I'm in the process of merging my separate personal and work GitHub accounts into one, so I think that must have unintentionally triggered something; I haven't actually made changes to this issue. |
It was the the MR that got closed: #32 but ah, I see it was auto-closed by deleting a reference: |
Ah, that was my personal fork that disappeared then. It's been a while so I don't know if the change is still valid, but feel free to grab the change and use it. |
Attempting to run
scraper
on a GitHub org with private repos results in an error.Output:
Here is a simplified config.json as a test case. The GSA/private-test repo is private and contains a README.md file.
Example of a real config.json where we encountered the issue. It scans properly until it arrives at a private repo, at which point it crashes.
Verified that my GitHub access token is valid and can view private repos by using the same token for a different script.
The text was updated successfully, but these errors were encountered: