<JRubyGithub>
[jruby] chrisseaton created truffle-new-require (+6 new commits): http://git.io/vsGw4
<JRubyGithub>
jruby/truffle-new-require f349a2f Chris Seaton: [Truffle] Start to pull out the code loading functionality.
<JRubyGithub>
jruby/truffle-new-require eed64b7 Chris Seaton: [Truffle] Remove the special casing for core:/ and replace it with truffle:/
<JRubyGithub>
jruby/truffle-new-require 6236e4e Chris Seaton: [Truffle] Fix loading stdlib from a jar - fixes #3264
JRubyGithub has left #jruby [#jruby]
JRubyGithub has joined #jruby
JRubyGithub has left #jruby [#jruby]
<JRubyGithub>
[jruby] chrisseaton opened pull request #3269: [Truffle] Refactor some of the require system (master...truffle-new-require) http://git.io/vsGwM
DomKM has joined #jruby
camlow325 has quit []
bbrowning is now known as bbrowning_away
dinfuehr has joined #jruby
dinfuehr has quit [Ping timeout: 265 seconds]
pietr0 has quit [Quit: pietr0]
havenwood has joined #jruby
treehau55 has joined #jruby
tikue has quit [Quit: Leaving...]
mdedetrich has joined #jruby
treehau55 has quit [Quit: Page closed]
havenwood has quit [Ping timeout: 260 seconds]
ekul has joined #jruby
<ekul>
having troble installing gems on ubuntu on digital ocean
<ekul>
NotImplementedError: waitpid unsupported or native support failed to load flock at org/jruby/RubyFile.java:298
<ekul>
anyone have an idea as to what is wrong?
bb010g has joined #jruby
dinfuehr has joined #jruby
cremes has joined #jruby
dinfuehr has quit [Ping timeout: 244 seconds]
cremes has quit [Client Quit]
dinfuehr has joined #jruby
cremes has joined #jruby
brycek has quit [Ping timeout: 272 seconds]
brycek has joined #jruby
lopex has quit [Quit: Connection closed for inactivity]
iloveitaly has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mdedetrich has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
jph98 has joined #jruby
jph98 has quit [Ping timeout: 264 seconds]
havenwood has joined #jruby
nirvdrum has quit [Ping timeout: 244 seconds]
mkristian has joined #jruby
<ekul>
fixed by installing via RVM
mkristian has quit [Quit: This computer has gone to sleep]
<kares>
yy ... forgot that I have an alias in the address
<headius>
thanks!
cristianrasch has joined #jruby
drbobbeaty has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
shellac has joined #jruby
cristianrasch has quit [Ping timeout: 250 seconds]
vtunka has joined #jruby
mdedetrich has joined #jruby
skade has quit [Read error: No route to host]
skade has joined #jruby
mdedetrich has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
thsig has quit [Ping timeout: 256 seconds]
cristianrasch has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
mdedetrich has joined #jruby
<GitHub120>
[jruby-openssl] kares created test-0.9.10-reverts (+2 new commits): http://git.io/vscnm
<GitHub120>
jruby-openssl/test-0.9.10-reverts fa5e674 kares: Revert "keep in line with MRI if possible" (on OpenSSL X.509 cert paths)...
<GitHub120>
jruby-openssl/test-0.9.10-reverts 91d2243 kares: Revert "the default cert could be PEM or a java keystore. it should load both whatver is used as default."...
shellac has joined #jruby
bbrowning_away is now known as bbrowning
<GitHub24>
[jruby-openssl] kares pushed 1 new commit to master: http://git.io/vsclz
<GitHub24>
jruby-openssl/master 2243aea kares: fill in 0.9.9 release notes
<kares>
going to prepare a staging release with reverts to run travis-ci
<kares>
enebo: basically the same thing as you already read in GH/mail-list
<enebo>
ok
<kares>
another 0.9.10
<kares>
I'll drop the current one
<enebo>
sure
skade has quit [Ping timeout: 246 seconds]
<GitHub121>
[jruby-openssl] kares pushed 3 new commits to master: http://git.io/vsCzc
<GitHub121>
jruby-openssl/master aa35fb9 kares: Revert "the default cert could be PEM or a java keystore. it should load both whatver is used as default."...
<GitHub121>
jruby-openssl/master 3fae31f kares: Revert "keep in line with MRI if possible" (on OpenSSL X.509 cert paths)...
<GitHub121>
jruby-openssl/master 9445efd kares: prepare for 0.9.10
<kares>
reverts on master - getting ready to stage 0.9.10
ivan\ has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
oblutak has joined #jruby
<GitHub92>
[jruby] kares pushed 1 new commit to jruby-1_7: http://git.io/vsC2k
<GitHub92>
jruby/jruby-1_7 4080603 kares: Revert "[build] get jossl-0.9.10 up for testing"...
<GitHub27>
[jruby] kares created test-jossl-0.9.10-1_7 (+1 new commit): http://git.io/vsCKM
<GitHub27>
jruby/test-jossl-0.9.10-1_7 3adf984 Christian Meier: [build] get jossl-0.9.10 up for testing
<kares>
let's see how travis-ci does and than your call for a release
<enebo>
kares: sure
<kares>
probably good idea to test 9K as well ... will do
<enebo>
kares: thanks
<enebo>
rtyler: since you have been doing a lot of triaging lately can you make sure when things are closed they get a milestone assigned
<enebo>
rtyler: fwiw so far I have not seen one where you closed the issue but I just thought I would mention it
<rtyler>
enebo: for many of the tickets that I was closing were effectively stale
<rtyler>
do you still want thing fixed in "current released versions" to have a milestone added?
<enebo>
rtyler: yeah so just make sure they are won’t fix or invalid or duplicate
<enebo>
rtyler: when I go through each release I figure which non-milestone closed issues were not labeled so we can make sure they get into the release notes
<rtyler>
rgr
<enebo>
I usually don’t ask people to do this until they are more regaulr in the process to alleviate that burden
<enebo>
too many rules burns out volunteers
<rtyler>
enebo: can you write it down for me? :)
<rtyler>
TRIAGING.md
<rtyler>
or something like that
<rtyler>
I am guaranteed to forget
<enebo>
rtyler: ah good idea…we can add it to wiki
skade has quit [Ping timeout: 272 seconds]
colinsurprenant has joined #jruby
skade has joined #jruby
<GitHub130>
[jruby] kares created test-jossl-0.9.10 (+1 new commit): http://git.io/vsCS2
<GitHub130>
jruby/test-jossl-0.9.10 1c0e63f kares: [build] test-out jruby-openssl 0.9.10 from staging
<enebo>
rtyler: our largest problem in my book wrt to releases is not knowing how important some fixes are
<rtyler>
enebo: one of the notes I have from jrubyconfeu is making it such that we can run the jruby/gradle acceptance tests with pre-release versions of jruby-complete
<rtyler>
I think that will help a lot for lookout
<enebo>
rtyler: yeah awesome
<rtyler>
since that exercises lots of jruby-complete functionality
<rtyler>
unfortunately what I see happen more often than not is that developers will work around something instead of filing a bug
<enebo>
rtyler: yeah I think it happens a lot in general in all software projects
<enebo>
I have not generated final issue list yet but I remember this
<rtyler>
nah, I checked that out on 1.7.21
<rtyler>
I couldn't repro
<rtyler>
anyways
kith has joined #jruby
<rtyler>
my biggest challenge isn't getting issues of import to you guys, but rather getting them from the various eng teams here
<enebo>
rtyler: I am just saying perhaps someone from lookout did make this as issue since I it got fixes
<enebo>
rtyler: this is also why when talking to you and colin I was hoping to get some paired developer rotation in both companies
<enebo>
rtyler: where 2 engineers spend a day or part of a day (and rotate) so they learn how to get engaged with out process and possibly fixing issues)
<rtyler>
enebo: right, I like that idea a lot
<enebo>
rtyler: it is awesome you are doing so much for our project right now but imagine :)
<rtyler>
I'm currently working with $MANAGEMENT to help determine what level of investment is right in JRuby moving forward
<enebo>
I personally do not think people need to do it very often to get enough knowledge to empoer them to report vs workaround
<enebo>
probably not enough time where they will end up losing any net time on their projects
<enebo>
since some portion of those reports will get fixed by us quickly
<enebo>
but preaching to the choir :)
<rtyler>
well, fixing issues without a good way of incorporating those back into our projects is definitely a limiting factor
<rtyler>
the velocity on releases is increasing which is good, but there's a big challenge for folks understanding that they ahve to wait a month to incorporate code from new jruby branches
<rtyler>
some of this is addressable by tooling on my end
<rtyler>
some by making sure people understand the cadence of releases
<enebo>
rtyler: I also think the more involved projects get with active development the more personal investment we have towards delivering quicker
hobodave has quit [Quit: Computer has gone to sleep.]
* rtyler
nods
<rtyler>
I'm all about pressuring you guys to deliver quicker
<rtyler>
buncha beer drinkin' slackers and all that xD
<enebo>
:)
erikhatcher has joined #jruby
<rtyler>
enebo: while I'm planning my day, anything to help with 1.7.22 release other than what mkristian is already working on
<enebo>
mkrisitian is not owrking on anything is he?
<rtyler>
jruby-openssl 0.9.10 I thought
<enebo>
rtyler: I think once kares closes jossl we will be good
<enebo>
rtyler: I tested with pre-revert and everything is good to go
<GitHub194>
[jruby] eregon pushed 1 new commit to master: http://git.io/vsWq8
<enebo>
rtyler: so I will do some more sanity there but I think we are ready
<rtyler>
enebo: is 1.7.22-SNAPSHOT up to date? I can run some internal tests
<enebo>
I don’t know
<enebo>
we have a cloudbees issue which seems to only happen on cloudbees
<enebo>
so there might not be an up to date one
<bbrowning>
enebo: what's the issue?
hobodave has joined #jruby
<enebo>
bbrowning: oh actually it might be fixed…mkristian removed text/pom.xml because he could see nothing using it
skade has joined #jruby
donV has joined #jruby
<enebo>
bbrowning: so it is back and I am not sure if we have ran…but we do not see this issue locally which is weird
<bbrowning>
hmm bees jobs look green except the -dist ones
<bbrowning>
jruby-1.7-dist failed last night with "java.lang.RuntimeException: Could not generate DH keypair: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)" for example
<enebo>
yeah restarting
<bbrowning>
looks like those have been failing for a while