yan

we submitted an envoy issue https://github.com/envoyproxy/envoy/issues/36552, where we were advised to submit an gRPC issue.

I also read the previous issue https://github.com/grpc/grpc/issues/34721, not sure whether it is the same or related: The previous issue stated that "after a HEAD request, all valid messages going through...

btw, this is blocking issue for us, I could not seem to change the bug priority though

this can be repro by first running curl Rest OPTION requests, it seems like that python gRPC service is confused by this Rest request, has this error "parse error: INTERNAL:...

@gnossen, thanks for looking into this! I’ll review your GitHub more closely tomorrow. Quick note on the repro steps: Step 1 is necessary; without it, no errors occur in Step...

@gnossen Thanks for the followup and the update! While we’ve also noticed that this bug occurs only with Envoy, we believe it still originates in the Python gRPC layer (C++...

@gnossen, thanks for the pointer! We tried v1.67.0 on our test service and couldn’t reproduce the issue locally. Could we please keep this issue open for now while we verify...

@gnossen thanks for looking into this and all your help! we have verified in production that v 1.67.0 fixed the issue.

@tyxia which gRPC forum I should reach out to? Here are python gRPC debug logs: I1018 16:08:25.517688418 44342 completion_queue.cc:1068] RETURN_EVENT[0x5d6cf08258a0]: QUEUE_TIMEOUT I1018 16:08:25.517734594 44342 completion_queue.cc:956] grpc_completion_queue_next(cq=0x5d6cf08258a0, deadline=gpr_timespec { tv_sec: 1729267705,...

@tyxia, filed gRPC bug https://github.com/grpc/grpc/issues/37953 This issue appears very similar to the previously reported one: https://github.com/grpc/grpc/issues/34721, which is also related to Envoy. By the way, even though the bug seems...