-
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
Can not parse event with tuple arguments #1629
Comments
Can you provide the output from |
Output
|
IIRC, someone brought this up in chat recently, too. My first guess was an old version, but like @recmo, they had recent-enough libraries. #1235 is what added tuple support generally, so really #829 should have closed. (Though clearly there's a new, specific problem here) I do notice that this PR only adds tests for tuples at method arguments and return values. I don't see any tests for tuple-typed events. So the first step seems like adding a test of parsing an event with a tuple-typed log value. Presumably that will fail and then we can get this fixed up. |
Maybe related to #1569 as well (arrays there, not tuples, but otherwise I guess similar)? |
Running into this as well. Any good workarounds? |
So can not support ABIEncoderV2 to enable structure-type parameter in event? |
I have the same issue when i try to parse an event wich takes a struct as parameters |
For anyone struggling here, applying the patch from #1484 works for me. |
|
Hello there! I just got a similar issue today. Is there a workaround? Should I use a fork of web3.py? |
Going to close this since #2211 should fix this particular example |
pip freeze
outputpip freeze
outputWhat was wrong?
I'm unable to parse this event from this contract. Getting the following error:
How can it be fixed?
Could be related to #829.
The text was updated successfully, but these errors were encountered: