Wallet sanity test is failing intermittently

[pgarg66]

Wallet sanity fails intermittently on testnet with the following stack trace:

stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:475
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:390
   6: rust_begin_unwind
             at libstd/panicking.rs:325
   7: core::panicking::panic_fmt
             at libcore/panicking.rs:77
   8: core::result::unwrap_failed
   9: solana::wallet::parse_command
  10: solana_wallet::main
  11: std::rt::lang_start::{{closure}}
  12: std::panicking::try::do_call
             at libstd/rt.rs:59
             at libstd/panicking.rs:310
  13: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:105
  14: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:392
             at libstd/rt.rs:58
  15: main
  16: __libc_start_main
  17: _start

[mvines]

@pgarg66 is this a dup of #1559? The backtrace here without a log for context is pretty rough to triage

[CriesofCarrots]

I'm not certain this is the same issue because it doesn't produce the panic, but here is a PR CI with a wallet-sanity failure: https://buildkite.com/solana-labs/solana/builds/4205#016f1ca7-1909-48ac-a211-80c6b6c2ea4b

Here's another: https://buildkite.com/solana-labs/solana/builds/4258#be3becfa-c125-4bf1-a18e-7fcb9562de3b

@jackcmay , please share here if you have any others to hand.
While it may be the same underlying problem, #1559 is definitely a different symptom (airdrop failure on testnet boot).
(cc @mvines )

[CriesofCarrots]

@pgarg66 , do you have the panic message from before the stack trace?
I was finally able to produce a similar panic in parse_command from wallet-sanity by passing a bad character into the $signature variable, but I'm not sure if it's the same panic.

[pgarg66]

Most likely it's the same. It was complaining about ':' being the extra character in the command.

[CriesofCarrots]

Hmm, I don't see any obvious ways wallet-sanity would pick up an errant ':'
If you see it again, would you shoot me all the wallet-sanity output?

[mvines]

I've not seen this in a while, if another occurrence is not reported this week the issue can be closed.

[pgarg66]

👍

[mvines]

Not observed recently in CI