fix(core): ensure project order in graph is deterministic #19968
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.
Current Behavior
The hash of the project configuration can change every run when using implicit dependencies configurations that contain glob patterns.
Expected Behavior
The project configuration hash is stable when the implicit dependencies have not changed. This is a pretty major issue, and a better fix would likely be to figure out why the order isn't deterministic to begin with, but it would be a larger PR and isn't obvious after looking over the code for a bit. I think the glob results are being processed in a different order when creating the graph nodes, and thats a lot harder to fix than just sorting the normalized array when we hash tasks.
Related Issue(s)
Fixes #19820