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

Async gem v2.14.2 breaks neo4j-ruby-driver #1722

Open
cguess opened this issue Aug 5, 2024 · 0 comments
Open

Async gem v2.14.2 breaks neo4j-ruby-driver #1722

cguess opened this issue Aug 5, 2024 · 0 comments

Comments

@cguess
Copy link

cguess commented Aug 5, 2024

I've also posted this bug here on the neo4j-ruby-driver repository, but the fix is also possible to (hopefully temporarily) be implemented here so I figured it's a good idea to cross-post.

The rehash, v2.14.2 of the async gem was released three weeks ago and updated the entire signaling process. Unfortunately this means the neo4j-ruby-driver gem breaks in a very obscure way unless you (as I did) dig through the backtrace of all the gems.

This results in an error that looks like

PageTest#test_page_node_requires_url_and_host_name:
ArgumentError: wrong number of arguments (given 0, expected 1)
    /Users/christopher/.rbenv/versions/3.1.4/lib/ruby/gems/3.1.0/gems/async-2.14.1/lib/async/queue.rb:85:in `signal'
    /Users/christopher/.rbenv/versions/3.1.4/lib/ruby/gems/3.1.0/gems/neo4j-ruby-driver-4.4.5/ruby/neo4j/driver/internal/handlers/pulln/auto_pull_response_handler.rb:6:in `signal'

A fix for a project is just to revert by adding gem "async", "2.12.0" to your project's Gemfile. I'm guessing adding the same dependency to the .gemspec file in this repo will equally fix this problem until the driver gem is updated. (I haven't had time to try this though)

Additional information which could be helpful if relevant to your issue:

Code example (inline, gist, or repo)

N/A Just use the regular onboarding setup

Runtime information:

Neo4j database version: 5
neo4j gem version: 4.4.5
neo4j-core gem version:

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

No branches or pull requests

1 participant