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

If a Custom Connection is Corrupted, Notify User, Don't Just Fail #985

MRayermannMSFT opened this issue Dec 10, 2018 · 2 comments


Copy link

@MRayermannMSFT MRayermannMSFT commented Dec 10, 2018

If a custom connection is corrupted, Storage Explorer fails to load anything in the tree. We should try to:

  1. Fix the azure resource producer to not fail if loading custom connections fails
  2. Catch corrupted connections earlier
  3. Give better error messages for corrupted connections
@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Dec 10, 2018
@MRayermannMSFT MRayermannMSFT added this to the 1.9.0 milestone Dec 10, 2018
@MRayermannMSFT MRayermannMSFT modified the milestones: 1.9.0, 1.10.0 May 20, 2019
@MRayermannMSFT MRayermannMSFT self-assigned this Jul 1, 2019
@MRayermannMSFT MRayermannMSFT moved this from Committed to Under Review in Storage Explorer Jul 26, 2019
@MRayermannMSFT MRayermannMSFT moved this from Under Review to In Progress in Storage Explorer Aug 8, 2019

This comment has been minimized.

Copy link

@placidseven placidseven commented Aug 22, 2019

I have clients using 1.9.0 and the issue is still present. Has this bug fix not been committed yet?


This comment has been minimized.

Copy link
Member Author

@MRayermannMSFT MRayermannMSFT commented Sep 3, 2019

We've checked in better handling for Storage Accounts as this is what we see people running into most. If people see it at the container level we can add the add'l error handling there as well.

Storage Explorer automation moved this from In Progress to Done Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.