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

Inquiry on Rails 7.2 Support Effort #395

Open
seuros opened this issue Jun 3, 2024 · 12 comments · Fixed by #397 · May be fixed by #405
Open

Inquiry on Rails 7.2 Support Effort #395

seuros opened this issue Jun 3, 2024 · 12 comments · Fixed by #397 · May be fixed by #405

Comments

@seuros
Copy link
Contributor

seuros commented Jun 3, 2024

Hi everyone,

I wanted to check if anyone is currently working on adding support for Rails 7.2. If there is already an effort underway, I would love to know more about it and see if there's any way I can assist.

If no one is handling this task, I am planning to dedicate some time over the weekend to work on it.

Remember this will be again a breaking change since the new version will support just 7.2.x

@theonlyriddle
Copy link

🥳 This would be very helpful!

I just updated to Rails 7.2 and found that my application wouldn't boot up. We've tentatively narrowed down the culprit to this gem.

@anthony0030
Copy link

@seuros that would be sooo Cool, I was debugging an app all day yesterday and came to the conclusion that just changing the version number in this gem was not enough to get it working.

@ugisozols
Copy link

👋 I was also looking into this and got my Rails app booting with the changes in #396. I do not know if that's enough at this point as my Rails app needs many more updates to run on 7.2, so take it as is.

@keithdoggett
Copy link
Member

Hey everyone thanks for the help in getting this up! Unfortunately I will not have much time to contribute for the next few weeks but will have time to review/make a release once we have a working version.

@ugisozols thanks for starting the PR. I haven't reviewed it yet, but we can work off of that branch for now and if necessary I can make a different dev branch people can fork off of.

@BuonOmo
Copy link
Member

BuonOmo commented Jul 5, 2024

@seuros it looks like the fix of require rgeo/activerecord was not enough (https://github.com/rgeo/activerecord-postgis-adapter/actions/runs/9805704288/job/27075934099). Do you think you would have time to fix that ? I think We'll have to wait for this before we can ship unfortunately :/

@seuros
Copy link
Contributor Author

seuros commented Jul 5, 2024

@BuonOmo That a flaky test happening only in CI and don't affect runtime (the connection take some time to get established), restart the specific build it will pass.

As i said in the other discussion, i will fix it in a separate PR.

@StoneGod
Copy link

Hi! What about releasing new version?

@StoneGod
Copy link

@seuros Hi! what about release new version of gem? #403
rails 7.2 already released

@totus
Copy link

totus commented Aug 23, 2024

Same Q here

@seuros
Copy link
Contributor Author

seuros commented Aug 23, 2024

The code is already merged in this repo, if you could use github path to run you whole test suite that will be helpful.

We don't want to release something that is not battle tested.

The test suite is flaky, but works locally.

@JamesChevalier
Copy link

The code is already merged in this repo, if you could use github path to run you whole test suite that will be helpful.

We don't want to release something that is not battle tested.

The test suite is flaky, but works locally.

I bumped my Rails version in my Gemfile:

gem "rails", "~> 7.2.1"

And pointed activerecord-postgis-adapter to GitHub:

gem "activerecord-postgis-adapter", github: "rgeo/activerecord-postgis-adapter"

And my test suite produces the error reported in #402 :

TypeError:
  can't cast RGeo::Geographic::SphericalLineStringImpl

I have some details that might be helpful that I'll share in that Issue.

@mjy
Copy link

mjy commented Aug 23, 2024

For what it's worth we have a 7.2 unofficial PR branch in CI for our app, see SpeciesFileGroup/taxonworks#4006.

There are quite a few geo specs in the suite (though I wouldn't recommend them as a model for how to do things, we have another branch refactoring the whole approach), and the failures we do have seem unrelated.

@BuonOmo BuonOmo linked a pull request Sep 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
10 participants