You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the RequestsEndpoint for fetching data, if you do not set the timeout, it uses requests defaults, which means no timeout.
However, if setting a timeout, the endpoint is not intercepting ReadTimeout errors. This is fine, and I can intercept this when making the call, but it would be nice if sgqlc also handled this. If this is something that the project wants, I can make a PR for this.
Judging by the HTTPEndpoint code, it's also not intercepting timeout errors, but I have not tested this to be sure.
The text was updated successfully, but these errors were encountered:
When using the RequestsEndpoint for fetching data, if you do not set the timeout, it uses requests defaults, which means no timeout.
However, if setting a timeout, the endpoint is not intercepting ReadTimeout errors. This is fine, and I can intercept this when making the call, but it would be nice if sgqlc also handled this. If this is something that the project wants, I can make a PR for this.
Judging by the HTTPEndpoint code, it's also not intercepting timeout errors, but I have not tested this to be sure.
The text was updated successfully, but these errors were encountered: