goyox86 has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
amsi has quit [Quit: Leaving]
heftig_ has joined #rubinius
heftig has quit [Read error: Connection reset by peer]
|jemc| has quit [Read error: Connection reset by peer]
sbryant has quit [Ping timeout: 258 seconds]
tenderlove has quit [Quit: Leaving...]
sbryant has joined #rubinius
havenwood has quit [Remote host closed the connection]
|jemc| has joined #rubinius
clauswitt has quit [Ping timeout: 245 seconds]
clauswitt has joined #rubinius
nirvdrum has quit [Ping timeout: 256 seconds]
amclain has joined #rubinius
|jemc| has quit [Ping timeout: 252 seconds]
sbryant has quit [Ping timeout: 258 seconds]
sbryant has joined #rubinius
sbryant has quit [Ping timeout: 258 seconds]
amclain has quit [Quit: Leaving]
|jemc| has joined #rubinius
sbryant has joined #rubinius
|jemc| has quit [Ping timeout: 264 seconds]
sbryant has quit [Ping timeout: 258 seconds]
sbryant has joined #rubinius
meh` has quit [Ping timeout: 240 seconds]
slaught has joined #rubinius
slaught has quit [Client Quit]
kagaro1 has joined #rubinius
kagaro has quit [Ping timeout: 240 seconds]
JohnBat26 has joined #rubinius
|jemc| has joined #rubinius
<|jemc|>
yopp: the error you see when trying to start the docker container means that it can't bind to port 80 because something else already is bound to it (which could be one of the other parts of your app, or it could be a dead version of the docker container that is persisting around - check the output of `docker ps -a` to see what containers are still "around")
<|jemc|>
you can also modify the command given in the README to use a port other than port 80, or leave off the port assignment entirely and use `docker inspect <container id>` to see what arbitrary port docker gave it
<|jemc|>
goyox86, brixen, jc00ke: regarding the docker container and blog post - I'm not entirely happy with the influxdb/grafana solution - goyox86, weren't you looking into a server-side graphing solution that would help us to avoid some of the problems with the fact that the grafana graphig/querying runs client-side? If we can come up with a cleaner solution, I'd like to promote that instead
|jemc| has quit [Ping timeout: 245 seconds]
Bwild has quit [Ping timeout: 244 seconds]
elia has joined #rubinius
<yorickpeterse>
morning
noop has joined #rubinius
noop has quit [Ping timeout: 240 seconds]
goyox86 has joined #rubinius
elia has quit [Quit: Computer has gone to sleep.]
<yopp>
|jemc-bot|, yeah, I've already found out that it's listening on boot2docker ip, not on localhos
<goyox86>
Morning!
|Blaze| has quit [*.net *.split]
goyox86 has quit [*.net *.split]
kfpratt has quit [*.net *.split]
mpapis has quit [*.net *.split]
blowmage` has quit [*.net *.split]
eregon has quit [*.net *.split]
Spakman has quit [*.net *.split]
JohnBat26 has quit [*.net *.split]
bennyklotz has quit [*.net *.split]
djinni has quit [*.net *.split]
brixen has quit [*.net *.split]
clauswitt has quit [*.net *.split]
jfredett-w1 has quit [*.net *.split]
machty has quit [*.net *.split]
cremes has quit [*.net *.split]
stormbrew has quit [*.net *.split]
yorickpeterse has quit [*.net *.split]
jeremyevans has quit [*.net *.split]
yxhuvud has quit [*.net *.split]
ahkurtz has quit [*.net *.split]
headius has quit [*.net *.split]
TheMoonMaster has quit [*.net *.split]
heroux has quit [*.net *.split]
cpuguy83 has quit [*.net *.split]
pd has quit [*.net *.split]
btcctf has quit [*.net *.split]
Gibheer has quit [*.net *.split]
stass has quit [*.net *.split]
imajes has quit [*.net *.split]
coffeejunk has quit [*.net *.split]
heftig_ has quit [*.net *.split]
johnmuhl has quit [*.net *.split]
guilleiguaran has quit [*.net *.split]
max96at|off has quit [*.net *.split]
kagaro1 has quit [*.net *.split]
abbe has quit [*.net *.split]
justinmcp_ has quit [*.net *.split]
alexsuraci has quit [*.net *.split]
mjc_ has quit [*.net *.split]
jc00ke has quit [*.net *.split]
chrisseaton has quit [*.net *.split]
cyndis has quit [*.net *.split]
arrubin has quit [*.net *.split]
mrb_bk has quit [*.net *.split]
andrewstewart has quit [*.net *.split]
Guest85414______ has quit [*.net *.split]
jeregrine has quit [*.net *.split]
stormwind has quit [*.net *.split]
halorgium has quit [*.net *.split]
larstobi has quit [*.net *.split]
DireFog has quit [*.net *.split]
dmilith has quit [*.net *.split]
erdic has quit [*.net *.split]
Liothen has quit [*.net *.split]
_ko10 has quit [*.net *.split]
bakkdoor has quit [*.net *.split]
tarcieri has quit [*.net *.split]
RealMarc has quit [*.net *.split]
pzol has quit [*.net *.split]
Rotonen_ has quit [*.net *.split]
saline has quit [*.net *.split]
|jemc-bot| has quit [*.net *.split]
locks has quit [*.net *.split]
atambo has quit [*.net *.split]
cypher23 has quit [*.net *.split]
yopp has quit [*.net *.split]
machete has quit [*.net *.split]
LTe_ has quit [*.net *.split]
tarcieri has joined #rubinius
TheMoonMaster has joined #rubinius
headius has joined #rubinius
Liothen has joined #rubinius
jeregrine has joined #rubinius
andrewstewart has joined #rubinius
heroux has joined #rubinius
yopp has joined #rubinius
coffeejunk has joined #rubinius
Gibheer has joined #rubinius
stormwind has joined #rubinius
pd has joined #rubinius
larstobi has joined #rubinius
Guest85414______ has joined #rubinius
halorgium has joined #rubinius
LTe_ has joined #rubinius
DireFog has joined #rubinius
yxhuvud has joined #rubinius
btcctf has joined #rubinius
bakkdoor has joined #rubinius
atambo has joined #rubinius
erdic has joined #rubinius
|jemc-bot| has joined #rubinius
_ko10 has joined #rubinius
imajes has joined #rubinius
mrb_bk has joined #rubinius
chrisseaton has joined #rubinius
cyndis has joined #rubinius
yorickpeterse has joined #rubinius
cpuguy83 has joined #rubinius
locks has joined #rubinius
saline has joined #rubinius
jeremyevans has joined #rubinius
cypher23 has joined #rubinius
stass has joined #rubinius
ahkurtz has joined #rubinius
stormbrew has joined #rubinius
dmilith has joined #rubinius
arrubin has joined #rubinius
jc00ke has joined #rubinius
mjc_ has joined #rubinius
alexsuraci has joined #rubinius
machete has joined #rubinius
max96at|off has joined #rubinius
machty has joined #rubinius
cremes has joined #rubinius
justinmcp_ has joined #rubinius
abbe has joined #rubinius
Rotonen_ has joined #rubinius
brixen has joined #rubinius
johnmuhl has joined #rubinius
clauswitt has joined #rubinius
kagaro1 has joined #rubinius
bennyklotz has joined #rubinius
|Blaze| has joined #rubinius
guilleiguaran has joined #rubinius
pzol has joined #rubinius
djinni has joined #rubinius
heftig_ has joined #rubinius
jfredett-w1 has joined #rubinius
RealMarc has joined #rubinius
blowmage` has joined #rubinius
mpapis has joined #rubinius
eregon has joined #rubinius
Y_Ichiro has quit [Max SendQ exceeded]
JohnBat26 has joined #rubinius
elia has joined #rubinius
elia has quit [Quit: Computer has gone to sleep.]
nirvdrum has joined #rubinius
elia has joined #rubinius
elia has quit [Client Quit]
elia has joined #rubinius
elia has quit [Quit: Computer has gone to sleep.]
|jemc| has joined #rubinius
|jemc| has quit [Quit: WeeChat 1.0.1]
|jemc| has joined #rubinius
elia has joined #rubinius
max96at|off is now known as max96at
enebo has joined #rubinius
sshao has joined #rubinius
meh` has joined #rubinius
elia has quit [Ping timeout: 256 seconds]
|jemc| has quit [Ping timeout: 245 seconds]
tenderlove has joined #rubinius
<brixen>
the keyword argument parsing is total sweetness
<brixen>
MRI 2.1.5 still fails a keyword spec
<brixen>
despite opening several issues related to keyword parsing
<yorickpeterse>
but if MRI fails that means it's a feature
<brixen>
pretty obvious MRI is never going to consider or contribute to rubyspec
<brixen>
which means there's no point wasting time maintaining it as a separate project
<yorickpeterse>
brixen: I'd disagree
<yorickpeterse>
There's opal, jruby, topaz in the past, etc
<chrisseaton>
brixen: we really appreciate having RubySpec as a project we can use - it's invaluable to us
<brixen>
they don't contribute to it either
kagaro1 has quit [Read error: Connection reset by peer]
kagaro has joined #rubinius
<brixen>
whether or not it's invaluable to some other project does not make it valuable to rubinius
<chrisseaton>
brixen: that's simply not true - I've got open PRs, and eregon has contributed work as well
<brixen>
a few PRs is not contributing
<yorickpeterse>
wat
<yorickpeterse>
I normally don't disagree, but that's a bit shortsighted
<brixen>
I don't think it is
<brixen>
I've been working on this a very long time
<yorickpeterse>
I'd argue that the primary reason more Rbx people work on it (today) is due to us having more control
<brixen>
I've wasted an enormous amount of time and effort on it
<yorickpeterse>
That is, we typically sync things, etc
<brixen>
that's not true
<chrisseaton>
I even reformatted and contributed the bibliography I put together for RubySpec because you suggested it
<brixen>
chrisseaton: yep, that was nice
<brixen>
if this was money though, it would be very simple
<brixen>
"I have you $5"
<brixen>
cool, it costs 2000 to keep the lights on
<chrisseaton>
brixen: if you need some help maintaining RubySpec, suggest some tasks for us to help with
<chrisseaton>
brixen: I can't promise anything radical but I'll lend a hand
<brixen>
write specs
<brixen>
it's that simple
<brixen>
there's a ton of MRI behavior that no one writes specs for
<brixen>
despite implementing it
<yorickpeterse>
brixen: that's like saying "just fix the world", I'd start with cleaning up the existing issues where possible
<brixen>
and write specs in way that conforms to the standards I set
<chrisseaton>
brixen: I actually opened a PR just yesterday that fixed a spec so it conforms to your standards
<brixen>
the existence of a project doesn't give you some magical entitlement to it
<yorickpeterse>
and at some point I want specs for the entire CAPI, but that's _a lot_ of work
<yorickpeterse>
I at some point toyed with the idea of a tool that converts MRI's test-unit tests into rubyspec, but it would be an equal amount of work to get that going compared to just doing things by hand
<chrisseaton>
brixen: I can't imagine at all where you're getting 'entitlement' from - I said I love your work and if you need more help maintaining it let me know - but I've already got open PRs that conform to your standards
<brixen>
chrisseaton: you're extremely new to this
<brixen>
you have a few PRs
<brixen>
that's nice
<brixen>
again, put that in monetary terms and see what you come up with
<yorickpeterse>
chrisseaton: heh, I completely forgot about that PR
<brixen>
I have decisions to make about what benefits Rubinius
<brixen>
the biggest waste of time for us is keeping track of MRI crap
<brixen>
MRI has had almost 8 years to get on the ball using rubyspec
<brixen>
they aren't, it's extremely unlikely they will and I'm not wasting more time with them
<yorickpeterse>
brixen: unrelated, we have those fucking bundler Git issues on Rubyspec, I believe that could be fixed by adding a Gemfile.lock, any objections against that?
<yorickpeterse>
brixen: I messed with that on a branch at some point, but for some reason never merged it
<enebo>
brixen: I agree you should do what you want with rubyspec, but you keep saying other projects never helped and it is flat out weird. nurse #5 contrib commitwise, mame #12, ujihisa #13, yugui #17, akr #22. I think they stopped largely because you keep saying they don’t contribute
<enebo>
(I omitted drbrain #20 because he used to work on rbx full time)
<enebo>
whoops missed kachick at #8
elia has joined #rubinius
havenwood has joined #rubinius
max96at is now known as max96at|off
max96at|off is now known as max96at
<yorickpeterse>
chrisseaton: another thing that would help: jruby 9k claims to have (almost) full 2.2 compatibility, rubyspecs for that would be tremendously useful
meh` has quit [Ping timeout: 245 seconds]
<chrisseaton>
yorickpeterse: good idea - I don't know anything about how they've tested the 2.2 stuff personally though
Bwild has joined #rubinius
<brixen>
enebo: number of commits is meaningless
<brixen>
enebo: go sum # of lines of current specs by contributor
<brixen>
I've had to fix a ton of crap committed by many people
<brixen>
enebo: also, a disconnect between your perception and reality is not "flat out weird"
<brixen>
ad hominem much
<enebo>
brixen: hahahahga
<enebo>
brixen: well you have zero interest in acknowledging that contributions are contributions and you say I cannot use weird?
<enebo>
brixen: like I said you can you do what you want I just wanted to point out the fallacy of your statement.
<brixen>
did you go sum # of current lines by contributor?
<brixen>
I pointed out the flaw in your supporting evidence
<brixen>
you tell me I'm wrong
<brixen>
but you don't actually follow the argument or look at the evidence
<enebo>
brixen: My only burden was to show that MRI have active contributors by a common metric (commits). I really feel I only have the burden of not-zero
<brixen>
also, "you have zero interest in acknowledging that contributions are contributions..." is ad hominem
<brixen>
don't impute my interest or motivations
<enebo>
heh
<tenderlove>
a few PRs isn't contributing, and number of commits doesn't seem to matter. I guess you can't win.
<enebo>
tenderlove: no one wins against brixen
<brixen>
put it in monetary terms and make your argument
<brixen>
there are ~20,000 specs
<tenderlove>
brixen: what is the criteria to be considered "a contributor"
<brixen>
a PR that changes one is 1/20,000
<brixen>
tenderlove: what would you define it to be?
<tenderlove>
brixen: doesn't matter what I think. *you* define the rules for this project, obviously
<brixen>
enebo: again, stop with the ad hominem or leave
<brixen>
tenderlove: why are you in this discussion?
<tenderlove>
I'm on the MRI team, I want to know
<brixen>
you want to know what?
<brixen>
what is your question?
<tenderlove>
brixen: what is the criteria to be considered "a contributor"?
<brixen>
ok
<brixen>
if you actually want to have this discussion, I have some questions
<brixen>
do you actually want to, or are you trolling?
<tenderlove>
ya, I actually want to know
<brixen>
ok, cool
<brixen>
so, what is the value of defining the term "a contributor"?
<tenderlove>
idk, you're the one using the word
<brixen>
no, I said contribute
<chrisseaton>
you said MRI and JRuby don't contribute - I don't believe that's true
<chrisseaton>
but I'm open to being convinced otherwise
<brixen>
since yugui said, MRI 1.9.2 won't ship until it passes rubyspec, MRI devs have contributed very very little, or not at all
<yopp>
yay, rubyspec fight!1
<brixen>
chrisseaton: go look at the commits in the past 2 years
<brixen>
a useful metric for contributor impact is not # of commits
<brixen>
it's # of current lines in the project
<chrisseaton>
would you at least agree it's hyperbole? that you meant they don't contribute as much as you think they should
<brixen>
part of the problem with rubyspec quality is letting people commit without adequate review
<brixen>
that costs the project a lot
<brixen>
tenderlove: are we discussing this or not?
<tenderlove>
my attention span is way too short for socratic dialogue
<tenderlove>
just tell me what we should be shooting for
<brixen>
I want to understand your opinion?
<brixen>
that's not valid?
<tenderlove>
my opinions don't matter. *you* define what are considered useful contributions to your project.
<brixen>
has MRI spec'd any features since 1.9.2?
goyox86 has joined #rubinius
<tenderlove>
¯\_(ツ)_/¯
amsi has joined #rubinius
<brixen>
and if they have, what is the % of features they spec'd versus features implemented
<brixen>
tenderlove: this isn't abstract
<brixen>
and your funny emoji isn't helpful
<brixen>
you attitude is obviously hostile
<tenderlove>
ok, so the yard stick for contribution is the % of spec'e features vs implemented featues?
<brixen>
the Thread::Backtrace::Location bug is a big deal
<brixen>
it breaks a lot of 4.1 apps
<brixen>
MRI doesn't even have a test for Thread::Backtrace::Location#path
<brixen>
and this is just one tiny case
* yopp
reseting "Ruby community without drama" counter
<brixen>
tenderlove: a useful metric for whether MRI is contributing is the % of specs they add for features they implement
<brixen>
tenderlove: do you disagree with that?
<tenderlove>
nope, it makes sense to me!
<brixen>
ok
<brixen>
so, how much has MRI contributed in the past 3-4 years?
<brixen>
any specs for ObjectSpace::WeakMap?
<brixen>
any specs for keywords?
<brixen>
any specs for Thread::Backtrace?
<brixen>
etc etc
<brixen>
I don't think I'm being unreasonable if you look at this metric
<brixen>
furthermore, matz could say, "use rubyspec"
<brixen>
he doesn't
<brixen>
it is what it is
<yopp>
Maybe it's time to crowdsource some devs, to do that?
<brixen>
yopp: please do!
<brixen>
and ensure they abide by my quality requirements
<jc00ke>
Do we know why Matz, et al, don't use or contribute to RubySpec? I'd sure like to know the reason, if there is one.
<jc00ke>
Sorry, didn't mean to use "contribute" like that. Meant more in the "actively" sense.
saline has quit [Remote host closed the connection]
<brixen>
chrisseaton: I made a comment on your PR
<yopp>
brixen, also planting a secret agents to MRI core might help :B
<brixen>
tenderlove: 2.1.5 still fails a keyword spec
<brixen>
tenderlove: despite opening tickets, despite the specs being there, etc
<jc00ke>
There has to be some barrier; what is it and how do we address it?
<brixen>
tenderlove: I recently tried to address the rubyspec failures on 2.1 and there are really obscure things that I can't find in redmine
<brixen>
tenderlove: it takes a ton of my time to do this because MRI devs don't contribute
<enebo>
brixen: or they no longer contribute
<brixen>
enebo: what is your point?
<brixen>
do they get perennial credit for having contributed?
<brixen>
is 1.9.2 still used?
<brixen>
it's not even supported by MRI any more
<brixen>
they don't contribute
<enebo>
brixen: most OSS people do get credit if the contributed at one time
<brixen>
present tense, relevant context
<chrisseaton>
brixen: (aside from the argument) are you happy with PRs that change spec names to correct spelling and grammar? I often see problems but not sure about changing them, because I guess it will invalidate people's tag files?
<brixen>
chrisseaton: all changes to improve the quality and clarity are needed
<brixen>
people can very easily retag
saline has joined #rubinius
<enebo>
brixen: I also think the fact they stopped is the crux of the problem and realizing they used to means something made them stop
<brixen>
enebo: so please go find out why
<brixen>
instead of blaming me
<enebo>
hmmm
<enebo>
brixen: ok well I said my piece whether you got anything from it or not. I am done…for now
<brixen>
enebo: it's interesting to me how quickly you defend whether other contribute
<chrisseaton>
well I'll put my money where my mouth is today and write some specs for #local_variables - is there a style guide?
<brixen>
enebo: you've implemented basically all of the jruby parser
<brixen>
I know how thorny eg keywords are
<enebo>
brixen: but I told you back then I stopped contributing because I did not like working with you. I do still encourage people contribute to rubyspec though. I say virtually every time I speak at a conference.
<brixen>
and know MRI tests don't cover the edge cases
<brixen>
enebo: I'm in #jruby
<brixen>
I see all the discussions
<enebo>
brixen: ok
<brixen>
it's as if there's an alternate reality
<brixen>
anyway, back to the original point
<brixen>
I have a budget of 24 hours every day
<brixen>
I have to make decisions about how to spend that in the context of what is actually valuable for rubinius
<brixen>
MRI devs clearly make a decision about what is valuable to them
<brixen>
enebo: as do you, whatever reason you want to label it with
<enebo>
brixen: I agree with that btw
JohnBat26 has quit [Ping timeout: 252 seconds]
<enebo>
brixen: My original statement said I think you should do what you feel wrt to rubyspec
<brixen>
|jemc-bot|: can you send me the creds for the Rubinius docker account, please
<brixen>
|jemc-bot|: you can use keybase.io if you have it, or I can send you an invite if you need it :)
<brixen>
cpuguy83: got a sec?
<cpuguy83>
brixen: Yep
<brixen>
cpuguy83: ok, sorry for going over this like the third time, but I'd like to get the docker situation squared away
<brixen>
and we tag a release, that will automatically build?
<brixen>
for Docker Hub?
<brixen>
cpuguy83: |jemc-bot| made an account for rbx
<cpuguy83>
brixen: If you want to have an account and an automated build yes. It would actually happen at every commit currently (limitation in DockerHub)
noop has joined #rubinius
<brixen>
ah hmm
<brixen>
that's gonna be a lot of builds
<brixen>
cpuguy83: what would be the best way to do only release tags?
<brixen>
could we have travis ping the docker hub hook on release?
<brixen>
instead of docker hub listening to github directly?
<cpuguy83>
brixen: Yes, indeed.
<brixen>
ah ok
<brixen>
any doc on that?
<cpuguy83>
one sec
<brixen>
sweet
<yopp>
brixen, what the most up to date ruby-building tool for rbx?
<yopp>
invalid option in RUBYOPT: -2 (RuntimeError)
<yopp>
:|
<brixen>
yopp: do you have a space in your directory name?
<yopp>
ah, it's just I'm an idiot
<brixen>
I've been considering adding support for EIDIOT :)
<yopp>
:D
<yopp>
okay, seems like keg version is running just fine
<brixen>
sweet
<yopp>
what should I do to get stats to grafana?
<brixen>
yopp: I'll be improving the key asap and hopefully get it back into official brew
<brixen>
yopp: just gotta kill Ruby from the build reqs
<brixen>
trying to get as far away from source building as possible on all platforms
<brixen>
yopp: er s/key/keg/
<brixen>
unfortunately, the recipe will have to be keg only but the option to brew link is decent
<brixen>
a more ambitious goal would be to get chruby to understand brew kegs
<brixen>
so it could select a ruby installed there (similar to detecting /opt/local or w/e)
* brixen
foods
<yopp>
nice idea
<yopp>
is there any way to check, that rbx connected to grafanadb?
<yopp>
hum
<yopp>
getting stats
<yopp>
but logging is broken: log writing failed. Device not configured
noop has quit [Ping timeout: 252 seconds]
goyox86 has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<brixen>
yopp: logging failed for which? rbx?
<brixen>
yopp: you can set logging to stdout/stderr
<brixen>
I think that's the docker way
<brixen>
yopp: -Xsystem.log=console
<yopp>
brixen, for our app when running under rbx
<brixen>
yopp: er ok
<yopp>
for some reason
<brixen>
yopp: what's it using for logging?
<yopp>
rails default logger
<yopp>
unicorn logging just fine
<yopp>
but seems like rails can't open file for some reason
<brixen>
rails default logger is SyslogLogger no?
<brixen>
yopp: which version of rbx?
<yopp>
rubinius 2.4.1
<yopp>
I've checked with 2.2.10 couple days ago, it was fine
<yopp>
let me check again
<brixen>
hmm
<brixen>
I will release 2.4.2 as soon as I fix this keywords issue
<brixen>
there are some important fixes in master
<yorickpeterse>
brixen: re rubyspec guidelines being ignored, I think we need to be much stricter on that matter. That is, if somebody submits a PR that doesn't match the requirements and doesn't really want to fix it, we close it
<yopp>
yep, it's working just fine on 2.2.10
<yopp>
and can't open logs on 2.4.1
<brixen>
yopp: any chance you could throw up a repo with the same rails version and logging setup?
<brixen>
yopp: if that repros it
<yopp>
let me try with blank rails app, but it might be anything, it's huge project with a lot of deps :|
<brixen>
yopp: ok
<brixen>
yorickpeterse: I have been, people bitch about that, too
<yorickpeterse>
brixen: well, then I'd say "fuck em"
<brixen>
I do ;)
<yorickpeterse>
brixen: perhaps this is Dutch honesty, but I couldn't care less about drive-by commits
slaught has joined #rubinius
<yorickpeterse>
I've dealt with those in the past for some of my own stuff, I just close them
<yorickpeterse>
if somebody can't be arsed to change a few bytes I can't be arsed spending 30 minutes reviewing and merging things
<yorickpeterse>
I'm personally very fond of closing things after a certain period (e.g. a month), but I'm reluctant applying that to rbx/rubyspec/rubysl unless we have some sort of consensus on the matter
<brixen>
yep
<brixen>
the problem with all the open PRs is that they will take a significant effort to make useful
<brixen>
generally, I just rewrite the specs at a certain point because that takes less of my time
<yorickpeterse>
well yeah, that's what I've done in the past as well: basically hijack what somebody was doing and do it right
<yopp>
ah, it was bundle issue
<yorickpeterse>
heh
<yorickpeterse>
where have we heard that before :P
<brixen>
yopp: what issue exactly?
<yopp>
with logging
<brixen>
heh
JohnBat26 has joined #rubinius
<brixen>
I guessed that much
<brixen>
can you describe it more than "bundle issue"?
<yopp>
I've started app without fucking bundle exec, so it used some random version of rails
<brixen>
sweet
<yopp>
but seems like it's working with rails 4.2.1!
<brixen>
cool
<yopp>
(apart of broken logging)
<brixen>
wait, logging is still broken?
<yopp>
No-no. with bundled deps it's working
<yopp>
Without bundled deps, with random gems, it's not.
<yopp>
hum
<yopp>
rbx responds in 1500ms, mri 2.1.2 in 250 :|
<brixen>
yopp: show me those stats :p
<yorickpeterse>
yopp: hit F5 a bunch of times
<brixen>
yopp: oh, you could try running with RBXOPT=-Xprofile
<yorickpeterse>
or run siege or something like that
<brixen>
start the app, run a few requests, exit the app, and you'll get the profile on stdout
<brixen>
show me that
<brixen>
yopp: if you're running "hello, world", I swear to god...
<brixen>
:p
<yopp>
:B
<yopp>
nope
<brixen>
I didn't think you were
<brixen>
anyone using Boundary?
<yopp>
where it will flush thre profiles?
<brixen>
the -Xprofile will write the results to stdout when the process exits
<yorickpeterse>
"Mongoid::Attributes#respond_to?" oh boy
<yorickpeterse>
But yeah, it looks like a lot of hashing is going on
<brixen>
yeah, thrashin' the hashin'
<brixen>
yopp: in 2.4.2 I'll be able to see more about how the JIT is working on that
<brixen>
yopp: so, could you save your test env so you can re-run for me?
<yorickpeterse>
yopp: can you run the app with -Xhash.hamt
<brixen>
you could try
<brixen>
but this is insertion heavy: 8.67 0.55 0.30 78974 0.00 0.01 Hash#new_bucket
<brixen>
and that's more expensive right now in HAMT
<yorickpeterse>
hm
heftig_ is now known as heftig
<yopp>
brixen, sure
<brixen>
down to 6 F on keywords
<yopp>
Yeah, it's building a lot of hashes
<yopp>
And one huge hash for xml
<brixen>
yopp: what is building them
<brixen>
which xml generator is used?
<yopp>
rabl, mongoid and serialization stuff
<yopp>
rabl + nokogiri
<brixen>
oh that thing
<yopp>
yeah, this pice of crap
<yorickpeterse>
Hm, I should probably benchmark how fast Oga is in _generating_ XML
<brixen>
yorickpeterse: uh yeah ;)
<yopp>
If my contract will be extended to next year, I'll try to fix rabl. Because I don't know why it takes 250ms to generate 25kb of xml
<yorickpeterse>
Granted it might be a bit unfair since it's just `Oga::XML::Element.new(:name => 'div').to_xml`
<brixen>
yorickpeterse: could you also fix rubygems so an Oga wrapper can "provide" Nokogiri?
<yorickpeterse>
brixen: I won't be providing a compatibility layer for Nokogiri
<yopp>
yorickpeterse, I can give you a hash
<brixen>
yorickpeterse: you don't have to
<yopp>
to serialize it to xml
<yorickpeterse>
brixen: or do you mean an adapter in RubyGems so it can use Oga?
<yorickpeterse>
(does RubyGems even use nokogiri?)
<yorickpeterse>
yopp: ah, that it can't do out of the box, you have to build the nodes yourself
<brixen>
yorickpeterse: no, I mean, fix rubygems so it's possible to specify that a different gem "provides" a dependency
<yorickpeterse>
brixen: euh, not sure if I'm following.
<brixen>
so that Rails dependency on nokogiri can be satisfied by oga-nokogiri
<yorickpeterse>
Hmm
<brixen>
it's a simple facility
<brixen>
using the new index metadata
<brixen>
and, of course, fixing dependency resolution to consider it
<yorickpeterse>
Well, I first have to fix my parser generator, then I have to fix the fkn aws-sdk (or replace it with their v2), then I have to fix a bunch of other things :P
<brixen>
haha
<brixen>
indeed
<brixen>
so, you'll need to prioritize your time
<yorickpeterse>
So maybe by next christmas
<brixen>
hmm, takes me back to an earlier conversation today
<brixen>
heh, next christmas is still only 2 days away :)
<yorickpeterse>
nah, tomorrow is spent on putting data through an entire new DB stack and having christmas brunch at the office
meh` has joined #rubinius
<yopp>
so rubygems are ended with xml?
pzol has joined #rubinius
<yorickpeterse>
ended with?
<yopp>
last time I've heard discussions about rubygems, it was about having plain text stuff
<yorickpeterse>
oh hm, I thought you were talking about the Dir.glob spec
<yorickpeterse>
heh
<yorickpeterse>
brixen: it's indeed not intentionally bad, but I'd say it's extremely lacking. That is, this would basically be the first, rough iteration of the spec
<yorickpeterse>
There's also some really questionable shit in there
<yorickpeterse>
e.g. why the heck is "Thread.pass if rand(100) >= 99" there
<yorickpeterse>
that has a 1% chance to run (assuming it were to be called 100 times at least)
<yorickpeterse>
err not sure, either way that line is really confusing
<yorickpeterse>
also the use of "::File.open" is odd since the specs are not namespaced
<yorickpeterse>
and I just can't figure out what it's actually meant to test
<yorickpeterse>
is it testing that it shouldn't raise "Errno::EEXIST"? that the file is simply there?
<yorickpeterse>
But yeah, this is basically where I draw a line and I'm not going to bother figuring it out, there's far too much going on
<yorickpeterse>
yay push done
<brixen>
yorickpeterse: yep
<brixen>
yorickpeterse: thanks for all the work on those
enebo has joined #rubinius
johnmuhl has joined #rubinius
<yorickpeterse>
all in a day's work
<yorickpeterse>
right I'm off for the night to dream about parser grammars and software bugs, toodles