Right now, in the "unstable" branch of nimbus-eth2, the latest nim-http-utils HEAD will trigger these errors in the VC logs:
{"lvl":"DBG","ts":"2021-02-01 22:21:24.500+01:00","msg":"Message sent to RPC server","topics":"JSONRPC-HTTP-CLIENT","tid":6239,"file":"httpclient.nim:188","address":{"family":"IPv4","address_v4":[127,0,0,1],"port":7003},"msg_len":70}
{"lvl":"DBG","ts":"2021-02-01 22:21:24.500+01:00","msg":"Malformed header received","topics":"JSONRPC-HTTP-CLIENT","tid":6239,"file":"httpclient.nim:98","address":{"family":"IPv4","address_v4":[127,0,0,1],"port":7003}}
{"lvl":"WRN","ts":"2021-02-01 22:21:24.500+01:00","msg":"Caught an unexpected error","topics":"vc","tid":6239,"file":"nimbus_validator_client.nim:57","err":"Empty response from server"}
Tested with:
./scripts/launch_local_testnet.sh --testnet 0 --nodes 4 --stop-at-epoch 5 --log-level DEBUG --disable-htop --data-dir local_testnet0_data --base-port 9000 --base-rpc-port 7000 --base-metrics-port 8008 --timeout 600 -- --verify-finalization --discv5:no
Right now, in the "unstable" branch of nimbus-eth2, the latest nim-http-utils HEAD will trigger these errors in the VC logs: