New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
better_errors swallows rescue_from #424
Comments
This is almost certainly an exception being raised inside of your The following results in "Rescued" being rendered to the browser.
The following results in Better Errors reporting a NameError for
I don't have an easy workaround, but if you |
Aha! I doubted you (because I was just doing a It's easy enough to disable |
Ran into the same issue. Was wrecking my brains, until decided to disable all my error / debugging gems in development and it finally worked. Then came across this issue. @RobinDaugherty Thanks for the suggestion. You were absolutely correct Better Error was eating up another error in rescue_from ( missing template) . Thank you! |
@brendon, can we make this permanent? I've done it on my fork, however, it should be default. |
@gencer, you'd need to talk to @RobinDaugherty :) |
oh sorry, wrong tag :) thanks for the correction. |
I'd love to fix this. It's a bit complicated though. Previously we showed the second error in the chain ( |
Very well, I only use it on development so I made my own fork and prefixed that condition with Until a solution found, I will fetch |
Just a note, this was fixed in Better Errors 2.7.0 (by #459). |
Hi there, I've noticed that
better_errors
intercepts the exception beforerescue_from
can get at it. This is on Rails 4.2 at least. Are you able to advise if there's a way around this?The text was updated successfully, but these errors were encountered: