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
the WsRpcClient here include a RpcClient, and RpcClient impl Handle, the Handle includes a function on_error, it uses default on_error function which just print out the error log. So when the WsRpcClient call the function direct_rpc_request, it fist connect the server, when getting a fused error, just print out the error log, the connect function still returns Ok, the result_out.recv() in the direct_rpc_request will waiting forever.
need to test:
When node_api is created successfully(which means the parachain is ok), if the WebSocket disconnected, what will happen when we use node_api? will it block the whole program?
❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain
the WsRpcClient here include a
RpcClient
, and RpcClient impl Handle, theHandle
includes a functionon_error
, it uses defaulton_error
function which just print out the error log. So when theWsRpcClient
call the function direct_rpc_request, it fistconnect
the server, when getting a fused error, just print out the error log, theconnect
function still returnsOk
, theresult_out.recv()
in thedirect_rpc_request
will waiting forever.need to test:
When node_api is created successfully(which means the parachain is ok), if the WebSocket disconnected, what will happen when we use node_api? will it block the whole program?
maybe some solutions:
The text was updated successfully, but these errors were encountered: