| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thank you Simon for the review!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
PTAL
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This histogram expired on 2023-05-01.Can you explain a bit about SuppressLatencyRecording()?
This looks something more than just removing expired histograms.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thank you Takashi for the review!
This histogram expired on 2023-05-01.Can you explain a bit about SuppressLatencyRecording()?
This looks something more than just removing expired histograms.
Yeah we ended up adding a new method here because it is a shared class. ScriptPromiseResolverWithTracker is a helper used by multiple features to record both ".Result" and ".Latency" histograms (or ".Latency2" in one case).
We only want to remove the ".Latency" histogram recording from this one instance (media_devices.cc), but the other clients of SPRWT are tracking ".Latency" histograms that are still active and won't be deleted. So we need clients to be able to turn on/off the recording of the ".Latency" histogram. (Usually these histogram removal CLs look like removing a RecordHistogram() line in the code, but here it's a guard clause to prevent going down a branch).
An alternative might be to add a boolean to the ctor of SPRWT for `bool record_latency = true`. That way, we wouldn't need to update the other call sites at all, and the media_devices call site would just look like `..., /*record_latency=*/false);`. This avoids adding a new method.
lmkwyt, thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |