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

plugin: Fix parsing of str or int amount_msat #457

Merged
merged 2 commits into from
Jun 5, 2024

Conversation

cdecker
Copy link
Collaborator

@cdecker cdecker commented Jun 3, 2024

We didnt implement parsing string correctly, leaving the extension unprased, causing the parser to err.

@cdecker cdecker force-pushed the 20240603-invoice-payload-decode-panic branch from de4599f to 5387a23 Compare June 4, 2024 10:52
@cdecker cdecker changed the base branch from main to cln-upgrade-24.02.1 June 5, 2024 12:05
@cdecker cdecker force-pushed the cln-upgrade-24.02.1 branch from c24ba09 to 111b1cf Compare June 5, 2024 13:15
@cdecker cdecker force-pushed the 20240603-invoice-payload-decode-panic branch from 5387a23 to 4dbb29b Compare June 5, 2024 13:15
cdecker added 2 commits June 5, 2024 16:40
Just patching this one over for now until we find the root cause.
We had missed this one place where the unit was not being parsed
correctly from an amount with a unit attached at the end, resulting in
incomplete parses. This fixes that.
@cdecker cdecker force-pushed the 20240603-invoice-payload-decode-panic branch from 4dbb29b to 26b57ef Compare June 5, 2024 14:40
@cdecker cdecker merged commit 0b19030 into cln-upgrade-24.02.1 Jun 5, 2024
13 checks passed
@cdecker cdecker deleted the 20240603-invoice-payload-decode-panic branch June 5, 2024 14:58
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

Successfully merging this pull request may close these issues.

1 participant