Skip to content

Small cleanups for recorder#68551

Merged
bdraco merged 3 commits intohome-assistant:devfrom
bdraco:recorder_cleanups
Mar 23, 2022
Merged

Small cleanups for recorder#68551
bdraco merged 3 commits intohome-assistant:devfrom
bdraco:recorder_cleanups

Conversation

@bdraco
Copy link
Copy Markdown
Member

@bdraco bdraco commented Mar 23, 2022

Proposed change

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

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.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

To help with the load of incoming pull requests:

- Fix comment

- Fix incorrect typing

- Add some more missing typing
@probot-home-assistant
Copy link
Copy Markdown

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@bdraco bdraco marked this pull request as ready for review March 23, 2022 08:47
@bdraco bdraco requested a review from a team as a code owner March 23, 2022 08:47
@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented Mar 23, 2022

Looks like I can't just cleanup one without trigger an error on the others :(

@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented Mar 23, 2022

That didn't cascade as much as I thought it would. Didn't have to pull in anything close to the whole branch to make mypy in the CI happy 👍

"""Start processing events to save."""
shutdown_task = object()
hass_started = concurrent.futures.Future()
hass_started: concurrent.futures.Future = concurrent.futures.Future()
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this future threadsafe? It seems we're abusing the concurrent.futures.Future api. Some of it is only meant for use in executor implementations:
https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.Future

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That uses a threading.Condition under the hood for access so it should be thread-safe. While it is not broken AFAICT, it would probably be good to refactor the implementation at some point as I think there are better options available now.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well I was going to suggest using run_callback_threadsafe but that uses concurrent.futures.Future as well

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like asyncio.run_coroutine_threadsafe does as well

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either one is still probably a better option here since at least it means if something does change with it there will be less places to fix

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's late late here so something to think about for tomorrow.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to do more testing, but #68593

@bdraco bdraco merged commit 8c10963 into home-assistant:dev Mar 23, 2022
@bdraco bdraco deleted the recorder_cleanups branch March 23, 2022 22:12
@github-actions github-actions bot locked and limited conversation to collaborators Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants