aboutsummaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorPéter Szilágyi <peterke@gmail.com>2017-09-27 18:14:52 +0800
committerFelix Lange <fjl@users.noreply.github.com>2017-09-27 18:14:52 +0800
commit2ab2a9f13116748ca343892f851e3632861c994e (patch)
tree97e5cc5dc3b07dbcdc6a73adfbfb07acf816d35f /tests
parent860e697b00c25b8f47371f8b8c7342d0230cee84 (diff)
downloaddexon-2ab2a9f13116748ca343892f851e3632861c994e.tar
dexon-2ab2a9f13116748ca343892f851e3632861c994e.tar.gz
dexon-2ab2a9f13116748ca343892f851e3632861c994e.tar.bz2
dexon-2ab2a9f13116748ca343892f851e3632861c994e.tar.lz
dexon-2ab2a9f13116748ca343892f851e3632861c994e.tar.xz
dexon-2ab2a9f13116748ca343892f851e3632861c994e.tar.zst
dexon-2ab2a9f13116748ca343892f851e3632861c994e.zip
core/bloombits, eth/filters: handle null topics (#15195)
When implementing the new bloombits based filter, I've accidentally broke null topics by removing the special casing of common.Hash{} filter rules, which acted as the wildcard topic until now. This PR fixes the regression, but instead of using the magic hash common.Hash{} as the null wildcard, the PR reworks the code to handle nil topics during parsing, converting a JSON null into nil []common.Hash topic.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions