Tx searching issue

[georgelombardi97]

Summary of Bug

The tx search functionality has issues. I m looking for outbound tx of an IBC tx on destination chain. The general logic is to search tx by packet sequence and recipient address and this logic works for all chains.
But on stride, when I search with recipient and packet_sequence, the response is empty.
However, when I search with only recipient, I get responses. And when I search only with packet sequence, I again get responses.
So I can search with packet_sequence and inside the responses manually search for my desired recipient and find the target tx.
But the same target tx cannot be found when searching for both params.

Version

From history I can confirm that the issue didn't exist in May. But I m not sure when the issue has been initiated.

Steps to Reproduce

Just check requests below:

Searching for both packet_sequence and recipient gives empty response which is an issue:
https://stride-api.cosmosrescue.com/cosmos/tx/v1beta1/txs?pagination.limit=100&limit=100&pagination.count_total=false&events=transfer.recipient=%27stride1ma425m2g8md7t38ptg8ykpezjtlaqgdfvhqdke%27&events=recv_packet.packet_sequence=%27130606%27
Searching for only packet_sequence :
https://stride-api.cosmosrescue.com/cosmos/tx/v1beta1/txs?pagination.limit=100&limit=100&pagination.count_total=false&events=recv_packet.packet_sequence=%27130606%27
Searching for only ibc transfer recipient:
https://stride-api.cosmosrescue.com/cosmos/tx/v1beta1/txs?pagination.limit=100&limit=100&pagination.count_total=false&events=transfer.recipient=%27stride1ma425m2g8md7t38ptg8ykpezjtlaqgdfvhqdke%27

But I expect searching for both packet_sequence and recipient together to work. Because the tx exists with the same packet sequence that contains a transfer recipient address!
Check this search for packet sequence: Link And it contains the below log which has transfer.recipient log of my desired address.

  "type": "transfer",
  "attributes": [
    {
      "key": "recipient",
      "value": "stride1ma425m2g8md7t38ptg8ykpezjtlaqgdfvhqdke"
    },

So this looks like and issue on indexer or db level that it cannot find the tx with two search conditions. But the same search with two or more params works for other chains.

I am not sure if the search issue is limited to the fields I used (It could be an issue with any other two fields too)

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned