-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Comments
🥳 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. |
@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. |
👋 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. |
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. |
@seuros it looks like the fix of require |
@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. |
Hi! What about releasing new version? |
Same Q here |
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:
And pointed activerecord-postgis-adapter to GitHub:
And my test suite produces the error reported in #402 :
I have some details that might be helpful that I'll share in that Issue. |
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. |
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
The text was updated successfully, but these errors were encountered: