pry-remote not working with test-kitchen

adecarolis commented 8 years ago

Within test-kitchen initiate instances I cannot manage to use use pry-remote.

Client side:

[root@test123 ~]# /opt/chef/embedded/bin/pry-remote
[root@test123 ~]#

Server side (chef-client):

       Compiling Cookbooks...
       [pry-remote] Waiting for client on druby://127.0.0.1:9876
       [pry-remote] Client received, starting remote session
       [pry-remote] Remote session terminated
       [pry-remote] Ensure stop service

       Frame number: 0/25

       From: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/pry-remote-0.1.8/lib/pry-remote.rb @ line 321 Object#remote_pry:

           319: def remote_pry(host = PryRemote::DefaultHost, port = PryRemote::DefaultPort, options = {})
           320:   PryRemote::Server.new(self, host, port, options).run
        => 321: end

This is what chef 12.13.37 installed:

[root@test123 ~]# /opt/chef/embedded/bin/gem list | grep pry
pry (0.10.4)
pry-byebug (3.4.0)
pry-remote (0.1.8)
pry-stack_explorer (0.4.9.2)
[root@test123 ~]#

This issue can be worked around by downgrading pry-byebug to version 1.1.3

rtacconi commented 8 years ago

Version 1.1.3 does not exist. I have this issue with or without pry-byebug

username-is-already-taken2 commented 7 years ago

I thought this issue might be because I'm using windows :) Did you ever manage to resolve it? or find a work around to debugging the client run? TIA

rtacconi commented 7 years ago

No, I gave up, this gem seems that it is not maintained.

username-is-already-taken2 commented 7 years ago

@rtacconi - thx for letting me know. Did you ever come up with another way of debugging the run?

rtacconi commented 7 years ago

I log into the instance create with Test Kitchen and I run these commands, including the chef-client:

https://gist.github.com/rtacconi/908a540a9476064c1fc9bdac188c8350

On 21 December 2016 at 12:25, username-is-already-taken2 < notifications@github.com> wrote:

@rtacconi https://github.com/rtacconi - thx for letting me know. Did you ever come up with another way of debugging the run?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Mon-Ouie/pry-remote/issues/68#issuecomment-268499917, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFBKaxLm2hPU_jmYbH6ZzCD8Vjv3hfsks5rKQykgaJpZM4JzDxL .

-- Riccardo Tacconi

http://github.com/rtacconi http://twitter.com/rtacconi

g2doug commented 6 years ago

I have experienced this problem and fixed it by removing pry-byebug.

Mon-Ouie / pry-remote

pry-remote not working with test-kitchen #68