Skip to content
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

Merged
merged 934 commits into from
Feb 11, 2022
Merged

Reformat core [CT-104 CT-105] #4697

merged 934 commits into from
Feb 11, 2022

Conversation

iknox-fa
Copy link
Contributor

@iknox-fa iknox-fa commented Feb 8, 2022

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

  • I have signed the CLA
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change

gshank and others added 30 commits February 8, 2022 09:55
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
actually fix static parser tracking

automatic commit by git-black, original commits:
  1c61bb1
  21a7b71
automatic commit by git-black, original commits:
  b501f43
fix jinja sampling for static parser

automatic commit by git-black, original commits:
  21a7b71
actually fix static parser tracking

automatic commit by git-black, original commits:
  1c61bb1
actually fix static parser tracking

automatic commit by git-black, original commits:
  1c61bb1
  6925ceb
* add tracking event for full reparse reason

* update changelog

automatic commit by git-black, original commits:
  2679792
  c69f28e
- 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
automatic commit by git-black, original commits:
  052a306
  98c015b
* 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
automatic commit by git-black, original commits:
  5e8ab9c
  af8622e
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
automatic commit by git-black, original commits:
  56ae206
  8520ff3
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:
  3d28b67
automatic commit by git-black, original commits:
  10cd06f
  b030b4e
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
@iknox-fa iknox-fa requested a review from a team February 8, 2022 16:18
@iknox-fa iknox-fa requested review from a team and leahwicz as code owners February 8, 2022 16:18
@iknox-fa
Copy link
Contributor Author

iknox-fa commented Feb 8, 2022

@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.

@cla-bot
Copy link

cla-bot bot commented Feb 8, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link

cla-bot bot commented Feb 8, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@leahwicz
Copy link
Contributor

@cla-bot check

@cla-bot
Copy link

cla-bot bot commented Feb 10, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link

cla-bot bot commented Feb 10, 2022

The cla-bot has been summoned, and re-checked this pull request!

@leahwicz
Copy link
Contributor

@cla-bot check

@cla-bot
Copy link

cla-bot bot commented Feb 10, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link

cla-bot bot commented Feb 10, 2022

The cla-bot has been summoned, and re-checked this pull request!

@leahwicz
Copy link
Contributor

@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

@cla-bot
Copy link

cla-bot bot commented Feb 10, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link

cla-bot bot commented Feb 11, 2022

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.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CT-105] use black code formatter