Immeidately mark dependencies as deprecated when the target plan was cleared #115
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.
This should resolve the issue report here where a robot waits for an excessive amount of time on a traffic dependency that has already moved out of the way.
The bug occurs when Robot A needs to wait at some point for Robot B to move out of the way, but Robot B has already completely finished its route before Robot A reaches the waiting point.
This PR detects whether Robot B has already finished its route while creating the dependency subscription, and immediately deprecates the dependency if true. If the robot has not finished its route at the time the dependency subscription is made, then there are other mechanisms that will detect the change and alert the waiting robot.