-
Notifications
You must be signed in to change notification settings - Fork 95
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: expect failure on direct rfq peer btc invoices #916
itest: expect failure on direct rfq peer btc invoices #916
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
itest seems to fail.
interesting, could be flaky, didn't hit this on local tests |
also linter seems to fail here with
passes locally |
dd49654
to
890764a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 need to remove the temp commit (waiting on dep I guess?), otherwise looks good.
thanks @ffranr , currently working on resolving an error with the htlc force-close test, will push once it has been resolved |
32daefb
to
19fd405
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM pending dependant PRs and nit mentioned in earlier review.
Can be updated to |
This commit represents the main integration between lnd running in integrated mode and tapd providing auxiliary components for custom channels.
This change will speed up integration tests by not waiting a full 5 seconds before re-trying the connection to lnd if it fails the first time.
Co-authored-by: Olaoluwa Osuntokun <[email protected]> Co-authored-by: Gijs van Dam <[email protected]> Co-authored-by: George Tsagkarelis <[email protected]>
Add the `priceoraclerpc`, `rfqrpc`, and the `tapchannelrpc` JSON callbacks to the litclient's `Registrations` array. This allows the litclient to use the rpc functions contained in these JSON callbacks.
…gh a build argument
1f4a0cd
to
d59c717
Compare
Previously we'd consider it acceptable to settle direct rfq peer invoices, which included no rfq scid, with asset HTLCs. This behavior has been updated on the tapd invoice manager and we no longer accept asset HTLCs on invoices that do not expect assets. This commit updates such payments in our itests to instead expect a failure.
19fd405
to
ec7a3e6
Compare
Updated |
Just FYI: The itests broke due to the update to the latest |
d59c717
to
76e65f1
Compare
Ah, actually, this PR fixes the CI (which makes sense). So I cherry picked the relevant commit into the base branch ( |
Description
Previously we'd consider it acceptable to settle direct rfq peer
invoices, which included no rfq scid, with asset HTLCs. This behavior
has been updated on the tapd invoice manager and we no longer accept
asset HTLCs on invoices that do not expect assets. This commit updates
such payments in our itests to instead expect a failure.
Tapd dependency: lightninglabs/taproot-assets#1244
Lnd dependency: lightningnetwork/lnd#9357