<ilikeorangutans[>
* maybe you can help me figure out what this exception i'm getting is about?
<headius[m]>
huh ok
<ilikeorangutans[>
i have no clue what is going on; i've tried to get a debug log out of it, but given that this seems to be an issue with jruby only i figured it might be a platform thing
<ilikeorangutans[>
was hoping someone here might have the magic answer :D
subbu|lunch is now known as subbu
valphilnagel_ has quit [Remote host closed the connection]
<headius[m]>
enebo: around?
<headius[m]>
ilikeorangutans: could you open this as a JRuby issue?
<enebo[m]>
hmm?
<headius[m]>
it may or may not be a bug but that would be the best way to proceed
<headius[m]>
enebo: I have been going through my bug queue and there's multiple ar-jdbc issues regarding 1.3
<headius[m]>
from people using DB adapters we don't support in 50+
<enebo[m]>
headius: yeah that is up to kares if he wants to or not. I have not touched 1.3
<headius[m]>
ok
<enebo[m]>
I suspect 1.3 is just going to be dead at this point
<enebo[m]>
and for that matter we need to consider retiring 50 and 51 since Rails does not support them but at this point a single commit here and there is not a big deal
<headius[m]>
right those I think are worth keeping alive longer but I am torn about this lost support
<headius[m]>
I know we had to cut our workload but it's a shame to lose those databases forever
<enebo[m]>
what?
<enebo[m]>
You mean all the dbs 1.3 had?
<headius[m]>
yeah
<enebo[m]>
I am pretty ambivalent on that. My only desire would have been for one of the tiny java dbs to be supported but people have not been banging down the doors over them either
<ilikeorangutans[>
<headius[m] "ilikeorangutans: could you open "> will do
<headius[m]>
I guess the decision then is whether to keep these bugs open or just kill them
<enebo[m]>
Put in an ass load of time to support a no longer supported db
<headius[m]>
well I thought that too but there's a couple different APIs all doing the same thing wrong
<headius[m]>
but that's irrelevant mostly, it's all on old adapters
<enebo[m]>
between 4 and 5 the connection adapter initializer switched arities
<enebo[m]>
What I had hoped is someone would actually PR some fixes for one of these guys but I would say nope
<enebo[m]>
If someone had jumped on this it is likely many adapters would partially work on 5 since they are not leveraging any native adapter code in activerecord
<enebo[m]>
but that is the rub
<enebo[m]>
It is almost better to get stuck earlier than have it bootstrap Rails but then have weird one off errors after that point
<enebo[m]>
Actually what I said above was confusing
<enebo[m]>
If someone had stepped up I would have welcomed it
<enebo[m]>
the nope is what happened
<headius[m]>
well I'm going to just go ahead and close these and say help wanted but we're not going to fix it
<headius[m]>
kares already marked one as wontfix but didn't close it
<enebo[m]>
ok yeah and I see kares already mostly said he wouldn't in one of those already
<headius[m]>
right
<headius[m]>
ok 1013 is actually against ARJDBC 52 but got hijacked by folks having problems with J2 and DB2
<headius[m]>
H2 not J2
<headius[m]>
I am closing anything that's about 1.3 or about unsupported databases in 50+, with a request for help to add that support back
<enebo[m]>
ok
<headius[m]>
ilikeorangutans: looks good!
<headius[m]>
II will try to reproduce
<headius[m]>
ilikeorangutans: have you tried this on a build of JRuby 9.3?
<headius[m]>
I just tried against master and it seems to be running ok
<headius[m]>
oho it finally failed
<headius[m]>
I wonder if this is getting tripped up on our package modules
ur5us has joined #jruby
<headius[m]>
yup that's it
<headius[m]>
ilikeorangutans: I will update the bug but I think this is due to us having some special objects where the class is actually a custom module