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
{{ message }}
This repository has been archived by the owner on May 27, 2021. It is now read-only.
When dyad_shutdown() is called, all outstanding streams have dyad_close() called on them. This prevents any data recently written to the stream--for example, a message indicating the session is ending--not to be received on the other end. It would be nicer if instead, shutdown could flush write buffers before closing the streams.
This could be optional, as the current behavior may be preferable in some circumstances.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When
dyad_shutdown()
is called, all outstanding streams havedyad_close()
called on them. This prevents any data recently written to the stream--for example, a message indicating the session is ending--not to be received on the other end. It would be nicer if instead, shutdown could flush write buffers before closing the streams.This could be optional, as the current behavior may be preferable in some circumstances.
The text was updated successfully, but these errors were encountered: