-
Notifications
You must be signed in to change notification settings - Fork 912
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
Still some msat suffixes #6244
Comments
Oh that is a really nice catch! thanks |
vincenzopalazzo
added a commit
to vincenzopalazzo/lightning
that referenced
this issue
May 9, 2023
This is a regression that we introduced in this release due to some dirty parts of our codebase. For historical reasons (I think), we were using a `json_add_sat_only` procedure defined in `peer_control.c`. So when @rustyrussell removed the _msat, we thought that all the fields were reflecting the new behavior, but we were wrong. This PR fixes this bug and also removes the additional function from `peer_control.c`. This way, we can be sure that there is no other part of our codebase that uses this method (except for other `json_add` methods). Link: ElementsProject#6244 Reported-by: @hMsats Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo
added a commit
to vincenzopalazzo/lightning
that referenced
this issue
May 9, 2023
This is a regression that we introduced in this release due to some dirty parts of our codebase. For historical reasons (I think), we were using a `json_add_sat_only` procedure defined in `peer_control.c`. So when @rustyrussell removed the _msat, we thought that all the fields were reflecting the new behavior, but we were wrong. This PR fixes this bug and also removes the additional function from `peer_control.c`. This way, we can be sure that there is no other part of our codebase that uses this method (except for other `json_add` methods). Link: ElementsProject#6244 Reported-by: @hMsats Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo
added a commit
to vincenzopalazzo/lightning
that referenced
this issue
May 9, 2023
This is a regression that we introduced in this release due to some dirty parts of our codebase. For historical reasons (I think), we were using a `json_add_sat_only` procedure defined in `peer_control.c`. So when @rustyrussell removed the _msat, we thought that all the fields were reflecting the new behavior, but we were wrong. This PR fixes this bug and also removes the additional function from `peer_control.c`. This way, we can be sure that there is no other part of our codebase that uses this method (except for other `json_add` methods). Link: ElementsProject#6244 Reported-by: @hMsats Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@vincenzopalazzo thanks Vincenzo! Better avoid a "Great Msat Migration" part 2 :-) |
ShahanaFarooqui
pushed a commit
that referenced
this issue
May 9, 2023
This is a regression that we introduced in this release due to some dirty parts of our codebase. For historical reasons (I think), we were using a `json_add_sat_only` procedure defined in `peer_control.c`. So when @rustyrussell removed the _msat, we thought that all the fields were reflecting the new behavior, but we were wrong. This PR fixes this bug and also removes the additional function from `peer_control.c`. This way, we can be sure that there is no other part of our codebase that uses this method (except for other `json_add` methods). Link: #6244 Reported-by: @hMsats Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue and Steps to Reproduce
local_funds_msat
etc. still have suffix msat inlightning-cli listpeers
Example:
getinfo
output"version": "v23.05rc3"
The text was updated successfully, but these errors were encountered: