<snusnu>
cored: that'd be overkill i guess .. defining the "other" short rake task "replacements" in case flay is not available, is totally fine to be left in the rakefile
<snusnu>
cored: it's the logic that actually performs the flay run, that we're interested in
<snusnu>
cored: same goes for flog btw
<snusnu>
cored: "ideally" the code highlighted in the link above, could be replaced by something like Devtools::Task::Flay.call(config)
<snusnu>
mbj: btw, how's that develry renaming coming along? you're happy using the gems in your work?
<mbj>
snusnu: 99%
<mbj>
snusnu: Not in master, still a branch.
<mbj>
snusnu: But I'm happy.
<mbj>
snusnu: Will pull in master and will be part of tomorrows deployment.
<mbj>
snusnu: I dont expect any problems.
<snusnu>
mbj: is it split the way we were talking about? a develry gem plus a develry-gemfile gem?
<snusnu>
cored: that's a "weird" one .. weird in the sense that i've just recently seen the flay task fail on it (when run in isolation, rake ci still works fine)
<snusnu>
dkubb: hey
cored has quit [Ping timeout: 245 seconds]
cored has joined #rom-rb
mbj has quit [Read error: Connection reset by peer]
<cored>
snusnu: so there is a testing mechanism for this tasks
<cored>
snusnu: I tried to test it in isolation
<cored>
snusnu: probably I will have to write that code to sum up the rational numbers inside the masses array
<snusnu>
cored: there's no tes mechanism, no .. that's part of the reason we want to have them extracted, so that they can be tested more easily
<cored>
snusnu: the .sum is not part of an array as far as I can see
<cored>
snusnu: don't know how exactly is this working at the moment
<snusnu>
cored: what i meant is, i ran bundle exec rake metrics:flay recently (on the latest ice_nine PR) .. and i noticed that the task errored because of that exact line
<snusnu>
cored: when being run as rake ci tho, it works just fine
<cored>
oh
<cored>
I see
<snusnu>
cored: iirc dkubb wrote that code, he might remember ;)