Skip to:

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

CancellationToken and CancellationTokenSource management needed

Description

As a complement to https://couchbasecloud.atlassian.net/browse/NCBC-2290#icft=NCBC-2290, we need some sort of process/pattern/whatever for managing CancellationTokenSource and CancellationTokens themselves passed into the SDK.

Currently the RetryOrchestrator does some work here in that if it encounters a CancellationToken.none, it will create a CancellationTokenSource with the timeout. This CTS, needs to be disposed, but currently its not. Additionally, throughout the source you will find child CTS's, these also need to managed.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Jeffry Morris September 11, 2020 at 7:01 PM

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

Details

Assignee

Reporter

Story Points

Components

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created January 21, 2020 at 10:18 PM
Updated September 11, 2020 at 7:01 PM
Resolved September 11, 2020 at 7:01 PM
Instabug