Skip to content

Conversation

@connorjclark
Copy link
Collaborator

ref #15944

Lantern does not need to know about our lrStatistics object. Instead, we can set the timing object based on it in our LH NetworkRequest -> Lantern NetworkRequest adapter.

@connorjclark connorjclark requested a review from a team as a code owner April 15, 2024 18:09
@connorjclark connorjclark requested review from adamraine and removed request for a team April 15, 2024 18:09
it('should use lrStatistics when needed', () => {
global.isLightrider = true;
const record = createRecord({timing: {}, lrStatistics: {requestMs: 100}});
const record = createRecord({timing: {}, lrStatistics: {TCPMs: 1, requestMs: 100}});
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was only accidentally working before - it was creating two NaN entries in the origin estimator using the code path I deleted. Without that code, zero samples were generated and the test was erroring w/ "No timing information".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants