-
Notifications
You must be signed in to change notification settings - Fork 470
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
Panic in SASTToolInCheckRuns #135
Comments
I tried it and it didn't fail for me.
|
@naveensrinivasan, I also tried with go1.15.6, and it still panics. |
You are right it fails when I try it within a loop. Thanks for that information 😄 . |
naveensrinivasan
added a commit
that referenced
this issue
Jan 18, 2021
Fixed the panic by doing a nil check. Fixes #135
naveensrinivasan
added a commit
that referenced
this issue
Jan 18, 2021
Fixed the panic by doing a nil check. Fixes #135
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into an odd issue today:
If I limit the checks to just SAST, I haven't seen it panic yet. I added some debugging print statements before the range loop to see what the github package is returning. It looks something like this:
It would be easy to add a nil-check before accessing
csr
, but it seems like the github package should be returning an error or a non-nil response.I tried updating to
github/v33
, but the problem remains.The text was updated successfully, but these errors were encountered: