Uploaded image for project: 'Couchbase Lite'
  1. Couchbase Lite
  2. CBL-2443

Race with expiration date set vs get

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.1.0
    • 3.0, 3.1.0
    • LiteCore
    • Security Level: Public
    • None
    • 1

    Description

      2021-09-22 22:12:48.641521-0700 xctest[75647:1365682] CouchbaseLite Database Verbose: {DB#3} begin transaction
      2021-09-22 22:12:48.642195-0700 xctest[75647:1365682] CouchbaseLite Database Verbose: {DB#3} SQLiteKeyStore(default) set expiration of '-eigiK_qNtzs7joBHDCB31Y' to 1632373969635
      2021-09-22 22:12:48.642338-0700 xctest[75647:1365682] CouchbaseLite Database Verbose: {DB#3} commit transaction
      

      {DB#3}

       commits the expiration as 1632373969635

      2021-09-22 22:12:48.642566-0700 xctest[75647:1365771] CouchbaseLite Database Verbose: {DB#5} Next expiration time is 1632373978635
      

      but then {DB#5} fetches previous expiration date as the next expiration

      Looks like a race is happening here?

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jimb Jim Borden
              jimb Jim Borden
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty