<GitHub168>
[jruby] ChrisBr opened pull request #5026: Fix String#rpartition for RegEx on Strings with multibyte chars (master...bug/fix-string-rpartition) https://git.io/vNdVr
shellac has joined #jruby
qmx_ has joined #jruby
qmx has quit [Ping timeout: 276 seconds]
havenwood has quit [Ping timeout: 276 seconds]
adam12 has quit [Ping timeout: 276 seconds]
qmx_ is now known as qmx
adam_ has joined #jruby
headius has quit [Ping timeout: 240 seconds]
headius has joined #jruby
havenwood has joined #jruby
havenwood has quit [Changing host]
havenwood has joined #jruby
<headius>
double blast...I can't regenerated it after loading it because it's a duplicate class then
<headius>
yeah this is a conundrum
bbrowning_away is now known as bbrowning
jrafanie has joined #jruby
<headius>
this change may have to be 9.2+
jrafanie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jrafanie has joined #jruby
<cremes>
Is there a way to disable the fiber thread pool and/or lock a fiber to a thread? Checked —properties but didn’t see anything obvious.
<headius>
cremes: hmm
<headius>
I don't believe there is a way right now
<cremes>
ok. If I wanted to hack that in for testing purposes, where would you point me?
<headius>
ThreadFiber.java in createThread()
<cremes>
i assume there is some kind of pool checkin/checkout that i could tweak...
<cremes>
great, I’ll have a look
<cremes>
is 9.2 imminent? :)
jrafanie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<headius>
cremes: not really...need to chat with enebo about whether we should wait for his symbol identifier work or push that to 9.3
<headius>
9.2 may absorb the Ruby 2.5 branch and skip 2.4
shellac has quit [Quit: Computer has gone to sleep.]
olle has joined #jruby
jrafanie has joined #jruby
xardion has quit [Ping timeout: 240 seconds]
xardion has joined #jruby
shellac has joined #jruby
<GitHub102>
[jruby] enebo closed pull request #5026: Fix String#rpartition for RegEx on Strings with multibyte chars (master...bug/fix-string-rpartition) https://git.io/vNdVr
<GitHub29>
jruby/ruby-2.5 e29816f Miguel Landaeta: No longer rescue exceptions from Integer#step when given a step value which cannot be compared with #> to 0...
<GitHub29>
jruby/ruby-2.5 b729677 Miguel Landaeta: No longer rescue exceptions of #coerce for Numerical comparison operators (< ,<=, >=, >)...
<GitHub29>
jruby/ruby-2.5 28100b3 Miguel Landaeta: Update MRI tests for methods that previously hid exceptions from coerce methods
<GitHub5>
[jruby] enebo closed pull request #5025: No longer hide exceptions from coerce method (ruby-2.5...no-longer-hide-exceptions-from-coerce-method) https://git.io/vN5Kr
claudiuinberlin has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
claudiuinberlin has joined #jruby
olle has quit [Quit: olle]
<cremes>
headius: I know that fibers can be backed by different native threads but I didn’t think this would change the RubyThread. Is it expected that Thread.current calls from within a Fiber would return different values over time?
shellac has quit [Quit: Computer has gone to sleep.]
claudiuinberlin has joined #jruby
subbu|lunch is now known as subbu
<cremes>
I know I can send ‘kill -QUIT <pid>’ to get the JVM to dump its *java* thread backtraces. Is there something similar for getting all of the Ruby thread & fiber backtraces?
<headius>
cremes: this is a known issue/problem/bug in JRuby, Thread.current will reflect the thread backing the fiber rather than the parent thread
<headius>
MRI actually had similar inconsistencies that led them to introduce fiber locals because thread locals were not always in the right place
<cremes>
ah…
<headius>
Thread.current from within a single fiber shouldn't change over time, but it won't reflect the parent thread
<cremes>
ok, that’s good to know for certain. I had a few moments where I thought I was losing my mind.
<headius>
I played with forcing it to become the current thread but synchronization of fiber results, resume/yield, etc got really difficult if it just became the other thread
<headius>
thread-based fibers are just a major hassle...if I could have real stack-swapping fibers I'd do it in a heartbeat
<cremes>
I have an open bug on MRI’s tracker requesting that they allow fibers to move freely between threads. They’ve already come back and said “no” but havne’t given reasons yet.
<cremes>
yeah, real coroutines would rock
<cremes>
maybe java11 ;)
<cremes>
too bad quasar or whatever that patch was called never got accepted into mainline jvm
<cremes>
shoot, a bunch of my code was written with the assumption that there would only ever be one parent Thread.current per Fiber and *all of its child fibers* within the same thread.
<cremes>
I don’t see an easy work around for JRuby… maybe a singleton/global registry where we can track the “ancestry” of a fiber and its parent thread…
<cremes>
^^ I know that probably makes no sense to you but it does in the context of what I’m working on.
<cremes>
headius: I’ll search for this issue on github. If I don’t see it, I’ll open one up to track it.
<jrubyn00b>
ThreadError: unable to create new native thread initialize at org/jruby/RubyThread.java:571 new at org/jruby/RubyThread.java:522 block in child.rb at child.rb:13 loop at org/jruby/RubyKernel.java:1292 <main> at child.rb:7
<jrubyn00b>
Buh, ignore me.
jrubyn00b has quit [Quit: Page closed]
jrafanie has quit [Ping timeout: 256 seconds]
shellac has quit [Quit: Computer has gone to sleep.]