[Bug]: Inconsistent blocking configuration in gRPC client vs. tests #116
Description
What happened?
In GRPC client, blocking is explicitly set to true. However, in the test, the cancel function expects blocking to be false. Otherwise TaskState would be TaskStateCompleted which is immutable.
For the JSON-RPC client, blocking isn't set (defaulting to false?), which matches the test expectation.
Why the gRPC client forced to blocking while the test expects non-blocking behavior?"
Relevant log output
Code of Conduct
- I agree to follow this project's Code of Conduct