[Regression] duckdb panics test or build with `not yet implemented: DuckDBAdapter::freshness`
- Dominant language
- Rust
- Stars
- 13.8k
- Forks
- 2.6k
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 56
Description
### Is this a regression in a recent version of dbt-core?
- [x] I believe this is a regression in dbt-core functionality
- [x] I have searched the existing issues, and I could not find an existing issue for this regression
### Which versions does this regression span?
Within dbt v2.x (worked in an older v2.x, broke in a newer v2.x)
### Current Behavior
Running `dbtf test` or `dbtf build` even on jaffle_shop at duckdb gives t
```
panic: panicked at fs/sa/crates/dbt-adapter/src/metadata/duckdb/mod.rs:225:9:
not yet implemented: DuckDBAdapter::freshness
```
### Workaround
For others running into this I found that if I do `dbt build --no-manage-state` it works.
### Expected/Previous Behavior
Before it actually tested
### Steps To Reproduce
Run `dbtf test` on [jaffle_shop_duckdb](https://github.com/dbt-labs/jaffle_shop_duckdb)
### Relevant log output
```shell
```
### Environment
```markdown
- OS: Linux Mint
- Python: irrelevant
- dbt (working version): dbt-fusion 2.0.0-preview.179
- dbt (regression version): dbt-fusion 2.0.0-preview.180
```
### Which database adapter are you using with dbt?
other (mention it in "Additional Context")
### Additional Context
DuckDB
Contributor guide
Assessment
This issue has not been assessed yet.