Grace Goheen

> The same "run mode" could apply to compile + docs generate. I believe this will also be relevant for our unit testing work, since unit tests do not need...

More notes from refinement: - we should do something deterministic here - this feels similar to the ordering of the unit tests in the build command (having some flexibility around...

Just ran into the same issue This works fine: ``` {% set old_etl_relation=adapter.get_relation( database="DEVELOPMENT", schema="DBT_GGOHEEN", identifier="stg_worlds" ) -%} {{ old_etl_relation }} ``` But when I try to call one of...

I'm not sure how you would create an integration test for this, because building a model works fine - it's just the preview that fails.

Same issue as reported here: - https://github.com/dbt-labs/dbt-audit-helper/issues/81 - https://github.com/dbt-labs/dbt-audit-helper/issues/56 - https://github.com/dbt-labs/dbt-audit-helper/issues/14

Hey - thanks so much for opening! Since this is currently broken, we're going to remove that callout from our docs site. But I will sync with our engineers to...

Just adding the reproducible example Harlan shared. I have a model I want to unit test: ``` # models/recursive_cte.sql WITH RECURSIVE asdf AS ( SELECT * FROM {{ ref('recursive_cte_given') }}...

We're going to call this out as a known limitation for the 1.8 release. But this is something we will revisit for 1.9 as an outcome of https://github.com/dbt-labs/dbt-core/issues/8499

I was able to reproduce this bug. ``` col_a|col_b|col_c 1|2|3 4|5|6 ``` When I configure my seed delimiter in a properties yml file: ``` seeds: - name: test_delimiter config: delimiter:...

We're only able to reproduce this issue in bigquery, all other adapters seem to be working fine. I'm going to transfer this over to `dbt-bigquery`