Re-enable initial sync tests that rely on a specific beginFetchingTimestamp with replicated fast count

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Some initial sync tests implicitly or explicitly rely on a specific beginFetchingTimestamp being set, but replicated fast count initial sync changed how this is computed where it can now be an earlier timestamp than expected.

            Assignee:
            Unassigned
            Reporter:
            Parker Felix
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: