-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(intersection): fix uninitialized tl_arrow_info variable issue #4283
fix(intersection): fix uninitialized tl_arrow_info variable issue #4283
Conversation
Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #4283 +/- ##
==========================================
- Coverage 15.20% 15.20% -0.01%
==========================================
Files 1489 1489
Lines 102668 102670 +2
Branches 31527 31530 +3
==========================================
Hits 15613 15613
- Misses 70104 70106 +2
Partials 16951 16951
*This pull request uses carry forward flags. Click here to find out more.
☔ View full report in Codecov by Sentry. |
@shmpwk @takayuki5168 I checked that there is no degradation, so can you approve this PR? |
…towarefoundation#4283) * update first conflicting/attention area Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * debug 1113, 1393 Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * migrated to latest Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> --------- Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
…towarefoundation#4283) * update first conflicting/attention area Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * debug 1113, 1393 Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * migrated to latest Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> --------- Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
…towarefoundation#4283) (#667) fix(intersection): fix uninitialized tl_arrow_info variable issue (autowarefoundation#4283) * update first conflicting/attention area * debug 1113, 1393 * migrated to latest --------- Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
…towarefoundation#4283) * update first conflicting/attention area Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * debug 1113, 1393 Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * migrated to latest Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> --------- Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
…towarefoundation#4283) * update first conflicting/attention area Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * debug 1113, 1393 Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> * migrated to latest Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp> --------- Signed-off-by: Mamoru Sobue <mamoru.sobue@tier4.jp>
Description
IntersectionLanelets::tl_arrow_solid_on
was uninitialized and was not updated carelessly. Due to this bug whenleft/right arrow
is not solid on when turning left/right each variable was like this when I debug printed.So for most of the time when the path is covering the intersection this condition was true in every iteration. So
first_conflicting_area
was null at first, and then initialized to an area after a few iterations.But if
lanelets_.value().tl_arrow_solid_on
is left uninitialized to 0, that condition will be applied only at the first time that the corresponding intersection module is activated, sofirst_conflicting_area
was permanently 0.Related links
https://tier4.atlassian.net/browse/RT1-2875?focusedCommentId=128666&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-128666
Tests performed
no degradation on the CI: https://evaluation.tier4.jp/evaluation/reports/50fcf368-aa63-574e-9de2-89eb26f5e8bc?project_id=prd_jt
Notes for reviewers
Interface changes
Not applicable.
Effects on system behavior
Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.