Open cgeers opened 2 years ago
The same one
@cgeers @vitaliyantonov22 can you share a demo repository to reproduce this behavior locally to fast-track the fix?
I have just run into this, it doesn't specifically have to be the health check that is configured. Any service that hosts more than a single GRPC service on the same endpoint will cause this behavior. In asp.net core that would look like this in the startup code:
app.UseEndpoints(e =>
{
e.MapGrpcService<Service1>();
e.MapGrpcService<Service2>();
});
If either map service call is commented out, postman will work fine, but when both are active, it fails.
I ran into this today as well. @pnquest description is reproducible for me, namely, having multiple services on the same port. I commented out my health check service and Postman reflection worked.
Is there an existing issue for this?
Describe the Issue
When using postman to interrogate a grpc server's exposed services via reflection, an "unkown error" is reported if the default health check service is enabled. Digging around in the logs, from
logs/renderer-requester.log
I see:The default and service specific health checks appear to be working properly when using other client utilities (
grpcurl
,grpc_cli
, etc.) but postman seems to have trouble with it.Steps To Reproduce
grpc::EnableDefaultHealthCheckService(true);
Screenshots or Videos
Operating System
macOS
Postman Version
9.15.13
Postman Platform
Postman App
Additional Context?
when disabling health checks, using postman grpc server reflection appears to work well.