-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channels opened by sockconnect() does not close automatically on EOF #11166
Comments
Still present on b7084fe Python version:
|
FWIW, I don't think this happens if you include an |
After a while, I think this behavior is correct. It prevents a class of bug where the channel id is reused but a stale one is held elsewhere before cleanup occurs (ie. in a dict). There should probably be documentation to remind users that they have to close the channel once they're done with it. I believe I got the assumption that the channel auto closes from
|
nvim --version
:Operating system/version: Gentoo
Terminal name/version: alacritty 0.3.3
$TERM
:alacritty
Steps to reproduce using
nvim -u NORC
Actual behaviour
The returned channel is still in the list.
lsof
will report that the socket held bynvim
is inCLOSE_WAIT
state.A walkaround is to close the channel manually via the handler on EOF.
Expected behaviour
The channel should be closed.
The text was updated successfully, but these errors were encountered: