Skip to:

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

[3.0.4 Backport] Revocation of non-existent role causes replication panic

Description

Originally reported on GitHub: https://github.com/couchbase/sync_gateway/issues/5610

Attached unit test to reproduce this - seemingly, if a user's access to a document is revoked and they lose access to a role that doesn't exist (i.e. it's removed from their admin_roles without ever being created through PUT /db/_role/foo), replication can panic. Stack trace on release/3.0.3:

Activity

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

Details

Assignee

Reporter

Labels

Story Points

Components

Sprint

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created July 7, 2022 at 4:16 PM
Updated August 31, 2024 at 10:59 AM
Resolved July 26, 2022 at 3:58 PM
Instabug