Clarify debug.rb compatibility in README #268
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I noticed I was running into the issue with byebug and zeitwerk mentioned in the README and in this byebug issue. I tried switching to debug.rb but had the same issue, which confused me since the docs mention it's compatible. As far as I can tell from the various GH issues, the debug.rb incompatibility was fixed in Ruby 3.1 onwards with a new TracePoint method mentioned in this debug.rb PR. I'm running Ruby 2.7.7 so I tried Break instead, which worked!
I was hoping to get this mentioned in the README since it wasn't very clear to me what the problem was with debug.rb until I spent a bit of time trawling through a couple of GH issues.