8000 Ensure recorder data integrity and MySQL lock error handling by frenck · Pull Request #37228 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Ensure recorder data integrity and MySQL 8000 lock error handling #37228

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 29, 2020
Merged

Ensure recorder data integrity and MySQL lock error handling #37228

merged 1 commit into from
Jun 29, 2020

Conversation

frenck
Copy link
Member
@frenck frenck commented Jun 29, 2020

Proposed change

This PR makes to changes to the purge of the recorder.

Additionally, a PR for the official Home Assistant MariaDB add-on will be made to reduce the occurrences of the MySQL locking issue.

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

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

@frenck frenck added this to the 0.112.0 milestone Jun 29, 2020
@frenck frenck mentioned this pull request Jun 29, 2020
Merged
@balloob balloob merged commit 79f1310 into dev Jun 29, 2020
@balloob balloob deleted the frenck-2020-0659 branch June 29, 2020 23:23
balloob pushed a commit that referenced this pull request Jun 30, 2020
@frenck @balloob
Ensure recorder data integrity and MySQL lock error handling (#37228)
dbdd4f0
hahn-th pushed a commit to hahn-th/core that referenced this pull request May 2, 2025
@tronikos
Tag Google Drive integration as platinum in docs (home-assistant#37228)
3502adf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@balloob balloob balloob approved these changes

Assignees
No one assigned
Labels
bugfix cherry-picked cla-signed core has-tests integration: recorder
Projects
None yet
Milestone
0.112.0
Development

Successfully merging this pull request may close these issues.

Recorder purge in batches not working on MariaDB
3 participants
@frenck @balloob @homeassistant
0