<RomainManni-Buca>
is it true that last jruby version dont have the compiler mode option as an optim for startups - was forcing jruby 1.9 before?
<RomainManni-Buca>
also is there any hack other than https://github.com/jruby/jruby/wiki/Improving-startup-time to really boost the startup? with asciidoctorj (just a jruby exec of asciidoctor (in ruby)) it is likely 3s to create the instance which is way too much (~500ms would be good)
shellac has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
rusk has joined #jruby
shellac has joined #jruby
shellac has quit [Client Quit]
shellac has joined #jruby
shellac has quit [Ping timeout: 245 seconds]
<kares[m]>
headius: meh, that is beta-ish :)
<kares[m]>
anyway its annoying maybe if it persist we should just remove it, till it gets some 💌
<headius[m]>
Yeah I know it is early days but it breaks one benefit of this, that I don't have to have three clients open. When it's unreliable I still have to.
<headius[m]>
I guess it would be more fair to say that's two strikes for the integration feature, not for matrix as a whole
<JulesIvanicGitte>
@headius thanks for the info :)
<CharlesOliverNut>
@rmannibucau There are some JVM and JRuby flags you can pass to improve startup. Can you show me an example of a simple use of asciidoctorj so I can have a go at it?
<CharlesOliverNut>
We have improvements coming up to try to cut startup time, but it's a difficult problem with any jvm tooling
lucasb has joined #jruby
<kares[m]>
test
<kares[m]>
yeah its anooying ... tried re-adding the bridge - seems to be not working much
<kares[m]>
(seemingly it does not work at all)
<headius[m]>
I think we should just drop it for now then...I'm getting double notifications one direction and the other way doesn't work
<lopex>
wtf
<lopex>
jruby -e "include Java; p org.joda.time.LocalTime.new.getHourOfDay()"
<lopex>
13
<lopex>
jruby -e "p Time.now"
<kares[m]>
yy its pbly best to try later
<lopex>
2019-04-26 13:28:38
<headius[m]>
I'm definitely eager to have a fully open chat room system but the integration with gitter and IRC is a bit too flaky right now
<lopex>
how does java read time zones ?
<kares[m]>
gitter bridge definitely has problems atm: `Bridge returned HTTP 500 Internal Server Error: this.client.delete is not a function`
<lopex>
date -> Fri Apr 26 15:29:34
<kares[m]>
lopex: should read it from the system
<kares[m]>
while JRuby does check ENV (TZ which Java does not)
<kares[m]>
got 15 from `org.joda.time.LocalTime.new.getHourOfDay()` :)
<kares[m]>
lopex: try the Java time API maybe it will read fine (compared to JODA)
<lopex>
kares[m]: jruby matches java
<lopex>
its' two hours off to system date
<kares[m]>
so `jruby -e "p java.time.LocalTime.now.getHour()"` is 15 for you?
<lopex>
13
<kares[m]>
heh
<lopex>
it's under docker though
<lopex>
which has - /etc/localtime:/etc/localtime:ro
<lopex>
volume
<kares[m]>
think its likely at UTC
<kares[m]>
for whatever reason ...
shellac has joined #jruby
<headius[m]>
hahah this.client.delete
<headius[m]>
yeeeeah might want to look into that folks
<headius[m]>
lopex: hey that MS950 guy got back to us
<headius[m]>
On MRI it looks like it does somehow figure out to use CP950. Maybe we can just alias?
<lopex>
oh there is ENC_REPLICATE("CP950", "Big5")
<headius[m]>
Aha, and CP950 is there
<headius[m]>
yeah
<headius[m]>
so I saw we just add another entry for MS950 and call it done
<headius[m]>
I say
<headius[m]>
not I saw
<lopex>
sp why the scripts didnt pick it up
<lopex>
er
<headius[m]>
MRI warns that it's an unknown encoding