-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add a way to silence the message "Weird... Response for not a thing we sent" #3982
Comments
This sounds absolutely like a bug. I’ll get in out in the next patch release. |
I just looked up that error. It is something that needs some way of signalling. I will add it as an Basically, it means the provider is sending back a response to a request that was never made. For example, it seems to be responding with an How are you able to trigger this? |
I was accessing the Nodereal provider's endpoint using the free pricing plan. This plan has a rate limit per second that is 2 times lower than the number of transactions needed to extract data from the mempool. As a result, the success rate of the requests was about 60%, and in the remaining 40% of cases, I received a lot of console messages. You can replicate this by using their free pricing plan. |
Fixed in v6.4.0. Now an Thanks! :) |
Describe the Feature
I am currently testing various providers using ethers.js v6 and when I access one of the providers I keep getting a
"Weird... Response for not a thing we sent"
message.I know the reason for this message (I'm running into provider restrictions) and I don't want this message to constantly appear in my console (thousands of messages in minutes), but in the code, it's just
console.log()
and I can't silence this message in any way.I would like this message to have some level like
console.debug()
or an alternative way to silence this message.Code Example
No response
The text was updated successfully, but these errors were encountered: