jsullivandigs has quit [Remote host closed the connection]
francisfish has joined #ruby-lang
yfeldblum has quit [Read error: Connection reset by peer]
yfeldblum has joined #ruby-lang
Speed has joined #ruby-lang
fragamus has quit [Quit: Computer has gone to sleep.]
futilegames has quit [Quit: futilegames]
yfeldblum has quit [Remote host closed the connection]
yfeldblum has joined #ruby-lang
yfeldblum has quit [Ping timeout: 240 seconds]
futilegames has joined #ruby-lang
Pupeno_ has joined #ruby-lang
lolmaus_ has joined #ruby-lang
lolmaus has quit [Ping timeout: 255 seconds]
devgiant has joined #ruby-lang
Pupeno has quit [Ping timeout: 240 seconds]
mikecmpbll has joined #ruby-lang
robmiller has quit [Quit: Leaving.]
elliotec has quit [Remote host closed the connection]
relix has joined #ruby-lang
elliotec has joined #ruby-lang
Karql has quit [Remote host closed the connection]
Speed has quit [Ping timeout: 252 seconds]
Atw has quit [Ping timeout: 265 seconds]
Karql has joined #ruby-lang
whitecrow1 has joined #ruby-lang
yatish27 has quit [Remote host closed the connection]
yatish27 has joined #ruby-lang
yatish27 has quit [Read error: Connection reset by peer]
yatish27_ has joined #ruby-lang
elliotec has quit [Remote host closed the connection]
elliotec has joined #ruby-lang
yatish27_ has quit [Remote host closed the connection]
yatish27 has joined #ruby-lang
loincloth has joined #ruby-lang
yatish27 has quit [Ping timeout: 265 seconds]
Speed has joined #ruby-lang
lsegal` has quit [Quit: Quit: Quit: Quit: Stack Overflow.]
yatish27 has joined #ruby-lang
skade has quit [Quit: Computer has gone to sleep.]
loincloth has quit [Ping timeout: 265 seconds]
elliotec has quit [Remote host closed the connection]
elliotec has joined #ruby-lang
symm- has joined #ruby-lang
francisfish has quit [Remote host closed the connection]
Pupeno_ has quit [Remote host closed the connection]
Speed has quit [Ping timeout: 268 seconds]
robmiller has joined #ruby-lang
Pupeno has joined #ruby-lang
skade has joined #ruby-lang
yfeldblum has joined #ruby-lang
yfeldblum has quit [Read error: Connection reset by peer]
Pupeno_ has joined #ruby-lang
lcdhoffman has joined #ruby-lang
postmodern has quit [Quit: Leaving]
skade has quit [Client Quit]
Pupeno has quit [Ping timeout: 255 seconds]
mikecmpbll has quit [Quit: i've nodded off.]
mikecmpbll has joined #ruby-lang
Speed has joined #ruby-lang
toretore has joined #ruby-lang
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
mehlah has quit [Quit: Leaving...]
Pupeno_ has quit [Remote host closed the connection]
Pupeno has joined #ruby-lang
Kuda has joined #ruby-lang
Pupeno has quit [Ping timeout: 240 seconds]
Pupeno has joined #ruby-lang
cnivolle has joined #ruby-lang
Kuda has quit [Quit: Byebye!]
cnivolle has quit [Remote host closed the connection]
cnivolle has joined #ruby-lang
faces has joined #ruby-lang
relix has joined #ruby-lang
face has quit [Ping timeout: 240 seconds]
elliotec has quit [Remote host closed the connection]
elliotec has joined #ruby-lang
Pupeno has quit [Remote host closed the connection]
joelmheim has joined #ruby-lang
Coincidental has quit [Remote host closed the connection]
Pupeno has joined #ruby-lang
chouhoulis has joined #ruby-lang
Pupeno has quit [Remote host closed the connection]
Pupeno has joined #ruby-lang
elliotec has quit [Remote host closed the connection]
elliotec has joined #ruby-lang
kyb3r_ has quit [Quit: Leaving]
francisfish has joined #ruby-lang
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
cored has joined #ruby-lang
dvorak has joined #ruby-lang
mehlah has joined #ruby-lang
yfeldblum has joined #ruby-lang
solars has quit [Read error: Operation timed out]
yfeldblum has quit [Ping timeout: 265 seconds]
lcdhoffman has quit [Quit: lcdhoffman]
skammer is now known as skammer|afk
simono has joined #ruby-lang
Speed has quit [Read error: Connection reset by peer]
skade has joined #ruby-lang
cnivolle_ has joined #ruby-lang
fijimunkii has quit [Ping timeout: 265 seconds]
Speed has joined #ruby-lang
cnivolle has quit [Ping timeout: 246 seconds]
yalue has joined #ruby-lang
chouhoul_ has joined #ruby-lang
solars has joined #ruby-lang
elia has quit [Quit: Computer has gone to sleep.]
chouhoulis has quit [Ping timeout: 255 seconds]
benlovell has joined #ruby-lang
workmad3 is now known as wm3|lunch
Speed has quit [Read error: Connection reset by peer]
Speed has joined #ruby-lang
skammer|afk has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
chouhoul_ has quit [Remote host closed the connection]
heftig has joined #ruby-lang
<yorickpeterse>
How to solve timeouts, the Ruby way:
<yorickpeterse>
session.receive_timeout = 10000
* yorickpeterse
shakes cane
<yorickpeterse>
clearly if we set the timeout high enough the problem will go away
elia has joined #ruby-lang
<yorickpeterse>
ignoring that it's *rather* unlikely for a server to keep the connection almost 3 hours open
Speed has quit [Read error: Connection reset by peer]
Speed has joined #ruby-lang
<apeiros>
it's not only the ruby way
relix has joined #ruby-lang
<apeiros>
I'm quite sure the other side of one of our partner interfaces is java. it takes >90s sometimes. I complained; their suggested solution: increase your timeout.
<yorickpeterse>
lol
* yorickpeterse
actually cries
francisfish has quit [Remote host closed the connection]
luiz_lha has joined #ruby-lang
benlovell has quit [Ping timeout: 264 seconds]
kitak_ has quit [Remote host closed the connection]
kitak_ has joined #ruby-lang
skammer has joined #ruby-lang
domakesaythings has joined #ruby-lang
tbuehlmann has quit [Quit: Leaving]
shinnya has joined #ruby-lang
<darix>
yorickpeterse apeiros: you could solve the problem by using java, then your code would be just as slow and you wouldnt notice the difference anymore. ymmv
<yorickpeterse>
Plus it would run everywhere
<apeiros>
darix: the slow part might be in COBOL, should I write parts of my stuff in that too?
<yorickpeterse>
No, Cobol is too old
<yorickpeterse>
try Lisp
<apeiros>
cobold
<yorickpeterse>
at least HN will approve
<apeiros>
kobold
<yorickpeterse>
that is, if your comments make it out of the moderation queue
<darix>
yorickpeterse: there is actually still an active cobal development
<yorickpeterse>
because moderation queues are a great fucking idea
<apeiros>
I thought HN was the pathological never approving ground
cnivolle_ has quit [Remote host closed the connection]
rsl has joined #ruby-lang
cnivolle has joined #ruby-lang
yfeldblum has quit [Ping timeout: 255 seconds]
manyrus has quit [Ping timeout: 245 seconds]
banister has joined #ruby-lang
solars has quit [Ping timeout: 252 seconds]
Speed has quit [Read error: Connection reset by peer]
wm3|lunch is now known as workmad3
Speed has joined #ruby-lang
bradcliffe has joined #ruby-lang
rahul_j has quit [Quit: rahul_j]
Johz has joined #ruby-lang
simono has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
face has joined #ruby-lang
kgrz has joined #ruby-lang
faces has quit [Ping timeout: 264 seconds]
symm- has quit [Ping timeout: 246 seconds]
bloodyhistory has joined #ruby-lang
charliesome has joined #ruby-lang
Speed has quit [Read error: Connection reset by peer]
Speed has joined #ruby-lang
charlies_ has quit [Ping timeout: 246 seconds]
solars has joined #ruby-lang
solars has quit [Client Quit]
solars has joined #ruby-lang
<bloodyhistory>
Hi guys! I published my gem on rubygems.org and created yard documentation. But rubydoc.info don't load doc from my gem. It doesn't see it at all. But it works pretty good with github. Have you any ideas about the reason of that?
domakesaythings has quit [Quit: Computer has gone to sleep.]
rahul_j has joined #ruby-lang
gjaldon has quit []
<yorickpeterse>
You might want to contact the admins of rubydoc.info for that
<yorickpeterse>
lsegal runs it, might be able to contact him on Twitter/IRC
Coincidental has joined #ruby-lang
domakesaythings has joined #ruby-lang
Guedes has joined #ruby-lang
Guedes has left #ruby-lang [#ruby-lang]
chouhoulis has joined #ruby-lang
Coincidental has quit [Ping timeout: 255 seconds]
<bloodyhistory>
yorickpeterse: ok, try it. thaks
francisfish has joined #ruby-lang
tinyfont has quit [Read error: Operation timed out]
jgpawletko has joined #ruby-lang
[spoiler] has quit [Quit: Leaving]
<gnufied>
typo lord detected
dik_dak has joined #ruby-lang
<bloodyhistory>
oops
jgpawletko_ has joined #ruby-lang
jgpawletko has quit [Ping timeout: 251 seconds]
jgpawletko_ is now known as jgpawletko
kitak__ has joined #ruby-lang
chouhoulis has quit [Remote host closed the connection]
yfeldblum has joined #ruby-lang
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
whitecrow1 has quit [Quit: Leaving]
kitak_ has quit [Ping timeout: 260 seconds]
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
djking has joined #ruby-lang
yfeldblum has quit [Ping timeout: 265 seconds]
djking has left #ruby-lang [#ruby-lang]
nathanstitt has joined #ruby-lang
mykoweb has joined #ruby-lang
<yorickpeterse>
wat
Speed has quit [Read error: Connection reset by peer]
Speed has joined #ruby-lang
kitak__ has quit [Remote host closed the connection]
<gnufied>
partly true. But things specially get hairy with lazy nature of let and if expectation got cleared on next run. I have seen some weird cases before.
<yorickpeterse>
it's also not thread-safe
<gnufied>
of course.
<yorickpeterse>
which, if you're using threads in tests, is quite annoying
<gnufied>
but it has invaded the test suites of projects I work on
<yorickpeterse>
My current nemesis is FactoryGurl
<yorickpeterse>
"BUT IT'S SO EASY TO CREATE OBJECTS" - uses factory once
<yorickpeterse>
I wouldn't mind it if it wasn't for the obscure DSL it imposes
<yorickpeterse>
I'll take Object#new with 15 arguments over some deeply nested Factory with 15 after hooks any day
yfeldblum has joined #ruby-lang
<yorickpeterse>
Perhaps I'm getting old (= less of a young shit), only a matter of time before I start writing Lisp
dstynchula has joined #ruby-lang
bzalasky has quit [Remote host closed the connection]
robbyoconnor has quit [Ping timeout: 240 seconds]
<yorickpeterse>
I shouldn't complain too much though, at least this project has tests
<yorickpeterse>
And they're not that bad
<yorickpeterse>
Just, inconsistent
lolmaus_ has quit [Ping timeout: 246 seconds]
benlovell has joined #ruby-lang
1JTAAX36Q has quit [Ping timeout: 265 seconds]
<ndrst>
I have a love hate relationship with FG, on the one hand it's quite comfortable. but on the other hand it lures you into awful design decisions.
<ndrst>
and makes the whole test suite just slow
yfeldblum has quit [Ping timeout: 268 seconds]
<yorickpeterse>
1) slow 2) have to look up where the fuck things come from 3) DSL is a pain to grok 4) fucking objects please
RobertBirnie has joined #ruby-lang
<yorickpeterse>
Same arguments can be made against fixtures
Speed has quit [Read error: Connection reset by peer]
jds has quit [Quit: Connection closed for inactivity]
lolmaus has joined #ruby-lang
jsutt has joined #ruby-lang
Speed has joined #ruby-lang
<ndrst>
fixtures for what?
<yorickpeterse>
For tests
<yorickpeterse>
e.g. HTML fixtures
<ndrst>
I also don't understand why people want test their orm with their business logic.
bawigga has quit []
<ndrst>
you mean static html files to parse or json api responses?
<yorickpeterse>
For example
<yorickpeterse>
"want to test their orm with their business logic" eh?
bawigga has joined #ruby-lang
michaeldeol has joined #ruby-lang
<ndrst>
people who have a logic abstracted from their active record, but then still do all the calls of the AR model instead of mocking them away -> FG
pr0ton_ has joined #ruby-lang
<yorickpeterse>
oh right
<yorickpeterse>
Well, if you have DB logic you sure as hell *do* want to test that against a DB
<yorickpeterse>
otherwise you're testing the void
<ndrst>
true. but many people don't even know that this can be done. and even more are afraid of this
<ndrst>
but in that case I have tests that take care fo this layer for me
__butch__ has joined #ruby-lang
jsutt has quit [Ping timeout: 252 seconds]
cnivolle_ has joined #ruby-lang
elliotec has joined #ruby-lang
<ndrst>
but until know I haven't seen a proper engineered and testes rails app
<yorickpeterse>
well, part of that is because Rails doesn't exactly promote it
<yorickpeterse>
e.g. I had a bunch of test suites that were fast, now they're slow again
cnivolle has quit [Read error: No route to host]
cnivolle_ has quit [Remote host closed the connection]
<yorickpeterse>
in between autoloading, activerecurd magic, FactoryGurl and god knows what there's not much left that promotes you to write clean, separated code
<yorickpeterse>
I mean, the stuff is not strictly bad, it just could be done a lot better
cnivolle has joined #ruby-lang
<ndrst>
true. but I get mad when I see callbacks that create other objects or records...
<yorickpeterse>
e.g. this test suite I'm unclogging atm isn't bad, it works and it seems to test some of the important bits
<yorickpeterse>
But holy cow it's inconsistent
toastynerd has joined #ruby-lang
<yorickpeterse>
some times it uses let(), then it uses a global class ("Mock", nothing can break here), then it uses a single letter var with let()
<yorickpeterse>
then it uses double() in a before block
<yorickpeterse>
I know this thing was written rather hastely but ugh
<yorickpeterse>
it also tests nonsense things like the #initialize of a class that never raises anything
<yorickpeterse>
like, the tests will fail anyway so testing it on its own makes no sense
rippa has joined #ruby-lang
<ndrst>
well one could argue that you have a focused test to see whats the problem. but when all of them fail you most likely will oversee that little test anyways
<yorickpeterse>
in this case it's a method that literally sets an ivar, that's it
elliotec has quit [Ping timeout: 264 seconds]
<yorickpeterse>
It doesn't do anything on its own to raise errors, validate things, etc
<yorickpeterse>
If said method raises none of the tests will pass
<ndrst>
well. then it's quite useless
nhmood has joined #ruby-lang
<ndrst>
enough working for tonight
mykoweb has quit [Remote host closed the connection]
<Senjai>
yorickpeterse: Dude, I've been there
mykoweb has joined #ruby-lang
<Senjai>
yorickpeterse: I had to raise a project from 10% coverage to 82% (so far) of horrible horrible code.
<Senjai>
Before we refactor it
Lewix has joined #ruby-lang
simono has quit [Read error: Connection reset by peer]
simono has joined #ruby-lang
<yorickpeterse>
haven't checked yet what the coverage is on this one
<yorickpeterse>
but I don't take coverage too seriously
<yorickpeterse>
That is, the literal number
toastyne_ has joined #ruby-lang
<yorickpeterse>
Since having 100% code coverage doesn't actually mean that you test 100% of teh code
cnivolle_ has joined #ruby-lang
<yorickpeterse>
It just happens to be that 100% *runs*
tharindu has joined #ruby-lang
mykoweb has quit [Ping timeout: 265 seconds]
<yorickpeterse>
I'd be interested in a system that would measure how much you *actually* test, but it would be pretty hard to create
cnivolle has quit [Ping timeout: 246 seconds]
nhmood has quit []
toastynerd has quit [Ping timeout: 268 seconds]
toastyne_ has quit [Remote host closed the connection]
<yorickpeterse>
as a start you'd have to only measure direct method calls
<yorickpeterse>
That is, a method called directly from a test counts up
retro|cz has quit [Ping timeout: 264 seconds]
<yorickpeterse>
but a method called from said method does not (assuming it's public)
macmartine has quit []
scampbell has joined #ruby-lang
iTrojan has quit [Ping timeout: 264 seconds]
hinbody has quit [Ping timeout: 240 seconds]
postmodern has joined #ruby-lang
thang__ has joined #ruby-lang
diegoviola has joined #ruby-lang
Atw has joined #ruby-lang
yfeldblu_ has joined #ruby-lang
thang__ has left #ruby-lang [#ruby-lang]
Lewix has joined #ruby-lang
yfeldblum has quit [Ping timeout: 265 seconds]
robmiller has quit [Quit: Leaving.]
fijimunkii has quit [Read error: Connection reset by peer]
fijimunkii has joined #ruby-lang
<yorickpeterse>
e.g. say you have method A and B. A calls B and only A is tested
<yorickpeterse>
in that case one assumes B works
<yorickpeterse>
but it's not directly tested on its own
<yorickpeterse>
Yet code coverage tools would report 100% code coverage
<yorickpeterse>
The C0-4 stuff looks interesting though
mehlah has quit [Quit: Leaving...]
rahul_j has quit [Ping timeout: 245 seconds]
cored has joined #ruby-lang
cored has quit [Changing host]
cored has joined #ruby-lang
rondale_sc has quit [Ping timeout: 240 seconds]
Evanescence has quit [Ping timeout: 246 seconds]
TheMoonMaster has quit [Read error: Operation timed out]
rahul_j has joined #ruby-lang
simono has joined #ruby-lang
Lewix has quit [Remote host closed the connection]
lcdhoffman has quit [Quit: lcdhoffman]
arBmind has quit [Quit: Leaving.]
dfr|test has quit [Ping timeout: 240 seconds]
benlovell has joined #ruby-lang
dwknoxy is now known as dknox-lunch
Pupeno has quit [Ping timeout: 264 seconds]
yatish27 has quit [Remote host closed the connection]
yatish27 has joined #ruby-lang
Evanescence has joined #ruby-lang
bawigga has quit []
bawigga has joined #ruby-lang
riffraff has joined #ruby-lang
<apeiros>
yorickpeterse: ah, I see.
yatish27 has quit [Ping timeout: 252 seconds]
centrx has joined #ruby-lang
bawigga has quit [Client Quit]
riffraff has quit [Client Quit]
skade has joined #ruby-lang
loincloth has quit [Remote host closed the connection]
Coincidental has joined #ruby-lang
bawigga has joined #ruby-lang
dfr|test has joined #ruby-lang
brianpWins has joined #ruby-lang
richardardrichar has joined #ruby-lang
bloodyhistory has joined #ruby-lang
bloodyhistory has quit [Client Quit]
dluv has quit [Ping timeout: 265 seconds]
GaelanAintAround has quit [Ping timeout: 265 seconds]
jsutt has joined #ruby-lang
zz_dlu has joined #ruby-lang
dfr|test has quit [Ping timeout: 240 seconds]
GaelanAintAround has joined #ruby-lang
brettweavnet has quit [Ping timeout: 245 seconds]
bawigga has quit []
bawigga has joined #ruby-lang
<havenwood>
The `active_support` gem needs to go away. So nasty. ActiveSupport lets you require `active_support` or `activesupport` but gem with the underscore is hard-linked to an old version.
<havenwood>
yxhuvvd: 33 million happy Rails users, a quarter million extremely confused people who try to get the latest ActiveSupport and get one that is years old. :O
<yxhuvvd>
that page doesn't say when they were downloaded though.
iTrojan has joined #ruby-lang
francisfish has quit [Remote host closed the connection]
<havenwood>
good point, but i'd imagine it has been pretty steady with people accidentally doing a `gem install active_support`, since you can `require 'active_support'` with the real ActiveSupport. But yeah, dunno.
yfeldblum has quit [Remote host closed the connection]
elia has joined #ruby-lang
lamb0o has joined #ruby-lang
yfeldblum has joined #ruby-lang
symm- has quit [Ping timeout: 252 seconds]
michaeldeol has joined #ruby-lang
loincloth has joined #ruby-lang
brettweavnet has joined #ruby-lang
rahul_j has quit [Quit: rahul_j]
yfeldblum has quit [Ping timeout: 255 seconds]
arBmind has joined #ruby-lang
toastynerd has quit [Remote host closed the connection]
tylersmith has quit [Ping timeout: 255 seconds]
AncientAmateur has quit [Remote host closed the connection]
ascarter has joined #ruby-lang
Speed has quit [Read error: Connection reset by peer]
Speed has joined #ruby-lang
TheMoonMaster has joined #ruby-lang
robmiller has joined #ruby-lang
diegoviola has quit [Quit: WeeChat 0.4.3]
dfr|test has joined #ruby-lang
Fushi has quit [Quit: Connection closed for inactivity]
tylersmith has joined #ruby-lang
robmiller1 has joined #ruby-lang
havenwood has quit []
<yorickpeterse>
ugh, activesupport
BeingUntoDeath has joined #ruby-lang
tharindu has quit [Read error: Operation timed out]
<yorickpeterse>
I always forget whether it's `require 'active_support'` or `require 'activesupport'`
<yorickpeterse>
s/whether/if
michaeldeol has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
robmiller has quit [Ping timeout: 264 seconds]
MichD is now known as michd
<apeiros>
it's require 'aktive_unterstützung'
<yorickpeterse>
hahaha
<yorickpeterse>
while we're at it
<yorickpeterse>
vereis 'actieve_ondersteuning'
<apeiros>
ah, left that part out…
<yorickpeterse>
I still need to find that Gem that basically let you do stuff such as 'User.fucking_new(...).fucking_sign_in'
<yorickpeterse>
can't remember the name
<apeiros>
I'd call such a gem fucking_ruby
<yorickpeterse>
also I just deployed our April fools prank, I wonder how many angry calls I'll get tomorrow
<apeiros>
^^
<yorickpeterse>
(changed the layout of our management backend to geocities)