Jeremy Yeo

Following this thread - some `global_project` macros are not dispatched today[^1] which could be confusing to some end users when they try and follow our docs on "Overriding global macros"...

TL;DR: All macros should be dispatch for the sake of consistency - I think this makes it "better UX". @dataders - My 2c is that it's irrelevant what the use-case...

Hey team, looks like the following scenario is related (`dbt-core 1.0.1`, `dbt-snowflake 1.0.0`). A barebones project with 3 models: ```sql -- my_model.sql select 1 as user -- my_model_2.sql select *...

@emmyoop - there are packages that contain many other packages - the [`dbt_ad_reporting`](https://github.com/fivetran/dbt_ad_reporting/blob/main/packages.yml) package contains all these dependencies: ```yml packages: - package: fivetran/pinterest version: [">=0.5.0", "=0.4.0", "=0.4.0", "=0.6.0", "=0.1.0", "=0.4.0",...

@csoule-shaker you're right about the separation of issues here - moved that to #4868 so that we can have that discussion separately.

Hey team, I've got a relevant one for you... if you have a malformed `dbt_project.yml`: ```yml name: "my_dbt_project" version: "1.0.0" config-version: 2 profile: "snowflake" model-paths: ["models"] macro-paths: ["macros"] snapshot-paths: ["snapshots"]...

At the top of my head, dbt can read environment variables so maybe something like this temporarily:  _Edit: Looks like this was mentioned in that other issue :P_

I've got a repro of this one (ensure partial parsing hasn't been accidentally disabled). ```yaml # dbt_project.yml name: "my_dbt_project" version: "1.0.0" config-version: 2 profile: "snowflake" models: my_dbt_project: +materialized: table +database:...

Reopening on behalf of customer :) On Redshift - the error message is: ``` 23:13:43 Runtime Error in model foo (models/foo.sql) Tried to run invalid SQL: /* {"app": "dbt", "dbt_version":...

> @jeremyyeo do you think this is a bug or a feature request? @dbeatty10 - I can't say for sure - we added this functionality / enhancement here to a...