forked from toholio/ruby-serialport
-
Notifications
You must be signed in to change notification settings - Fork 58
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
read_timeout not working #73
Comments
I am also having this problem. Were you able to solve this? |
No. And I haven't seen anything that says they even acknowledge there's a problem.--Sent from my Android phone with GMX Mail. Please excuse my brevity.On 10/24/22, 6:01 PM Sumit Birla ***@***.***> wrote:
I am also having this problem. Were you able to solve this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Well ok then, I would say this gem is Useless for anyone doing serious work. |
Please try this gem. It's meant as a replacement. You can use regular Ruby IO method calls like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running with: ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu] on Linux Mint 20.3
I have the following code snippet, but here is what I would expect: I would expect that after say 250 ms, that if there was no input then an error would be produced. EIO? but if a character came then the loop would continue. What is actually happening is nothing, it just hangs:
The text was updated successfully, but these errors were encountered: