Sending N messages to a chain does not always return N responses

[ancazamfir]

Summary of Bug

When hermes submits N messages to a chain it should get back N responses. This is currently broken when Tx errors occur.

When the messages are sent to cosmos-sdk, they may be split in M transactions. If one of the Tx-es fails all messages are considered failed (the index in the error indicates the position of the message that caused the failure). The Tx failure should recorded for all its messages.

Version

master

Steps to Reproduce

• start two chains
• create channel
• send N transactions making sure max_msg_num is smaller than N
  (tested with max_msg_num = 5 and send N=15).
• there may be other ways to cause the error, i used the ft-transfer with a big amount such that the wallet is drained at some message x, x > max_msg_num
  (tested with wallet that has 100M samoleans and sent 15 transfers of 9M each)
• the output should show N results

Acceptance Criteria

---

For Admin Use

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