Actually, the heroku guys hooked me up, I thought I'd post here so google could find it. Basically it sounds like some weird environment thing that heroku does exposes a bug in hoptoad. The workaround is to add a line to your hoptoad initializer, so it should look like this :
HoptoadNotifier.configure do |config| config.api_key = <your key> config.environment_filters << 'async.' # workaround for hoptoad bug on heroku end On Tue, Feb 24, 2009 at 4:38 AM, Ryan Lemmer <[email protected]> wrote: > Hi Jeremy, I also suffer from this ailment - did you resolve your problem? > Ryan > > I was seeing this at doinlists and now I'm seeing it on another project. > > I installed hoptoad, I did the rake test and it successfully sent a message > to hoptoad. Then I pushed to heroku and did "heroku rake hoptoad:test" and > it again successfully sent to hoptoad, this time with a "production" > environment specified. But when I create an exception in my site, on > heroku, hoptoad never receives the notification. but, if I look at the > logs, the last thing after the exception is Hoptoad Success: Net::HTTPOK > > What's going on? > > Jeremy > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
