Since the CancellationToken is not passed, if an RPC call is cancelled the cancellation of the cancellation token wont result in the write being cancelled resulting in Halibut taking longer to cancel the call.
This can be worked around by using one of the other DataStream constructor methods.
Note that stream timeouts still apply, so Halibut can not be stuck forever in the write.
The issue is in the code below.
Since the CancellationToken is not passed, if an RPC call is cancelled the cancellation of the cancellation token wont result in the write being cancelled resulting in Halibut taking longer to cancel the call.
This can be worked around by using one of the other DataStream constructor methods.
Note that stream timeouts still apply, so Halibut can not be stuck forever in the write.
The issue is in the code below.
