srlowe
srlowe
Same on node 1.4.2, Win7. Doesn't seem like anyone is looking at this, oh well.
Just tried to recreate this (thanks for the reproduction steps Chris), but to my surprise it worked as expected (ie. the CLI passed env vars are still present after the...
However, I've also not been able to reproduce this on the original v12.9.1. One theory is that is it may be due to supervisor changes since then.
@rahul-thakoor Is it failing with an error message?
> Why is this change hidden behind an `is v14` check? @LucianBuzzo it's a breaking change that will require a new major version, and this is how we have handled...
> Right, so do you consider any change in visual output a breaking change? @LucianBuzzo Paulo has quite strong views on not breaking things for people who may be scripting...
@LucianBuzzo Right, one of the things this PR adds is a standard --json flag across all commands that output structured data. So this should make scripting much easier and frees...
@xginn8 Do you know of a way to reproduce this device state for testing?
@xginn8 Ah I've managed to reproduce.
@pdcastro Yeah the backend masking something crossed my mind too. However the local ssh also doesn't use `spawnSshAndExitOnError`, so the problem could be there too. Will require some in depth...