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
Actual:
Intermittently, the cancellation token is ignored and the cancellation is never passed to the server
Expected:
The server method is cancelled
Root Cause: ReadAndHandleRequestsAsync() kicks off each request on its own thread, and the cancellation request, though arrived second, may be handled faster than the method invocation, and may not find its id in inboundCancellationSources, and won't be able to cancel it.
The text was updated successfully, but these errors were encountered:
To ensure that cancellation request is processed after the method it is
cancelling, we handle all incoming requests sequentilly, and only yield
when we execute user code.
Fix for #56
To ensure that cancellation request is processed after the method it is
cancelling, we handle all incoming requests sequentilly, and only yield
when we execute user code.
Fix for #56
To ensure that cancellation request is processed after the method it is
cancelling, we handle all incoming requests sequentilly, and only yield
when we execute user code.
Fix for #56
To ensure that cancellation request is processed after the method it is
cancelling, we handle all incoming requests sequentilly, and only yield
when we execute user code.
Fix for #56
Repro:
Actual:
Intermittently, the cancellation token is ignored and the cancellation is never passed to the server
Expected:
The server method is cancelled
Root Cause:
ReadAndHandleRequestsAsync() kicks off each request on its own thread, and the cancellation request, though arrived second, may be handled faster than the method invocation, and may not find its id in
inboundCancellationSources
, and won't be able to cancel it.The text was updated successfully, but these errors were encountered: