-
Notifications
You must be signed in to change notification settings - Fork 1.8k
"filter not found" in Web3.py 4.2.0 #923
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
Comments
Node managed filters have a way of disappearing. There is a pull request open for a drop in replacement for node managed filters with a web3 managed filter that will leverage the stateless The web3 managed filter will solve a lot of problems that the node based filters suffer from: filters getting lost by the client, inability to use filters on infura, unable to use filters across multiple load balanced nodes. |
To expand on this a bit: it's expected behavior for the node to delete installed filters at any time. In the current API, one must always check if the filter is gone and reinstall it, on every data pull. (Hence, Dylan's work on a better solution) |
I am getting this same error. How can I fix it? I am using latest version of web3.py |
@DragonDmoney Nodes consistently drop filters. You may just have to make the filter again. Also, usage questions are better asked in the discord channel. |
What was wrong?
"Filter not found" exception was unexpectedly thrown in about 45 mins after the filter was created.
Please include any of the following that are applicable:
Anonymized code:
Geth/v1.8.6-stable-12683fec/linux-amd64/go1.10
How can it be fixed?
I don't have any concrete suggestions.
The text was updated successfully, but these errors were encountered: