We've been consistently hitting this issue when using the GRPC client to read Persistent subscription info.
Client version: 3.1.0
Server version: 22.10.1
Right now, our implementation is falling back to a custom implemented HTTP client (the GRPC client seems to have a fallback mechanism to HTTP if the "feature" is not enabled, but I can't figure out how to force it to be used instead)
Hey @m-guesnon-pvotal and thanks for reporting this issue. While waiting for the review, could you try that patch in #151 and see if it fixes your issue?
Hi,
We've been consistently hitting this issue when using the GRPC client to read Persistent subscription info.
Client version: 3.1.0 Server version: 22.10.1
Right now, our implementation is falling back to a custom implemented HTTP client (the GRPC client seems to have a fallback mechanism to HTTP if the "feature" is not enabled, but I can't figure out how to force it to be used instead)
Stack trace
Location of the root cause: