Skip to content

Error closing client when LaunchDarkly relay proxy in daemon mode#119

Closed
benpagedelphix wants to merge 1 commit into
launchdarkly:masterfrom
benpagedelphix:master
Closed

Error closing client when LaunchDarkly relay proxy in daemon mode#119
benpagedelphix wants to merge 1 commit into
launchdarkly:masterfrom
benpagedelphix:master

Conversation

@benpagedelphix

Copy link
Copy Markdown

Do not attempt to read the _update_processor attribute when closing the client if the client is running in ldd mode because initialization of the _update_processor attribute does not occur if use_ldd is set to true in the config.

@eli-darkly

Copy link
Copy Markdown
Contributor

This definitely needs to be fixed, but I think we're going to go in a slightly different direction: making sure that all of the object's attributes are always set at initialization time, so we don't need to go "check this other attribute first because if it has a certain value, then the attribute I want won't exist." In other words, the close method should not need to know the details of the use_ldd behavior.

@eli-darkly eli-darkly closed this Apr 9, 2019
@benpagedelphix

Copy link
Copy Markdown
Author

That makes sense to me, thanks for fixing this ASAP

LaunchDarklyCI pushed a commit that referenced this pull request Nov 21, 2019
add Python 3.8 CI build, and make syntax warnings fatal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants