Skip to content
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

An error occurs after expanding the Azure registry #4141

Closed
v-xinda opened this issue Oct 26, 2023 · 7 comments · Fixed by #4142
Closed

An error occurs after expanding the Azure registry #4141

v-xinda opened this issue Oct 26, 2023 · 7 comments · Fixed by #4142

Comments

@v-xinda
Copy link

v-xinda commented Oct 26, 2023

OS: All
Build Version: 1.27.0

Repro Steps:

  1. Connect Azure registry -> Expand it.
  2. Check whether no error occurs.

Expect:
No error occurs.

Actual:
An error occurs.
Screenshot 2023-10-26 at 10 13 25

@v-xinda v-xinda added the AT-CTI label Oct 26, 2023
@bwateratmsft
Copy link
Collaborator

I have seen this too but I did not notice any negative effects. @TylerLeonhardt is this a known issue?

@bwateratmsft
Copy link
Collaborator

It looks like this might be due to microsoft/vscode-azuretools#1607 which just requires an update of the azureauth package.

@bwateratmsft bwateratmsft self-assigned this Oct 26, 2023
@bwateratmsft bwateratmsft removed their assignment Oct 26, 2023
@v-xinda
Copy link
Author

v-xinda commented Nov 8, 2023

This issue still reproduces for now with the build 20231107.2.

@bwateratmsft
Copy link
Collaborator

I haven't seen this since the update. @v-xinda, can you email me the output from the Output window, "Microsoft Authentication" tab when the error occurs? Please email it as it may contain PII.

image

@bwateratmsft
Copy link
Collaborator

I suspect this issue may still occur even after it's been fixed in the Docker extension, but if you don't encounter it to begin with, you never will. Essentially, the authentication provider is getting stuck with a bad session and it seems unable to actually log out of it, so the error keeps coming up, but the Docker extension is no longer requesting bad sessions.

@bwateratmsft
Copy link
Collaborator

In short, it won't be an issue for external users if my suspicion is right.

@bwateratmsft
Copy link
Collaborator

Based on offline conversation I think my hunch is right; the bad data left over from before the fix caused the issue to reoccur once, but never again. External customers should not run into this.

@microsoft microsoft locked and limited conversation to collaborators Dec 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants