Avoid tasserting when we encounter a bucket document mismatch

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-12-26
    • 135
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when decompressing and updating a bucket document, we can trip a tassert when "Bucket document changed between initial read and update". We don't need to be tasserting here and should update it by throwing a WCE instead.

            Assignee:
            Fausto Leyva (Inactive)
            Reporter:
            Fausto Leyva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: