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
Does anyone know what causes these errors? Is it normal to explicitly catch and handle these specific errors or is it more likely a problem on my app or server? The server is just a Hetzner VPS with very basic configuration, I can't imagine it being that with the popularity that Hetzner has; as to the app, it only happens very occasionally, the same request will succeed after any subsequent attempt.
The text was updated successfully, but these errors were encountered:
importkyfrom'ky';constresponse=awaitky('https://example.com',{hooks: {beforeRetry: [async({error})=>{if(!isNetworkError(error)){throwerror;}}]},retry: {limit: 2,// Number of retry attemptsmethods: ['get'],// Methods to retrystatusCodes: [0]// Include network errors (status code 0)}});
However, I think it would be useful if Ky had a retry.shouldRetry function. Then it could simply be:
Hard to know for sure. The occasional network errors like 'Failed to fetch' can have various causes, including transient network issues. It's common to handle such errors in your app. The fact that the same request often succeeds on subsequent attempts suggests external factors may be at play, and the basic server configuration may not be the main issue.
We have these errors happening only occasionally and I'm not able to reproduce these errors.
Is it possible to retry only when errors are network errors: https://github.com/sindresorhus/is-network-error/blob/main/index.js ?
Does anyone know what causes these errors? Is it normal to explicitly catch and handle these specific errors or is it more likely a problem on my app or server? The server is just a Hetzner VPS with very basic configuration, I can't imagine it being that with the popularity that Hetzner has; as to the app, it only happens very occasionally, the same request will succeed after any subsequent attempt.
The text was updated successfully, but these errors were encountered: