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
This commit fixes a potential deadlock when running in conjunction with
lnd/litd. On startup, if a custom message needs to be sent by an lnd
component as part of its initialization, it would previously run into
the waitForReady method in tapd and wait. But that would block lnd from
fully starting up, meaning that waitForReady would never return.
We fix this by queuing up incoming messages so we can handle them
asynchronously once we've fully started up.
This is safe as long as the server and funding controller have been
created, even if not fully started. The queued messages will be
processed as soon as the funding controller's Start method is called.
0 commit comments