microsoft / microsoft/AzureStorageExplorer
Storage Explorer can't find newly-created blob container when choosing to open in Storage Explorer from VS Code storage extension
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
From https://github.com/Microsoft/vscode-azurestorage/issues/64
Steps to Reproduce:
- Open storage explorer
- From VS Code storage extension, create a new blob container
- Select 'Open Azure Account from Storage Explorer' on the new container
Expected Experience:
Storage Explorer should realize it doesn't have this blob container cached, and should check if it actually exists and then show it.
Actual Experience:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow in Storage Explorer: create a blob container from the VS Code storage extension, then choose “Open Azure Account from Storage Explorer” on it. Start by tracing the open-account action and its cached-container lookup; done means a newly created container is discovered and shown instead of producing the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100