-
Notifications
You must be signed in to change notification settings - Fork 345
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
Cannot read properties of undefined (reading 'originalError') #6088
Comments
Also related: dotansimha/graphql-yoga#2967 |
I'm getting this with a swagger source behind mesh. Quite annoying as I end up getting a 500 from mesh, but the backend source worked fine. |
@Flamefork have you found a workaround for this? In my case the backend rest API is not erroring, so it seems the only error is happening in mesh. I tried bumping to the versions in this one #6059 but I'm still seeing the same issue. This happens with a single source for me. |
Thanks for the details but could you please create a reproduction on CodeSandbox or StackBlitz instead of Docker? |
I've noticed other people with the same issue here: zalando-incubator/graphql-jit#234 @ardatan is there a way to just run without graphql-jit ? |
@ardatan I'm also running into issues where I'm receiving an undefined error for originalError. I reproduced a codesandbox here: https://codesandbox.io/p/sandbox/sad-poincare-lkhtjp This is also my first time using codesandbox so hopefully there aren't any issues with the environment. After running the command: Here's the request body that I ran:
Hopefully this helps resolve the issue. |
Unfortunately I am not able to reproduce it even if I installed the dependencies and updated the |
Fixed in the upstream package; |
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
Github,
Stackblitz
or
CodeSandbox
Describe the bug
A real error being masked by an exception in
graphql-yoga
's result-processor if more than one source used.Seems like the problem is caused by
graphql-jit
's own version ofGraphQLError
which could have (and having)undefined
inextensions
, while in a lot of places it is treated as non-nullable, as ingraphql-js
.For some reason, this problem does not occur when only one source present.
#6059 looks like another instance of this bug, though the one I'm reporting reproduces with the latest mesh version, after the fix.
To Reproduce Steps to reproduce the behavior:
I've uploaded a gist inspired by @TomKlaverAH reproduction 🙏 :
https://gist.github.com/Flamefork/2f00268dfb31a2b27dca5c5fc1e1692d
You can run it in one go with docker using:
Expected behavior
The scenario is intentionally erroneous, the problem is that the expected outcome of this erroneous request should be a proper error
but instead mesh responds with a generic exception in a response processing code
(formatted responses a bit for readability)
The text was updated successfully, but these errors were encountered: