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.

Sign up for GitHub

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

Jump to bottom

"Entry not found in cache" error when importing ACR, ASA, and AML modules #161

Closed
LazarusX opened this issue May 24, 2018 · 5 comments
Closed

"Entry not found in cache" error when importing ACR, ASA, and AML modules #161

LazarusX opened this issue May 24, 2018 · 5 comments
Labels
bug external dependency Cannot fix only in this code base. It depends on the fix on third-party Obsolete

Comments

@LazarusX
Copy link
Contributor

Reported by @czgtest

Steps to reproduce:

  1. Open VS Code for several hours without using it
  2. Import an existing module on ACR
  3. Notice below error:
    Screenshot
@LazarusX LazarusX added the bug label May 24, 2018
@LazarusX LazarusX self-assigned this May 24, 2018
@LazarusX
Copy link
Contributor Author

Possibly related to microsoft/vscode-azure-account#53

@LazarusX LazarusX mentioned this issue Nov 23, 2018
Merged
@LazarusX
Copy link
Contributor Author

Workaround: open command palette and run "Reload Window" or restart VS Code.

@adashen adashen added the external dependency Cannot fix only in this code base. It depends on the fix on third-party label Nov 23, 2018
@LazarusX LazarusX changed the title "Entry not found in cache" error when importing ACR modules "Entry not found in cache" error when importing ACR, ASA, and AML modules Nov 23, 2018
@LazarusX
Copy link
Contributor Author

Importing ASA and AML modules is also impacted.

@adashen
Copy link
Member

adashen commented Dec 12, 2019

microsoft/vscode-azure-account#53 external dependency

@konichi3
Copy link
Collaborator

konichi3 commented Jan 9, 2021

Hi

Thank you for filing the issue.

We are looking to clean up the reported issues that are obsolete such that our team can focus on the latest issues reported.
As such, we are going to close the issue for now.

If the issue is still blocking or critical to you, please file a new issue and we will do our best to respond as soon as possible.
When you file a new issue, please ensure following additional information are provided.

o If you believe it’s a bug, provide detail repro steps.
o If it’s a feature request, please note as such
o Expected outcome
o Is this a blocking issue?

Thank you,
Azure IoT Developer and Device team

@konichi3 konichi3 closed this as completed Jan 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug external dependency Cannot fix only in this code base. It depends on the fix on third-party Obsolete
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@LazarusX @adashen @konichi3