This awaits on the new connection future instead of just spawning it because otherwise the Lib3hToClient::HandleGetGossipingEntryList and Lib3hToClient::HandleGetAuthoringEntryList messages get sent and can be responded to before the join is complete. This leads to the responses to those messages being thrown away. Then the agents id's never actually get into the DHT.
testing/benchmarking notes
( if any manual testing or benchmarking was/should be done, add notes and/or screenshots here )
followups
( any new tickets/concerns that were discovered or created during this work but aren't in scope for review here )
changelog
[ ] if this is a code change that effects some consumer (e.g. zome developers) of holochain core, then it has been added to our between-release changelog with the format
- summary of change [PR#1234](https://github.com/holochain/holochain-rust/pull/1234)
documentation
[ ] this code has been documented according to our docs checklist
PR summary
This awaits on the new connection future instead of just spawning it because otherwise the
Lib3hToClient::HandleGetGossipingEntryListandLib3hToClient::HandleGetAuthoringEntryListmessages get sent and can be responded to before the join is complete. This leads to the responses to those messages being thrown away. Then the agents id's never actually get into the DHT.testing/benchmarking notes
( if any manual testing or benchmarking was/should be done, add notes and/or screenshots here )
followups
( any new tickets/concerns that were discovered or created during this work but aren't in scope for review here )
changelog
documentation