FIX: faucet stops working with psql indexer

[laciferin2024]

Getting:

  "error": "Usage:\n  coind query txs [flags]\n\nExamples:\n$ coindd query txs --query \"message.sender='cosmos1...' AND message.action='withdraw_delegator_reward' AND tx.height > 7\" --page 1 --limit 30\n\nFlags:\n      --grpc-addr string   the gRPC endpoint to use for this chain\n      --grpc-insecure      allow gRPC over insecure channels, if not the server must use TLS\n      --height int         Use a specific height to query state at (this can error if the node is pruning state)\n  -h, --help               help for txs\n      --limit int          Query number of transactions results per page returned (default 100)\n      --node string        <host>:<port> to CometBFT RPC interface for this chain (default \"tcp://localhost:26657\")\n      --order_by string    The ordering semantics (asc|dsc)\n  -o, --output string      Output format (text|json) (default \"text\")\n      --page int           Query a specific page of paginated results (default 1)\n      --query string       The transactions events query per Tendermint's query semantics\n\nGlobal Flags:\n      --chain-id string     The network chain ID (default \"coinfi\")\n      --home string         directory for config and data (default \"/Users/hiro/.coind\")\n      --log_format string   The logging format (json|plain) (default \"plain\")\n      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic|disabled or '*:<level>,<key>:<level>') (default \"info\")\n      --log_no_color        Disable colored logs\n      --trace               print out full stack trace on errors\n\nfailed to search for txs: error in json rpc client, with http response metadata: (Status: 200 OK, Protocol HTTP/1.1). RPC error -32603 - Internal error: the TxIndexer.Search method is not supported\n: exit status 1"

This doesn't happen with kv config in config.toml:

indexer = "psql"

[laciferin2024]

This is primarily cuz of tendermint

The psql indexer type allows an operator to enable block and transaction event indexing by proxying it to an external PostgreSQL instance allowing for the events to be stored in relational models. Since the events are stored in a RDBMS, operators can leverage SQL to perform a series of rich and complex queries that are not supported by the kv indexer type. Since operators can leverage SQL directly, searching is not enabled for the psql indexer type via Tendermint's RPC -- any such query will fail.

But can our faucet not use those rpcs?

[julienrbrt]

Right! However i think the funds are still being sent right?
WaitTx will indeed not work if you aren't using a kv indexer on the cometbft side.
We won't be ablwe to nicely query the tx in another way, however I do think it is valuable not to return an error if we cannot query it.