Skip to content

fix(external_velocity_limit_selector): use max_vel when no sender has… - #3628

Merged
kotaro-hihara merged 3 commits into
v4.4.0.1-hotfixfrom
fix/v4.4.0.1-hotfix/external_velocity_limit_initial_max_vel
Oct 20, 2026
Merged

kotaro-hihara merged 3 commits into
v4.4.0.1-hotfixfrom
fix/v4.4.0.1-hotfix/external_velocity_limit_initial_max_vel

Conversation

@kotaro-hihara

@kotaro-hihara kotaro-hihara commented Oct 20, 2026 •

Copy link
Copy Markdown

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

… set a limit

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.

Co-authored-by: Cursor <cursoragent@cursor.com>
@mergify

mergify Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

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.

kotaro-hihara and others added 2 commits October 20, 2026 19:16
…te subscribers

The output QoS is volatile and trajectory_modifier starts after this node, so the configured max_vel never reached ExternalVelocityLimit.

Co-authored-by: Cursor <cursoragent@cursor.com>
A volatile one-shot publish is missed by trajectory_modifier, so publish max_vel once as transient_local and match that durability on the subscribers.

Co-authored-by: Cursor <cursoragent@cursor.com>
@sonarqubecloud

Copy link
Copy Markdown

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

@kotaro-hihara
kotaro-hihara merged commit 18160cb into v4.4.0.1-hotfix Oct 20, 2026
3 of 4 checks passed
@kotaro-hihara
kotaro-hihara deleted the fix/v4.4.0.1-hotfix/external_velocity_limit_initial_max_vel branch October 20, 2026 11:46
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.

2 participants