-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-2347] [Bug] Petite laideur in v1.5 logging: datetimes #7255
Comments
github-actions
bot
changed the title
Petitess laideurs in v1.5 logging
[CT-2347] Petitess laideurs in v1.5 logging
Apr 1, 2023
jtcohen6
changed the title
[CT-2347] Petitess laideurs in v1.5 logging
[CT-2347] Petite laideur in v1.5 logging: timestamps
Apr 1, 2023
jtcohen6
changed the title
[CT-2347] Petite laideur in v1.5 logging: timestamps
[CT-2347] Petite laideur in v1.5 logging: datetimes
Apr 1, 2023
5 tasks
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
Just ran into this one as well, during
Update: Already fixed by #7262! |
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
jtcohen6
changed the title
[CT-2347] Petite laideur in v1.5 logging: datetimes
[CT-2347] [Bug] Petite laideur in v1.5 logging: datetimes
Apr 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: