commando: always active.

We used to activate on the first rune creation, but we're no longer in charge
of runes, so we can't make that call.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2023-07-25 11:12:43 +09:30
parent e28469783e
commit cd16690af8
2 changed files with 6 additions and 24 deletions

View File

@@ -14,7 +14,6 @@ from utils import (
import ast
import base64
import concurrent.futures
import json
import os
import pytest
@@ -2617,13 +2616,6 @@ def test_commando(node_factory, executor):
l1, l2 = node_factory.line_graph(2, fundchannel=False,
opts={'log-level': 'io'})
# Nothing works until we've issued a rune.
fut = executor.submit(l2.rpc.call, method='commando',
payload={'peer_id': l1.info['id'],
'method': 'listpeers'})
with pytest.raises(concurrent.futures.TimeoutError):
fut.result(10)
rune = l1.rpc.commando_rune()['rune']
# Bad rune fails