Closed erikdstock closed 6 months ago
@erikdstock Thanks for reporting! There seems to be some stuff that I have to catch up on in terms of the Ruby GraphQL client. I'll look into this and see if I can solve the issue quickly.
It seems like the repo has been moved to github-community-projects/graphql-client. I have sent a PR https://github.com/github-community-projects/graphql-client/pull/10 as a pernanent fix for this.
I have also cut a new release of artemis
v1.0.0 that does not have any version constrants on the graphcl
gem, so you should be able to work around this issue by using the latest gems and the PR above:
gem "artemis", ">= 1.0.0"
gem "graphql-client", git: "https://github.com/github-community-projects/graphql-client.git", commit: "b177b19"
Edit 02/06/2024: The PR linked above has been merged and I have updated the gem declaration above.
It seems like the repo has been moved to github-community-projects/graphql-client.
Wow, how did you track this down?
There is a private Slack community for the people who purchased The Complete Guide to Rails Performance and a dozen of folks had a conversation about it.
@erikdstock I just wanted to check in and see if this is still an issue. Please let me know if you any other help. Thanks!
I'm closing this issue as I believe the deprecation warnings have been addressed in the new graphql-client
repo.
As of Rails 7.1 a certain logging call triggered by Artemis through the graphql-client gem is supposed to use kwargs, but it doesn't. As a result, a wall of deprecation warnings appear in logs.
To make matters worse, the
graphql-client
source repo disappeared recently which is strange since it was repo under the github org. Here is one of the last wayback machine snapshots. As the remaining hosted documentation notes, this library is just a thin wrapper around thegraphql
gem, so it might be worth moving off this completely.In our application we fixed this temporarily by adding a monkey patch to
config/initializers/graphql_client.rb
Here is a link from our investigations with another approach to the fix.
h/t @jonallured for help with the investigation and fix.