Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Logging Replicator reasons of state change

Description

In addition to seeing the following logs when replicator changes state,

   [Sync]: {Puller#357} {Coll#0} now busy

We would like to see reason for debugging purpose, like "(_caughtUp=0)" in the following 

    [Sync]: {Puller#357} {Coll#0} state now busy (_caughtUp=0)

 

Activity

Show:

CB robot August 27, 2024 at 1:47 AM

Build couchbase-lite-log-3.3.0-20 contains couchbase-lite-core commit 8dda4bd with commit message:
: Logging Replicator reasons of state change (#2016)

CB robot August 26, 2024 at 11:23 PM

Build couchbase-lite-cblite-3.3.0-21 contains couchbase-lite-core commit 8dda4bd with commit message:
: Logging Replicator reasons of state change (#2016)

buildteam_automation July 23, 2024 at 12:53 AM

Build couchbase-lite-ios-3.3.0-9 contains couchbase-lite-core commit 8dda4bd with commit message:
: Logging Replicator reasons of state change (#2016)

CB robot July 16, 2024 at 5:47 PM

Build couchbase-lite-core-3.3.0-38 contains couchbase-lite-core commit 8dda4bd with commit message:
: Logging Replicator reasons of state change (#2016)

CB robot June 5, 2024 at 11:40 AM

Build couchbase-lite-ios-3.2.0-103 contains couchbase-lite-core commit 8dda4bd with commit message:
: Logging Replicator reasons of state change (#2016)

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Sprint

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created January 29, 2024 at 6:29 AM
Updated August 27, 2024 at 1:47 AM
Resolved May 3, 2024 at 11:00 PM
Instabug