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

use ListPeerChannels #314

Closed
wants to merge 2 commits into from
Closed

Conversation

YusukeShimizu
Copy link
Contributor

@YusukeShimizu YusukeShimizu commented Sep 10, 2024

CLN 24.05 removed channels list from ListPeers response.
The listpeers command in the clightning package to use the listpeerchannels function instead of listpeers.

fixes #304 (comment)

@YusukeShimizu YusukeShimizu changed the base branch from update-nix to master September 10, 2024 05:27
@YusukeShimizu YusukeShimizu marked this pull request as ready for review September 10, 2024 05:28
CLN 24.05 removed channels list from ListPeers response.
The listpeers command in the clightning package to use
the listpeerchannels function instead of listpeers.
@YusukeShimizu YusukeShimizu changed the base branch from master to update-nix September 10, 2024 05:59
@YusukeShimizu YusukeShimizu changed the title nix: update dependencies use ListPeerChannels Sep 10, 2024
@YusukeShimizu YusukeShimizu changed the base branch from update-nix to master September 11, 2024 01:13
This commit updates the glightning dependency to the latest version
available as of September 10, 2024.

Removed custom replace directive for glightning.
@grubles
Copy link
Collaborator

grubles commented Sep 11, 2024

I get the same message in my debug.log whether running master or this PR:

2024-09-11T17:23:36.596Z **BROKEN** plugin-topology: DEPRECATED API USED: listchannels.include_private by \"12/cln:listchannels#130\"

@Impa10r
Copy link
Contributor

Impa10r commented Sep 11, 2024

this is a bug in CLN 23.08

@wtogami
Copy link
Contributor

wtogami commented Sep 15, 2024

Running master branch with d51fa0a locally merged for the past two days.

2024-09-15T00:47:25.078Z DEBUG   plugin-peerswap: 
2024-09-15T00:47:25.078Z DEBUG   plugin-peerswap:  msghandler err: message type not in range
2024-09-15T00:47:25.078Z DEBUG   plugin-peerswap: 
2024-09-15T00:47:25.078Z DEBUG   plugin-peerswap:  msghandler err: message type not in range

Unclear where this is coming from. It happened only twice so far.

@grubles
Copy link
Collaborator

grubles commented Sep 15, 2024

@wtogami Those errors have occurred for me since at least April, according to my debug.log. It looks like the chanbackup plugin prints a message right before those errors each time. Examples:

2024-08-05T21:09:48.500Z DEBUG   plugin-chanbackup: datastore succeeded for Saving latestscb           
2024-08-05T21:09:48.503Z DEBUG   plugin-peerswap:                                                      
2024-08-05T21:09:48.503Z DEBUG   plugin-peerswap:  msghandler err: message type not in range           
2024-08-05T21:09:48.503Z DEBUG   plugin-peerswap:                                                      
2024-08-05T21:09:48.503Z DEBUG   plugin-peerswap:  msghandler err: message type not in range  
2024-09-10T17:08:42.250Z DEBUG   plugin-chanbackup: Peer sent bad custom message for chanbackup!       
2024-09-10T17:08:42.253Z DEBUG   plugin-peerswap:                                                      
2024-09-10T17:08:42.253Z DEBUG   plugin-peerswap:  msghandler err: message type not in range           
2024-09-10T17:08:42.253Z DEBUG   plugin-peerswap:                                                      
2024-09-10T17:08:42.253Z DEBUG   plugin-peerswap:  msghandler err: message type not in range 

@Impa10r
Copy link
Contributor

Impa10r commented Sep 15, 2024

@wtogami Those errors have occurred for me since at least April

#305

@YusukeShimizu
Copy link
Contributor Author

I am going to close this pr because it is not serving its purpose, but please let me know if there are any problems.

@YusukeShimizu
Copy link
Contributor Author

YusukeShimizu commented Sep 16, 2024

I wll summarize the situation:

The plugin-topology: DEPRECATED API USED #314 (comment) will not be fixed by the changes in this Pull Request.
The reason why this is happening is under investigation.
This fix might be related?
ElementsProject/lightning#7652

While the channels field in ListPeers will be removed in version 23.05(rustyrussell/lightning@857a55c) , my understanding is that the peerswap-listpeers does not uses the channels field.

msghandler err: message type not in range #314 (comment) is addressed by #315.

@YusukeShimizu
Copy link
Contributor Author

ElementsProject/lightning#7652 could be the cause.
peerswap-listpeers has a dependency on listchannels.

If that's the cause, no fix is needed for peerswap, and it should be resolved by updating the cln version.

@wtogami
Copy link
Contributor

wtogami commented Sep 19, 2024

https://github.com/ElementsProject/lightning/commits/release-24.08.1/
Confirmed the deprecation warning is fixed in upcoming CLN v24.08.1. Closing.

@wtogami wtogami closed this Sep 19, 2024
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.

4 participants