馃悰 Fix parse error parser_backtrace (for ruby <= 3.3) - #604
Merged
nevans merged 1 commit intoFeb 10, 2026
Merged
Conversation
Since the backtrace_locations don't _explicitly_ include the class name, this still feelds inherently brittle. But it's very useful! It's a worthwhile tradeoff, IMO.
nevans
deleted the
response_parse_error-detailed_message-fix-parser_backtrace
branch
February 10, 2026 23:30
This file contains hidden or 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
1 participant
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.
Since the
#backtrace_locationsdon't explicitly include the class name, this still feels inherently brittle. But it's very useful! It's a worthwhile tradeoff, IMO.