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

Incompatibility with graphql-ruby 2.0.18+ #87

Open
swrobel opened this issue Mar 19, 2023 · 2 comments
Open

Incompatibility with graphql-ruby 2.0.18+ #87

swrobel opened this issue Mar 19, 2023 · 2 comments

Comments

@swrobel
Copy link

swrobel commented Mar 19, 2023

It seems there was a breaking change introduced in 2.0.18 that causes use BatchLoader::GraphQL to cause the following exception:

vendor/bundle/ruby/3.2.0/gems/graphql-2.0.19/lib/graphql/schema.rb:944:in `tracer': Can't add tracer after configuring a `trace_class`, use GraphQL::Tracing::LegacyTrace to merge legacy tracers into a trace class instead.
  raise ArgumentError, "Can't add tracer after configuring a `trace_class`, use GraphQL::Tracing::LegacyTrace to merge legacy tracers into a trace class instead."
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ (ArgumentError)
from vendor/bundle/ruby/3.2.0/gems/batch-loader-2.0.1/lib/batch_loader/graphql.rb:10:in `use'
from vendor/bundle/ruby/3.2.0/gems/graphql-2.0.19/lib/graphql/schema.rb:243:in `use'
@chriswright47
Copy link

I'm also seeing this issue in my application. I am working around it for the moment by locking the graphql gem version to 2.0.17:

gem "graphql", "~> 2.0", "<= 2.0.17"

@sodabrew
Copy link

Is it broken specifically with that version, or with all onwards versions? (did graphql-rb revert this?)

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

3 participants