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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize find bad JSON data #31963

merged 1 commit into from Feb 19, 2020

Optimize find bad JSON data #31963

merged 1 commit into from Feb 19, 2020


Copy link

balloob commented Feb 18, 2020

Breaking change

Proposed change

Make finding bad JSON data a lot faster thanks to @sanyatuning in

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:


  • 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
@balloob balloob requested a review from home-assistant/core as a code owner Feb 18, 2020
@project-bot project-bot bot added this to Needs review in Dev Feb 18, 2020

This comment has been minimized.

Copy link

codecov bot commented Feb 18, 2020

Codecov Report

Merging #31963 into dev will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev   #31963      +/-   ##
+ Coverage   94.68%   94.69%   +0.01%     
  Files         764      766       +2     
  Lines       55384    55543     +159     
+ Hits        52439    52596     +157     
- Misses       2945     2947       +2
Impacted Files Coverage 螖
homeassistant/util/ 85.5% <100%> (-0.21%) 猬囷笍
homeassistant/components/mqtt/ 97.11% <0%> (-0.02%) 猬囷笍
homeassistant/components/automation/ 100% <0%> (酶) 猬嗭笍
homeassistant/components/mqtt/ 100% <0%> (酶) 猬嗭笍
homeassistant/components/mqtt/ 98.47% <0%> (酶)
homeassistant/components/mqtt/ 100% <0%> (酶)
homeassistant/components/mqtt/ 98.05% <0%> (+0.05%) 猬嗭笍

Continue to review full report at Codecov.

Legend - Click here to learn more
螖 = absolute <relative> (impact), 酶 = not affected, ? = missing data
Powered by Codecov. Last update 4ed7a7f...98f0483. Read the comment docs.

@balloob balloob merged commit 9f83096 into dev Feb 19, 2020
11 checks passed
11 checks passed
CI Build #20200218.76 succeeded
CI (FullCheck Mypy) FullCheck Mypy succeeded
CI (FullCheck Pylint) FullCheck Pylint succeeded
CI (Overview CheckFormat) Overview CheckFormat succeeded
CI (Overview Lint) Overview Lint succeeded
CI (Overview Validate) Overview Validate succeeded
CI (Tests PyTest Python37) Tests PyTest Python37 succeeded
cla-bot Everyone involved has signed the CLA
codecov/patch 100% of diff hit (target 94.68%)
codecov/project 94.69% (+0.01%) compared to b5df2ba
docs-missing Documentation ok.
Dev automation moved this from Needs review to Done Feb 19, 2020
@balloob balloob deleted the optimize-find-bad-json-data branch Feb 19, 2020
@lock lock bot locked and limited conversation to collaborators Feb 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can鈥檛 perform that action at this time.