You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
When installing dbt-core into an environment where an older version of click is installed, dbt-core will throw a vague error Error: Invalid value for '--warn-error-options': Cannot load YAML from type <class 'dbt.helper_types.WarnErrorOptions'>. It seems dbt-core is pinning click<9 which allows it to use older versions of click that it seems no longer compatible with. I think dbt-core should be pinning a minimum version requirement of click that plays well with the library.
Expected Behavior
No error.
Steps To Reproduce
Install click==8.0.0
Install the latest dbt-core
Attempt to use the dbt cli w/ a command dbt ls or something
Relevant log output
Error: Invalid value for'--warn-error-options': Cannot load YAML from type<class 'dbt.helper_types.WarnErrorOptions'>
github-actionsbot
changed the title
[Bug] Error: Invalid value for '--warn-error-options'
[CT-3138] [Bug] Error: Invalid value for '--warn-error-options'
Sep 20, 2023
Is this a new bug in dbt-core?
Current Behavior
When installing
dbt-core
into an environment where an older version of click is installed,dbt-core
will throw a vague errorError: Invalid value for '--warn-error-options': Cannot load YAML from type <class 'dbt.helper_types.WarnErrorOptions'>
. It seemsdbt-core
is pinningclick<9
which allows it to use older versions of click that it seems no longer compatible with. I thinkdbt-core
should be pinning a minimum version requirement of click that plays well with the library.Expected Behavior
No error.
Steps To Reproduce
Install
click==8.0.0
Install the latest
dbt-core
Attempt to use the dbt cli w/ a command
dbt ls
or somethingRelevant log output
Environment
Which database adapter are you using with dbt?
snowflake
Additional Context
No response
The text was updated successfully, but these errors were encountered: