NRID Test Scenario Timing

[wing-utm-sharing-airspace]

Observed behavior
In ASTM NetRID Display Provider behavior, Verify query to SP - our USS occasionally fails the DP queried SP check when we can see an outgoing query to the MockUSS Service Provider from out Display Provider logs.

It seems like there may be a clock sync issue between systems. For example, in the attached test run, The test queries the Display Provider under test with 'initiated_at': 2026-05-15T21:56:11.645881Z

The MockUSS logs are queried with 'from_time'=2026-05-15T21:56:11.645805Z.

Our Display Provider indicates the request to the Mock Service Provider was sent at 2026-05-15 21:56:11.02.

Is it possible the the query to the MockUSS logs is not sufficiently early enough to pick up the requests?

45db187f-6f03-4ca8-8278-41f9c9bcd205.zip

Observed behavior
Generally would expect to consistently be able to pass tests without all systems clocks being perfectly synced.

[BenjaminPelletier]

Agreed; it does look like we query for interactions strictly past uss_qualifier's local clock as of dispatch of the request that should trigger the behavior, and that is only guaranteed to work if all clocks are perfectly in sync. We should make sure scenarios will still work even if clocks between systems are not perfectly in sync. In general, I think that means making sure any evaluation of interactions collected from mock_uss do not depend on uss_qualifier's clock.

[BenjaminPelletier]

I believe #1460 resolves this for the specific scenarios mentioned, though we should also look more holistically through the codebase to see where else server clock sync may need to be mitigated.