Skip to content

fix: make sure all_rates doesn't have a unit of measure #83

fix: make sure all_rates doesn't have a unit of measure

fix: make sure all_rates doesn't have a unit of measure #83

Triggered via pull request November 4, 2023 17:09
@firstof9firstof9
synchronize #77
fix-76
Status Failure
Total duration 1m 25s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

pull.yml

on: pull_request
Validate
1m 17s
Validate
Check style formatting
7s
Check style formatting
Matrix: Run tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Run tests (3.11)
Process completed with exit code 127.
Validate
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
Validate
Process completed with exit code 1.
Run tests (3.11)
Unexpected input(s) 'fetch-depth', valid inputs are ['python-version', 'python-version-file', 'cache', 'architecture', 'check-latest', 'token', 'cache-dependency-path', 'update-environment', 'allow-prereleases']
Run tests (3.11)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
Validate
[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.