tersec

``` 2022-08-02T07:01:14.1824551Z /home/runner/work/nimbus-eth2/nimbus-eth2/beacon_chain/beacon_chain_db.nim: In function ‘getSplitBlock__beacon95chain95db_37951’: 2022-08-02T07:01:14.1826047Z /home/runner/work/nimbus-eth2/nimbus-eth2/beacon_chain/beacon_chain_db.nim:903:200: error: dereferencing pointer to incomplete type ‘tyObject_TrustedSignedPartialBeaconBlock__nZPmS9bKi6dcEhRUFGxsqgg {aka struct tyObject_TrustedSignedPartialBeaconBlock__nZPmS9bKi6dcEhRUFGxsqgg}’ 2022-08-02T07:01:14.1826904Z if GetResult.found != db.partialBlocks[T.toFork].getSZSSZ( 2022-08-02T07:01:14.1827349Z ^ 2022-08-02T07:01:14.2158988Z make[1]: *** [/home/runner/work/nimbus-eth2/nimbus-eth2/nimcache/release/nimbus_light_client/@mbeacon_chain_db.nim.c.o] Error...

https://github.com/nim-lang/Nim/issues/20141 is what hit the Linux CIs. They're using Ubuntu 18.04, and thus gcc 7.x, while the VM in which I recreated/tested this was Ubuntu 20.04 and gcc 9.x, so...

For capturing timing, not necessarily. Logs come with timestamps, and any pair of logs can therefore be compared. They exist in a global/shared timeline, unlike metrics. It's also more straightforward/freeform...

This turned out not to be the problem, so closing. If people think that it's worth doing some of the logging discussed here, that can be raised in a separate...

https://github.com/status-im/nimbus-eth2/tree/measure-block-proposal-timing does this in a way that, while conceivably doable in `stable`/`unstable`, probably would need refining. One aspect is that it intentionally doesn't try to time durations, but log and...

Why? Nimbus still doesn't really have the hot/cold storage distinction this issue proposes. Era files have been gradually developing (https://github.com/status-im/nimbus-eth2/pull/3394 develops them a bit further, for example), but they're not...

Yes, "using era files and state diffs as a future direction for hot/cold". That particular PR was closed as obsolete, but hot/cold block storage remains a goal, and as the...

https://github.com/status-im/nimbus-eth2/pull/3877/ adds doppelganger detection and https://github.com/status-im/nimbus-eth2/pull/3915 addresses the metrics.

This `nim-web3` bump isn't safe: https://github.com/status-im/nimbus-eth2/pull/3850 That's an issue in `nim-web3`, and I'll revert the changes there. This `Quantity` thing is a real spec divergence, but also, shouldn't block other...

It shouldn't need a full revert -- there's one specific condition which causes problems currently due to the somewhat less-than-rigorous `Quantity` usage (e.g., for various hashes which are definitely not...