<headius>
I think we should bump it up a bit and see if it happens again
<headius>
I bumped it up on master to 768M, we will see if it happens anymore
joast has quit [Ping timeout: 240 seconds]
joast has joined #jruby
danieljrubyquest has quit [Ping timeout: 250 seconds]
ChrisSeatonGitte has quit [Ping timeout: 250 seconds]
TimGitter[m] has quit [Ping timeout: 245 seconds]
JesseChavezGitte has quit [Ping timeout: 256 seconds]
CharlesOliverNut has quit [Ping timeout: 256 seconds]
lopex[m] has quit [Ping timeout: 256 seconds]
MattPattersonGit has quit [Ping timeout: 252 seconds]
BlaneDabneyGitte has quit [Ping timeout: 252 seconds]
XavierNoriaGitte has quit [Ping timeout: 252 seconds]
ChrisSeatonGitte has joined #jruby
danieljrubyquest has joined #jruby
TimGitter[m] has joined #jruby
enebo[m] has quit [Ping timeout: 256 seconds]
CharlesOliverNut has joined #jruby
JesseChavezGitte has joined #jruby
lopex[m] has joined #jruby
MattPattersonGit has joined #jruby
XavierNoriaGitte has joined #jruby
BlaneDabneyGitte has joined #jruby
enebo[m] has joined #jruby
<kares[m]>
finally managed to test Logstash against master snapshots - failing atm but it might be an embed setup issue on the Logstash side.
<kares[m]>
unfortunately I am kept low to 'proactively' look into stuff (or do JRuby work) ... guess we'll follow up after 9.3.0 once this is more pressing on Logstash.
<kares[m]>
interestingly the other PR (post-poned for 9.3.1) for changing Ruby thread to bubble up Java errors is smt that came out of Logstash.
<kares[m]>
same outcome my manager does not appreciate this 😥
<headius>
kares we can certainly ship that other PR if it is ready, I just postponed it because I figured you were busy with other things