This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Fix nullref in SpecializedNamespace and arg-null ProtocolInfo dict access#451
Uh oh!
There was an error while loading. Please reload this page.
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
jakebailey changed the title jakebailey changed the title 
MikhailArkhipov approved these changes Dec 3, 2018
jakebailey added a commit to jakebailey/python-language-server that referenced this pull request Nov 1, 2019
…cess (microsoft#451) Fixesmicrosoft#449. Also fixes an ArgumentNullException in a dictionary TryGetValue in ProtocolInfo. I'm not sure why that one is happening, but it's also showing up as frequently as the SpecializedNamespace issue.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
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.
Fixes#449.
Also fixes an ArgumentNullException in a dictionary TryGetValue in ProtocolInfo. I'm not sure why that one is happening, but it's also showing up as frequently as the SpecializedNamespace issue.