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'm a little confused at how this is happening - it looks like the 0.16.0-b3 pre-release (on PyPi) includes a macros/materializations/merge.sql file which is not present in the source code used to generate this release.
There are two things to check out here:
Do we need to do something special to ensure that a merge.sql file from a previous release (eg. 0.15.2) does not persist after a user upgrades to 0.16.0?
Does our build script for dbt need to be updated to wipe out the dist/ dir (or similar) to ensure that assets from different releases aren't persisted across releases errantly?
For reference, this file is includes in site-packages/dbt using this pypi release, but no such merge.sql file exists in dev/barbara-gittings. The code from #2140is present in the release (which also deletes the merge.sql file), so this isn't a question of the 0.16.0-b3 pre-release not mapping to the latest commit on dev/barbara-gittings.
Steps To Reproduce
python3 -m venv env
source env/bin/activate
pip install dbt==0.16.0-b3
# This file should not exist!
cat env/lib/python3.7/site-packages/dbt/include/bigquery/macros/materializations/merge.sql
The text was updated successfully, but these errors were encountered:
This looks like a release issue of some sort - the file exists in a pristine install of dbt==0.16.0b3 as well, but it's not in the repository. I'll investigate the package-building aspect more thoroughly in the next couple days, but there's code in the package build script that explicitly calls shutil.rmtree on the dist folder before we start building:
I believe I've found a fix for this (though it's super hard to tell, given the nature of the issue) and pushed a corresponding change to my package build script PR in #2119 - when we rm -rf the dist/ folders, also remove the build/ folders.
Describe the bug
See a description of the bug here: https://discourse.getdbt.com/t/pre-release-v0-16-0-barbara-gittings/922/2?u=drew
I'm a little confused at how this is happening - it looks like the 0.16.0-b3 pre-release (on PyPi) includes a
macros/materializations/merge.sql
file which is not present in the source code used to generate this release.There are two things to check out here:
merge.sql
file from a previous release (eg. 0.15.2) does not persist after a user upgrades to 0.16.0?dist/
dir (or similar) to ensure that assets from different releases aren't persisted across releases errantly?For reference, this file is includes in
site-packages/dbt
using this pypi release, but no suchmerge.sql
file exists indev/barbara-gittings
. The code from #2140 is present in the release (which also deletes themerge.sql
file), so this isn't a question of the0.16.0-b3
pre-release not mapping to the latest commit ondev/barbara-gittings
.Steps To Reproduce
The text was updated successfully, but these errors were encountered: