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
Since the switch to the new proto library, datetimes are ugly-rendered in text-formatted logging, and they take up more space than they should:
Timing info for seed.test.my_seed (execute): seconds: 1680366677
nanos: 785534000
=> seconds: 1680366680
nanos: 375668000
Command `dbt clone` succeeded at seconds: 1680366681
nanos: 79572000
after 7.66 seconds
From looking at the JSON-formatted logs, this also shows up in the message field. Let's pretty-stringify these datetime values wherever they're being f-string formatted into message.
The text was updated successfully, but these errors were encountered:
jtcohen6
changed the title
[CT-2347] Petite laideur in v1.5 logging: datetimes
[CT-2347] Petites laideurs in v1.5 logging: datetimes, "unable to parse dict"
Apr 4, 2023
jtcohen6
changed the title
[CT-2347] Petites laideurs in v1.5 logging: datetimes, "unable to parse dict"
[CT-2347] Petite laideur in v1.5 logging: datetimes
Apr 5, 2023
Since the switch to the new proto library, datetimes are ugly-rendered in text-formatted logging, and they take up more space than they should:
From looking at the JSON-formatted logs, this also shows up in the
message
field. Let's pretty-stringify these datetime values wherever they're being f-string formatted intomessage
.The text was updated successfully, but these errors were encountered: