-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Reformat core [CT-104 CT-105] #4697
Conversation
empty automatic commit by git-black, original commits: d7ea364
for processing automatic commit by git-black, original commits: a83f00c
* Fix docs generation for cross-db sources in REDSHIFT RA3 node (#3408) * Fix docs generating for cross-db sources * Code reorganization * Code adjustments according to flake8 * Error message adjusted to be more precise * CHANGELOG update * add static analysis info to parsing data * update changelog * don't use `meta`! need better separation between dbt internal objects and external facing data. hacked an internal field on the manifest to save off this parsing info for the time being * fix partial parsing case Co-authored-by: kostek-pl <67253952+kostek-pl@users.noreply.github.com> automatic commit by git-black, original commits: 4d24656 a76ec42
automatic commit by git-black, original commits: b501f43
fix jinja sampling for static parser automatic commit by git-black, original commits: 21a7b71
automatic commit by git-black, original commits: 3944705
actually fix static parser tracking automatic commit by git-black, original commits: 1c61bb1
- removed 3 new log call sites and replaced with structured logs - removed 2 unused struc logs automatic commit by git-black, original commits: 5cc8626
* add tracking event for full reparse reason * update changelog automatic commit by git-black, original commits: 2679792
report exception information. automatic commit by git-black, original commits: af16c74
automatic commit by git-black, original commits: aadf3c7
* Fix docs generation for cross-db sources in REDSHIFT RA3 node (#3408) * Fix docs generating for cross-db sources * Code reorganization * Code adjustments according to flake8 * Error message adjusted to be more precise * CHANGELOG update * add static analysis info to parsing data * update changelog * don't use `meta`! need better separation between dbt internal objects and external facing data. hacked an internal field on the manifest to save off this parsing info for the time being * fix partial parsing case Co-authored-by: kostek-pl <67253952+kostek-pl@users.noreply.github.com> automatic commit by git-black, original commits: 2cc0579 4d24656
The alias name check is now tied to the behavior of adapter.Relation.create_from(...) Plugins that override the `include` of their relations will use whatever they render to for the check the actual exception-raising code gets the name that was compared instead of generating its own Finally, I added a reasonable fallback behavior since this method was exposed to the context automatic commit by git-black, original commits: 20c5c4c 5e8ab9c af8622e
automatic commit by git-black, original commits: e935439
Handle empty vars dict Check sources for unused configs - add a test Warn when dbt finds "vars" in "models", "seeds", etc blocks - add a test Clean up enabled/disabled code to share between sources and nodes - only log downstream tests at debug level when a source is disabled - include the offending project name in the v1 deprecation message - Fix tests that care about error messages, add new ones automatic commit by git-black, original commits: b8febdd c18b72b
automatic commit by git-black, original commits: 10aded7
…egration test for checking case-insensitive extensions automatic commit by git-black, original commits: f9343c4
automatic commit by git-black, original commits: 1d91890
* Fix docs generation for cross-db sources in REDSHIFT RA3 node (#3408) * Fix docs generating for cross-db sources * Code reorganization * Code adjustments according to flake8 * Error message adjusted to be more precise * CHANGELOG update * add static analysis info to parsing data * update changelog * don't use `meta`! need better separation between dbt internal objects and external facing data. hacked an internal field on the manifest to save off this parsing info for the time being * fix partial parsing case Co-authored-by: kostek-pl <67253952+kostek-pl@users.noreply.github.com> automatic commit by git-black, original commits: 4d24656 7563b99 aadf3c7
automatic commit by git-black, original commits: 007cb45
@leahwicz do you know if we can disable the CLA bot for this? Each commit is made as it's original committer, many of which pre-date the cla-bot. |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
@cla-bot check |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
The cla-bot has been summoned, and re-checked this pull request! |
@cla-bot check |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
The cla-bot has been summoned, and re-checked this pull request! |
@iknox-fa when you are ready to merge let me know and we can coordinate on the CLA check. We might have to remove it as required and then close/reopen the PR and then merge |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Joel Labes, Jacob Beck.
|
resolves #3195 and #3196 (CT-104, CT-105)
Description
The results of running the pre-commit code in this PR vs main.
Note that the commits were made using git-black and therefor maintain the correct history.
Checklist
CHANGELOG.md
and added information about my change