mirror of
https://github.com/status-im/nimbus-eth2.git
synced 2025-01-09 13:56:23 +00:00
8b01284b0e
hash_tree_root was turning up when running beacon_node, turns out to be repeated hash_tree_root invocations - this pr brings them back down to normal. this PR caches the root of a block in the SignedBeaconBlock object - this has the potential downside that even invalid blocks will be hashed (as part of deserialization) - later, one could imagine delaying this until checks have passed there's also some cleanup of the `cat=` logs which were applied randomly and haphazardly, and to a large degree are duplicated by other information in the log statements - in particular, topics fulfill the same role
40 lines
1.2 KiB
Nim
40 lines
1.2 KiB
Nim
{.push raises: [Defect].}
|
|
|
|
import
|
|
os, strformat, chronicles,
|
|
ssz/ssz_serialization,
|
|
beacon_node_types,
|
|
./spec/[crypto, datatypes, digest]
|
|
|
|
# Dump errors are generally not fatal where used currently - the code calling
|
|
# these functions, like most code, is not exception safe
|
|
template logErrors(body: untyped) =
|
|
try:
|
|
body
|
|
except CatchableError as err:
|
|
notice "Failed to write SSZ", dir, msg = err.msg
|
|
|
|
proc dump*(dir: string, v: AttestationData, validator: ValidatorPubKey) =
|
|
logErrors:
|
|
SSZ.saveFile(dir / &"att-{v.slot}-{v.index}-{shortLog(validator)}.ssz", v)
|
|
|
|
proc dump*(dir: string, v: SignedBeaconBlock) =
|
|
logErrors:
|
|
SSZ.saveFile(dir / &"block-{v.message.slot}-{shortLog(v.root)}.ssz", v)
|
|
|
|
proc dump*(dir: string, v: TrustedSignedBeaconBlock) =
|
|
logErrors:
|
|
SSZ.saveFile(dir / &"block-{v.message.slot}-{shortLog(v.root)}.ssz", v)
|
|
|
|
proc dump*(dir: string, v: HashedBeaconState, blck: BlockRef) =
|
|
logErrors:
|
|
SSZ.saveFile(
|
|
dir / &"state-{v.data.slot}-{shortLog(blck.root)}-{shortLog(v.root)}.ssz",
|
|
v.data)
|
|
|
|
proc dump*(dir: string, v: HashedBeaconState) =
|
|
logErrors:
|
|
SSZ.saveFile(
|
|
dir / &"state-{v.data.slot}-{shortLog(v.root)}.ssz",
|
|
v.data)
|