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

Detaching SAS service connections sometimes results in errors #537

Closed
craxal opened this issue Aug 2, 2018 · 2 comments
Closed

Detaching SAS service connections sometimes results in errors #537

craxal opened this issue Aug 2, 2018 · 2 comments
Assignees
@MRayermannMSFT
Labels
🪲 bug Issue is not intended behavior ⚙️ attach Related to attaching via keys, SAS, etc. ❔ investigate We need to look into this further ✅ no repro Cannot be reproduced
Milestone
1.13.0

Comments

@craxal
Copy link
Contributor

craxal commented Aug 2, 2018 •
edited
Loading

Storage Explorer Version: 1.4.0
Platform/OS Version: Windows 10
Architecture: ia32
Regression From: 1.3.1

Steps to Reproduce:

  1. Attach several blob containers via SAS URI.
  2. Refresh the Local & Attached > Storage Accounts > (SAS-Attached Services) > Blob Containers node.
  3. Attempt to detach each connection made in step 1.

Expected Experience:

Detachment happens smoothly for each node.

Actual Experience:

An error occurs after attaching. The Blob Containers node no longer displays children. Clicking the Load more button resurfaces the same error.

image

Workaround:

Just refresh the Blob Containers node, and all the children appear normally.
@craxal craxal added ⚙️ attach Related to attaching via keys, SAS, etc. 🪲 bug Issue is not intended behavior ❔ investigate We need to look into this further labels Aug 2, 2018
@craxal craxal added this to the 1.5.0 milestone Aug 2, 2018
@MRayermannMSFT MRayermannMSFT modified the milestones: 1.5.0, 1.6.0 Oct 25, 2018
@craxal craxal modified the milestones: 1.6.0, 1.7.0 Dec 3, 2018
@MRayermannMSFT
Copy link
Member

I'm pretty sure we fixed this, and neither Jason nor I have seen it recently. I'll re verify today and close if it doesn't repro.

@MRayermannMSFT MRayermannMSFT added this to the 1.13.0 milestone Mar 16, 2020
@MRayermannMSFT MRayermannMSFT self-assigned this Mar 16, 2020
@MRayermannMSFT
Copy link
Member

Unable to reproduce.

@MRayermannMSFT MRayermannMSFT added the ✅ no repro Cannot be reproduced label Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MRayermannMSFT MRayermannMSFT

Labels
🪲 bug Issue is not intended behavior ⚙️ attach Related to attaching via keys, SAS, etc. ❔ investigate We need to look into this further ✅ no repro Cannot be reproduced
Projects
None yet
Milestone
1.13.0
Development

No branches or pull requests
2 participants
@craxal @MRayermannMSFT