Andy
Andy
for sure - it's this: https://github.com/dbt-labs/dbt-core/blob/7239ffe41dfe743d1117adab5cebe75740335e89/core/dbt/include/starter_project/dbt_project.yml The guide on the demo project, just correcting a typo here. So I guess not *really* docs maybe? Sort of an in-between.
> Hey @andy-clapson, thanks for the contribution! Two questions: > > * Are you able to sign the CLA? If not, we won't be able to accept the changes unfortunately...
@jtcohen6 I've done all this, and added the changelog entry as well
pushed commit to address failing test - I don't want to expand the scope of this PR, but that f-string readme used in the init asserts seems like it's repeated...
I am also seeing this issue when importing both charts and dashboards, I'm unclear on the precise cause (not much that is useful from the logs I can see). I...
this might not be the solution you're going for, but the `warnings` module in stdlib is pretty effective for tuning out warnings from 3rd party packages: https://docs.python.org/3/library/warnings.html
Same issue here, with the same exception.
hey thanks so much @patrickfuller ! I'll use this fix for the moment, but we may take some time to send up a PR. I really appreciate the quick response...
In a perfect world this warning would go away, but in case you want to simply tune out the log noise you can add something like this to your custom...
This is something that should be managed at the db level (using different users), which I know you said was something you didn't want to do. Otherwise data source permissions...