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
Describe the bug sudph transport do not close properly. When one edge of the transport closes the transport the other edge does not get notified. Consequently it treats the transport as alive and may write to it or fail to act on the transport being down. This was first noted by @i-hate-nicknames in #842
Steps to Reproduce
Steps to reproduce the behavior:
Open sudph transport
Close the sudph transport
Observe that the remote edge is not closing the transport on its edge
Possible implementation
This is likely the result of sudph using kcp library which may not support the needed shutdown behavior. Maybe it can be configured to do so.
The text was updated successfully, but these errors were encountered:
Describe the bug
sudph
transport do not close properly. When one edge of the transport closes the transport the other edge does not get notified. Consequently it treats the transport as alive and may write to it or fail to act on the transport being down. This was first noted by @i-hate-nicknames in #842Steps to Reproduce
Steps to reproduce the behavior:
sudph
transportsudph
transportPossible implementation
This is likely the result of
sudph
usingkcp
library which may not support the needed shutdown behavior. Maybe it can be configured to do so.The text was updated successfully, but these errors were encountered: