-
Notifications
You must be signed in to change notification settings - Fork 117
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
Tapioca errors when upgrading from GoodJob 4.0.1 to 4.0.2 #1950
Comments
Does it error if you run |
It does not error:
|
I was poking at lib/active_record/type.rb:50 and noticed the last commit was from attribute should not require a connection is established (rails/rails#41302) which seems to indicate a regression in Rails? |
Indeed, I believe it is a rails bug as well. I've openend rails/rails#52311. Why it works in a console, I'm fairly sure it has something to do with it calling |
Thanks a bunch @Earlopain, I'll close this and we can continue on the Rails issue you opened. |
I think this is a Tapioca issue and not a GoodJob one.
I'm upgrading GoodJob to 4.x. I upgraded to 3.99 and ran all the migrations per the instructions.
tapioca gem
andtapioca dsl
run without issue with GoodJob 4.0.0 and 4.0.1, but 4.0.2 causes aConnectionNotEstablished
error (see below for backtrace) when running these Tapioca commands.I double checked Postgres is still running 😉 and it is. The
good_job-4.0.2/app/models/good_job/discrete_execution.rb:18
line before going into Active Record code points to theattribute :duration, :interval
line that shipped in bensheldon/good_job#1408 as part of the 4.0.2 release. Since that line seems to be for Rails 6.1 only, I made it conditional and the problem went away: bensheldon/good_job#1412Backtrace:
The text was updated successfully, but these errors were encountered: