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
Should we do some error handling for common service-account related errors? For instance, if the service key is expired then initializing a core class with creds_path would throw:
Should we do some error handling for common service-account related errors? For instance, if the service key is expired then initializing a core class with creds_path would throw:
RefreshError: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'})
but instead we could try/catch and throw a plain-language error like "Your service account key has expired. Please make a new one and try again".
This would hopefully keep non-technical user working in a notebook from getting blocked and needing a programmer's help.
Another error case might be when the service account key and agent id are for different projects.
The text was updated successfully, but these errors were encountered: