-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: nil pointer in analysis #35339
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
Comments
Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here. |
Change https://golang.org/cl/205161 mentions this issue: |
Just mailed CL 205161 to handle this, but I'm curious about how you triggered it. Do you mind rebuilding |
I can't work out how to download the patch.. I must be misunderstanding something. |
Updates golang/go#35339 Change-Id: Ie990672b619d1844f66abf62010fe9a69daf00d9 Reviewed-on: https://go-review.googlesource.com/c/tools/+/205161 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Cottrell <[email protected]>
I've just tagged a pre-release of |
will do when I get back home later. |
I am still getting errors. I changed my startup script to this (commenting out the install steps).. maybe I did this wrong?
and got this stack trace
|
Change https://golang.org/cl/205500 mentions this issue: |
@ilanpillemer: Just uploaded CL 205500 for you to try again. To install it, |
will do first thing tomorrow morning (though if sync to latest do I lose static check?) or is static check etc included in the CL patch? |
Thanks! And no, staticcheck is in at master - you just need to opt-in with the configuration. |
I feel I am misunderstanding something.. so I sync the tools directory to latest, but I build gopls from master and then add the patch? |
Oh I'm sorry, I should've been more precise with my language. I didn't mean latest as in the latest tag, but rather latest as in master. Edited my comment. |
thanks! first thing tomorrow when I get back into the code I am working on I will do that. |
I have applied the patch.. Here are some logs that may help understand what is happening?
|
Thank you for sharing these logs! I just uploaded another patchset to CL 205500 if you'd be willing to try again and share the logs. |
Of course. Will do soon. |
please find log attached.. hope it helps! I didn't use stringer during the time of log generation.. let me know if you need another log after I do.. or if this tells you enough. I made some changes to the |
just in case.. I created a dummy new value.. reran go generate (which also used stringer) and here are the logs. I also restarted gopls between log generation. So previous log when a change was made in goyacc, and this one stringer. eg
|
Thank you! Looks like one staticcheck pass is failing in some unexpected way. Just uploaded another patchset to CL 205500 if you'd be willing to try again. |
I am very happy and willing to help as long as it takes. |
Great thank you so much! Pushed one more update so the quantity of log messages will be less overwhelming. |
ok. here is the log from before the last push (doesn't have the update to reduce quantity of log messages).. the stderror was full of this too
|
Here are the logs after the latest patchset Here are some extracts from stderror
|
Wow I can't believe it took me this long to catch it! The nil pointer was coming from line 344 in |
Change https://golang.org/cl/205859 mentions this issue: |
I won't be ablt to check until tomorrow morning. |
logs after latest fix attached |
Updates golang/go#35339 Change-Id: I2611b1a61bcf777fe4ce0f5446d1897c5698af86 Reviewed-on: https://go-review.googlesource.com/c/tools/+/205859 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Cottrell <[email protected]>
Change https://golang.org/cl/206149 mentions this issue: |
Thanks! Just pushed another update to the CL :) The change that actually fixes the nil pointer has been merged and cherry-picked for the release, so thank you for helping me find that! The remaining investigation will help us understand why there is an error creating an error message here. |
Updates golang/go#35339 Change-Id: I2611b1a61bcf777fe4ce0f5446d1897c5698af86 Reviewed-on: https://go-review.googlesource.com/c/tools/+/205859 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Cottrell <[email protected]> (cherry picked from commit b93886d) Reviewed-on: https://go-review.googlesource.com/c/tools/+/206149 Reviewed-by: Heschi Kreinick <[email protected]>
On Monday I will apply the latest CL and send the logs. |
some more logs and some extracts from stderr
|
might be related to |
some more logs |
This error now appears to be related to #34433 and the use of yacc with |
Please answer these questions before submitting your issue. Thanks!
What did you do?
I had gopls running
What did you expect to see?
gopls doing stuff
What did you see instead?
gopls doing stuff and restarting
stack trace of
another example
Build info
Go info
The text was updated successfully, but these errors were encountered: