IRB Debug Init + byebug

[jmarrec]

Pull request overview

• Companion PR: https://github.com/NREL/openstudio-gems/pull/84

• Opening as Draft because I'm not sure this is going to be wanted

This PR does two things:

• When loglevel is Trace, it preloads the IRB code so you can put binding.irb anywhere and it'll work. That includes inside our gem initialization code, but will work in any external script too. This allows you to inspect variables, but you don't have frame execution, because "debug" gem is built shared actually... see https://github.com/jmarrec/conan-recipes/issues/6
• After initialization is done, meaning in an external script for eg, you can require 'byebug' and put byebug and this will allow you to have frame execution, see this example

Pull Request Author

• [ ] Model API Changes / Additions
• [ ] Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
• [ ] Model API methods are tested (in src/model/test)
• [ ] EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
• [ ] If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
• [ ] If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
• [ ] Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
• [ ] All new and existing tests passes
• [ ] If methods have been deprecated, update rest of code to use the new methods

Labels:

• [ ] If change to an IDD file, add the label IDDChange
• [ ] If breaking existing API, add the label APIChange
• [ ] If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

• [ ] Perform a Code Review on GitHub
• [ ] Code Style, strip trailing whitespace, etc.
• [ ] All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
• [ ] Labeling is ok
• [ ] If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• [ ] If feature, test running new feature, try creative ways to break it
• [ ] CI status: all green or justified

[kbenne]

@jmarrec. This would be very useful for the kind of issues we just worked through with bundler. I'm sure that was part of the inspiration. What would be the downside of merging this? It seems like a win/win.

[jmarrec]

Downsides include:

• people who do ask for trace loglevel get code they don't need (they will not notice and noone asks for trace level output unless they're in trouble so big they wouldn't care), so noop here
• byebug is a new native ext gem

[jmarrec]

Will do