-
Notifications
You must be signed in to change notification settings - Fork 225
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 on first time. #248
Comments
Affected by same. Will attempt to install via binary next. |
Same result with binary v0.5.0: https://github.com/erroneousboat/slack-term/releases/tag/v0.5.0 $> slack-term-darwin-amd64 -config ~/.config/slack-term.config
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x1440ba6]
goroutine 1 [running]:
github.com/erroneousboat/slack-term/service.NewSlackService(0xc0000acdc0, 0x29, 0xc0000acdc0, 0x0)
/home/jp/Projects/slack-term/service/slack.go:71 +0x2b6
github.com/erroneousboat/slack-term/context.CreateAppContext(0x7ffeefbfeb62, 0x29, 0x0, 0x0, 0x0, 0x157420f, 0x6, 0xc00002c900, 0x116, 0xc00001e1c0, ...)
/home/jp/Projects/slack-term/context/context.go:81 +0xd7
main.main()
/home/jp/Projects/slack-term/main.go:99 +0x1c2 |
Same result on v0.4.1 but different stack trace: $> slack-term-darwin-amd64 -config ~/.config/slack-term.config
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x13a26d1]
goroutine 1 [running]:
github.com/erroneousboat/slack-term/service.NewSlackService(0xc420250000, 0x29, 0xc420250000, 0x0)
/home/jp/go/src/github.com/erroneousboat/slack-term/service/slack.go:66 +0x2f1
github.com/erroneousboat/slack-term/context.CreateAppContext(0x7ffeefbfeb62, 0x29, 0x0, 0x0, 0x0, 0x14b1fc7, 0x6, 0xc42024e120, 0x116, 0x0, ...)
/home/jp/go/src/github.com/erroneousboat/slack-term/context/context.go:77 +0xd3
main.main()
/home/jp/go/src/github.com/erroneousboat/slack-term/main.go:102 +0x1b4 FWIW, my |
Confirmed the same result as the above reports - both pulling the binaries and building from scratch off of the current head #c19c20a The nil pointer dereference is happening on
Changing to this gets around the crash:
Then the program exits with the error message:
It looks like something isn't set up correctly with the token / access, causing the user info to not be available and the missing_scope error. |
Same issue here on FreeBSD (13.0-several), running version 0.5.0_1 from ports.
When started I can scroll through the channels just fine, typing not sure atm, but after a minute or so it will crash. |
Version: master branch
Installation method: go get -u github.com/erroneousboat/slack-term
~/go/src/github.com/erroneousboat/slack-term$ go install .
~/go/bin$ ./slack-term -token xxxxxxxxxxxxx
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x84e5b6]
goroutine 1 [running]:
github.com/erroneousboat/slack-term/service.NewSlackService(0xc0000d2dc0, 0x27, 0xc0000d2dc0, 0x0)
/home/smartin/go/src/github.com/erroneousboat/slack-term/service/slack.go:71 +0x2b6
github.com/erroneousboat/slack-term/context.CreateAppContext(0xc00002a210, 0x27, 0x7fff9b8cf768, 0x4c, 0x0, 0x98e37d, 0x6, 0xc0000fc5a0, 0x116, 0xc0000a0160, ...)
/home/smartin/go/src/github.com/erroneousboat/slack-term/context/context.go:81 +0xd7
main.main()
/home/smartin/go/src/github.com/erroneousboat/slack-term/main.go:99 +0x1c2
The text was updated successfully, but these errors were encountered: