-
Notifications
You must be signed in to change notification settings - Fork 30
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
Crash whilst generating report #258
Comments
@skye-pp thanks for raising this error. I'm looking into it now. |
Found a different issue, getting that merged and released. But we are aware of rate limiting needed (reference github/github-ospo#77). I'll work on it this weekend. Again, thank you for raising the flag. |
Thanks! Just to make sure I understand, are you saying you think the error is related to rate limiting, or it was related to the separate issue you found and fixed? |
@skye-pp I believe your trace lends towards rate limiting. You wouldn't have authenticated successfully (when using a PAT) if it was the other issue (fixed with 2.1.0 release). If you want to pull 2.1.0 and retry, that'd be appreciated to confirm. |
@skye-pp I looked at this over the weekend. We have a few paths forward. I'm speaking with other maintainers on how best we want to proceed. |
Hey @jmeridth - any word on a path forward? 🙂 |
Describe the bug
Hi there, and happy new year 🎉
I'm trying out this action on relatively large organization (~1k repositories) and finding that it crashes out after a minute or so, in approximately the same place each time.
The traceback isn't obviously about rate limiting so I thought I'd raise an issue:
Please let me know if there's anything I can provide to help debug.
To Reproduce
Version used:
v2.0.1
(d6c45761f4ee2f781251c788006d14ca48c6ec8e
).Expected behavior
N/A
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: