Response status when Accounts is banned or session Expired

[0xGhostCasper]

Hi, @vladkens !

I thought it would be super useful to return some kind of Command or Query result objects from method calls with success status codes and error reasons instead of just returning None values in case of expired session or banned account, because right now we cannot spot and react to situations when account gets banned or session expires - we only see debug logs and that's it, this is not helping to manage application flow.

I believe this should be useful for others aswell, I believe I already saw such suggestion before here in issues section.

[sicholas]

#137 This is what was causing my scripts to never grab full following. Would hit a banned account and would just stop the gather function.

[sicholas]

Got it to work by editing the queue_client.py code, was truly never catching the banned 403 error. This implementation has it simply removes the account and places it in inactive status. Let me know if that helps! @0xGhostCasper

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.