ur5us has quit [Ping timeout: 245 seconds]
ur5us has joined #jruby
ur5us has quit [Ping timeout: 245 seconds]
ur5us has joined #jruby
ur5us_ has joined #jruby
ur5us has quit [Ping timeout: 250 seconds]
ur5us_ has quit [Ping timeout: 252 seconds]
ur5us_ has joined #jruby
ur5us__ has joined #jruby
ur5us_ has quit [Ping timeout: 245 seconds]
ur5us__ has quit [Ping timeout: 260 seconds]
Specialist has joined #jruby
sagax has quit [Ping timeout: 246 seconds]
<headius[m]> Good morning
sagax has joined #jruby
<headius[m]> byteit101: thanks for getting it back to "green" again
<headius[m]> I am landing some things on 9.2, then triage latest reports, then back to closing out 9.3 stuff
<byteit101[m]> NP. I don't think anyone has reviewed the code (or the assorted minor TODO's I had questions about in said code). I'll add the ruby api doc later today
<headius[m]> ok
<headius[m]> The socket library from master has been backported to 9.2 and looks good
<headius[m]> backport meaning copy 😀
<headius[m]> git st
<headius[m]> hah
<headius[m]> perils of everything in dark mode
<travis-ci> jruby/jruby (jruby-9.2:c79330a by Charles Oliver Nutter): The build is still failing. https://travis-ci.com/jruby/jruby/builds/226133633 [173 min 17 sec]
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<headius[m]> 9.2 merged to master and I set the 9.2 deploy job to allow failures since the main dist still does deploy
<headius[m]> only jruby-jars artifact seems to be failing due to some oddity in the ruby/maven integration
travis-ci has joined #jruby
<travis-ci> jruby/jruby (jruby-9.2:125a5b2 by Charles Oliver Nutter): The build was fixed. https://travis-ci.com/jruby/jruby/builds/226139568 [170 min 14 sec]
travis-ci has left #jruby [#jruby]
<headius[m]> 👍
<headius[m]> kares: 6661 looks fine... remove the commented out line and merge at will
ur5us__ has joined #jruby
<byteit101[m]> doc pushed
Specialist has quit [Ping timeout: 250 seconds]
ur5us_ has joined #jruby
ur5us__ has quit [Ping timeout: 250 seconds]