You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a byebug issue, but it seems there's some issue with threads or Timeout library.
It comes up in minitest based unit testing, where if I run a series of tests and debug one of them, the others all have a timeout-related error. Also in libraries using timeout, such as some HTTP clients. If I try to run the library in byebug command line, it throws this exception.
[1, 5] in ./test.rb
1: #!/usr/bin/env ruby
2: require 'byebug'
3: require 'timeout'
4: byebug
=> 5: true
(byebug) Timeout::timeout(1) {}
WARNING: No backtrace available!!/home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:95:in `join': No live threads left. Deadlock? (fatal)
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:95:in `ensure in block in timeout'
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:95:in `block in timeout'
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:35:in `block in catch'
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:35:in `catch'
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:35:in `catch'
from /home/project/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/timeout.rb:106:in `timeout'
from ./test.rb:5:in `<main>'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/command.rb:114:in `eval'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/command.rb:114:in `bb_warning_eval'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/commands/eval.rb:29:in `block in execute'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/commands/eval.rb:7:in `run_with_binding'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/commands/eval.rb:25:in `execute'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:198:in `one_cmd'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:179:in `block (2 levels) in process_commands'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:178:in `each'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:178:in `block in process_commands'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:171:in `catch'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:171:in `process_commands'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:89:in `at_line'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:49:in `block in at_line'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:47:in `synchronize'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/processors/command_processor.rb:47:in `at_line'
from /home/project/.rvm/gems/ruby-2.1.1/gems/byebug-3.1.2/lib/byebug/context.rb:78:in `at_line'
from ./test.rb:5:in `<main>'
The text was updated successfully, but these errors were encountered:
I'm not sure if this is a byebug issue, but it seems there's some issue with threads or Timeout library.
It comes up in minitest based unit testing, where if I run a series of tests and debug one of them, the others all have a timeout-related error. Also in libraries using timeout, such as some HTTP clients. If I try to run the library in byebug command line, it throws this exception.
The text was updated successfully, but these errors were encountered: