-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guard injection against old rubies #4140
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4140 +/- ##
=======================================
Coverage 97.77% 97.77%
=======================================
Files 1353 1353
Lines 81820 81820
Branches 4145 4145
=======================================
+ Hits 79997 79999 +2
+ Misses 1823 1821 -2 ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-11-27 13:30:19 Comparing candidate commit f9aec1a in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 30 metrics, 2 unstable metrics. scenario:profiler - sample timeline=false
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the PR adds a new file, this script needs to be updated.
cp ../lib-injection/host_inject.rb sources |
ff2bea5
to
afe6b26
Compare
These versions may be unable to execute - or even parse - the main host injection script.
50fa474
to
f9aec1a
Compare
What does this PR do?
Add a known-processable frontend script to the main injection script.
Motivation:
Main injection script may be attempted to be loaded via
RUBYOPT=-r'/path/to/host_inject.rb'
but be unprocessable.Change log entry
Add safe NOOP injection script for very old rubies
Additional Notes:
How to test the change?