Skip to content

Fix race condition for component loaded before listening#13887

Merged
balloob merged 2 commits intodevfrom
fix-config-comp-race
Apr 14, 2018
Merged

Fix race condition for component loaded before listening#13887
balloob merged 2 commits intodevfrom
fix-config-comp-race

Conversation

@balloob
Copy link
Copy Markdown
Member

@balloob balloob commented Apr 14, 2018

Description:

We would miss out on any component_loaded events after we checked which components got loaded and before we register a listener (because we yield from)

Related issue (if applicable): fixes #13740

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

@balloob balloob merged commit bba997e into dev Apr 14, 2018
pvizeli added a commit that referenced this pull request Apr 15, 2018
pvizeli added a commit that referenced this pull request Apr 15, 2018
* Revert "Add unique_id for BMW ConnectedDrive (#13888)"

This reverts commit 9014e26.

* Revert "Added snips service descriptions (#13883)"

This reverts commit 1c4da0c.

* Revert "Fix race condition for component loaded before listening (#13887)"

This reverts commit bba997e.

* Revert "Missing property decorator added (#13889)"

This reverts commit bf98b79.

* Revert "Update frontend to 20180414.0"

This reverts commit 1617fbe.

* Revert "Further untangle data entry flow (#13855)"

This reverts commit 4d44c0f.

* Revert "add support for Kodi discovery (#13790)"

This reverts commit 5a5dad6.

* Revert "Update yweather.py (#13851)"

This reverts commit c3388d6.
balloob added a commit that referenced this pull request Apr 18, 2018
* Fix race condition for component loaded before listening

* async/await syntax
@balloob balloob mentioned this pull request Apr 18, 2018
@balloob balloob removed this from the 0.67.1 milestone Apr 18, 2018
@callagga
Copy link
Copy Markdown

@balloob - any ideas when this fix would be available? I'm on v0.67.0. I'm happy to learn how to look up which fixes will be against what release in github but I'm not sure how to do this.

@riemers
Copy link
Copy Markdown

riemers commented Apr 18, 2018

@callagga if you look at the reference #13975 you can see that was merged into master with a version bump. That is the item 2 ticks above your post.

@kellerza kellerza deleted the fix-config-comp-race branch April 18, 2018 07:05
@callagga
Copy link
Copy Markdown

thanks @riemers - does this imply HA 0.67.1 is ready to upgrade via the "pip3 install --upgrade homeassistant" approach, noting it was only 5 hours ago?

@riemers
Copy link
Copy Markdown

riemers commented Apr 18, 2018

My rule of thumb is, if it is not on the home page it is not yet out. Sometimes it maybe but i don't look at it that straight. Also these conversations are more suited on Discord then in the merged issue :)

@callagga
Copy link
Copy Markdown

ok thanks

@home-assistant home-assistant locked and limited conversation to collaborators Apr 18, 2018
@balloob balloob added this to the 0.67.1 milestone Apr 27, 2018
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.

Z-Wave parameters drop down menu is not working 0.67.0b0

6 participants