15:54 <headius> Hmm

20:04 <headius> https://github.com/jruby/jruby/pull/7285

20:04 <headius> enebo: I saw you reopened the related issue for this PR so we should pick it over... have you done that part?

20:18 <lopex[m]> headius: wow, so integrating virtual threads is as easy ?

20:18 <enebo[m]> headius: I merged k77chi saying it needed to be removed to fix other issues so I think this fix might not be right (and i did not notice I did this)

20:18 <enebo[m]> That PR itself did not say it was reverting...let me find that

20:19 <enebo[m]> https://github.com/jruby/jruby/pull/7311

20:22 <headius> It looks like it will work for us but I'm trying to figure out the right way to map Ruby threads and fibers to JDK virtual threads

20:24 <lopex[m]> they already implement a Thread dont they ?

20:25 <lopex[m]> I imagine there;s lot more machinery behind even from for users

20:25 <enebo[m]> headius: https://github.com/jruby/jruby/pull/7257

20:25 <headius> Yeah it mimics the thread API but behind the scenes it gets scheduled to run on a native thread

20:26 <headius> The plumbing underneath is full on continuations but apparently it's unsafe to expose to normal users at this point

20:26 <enebo[m]> This is probably a good thing but I did not read much and I don't know anything about security of GHA

20:26 <lopex[m]> but I guess work stealing etc doesnt leak here ?

20:26 <lopex[m]> I mean as an abstraction

20:28 <lopex[m]> I hope it wont be as dissatisfying as modules