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
In #1699, I added a feature where a SIGHUP causes the RPC server to recompile the manifest. Unfortunately, it just keeps shoving the logs to stdout/dbt.log. Instead/additionally (whichever is easier) it should make them available to the 'status' method under a 'logs' key.
Describe alternatives you've considered
We could just keep dumping them to the regular logger
Additional context
N/A
Who will this benefit?
RPC clients
The text was updated successfully, but these errors were encountered:
Describe the feature
In #1699, I added a feature where a SIGHUP causes the RPC server to recompile the manifest. Unfortunately, it just keeps shoving the logs to stdout/dbt.log. Instead/additionally (whichever is easier) it should make them available to the 'status' method under a 'logs' key.
Describe alternatives you've considered
We could just keep dumping them to the regular logger
Additional context
N/A
Who will this benefit?
RPC clients
The text was updated successfully, but these errors were encountered: