You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Python client, every command logs a stack trace, as debug level, before exiting the program. In the GO client, this currently doesn't happen. This can be tricky and it'd be nice to have a general way to do this, since we return errors at many different places and it wouldn't be nice to print the stack trace in all of them.
Maybe error wrapping is worth exploring but it could be hard to integrate it with the swagger api errors
The text was updated successfully, but these errors were encountered:
In the Python client, every command logs a stack trace, as debug level, before exiting the program. In the GO client, this currently doesn't happen. This can be tricky and it'd be nice to have a general way to do this, since we return errors at many different places and it wouldn't be nice to print the stack trace in all of them.
Maybe error wrapping is worth exploring but it could be hard to integrate it with the swagger api errors
The text was updated successfully, but these errors were encountered: