This problem started for me after upgrading to 17.8.4. I downgraded back to 17.8.3, and am still facing the same problem.
how to fix StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. ---> System.OperationCanceledException : The operation was canceled.
even upgrade to the latest Version 17.6.4
still does it, can even be idle when it happens, Super annoying.
StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. ---> System.OperationCanceledException : The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at async StreamJsonRpc.MessageHandlerBase.WriteAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.SendAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync(<Unknown Parameters>)
--- End of inner exception stack trace ---
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync(<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async StreamJsonRpc.JsonRpc.InvokeCoreAsync[TResult](<Unknown Parameters>)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at async Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection`1.TryInvokeAsync[TService](<Unknown Parameters>)
9 answers
Sort by: Most helpful
-
-
Maciej Milański 0 Reputation points
2024-01-11T19:57:13.55+00:00 Hi! I'm not sure in what scenario you're getting this error. In my case it was while trying to train model for text classification. When using vs22 the error occurred, but using mlnet cli tool allow me to train model succesfully. So it was solution for me.
-
Mark Morrison 0 Reputation points
2024-01-24T12:28:03.38+00:00 Regarding this issue I have been experiencing it from last year thinking the issue was with visual studio but since last week I now believe it was an issue with the settings for my CPU in the bios. When I increased the LLC and the vcore and adjusted the frequency for the cores I am no longer experiencing the issue. So persons might need to check if the cores of their CPU are actually stable at specific frequencies, vcore and LLC. My 14900k could not even run 5.8ghz on one of the so called "favored" cores and I had to try and figure out which cores can actually run at the expected 6.0ghz.
-