`forc index status` panics

[ra0x3]

Issue

Thanks for opening an issue on the Fuel Indexer project.

*If you're an internal FuelLabs contributor, please feel free to remove this template when creating issues, as this template is meant for external users and contributors.

Prerequisites

• [x] Can you reproduce the problem?
• [x] Do you know which version of the indexer you're using?
• [x] Are you using the latest versions of Fuel ecosystem components available in fuelup?
• [x] Did you already check for an answer in previous Discussions?

Description

• forc index status panics

Steps to Reproduce

• I have an indexer deployed for the past 17 days in QA
• I run forc index status --url http://beta-4-indexer-qa.swayswap.io --auth $INDEXER_QA_JWT
• I get the error

Expected behavior: I'd expect the command to not panic

Actual behavior: The command panics when trying to read the JSON repsonse?

forc index status --url http://beta-4-indexer-qa.swayswap.io --auth $INDEXER_QA_JWT

✅ Successfully fetched service health:

client status: OK
database status: OK
uptime: 17days 11h 3m 32s

thread 'main' panicked at /Users/runner/work/fuel-indexer/fuel-indexer/plugins/forc-index/src/ops/forc_index_status.rs:100:34:
Failed to read JSON response.: reqwest::Error { kind: Decode, source: Error("invalid type: map, expected a tuple of size 2", line: 1, column: 1) }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    81581 abort      forc index status --url http://beta-4-indexer-qa.swayswap.io --auth

Versions

Please list what version of indexer components you're using. Latest is currently .

• fuel-indexer: 0.23.0
• forc-index: 0.23.0
• forc: N/A

[ra0x3]

Sorry for the comment on this. There is no issue. QA has not been re-deployed with 0.23.0