-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Support for Rails 6.1 / Ruby 3.2 #785
Comments
@Timmitry happy new year! thanks for reporting! What version of Rails are you running? I'm curious because I upgraded my Rails 7.0 app and it went ok. |
We are using Rails 6.1.7. Hope that helps to find the issue, if not, I'm glad to provide more information 🙂 |
@Timmitry thank you, that's helpful. There is some incompatibility with earlier versions of Rails 6.0.x, but if you're on 6.1.7 🤔 Could you share your complete backtrace of the error? I'm curious why the Notifier is calling down into |
Hmm, this might be an issue with Rails. This looks very similar: rails/rails#46883 |
I think this PR will fix it: rails/rails#46895 |
Oh, that does indeed look like the problem. So it's not good job but rather the combination of Ruby 3.2 and Rails 6.1 that causes problems. Let's see if they fix it for Rails 6.1, otherwise we will just delay the Ruby update and first do the Rails update 🙂 Here's the stackrace, even though that should probably not be an issue anymore: Stacktrace
|
@Timmitry Can this issue be closed, as it's Rails related? |
@morgoth Yes, I think so, for people using Rails 6.1, the corresponding issue is linked, and as you said, it works with Ruby 3.2, so all good, thanks 👍 |
Hello and a happy new year!
I just tried to start GoodJob with the newly released Ruby 3.2 for my application, and it raises an error:
The error originates from this line:
good_job/app/models/good_job/lockable.rb
Line 75 in f683f37
Not really urgent, but just wanted to share this 🙂
The text was updated successfully, but these errors were encountered: