fix(static_obstacle_avoidance): update UUID when candidate shift is empty #8901
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.
Description
Fix rtc state transition error for static_obstacle_avoidance module.
There was a problem that the same UUID was used for candidates shift line, although the cooperateStatus has been changed to FAILED.
This happens when
removeCandidateRTCStatus
function is once called, and the candidate is re-registered in the next period.This PR generates a new UUID once the
removeCandidateRTCStatus
function is called.Related links
How was this PR tested?
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.