Repository navigation
[uss_qualifier] Move planned-flights state out of flight planner client - #1781
Open
BenjaminPelletier wants to merge 2 commits into
Open
BenjaminPelletier wants to merge 2 commits into
BenjaminPelletier wants to merge 2 commits into
Conversation
BenjaminPelletier
marked this pull request as ready for review
October 8, 2026 01:13
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The key feature to enable #1458 resolution is the ability to run test scenarios in parallel. One thing currently preventing this outcome is that flight planner clients have attached state that tracks planned flights via mutation. This means scenarios cannot run in parallel because the state shared by the flight planner client used in both scenarios would be polluted by flights generated by the other scenario.
This PR fixes that problem by moving the planned-flight state out of the flight planner client and into each scenario individually.