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

uninitialized constant BetterErrors::Middleware::VERSION (NameError) #483

Closed
seb-sykio opened this issue Oct 2, 2020 · 7 comments
Closed

Comments

@seb-sykio
Copy link

 3: from .rvm/gems/ruby-2.6.5/gems/better_errors-2.8.2/lib/better_errors.rb:9:in `<top (required)>'
 2: from .rvm/gems/ruby-2.6.5/gems/better_errors-2.8.2/lib/better_errors/middleware.rb:7:in `<top (required)>'
 1: from .rvm/gems/ruby-2.6.5/gems/better_errors-2.8.2/lib/better_errors/middleware.rb:28:in `<module:BetterErrors>'

.rvm/gems/ruby-2.6.5/gems/better_errors-2.8.2/lib/better_errors/middleware.rb:43:in `class:Middleware': uninitialized constant BetterErrors::Middleware::VERSION (NameError)

ruby 2.6
rails 4.2.11.3

@frobert
Copy link

frobert commented Oct 2, 2020

Same here after update :/

Rails 6.0.3.3
Ruby 2.7.1

@joker-777
Copy link

Same for me!

@frobert
Copy link

frobert commented Oct 2, 2020

Duplicate of #482

@afuno
Copy link

afuno commented Oct 2, 2020

Same

jcoglan pushed a commit to UKGovernmentBEIS/beis-report-official-development-assistance that referenced this issue Oct 2, 2020
There is a bug in better_errors 2.8.2, where it uses its VERSION
constant without having loaded it first [1]. This is preventing our app
from booting so I'm reverting this version bump until that issue is
fixed.

This reverts commit a6e2172, reversing
changes made to ce4f953.

[1]: BetterErrors/better_errors#483
@jcoglan
Copy link

jcoglan commented Oct 2, 2020

I believe this change is the source of the problem: referring to VERSION without having explicitly loaded that constant. It's stopping our Rails app from booting.

https://github.com/BetterErrors/better_errors/compare/v2.8.1..master#diff-5e3c1d57ea649185a86b730f951f5a18R43

@addisonmartin
Copy link
Contributor

I've submitted a fix:
#480

@RobinDaugherty
Copy link
Member

Very sorry for my mistake everyone, release 2.8.3 fixes this and is live (and I tested it in an app). Thank you @addisonmartin and @peaonunes for the PRs!

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

No branches or pull requests

7 participants