Incorrect nanosecond calculation for trapper items

XMLWordPrintable

    • Type: Incident report
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: 3.0.8, 3.2.4, 3.4.0alpha1
    • Component/s: Proxy (P), Server (S)
    • None
    • Sprint 51 (Apr 2019)

      When sending trapper values with timestamps only seconds can be set, so server assigns nanosecond value. However instead of starting with 0 the nanoseconds are taken from server-client time difference data, which practically is a random value.

      This means that if two values are sent with the same timestamp the second value timestamp might be less than first value timestamp.

            Assignee:
            Michael Veksler
            Reporter:
            Andris Zeila
            Team A
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: