eth_getLogs: invalid argument 0: hex number with leading zero digits

[wbt]

MetaMask's code for polling for events causes a lot of warnings in a Geth node log.

Details: web3/web3.js#3379

[wbt]

Whatever used to work for getting events is no longer working for events coming in after the initial set (e.g. if additional events occur), and it appears to be due to this issue. I know that websocket support is definitely not a priority, but are there any plans to address this?

[vandan]

Could be an issue with eth-json-rpc-filters.
Need to reproduce and investigate.

[schiemon]

Does anyone know any workaround? I have the same issue meaning I am able to load the initial set of events but fail with warnings (see title) in the rpc-node's console for events that happen later. I am using GoQuorum with Docker.

[wbt]

Does anyone know any workaround?

Ignoring the warnings? If you're seeing failures there should be errors somewhere.

[schiemon]

Unfortunately, I cannot reproduce the state anymore (it is O.K. now for some reason) but I did not remember seeing any errors in the node's console. I needed a workaround not for the warnings but for my web client which did not receive any events presumably because of this. When I come to this situation again I can give you more context.

[schiemon]

In the last days, my colleagues and I repeatedly get this error (err=)

WARN [10-07|13:34:38.661] Served eth_getLogs                       conn=172.16.239.1:61790 reqid=8138132905274248 t="569.75µs"  err="invalid argument 0: hex number with leading zero digits"

I am using GoQuorum@22.4.1 (via quickstart) and web3.js@1.8.0.