-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEN0100 and GEN0105 uss_qualifier checks to verify ASTM F3548-21 #468
Comments
Discussing the topic with @mickmis and @barroco, we were wondering if this might not require adding a new endpoint, depending how strictly we want to test the requirements: The gist of our discussion:
We also conclude that logs will likely contain what we need to cover GEN0100/0105, but these won't be available for the initial MVP so we need an alternative. (If this requires more discussion/editing we can take it to a separate design doc) Retained approachAt the weekly meeting held on 16th of Jan '24, we agreed to have a first check using the "create something in the past" approach, which should be forbidden, and expect that the USS will reject it. More precisely, we would call the A more comprehensive coverage of GEN0100/105 will be done once we have access to log data. |
Implemented in #555 |
As part of #274, we should check GEN0100 and GEN0105. Presumably these requirements will be checked together since a good way of measuring time synchronization (GEN0100) is via timestamps (GEN0105).
Possible approach 1:
When op intent details change (creation or update), note when the change was made. If volumes end time is before time change was made, USS may be violating USS0105, or it may be violating GEN0100, or it may be violating GEN0105.
Possible approach 2 (not mutually exclusive):
If/when we obtain log data, compare timestamps for when we know certain events occurred to when they are indicated in the logs1, 2, 3
The text was updated successfully, but these errors were encountered: