It was happening all the time. I ended up switching to resque & resque- scheduler to try and debug (which gave me a new error). Through that process I realized that heroku is on bundler 1.1.x while I had 1.0.x locally. That (and heroku's support) helped me to track down the resque issue.
Any one that has a similar issue I'd suggest checking the log file after you push to heroku and make sure you're running the same version of bundler. 1.1 isn't stable yet and it does some strange things still. On Oct 17, 11:09 pm, Jonathan Owens <[email protected]> wrote: > We get this happening in Resque sometimes and restarting the worker seems to > clear it up. Still annoying though. Have you ever gotten this to run > successfully or does it fail immediately? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
