You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm coming back up to speed on project I wanted to run importer to make sure we were up to date. I haven't run the importer in a very long time. When I ran it tonight, I got an error message related to the realms API. Looks like we were using a graphql endpoint. When it runs, I get an error in the response, "PersistedQueryNotSupported". I couldn't find documentation anywhere even about this API so it's hard for me to 'fix'. From the looks of it, maybe its possible they no longer support unauth'd requests.
If I can get verification from someone who is familiar that would be great. If that is the problem I can make a change to use the blizzard api with token, and maybe move it to not run by default, and when requested to run, take the token as an argument. Thoughts?
Meanwhile, for my current run I'm going to disable this 'fixer' in the default runner list so as to not fail on run.
The text was updated successfully, but these errors were encountered:
Hi @kevinclement, good to hear you're back on maintaining the project! I haven't got an active subscription myself and do not have much time to spare so I won't be of much help, at least not in the near future.
Regarding the PersistedQueryNotSupported error, this is the same I got a while back when the URL of the realms API was updated: #501. I'm not sure if it is the same issue this time.
Hey dataimporter experts, @seirl and @maxdekrieger.
As I'm coming back up to speed on project I wanted to run importer to make sure we were up to date. I haven't run the importer in a very long time. When I ran it tonight, I got an error message related to the realms API. Looks like we were using a graphql endpoint. When it runs, I get an error in the response, "PersistedQueryNotSupported". I couldn't find documentation anywhere even about this API so it's hard for me to 'fix'. From the looks of it, maybe its possible they no longer support unauth'd requests.
If I can get verification from someone who is familiar that would be great. If that is the problem I can make a change to use the blizzard api with token, and maybe move it to not run by default, and when requested to run, take the token as an argument. Thoughts?
Meanwhile, for my current run I'm going to disable this 'fixer' in the default runner list so as to not fail on run.
The text was updated successfully, but these errors were encountered: