Transaction is temporarily banned

[thewhaleking]

Users sometimes get the error:
Subtensor returned Custom type(1012) error. This means: Transaction is temporarily banned

This usually indicates that the transaction did go through. In situations like this, we should attempt to see if the transaction did indeed go through, and continue from there.

[camfairchild]

I think it means we're not catching the initial error and instead retrying

[thewhaleking]

I think it means we're not catching the initial error and instead retrying

I'm gonna run some tests tomorrow.

[thewhaleking]

It might stem from this:
https://github.com/opentensor/async-substrate-interface/blob/ed422b673409d9869f3da4ee68ccf709f9980602/async_substrate_interface/async_substrate.py#L1776-L1788

We only return the last message received from the websocket regarding extrinsics. Will dig deeper tomorrow

[thewhaleking]

It might stem from this: https://github.com/opentensor/async-substrate-interface/blob/ed422b673409d9869f3da4ee68ccf709f9980602/async_substrate_interface/async_substrate.py#L1776-L1788

We only return the last message received from the websocket regarding extrinsics. Will dig deeper tomorrow

Different method entirely. Nevermind.

I think it means we're not catching the initial error and instead retrying

It's not that. It's not from retrying. While possibly it is in some cases, but the user should see some info about retrying. Errors are caught and returned immediately. I really wish I could recreate this as users do.

[thewhaleking]

The issue is probably resolved by using the updated retry logic in async-substrate-interface 1.5+, but I did add debug log functionality in #597 which may help diagnose if it's not.