Skip to content

Fix issue #23: prevent duplicate diagnostics when external node is already publishing#33

Draft
bmchalenv wants to merge 1 commit intoNVIDIA-ISAAC-ROS:mainfrom
bmchalenv:fix/issue-23-external-diagnostics
Draft

Fix issue #23: prevent duplicate diagnostics when external node is already publishing#33
bmchalenv wants to merge 1 commit intoNVIDIA-ISAAC-ROS:mainfrom
bmchalenv:fix/issue-23-external-diagnostics

Conversation

@bmchalenv
Copy link
Contributor

Fixes #23.

Subscribe to /diagnostics in GreenwaveMonitor to track topic names already published externally. add_topic() now returns an error if a topic's diagnostics are already being published by an external node, preventing duplicate and potentially conflicting diagnostic entries.

…ernal node is already publishing

Subscribe to /diagnostics in GreenwaveMonitor to track topic names already
published externally. add_topic() now returns an error if a topic's diagnostics
are already being published by an external node, preventing duplicate and
potentially conflicting diagnostic entries.

Also fix copyright-required pre-commit hook to only run at pre-commit stage,
preventing it from incorrectly checking COMMIT_EDITMSG for a copyright header.

Signed-off-by: Blake McHale <bmchale@nvidia.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.

A duplicate greenwave diagnostics object is generated by Greenwave Monitor when the diagnostics are published externally

1 participant