Hey @owen, just wanted to flag something I noticed moving back to the dbt cli resource from the rpc resource for one of my user repos. There seems to be some logging changes going on w/ DBT at least on version 1.1.0. Everything looks great w/ the default dbt logging when running commands via dagster-dbt on a Mac. However, when I run the same command on Linux (containerized) I get a whole host of extra logging in addition to the correctly formatted messages (screen below). When I enable this flag

DBT_ENABLE_LEGACY_LOGGER=True

, the excess verbose messages disappear. However, the messages coming back aren't parsed correctly because it seems like the message structure has changed to something more nested:

{'timestamp': '2022-05-25T22:32:28.957628Z', 'message': '{"code": "Z015", "data": {}, "invocation_id": "f8f78495-2ab1-4aa5-aa95-6b466097fd67", "level": "info", "log_version": 2, "msg": "Finished cleaning all paths.", "pid": 6183, "thread_name": "MainThread", "ts": "2022-05-25T22:32:28.957440Z", "type": "log_line"}', 'channel': 'dbt', 'level': 11, 'levelname': 'INFO', 'thread_name': 'MainThread', 'process': 6183, 'extra': {'run_state': 'internal'}}

ah I see, thanks for flagging! I'll see if there's a quick fix that we can get in for next week's release (I think you're right that this is probably because of a change in dbt 1.1.0)

Of course, looking forward to it!

My team is encountering a similar issue, what is the status of this? @owen

hi @Steven Litvack-Winkler -- what version are you running of dagster-dbt / dbt-core? this is working as of the most recent version of dagster-dbt, but a bug could have resurfaced

I’m running dagster 0.15.10 and dbt-core 1.2.1.

got it -- I believe this issue got fixed in dagster 1.0 (which corresponds to dagster-dbt 16.0). I think dagster-dbt 16.x should be compatible with dagster 0.15.10 (even if pip complains about it), so if you're not in a position to upgrade your dagster version, you may be able to upgrade just that version

Okay, I’ll try this. Thanks for the help.