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(network-request): use ms instead of seconds #14567

Merged
merged 4 commits into from
Nov 29, 2022
Merged

Conversation

connorjclark
Copy link
Collaborator

@connorjclark connorjclark commented Nov 28, 2022

split out from #14311

Changes the network request (aka network records) start and end time properties to be in ms, instead of seconds. This should not impact any audit values - network-requests was already converted to ms

However critical-request-chain timings and startTime/endTime in lantern nodes remain as seconds. They'll be adjusted in a followup.

@connorjclark connorjclark requested a review from a team as a code owner November 28, 2022 23:23
@connorjclark connorjclark requested review from brendankenny and removed request for a team November 28, 2022 23:23
Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

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

nice!
so happy to be so much closer to seconds-free.

one Q below that's got me pensive.

@@ -25,14 +25,14 @@ class NetworkNode extends BaseNode {
* @return {number}
*/
get startTime() {
return this._record.startTime * 1000 * 1000;
return this._record.startTime * 1000;
Copy link
Member

Choose a reason for hiding this comment

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

seems kinda awkward that the lantern depgraph and crc are still in seconds.

wdyt about changing both of those in here, too?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I mentioned this in the other PR, but I would like to keep lantern changes in a separate PR. I expect it to change a number of things in a trivial way (snapshots, accuracy) due to the limits of floating point precision. It should be a quick change I can follow up with when this lands.

Copy link
Member

Choose a reason for hiding this comment

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

ok!

Copy link
Member

Choose a reason for hiding this comment

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

maybe add some comments in network-node/base-node/cpu-node and crc that these times are in seconds?
and/or a TODO?

cuz right now its kinda impossible to tell from the code.

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.

None yet

4 participants