twoeths

looks like it caused by this one https://github.com/ChainSafe/lodestar/pull/6028/files#diff-e50e7caad2bee8b503fd63320dbc6c32e9f90f05aa76b211df989d02030a9aa6R613 it's supposed to get agent version after 1s but right now we try to get agent version immediately right after a `peer:connect`...

gossip block "till received" is somehow 150ms later than unstable + stable mainnet nodes "till received" is created in gossipsub of network thread

also rss is ~2GB higher than unstable

memory on service deployment is usually higher than that of docker https://github.com/ChainSafe/js-libp2p-gossipsub/pull/468#issuecomment-1931624210 just reviewed the memory in the last 2 days, rss has been stable and decreased over time

e2e tests are stable, passed 6 times. The key thing is to use `useWorker=false`, it works nice with vitest. I suppose we could/should do the same thing for other failed...

decide to separate this PR to multiple PRs to make it easier to review

A lot of failed tests happen with `useWorker=true`, I think it has something to do with the fact that vitest also run in worker thread for gossipsub, I suggest to...

> Should we not wait additional occurrence with such hype to mark it a bug? If it's just once ever, there could not some non-code related issue. I believe it's...

this is too big to review and get merged imo. @ensi321 I suggest breaking this into at least 2 PRs: - Forkchoice change, constants and related tests. This is quite...

idea 1 is not possible for now because LeftNodes are shared across states, can revisit once we're done with n-historical state #5968 work given a deleted check point state, can...