Describe the bug
When running edr report command, it fails with a validation error indicating that the severity field in TestResultDBRowSchema contains the value "none", which is not allowed.
To Reproduce
Steps to reproduce the behavior:
- run
dbt build with dbt Fusio
- Run
edr report
- See validation error
Expected behavior
The elementary report should generate successfully without validation errors.
Screenshots
N/A
Environment (please complete the following information):
- Elementary CLI (edr) version: 0.20.1
- Elementary dbt package version: 0.20.1 (found in
packages.yml file)
- dbt version you're using: dbt-fusion 2.0.0-preview.92
- Data warehouse: BigQuery
- Infrastructure details: macOS darwin 24.6.0, development environment, local deployment
Additional context
Full error message:
ERROR — Could not generate the report - Error: 1 validation error for TestResultDBRowSchema
severity
none is not an allowed value (type=type_error.none.not_allowed)
The error occurs in the TestResultDBRowSchema validation when processing test results data. This appears to be a schema validation issue where the severity field is returning "none" instead of an expected enumerated value.
Would you be willing to contribute a fix for this issue?
I would be willing to help test a fix but would need guidance on contributing code changes.
Describe the bug
When running
edr reportcommand, it fails with a validation error indicating that theseverityfield inTestResultDBRowSchemacontains the value "none", which is not allowed.To Reproduce
Steps to reproduce the behavior:
dbt buildwith dbt Fusioedr reportExpected behavior
The elementary report should generate successfully without validation errors.
Screenshots
N/A
Environment (please complete the following information):
packages.ymlfile)Additional context
Full error message:
The error occurs in the
TestResultDBRowSchemavalidation when processing test results data. This appears to be a schema validation issue where the severity field is returning "none" instead of an expected enumerated value.Would you be willing to contribute a fix for this issue?
I would be willing to help test a fix but would need guidance on contributing code changes.