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
Cyclic restarts with prune_bundler
and Bundler.setup
(require
) and workers
> 1
#2319
Comments
prune_bundler
and Bundler.setup
(require
)prune_bundler
and Bundler.setup
(require
) and workers
> 1
I can't reproduce, I tried both with Ruby 2.6.6 + Bundler 2.1.2 and Ruby 2.7.1 + Bundler 2.1.4, on macOS 10.14. Code
|
Ruby 2.7.1 (rbenv), Arch Linux, Bundler 2.1.4. My code the same as your. Unfortunately, I even don't know how to debug, add some backtraces or verbose. There are no such options for |
@dentarg, please, ensure that you have |
I'm trying to debug. Working with
Even when I've added So, the problem in this block (or |
New info: the problem exactly in I've got ["/home/alex/.rbenv/versions/2.7.1/bin/ruby", "/home/alex/Projects/ruby/puma/bin/puma-wild", "-I", "/home/alex/Projects/ruby/puma/lib:/home/alex/Projects/ruby/extensions/x86_64-linux/2.7.0/puma-5.0.0.beta1", "nio4r:2.5.2", "-C", "puma.rb", {:close_others=>false}] and the result command for me looks like:
And it cyclic fails in the same way with the same output from I don't know how to debug further. |
Probably it's a simple recursion, what do you think? In any case, it looks like critical error. |
Yep, just simple check for |
What happens if you remove the following from Puma config? ## Require gems
require 'bundler/setup'
Bundler.require |
It works, but I require in real-life application another file, like |
Let's discuss this issue a bit more, please. The decision affect my web applications a lot. From here: https://github.com/puma/puma/blob/5d02e45/lib/puma/dsl.rb#L572-L585
In this context I'm not sure for what this options is. Like… Like… what about case if I want to update the Puma from v4 to v5, for example? Please, describe, for what cases this option, when conflicts (problems) will be possible and when everything will be 100% OK. |
But in the same time I guess |
Describe the bug
I'm trying to start a server via
pumactl
, but it fails in an infinity loop without backtraces:Puma config:
To Reproduce
Bundler.require
(or.setup
) +prune_bundler
+workers
> 1.Run it with:
Expected behavior
Server starts or some descriptive errors (once, not in a loop).
Desktop (please complete the following information):
4.3.5
and5.0.0.beta1
The text was updated successfully, but these errors were encountered: