Skip to content

feat: max_hz rate-cap column on ROS2DiagnosticsInfo - #5

Merged
alvgaona merged 1 commit into
mainfrom
feature/rew-200
Jul 20, 2026
Merged

feat: max_hz rate-cap column on ROS2DiagnosticsInfo#5
alvgaona merged 1 commit into
mainfrom
feature/rew-200

Conversation

@alvgaona

@alvgaona alvgaona commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds an optional max_hz column to the ROS2DiagnosticsInfo archetype so the bridge can report the effective per-topic throttle cap and viewers can annotate the wire rate. An empty column entry means the topic is unthrottled, mirroring how latency_ms encodes absence, which is also the compatibility contract. Older viewers ignore the unknown component and a newer viewer paired with an older bridge simply renders no cap.

Related

REW-200

Breaking change

Adding a field to DiagnosticsMeta is breaking for constructors, hence the bump to 0.7.0.

The bridge's per-topic throttle reports its effective cap so viewers can
annotate the wire rate. Empty column entry means unthrottled. Breaking
for DiagnosticsMeta constructors, hence 0.7.0.
@alvgaona
alvgaona merged commit b423572 into main Jul 20, 2026
3 checks passed
@alvgaona
alvgaona deleted the feature/rew-200 branch July 20, 2026 14:39
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.

1 participant