-
Notifications
You must be signed in to change notification settings - Fork 124
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
Puma plugin causes warning about unresolved or ambiguous Gem specs #243
Comments
Sorry for the delay here, @MrSerth! I'll look into this one very soon. |
Don't worry @rosa, thanks for all the effort you put into Rails and open source software! |
In the end, we're going to keep the Puma plugin, so I'm going to reopen this one! 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working with the puma plugin, another issue could occur. Potentially, this issue is resolved together with #241. The issue is that pruning the bundler environment together with a
on_restart
directive causes issues withGem::Specification.reset
:I tested multiple combinations, but adding Solid Queue together with the puma plugin and configuring
on_restart
was the only combination this error occurred. As soon as either the gem or theon_restart
is removed, no warning is issued.Steps to reproduce:
rails new "solid_queue" -T --api --no-tests
gem "solid_queue"
bundle install
rails generate solid_queue:install
rails db:migrate
puma.rb
config:a. Configure
workers
to be used, i.e.workers 2
b. Add
prune_bundler
c. Add an (empty) block for restarts:
on_restart {}
d. Add the puma plugin with
plugin :solid_queue
rails s
Ruby: 3.3.2 +YJIT
Rails: 7.1.3.4
Puma: 6.4.2
Solid Queue: 0.3.3
The text was updated successfully, but these errors were encountered: