Question

I started a blank project with methadone, an awesome framework for building command line apps. The only problem is that I am unable to debug from within the App class that’s in bin/my_app

The App class is a file created when you run methadone. Here’s how I’m trying to use pry

#!/usr/bin/env ruby

require 'optparse'
require 'methadone'
require 'my_app'
require 'pry'

class App
  include Methadone::Main
  include Methadone::CLILogging

  main do
     binding.pry    #  <= pry here
  end

  ...

When I run rake features I can tell the running process is trying to do something with pry since it pauses for a few seconds. I get the following error and then rake/cucumber is aborted.

process still alive after 3 seconds (ChildProcess::TimeoutError)

I can use pry just fine from the cucumber steps, rspec, or any other place, just not from anywhere in this App class.

One very interesting thing is that if I run my command line app from the console it WILL stop where pry is. It just wont pop into pry when using cucumber.

How can I get the app to work with pry when I’m running rake features?

Update

Sorry, I should clarify that methadone comes with aruba. So my cucumber scenario would look like this

When I successfully run `my_app arg1`

However, it WILL go into debug/pry if I run it with

bundle exec bin/my_app

Answer 1

Use pry-remote to connect to a pry session in the Aruba-managed subprocess.

(Disclosure: I paired with @Dty to come to this solution)