Repository navigation
v0.3 REST and gRPC clients send blocking requests as non-blocking #1428
Description
What happens
CompatRestTransport.send_message and CompatGrpcTransport.send_message with a request that has no configuration return the task as soon as it is submitted. The v0.3 JSON-RPC transport returns the completed task for the same request.
Why
ToProto.message_send_configuration(None) returns an empty SendMessageConfiguration. v0.3 blocking has no presence, so the server reads the empty configuration as blocking=false. The JSON-RPC transport leaves the configuration out and gets the blocking default. This is the client side of #1321 and #1334.
Only callers using the transports directly see it. BaseClient always sets a configuration.
Version
main @ 28f8a62
Activity
rohityan commentedon Nov 6, 2026
Hi @ConnorMoss02, thank you for reporting this and for the contribution. Your root-cause analysis is correct, and your approach to resolve this in PR #1429 is the correct fix .
Until the PR is reviewed as a workaround callers can avoid this by routing requests through
BaseClientor explicitly supplying aSendMessageConfigurationon transport calls.fix(compat): send no v0.3 configuration when the request has none (a2…