Check if we can initialize the PeerPool earlier

What is wrong?

This is a follow up to the discussion @pipermerriam and I had here.

Currently the PeerPool isn’t available until some other async tasks are resolved. This issue serves as a reminder to check whether the PeerPool could be created synchronously earlier.

How can it be fixed

A possible idea would be to create the PeerPool early on without the dependencies that first need to be resolved asynchronously and then as a second step, once these dependencies are resolved, call some initialization API on the PeerPool. Before that, the PeerPool would already exist but would reside in some sort of bootstrapping mode until that API is called.

Not sure, if I like that tbh. ¯_(ツ)_/¯

[gsalgado]

ISTM that the problem here is the fact that Server.peer_pool only gets set in Server._run() and not in Server.__init__(), as it should. IIUC we do that because of some (far from ideal) server or sharding tests. If we fix those tests we could then initiate a PeerPool and assign it to Server.peer_pool in Server.__init__(), as I think we should do

[cburgdorf]

Solved problem. Closing.