Steven! Ragnarök

Is this something Grape is interested in? If so I'll definitely do what I can.

Unfortunately work got really busy right after posting this. But I've set aside this whole weekend for improving the open source tools behind my work projects. So I will take...

I added failing test cases [here](https://github.com/nuclearsandwich/grape/commit/fb512eb52b503cb087988e7f0bb0f331d8a18840) and [here](https://github.com/nuclearsandwich/grape/commit/06348a4f2db782ff9025b4fd5e6d88c44da6ac86). Working on a fix now based on presskey's suggestion.

I was spelunking `lib/grape/api.rb` and `lib/grape/endpoint.rb` and was getting worried that the only way to keep the helpers up to date for every new request would be to delay evaluation...

Based on what I saw, using a `Grape::Context` object to organize those settings seems like a good way to go. But I'm pretty sure that no `compile!`method will be needed...

@mbleigh, have you started working on this? I'm taking a stab at implementing `Grape::Context` this weekend for GoGaRuCo.

> Do you happen to have any suggestions (maybe a compile flag or sorts) to avoid this issue, and make our build jobs more stable, I'm happy to investigate what...

> @nuclearsandwich: I'm curious, would a change to Rolling failure notifications be possible? Rolling is unique among distributions where notifications about failures due to upstream packages should be less liberal...

> > `SteveMacenski:` Can you expand on that a little more? Where would we setup this filter? > `Timple:` Sounds like a personal email rule which simply trashes the rolling...

> Should I release and then get some rule or how do you want to play this? Well I actually sat down to export one of my existing gmail filters...