-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
log filter with address option is not returning log #629
Comments
Looking into the node console i get:
But only when i use the first filter, where i get a log.. |
@frozeman please confirm that this issue is still pending |
it is |
Give me a test case please. Give me the steps, code, etc. |
in my first comment there is one :) You can additionally run the rpc-tests by following the readme here: https://github.com/ethereum/rpc-tests Then just run only the filter logs using:
We can also go together over this in a skype call |
|
* do not support relative paths for fuse
…1269) This changes them to use medium+ instead of the default medium, which should help with flaky tests where the machine is overloaded and which don't happen on dev machines since they're more powerful (e.g. ethereum#629). If the failures keep happening, we can either (a) increase further to large, (b) increase the waits in the tests, (c) make those specific tests not run using `t.Parallel()`.
When leaving the address option it retrurns the log.
e.g. creating a filter:
And then calling
eth_getFilterLogs
Returns one log:
But adding the address filter option like:
And then getting the logs again using:
returns no log:
The text was updated successfully, but these errors were encountered: