-
Notifications
You must be signed in to change notification settings - Fork 505
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
Rails 5.2 + Puma doesn't work when Puma workers are enabled #511
Comments
Seems to be a duplicate of #489 |
@zainzafar did you figure this out? I have the same issue ... |
@knagode nop.. I stuck to Rails 5.1.x for now. Rails 6 has native support for multiple databases. |
@zainzafar After I added (
Octopus started working but I only can use it on dynos - I still have issues on worker dynos or rails console. |
@zainzafar how do you use octopus in gemfile? |
I did |
HI @zainzafar, I haven't used Octopus + Puma yet. I'll try to reproduce your error locally to see if I can fix it. Thiago |
Thanks @thiagopradi. This is the only gem that's preventing us to upgrade to Rails 5.2. Would love a fix to this. |
@thiagopradi looks like there is a number of issues opened related to this; any chance you could help? |
Any update on this @thiagopradi? |
@zainzafar - did you have any luck with this? |
Still running into issues with this. Tried using the branch from master as well as kevinjcoleman's branch, but having no luck. Anyone else figure this out?
We're using Puma and Rails 5.2.8.1 |
Don't want to speak too soon, but I might have fixed it with this:
|
Can you upgrade your rails to version 7? |
My environment:
Rails 5.2.0
Octopus: 0.10.1
Puma 3.12.0
The text was updated successfully, but these errors were encountered: