Not showing appropriate stack trace or file location with Rails 5.1

[niedfelj]

Not sure what's going on here, but an example putting <%= hi %> in a template in 5.0:

And in 5.1:

[niedfelj]

It seems to be limited to errors in templates/render code

[niedfelj]

@charliesome Are you still maintaining this?

[kobaltz]

I noticed this as well and confirmed it's still an issue in Ruby on Rails 5.1.1

[niedfelj]

@kobaltz I was going to try to fix this today, and then when I did a checkout and local bundle config, it started working...very strange, but I've tested in a new rails 5.1.1 project in addition and switched back and forth between published gem and the git/master branch and can confirm that using the git method in the Gemfile seems to make it work. Can you confirm also?

  gem 'binding_of_caller'
  gem 'better_errors', git: 'https://github.com/charliesome/better_errors.git', branch: 'master'

I even tried using the published better_errors.gemspec for 2.1.1 in a local checkout (that was the only file that was different) and it still worked, so maybe this is a bundler issue?

Here's my local setup:

ruby 2.4.1
rails 5.1.1
bundler 1.14.6
rubygems 2.6.11
mac os 10.12.4

[kobaltz]

@niedfelj It did work with the https://github.com/charliesome/better_errors source. Thanks.

[dsfernandobond]

Had the same problem, using https://github.com/charliesome/better_errors fixed it for me too thanks.

[inopinatus]

Thanks! This was making debugging of partials really painful.

[rept]

Working now with master branch!

[RobinDaugherty]

Sounds like this was fixed by #354. New release of the gem will be coming soon.

[RobinDaugherty]

Version 2.2.0 of the gem has been released, so this issue seems to be fixed.

[paneq]

Not fixed for me unfortunately :(

• rails 5.0.6
• ruby 2.5.1p57

[RobinDaugherty]

@paneq @golddiga this issue was for Rails 5.1. Rails 5.0 hasn't had this issue reported. But in my testing with Rails 5.0.6 on Ruby 2.5.1 and an ERB template, I'm getting the correct location. Can you open a new issue with some more information on how to reproduce your issue?