You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dbt server logging output shows "QueueFeederThread" as the source for all log output. This isn't correct - the logs are actually being emitted by threads named things like master or Thread-3. Let's update the log handling code to print the correct thread name in the structured logs.
This change will help us better understand:
parallelized execution in dbt
per-thread connections and query pooling
Expected behavior
The thread_name in structured log output in the dbt server responses (like from poll) should render out as master or Thread-N or similar, not QueueFeederThread.
Screenshots and log output
The output of dbt --version:
0.15.0-b3
The operating system you're using:
macOS
The output of python --version:
Py3.7.5
The text was updated successfully, but these errors were encountered:
Describe the bug
The dbt server logging output shows "QueueFeederThread" as the source for all log output. This isn't correct - the logs are actually being emitted by threads named things like
master
orThread-3
. Let's update the log handling code to print the correct thread name in the structured logs.This change will help us better understand:
Expected behavior
The
thread_name
in structured log output in the dbt server responses (like frompoll
) should render out asmaster
orThread-N
or similar, notQueueFeederThread
.Screenshots and log output
The output of
dbt --version
:The operating system you're using:
macOS
The output of
python --version
:Py3.7.5
The text was updated successfully, but these errors were encountered: