We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Proto file(s)
syntax = "proto3"; package protos; option go_package = "/protos"; message TestRequest { sfixed64 id = 1; } message TestResponse { sfixed64 id = 1; } service TestService { rpc Echo (TestRequest) returns (TestResponse); }
Command line arguments / config
ghz --insecure \ --proto schema/test.proto \ --call protos.TestService.Echo \ -d '{ "id": 1000000000000000089 }' \ -n 1 \ 0.0.0.0:9009 # Server log: # Id: 1000000000000000100
Describe the bug
ghz is rounding the sfixed64 integer, which can result in confusion and incorrect test results.
sfixed64
1000000000000000089 is rounded up to 1000000000000000100.
1000000000000000089
1000000000000000100
10000000000000089 is rounded down to 10000000000000088.
10000000000000089
10000000000000088
Tests made with Postman:
Server log:
Id: 10000000000000089 Id: 1000000000000000089
To Reproduce
See this repository: https://github.com/themreza/ghz-test-sfixed64/tree/main
Expected behavior
The request sent to the server must match the call data argument.
Environment
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Proto file(s)
Command line arguments / config
Describe the bug
ghz is rounding the
sfixed64
integer, which can result in confusion and incorrect test results.1000000000000000089
is rounded up to1000000000000000100
.10000000000000089
is rounded down to10000000000000088
.Tests made with Postman:
Server log:
To Reproduce
See this repository: https://github.com/themreza/ghz-test-sfixed64/tree/main
Expected behavior
The request sent to the server must match the call data argument.
Environment
The text was updated successfully, but these errors were encountered: