Skip to content

If we failed to get a default profile, fail the settings load#1343

Merged
DHowett-MSFT merged 1 commit intomasterfrom
dev/duhowett/defaultstopmaybe
Jun 20, 2019
Merged

If we failed to get a default profile, fail the settings load#1343
DHowett-MSFT merged 1 commit intomasterfrom
dev/duhowett/defaultstopmaybe

Conversation

@DHowett-MSFT
Copy link
Contributor

This stops the crash in #1318.

@DHowett-MSFT
Copy link
Contributor Author

@zadjii-msft this fixes a symptom. I do not know if it is correct, but it is more correct than it was. What do you think?

@zadjii-msft
Copy link
Member

It's definitely more correct, though I'm not sure popping the error dialog would be enough to clue people in that the default GUID is null.

More correct would be popping the error if the default guid isn't in the list of profiles at all.

Even more correct would be to specifically display a message that there was no default profile (though that might be too much for this release).

Obviously the most correct solution would be to figure out what causes this zeroing. I don't have a lead on this - @DHowett-MSFT you changed the title of #1318 to say "~30% impact" - do we have more repros? If we can narrow it down today I'd love to fix the real issue, but this is probably good enough if we can't.

Copy link
Member

@miniksa miniksa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is OK enough to stop the crash. I agree we should fix the root, but crashy crashy is bad.

@DHowett-MSFT DHowett-MSFT merged commit 66cb7c4 into master Jun 20, 2019
@DHowett-MSFT DHowett-MSFT deleted the dev/duhowett/defaultstopmaybe branch June 20, 2019 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants