-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
using pry-byebug with selenium - deadlock error and unable to step through my code #201
Comments
This shows what happens if I use 'next' rather than 'step'. It doesn't stop at each put statement. (which is what I want to do). So either way, step or next, it doesn't work or doesn't do what I'd like.
|
I have a similar issue while using pry-byebug with pry-remote on MacOS. If I try to use [36] pry(#<Admin::VersionsController>)> finish
From: /usr/local/lib/ruby/gems/2.6.0/gems/pry-remote-0.1.8/lib/pry-remote.rb @ line 211 PryRemote::Server#run:
206: def run
207: setup
208:
209: Pry.start(@object, @options.merge(:input => client.input_proxy, :output => client.output))
210: ensure
=> 211: teardown
212: end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I try using pry-byebug, I find I am unable to step through my code.
It goes into some internal code not written by me, and then gives an error about deadlock.
For anybody unfamiliar with Selenium, it is a library that lets a person programmatically control a web browser. I am using Mac osx. I had to do
$gem install selenium-webdriver
(which I guess you know). And I had to install a chrome web driver which I did with$brew tap homebrew/cask
and$brew cask install chrome driver
. Selenium is running fine for me.The program below demonstrates an issue I'm having with pry-byebug.
The text was updated successfully, but these errors were encountered: