Nothing showed except `PANIC` when typing [Solved]

shenwei356 commented 8 years ago

Prerequisites

[x] Have you run go get -u github.com/nsf/gocode (emphasis on the -u flag)?
[x] Have you tried launching atom . from the terminal in your project's directory?

[x] Have you verified the output from go env is correct? If it is, please include the output in this issue.

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/shenwei/shenwei/script/Go/project"
GORACE=""
GOROOT="/usr/local/app/go"
GOTOOLDIR="/usr/local/app/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build730322641=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

[x] Are you running the latest version of Atom? Have you tried Atom Beta, which can be run side-by-side with Atom Stable?
```
atom 1.9.9
```
[x] Have you updated your Atom packages?
[x] Have you run gocode in server debug mode? In your terminal:
- Run gocode close
- Run gocode -s -debug
- Type in atom
- Please include some debug output from gocode
- _It works in this step!!!_
  Description

Nothing showed except PANIC when typing.

Now _I follow this issue template, and solved it, hope people can solve this if meeting the same problem_.

Output From `go env`

[go env output here]

Steps to Reproduce

[First Step]
[Second Step]
[and so on...]
Expected Behavior

[What you expected to happen]

Actual Behavior

[What actually happened]

joefitzgerald commented 8 years ago

Yeah, in general, the procedure for solving the panic issue (which will happen after every go upgrade is:

Run gocode close
Run go get -u github.com/nsf/gocode

jfesler commented 8 years ago

This bit me as well. Since we know the expected behavior.. is this something that can be trapped, and something useful as a popup given to the user?

In my case I blew away all of go - entirely - but did not run "gocode close".

joefitzgerald commented 8 years ago

That's a great idea. Offering to close and go get gocode after receiving a panic is a great way to deal with this.

vivace-io commented 7 years ago

Side Note:

For those in the future looking to solve this issue or similar issues - make sure you've ended the gocode process after updating the gocode package. Otherwise, the issue will persist until you reboot your setup or gocode exits on it's own.

joefitzgerald commented 7 years ago

gocode close is now run automatically when you run the golang:update-tools command (ctrl + alt + shift + g u). Please run this first if you ever experience PANIC autocomplete results.

joefitzgerald / autocomplete-go