-
Notifications
You must be signed in to change notification settings - Fork 64
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
Better error reporting on query timeout - context deadline exceeded #187
Comments
note QueryTimeout is in 2.0 only - see #186 previous versions hardcoded at 30s. |
This is a client issue. Ill wrap this error in the go-client and PR the plugin when we release the client. |
@gingerwizard are you able to create a PR for this? Was it fixed? |
Hey @gingerwizard - confirming if this issue was fixed and if so, is there a corresponding PR that we can link this issue to? |
@alyssabull no, this wasn't fixed yet. @SpencerTorres can you take a look? |
@jkaflik yes, I can catch this error and add a clearer message 👍 |
Currently, if the query deadline is exceeded (as controlled by QueryTimeout) in 2.0, the go driver returns a
error querying the database: context deadline exceeded
error. This isn't particularly clear and basically means the user needs to increase the query timeout (default 60s).We should catch this specific error and wrap with something to indicate as such.
The text was updated successfully, but these errors were encountered: