Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency conflict in CI for sqlparse using dbt-core 1.8.0b2 and dbt-redshift 1.8.0b2 #883

Closed
5 tasks
dbeatty10 opened this issue Apr 18, 2024 · 1 comment
Closed
5 tasks
Labels
bug Something isn't working

Comments

@dbeatty10
Copy link
Contributor

dbeatty10 commented Apr 18, 2024

Describe the bug

See https://app.circleci.com/pipelines/github/dbt-labs/dbt-utils/1658/workflows/0cf13398-5bd6-4cdd-9cbe-2d9205bab958/jobs/5449

image

Steps to reproduce

Run CI.

Expected results

CI passes.

Actual results

CI fails.

Screenshots and log output

INFO: pip is looking at multiple versions of dbt-redshift to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r dev-requirements.txt (line 3) and -r dev-requirements.txt (line 6) because these package versions have conflicting dependencies.

The conflict is caused by:
    dbt-core 1.8.0b2 depends on sqlparse<0.6.0 and >=0.5.0
    dbt-redshift 1.8.0b2 depends on sqlparse<0.5 and >=0.2.3

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Exited with code exit status 1

System information

The contents of your packages.yml file:

Which database are you using dbt with?

  • postgres
  • redshift
  • bigquery
  • snowflake
  • other (specify: ____________)

The output of dbt --version:

<output goes here>

Additional context

Are you interested in contributing the fix?

@dbeatty10 dbeatty10 added bug Something isn't working triage and removed triage labels Apr 18, 2024
@dbeatty10
Copy link
Contributor Author

This seemingly self-resolved sometime during the last couple weeks:

Now

image

Before

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant