search

Mon-Ouie / pry-remote

Connect to Pry remotely
Other
639 stars 81 forks source link

cant connect to session #60

Open artofhuman opened 10 years ago

artofhuman commented 10 years ago

I try to debug resque job. in my code pry.binding.remote_pry When i start resque QUEUE=* rake resque:work --trace and see in log [pry-remote] Waiting for client on druby://127.0.0.1:9876

try to connect: pry-remote and get error

...trace
FATAL: Pry failed to get user input using `#<struct PryRemote::InputProxy input=#<PryRemote::IOUndumpedProxy:0x000000028d1218>>`.
To fix this you may be able to pass input and output file descriptors to pry directly. e.g.
  Pry.config.input = STDIN
  Pry.config.output = STDOUT
  binding.pry
olivierlacan commented 9 years ago

I'm having the same issue after upgrading to pry-byebug 2.0.0 from 1.3.2 (byebug 2.7.0 to 3.5.1). Going to look into what changed in byebug 3.x since that major version bump probably has something to do with it.

@artofhuman What Ruby version do you use? Do you use pry-debug or pry-byebug?

artofhuman commented 9 years ago

@olivierlacan i use 1.9.3 with rails-express patch and i use pry-debug

olivierlacan commented 9 years ago

@artofhuman FYI for me rolling back to pry-byebug 1.3.3 fixed the issue on Ruby 2.0.0.

januszm commented 7 years ago

@olivierlacan do you know what was the change in pry-byebug that caused this issue? I'm having the same problem when I just use the pry-remote gem alone and connect to the server from my dev env.