-
Notifications
You must be signed in to change notification settings - Fork 36
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
CRITICAL: TypeError: Cannot read property 'type' of undefined #33
Comments
thanks for the PR but its not a fix. I never faced the issue you are describing, can you please elaborate and provide more information, some real reproduction? |
Here is a demo of the bug in action: The first part of this gif shows the original vesper code. As you can see, batch operations fail with current vesper code but work fine with the fix I propose. If you want to reproduce this, you can close this repo. Use
|
@pleerock Hi, I have pretty the same issue, when trying to run many mutations simultaneously.
on random of those requests. @gaspard fix doesn't really help since I just get another undefined errors. My tsconfig.json config:
I'm on windows 10, using postgress for DB and folllowing deps versions:
Let me know if you need some more info or anything. |
@AntonPuko @gaspard |
@yubozhao yep, it works with transactions disabled for those queries. |
This line is exploding:
https://github.com/vesper-framework/vesper/blob/master/src/index.ts#L115
I tried to understand why sometimes the connection options exist and why it sometimes does not exist.
The bug only appears if the UI triggers many operations at once, sending many async requests to the server. It fails both with postgres and sqlite.
This is a sad bug as it makes vesper unusable because random queries fail.
The text was updated successfully, but these errors were encountered: