Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix race on check MQTT subscriptions #88117

Merged
merged 3 commits into from
Feb 14, 2023
Merged

Conversation

jbouwh
Copy link
Contributor

@jbouwh jbouwh commented Feb 14, 2023

Proposed change

Check MQTT subscriptions under paho client lock to avoid a race.

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)
  • Deprecation (breaking change to happen in the future)
  • 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.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @emontnemery, mind taking a look at this pull request as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.

@jbouwh jbouwh mentioned this pull request Feb 14, 2023
19 tasks
@balloob balloob merged commit aaf8196 into home-assistant:dev Feb 14, 2023
@corporategoth
Copy link

This is missing a key thing that is in #88072

Specifically, when you subscribe to a topic, MQTT will send you the latest status for that topic.
For the initial subscription, this will work (and the entity will get notified of that).

My change also adds a last_message for each topic (at least each simple topic) and will send the last message that was received on that topic to new subscribers.

@corporategoth
Copy link

Though, I guess, we will now have to change my MR to accommodate this MR since it's merged.

@corporategoth
Copy link

corporategoth commented Feb 14, 2023

Nevermind, I mis-read. The other only handles unsubscribes, not subscribes. My MR is still relevant.

@jbouwh jbouwh deleted the mqtt-lock branch February 14, 2023 22:04
@github-actions github-actions bot locked and limited conversation to collaborators Feb 15, 2023
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.

None yet

5 participants