crypto com query unreceived packets borks

[greg-szabo]

Crate

hermes

Summary of Bug

Trying to query unreceived packets on the crypto.com mainnet results in panic.

$ hermes query packet unreceived-packets crypto-org-chain-mainnet-1 transfer channel-10
Jun 21 17:32:05.062  INFO using default configuration from '/home/admin/.hermes/config.toml'
Jun 21 17:32:05.064 DEBUG Options: QueryUnreceivedPacketsCmd { chain_id: ChainId { id: "crypto-org-chain-mainnet-1", version: 1 }, port_id: PortId("transfer"), channel_id: ChannelId("channel-10") }
Jun 21 17:32:05.068 TRACE subscribing to query: tm.event = 'Tx' chain.id=crypto-org-chain-mainnet-1
Jun 21 17:32:05.069 TRACE subscribing to query: tm.event = 'NewBlock' chain.id=crypto-org-chain-mainnet-1
Jun 21 17:32:05.071 TRACE subscribed to all queries chain.id=crypto-org-chain-mainnet-1
Jun 21 17:32:05.071 TRACE getting counterparty chain chain_id=crypto-org-chain-mainnet-1 port_id=transfer channel_id=channel-10
Jun 21 17:32:05.071 DEBUG starting event monitor chain.id=crypto-org-chain-mainnet-1
Jun 21 17:32:05.081 TRACE counterparty chain: osmosis-1 chain_id=crypto-org-chain-mainnet-1 port_id=transfer channel_id=channel-10
Jun 21 17:32:05.081 DEBUG Fetched from source chain crypto-org-chain-mainnet-1 the following channel IdentifiedChannelEnd { port_id: PortId("transfer"), channel_id: ChannelId("channel-10"), channel_end: ChannelEnd { state: Open, ordering: Unordered, remote: Counterparty { port_id: PortId("transfer"), channel_id: Some(ChannelId("channel-5")) }, connection_hops: [ConnectionId("connection-12")], version: "ics20-1" } }
The application panicked (crashed).
Message:  called `Result::unwrap()` on an `Err` value: Error(Context { kind: Rpc(Url { inner: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Ipv4(10.10.51.151)), port: Some(26657), path: "/", query: None, fragment: None }, scheme: Http, host: "10.10.51.151", port: 26657 }), source: Some(Error { code: HttpError, message: "error trying to connect: tcp connect error: Connection timed out (os error 110)", data: None }), backtrace: Some(   0: <ibc_relayer::chain::cosmos::CosmosSdkChain as ibc_relayer::chain::Chain>::init_light_client
   1: ibc_relayer::chain::runtime::ChainRuntime<C>::spawn
   2: <ibc_relayer_cli::commands::query::packet::QueryUnreceivedPacketsCmd as abscissa_core::runnable::Runnable>::run
   3: abscissa_core::application::Application::run
   4: abscissa_core::application::boot
   5: hermes::main
   6: std::sys_common::backtrace::__rust_begin_short_backtrace
   7: std::rt::lang_start::{{closure}}
   8: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/core/src/ops/function.rs:259:13
      std::panicking::try::do_call
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:379:40
      std::panicking::try
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:343:19
      std::panic::catch_unwind
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panic.rs:431:14
      std::rt::lang_start_internal
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/rt.rs:34:21
   9: main
  10: __libc_start_main
  11: _start
) })
Location: relayer-cli/src/commands/query/packet.rs:212

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Version

special osmosis prod version as of Monday (after troubleshooting call)

Steps to Reproduce

Acceptance Criteria

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[greg-szabo]

Same with unreceived-acks.
Querying commitments work.

[greg-szabo]

All right, this turned out to be that the GRPC port was not available for Hermes.

My issue is resolved, but it would be nice to have a more straightforward error message when a port is unavailable.