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
Heavy concurrent use of web3 causes crashes #642
Comments
This was a combination of two things:
|
I never experienced parsing error, but With a simple code like this:
I got None right now, instead of waiting for the filter requirtments to met. And if I try to loop and using web3 then I get this code easily also.
|
Please open a separate issue for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the example, I'm using the public API key from Alchemy for testing rate limits, see https://docs.alchemy.com/alchemy/documentation/throughput
Example code:
Running this with
cargo run
will cause abnormal request grouping:and further panics such as:
or
This only happens for batch transports
The text was updated successfully, but these errors were encountered: