-
Notifications
You must be signed in to change notification settings - Fork 274
Fix case where user gets stuck while logging into Builder ID #4923
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
Conversation
| .BuilderId(scopes, onPendingToken, onError, onSuccess) | ||
| .login(project) | ||
|
|
||
| // TODO refresh the pane here for case when provider is no-op (i.e. provider exists and has a valid token), to fix issue where user is stuck waiting for browser |
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.
maybe solved by abandoning idempotency semantics as current diff;
write test to confirm scenario when activeConnection() has delta from activeConnectionForFeature()
Qodana Community for JVM2 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
If user ends up in state where they have a connection, but extension doesn't think it's valid for Q, then the sign-in flow will never complete and they need to restart the IDE for the new token to be picked up
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.