Skip to:

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

[3.1.2 backport] Investigate the default scope/collection requiring resync after upgrade

Description

Investigate a possible bug where a default collection is being identified as requiring resync after an upgrade of a db that is configured to only use the default scope and collection.

Activity

Show:

CB robot April 8, 2024 at 10:11 PM

Build sync_gateway-3.2.0-350 contains sync_gateway commit b605a61 with commit message:
[3.1.2 backport] Avoid triggering unnecessary resync when working with default collection (#6531)

CB robot April 8, 2024 at 9:31 PM

Build sync_gateway-3.2.0-348 contains sync_gateway commit b605a61 with commit message:
[3.1.2 backport] Avoid triggering unnecessary resync when working with default collection (#6531)

CB robot April 8, 2024 at 8:52 PM

Build sync_gateway-3.2.0-346 contains sync_gateway commit b605a61 with commit message:
[3.1.2 backport] Avoid triggering unnecessary resync when working with default collection (#6531)

CB robot April 8, 2024 at 8:21 PM

Build sync_gateway-3.2.0-344 contains sync_gateway commit b605a61 with commit message:
[3.1.2 backport] Avoid triggering unnecessary resync when working with default collection (#6531)

CB robot April 8, 2024 at 7:41 PM

Build sync_gateway-3.2.0-342 contains sync_gateway commit b605a61 with commit message:
[3.1.2 backport] Avoid triggering unnecessary resync when working with default collection (#6531)

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 September 15, 2023 at 3:14 PM
Updated August 31, 2024 at 11:00 AM
Resolved October 13, 2023 at 10:17 PM
Instabug