Source: Don't disconnect DCP client if it was never connected
Description
Environment
None
Gerrit Reviews
None
Release Notes Description
None
relates
Activity
Show:

David Nault
changed the StatusMay 31, 2023 at 4:03 AMOpen
Closed

David Nault
updated the ResolutionMay 31, 2023 at 4:03 AMNone
Fixed

David Nault
changed the StatusMay 31, 2023 at 4:03 AMNew
Open

David Nault
updated the Linked IssuesMay 30, 2023 at 6:33 PMNone
This issue blocks CBSE-14292

David Nault
updated the Linked IssuesMay 30, 2023 at 6:33 PMNone
This issue relates to JDCP-237

David Nault
created the IssueMay 30, 2023 at 6:32 PMFixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
David Nault
David NaultReporter
David Nault
David NaultStory Points
1
Sprint
None
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Sentry
Linked Issues
Sentry
Linked Issues
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created May 30, 2023 at 6:32 PM
Updated May 31, 2023 at 4:03 AM
Resolved May 31, 2023 at 4:03 AM
Instabug
As a workaround for JDCP-237: Client.disconnect() is not idempotentNew, and the fact that the DCP client's `connect()` method calls `disconnect()` internally if the connection failed, we need to keep track of whether the connection was successful, so we don't end up calling `disconnect()` if the client has already been disconnected due to a failed connection attempt.