This repository was archived by the owner on Jun 5, 2025. It is now read-only.
fix crashing due to null exception in compute system cache #2880
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the pull request
This PR fixes a crashing issue where we look at the lazy loaded value of a DeveloperID without a null check on the value.
Video of me invoking each operation without crashing Dev Home:
performing.operations.without.crashing.mp4
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
Confirmed all hyper-v operations do not crash dev home.
Note: Once #2861 is fixed the state of the card should be updated correctly
PR checklist