-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/sk 752 #565
Bugfix/sk 752 #565
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment.
self.detach() | ||
logger.error("GRPC hearbeat: Token expired. Disconnecting.") | ||
self.disconnect() | ||
sys.exit("Unauthorized. Token expired. Please obtain a new token.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why? this will break the client trying to refresh token?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, was thinking about that, but currently the client is not trying to refresh the token, right? So for now the right things seems to be to disconnect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no that's not right they will try to refresh tokens, if you ask for new assignment and the token has expired it will try to get a new one. But only when calling REST-API
Description
Bugfix - missing self.attach() upon client reconnection attempt.
Also introduces the logic change that if the reason for a client being disconnected is Token expirations, no reconnection attempts are made and the client exits.
Closes SK-752.