For example, when a Requisition update does not result in a state transition for the parent Measurement then the update_time and etag of the Measurement do not change. This means that these updates are missed in StreamActiveComputations calls.
I believe this only affects Requisition and ComputationParticipant resources.
There's likely little to no impact of this currently unless we make changes to how the Herald tracks Measurement updates, so this may be more of a technical correctness fix to avoid surprises.
For example, when a Requisition update does not result in a state transition for the parent Measurement then the
update_timeandetagof the Measurement do not change. This means that these updates are missed in StreamActiveComputations calls.I believe this only affects Requisition and ComputationParticipant resources.
There's likely little to no impact of this currently unless we make changes to how the Herald tracks Measurement updates, so this may be more of a technical correctness fix to avoid surprises.