Possible bug in the CLI networks command

When I was making a screencast on the networks sub-command I got this – which came as a bit of a shock…

Both network configs are marked as current Kinda threw me so it was a lot shorter and less fluent than it should have been.
However the basics are there so I’ll redo this networks segment

Strange, not seen that before. I’ll see if I can replicate it in a bit.
PS new version of the CLI should be released shortly, but not with anything that should fix or affect this.

1 Like

start a default baby-fleming then run

safe networks add baby-fleming ~/.safe/node/node_connection_info.config  safe networks check
safe networks add fleming-testnet https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config
safe networks       

All will look as expected, then

safe networks switch fleming-testnet
safe networks

shows asterisks against both entries

1 Like