-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
regression in eth.getLogs #999
Comments
schmir
added a commit
to trustlines-protocol/py-eth-index
that referenced
this issue
Aug 10, 2018
We need this for testing interaction with the blockchain. This adds eth-tester together with py-evm as a backend. This introduces lot's of new (indirect) dependencies (as can be seen in the constraints.txt file) Currently we don't deploy any of our contracts. Instead we test that eth_getLogs works. I ran into a regresssion with that function while trying to update to web3 4.5.0. See ethereum/web3.py#999
Hrm, looks like we should do two things.
|
schmir
added a commit
to trustlines-protocol/py-eth-index
that referenced
this issue
Aug 16, 2018
4.5 won't work. see ethereum/web3.py#999
This was referenced Aug 16, 2018
Fixed in #1005 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What was wrong?
The following code call eth.getLogs with address being a list of addresses. This works fine in web3 4.4.1, but is broken in web3 4.5.0.
This produces the following error on 4.5.0:
How can it be fixed?
The following patch fixes the issue for me, but would prevent passing in a single address as string.
I fail to see if/how one can declare a union type for the
address
parameter, something likeaddress | address[]
Completely removing the type specification for the address field would also solve it.
The text was updated successfully, but these errors were encountered: