Open sonnmp opened 12 months ago
The code as written is - intentionally - the same as the BCL implementation when it exists, so if we changed this, we'd also need to use the diverged version in all cases, which in turn breaks the virtual
; so: before going that route, I'd like to first explore whether we're trying to fix the wrong thing. So; what is the actual repro here? Did the client signal disconnect, or did the client detach without signaling disconnect? (what it means to signal disconnect depends a little on how the client is sending)
Can we see the client part of this conversation? Also, I wonder whether there's something we could/should do in the server binding instead, to catch this exception scenario and instead write an ILogger message at a given id/severity
I found that when user cancelled subscribe on duplex streaming, server console show error. It is just cosmetic on console.
The error point to ChannelAsyncEnumerableExtensions.cs:line 34, which is:
` It require a catch here, so I fix it as:
` I just check on my server and now the console show error no more. It is somewhat essential because I use console for high severity error. Final, thank for your great work. It help the community a lot