Russ Hammett

Yeah I'm a bit unclear on how this is supposed to be integrated, or if this should just be more of a boolean flag? `GitVersioning` just as an example seems...

Sorry for the spam... I didn't realize that referencing issues on my own fork would hit the issue on origin. Still learning the flow of git/hub :) I figured it...

There is currently no differences between the group level configuration and the test case level parameter for many properties, the inclusion of both was just an oversight. I'll look into...

Hey @AlexThurston I wouldn't say this is exactly "intended" behavior, but it *kind of* is at the moment, anything that hits our "workflow" queue - things that need approval -...

I updated the cancel endpoints to return the same sort of payload the previous implementation did:  Regarding what canceling a test session actually does? Potentially nothing, but if the...

Guessing it's a miss in the validator around the condition of having `!dataUnitLenMatchesPayload`, but registering capabilities where the `dataUnitLen` and `payloadLen` only have matching values.

@EdSmith-Viasat I don't really understand what's being asked here... `partyIds` are randomly provided in the vector set to be plugged in as a portion of your fixed info construction for...

@GlennUL this is possible yes - though KAS has a *lot* of moving parts, and I'm currently otherwise heavily occupied in other work. I can try to take a look...

I unfortunately will not have the bandwidth to get to this at the moment, but if this is something that is preventing a validation, please feel free to have the...

@locksmithone the intention of the flag is to indicate that the IUT *CAN* support test cases where the payload and data unit length don't match. The testing still operates under...