-
Notifications
You must be signed in to change notification settings - Fork 548
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
strscan dependency/version #2410
Comments
I can confirm that this also happens when upgrading As a workaround, locking the This issue feels like it may be either closely related to or caused by #2409 |
I can confirm, locking the strscan version to 1.0.3 in my Gemfile works. Thanks @minivdweek. |
fixed, see: #2409 |
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
The commit 229ddea introduces a bug on Passenger: ``` App 2590953 output: Error: The application encountered the following error: You have already activated strscan 3.0.1, but your Gemfile requires strscan 3.0.3. Since strscan is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports strscan as a default gem. Gem::LoadError)() ``` A (temporary) workaround is to fix strscan to 3.0.1. The issue seems to be this one: phusion/passenger#2409 According to these issues, the best workaround is to use `PassengerPreloadBundler` in order to load right versions of gems. Ref phusion/passenger#2410 (comment)
The latest passenger include a new option to load ruby bundles earlier, working around deployment issues. See: * phusion/passenger#2410 * phusion/passenger#2409
Issue report
Question 1: What is the problem?
I expect my Rails app to run, like it has for years.
My Rails app does not run.
I upgraded (compiled from source) my Ruby from 2.7.4 to 2.7.5. I recompiled Passenger. I restarted Apache. I then get this error in the logs:
Question 2: Passenger version and integration mode:
Both 6.0.10 and 6.0.12 produce the same error for me.
Question 3: OS or Linux distro, platform (including version):
Debian 10, Apache 2.4.51
Question 4: Passenger installation method:
source tarball
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Rails 6.1.4, Ruby 2.7.5
Question 6: Are you using a PaaS and/or containerization? If so which one?
No.
Question 7: Anything else about your setup that we should know?
Ruby 2.7.4 works fine for me.
The text was updated successfully, but these errors were encountered: