Tags: couchbase/sync_gateway
Tags
[3.2.2 Backport] CBG-4495: do not put documents into rev cache for an… … on demand import (#7346) * [3.2.2 Backport] CBG-4495: do not put documents into rev cache for an on demand import (#7328) * CBG-4494 do not put documents into rev cache when they are being loaded * have all on demand imports skip rev cache * skip test which requires import * remove redundant argument * Remove single duplicate test always (#7332) * CBG-4499: fix leaking goroutines (#7335) * CBG-4499: fix leaking goroutines * updates to address review --------- Co-authored-by: Tor Colvin <[email protected]> Co-authored-by: Gregory Newman-Smith <[email protected]>
CBG-4221 [3.1.11 backport] Don't increment high sequence cached for u… …nused sequences on pendingLogs (#7106) CBG-4221 [3.1.11 backport] Don't increment high sequence cached for unused sequences on pendingLogs If unused sequences ranges are pushed to pendingLogs, they shouldn't increment the channel cache's highSequenceCached until they are processed.
[3.1.10 backport] CBG-4107 CBG-4173 : remove database even if removeC… …orruptConfigIfExists fails (#7060) * CBG-4088: If we error in removeCorruptConfigIfExists we don't unload/remove database (#7014) * CBG-4087: remove configs from invalid tracking that are not found in config poll (#7020) * CBG-4087: remove configs from invalid tracking that are not found in config poll * update test --------- Co-authored-by: Gregory Newman-Smith <[email protected]>
[3.1.6 backport] CBG-3876 suppress warning for non json objects (#6795) * [CBG-3876] suppress warning for non json objects backport of CBG-3835 catch error in case there is a valid json but not a JSON object (#6756) * Remove logging for invalid JSON in sync attribute log in the case where there is _sync xattr but the body has become non json * Update log messages * Update db/import_listener.go Co-authored-by: Adam Fraser <[email protected]> --------- Co-authored-by: Adam Fraser <[email protected]> * Change test to work without multi-xattr write APIs --------- Co-authored-by: Adam Fraser <[email protected]>
[3.1.5] Restore 3.1 handling for admin_channels, admin_roles (#6770) Omitting default collection admin_channels, admin_roles on a PUT /db/_user should not remove those channels - callers must explicitly specify an empty array. Handling for named collections is unchanged - if scopes/collection is specified in collection_access, contents are treated as a replace. Added tests for interaction with JWT channel updates.
PreviousNext