Skip to content
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

Draft
wants to merge 22 commits into
base: master
Choose a base branch
from
Draft

Bump to 7.2.0 #405

wants to merge 22 commits into from

Conversation

BuonOmo
Copy link
Member

@BuonOmo BuonOmo commented Sep 4, 2024

Closes #403
Closes #395

@BuonOmo BuonOmo marked this pull request as ready for review September 4, 2024 12:10
@BuonOmo BuonOmo force-pushed the bump-7-2 branch 4 times, most recently from 8d66e71 to 0ac2822 Compare September 4, 2024 12:19
@BuonOmo BuonOmo changed the title Bump 7 2 Bump to 7.2.0 Sep 4, 2024
@@ -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"
Copy link
Member Author

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"
Copy link
Contributor

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.

Copy link
Member Author

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just this : #378

Copy link
Member Author

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BuonOmo yeah I hadn't figured out how to replicate the exclusions like in the CRDB adapter, but we definitely need that here since some are failing (which is expected). But to @seuros 's point that's why I just left the postgis tests for now.

Copy link
Member Author

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 ?

Copy link
Member

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"]
Copy link
Contributor

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.

Copy link
Member Author

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 :/

Copy link
Contributor

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.

Copy link
Member Author

@BuonOmo BuonOmo Sep 5, 2024

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.

[...]

EMAIL

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|
Copy link
Contributor

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean?

Copy link
Contributor

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.

Copy link
Member Author

@BuonOmo BuonOmo Sep 5, 2024

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..

@vfonic
Copy link

vfonic commented Sep 10, 2024

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:
Screenshot 2024-09-10 at 14 25 49

Thanks!

@BuonOmo
Copy link
Member Author

BuonOmo commented Sep 11, 2024

@vfonic I think your issue is not related to this adapter. To make sur of this you can replace the activerecord adapter with postgresql and see if you still have the failure.

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?

@vfonic
Copy link

vfonic commented Sep 11, 2024

Thanks @BuonOmo, I'll have a look.

What do you mean by

replace the activerecord adapter with postgresql and see if you still have the failure.

?

Thanks!

@BuonOmo
Copy link
Member Author

BuonOmo commented Sep 12, 2024

@vfonic in your codebase, stop using active-record-postgis-adapter, and in your database configuration file (likely database.yml) set postgres instead of postgis. And check if this error still occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inquiry on Rails 7.2 Support Effort
4 participants