e2e test catch panic in client utils init-genesis call

[tzemanovic]

in anoma/anoma#1163 we ran into an issue that caused client utils init-genesis to panic, but e2e tests were failing without reporting the panic in the client, e.g.:

No unread output for command: "anoma/target/debug/anomac" "--base-dir" "/var/folders/8n/xzxk5c154qzg_chndqmzgfdr0000gp/T/.tmpNCrj6l" "--mode" "validator" "utils" "init-network" "--unsafe-dont-encrypt" "--genesis-path" "/var/folders/8n/xzxk5c154qzg_chndqmzgfdr0000gp/T/.tmpNCrj6l/e2e-test-genesis-src.toml" "--chain-prefix" "e2e-test" "--localhost" "--dont-archive" "--allow-duplicate-ip" "--wasm-checksums-path" "anoma/wasm/checksums.json"
Error:
   0: EOF was reached; the read may successed later

[tzemanovic]

this only seems to happen with expectrl (#1095), rexpect didn't have this issue:

Error:
   0: EOF (End of File): Expected Regex: "Derived chain ID: .*\n" but got EOF after reading "The application panicked (crashed).

and it showed the location and trace

[cwgoes]

@tzemanovic is this still applicable?

[tzemanovic]

@tzemanovic is this still applicable?

I think this can still happen - would be nice to fix, because it's not clear what actually failed when it does happen

[tzemanovic]

this is no longer an issue