This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
Fix validation of flight plans #25
Merged
Conversation
This file contains 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
Flight plans received from the client failed to pass validation, which upon further investigation revealed a bug in the algorithm. Since flight plans are stored in reverse order, checking if the next node is the same has to be done by comparing the last nodes in the lists.
jdno
force-pushed
the
fix-flight-plan-validation
branch
from
051d81e
to
2260019
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Flight plans received from the client failed to pass validation, which
upon further investigation revealed a bug in the algorithm. Since flight
plans are stored in reverse order, checking if the next node is the same
has to be done by comparing the last nodes in the lists.