Skip to content

Remove timestamp fallbacks for non-batched publishing#141

Draft
mjohanse-emr wants to merge 1 commit into
mainfrom
users/mjohanse/remove_timestamp_fallbacks
Draft

Remove timestamp fallbacks for non-batched publishing#141
mjohanse-emr wants to merge 1 commit into
mainfrom
users/mjohanse/remove_timestamp_fallbacks

Conversation

@mjohanse-emr

@mjohanse-emr mjohanse-emr commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

What does this Pull Request accomplish?

This PR removes the timestamp fallbacks from non-batched publish measurement.

Before this change, if timestamp was not provided, we would fall back to one of these two values:

  1. Waveform t0 if we are publishing a waveform and t0 is set.
  2. The current time if we are publishing a waveform without t0 or publishing any other type.

The desire is to conceptually move this logic into the Datastore Server. The implementation may not look exactly the same, but the goal on the client side is just to pass through the provided timestamp without altering it.

Why should this Pull Request be merged?

AB#3926275

We want to remove the timestamp fallbacks until we decide how to handle it on the server side.

What testing has been done?

I updated two unit tests to check for a default PrecisionTimestamp if no timestamp is provided.
All unit tests and acceptance tests pass.

Signed-off-by: Michael Johansen <michael.johansen@emerson.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant