Make large-message stripping opt-in (default: full data forwarded)#6
Merged
Merged
Conversation
Stripping uint8[] data from Image/PointCloud2/LaserScan/OccupancyGrid messages was previously on by default, so clients received metadata-only messages unless the operator knew to disable it. Flip the default: messages are forwarded intact, and stripping is enabled explicitly with strip_large_messages:=true for low-bandwidth deployments. - ros2 main: strip_large_messages parameter default true -> false - Ros2SubscriptionManager: constructor default flipped to match - New test suite covering both defaults-include-data and opt-in-strips - README/CLAUDE.md updated to document the opt-in semantics Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stripping
uint8[] datafrom Image/PointCloud2/LaserScan/OccupancyGrid messages was on by default, so clients silently received metadata-only messages unless the operator knew to disable it. This flips the behavior: full message data is forwarded by default, and stripping becomes an explicit opt-in (strip_large_messages:=true) for low-bandwidth deployments.Stacked on #5 (
fix/review-findings) — GitHub will retarget tomainautomatically when that merges.Changes
strip_large_messagesROS parameter default:true→falseRos2SubscriptionManagerconstructor default flipped to matchRos2SubscriptionManagerTestsuite (real pub/sub roundtrip): default config must deliver the full image payload; explicit opt-in must strip itTest plan
DataFieldsIncludedByDefaultwatched failing before the flip (payload stripped), passes afterOptInStrippingRemovesDatapins that opt-in stripping keeps workingpre-commit run -aclean🤖 Generated with Claude Code