Keep track of errors that happened on the rebalancer

[Art3miX]

More details at: #5

Add a storage to keep track of failed message that happened for the rebalancer, in a perfect world, the rebalancer should not execute messages that are failing.

Status

• Nov 5th, 2023 (05/11/2023) Custom events are added, which allows us to manually see errors if they happen when running the system_rebalance message, while not ideal it does show us an error happen, it tells us what type of an error (account or executed by the account), and it does tell us the error message.

Missing

• [ ] Get more details about the error - we currently know where the error happened, and we get the error message, but we don't know for which account or auction this error happened, we need to get as much details as possible from the error so we can fix it faster.
• [ ] Automate errors reading off chain, currently we can check manually the explorer if any error happened during the rebalancer message, manual work is not ideal, we want the list of errors to be pulled into some off-chain list so we can check easily.

[Art3miX]

Update - Nov 5th, 2023 (05/11/2023)

A custom event will be shown in the explorer if any error happened (it wont if none happened), this gives us some way of manually checking if an error happened during the rebalancer message and fix it.

The given errors are basic and will only show the error message and what type of an error (with account or with a message to the auction), but it won't give us more details (depending on the error). We do want to include more details, at least what address this error happened to, but reply is very limited, even more in case of an error, only available is the id and the error message, and id is u64 which limits what extra data we can pass to it.

We also want to automate the error showing to some off-chain list, so we won't relay on manually checking explorers.

Action

• [x] Add v0.2 tag
• [x] Update todo list on the issue

[Art3miX]

Closing. We address this directly in https://github.com/timewave-computer/server/pull/1, now in slack we will see if any account failed during rebalancing, and with our manual testing we can isolate the account config and see exactly what went wrong.