Nico Flaig

Error logs for eth1 provider where just added in v1.12.0 - https://github.com/ChainSafe/lodestar/pull/5949 Not sure if those were necessary, maybe @nazarhussain can clarify. If we expect those to always be set...

> It's not necessary if eth1 and execution are pointing to same provider url. If not then each provider can have different status. Does this mean we close this issue?...

- Will be resolved by https://github.com/ChainSafe/lodestar/pull/6080

That would be great, I assigned the issue to you

This is really straight forward to implement and we should consider including that in the next release as for example Teku VC calls this API by default and has to...

> @nflaig Do you know if there were some special configuration passed to node when this behavior triggered? I don't think it is related to specific configuration, it really just...

Just to highlight the difference of this issue compared to https://github.com/ChainSafe/lodestar/issues/5642 and https://github.com/ChainSafe/lodestar/issues/5775 What happens now is that libp2p stop never resolves, we basically have a hanging promise. The other...

> Can we look into implementing a hack to unblock our v1.12 while we take time to figure out the root cause? Maybe wrap `libp2p.stop` into a `withTimeout`? https://github.com/ChainSafe/lodestar/blob/18dc0c958189cb60fd8df7db6b1ebdf060edbd96/packages/beacon-node/src/network/peers/peerManager.ts#L664

> > any ideas? > > Nothing specific but I find [why-is-node-running](https://www.npmjs.com/package/why-is-node-running) very helpful when tracking down active handles that stop processes from exiting. It not related to active handles,...

> The [libp2p.stop method](https://github.com/libp2p/js-libp2p/blob/master/packages/libp2p/src/libp2p.ts#L249-L264) just stops each component. Do you have any [logs](https://github.com/libp2p/js-libp2p/blob/master/doc/GETTING_STARTED.md#node) available to see which component is causing the problem? The issue is not that easy to reproduce,...