Is this your first time opening an issue?

• I have read the expectations for open source contributors

Describe the Feature

Currently the timestamp in event logging is always output in utc. It would be helpful to be able to set the time zone via a configuration or parameter (either local or any other time zone).

Describe alternatives you've considered

I have not found any alternatives. One has to live with utc.

Who will this benefit?

This would make it easier to evaluate the logs and help to avoid confusion. Additionally the evaluation of dbt logs in combination with other logs using lokal or any other timezone would be easier.

Are you interested in contributing this feature?

No response

Anything else?

No response

I've found that dbt is suppressing import-time warnings here: https://github.com/dbt-labs/dbt-core/blob/72c17c446440afe7d4b6501ed364effe8e14c9f2/core/dbt/logger.py#L356

This starts a context manager which is never closed. The unclosed context manager is preventing warnings in my application from being displayed.

FYI, dbt is being imported in my application by sqlfluff, which I'm using to parse SQL queries.

A quick fix could be to use:

debug_warnings = DebugWarnings()
debug_warnings.start()

instead of

DebugWarnings().__enter__()

and then adding

debug_warnings.end()

to the bottom of logger.py.

Although, I'm not sure if this will provide the right behaviour, it does allow my application to issue warnings again.

If my solution is reasonable, I'd be happy to open a PR.

I'm using:

• dbt-core 1.0.6
• dbt-snowflake 1.0.1
• sqlfluff 0.11.2
• sqlfluff-templater-dbt 0.11.0

resolves #

Description

Checklist

• I have read the contributing guide and understand what's expected of me
• 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 opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

The new release of networkx (2.8.1) is causing issues with model selection logic so lowering the version range to not include it.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

You can trick dbt into giving dynamic freshness check behaviour with something like this:

        freshness:
          error_after:
            count: "{{ 48 if run_started_at.strftime('%w') == '1' else 24 }}" #looser expectations on Monday
            period: hour

Community Slack thread.

@jtcohen6 pointed out that

Small word of warning — this won't be re-parsed by partial parsing, and so it's liable to get stale. Shouldn't be an issue in scheduled runs (which don't persist partial-parse state between runs), it might just be cause for surprise if you come back to it locally a few days from now.

https://docs.getdbt.com/reference/parsing#known-limitations

Expected Behavior

Again from jerco:

In the future, we should think about ways to always re-parse (invalidate cache) for any configs/properties/nodes/etc that depend on "volatile" variables like run_started_at or invocation_id

Steps To Reproduce

1. Configure a source freshness check as described above, such that it will fail today and pass every other day of the week
2. Run dbt source freshness, note that the test fails
3. Wait a day (or change the code above to be dependent on the minute of the day or something)
4. Run dbt source freshness again. Note that the test still fails, even though it's a different day of the week.
5. Run dbt source freshness --no-partial-parse. Note that the test now passes, because it's re-parsed the project and re-evaluated run_started_at.

Relevant log output

No response

Environment

- OS: macOS
- Python: 3.8.x
- dbt: 1.0-rc1

What database are you using dbt with?

snowflake

Additional Context

Related: https://github.com/dbt-labs/dbt-core/issues/2330

resolves #5257

This is a pretty simple string substitution PR, changing up all instances of py38 to py in the Makefile, to support running with the user's local default python version instead of always requiring Python 3.8.

Checklist

• I have read the contributing guide and understand what's expected of me
• 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 opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

resolves #5189

Description

Add "grants" attribute to NodeConfig. Fix up all the tests.

This also contains a fix for a partial parsing error that was encountered when writing the test.

Checklist

• I have read the contributing guide and understand what's expected of me
• 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 opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

resolves #5189

Description

Add "grants" attribute to NodeConfig. Fix up all the tests.

This also contains a fix for a partial parsing error that was encountered when writing the test.

Checklist

• I have read the contributing guide and understand what's expected of me
• 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 opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

resolves #5189

Description

Add "grants" attribute to NodeConfig. Fix up all the tests.

This also contains a fix for a partial parsing error that was encountered when writing the test.

Checklist

• I have read the contributing guide and understand what's expected of me
• 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 opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry