You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mark TSServer reponses affected by updateGraph calls #34774
TSServer logs currently get very noisy with updateGraph calls, but it's not clear what is actually the cause of the work being done there. From discussion with Andrew Casey (@amcasey), it sounds like a reasonable solution is to have TSServer responses should indicate that they're forcing updateGraph calls.
changed the title [-]Mark whenever TSServer responses trigger an `updateGraph` [/-][+]Mark TSServer reponses affected by `updateGraph` calls[/+]on Oct 28, 2019
The goal here is not to determine what triggers graph updates, but which operations are affected by updateGraph computations (i.e. delays), how often, and to what extent.
Activity
[-]Mark whenever TSServer responses trigger an `updateGraph` [/-][+]Mark TSServer reponses affected by `updateGraph` calls[/+]amcasey commentedon Oct 28, 2019
The goal here is not to determine what triggers graph updates, but which operations are affected by
updateGraphcomputations (i.e. delays), how often, and to what extent.Report time spent in updateGraph
Report time spent in updateGraph (#35675)