Skip to content

correct order of init of parent and subclasses in manufacturerspecifi… #26

correct order of init of parent and subclasses in manufacturerspecifi…

correct order of init of parent and subclasses in manufacturerspecifi… #26

Triggered via push October 1, 2023 21:12
Status Failure
Total duration 11m 14s
Artifacts

ci.yaml

on: push
Collect information & changes data
16s
Collect information & changes data
Matrix: Prepare dependencies
Prepare pre-commit base
18s
Prepare pre-commit base
Check hassfest
50s
Check hassfest
Check all requirements
30s
Check all requirements
Check mypy
44s
Check mypy
Check ruff
25s
Check ruff
Check other linters
1m 33s
Check other linters
Check black
21s
Check black
Matrix: pytest
Matrix: pytest-mariadb
Matrix: pytest-postgres
Upload test coverage to Codecov
0s
Upload test coverage to Codecov
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Check mypy: homeassistant/components/zha/core/cluster_handlers/manufacturerspecific.py#L407
Incompatible types in assignment (expression has type tuple[AttrReportConfig, AttrReportConfig, ... <14 more items>], variable has type tuple[AttrReportConfig, AttrReportConfig, ... <9 more items>]) [assignment]
Check mypy
Process completed with exit code 1.
Check pylint
Process completed with exit code 4.
Check pylint: homeassistant/components/zha/core/cluster_handlers/manufacturerspecific.py#L403
W7432: Return type should be None in __init__ (hass-return-type)
Check pylint: homeassistant/components/zha/core/cluster_handlers/manufacturerspecific.py#L450
W7432: Return type should be None in __init__ (hass-return-type)
Check pylint: homeassistant/components/zha/core/cluster_handlers/manufacturerspecific.py#L470
W7432: Return type should be None in __init__ (hass-return-type)