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
26ceb4d Retry initial client connections (Elias Rohrer)
Pull request description:
I'm not sure what of the behavior really changed since the `bitcoind` days, but here's yet another thing I stumbled across while trying to making the switch to `corepc-node`:
Previously, `corerpc-node` would try to establish a connection via the given `Auth` cookie, and would panic if it couldn't setup a initial connection. Only the rest of the initial setup steps would be retried with time-delay.
This however was race-y, as the auth cookie might not already be synced to disk on first startup of a fresh `bitcoind` instance (with fresh data dir), when we try to connect for the first time. Here, we move the intial connection logic into the retry loop to simply also retry it instead of panicking.
@tcharding Seems this might be the last issue (fingers crossed) that keeps LDK and LDK Node from switching our CI over to `corepc-node`. As the switch is also blocking some features, it would be much appreciated if this could be released soonish after it's reviewed.
ACKs for top commit:
nervana21:
tACK 26ceb4d
tcharding:
utACK 26ceb4d
Tree-SHA512: f793152ba101c0646389404bfb4fcbc7cfe0c3323ea06639aa2c625c1a39bd49cae552e86e37f5ad8d6fbbf107f326fe6a410989598aaeba6c8db26dd352f267
0 commit comments