Revert Emit eval props if requested by any sink (#10243)#10447
Merged
f-alizada merged 2 commits intodotnet:mainfrom Aug 2, 2024
Merged
Revert Emit eval props if requested by any sink (#10243)#10447f-alizada merged 2 commits intodotnet:mainfrom
f-alizada merged 2 commits intodotnet:mainfrom
Conversation
Member
Author
f-alizada
approved these changes
Aug 2, 2024
Contributor
f-alizada
left a comment
There was a problem hiding this comment.
Let's revert the change and investigate later per:
https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems/edit/2173921
AR-May
approved these changes
Aug 2, 2024
JanKrivanek
added a commit
that referenced
this pull request
Aug 12, 2024
JanKrivanek
added a commit
that referenced
this pull request
Aug 15, 2024
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/VS/pullRequest/567354#1721971513
Context
#10243 introduced proper populating of eval props based on Loggers requests - this however can lead to props being populated on both - ProjectStartedEventArgs and EvaluationProjectFinishedEventArgs - which leads to higher allocations. We have couple options how to proceed: