<dpg>
I have it defined in another method (create) where the @post is floating around
<dpg>
I want it to join the channel, then post the title - url of the @post
<dpg>
then part
<dpg>
I also have another question about running cinch with delayed_job
<dpg>
(it doesn't work)
<dpg>
OOB.
<dominikh>
(I have no idea what delayed_job is). as for instance variables in that block, the block executes in a different context. but there's no need to use Bot.new with a block. you can do bot = Bot.new; bot.config.foo = bar; bot.start
<dpg>
then just access bot.config.foo by calling self.config.foo ?
<dpg>
from inside?
<dominikh>
I'm not sure what "inside" you're refering to since we eliminated the block
v0n has joined #cinch
<dpg>
I still have to ... snap you're right.
<dpg>
I need coffee.
<dpg>
delayed_job is a background job queuing process
<Cinchy>
[gist] gist:8718191 (at gist.github.com, ctwiz on 2014-01-30 20:37)
<dpg>
full trace*
<dpg>
ok cool. I'll take a look at it some more.
<dpg>
I appreciate the help. :)
<dominikh>
remind me of ruby stacktraces, top is the last call?
<dominikh>
what value exactly are you pushing into that queue?
<dominikh>
a bot instance?
<dpg>
yeah
<dpg>
bot.delay.start
<dpg>
so it serializes the data
<dpg>
s/data/object/
<dpg>
then runs it when it's available
<dominikh>
okay, thing is: that delay lib is calling respond_to? on the Bot. it passes two arguments, which apparently is possible since some time. our respond_to? (we overwrote it) only accepts one value. thus the exception
<dpg>
bot.start (hopefully)
<dpg>
ah.
<dpg>
alright. thanks. maybe I can submit a pull request?
<dominikh>
I could patch that (quicker than working on a PR), but I sort of don't feel like bumping the version for that :/ as a matter of fact I wonder why it calls respond_to?
<dpg>
no worries. I'll just fork it.
<dpg>
easier for me, and you won't have to worry about it.
<dpg>
I appreciate the help though. Thanks a ton. and great work on the code.
<dominikh>
meh, I'll push a new version
<dpg>
awesome. :)
<dominikh>
easier for both of us in case someone else runs into the same thing
<dpg>
sounds good.
<dpg>
you're a rockstar
<dpg>
this you on twitter? @dominikh
<dominikh>
nope
<dominikh>
I'm @dominikhonnef on there; but I hardly ever tweet
<dpg>
cool. following you anyways, just in case you want to one day. :)
<dominikh>
hehe
<dominikh>
looks like respond_to had that second argument for ages, so it's a bug in Cinch anyway
<CM-Punk>
So, any ideas?
<dominikh>
dpg: I pushed cinch 2.0.12 to rubygems; github will follow soon
<dpg>
cool thanks!
nOgAnOo has quit [Quit: Hard forks?! Hash Tables?! Someone tell me what's going on here!!!! I love you forever and always.]