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

TEL - Create Latency Node #127

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

TEL - Create Latency Node #127

wants to merge 1 commit into from

Conversation

davidbeechey
Copy link
Contributor

No description provided.

@davidbeechey davidbeechey self-assigned this Jul 2, 2024

const auto payload = nextMessage->payload;
const auto topic = core::MqttTopic::kLatencyResponse;
const core::MqttMessage::Header header{.timestamp = 0,
Copy link
Contributor

Choose a reason for hiding this comment

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

you need a WallClock as a data member, then:
.timestamp = time_.now().time_since_epoch().count()

}

void Latency::run()
{
Copy link
Contributor

Choose a reason for hiding this comment

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

while (true) otherwise this runs once lol

@@ -152,7 +152,7 @@ export const PodsProvider = ({ children }: { children: React.ReactNode }) => {
publish(
'latency/request',
JSON.stringify({
latency: new Date().getTime().toString(),
timestamp: new Date().getTime().toString(),
Copy link
Contributor

Choose a reason for hiding this comment

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

here and elsewhere, are you remembering that all mqtt messages are of the format:

{
  header : {
    timestamp: int,
    priority: int
  },
  payload: { rest of data }
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahhh I see. Will need to change this throughout the telemetry code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants