-
Notifications
You must be signed in to change notification settings - Fork 59
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
Test ddtrace dependency range #733
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-redshift contributing guide. |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.4.latest 1.4.latest
# Navigate to the new working tree
cd .worktrees/backport-1.4.latest
# Create a new branch
git switch --create backport-733-to-1.4.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.4.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.4.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.2.latest 1.2.latest
# Navigate to the new working tree
cd .worktrees/backport-1.2.latest
# Create a new branch
git switch --create backport-733-to-1.2.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.2.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.2.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-733-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3.latest 1.3.latest
# Navigate to the new working tree
cd .worktrees/backport-1.3.latest
# Create a new branch
git switch --create backport-733-to-1.3.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.3.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.5.latest 1.5.latest
# Navigate to the new working tree
cd .worktrees/backport-1.5.latest
# Create a new branch
git switch --create backport-733-to-1.5.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.5.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.5.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-733-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 13ada0a84b466e53f76c8a1bd1633cde7f5c72a0
# Push it to GitHub
git push --set-upstream origin backport-733-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest Then, create a pull request where the |
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a)
* Test ddtrace dependency range (#733) * set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog * pin pytest to version 7 --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a) --------- Co-authored-by: Matthew McKnight <[email protected]>
* Test ddtrace dependency range (#733) * set bounds for ddtrace due to tests failing * hard pin ddtrace, create changelog * pin pytest to version 7 --------- Co-authored-by: Mike Alfare <[email protected]> (cherry picked from commit 13ada0a) --------- Co-authored-by: Matthew McKnight <[email protected]>
resolves #734
docs dbt-labs/docs.getdbt.com/#
Problem
A change in ddtrace or a upper dependency around helpconfig seems to be causing failures in adapters. setting bounds to be in the 2.3.x range seems to get us passing.
Solution
Checklist