From 10cb2902057ba2c5b906f07449ac30e228cb488a Mon Sep 17 00:00:00 2001 From: riobah <31589101+riobah@users.noreply.github.com> Date: Sat, 9 Mar 2024 18:10:32 +0300 Subject: [PATCH] Updating comment for invalidated_radio_threshold_report_req_v1.timestamp - it is seconds, not milliseconds The comment states the `timestamp` field of `invalidated_radio_threshold_report_req_v1` message is in milliseconds but the data shows that it is in seconds: ``` verified_invalidated_radio_threshold_ingest_report_v1 { status: 0, timestamp: 1709986943271n, report: invalidated_radio_threshold_ingest_report_v1 { receivedTimestamp: 1709986005909n, report: invalidated_radio_threshold_report_req_v1 { cbsdId: '', hotspotPubkey: , reason: 0, timestamp: 1709985995n, carrierPubKey: , signature: Uint8Array(0) [] } } } ``` --- src/service/poc_mobile.proto | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/service/poc_mobile.proto b/src/service/poc_mobile.proto index d03c68ac..201e2482 100644 --- a/src/service/poc_mobile.proto +++ b/src/service/poc_mobile.proto @@ -178,7 +178,7 @@ message invalidated_radio_threshold_report_req_v1 { bytes hotspot_pubkey = 2; // the reason the thresholds are invalidated invalidated_threshold_reason reason = 3; - // Timestamp in milliseconds since unix epoch + // Timestamp in seconds since unix epoch // of when the thresholds were invalidated uint64 timestamp = 4; // pubkey of the carrier identity service