hey I have seen this topic already raised in the channel, but I am not sure why this happens now. We have a linter running in CI, so far so good. This checks which models should be linted by comparing current PR docs with latest docs on S3. During the last PR, we ran

dbt run --select elementary

as we upgraded version, now the elementary models appear both in the

manifest

and

catalog

, throwing of course an error when running the linter. I could probably try to disable the linter from crawling through those models, but why is this happening only right now when I upgraded and is there a solution to fix this? thanks!

ok - downloading lastest artifacts
ok - identifying changed models
ok - the following models have changed:
models/edr/alerts/alerts_anomaly_detection.sql
models/edr/alerts/alerts_dbt_models.sql
models/edr/alerts/alerts_dbt_source_freshness.sql
models/edr/alerts/alerts_dbt_tests.sql
models/edr/alerts/alerts_schema_changes.sql
models/edr/data_monitoring/data_monitoring/data_monitoring_metrics.sql
models/edr/dbt_artifacts/dbt_artifacts_hashes.sql
models/edr/dbt_artifacts/dbt_columns.sql
models/edr/dbt_artifacts/dbt_exposures.sql
models/edr/dbt_artifacts/dbt_invocations.sql
models/edr/dbt_artifacts/dbt_metrics.sql
models/edr/dbt_artifacts/dbt_models.sql
models/edr/dbt_artifacts/dbt_run_results.sql
models/edr/dbt_artifacts/dbt_seeds.sql
models/edr/dbt_artifacts/dbt_snapshots.sql
models/edr/run_results/dbt_source_freshness_results.sql
models/edr/dbt_artifacts/dbt_sources.sql
models/edr/dbt_artifacts/dbt_tests.sql
models/edr/run_results/elementary_test_results.sql
models/edr/run_results/job_run_results.sql
models/edr/data_monitoring/anomaly_detection/metrics_anomaly_score.sql
models/edr/run_results/model_run_results.sql
models/edr/data_monitoring/schema_changes/schema_columns_snapshot.sql
models/edr/run_results/test_result_rows.sql
ok - linting modified models:

User Error: Specified path does not exist. Check it/they exist(s): models/edr/alerts/alerts_anomaly_detection.sql.
cleanup