Open gunnava opened 3 weeks ago
Thanks for reporting this @gunnava!
How large is the seed file? If it is larger than 1 MiB, then it won't show up during state comparison.
I wasn't able to reproduce this will a very simple seed file less than 1 MiB. See below for details.
I tried the files and commands below, and things worked as expected.
Start with these files:
dbt_project.yml
flags:
warn_error_options:
error:
- NoNodesForSelectionCriteria
- NothingToDo
seeds/my_seed.csv
id
1
Run this command:
dbt build --target-path artifacts
Then change the seed file to this:
seeds/my_seed.csv
id
2
And run this command:
dbt build --select state:modified+ --state artifacts
It all worked as expected for me.
Is this a new bug in dbt-core?
Current Behavior
The "Generate compare changes" step (debug logs for the run step attached) is throwing an error for a PR where only a seed is changed and with the warning config as below:
Expected Behavior
The expectation is that the Generate compare changes should show the files changed if any and not throw the warning "Nothing to do"
Steps To Reproduce
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
Slack thread: https://dbt-labs.slack.com/archives/C02SRNY2EQ4/p1726685698514849