Mitigate truffleruby failure by using unreleased stringio gem#790
Closed
Mitigate truffleruby failure by using unreleased stringio gem#790
Conversation
Member
|
Shouldn't be necessary anymore (stringio 3.1.0 was released) |
The fix has been merged but not released yet: ruby/stringio#71
st0012
force-pushed
the
mitigate-truffleruby-failure
branch
from
f495997 to
46df4f2
Compare
Member
|
But unfortunately there seems to be some not updated cache or so yet in rubygems.org :/ |
Member
|
The failure on https://github.com/ruby/irb/actions/runs/7017641177/job/19091354167?pr=790#step:3:87 is due to the debug gem using RBASIC()->flags too. |
Member
Member
Author
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
2 participants
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.
The fix has been merged but not released yet: ruby/stringio#71