-
Notifications
You must be signed in to change notification settings - Fork 798
gopls: automated issue report (crash) #2328
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
Hi @suzmue , Thank you for taking care it. the whole story is: Now it works after I reload the IDE, but I can't see the progress of go generate(there are handred lines of commands, I can see it before this crash). Thank you.I just got a output again and copied it here: [Info - 10:49:01] 2022/07/12 10:49:01 background refresh finished after 1.2117727s [Info - 10:49:20] 2022/07/12 10:49:20 protoc --proto_path=. --dart_out=grpc:D:\flutterwork\osc_client\lib\grpc google/type/color.proto google/protobuf/timestamp.proto google/protobuf/empty.proto google/protobuf/any.proto google/protobuf/wrappers.proto
panic: runtime error: invalid memory address or nil pointer dereference goroutine 60146 [running]: |
This is a dupe of golang/go#53781. Apologies for the breakage: we'll release [email protected] this week with a fix. |
gopls version: v0.9.0 (go1.17.6)
gopls flags:
update flags: proxy
extension version: 0.34.1
go version: 1.17.6
environment: Visual Studio Code win32
initialization error: undefined
issue timestamp: Sun, 10 Jul 2022 15:53:46 GMT
restart history:
Sun, 10 Jul 2022 15:47:18 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.
Failed to auto-collect gopls trace: no gopls log.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>
The text was updated successfully, but these errors were encountered: