Timo Rößner

I am having the same problem and just stumbled across this GH issue by accidence - could you make this behaviour prominent in the README so that it is crystal...

Excellent summary. One more thing: i think right now the "success" callback is more of an "execute at the end" callback. I dont think we are checking there for any...

No problem, noted..:)

Sorry for the late reply, I kind of missed this one! > > I may want to propagate some exceptions and others I may want to handle in event_failed callback....

@jondecko @geoffgarside sounds excellent to me. Personally I am all on the "raise hell" side when it comes to invalid keys since imho it's too easy to make a mistake...

> > We just have to properly communicate that when/if this gets merged. Since we're following semantic versioning this shouldn't be a problem - we'd just bump up our gem...

I'm sorry but I really don't want to decrypt your description..:) Can you please state what the problem is exactly and what you would suggest in order to fix it?

I see. Good point, thanks for letting me know, I'll look into it.

Sounds like a legit bug. Unfortunately I'm on vacation currently and I have no idea when I can really look into it. Unless you come up with a pull request...

Yeah, that's most certainly a bug. Pull requests welcome!