Skip to content
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

Bug with --lb-startegy flag #313

Closed
sunoce opened this issue Sep 14, 2021 · 0 comments
Closed

Bug with --lb-startegy flag #313

sunoce opened this issue Sep 14, 2021 · 0 comments

Comments

@sunoce
Copy link

sunoce commented Sep 14, 2021

Command line arguments / config
ghz localhost:6565 --proto proto-files/service.proto --data-file request-data-files/test_data.json --lb-strategy=round_robin

Describe the bug
Hello guys,

I wanted to test the '--lb-strategy' flag that was introduced in release v0.91.0.
When I use this flag in the cmd command, I get the following error the newest release:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7a1d7e]

goroutine 1 [running]:
go.uber.org/zap.(*SugaredLogger).log(0x0, 0x1, 0x0, 0x0, 0xc00072d9e8, 0x3, 0x3, 0x0, 0x0, 0x0)
/home/runner/go/pkg/mod/go.uber.org/[email protected]/sugar.go:221 +0x17e
go.uber.org/zap.(*SugaredLogger).Warn(...)
/home/runner/go/pkg/mod/go.uber.org/[email protected]/sugar.go:107
main.main()
/home/runner/work/ghz/ghz/cmd/ghz/main.go:319 +0xaed

To check if this is only a bug i downloaded release v0.91.0 and tested the same call with this release without an error.

Expected behavior
No error while using lb-strategy

Environment

  • OS: Ubuntu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants