Skip to content
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

The fetch middleware produces an empty response when retries have been exhausted #166

Open
mcmire opened this issue Dec 12, 2022 · 0 comments

Comments

@mcmire
Copy link
Contributor

mcmire commented Dec 12, 2022

The fetch middleware has a series of errors that it will look for when making the request to the RPC endpoint, and if any of them appear, it will retry the request up to 5 times. If the request still fails after the retries have been exhausted, the middleware will do nothing and return an empty response. The empty response is then caught by json-rpc-engine, which produces its own error. Thus, the original error is lost. This is in opposition to the Infura middleware exposed by eth-json-rpc-middleware, which produces a "All retries exhausted" error, along with the original error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants