Skip to content

Conversation

@rustyrussell
Copy link
Contributor

Erroneous check made us complain every time we output a deprecated field in listchannels.

Fixes: #7652

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
It's an output field (which we don't complain about), not an input field!

Fixes: ElementsProject#7652
Changelog-Fixed: Logging: removed bogus "**BROKEN** plugin-topology: DEPRECATED API USED: listchannels.include_private" message.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
@rustyrussell rustyrussell added Type::Bug An error, flaw, or fault that produces an incorrect or unexpected result logging labels Sep 13, 2024
@rustyrussell rustyrussell added this to the v24.08.1 milestone Sep 13, 2024
@rustyrussell rustyrussell self-assigned this Sep 13, 2024
Comment on lines +4420 to +4424
def test_listchannels_broken_message(node_factory):
"""This gave a bogus BROKEN message with deprecated-apis enabled"""
l1 = node_factory.get_node(options={'allow-deprecated-apis': True})

l1.rpc.listchannels()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may want to assert on the logs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cleanup already does this automatically...

@rustyrussell rustyrussell merged commit bfe0557 into ElementsProject:master Sep 16, 2024
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

logging Type::Bug An error, flaw, or fault that produces an incorrect or unexpected result

Projects

None yet

Development

Successfully merging this pull request may close these issues.

listchannels throws DEPRECATED API USED message

2 participants