Log program uptime in ms with us precision instead of datetime#53
Conversation
The timestamps now show milliseconds with microsecond precision (e.g. 123.456ms) since the program started. The full start datetime is logged on the first line. Co-authored-by: HalFrgrd <4559349+HalFrgrd@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
- Replace chrono with humantime. - Format log timestamps as zero-padded seconds with microsecond precision (XXX.XXXXXXs). - Log full RFC3339 start time on the first log line. Co-authored-by: HalFrgrd <4559349+HalFrgrd@users.noreply.github.com>
1 participant
Modified
src/bin/evp.rsto replace theTimeOnlylog timer with anUptimetimer. TheUptimetimer calculates and formats the time elapsed since the program startInstantwith microsecond precision. Updatedinit_tracingto accept the startInstantand log the full start datetime (including year, month, day, and UTC) on the initial "initialising tracing" log line.PR created automatically by Jules for task 12685996509406020759 started by @HalFrgrd