Skip to content

[CT-2160] [Regression] "Legacy" Logging Broken in 1.4.2rc1 #7028

Closed
@peterallenwebb

Description

@peterallenwebb

Is this a regression in a recent version of dbt-core?

  • I believe this is a regression in dbt-core functionality
    I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior

When running a dbt command from the cli with the DBT_USE_LEGACY_LOGGER env var set, the console logs are written via a standard Python logger, rather than the logbook logger, as they should be to support legacy logging scenarios correctly.

Expected/Previous Behavior

Logging should be directed to the logbook log with this flags set, just as it was in 1.4.1.

Steps To Reproduce

Issue was seen when running dbt build with DBT_USE_LEGACY_LOGGER=True on the jaffle_shop project with 1.4.2rc1 on macOS with Python 3.10, but likely affects all platforms, Python versions, and projects.

Relevant log output

At the console, logs look the same, but integrations relying on logbook are failing.

Environment

- OS: macOS
- Python: 3.10
- dbt (working version): 1.4.1
- dbt (regression version): 1.4.2rc1

Which database adapter are you using with dbt?

postgres

Additional Context

No response

Activity

changed the title [-][Regression] "Legacy" Logging Broken in 1.4.2rc1[/-] [+][CT-2160] [Regression] "Legacy" Logging Broken in 1.4.2rc1[/+] on Feb 22, 2023
jtcohen6

jtcohen6 commented on Feb 28, 2023

@jtcohen6
Contributor

Resolved by #7029

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @peterallenwebb@jtcohen6

        Issue actions

          [CT-2160] [Regression] "Legacy" Logging Broken in 1.4.2rc1 · Issue #7028 · dbt-labs/dbt-core