Dave Myron
Dave Myron
I've actually been working on this the past couple days (it's coming as a side effect of handling dead connections to beanstalk). The first revision will use the existing hook...
@mexisme I see what you're saying with the conflation bit there. What it should probably do is pass the newly-minted Connection into the `work_one_job` method (which accepts an optional Connection...
@nesquena Memoizing the connection as a static/class variable seems to be causing several problems. What do you think about moving it strictly to an instance variable? Then no more problems...
Ran into this today myself (or at least uncovered it… sigh). I'm on Backburner 1.1.0 with beaneater ~> 1.0. I'm baffled by this. The only way that beaneater would say...
@boncey Do you have a repro case?
From beanstalkd's protocol.txt it states: > A client can delete jobs that it has reserved, ready jobs, delayed jobs, and jobs that are buried. > Unfortunately beanstalkd isn't verbose _enough_...
Working on the packet capture, but here's a stacktrace from my failure (using 1.1.0 and beaneater 1.0) – And yes, this be Windows... don't ask! ``` ruby E, [2015-10-01T21:17:09.196290 #2832]...
@geoffroymontel Once 1.1 goes out (today?) you'll be able to add hooks for `on_retry` and `on_bury`. Will those be sufficient?
Possibly. You mean killed killed, not just buried. They should work for timeouts though…
Is this something that can be handled on a project-basis with the `on_error` hook?