-
Notifications
You must be signed in to change notification settings - Fork 21.7k
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
Fix pg 1.5.0 deprecation warning #48048
Conversation
@yahonda Looks like the test failures are somehow related to the pg gem upgrade, so there might be some bigger problems than only deprecation warning. |
Right. We will need to address these two failures with pg 1.5.0 gem. https://buildkite.com/rails/rails/builds/95886#0187b335-ed2c-4532-8176-68ae11d2a67f/1076-1087 Failure:
BasicsTest#test_preserving_time_objects_with_time_with_zone_conversion_to_default_timezone_local [/rails/activerecord/test/cases/base_test.rb:324]:
--- expected
+++ actual
@@ -1 +1 @@
-Sat, 01 Jan 2000 00:00:00.000000000 CST -06:00
+2000-01-01 01:00:00 UTC
bin/rails test /rails/activerecord/test/cases/base_test.rb:317
........................................F
Failure:
BasicsTest#test_preserving_time_objects_with_utc_time_conversion_to_default_timezone_local [/rails/activerecord/test/cases/base_test.rb:310]:
Expected: 2000-01-01 00:00:00 UTC
Actual: 1999-12-31 19:00:00 UTC
bin/rails test /rails/activerecord/test/cases/base_test.rb:304 |
Opened #48049 for these two failures. |
Yes, please fix it. |
Gemfile.lock
Outdated
@@ -358,7 +358,7 @@ GEM | |||
parser (3.2.1.1) | |||
ast (~> 2.4.1) | |||
path_expander (1.1.1) | |||
pg (1.4.5) | |||
pg (1.5.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, this change is not required since Rails CI will remove the Gemfile.lock
and perform a bundle install
, but for clarity, Let's change the pg gem version to 1.5.1 that includes the fix for #48049
https://github.com/rails/buildkite-config/blob/cde08283a7f570c1b0185eb626f835e393350801/Dockerfile#L134
@yahonda I updated the pg version |
Thank you for the fix. |
Fix pg 1.5.0 deprecation warning
Backported to 7-0-stable branch via 71503fb |
@yahonda This issue is preventing new projects from running properly, are you going to patch the current gem today?
|
No, I do not think so. You can use the |
FYI Rails 7.0.5 has been released that includes this fix
|
Thanks a lot. |
Will this be applied to Rails 6 as well? |
Thanks @morgoth |
Fix pg 1.5.0 deprecation warning
@iraszl It won't. Rails 6.1 only receives security fixes (see #48435 (comment)). You could use the version in #48435, but you're probably better off putting in the effort to upgrade to rails 7.0 (or temporarily downgrade |
We stopped upgrading due to deprecation notices in Rails. See #21271 (comment) But pg 1.5.3 and Rails 7.0.5 should have fixed the issue. See rails/rails#48046 (comment) and rails/rails#48048 (comment)
We stopped upgrading due to deprecation notices in Rails. See #21271 (comment) pg 1.5.3 and Rails 7.0.5 should have fixed the issue. See rails/rails#48046 (comment) and rails/rails#48048 (comment)
Closes #48046
/cc @yahonda