-
Notifications
You must be signed in to change notification settings - Fork 25
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 fails with No live threads left. Deadlock? fatal error after making any API call with Faraday #28
Comments
Thank you for the report. I wondered if there could be a problem when nesting calls to Could you try with Ruby 3.0+? Could you try to minimize the example to avoid depending on gems? I don't have a Windows dev env, so I cannot really investigate myself if it's not reproducible on Linux. |
Thanks for checking. It will likely take me a while to find time to simplify this further. Using any version of byebug/faraday reproduces the issue, and only on timeout versions >= 0.3.0. I have no idea why the API call through faraday is needed before this will repro Ruby 3.0+ is a goal for us, but our mono repo has some gem dependencies keeping us on 2.7 for the time being. Currently I'm forcing a downgrade of timeout to 0.2.x to workaround the issue until we can find a better solution. |
Could you try your repro above on Ruby 3.0 on Windows and reply here whether it's also affected or not? That shouldn't require much work. FYI in case it is related to #17, see #17 (comment) (i.e., that should be fixed in CRuby IMO, let's see how that issue evolves). |
I am seeing it on Ruby 3.2 and timeout 0.4.1 (on Windows Server) using the above example.
|
This only occurs on Windows machines, to my knowledge and only in version 0.3.x
Script that reproduces this
timeout_error.rb
On a windows machine, run the script
./timeout_error.rb
The text was updated successfully, but these errors were encountered: