-
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
Web3 can't parse event indexed args of dynamic type #350
Comments
@chriseth thats exactly what we've talked about |
Also, there's a problem with contract.allEvents(function(err, result) {
console.log(err, result);
});
contract.test({ from: '0xcd2a3d9f938e13cd947ec05abc7fe734df8dd826' }, function(err, result) {
console.log(err, result);
}); This code creates a filter for all events from contract's address, so it will get |
This are anonymous logs and i though @debris fixed it. We will look into this. |
I'm also bumping into this issue. I'm using indexed strings as event topics but web3 event filter breaks with the following message:
|
JavaScript error 22:47:40 web3.js - line 14280 - Uncaught BigNumber Error: new BigNumber() not a base 16 number: |
Lets discuss this in #344 |
Hi,
Web3 parses event indexed args just like data args (https://github.com/ethereum/web3.js/blob/develop/lib/web3/event.js#L147), but in Solidity indexed arg can take only 32 bytes. So web3 fails to parse length of the value with the error:
Uncaught BigNumber Error: new BigNumber() not a base 16 number:
.Since version 0.1.7 of
solc
the topic is a hash of a value (#344), earlier it were the beginning 32 bytes of a value.The text was updated successfully, but these errors were encountered: