Conversation
|
@kou I have merged my PR for JRuby to switch to the gem, and a snapshot build is being generated right now. The additional patch here is needed to remove some object flags from JRuby core that are specific to StringIO. I have patched around the issue in JRuby master but this will allow me to remove the flags completely. Once setup-ruby picks up the latest JRuby nightly then we should be able to restart the build and see what fails. I will fix any additional issues in this PR. |
|
OK! |
|
Well I am confused. It appears to have picked up the nightly build but it still does not pass the tests. When I run them locally, they pass: Are you able to try running them yourself and let me know if they fail? |
|
Ok I think I was wrong. The JRuby commit that would have strscan as a gem is jruby/jruby@dd44c46. The strscan CI build last used 5ce97a58dc, a previous commit. I will make sure there's a fresh snapshot build now so that it will be picked up by tomorrow, and then we will re-run tests and see how it looks. |
|
@headius I've released 3.0.3 now for CRuby 3.2.0. Should we include this change for the latest stringio release? If so, we should merge this and release 3.0.4 with this change. |
|
Yes I believe we can make this change now. Perhaps we can merge and push a .pre gem so I can test it for JRuby 9.4.1? |
Flag registry works based on class, but core cannot reference the StringIO class now, so we move the flags out to the gem.
377ec22 to
ebbc292
Compare
|
I have rebased on master so we can get an updated CI run. |
|
Looks good to me! |
|
Thanks! |
|
Released. |
This eliminates the StringIO object flags in JRuby core, which which have moved into the gem. See ruby/stringio#26
Now that there's a pre gem out there are a few additional fixes needed to get things working.