Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-3115

Pry navigation does not work with puppetserver foreground

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Template:
    • Acceptance Criteria:
      Hide

      A package installed puppetserver instance should be able to execute via a puppetserver foreground session, and pry breakpoints should support navigation commands like `step` and `next`.

      Show
      A package installed puppetserver instance should be able to execute via a puppetserver foreground session, and pry breakpoints should support navigation commands like `step` and `next`.
    • Team:
      Froyo
    • QA Risk Assessment:
      Needs Assessment

      Description

      When running puppetserver in a foreground session, pry navigation does not work.

      The error supplied says

      /opt/puppetlabs/server/data/puppetserver/jruby-gems/gems/pry-nav-0.3.0/lib/pry-nav/tracer.rb:38: warning: tracing (e.g. set_trace_func) will not capture all events without --debug flag
      

      I have been unable to find a way to pass that flag, or another set of flags that will satisfy jruby an enable navigation commands like `next` or `step` to work.

      This is a problem for development of products and features like report processors that run in the puppetserver process. It slows down development significantly if stepping into a function requires stopping the process entirely to put a new pry breakpoint in the spot you want to get to, and then starting the service again and starting another puppet run, etc, etc, to get back to the spot you need to get to.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            william.hurt William Hurt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support