<headius>
this never landed because it dug too deep and caused other problems... I guess I forgot I reverted this part of the fix
<headius>
ok simple fix for the method_missing problem is to just revert direct indy binding of user-created method_missing
<headius>
we'll revisit it later but this logic needs some refactoring
<headius>
splitting is probably applicable here too so that will force us to do more
<headius>
I see this filling up logs in at least the indy mri:core job
<headius>
/home/runner/work/jruby/jruby/test/mri/ruby/test_thread_queue.rb:553: warning: deprecated Object#=~ is called on FalseClass; it always returns nil
<headius>
guess I shoul dlook into that too
<headius>
it doesn't fail but warns thousands of times
<byteit101[m]>
If it does, I'll try to tag a release
<headius>
byteit101: I'm still getting that SO_VERSION error
<headius>
I installed the binary for amd64-darwin and the bindings
<headius>
from all-gems on that build
<byteit101[m]>
No, java
<headius>
oh
<byteit101[m]>
This is where we failed last time iirc :-)
<headius>
loads ok with that installed
<byteit101[m]>
(I mean you can test MRI if you wnt)
<headius>
ahh right the java one has all the binaries
<byteit101[m]>
Yup
<byteit101[m]>
Ok, so the -java binary works for you on arm apple?
<headius>
yeah seems to work here on M1
<headius>
yes
<byteit101[m]>
Yay!
<byteit101[m]>
Only took... 4 months to confirm xD
<headius>
so tag off and then we can upgrade what we install for JRuby build
<byteit101[m]>
Awkwardly I did this fix in the middle of win32 work
<headius>
I will send you auth info for the MacStadium M1 instance; there's a couple GH runners on there now but they're idly 99% of the time
<byteit101[m]>
oh great!
<headius>
so we just need to set up another runner for your stuff
<headius>
two existing = one for JRuby and one for JNR
<headius>
runners are at org level I believe
<byteit101[m]>
I'm not sure if I can get to this before the weekend, still lots of post-vacation stuff I need to do, but at least we have a confirmed fix.
<byteit101[m]>
I'll update the ticket now
<byteit101[m]>
then I'll backport the fix soonish
<byteit101[m]>
Hopefully release tomorrow or over the weekend
<byteit101[m]>
And we can maybe discuss the win32 issues after that?
<headius>
ok no problem
<headius>
yeah I am back home for a while now
<headius>
I also have win32/arm64 running in parallels so we can try to cover that too
<byteit101[m]>
I'll need to split the ci-run target as right now it assumes it's running on intel GHA
<headius>
byteit101: seems like your dm is not getting e2e encryption
<byteit101[m]>
Ah, this is an old build, let me try something
<headius>
I'll have to dig deeper into how this test is set up
<headius>
could be something with how the strings are being compiled
<headius>
argh
<enebo[m]>
my fun arg is spending 35 minutes trying to decode optparse to realize while is not working right then realize yarp is returning keyword_while_modifier for a keyword_while and compiling it as an until