You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I was adding benchmarks to the Client.Receive function, I found out that the function blocks forever, hence blocking the benchmark. This was also the case while testing GatewayD manually for long-running queries. So, I believe adding a timeout will stop the receive function from blocking the event loop, thus hanging the entire process and the message flow.
The text was updated successfully, but these errors were encountered:
While I was adding benchmarks to the
Client.Receive
function, I found out that the function blocks forever, hence blocking the benchmark. This was also the case while testing GatewayD manually for long-running queries. So, I believe adding a timeout will stop the receive function from blocking the event loop, thus hanging the entire process and the message flow.The text was updated successfully, but these errors were encountered: