From: hsbt@... Date: 2016-08-17T05:28:13+00:00 Subject: [ruby-core:76945] [Ruby trunk Bug#8668][Rejected] Net::Telnet waitfor('Waittime'=>0) may wait forever Issue #8668 has been updated by Hiroshi SHIBATA. Status changed from Open to Rejected Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN to 2.1: UNKNOWN net-telnet has been extracted https://github.com/ruby/net-telnet ---------------------------------------- Bug #8668: Net::Telnet waitfor('Waittime'=>0) may wait forever https://bugs.ruby-lang.org/issues/8668#change-60174 * Author: Scott Johnson * Status: Rejected * Priority: Normal * Assignee: * ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [armv6l-linux-eabihf] * Backport: 2.1: UNKNOWN ---------------------------------------- waitfor('Waittime'=>0) says it will not wait once the expected prompt has matched, yet if the remote end continues to send data, it will in fact wait, possibly forever. Line 555 of net/telnet.rb (from 2.0.0) is: until(prompt === line and not IO::select([@sock], nil, nil, waittime)) Which means even though prompt has matched, it will still call IO::select, and if new data has arrived, it will make another pass through this loop. In my case there is constantly new data arriving (though it is only telnet control data) and so the loop never exits even though the prompt was matched long ago. I fixed this with: until(prompt === line and (waittime==0 or not IO::select([@sock], nil, nil, waittime))) Though I don't know what other implications that change might have. -- https://bugs.ruby-lang.org/ Unsubscribe: