-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Failed to load schema - TypeError: crossUndiciFetch.fetch is not a function (cont) #7396
Comments
Nobody has created a reproduction and then they said the issue has been gone after reinstalling etc.
Nobody is creating a reproduction but writing the same comments. So the issue was too heated and it is impossible to move on without a reproduction for us.
There are bunch of GraphQL APIs here. |
Hi, I made a reproduction here |
I don't think it was too heated. More users were reporting the issue. I was only open for a few hours. You could give it more time for us to reproduce. I truly appreciate the effort you guys put in maintaining these tools but closing bugs (and locking them) too soon will deter users from reporting them in the first place. Thanks @naquiroz for reproducing the issue. |
I would also like to add that, I just deleted |
Ok it seems like a broken release in one of the dependencies. |
Ok, I resolved the issue by removing the lockfile and reinstalling dependencies. So I guess this is fixed? |
I ran into this and fixed it by replacing I think it has something to do with undici's dns resolution, based on reading nodejs/undici#1248 (comment) Also relevant for: #7388 |
Sheesh, @stereosteve workaround worked. |
This is a continuation of #7388 . I don't understand why such a severe bug which breaks the the application and is reported by so many users in just a few hours is being closed. The ability to comment was also blocked which is something I don't understand the reason for. I understand it is very hard to maintain such a popular tool but this bug is important to solve. At the very least keep the ticket open for us to have a place to discuss it and debug as a group.
I suggest using a label like
requires-reproduction
instead of closing and locking.About reproducing: Is there a public schema url we can try to reproduce this on?
Describe the bug
When running the generate command I get this error:
Running this command works so I believe it's a dependency issue:
To Reproduce
Steps to reproduce the behavior:
codegen.json
config file:Expected behavior
Environment:
OS: linux
React
Additional context
The text was updated successfully, but these errors were encountered: