Skip to content
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

Can't see errors in templates #462

Closed
manuelmeurer opened this issue May 13, 2020 · 4 comments · Fixed by #463
Closed

Can't see errors in templates #462

manuelmeurer opened this issue May 13, 2020 · 4 comments · Fixed by #463

Comments

@manuelmeurer
Copy link

manuelmeurer commented May 13, 2020

With better_errors 2.7.0, when there's an error in one of my templates, this is what I see:

ActionViewTemplateError+at+slack_messages+2020-05-13+16-03-05

Obviously that's not really helpful because I don't see the actual error.

This is the same error with 2.6.0:

NoMethodError+at+slack_messages+2020-05-13+16-00-19

It correctly shows the error in the template.

@RobinDaugherty
Copy link
Member

Thanks @manuelmeurer this is fixed in release 2.7.1 of Better Errors.

(In future, please attach screenshots directly in GitHub instead of linking to an external site. I downloaded and attached the ones you linked to in your PR description.)

@manuelmeurer
Copy link
Author

Wow thanks for the super quick fix, @RobinDaugherty!

@manuelmeurer
Copy link
Author

@RobinDaugherty With 2.7.1, I don't see the live shell for ActionView::Template::Error errors:

ActionView:Template:Error at : 2020-05-15 17-09-43

With 2.6.0, it is there:

RuntimeError+at++2020-05-15+16-47-13

For non-ActionView::Template::Error errors, 2.7.1 shows the live shell correctly.
Do you want me to create a new issue for this?

@RobinDaugherty
Copy link
Member

RobinDaugherty commented May 15, 2020

Unfortunately, I noticed this after the new version was live. It's because the backtrace frame containing the context from the template itself is only present in the cause of the exception that was raised. I've opened #466 for this. I've been working on a big change that will allow us to navigate between causes (implementation of #464), which I hope to have out this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants