Describe the bug
We can create an unlimited number of filters using eth_newFilter. There should be a maximum cap on the number of filters that can be created, something like 100 or a bit fewer.
Each filter can potentially cause a performance hit in calls like eth_getFilterLogs, so we want to ensure that only a limited number can be created.
To reproduce
- Go to
api_run_tests and remove the call to ignore in the last create_eth_new_filter_limit_test test
- Run
forest-tool api test-stateful with similar parameters that are on the CI
- See error
Expected behaviour
The test is passing, so we no longer need to call ignore on it.
Screenshots
Environment (please complete the following information):
- OS:
- Branch/commit
- Hardware
Other information and links
Describe the bug
We can create an unlimited number of filters using
eth_newFilter. There should be a maximum cap on the number of filters that can be created, something like 100 or a bit fewer.Each filter can potentially cause a performance hit in calls like
eth_getFilterLogs, so we want to ensure that only a limited number can be created.To reproduce
api_run_testsand remove the call to ignore in the lastcreate_eth_new_filter_limit_testtestforest-tool api test-statefulwith similar parameters that are on the CIExpected behaviour
The test is passing, so we no longer need to call ignore on it.
Screenshots
Environment (please complete the following information):
Other information and links