Skip to content

TEMPORARY: require explicit msg_type for inbound topics (BOT-301) - #35

Closed
stephen-derosa wants to merge 1 commit into
sderosa/integration-cleanfrom
sderosa/working-integration
Closed

stephen-derosa wants to merge 1 commit into
sderosa/integration-cleanfrom
sderosa/working-integration

Conversation

@stephen-derosa

Copy link
Copy Markdown
Collaborator

Isolated single commit re-adding the temporary inbound msg_type stopgap on top of the clean integration branch, for continued integration testing. LiveKit DataTracks do not yet carry ROS message-type metadata, so a pure consumer cannot infer an inbound track's type; this lets the bridge create the republishing publisher from a configured type.

Drop this commit (it is the exact inverse of "Drop temporary inbound msg_type stopgap (BOT-301)" on sderosa/integration-clean) once DataTracks propagate the ROS type with the track.

Isolated single commit re-adding the temporary inbound msg_type stopgap
on top of the clean integration branch, for continued integration
testing. LiveKit DataTracks do not yet carry ROS message-type metadata,
so a pure consumer cannot infer an inbound track's type; this lets the
bridge create the republishing publisher from a configured type.

Drop this commit (it is the exact inverse of "Drop temporary inbound
msg_type stopgap (BOT-301)" on sderosa/integration-clean) once
DataTracks propagate the ROS type with the track.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@linear-code

linear-code Bot commented Jul 9, 2026 •

Copy link
Copy Markdown
BOT-301 Services <> RPC

  • Align ROS2 QOS with livekit QOS (needs further work)
  • forward ROS2 services to LiveKit RPC calls
  • for LiveKit RPC calls to ROS2 services

NOTE: RPC calls currently only take in strings. So this is blocked by MCAP header in DataTracks work. cc jacobgelman to reference ticket number.

NOTE: while this can be targeted for V1.25/1.5 this work is imperitive to a complete project. If the rest of the project is complete and this is all thats left we can simply use strings and encode the ros2 messages as base64.

Review in Linear

@stephen-derosa

Copy link
Copy Markdown
Collaborator Author

closed in favor of:
#36

@stephen-derosa
stephen-derosa deleted the sderosa/working-integration branch July 9, 2026 18:12
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