nirvdrum_ has joined #jruby
nirvdrum_ has quit [Ping timeout: 265 seconds]
travis-ci has joined #jruby
<travis-ci> jruby/jruby (master:1ad6c29 by Marcin Mielzynski): The build is still failing. https://travis-ci.org/jruby/jruby/builds/605739364 [209 min 8 sec]
travis-ci has left #jruby [#jruby]
rusk has joined #jruby
<rdubya[m]> Sorry to be late to the party on the OpenSSL thing but every time we start our app we get this message: `OpenSSL implementation doesn't support ALPN.` looks like its coming from https://github.com/socketry/async-http/blob/master/lib/async/http/protocol/https.rb#L31
nirvdrum_ has joined #jruby
lucasb has joined #jruby
drbobbeaty has quit [Ping timeout: 276 seconds]
<headius[m]> Looks like an upgrade is in order then
<enebo[m]> it appears JSSE supports ALPN in 9+ and netty has their own impl as registered provider
<enebo[m]> can jruby-openssl even use that stuff or is it all BC?
xardion has quit [Remote host closed the connection]
<enebo[m]> rdubya: is mssql rake stuff set up where things will properly build? Is there anything I need to do with the fork repo for rubygems?
<enebo[m]> I have release 50-52 so far
xardion has joined #jruby
<enebo[m]> hmmm it would appear we don't
<enebo[m]> kares: rdubya We don't actually CI sqlserver so that is also a secondary concern but I don't know if azureci or the other big windows ci (forget name) can just run against sqlserver or not
<rdubya[m]> I have it running on travis
<rdubya[m]> I updated the gemspec so it should be able to be built
<rdubya[m]> is there other stuff that needs to be done with it?
<enebo[m]> rdubya: I do not see it in Rakefile so perhaps all I need is to add that subdir
<enebo[m]> maybe I have forgotten how this works too
<enebo[m]> :)
<rdubya[m]> lol
<enebo[m]> ./activerecord-jdbcmssql-adapter/activerecord-jdbcmssql-adapter.gemspec
<enebo[m]> this gemspec should use the forked dep
<enebo[m]> is that right?
<enebo[m]> Or is it totally self-contained
<rdubya[m]> its self contained
<rdubya[m]> oh
<rdubya[m]> that one isn't used anymore
<rdubya[m]> the gemspec is in the forked repo
<rdubya[m]> thought about updating it to add a message about it being deprecated but wasn't sure what we should do with it
<enebo[m]> yeah ok so I release 60.0 without any ms stuff and then this can be released which just depends on 60.0 of arjdbc
<rdubya[m]> right now it depends on 50.5
<enebo[m]> without any ms stuff I mean the pieces we do not have comitted into the Java bits
<rdubya[m]> i haven't gotten 51 or 52 started yet
<enebo[m]> oh ok cool so I put out new releases from 50-52
<rdubya[m]> all the java bits are in the arjdbc repo
<enebo[m]> so this is all independent in any case
<rdubya[m]> yeah
<enebo[m]> and you can now use official release of 50 to run sqlserver
<enebo[m]> and I take it you are releasing the forked repo as need be
<enebo[m]> or I should ask if you plan on it since you are developing it
<rdubya[m]> I can publish it, wasn't sure if you wanted to keep tabs on that since its hosted in the jruby org
<enebo[m]> rdubya: you are actually using it so I feel you would be more likely to recognize any issues from releasing it
<enebo[m]> At some future point we (kares/me) can release it but until it is more mundane I trust you over me :)
<rdubya[m]> ok lol, i can do it
<enebo[m]> but you are trusted to do this if that was your question
<rdubya[m]> cool, I haven't published many gems so I wasn't sure if there were organizations or anything on the rubygems side
<enebo[m]> you just need to have your email associated with the project (and some key )
<enebo[m]> so it is essentially a new gem so I think you can just publish and then we can get our ids added
<enebo[m]> for now just in case you are hit by a bus
<rdubya[m]> cool, i can do that
<enebo[m]> coolio
victori has quit [Remote host closed the connection]
victori has joined #jruby
nirvdrum_ has quit [Ping timeout: 240 seconds]
rusk has quit [Remote host closed the connection]
nirvdrum_ has joined #jruby
lucasb has quit [Quit: Connection closed for inactivity]
<headius[m]> Awesome!
<rdubya[m]> enebo: what do I need to do to give you and kares access?
<headius[m]> I think another tweet is in order
<enebo[m]> congrats
<rdubya[m]> thanks!
<headius[m]> rdubya you have Twitter yes? I will tweet about SQL server support
<rdubya[m]> cool, yeah its rwidmer
<headius[m]> Oh right
<enebo[m]> LOL rdubya already 16 downloads!
<enebo[m]> metafr: you know you mentioned carrierwave and I forgot that minimagick backend does support JRuby so carrierwave should work out of the box without having to consider image_voodoo
<enebo[m]> I think it uses open3 to call rmagick so my comments on using image_voodoo and being faster is no doubt true but someone would need to integrate image_voodoo
<fidothe> Not hugely critical, but when will post-9.2.9.0 nightlies start appearing on Sonatype? I have a thing that builds JRuby docker images, including the most recent nightly snapshot and I'm not sure if I need to add error handling for this immediate post-release stage, or just wait a couple of days...
<fidothe> (It builds JRuby images off of various JVM versions so I can build CircleCI images off of those so I can test https://github.com/fidothe/saxon-rb
Osho has joined #jruby
nirvdrum_ has quit [Ping timeout: 252 seconds]
<enebo[m]> fidothe: I will correct that now...I did not bump to next SNAPSHOT version
<enebo[m]> done
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<travis-ci> jruby/jruby (master:a3ce988 by Thomas E. Enebo): The build was fixed. https://travis-ci.org/jruby/jruby/builds/606239785 [206 min 47 sec]