-
Notifications
You must be signed in to change notification settings - Fork 767
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
Error in parsing response body #1461
Comments
[2024-09-01T09:05:54.537Z] "OPTIONS /yeying.api.identity.Identity/Search HTTP/1.1" 200 - 0 0 0 - "-" "Mozilla/5.0 (darwin) AppleWebKit/537.36 (KHTML, like Gecko) jsdom/25.0.0" "457182f3-5644-4481-8edc-140c9fc14832" "-" |
In Envoy's log, when 9188 bytes are returned, the test case does not report an error. When 16583 bytes are returned, an error is reported. |
@kobofare Hi, thanks for the report! I'm wondering if you could share some code snippets and your test setup configs (e.g. maybe with docker as well), so it could help us understand the issue? Are you talking to a real grpc server behind envoy? It's rather difficult for me to make out what exactly is going on from the log you provided :) |
yes, a real grpc server, this is a vitest config:
|
js client code:
|
Use jdsom and vitest to write unit tests. sends a grpc request to the envoy proxy. When the number of bytes returned is less than 16k, it can be returned correctly. Otherwise, the error "Error in parsing response body" will be reported.
jsdom:25.0.0
vitest:2.0.5
grpc-web:1.5.0
google-protobuf:3.21.4
The text was updated successfully, but these errors were encountered: