Updating dbt-duckdb imports to fix CI pipeline #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@pgoslatara : I am afraid it will not be an easy fix. We need more time to investigate this |
|
@JCZuurmond No worries, thanks for taking a look. I tried and got nowhere 😢! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of #66 it was noticed that
toxwas failing to run. A manual trigger of the CI pipeline here also showed this behaviour. This is likely due to this commit indbt-duckdbwhich was released as part of v1.4.2 last week. Oursetup.pypermits patch version upgrades ofdbt-duckdb.This PR updates the imports for
dbt-duckdbto reflect the changes made in last weeks release.