-
Notifications
You must be signed in to change notification settings - Fork 179
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
i get unexpected @path error. #374
Comments
Based on the backtrace, it fails on Could you run the following ?
|
Here's where it fails in Ruby itself: https://github.com/ruby/ruby/blob/0db68f023372b634603c74fca94588b457be084c/ext/pathname/pathname.c#L80-L81 This suggest somehow a |
The underlying bug can be reproed with: >> Pathname.new("/").tap { |p| p.instance_variable_set(:@path, nil) }.to_s
(irb):3:in `to_s': unexpected @path (TypeError) The question being what in your environment might be doing such a thing. |
@casperisfine Here's my output for
Edit: I managed to create a new project by following this workaround but I still get the same error while doing EDIT 2: Somehow the issue got resolved by removing all gems, installing rails (and dependencies) again and rehashing rbenv shims. Still uses bootsnap 1.9.1 so it probably isn't an issue of bootsnap. |
Well, another take on this issue: My problems start much later, i.e. when trying to deploy. The following is from the Capistrano log:
|
Hum, your pathname is loaded twice because of rubygems/rubygems#4992, it could be the root cause or not. Either way I'll be closing this because I'm pretty sure it has nothing to do with bootsnap. If you want to prove it, you can set |
Thanks for the pointer! |
Just for reasons of completeness: I purged all installations of and references to pathname version 0.2 on dev and server; afterwards I was able to deploy again. No idea, how this version had been installed in the first place; might have been a too careless |
Hello, i get this error when i run rails s . I use ruby 3.0.2 and rails 7.0.0.alpha2.
The text was updated successfully, but these errors were encountered: