Document that pry-remote and pry-nav/pry-byebug do not work together #2167
Labels
Docs
Documentation, hands-on lab, and examples.
Comments
lucywyman
added a commit
to lucywyman/bolt
that referenced
this issue
Oct 7, 2020
… together This adds a note to the 'Debugging Tasks' section of the docs under the ruby section that the library we recommend, 'pry-remote', does not work with common pry libraries 'pry-nav' and 'pry-byebug'. This issues is [known](Mon-Ouie/pry-remote#35 (comment)) and does not seem likely to be resolved. I opted not to include this in our known issues page since this isn't an issue with Bolt itself. Closes puppetlabs#2167 !no-release-note
beechtom
added a commit
that referenced
this issue
Oct 7, 2020
(GH-2167) Add note that pry-remote and pry-nave do not work together
dontlaugh
pushed a commit
to dontlaugh/bolt
that referenced
this issue
Nov 22, 2020
… together This adds a note to the 'Debugging Tasks' section of the docs under the ruby section that the library we recommend, 'pry-remote', does not work with common pry libraries 'pry-nav' and 'pry-byebug'. This issues is [known](Mon-Ouie/pry-remote#35 (comment)) and does not seem likely to be resolved. I opted not to include this in our known issues page since this isn't an issue with Bolt itself. Closes puppetlabs#2167 !no-release-note
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Change You Would Like
This link sums the issue up fairly well, but basically
pry-remotewhich is necessary to debug tasks run using Bolt does not work withpry-navorpry-byebug. We should document this issue in the task debugging docs and on the known issues page.The text was updated successfully, but these errors were encountered: