Ben Edgington

Is this issue still alive, or can we close it now?

Still present in Teku 22.5.2; seems like no prospect of it being fixed at the Javalin end. Is there nothing we can do to suppress this message?

Closing as stale. Please open new issues for anything that remains important.

> Adding proper response message and error code to 404 response to indicate whether it's a skip slot or simply node doesn't have it would be more appropriate? As per...

A relatively minor issue, but learning lessons from Eth 1, how about a mandatory checksum for Eth 2.0 addresses? [EIP55](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-55.md) retro-fitted a checksum format to Eth 1, but this is...

Referencing #6345 in case it might be related.

Not running in docker - just running the besu distribution directly via systemctl. No custom logging settings at all. I can supply multiple thousands of examples from my logs if...

``` $ journalctl -u besu.service --since "2022-08-27 00:00" | wc -l 67509 $ journalctl -u besu.service --since "2022-08-27 00:00" | uniq | wc -l 45206 ``` This suggests that ~22...

The first column in the below is the number of times the identical line (including timestamp) was printed consecutively - apparently up to 32 times. I didn't see these particularly...

Here's the service file: ``` [Unit] Description=Besu Client Wants=network-online.target After=network-online.target [Service] Type=simple User=besu Group=besu Restart=always RestartSec=5 SuccessExitStatus=143 WorkingDirectory=/data/besu Environment=JAVA_OPTS=-Xmx4g ExecStart=/usr/local/besu/bin/besu --config-file /etc/besu/besu.toml [Install] WantedBy=multi-user.target ``` And here's the config file....