You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to use grpcurl against a proxy server (therefore hitting all sorts of unusual edge cases) has been a bit of a pain for debugging because it doesn't generally provide any diagnostics, even with -v/-vv. I would have expected one or the other to include details about the connection state and reflection queries, but instead the output is generally minimal / confusing. Some examples:
Hit an Envoy proxy incorrectly routing /grpc.reflection.v1alpha.ServerReflection to an HTTP server
$ grpcurl -vv -plaintext -d '{}' my_proxy:8080 my.CoolService.Endpoint
# no output, just hangs, I suspect because the HTTP server doesn't correctly close the streaming reflection request
^C
Passing -max-time helps but you need to look closely to realize it's reporting that reflection is what timed out
Obviously these are all cases were I would expect grpcurl to fail, but the output, especially with -vv, is IMO lacking. It would be great if more information could be surfaced in -v or -vv mode about the connection status and what data is being requested for reflection.
The text was updated successfully, but these errors were encountered:
Trying to use
grpcurl
against a proxy server (therefore hitting all sorts of unusual edge cases) has been a bit of a pain for debugging because it doesn't generally provide any diagnostics, even with-v
/-vv
. I would have expected one or the other to include details about the connection state and reflection queries, but instead the output is generally minimal / confusing. Some examples:Hit an Envoy proxy incorrectly routing
/grpc.reflection.v1alpha.ServerReflection
to an HTTP serverPassing -max-time helps but you need to look closely to realize it's reporting that reflection is what timed out
Hit that same HTTP server directly (this is a particularly odd failure as the server is up, and
curl my_server:8080
responds):Obviously these are all cases were I would expect
grpcurl
to fail, but the output, especially with-vv
, is IMO lacking. It would be great if more information could be surfaced in-v
or-vv
mode about the connection status and what data is being requested for reflection.The text was updated successfully, but these errors were encountered: