Skip to content

Sense should only load default ssl certificates once to avoid I/O in the event loop#35523

Merged
bdraco merged 1 commit into
home-assistant:devfrom
bdraco:sense_io_event_loop_from_load_default_certs
May 12, 2020
Merged

Sense should only load default ssl certificates once to avoid I/O in the event loop#35523
bdraco merged 1 commit into
home-assistant:devfrom
bdraco:sense_io_event_loop_from_load_default_certs

Conversation

@bdraco
Copy link
Copy Markdown
Member

@bdraco bdraco commented May 11, 2020

Proposed change

When the websocket is created SSLContext.load_default_certs is called
each time which opens up the system default ssl certs file and reads it in

Normally this goes unnoticed, however since there are frequent connects
and disconnects of the websocket it was noticeable.

Waiting for scottbonline/sense#35

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

@bdraco bdraco added the waiting-for-upstream We're waiting for a change upstream label May 11, 2020
@probot-home-assistant probot-home-assistant Bot added integration: sense small-pr PRs with less than 30 lines. dependency-bump Pull requests that update a dependency file labels May 11, 2020
@probot-home-assistant
Copy link
Copy Markdown

Hey there @kbickar, mind taking a look at this pull request as its been labeled with a integration (sense) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@kbickar
Copy link
Copy Markdown
Contributor

kbickar commented May 12, 2020

https://github.com/scottbonline/sense/releases/tag/0.7.2 Release is now available

When the websocket is created `SSLContext.load_default_certs` is called
each time which opens up the system default ssl certs file and reads it in

Normally this goes unnoticed, however since there are frequent connects
and disconnects of the websocket it was noticeable.
@bdraco bdraco force-pushed the sense_io_event_loop_from_load_default_certs branch from 9faf6e1 to a157630 Compare May 12, 2020 03:40
@bdraco bdraco removed the waiting-for-upstream We're waiting for a change upstream label May 12, 2020
@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented May 12, 2020

Thanks @ctalkington

@bdraco bdraco merged commit 68179e2 into home-assistant:dev May 12, 2020
@lock lock Bot locked and limited conversation to collaborators May 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed dependency-bump Pull requests that update a dependency file integration: sense small-pr PRs with less than 30 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants