Don Schrimsher
Don Schrimsher
Hey @deivid-rodriguez! You're welcome. Thanks for all of the work you've put into this project! Byebug has been an invaluable resource to me as a Ruby developer. No problem. Totally...
@os97673 Thanks! By "debug output" do you mean just printing to the terminal using `puts` or `pp`? I belive you're correct. I did some digging in Capybara and found that...
@deivid-rodriguez Perfect. I was wondering if there was a Byebug verbose option or something like that. Thanks!
Got it. I'm going to do some digging as soon as I get a chance. Thanks for you help!
Hoping to provide a fix shortly.
Hi Deivid, sorry for the delay in getting to this. I've been swamped. It may be a couple of more weeks before I'm able to get to it. I'd still...
@deivid-rodriguez Yes. I finally got a chance to look into this. I've narrowed down the hang to an IO#select call that reads from a socket in capybara-webkit [here](https://github.com/thoughtbot/capybara-webkit/blob/753348ecb40b133e174225d8bd8b8ed900d2a2c2/lib/capybara/webkit/connection.rb#L44). I'm trying...
Yes. I'm trying to figure out where a good spot to start looking in byebug would be. Any ideas?
@dkniffin The farthest I've been able to get so far is figuring this out is that the hang it happening in capybara-webkit on an IO select call. I'm not sure...
@dkniffin Sure. capybara-webkit communicates with the capybara server via [TCPSockets](http://ruby-doc.org/stdlib-2.1.1/libdoc/socket/rdoc/TCPSocket.html). After a lot of `puts`s, I traced this thread hanging issue down to an IO#select call in capybara-webkit's Connection class...