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.
Expose import graph to tasks #13680
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
Uh oh!
There was an error while loading. Please reload this page.
Expose import graph to tasks #13680
Changes from all commits
15499afFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Nullable safety gap in deserialization
importedPathis initialized tonulland passed toTranslate(ref string). PerBinaryTranslator.TranslateNullable: if the stream marker isfalse, the method returns early andimportedPathremainsnull. This null is then passed tonew ProjectImportEdge(importedPath, ...)whereImportedProjectPathis declared as non-nullablestring.While the writing path guarantees non-null values (they come from
FullPathwhich is validated), corrupted or forward-incompatible streams could trigger this path.Consider adding a defensive null check:
Or at minimum suppress the nullable warning with
importedPath!to document the invariant explicitly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[MODERATE] Correctness — Null
importedPathsilently violates non-nullable contractDuring deserialization the code initialises:
ITranslator.Translate(ref string)wraps the value in a nullable-marker protocol: on the read side,TranslateNullablereads one boolean; iffalse, it returns early and leaves the local unchanged (stillnull). So if the stream ever marks the path as null (corrupted packet, version skew, or crafted stream),importedPathstaysnulland gets silently passed toProjectImportEdgewhose first positional parameter isstring ImportedProjectPath— non-nullable by declaration. This will produce anImportEdgeslist whose entries haveImportedProjectPath == null, causing NREs in any caller that unconditionally dereferences it.In practice the writer never emits a null
ImportedProjectPathbecauseresolvedImport.ImportedProject.FullPathis always populated. But the deserializer has no local guard.Recommendation:
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.