pawnbox has quit [Remote host closed the connection]
pawnbox has joined #jruby
yfeldblum has quit [Ping timeout: 246 seconds]
mkristian has joined #jruby
pawnbox has quit [Remote host closed the connection]
pawnbox has joined #jruby
robbyoconnor has quit [Ping timeout: 264 seconds]
skade has joined #jruby
pawnbox has quit [Remote host closed the connection]
pawnbox has joined #jruby
elia has joined #jruby
TheWhip has quit [Remote host closed the connection]
robbyoconnor has joined #jruby
robbyoconnor has quit [Remote host closed the connection]
robbyoconnor has joined #jruby
mkristian has quit [Quit: This computer has gone to sleep]
pawnbox has quit [Ping timeout: 272 seconds]
havenwood has quit [Ping timeout: 240 seconds]
pawnbox has joined #jruby
skade has quit [Ping timeout: 246 seconds]
TheWhip has joined #jruby
pawnbox_ has joined #jruby
pawnbox has quit [Ping timeout: 250 seconds]
samphippen has joined #jruby
pawnbox_ has quit [Remote host closed the connection]
pawnbox has joined #jruby
pawnbox has quit [Remote host closed the connection]
pawnbox has joined #jruby
yfeldblum has joined #jruby
blaxter has joined #jruby
temporal_ has quit [Read error: Connection reset by peer]
temporalfox has joined #jruby
drbobbeaty has joined #jruby
mkristian has joined #jruby
snim2_ has joined #jruby
vtunka has joined #jruby
mkristian has quit [Quit: This computer has gone to sleep]
TheWhip has quit [Remote host closed the connection]
TheWhip has joined #jruby
TheWhip has quit [Remote host closed the connection]
kares has joined #jruby
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
TheWhip has joined #jruby
TheWhip has quit [Remote host closed the connection]
nateberkopec has joined #jruby
TheWhip has joined #jruby
yfeldblum has quit [Ping timeout: 246 seconds]
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #jruby
elia has quit [Ping timeout: 240 seconds]
TheWhip has quit [Remote host closed the connection]
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
TheWhip has joined #jruby
cristianrasch has joined #jruby
TheWhip_ has joined #jruby
TheWhip has quit [Read error: Connection reset by peer]
TheWhip has joined #jruby
TheWhip_ has quit [Ping timeout: 256 seconds]
elia has joined #jruby
brauliobo_ has joined #jruby
TheWhip_ has joined #jruby
TheWhip has quit [Ping timeout: 246 seconds]
<GitHub157>
[jruby] perlun opened issue #3375: NameError: cannot load Java class net.Protocol http://git.io/vCUIp
yfeldblum has joined #jruby
vtunka has quit [Quit: Leaving]
mkristian has joined #jruby
cristianrasch has quit [Quit: Leaving]
TheWhip_ has quit [Ping timeout: 240 seconds]
TheWhip has joined #jruby
TheWhip has quit [Ping timeout: 264 seconds]
TheWhip has joined #jruby
samphippen has joined #jruby
TheWhip_ has joined #jruby
TheWhip has quit [Read error: Connection reset by peer]
drbobbeaty has joined #jruby
TheWhip_ has quit [Ping timeout: 240 seconds]
TheWhip has joined #jruby
mkristian has quit [Quit: This computer has gone to sleep]
pawnbox has quit [Read error: Connection reset by peer]
pawnbox has joined #jruby
TheWhip has quit [Ping timeout: 252 seconds]
TheWhip has joined #jruby
bga57 has quit [Ping timeout: 246 seconds]
TheWhip has quit [Read error: Connection reset by peer]
cristianrasch has joined #jruby
TheWhip has joined #jruby
<GitHub195>
[jruby] eregon commented on commit e0f049e: I guess the FindBugs issue was caused by the reflective access more than setAccessible().... http://git.io/vCU4y
yfeldblum has quit [Remote host closed the connection]
bga57 has joined #jruby
TheWhip has quit [Read error: Connection reset by peer]
TheWhip has joined #jruby
skade has joined #jruby
TheWhip has quit [Ping timeout: 264 seconds]
TheWhip has joined #jruby
nirvdrum has joined #jruby
lance|afk is now known as lanceball
mkristian has joined #jruby
<GitHub194>
[jruby] nirvdrum commented on commit e0f049e: Strange. Here's the link to the error:... http://git.io/vCUad
TheWhip has quit [Ping timeout: 244 seconds]
tcrawley-away is now known as tcrawley
TheWhip has joined #jruby
mkristian has quit [Quit: This computer has gone to sleep]
TheWhip has quit [Read error: Connection reset by peer]
TheWhip has joined #jruby
bbrowning_away is now known as bbrowning
TheWhip_ has joined #jruby
TheWhip has quit [Ping timeout: 256 seconds]
yfeldblum has joined #jruby
lea has quit [Ping timeout: 240 seconds]
TheWhip_ has quit [Ping timeout: 240 seconds]
lea has joined #jruby
Aethenelle has joined #jruby
yfeldblum has quit [Ping timeout: 246 seconds]
mkristian has joined #jruby
<GitHub23>
[jruby] eregon pushed 2 new commits to master: http://git.io/vCUDy
<GitHub23>
jruby/master 9febd8c Benoit Daloze: [Truffle] The alias keyword looks up the default definee and not self....
<GitHub23>
jruby/master 2e4e39a Benoit Daloze: Add spec for alias on top level
<headius>
element_reference failure tags as Proc#call
<headius>
boo
<headius>
so I had the same ones then
<headius>
had to do yield manually for some reason
<headius>
shared specs seem to have tagging problems fairly often for me
havenwood has quit [Ping timeout: 250 seconds]
yfeldblum has quit [Ping timeout: 240 seconds]
<headius>
man, block parameters have to be the most screwy part of Ruby language
<headius>
101 special cases
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
<lopex>
and designed by overhead
<xardion>
headius: yes :D
<headius>
lopex: setup_complex_parameters in MRI is a rabbit hole of complexity
camlow325 has quit [Read error: Connection reset by peer]
<lopex>
headius: dont even want to go there
<lopex>
if they named it complex then ..
camlow325 has joined #jruby
subbu|lunch is now known as subbu
<xardion>
that and the return statement when used in a block, depending on how that block was created.
<lopex>
I hope complex and complicated are not synonyms
<xardion>
not as many cases, but still gnarly
<lopex>
gnarly ~ complicated
<headius>
xardion: I think I finally figured that one out this summer
<headius>
it always returns from the nearest lexically-containing non-block context
<lopex>
design(some_complication, some_accident)
<xardion>
yeah, it's not horrible, but it begs the question: "why? and what criteria was used to decide that behavior?"
<lopex>
no algebra involved
<headius>
Java folks evaluated non-local return when they worked on Java 8 lambdas and decided it was just too complicated
<xardion>
the thing that gets me is that return in a Proc.new is different from one in a -> {}
<xardion>
I understand it being different in an implicit block (i.e. def something do; end)
<lopex>
headius: same for generics and reflection
<xardion>
I guess it has to do with the assumption that Proc.new is really a handy container to pass around a function, where as lambda are almost always a closure.
<xardion>
assuming I'm not getting the return behavior backwards (return in a Proc just returns from the proc, return in a lambda returns in the binding context)
<xardion>
anyway, I probably do have that wrong, but it is somewhat of an odd-duck. Not as tangled as block parameters though
<headius>
lopex: yeah, like a handful of AST nodes I suppose? :-)
<lopex>
headius: yeah
<lopex>
I mean, almost no mental mapping
<lopex>
headius: is the anything on hte horizon of returning multiple values at once in java ?
<lopex>
efficiently
<headius>
value types will do that for us
<lopex>
headius: for now in strng support I just return two int in a long in places
<lopex>
headius: what's the times line for that ?
<headius>
10
<lopex>
*timeline
<lopex>
bleh
<xardion>
yeah, I had that backwards. Still, it's odd that a lambda is explicitly different in that regard
<headius>
yeah
<headius>
xardion: I can never remember either :-)
<headius>
here we are 10 years into working on JRuby and I'm fixing a bug in lambda argument handling
<lopex>
and I remember reading about you being hired by Sun
<lopex>
like it was yesterday
<headius>
heheh
<headius>
good times
<lopex>
the's where it all started
<headius>
I miss Sun
<xardion>
yeah, if you do a return in a lambda, it just returns that value to the calling context. If you do that in a proc, it causes the binding context to return.
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
<xardion>
And my reasoning for why they do that is correct, I just had it backwards. Procs are intended to be used as a drop-in code snippet or a closure. A lambda is treated more like a first-class method (checks arity, for instance)
<xardion>
well, what you're doing there is slightly different.
<headius>
I didn't call them :-D
<xardion>
yeah, hehehe
<headius>
fixed
<headius>
matches expectations
<xardion>
yeah, it does
<xardion>
that's good, at least we know they didn't change that in 2.2.2
<xardion>
heads would roll
<headius>
lambda roots the block at that level while proc leaves the root at nearest non-block enclosure
<xardion>
right, makes sense since lambdas are intended to be an anonymous function. But, they DO have access to the binding of the context where they're defined.
<xardion>
so you can also use a lambda as a closure, just have to be aware of how return works, and the fact that it will check the number of parameters passed when you call() it
<xardion>
typically, if you want to return from a block, use next.
<xardion>
heh unless you defined that block in a loop :P
<xardion>
which would be bad(tm)
<xardion>
actually, that probably would still work as you intended, but it's gross
<headius>
xardion: nobody knows about next and break for the other types of return
<headius>
or practically nobody
<GitHub118>
[jruby] mkristian force-pushed deadlock from fc06782 to 455bcf0: http://git.io/vCIBq
<GitHub118>
jruby/deadlock 455bcf0 Christian Meier: improve RequireLock to better match its semantic...
elia has joined #jruby
<GitHub163>
[jruby] nirvdrum pushed 2 new commits to master: http://git.io/vCIBj
<GitHub163>
jruby/master 46d74df Kevin Menard: [Truffle] Removed unused conversions from JRuby objects to Truffle objects.
<GitHub163>
jruby/master 1a9aec2 Kevin Menard: [Truffle] Added missing attribution.
<xardion>
is it weird that whenever I read about Java 8's Metaspace, I always initially read it as Meatspace?
<nirvdrum>
I'm afflicted similarly.
<GitHub156>
[jruby] headius pushed 1 new commit to master: http://git.io/vCI0E
<GitHub156>
jruby/master f3dd725 Charles Oliver Nutter: Lambda should not splat yielded array with single rest arg....
<GitHub40>
[jruby] headius closed issue #3371: splash params lose a nesting level *only* in #_to_proc http://git.io/vcdxQ
<headius>
xardion: I always say meatspace
<headius>
I think I have infected a few others with it too
camlow325 has quit [Read error: Connection reset by peer]
camlow32_ has joined #jruby
camlow32_ has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
havenwood has quit [Ping timeout: 240 seconds]
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
djbkd has quit [Read error: Connection reset by peer]
camlow325 has quit [Read error: Connection reset by peer]
camlow325 has joined #jruby
havenwood has quit [Ping timeout: 246 seconds]
<headius>
perhaps just having the bug number in the spec commit is good enough
<GitHub22>
[jruby] headius pushed 1 new commit to master: http://git.io/vCIPe
<GitHub22>
jruby/master 19bc111 Charles Oliver Nutter: Add yield-to-lambda cases that were not all consistent in JRuby....
havenwood has joined #jruby
brauliobo has quit [Ping timeout: 256 seconds]
<xardion>
using puma with threads set at 0:16 (0 minimum, 16 max), and HikariCP with a thread pool of 16, I would expect to see 16 threads at idle (1 for each connection), possibly 32 if the driver itself has its own thread
<xardion>
but I have 60 at idle, jumps up to 76 when the server is loaded, which I expect
<xardion>
seems as if between HikariCP and the Vertica JDBC driver, there are 5 threads per connection
bbrowning is now known as bbrowning_away
<xardion>
that said, I don't know if that's really what's going on, since dropping the size of the connection pool has no noticable effect
<headius>
xardion: fibers?
<headius>
JVM itself has 10-15 threads for other purposes
<xardion>
That explains some of it at least
<headius>
JRuby has a couple JIT threads
<headius>
ahd fibers use threads
<xardion>
none of my code uses fibers, so it would have to be something in the vertica jdbc driver or hikaricp, maybe in slf4j?
<xardion>
I doubt it's the jdbc driver or hikari, since fiddling with the pool size has no impact. I'm not that concerned, considering the performance is great and the memory usage doesn't spike like my MRI implementation did.
<xardion>
just curious where they're all coming from
<chrisseaton>
xardion: don't they have names?
gregoriokusowski has quit [Quit: gregoriokusowski]
brauliobo has joined #jruby
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<xardion>
chrisseaton: they just all say java
<xardion>
unless there's a different way to see java thread names
<chrisseaton>
What tool are you using? JVisualVM and jstack should all tell you the names
<xardion>
oh right, forgot about jstack
<xardion>
ok, it's all JVM and jRuby threads, and the underlying native threads they're using (probably because of java.nio epoll)
<xardion>
so no worries
<xardion>
there's only around 11 actual JVM+jRuby threads
havenwood has quit [Ping timeout: 250 seconds]
lanceball is now known as lance|afk
cremes has quit [Ping timeout: 240 seconds]
colinsurprenant has quit [Quit: colinsurprenant]
enebo has quit [Quit: enebo]
cremes has joined #jruby
jimbaker has joined #jruby
<xardion>
oh, I've got parallel GC going too. Totally forgot about that :P
hobodave has quit [Quit: Computer has gone to sleep.]
yfeldblu_ has joined #jruby
yfeldblum has quit [Ping timeout: 246 seconds]
hobodave has joined #jruby
hobodave has quit [Ping timeout: 255 seconds]
Aethenelle has quit [Quit: Aethenelle]
TheWhip has quit [Ping timeout: 246 seconds]
samphippen has joined #jruby
havenwood has joined #jruby
yfeldblu_ has quit [Remote host closed the connection]