Repository navigation
[uss_qualifier/reports] Specify participants associated with resources - #1820
Open
BenjaminPelletier wants to merge 1 commit into
Open
BenjaminPelletier wants to merge 1 commit into
BenjaminPelletier wants to merge 1 commit into
Conversation
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 resource origin block at the top of test scenario pages in the uss_qualifier sequence view artifact is useful to determine where the resource used in the scenario came from, but it's often very useful to know which participant's resource it is (for instance, USS 1's DSS, USS 2 as a flight planner). This PR adds that capability by recording resource participant associations in the same way as resource origins.
I encountered the problem in #1819 while developing this PR which is why there is some fiddly type checking/inspection/import workarounds included. I've instructed agents not to make the problem worse while we await resolution of #1819. The first note added to AGENTS.md can be removed when #1819 is resolved.