We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While we use weights to prioritize certain providers over others, we don't eliminate errors whenever we hit a low-weighted RPC provider.
We should retry the lookup to the weighting system 2 times to avoid getting errors as much as possible.
It should retry on a non-2xx status code. Possibly it could also detect that the body contains a JsonRpcResponse error or a non-JsonRpcResponse value.
We should also report metrics on this.
The text was updated successfully, but these errors were encountered:
Also add timeouts trying to get a request from the upstream provider. If it times out, retry again.
Sorry, something went wrong.
chris13524
Successfully merging a pull request may close this issue.
While we use weights to prioritize certain providers over others, we don't eliminate errors whenever we hit a low-weighted RPC provider.
We should retry the lookup to the weighting system 2 times to avoid getting errors as much as possible.
It should retry on a non-2xx status code. Possibly it could also detect that the body contains a JsonRpcResponse error or a non-JsonRpcResponse value.
We should also report metrics on this.
The text was updated successfully, but these errors were encountered: