-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Event log decode fails #3684
Comments
Please see related issue: #3544 from ethers-io/ethers.js#992 (comment):
|
Okay. I didn't see that. Since there is another issue open reg. the same, should I close this? |
@viswanathkgp12 We'll keep it open for now, its a good reference point. |
I've added support in ethers 5.0.12 for supporting legacy Solidity 0.4 external event data. I believe web3 depends on the abi package directly, in which case web3 should upgrade to For more details, please see ethers-io/ethers.js#891. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
@koraykoska Can you double check this :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
@ethersproject/abi is on 5.0.7 and this issue shouldn't exist any more. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
I've tried decoding
OracleRequest
event logs from this tx usingweb3.eth.abi.decodeLog
Expected behavior
Decodes correctly to:
Actual behavior
Event log decode fails. Logs attached below.
From the logs, it looked like the abi decoder expects event data to be a multiple of
32 bytes
or64 hex characters
. When I padded extra zeroes at the end to satisfy this condition, it decoded correctly. I think the library should handle this automatically.Steps to reproduce the behavior
Logs
Environment
Tested on web3js
v1.2.9
andv1.2.11
The text was updated successfully, but these errors were encountered: