Michelle Ark

> However, we've had external eyes on it. It's well gated, well tested, and confirmed backwards compatible. LGTM 🚀 echoing this as well ✅

codecov check summaries are stale, here's what you actually see clicking into 'details':

Corresponding schemas PR: https://github.com/dbt-labs/schemas.getdbt.com/pull/60

Hey @keraion, thank you for taking the time to diagnose and open this issue. dbt does [not officially support parallel execution](https://docs.getdbt.com/reference/programmatic-invocations#parallel-execution-not-supported), and it would be quite a large undertaking to...

Added a tech debt ticket re: protoc versions; https://github.com/dbt-labs/dbt-core/issues/10658

Could you please create/link a corresponding [issue in docs.getdbt.com](https://github.com/dbt-labs/docs.getdbt.com/issues?q=is%3Aissue+is%3Aopen) so the docs team can work on documenting the new behaviour once this is merged?

Since singular tests aren't explicitly linked to models in schema.yml files already, we would need to introduce a new top-level 'tests' resource in order to parse descriptions: ``` # top-level...

@liorash-targetboard - where was this yaml block specified within your dbt project? I tried to add it to the dbt_project.yml as well as as a property of a model yml...

Fixed via https://github.com/dbt-labs/dbt-core/pull/12168 Confirmed by repro as described in https://github.com/dbt-labs/dbt-core/issues/10353#issuecomment-2237798749

@barak107 @graciegoheen - Is it possible the issue here is simply that the `state:` prefix is missing from the selectors? Ie, the command should be `dbt ls -s "state:modified+,+state:modified" --defer...