Open hydrogen18 opened 3 years ago
Having the same error when using --state matched
So I think what is happening here is it only filters on deployment state, not group state (part of a deployment). I'm just going to update the CLI to validate the --state
flag before it sends it to the RPC server. There is no reason to send the request if the provided value is invalid.
There's no matched
state for groups. Only the below states are available now.
"invalid": 0,
"open": 1,
"paused": 2,
"insufficient_funds": 3,
"closed": 4,
If I run with a flag of
--state matched
I get this resultWhich seems to indicate the server can't filter by that, or something similar. It should be possible, or we should not even allow the request to go on to the RPC node.
Switching to `--state active' gives even more confusing results
The returned deployment actually says "state: matched", which does not seem right at all