Hello guys, i have a non-solidus related issue . I...
# support
j
Hello guys, i have a non-solidus related issue . I'm getting the following error on my the nginx logs trying to launch a solidus store. Any pointers would be greatly appreciated. Note: I have added
Copy code
gem 'stringio', '~> 3.0', '>= 3.0.2'
and still nothing. The error is as below.
Copy code
[ E 2022-09-23 18:36:08.4569 20124/T34 age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/deploy/BizDigital/current: The application encountered the following error: You have already activated stringio 0.1.0, but your Gemfile requires stringio 3.0.2. Since stringio is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports stringio as a default gem. (Gem::LoadError)
  Error ID: e672af7b
  Error details saved to: /tmp/passenger-error-YOCeFs.html
Thanks in advance.
t
I recently ran into this same error on one of our sites. I fixed it by adding the psych gem (a solidus_core dependency) to the gemfile, and locking it to a psych commit before they required stringio directly in the gemspec, and everything's working now. There may be a better fix, but this worked for me.
gem "psych", github: "ruby/psych", ref: "67ecafb0e2aed5974adff45280080eab1e25656d"
j
You just added it to your gemfile like that? It doesn't seem to go past bundle install.
Copy code
Fetching <https://github.com/ruby/psych.git>
Fetching gem metadata from <https://rubygems.org/>.........
Resolving dependencies....
Your bundle is locked to psych (4.0.5) from <https://github.com/ruby/psych.git> (at 67ecafb@67ecafb), but that version can no longer be found in that source. That means the author of psych (4.0.5) has removed it. You'll need to update
your bundle to a version other than psych (4.0.5) that hasn't been removed in order to install.
t
Ya, that was all I needed. Bundle install worked after that. Might need to look in your gemfile and confirm what is requiring psych and locking it to that version.
errr the lock file I mean
j
Worked like magic. I deleted the gemfile.lock and did a fresh bundle bundle then deployed. Thanks @Tyler Kocheff Appreciate the help
👍 1