-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Commit dry run works on 0.18.1 release, not after recent commits #3581
Comments
Draft
@raphjaph should we expect to see a fix for this today or should I go figure out how to make the change myself locally? |
Can you also add the PSBT into the wallet resume & resume --dry-run? 🙏
That is null too
…On Thu, Apr 18, 2024, 12:19 PM wizardlabsxyz ***@***.***> wrote:
@raphjaph <https://github.com/raphjaph> should we expect to see a fix for
this today or should I go figure out how to make the change myself locally?
—
Reply to this email directly, view it on GitHub
<#3581 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUVJKEK6JHAXO73F5JABGX3Y6AMDRAVCNFSM6AAAAABGL5HXCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVGAZDGNRXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
on release 0.18.1 release code, I don't get this error on mainnet trying to dry run an etch commit.
when I sync to your newest commits AFTER 0.18.1, I get this error message. Is there a new limitation that we can't kick off a commit earlier than 840k to resume later?
The text was updated successfully, but these errors were encountered: