-
Notifications
You must be signed in to change notification settings - Fork 601
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
Pry 0.13 prevents rails 6 from booting if also using Spirit Hands #2121
Comments
Try updating pry-byebug. The latest release of pry is incompatible with older versions of pry-byebug. See deivid-rodriguez/pry-byebug#287. |
I was also getting Also bumping Thanks for the solution @barrettkingram !, and for creating this issue @brandondrew . |
@barrettkingram That doesn't fix the issue for me. In order to get Rails to start, I must keep pry and pry-byebug back. Here's the output of
|
@brandondrew Any chance you can provide a sample rails app that reproduces the issue? Also worth double checking the problem isn't something that can be resolved by removing your bootsnap cache or disabling spring. |
Update from pry-byebug (3.6.0) -> pry-byebug-3.9.0.gem helps me. I had problem with running pry without rails |
Running pry in command line didn't work until update:
|
Just for some additional info, this is also an issue in Rails 3.2, it doesn't only effect newer Rails Versions. |
For anyone landing here from Google, updating |
This particular commit breaks
That happens because The solution is to either downgrade |
I selectively disabled other gems to see if any were creating this conflict as a side effect. I found that disabling Spirit Hands enables me to upgrade Pry to the latest version. However, if I limit the version of Pry, then I can use Spirit Hands. So I have two work-arounds. A. Remove Spirit Hands:
B. Use Spirit Hands & limit Pry:
I haven't investigated to see how or why there is a conflict between Spirit Hands and the latest version of Pry. So I can't say whether this issue should be closed or not. I'm updating the title to better reflect the situation. |
That sounds like a different issue. |
It's probably different from the issue that others wrote about here, but it is the issue that I originally reported. There was perhaps enough of a similarity between what I reported and what they experienced that there was a lot of discussion here about their issues, which appear to be different from mine. |
I took a quick look into spirit_hands, and it seems like the current issue is related to the removal of autoloading plugins made on #2119. This needs to be fixed on spirit_hands side in order to be compatible with newer pry versions. If I have some time tomorrow I'll send a PR there. |
After
bundle update pry
, which resulted in the following change:When I start rails, I get a long stack trace (which appears to strangely include more or less the same info twice):
I renamed my
~/.pryrc
file to eliminate the possibility that the problem is related to anything in there.The text was updated successfully, but these errors were encountered: