Scott Meves

Looks like the post describing the changes are here: http://sendgrid.com/blog/event-webhook-update-batched-vs-unbatched-events/ @adooylabs, want to take a stab and forking this and making a pull request to lee?

@mikemarsian pull requests are welcome! ;)

@mikemarsian @adooylabs I just dug into this a bit and as far as I can tell the API changes announced in February don't break this gem. It sounds like they...

@mikemarsian if you don't mind, give this branch a go: https://github.com/quikly/gridhook/tree/accept-plain-text That version will attempt parse the post body as JSON even if the json content-type header is not set.

I'm wondering why when sendgrid notifies my app it uses the proper content type, but @mikemarsian is seeing something different. I'm still using this gem in production and the sendgrid...

For an immediate fix you could try to roll back to ref: fcbd824c28ef5e87b51594830e2b977524368ec0 in your gemfile. If you can get a copy of the payload that is causing the error...

> I thought it should be cached if already called 🤔 > Also I;m wondering if we could break any existing ORM extension with such changes. Have to think In...

We have run into this quite a bit w/ webpack watcher; if we introduce a syntax error in our jsx code, webpacker-watcher spits out this error and hangs.

Has anyone been able to figure this out with Heroku CI? Our feature specs are currently failing as a result of this. I've run `heroku repo:purge_cache -a appname` but that...

> @stereoscott @vezzick's solution did not work for me. Heroku Support said to instead use the "Run Again Without Cache" option in the CI UI. This worked. > ![Heroku CI...