Overload of warning logs when using dbt-core 1.8.* about dagster HOT 6 OPEN

Plus one. I had to revert because I was getting OOMs from the number of logs being emitted

from dagster.

Still getting some warnings when using dbt==1.7.*, but not as many:

/Users/niallwoodward/dev/select/web/backend/.venv/lib/python3.11/site-packages/dagster_dbt/dbt_project.py:193: ExperimentalWarning: Class `DagsterDbtManifestPreparer` is experimental. It may break in future versions, even between dot releases. To mute warnings for experimental functionality, invoke warnings.filterwarnings("ignore", category=dagster.ExperimentalWarning) or use one of the other methods described at https://docs.python.org/3/library/warnings.html#describing-warning-filters.
  manifest_preparer: DbtManifestPreparer = DagsterDbtManifestPreparer()

Has Dagster changed its logging significantly in dagster==1.7.*? I'm noticing a lot more (not desirable) logging across the board.

from dagster.

Could #22267 (which went out in 1.7.10) have somehow caused this? The intention there was to change the formatting of warnings, not the frequency, but I’m wondering if it has unintended side effects.

I’m not sure how to square that with the problem occurring when you just upgrade dbt-core and don’t upgrade dagster though.

from dagster.

linking the similar report in #22460 for context

from dagster.

Thanks for your quick response on this @gibsondan.

from dagster.

Could #22267 (which went out in 1.7.10) have somehow caused this?

Don't know if this is question is targeted at me or Niall but from my point of view: doubt it since it started happening from Dagster 1.7.7

from dagster.