-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
ago
isn't a method on Integers in ActiveSupport?
#1272
Comments
That's odd. Can you share a link to it being removed? |
I dove a bit further into it, and it appears that changing the way the duration variables are defined fixes the issue.
# Interval until the process record being updated
STALE_INTERVAL = 30.second # singularized it
# Interval until the process record is treated as expired
EXPIRED_INTERVAL = 5.minute # singularized it Not sure if that's an actual fix, or if I just somehow have something weird going on with |
I think something strange is going on with your ActiveSupport. I think this is where Rails patches Numerics with If |
Shoot, ok. That sounds like it might be a nightmare to track down. Thank you for your input, I'll try to figure out what's going on in my project. |
I just ran into the same issue. My app is running in a stripped-down API mode, and ActiveJob wasn't being loaded. After uncommenting |
I just installed
good_job
to try it out, and upon runningserver
for the first run, I was confronted with a looping wall of errors. It looks like there's a transactional database call that's failing and retrying infinitely due to the following error:[GoodJob] Notifier errored: NoMethodError: undefined method 'ago' for 30:Integer
located in
good_job-3.26.1/app/models/good_job/process.rb:135
Some light Googling suggests
ago
was removed from ActiveSupport at some point, and trying30.seconds.ago
in the Rails console also fails with the same message.The text was updated successfully, but these errors were encountered: