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

add time sync logs #583

Merged
merged 5 commits into from
Mar 21, 2024
Merged

add time sync logs #583

merged 5 commits into from
Mar 21, 2024

Conversation

MishkaMN
Copy link
Contributor

@MishkaMN MishkaMN commented Mar 19, 2024

PR Details

Description

Adds logs to support usdot-fhwa-stol/carma-analytics-fotda#43

Related Issue

CDAR-774

Motivation and Context

Data Analysis

How Has This Been Tested?

Types of changes

  • Defect fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that cause existing functionality to change)

Checklist:

  • I have added any new packages to the sonar-scanner.properties file
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
    V2XHUB Contributing Guide
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@MishkaMN MishkaMN changed the title add sim add time sync logs Mar 19, 2024
@@ -18,12 +18,12 @@ namespace CDASimAdapter{
success = GetConfigValue<double>("X", location.X);
success = success && GetConfigValue<double>("Y", location.Y);
success = success && GetConfigValue<double>("Z", location.Z);
PLOG(logINFO) << "Location of Simulated V2X-Hub updated to : {" << location.X << ", "
PLOG(logINFO) << "Location of Simulated V2X-Hub updated to : {" << location.X << ", "
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do all you PRs have changes in random lines of code. There is no change here right?

Copy link
Contributor

Choose a reason for hiding this comment

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

Do you have some kind of formatting running

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah it is the vscode whitespace formatter. if you turn it off in the github to see then it moves it away

std::string payload =msg.to_string();
PLOG(logDEBUG1) << "Sending Time Sync Message " << msg << std::endl;
auto time_now = std::chrono::system_clock::now();
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we put this entire logic inside a block that is skipped if not in debug mode and add a comment here indicating what this is for and maybe that it will eventually be removed.

Copy link
Contributor

@paulbourelly999 paulbourelly999 left a comment

Choose a reason for hiding this comment

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

See comments

@paulbourelly999
Copy link
Contributor

Also I just merged a PR that fixes some all of the CI stuff into the release candidate. I had previously already fixed it in develop. You may want to rebase you PR on that to make sure the failures here are not independent and to get sonar reports.

@paulbourelly999 paulbourelly999 merged commit 6d60d91 into lavida Mar 21, 2024
9 checks passed
@paulbourelly999 paulbourelly999 deleted the feature/add-time-sync-logs branch March 21, 2024 17:30
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