Repository navigation
fix(planning): latch max_vel with transient_local QoS - #3634
Merged
Conversation
Publish the configured max_vel when no sender has set a limit, using transient_local so subscribers that start later still receive it. Co-authored-by: Cursor <cursoragent@cursor.com>
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
|
shmpwk
approved these changes
Oct 21, 2026
shmpwk
deleted the
fix/v0.64/e2e_scenario_pass/external_velocity_limit_initial_max_vel
branch
October 21, 2026 23:44
shmpwk
pushed a commit
to tier4/pilot_auto_planning
that referenced
this pull request
Nov 5, 2026
…_universe#3634) Publish the configured max_vel when no sender has set a limit, using transient_local so subscribers that start later still receive it. Co-authored-by: Cursor <cursoragent@cursor.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.
backport
tier4/pilot_auto_planning#14
An empty clear was published as max_velocity 0 because hardest_limit_ stayed at its default. Initialize it from max_vel so departure is not blocked.
slack