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

bug: GraphiQL intermittently fails to work with the <DGS_GRAPHQL_PATH> failing to be replaced #1661

Open
lthoulon-locala opened this issue Oct 10, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@lthoulon-locala
Copy link

lthoulon-locala commented Oct 10, 2023

Expected behavior

When I use the GraphiQL it should work

Actual behavior

A picture is worth a thousand words:

Capture d’écran 2023-10-10 à 11 20 44

This happens when I load /graphiql. The page shows up fine but it triggers the introspection query that returns this error. Once the error is there it never goes away unless I restart the server and I get lucky. We've tried increasing the machine's resources and it seems to solve the issue confirming IMO the race condition theory.

Steps to reproduce

Not sure how to reproduce as it's not always the case. Seems like some race condition as described in #1135
It almost never happens locally on my Mac M1 and almost always happen on our dev developpement server that has much less resources (CPU, ram, ...)
I'm using version 7.5.3 of the dgs-bom.

@lthoulon-locala lthoulon-locala added the bug Something isn't working label Oct 10, 2023
@lthoulon-locala lthoulon-locala changed the title bug: bug: GraphiQL intermittently fails to work with the <DGS_GRAPHQL_PATH> failing to be replaced Oct 10, 2023
@kailyak
Copy link
Contributor

kailyak commented Oct 11, 2023

Hello @lthoulon-locala. Can you explain more about what steps you are taking to use GraphiQL and where in that process you are getting the error?

@lthoulon-locala
Copy link
Author

@kailyak I added more precisions to the original message. Let me know if that's sufficient.

@lthoulon-locala
Copy link
Author

HI. Still getting this error using latest 8.2.2. Any updates on the matter ?
Thanks

@srinivasankavitha
Copy link
Contributor

Hi @lthoulon-locala - unfortunately we are not able to reproduce this issue either. If you have a branch or a test case that can reproduce this, we can dig into this further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants