Add Logging and warning if a segment saving does not save the actual content (presumably due to mobile network latencies)

XMLWordPrintable

    • Critical
    • None
    • Hide
      7.40.6 / 7.41.1: FIX: Detected segment savings that actually are not saved are only logged due to many false-positive detections
      7.40.5: FIX: Add detection and warning of segment savings that actually were not saved presumably due to high mobile network latencies
      Show
      7.40.6 / 7.41.1: FIX: Detected segment savings that actually are not saved are only logged due to many false-positive detections 7.40.5: FIX: Add detection and warning of segment savings that actually were not saved presumably due to high mobile network latencies
    • None

      PROBLEM

      It can happen, a segment is saved in the editor but the syncing to the server fails, what seems to be connected to mobile network latencies - although the cause is not fully understood

      SOLUTION

      Since we can detect the Problem by comparing the set targetEdit throughout the different phases, we add a detection of a problem and present the user an error hinting at the problem and logging the console contents

      FRONTEND TESTING

      Since it is not known how to reproduce the error there can be no real frontend-testing. It could be attempted to challenge the detection to produce false positives

      HINT

      The branch inherits from hotfix/MITTAGQI-566-add-debug-code-to-the-editor and can only be integrated after merging that branch ...

            Assignee:
            Axel Becher
            Reporter:
            Axel Becher
            Axel Becher Axel Becher
            Leon Kiz
            Leon Kiz
            Leon Kiz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None