Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

itest: fix issues caused by the bump to lnd 0.15.4-beta #153

Open
ellemouton opened this issue Nov 23, 2022 · 0 comments
Open

itest: fix issues caused by the bump to lnd 0.15.4-beta #153

ellemouton opened this issue Nov 23, 2022 · 0 comments

Comments

@ellemouton
Copy link
Member

In #152, the lnd version that faraday uses was bumped from v0.15.-0-beta to v0.15.4-beta. This then caused some of the faraday itests to break. Specifically:

  1. The closeChannel method started to use a zero value fee. This has temporarily been solved by ignoring the used fee and instead using a hardcoded fee value. See 1 and 2
  2. The second issue is that force closes no longer show up as confirmed in the itest. This could possibly due to the first issue? Perhaps the zero fee txs dont get accepted into the mempool?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant