-
Notifications
You must be signed in to change notification settings - Fork 276
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
Rails 7.1 Incompatibility #1702
Comments
@boone could you test activegraph 11.5.0.alpha.1? It has both zeitwerk migration and activesupport 7.1 compatibility. |
@klobuczek So far all I changed was to set the ActiveGraph gem to the new alpha and updated Gemfile.lock. Trying to start the Rails app I encountered:
I also noted the Does something else need to change in our app for compatibility with the alpha changes? Thanks! |
I just tried it as well. ActiveGraph version: 11.5.0.alpha.1 And I got this error:
|
I'm not a zeitwork expert, but I think you still need When I added |
@boone @jhulme-ut please have a look at 11.5.0.beta.2. The above issues should be fixed. Let us know if you find any further issues. |
Thanks @klobuczek that seems to be working now - tested against neo4j 4.4.26 The only issue I've run into is that a couple of queries are throwing an error:
And we weren't getting this error in update: fixed the issue in our data. And the error is gone now. We just needed to rename the schema migration nodes
|
I'm using activegraph-11.5.0.beta.2 with rails-7.1.2 and neo4j-ruby-driver-4.4.5 but still encounter a problem with missing rake tasks. The attached file shows what happens when
Commenting out the last two lines "fixes" the issue, and adding |
Just read through all your comments here as my attempt to use latest stable releases failed with this error:
the following combination doesn't mess with loading:
|
@georgkreimer the latest stable release is not compatible with the latest rails. We have been hesitant in putting upper limits on the activegraph gem dependencies as that puts more repressibility on our end to frequently retest and re-release. We are stretched thin here. At the moment it is your responsibility to put the upper limits in your Gemfile if you found an incompatibility. It will be mostly on rails gems. |
Everyone, please retest your cases with https://rubygems.org/gems/activegraph/versions/11.5.0.beta.3 |
@klobuczek I appreciate all the work you do! Edit: Yes, it works without neo4j-ruby-driver. And ActiveGraph 11.5.0.beta.3 work on latest rails and Neo4j 4.4.19. |
Everything seems to be working for me |
Hi, just wondering if there is an estimate of when 11.5 will be released |
still gives:
Updating to v.12 requires v5 of the driver:
resulting in:
but it looks like all of the neo4j-ruby-driver versions listed at rubygems after 4.4.5 require java, not the ruby-native driver. 🤷♂️ |
I am running a Rails 7.0 app with ActiveGraph 11.4.0 and see a deprecation warning when the app starts:
It references the line in
application.rb
which callsrequire 'active_graph/railtie'
.It looks like
ActiveSupport::PerThreadRegistry
is included here: https://github.com/neo4jrb/activegraph/blob/master/lib/active_graph/node/scope.rb#L147. Since that block of code references following ActiveRecord, perhaps whatever the latest ActiveRecord is doing could be used there as well?Thank you.
The text was updated successfully, but these errors were encountered: