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
Timeout crashes the telnetlib server #51
Labels
Comments
zofy
pushed a commit
to zofy/telnetlib3
that referenced
this issue
Jan 27, 2021
This is a potential fix for the issue jquast#51. * BaseServer.connection_lost() notifies the reader that the connection was lost. * TelnetWriter.close() was modified to avoid calling the close, when it's already closed.
jquast
added a commit
that referenced
this issue
Feb 3, 2021
I made 2 additional fixes and merged to master,
i'll release to pypi in 8 or more hours |
this fix is going to pypi shortly as 1.0.4 |
Thank you, great job! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've encountered a server crash after the timeout occurred. I think the issue was introduced after he circular reference was broken: 782c677
Let's start a simple telnetlib sever with timeout set to 5 seconds.
After the server is started and client makes a connection (
telnet localhost 8023
). After 5 seconds, the server crashes with:Could you verify that this is a bug?
IMHO the TelnetReaderUnicode.read() should be able to take the timeout into account. What do you think?
The text was updated successfully, but these errors were encountered: