dbt-duckdb hangs during dbt compile when used with dbt-fusion engine

[kylejbrk]

% uv run dbt compile
dbt-fusion 2.0.0-preview.196
   Loading profiles.yml

It hangs indefinitely. With --log-level debug it gets stuck at:
Initializing schema store with entry: Frontier(CanonicalFqn { catalog: "openfoodfacts", schema: "main", table: "products" }) and interval: None
No platform credentials found, skipping remote license
License check failed: Feature not licensed: 'lineage'
Setup:

requires-python = ">=3.9"
dependencies = [
    "dbt>=2.0.0rc196",
    "dbt-duckdb>=1.10.0",
]
[tool.uv]
prerelease = "allow"

The project has an external source pointing to a local parquet file via loader: local-parquet.
Works fine with: dbt-core>=1.9.0,<1.10.0 + dbt-duckdb>=1.10.0
Is Fusion support planned for dbt-duckdb, or is there a workaround for this schema store initialization hang?

[jwills]

ah @kylejbrk I don't work on fusion stuff-- @dataders where should stuff like this go?

[kylejbrk]

@jwills FYI dbt-core and dbt fusion are merging. The dbt-duckdb would need to support it if the plan is to support dbt v2.0

https://github.com/dbt-labs/dbt-core#about-dbt-core-v20

[jwills]

ah cool; reminds me of an old google saying: "there are two ways to do X: the way that is deprecated, and they way that doesn't work yet"