-
Notifications
You must be signed in to change notification settings - Fork 234
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
Bump to 7.2.0 #405
base: master
Are you sure you want to change the base?
Bump to 7.2.0 #405
Conversation
8d66e71
to
0ac2822
Compare
@@ -17,7 +17,6 @@ | |||
require_relative "postgis/oid/spatial" | |||
require_relative "postgis/oid/date_time" | |||
require_relative "postgis/type" # has to be after oid/* | |||
require_relative "postgis/create_connection" |
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.
This is the only actual needed change according to the current test suite, but I'm trying with the whole rails test suite to be sure we do not miss anything
@@ -3,7 +3,7 @@ require "rake/testtask" | |||
require_relative "test/rake_helper" | |||
|
|||
task default: [:test] | |||
task test: "test:postgis" | |||
task test: "test:all" |
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.
i think the whole suite is flaky.
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.
I'll look at it. I have good experience with this suite now that I maintain the CRDB adapter. It usually is flaky due to some tests modifying the db. Which they should not do if they are correctly changed for our use case. Do you have any further information?
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.
Just this : #378
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.
Thx, I plan on excluding using minitest-exclude
and opening an issue for excluded tests
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.
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.
Now we only have Postgis basic tests flaky. If one of you has time to look into it it would be much appreciated. Otherwise maybe we can skip them for now and make this or top priority issue, just so we can release this ?
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.
@BuonOmo so just to make sure I'm clear, there's a few postgis
tests that were working and are now flakey? I can try to work through some of them. Is it only in the CI?
@@ -10,16 +10,17 @@ Gem::Specification.new do |spec| | |||
|
|||
spec.version = ActiveRecord::ConnectionAdapters::PostGIS::VERSION | |||
spec.authors = ["Daniel Azuma", "Tee Parham"] |
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.
name should be updated and index matched with the emails.
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.
these are authors, I do not consider myself as author :/
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.
Normally, you keep the old authors and maintainers and prepend active ones.
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.
Not according to the specification reference:
**AUTHORS=(value)
A list of authors for this gem.
[...]
A contact email address (or addresses) for this gem
https://guides.rubygems.org/specification-reference/
I'd rather not mention myself as author unless I rewrite a significant portion of the gem alone.
@@ -99,20 +99,20 @@ def test_joined_spatial_attribute | |||
private | |||
|
|||
def create_foo | |||
Foo.connection.create_table :foos, force: true do |t| | |||
Foo.lease_connection.create_table :foos, force: true do |t| |
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.
these test case work in isolation
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.
What do you mean?
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.
I mean if you run any test that break alone, it works.
Something wrong with CI that we should fix.
Checkout https://github.com/nektos/act if you want to have your own github runner locally.
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.
Thanks for act, I am still unsure about your first point though..
Hey @BuonOmo! Thanks for the great work you've done so far on support for Rails 7.2! I've tried switching to this branch and upgrading to Rails 7.2. Here's the error I'm getting when I try to load my ActiveAdmin dashboard page, I don't know how to take it from here. I hope it's useful to you: Thanks! |
@vfonic I think your issue is not related to this adapter. To make sur of this you can replace the activerecord adapter with If it is related though could you open an issue with a reproducible example ? Or at least a stack trace and a gemfile.lock so I could investigate? |
Thanks @BuonOmo, I'll have a look. What do you mean by
? Thanks! |
@vfonic in your codebase, stop using |
Closes #403
Closes #395