Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core(lantern): remove LR statistics #15946

Merged
merged 3 commits into from
Apr 15, 2024
Merged

core(lantern): remove LR statistics #15946

merged 3 commits into from
Apr 15, 2024

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
@@ -332,7 +334,7 @@ describe('DependencyGraph/Simulator/NetworkAnalyzer', () => {

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".

core/lib/lantern/types/lantern.d.ts Outdated Show resolved Hide resolved
Co-authored-by: Adam Raine <6752989+adamraine@users.noreply.github.com>
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