Handle Ruby 3.1 eval location change #366
Merged
+2
−1
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
casperisfine
changed the title
Ref: ruby/ruby#4519 On Ruby 3.1, `Backtrace::Location#absolute_path` returns `nil` if the code was loaded with eval. That same PR made `require_relative` fallback to `Backtrace::Location#path` in such case, so we're doing the same.
casperisfine
force-pushed
the
fix-ruby-head-require-relative-from-evaled-file
branch
from
6ec6663
to
0d64e7e
Compare
casperisfine
deleted the
fix-ruby-head-require-relative-from-evaled-file
branch
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.
Ref: ruby/ruby#4519
On Ruby 3.1,
Backtrace::Location#absolute_pathreturnsnilif the code was loaded with eval. That same PR maderequire_relativefallback toBacktrace::Location#pathin such case, so we're doing the same.