You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PeerManager::new_routing_only (and PeerManager::new_channel_only) doesn't work with lightning-net-tokio because setup_inbound and setup_outbound take a PeerManager with Arc parameters but the PeerManager::new_routing_only returns a PeerManager without using an Arc for the RoutingMessageHandler.
Reported by a participant at the Bitcoin++ hackathon. Workaround is to instantiated the PeerManager using an Arc for the parameter instead of using PeerManager::new_routing_only.
The text was updated successfully, but these errors were encountered:
Yuck. We should make the generic parameters in lightning-net-tokio more..generic and let them be Deref + Sync or whatever is needed to make tokio happy.
PeerManager::new_routing_only
(andPeerManager::new_channel_only
) doesn't work withlightning-net-tokio
becausesetup_inbound
andsetup_outbound
take aPeerManager
withArc
parameters but thePeerManager::new_routing_only
returns aPeerManager
without using anArc
for theRoutingMessageHandler
.Reported by a participant at the Bitcoin++ hackathon. Workaround is to instantiated the
PeerManager
using anArc
for the parameter instead of usingPeerManager::new_routing_only
.The text was updated successfully, but these errors were encountered: