ktranslate does not output the correct logTimeStamp on OS with non-UTC timezone settings

[qryuu]

What is the problem the customer is trying to solve?

When ktranslate is run on an OS with a non-UTC setting, ktranslate's own logTimeStamp is shifted by the time difference from UTC.

Why is it important for users that we fix that problem?

This is a problem that all users who use ktranslate on OSes that are not set to UTC will face. If the logTimeStamp is shifted, it will be difficult to correlate with other logs, and it will be a major obstacle to troubleshooting.

What is the objective they are pursuing?

The user wants ktranslate to output the correct logTimeStamp even on OSes running in timezones other than UTC.

Use cases and user stories:

A user in a non-UTC time zone, such as JST, runs ktranslate. The user wants to check the logs of ktranslate, but the logTimeStamp is shifted from the actual time, making it difficult to analyze the log.

Is there a known workaround?

The user can set the OS's time zone to UTC, but this may affect other applications running on the OS.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[qryuu]

Would you mind looking into this issue?

[steventine]

@qryuu I had this problem too. I'm using New Relic and I made this change, which fixed it for me - #845

I'm hopeful we can get a change like this (even if it's behind a new config flag to be safe) into ktranslate

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[steventine]

This issue was fixed in the #844 PR by including the time zone in the logTimeStamp. This PR has been merged, so I would expect it to be resolved once a new ktranslate release is created that includes that PR.