Change log file entries to include human readable timestamp

[julie777]

Is your feature request related to a problem? Please describe.

I just submitted another issue and had to infer the related part of the log file because the timestamp is not human readable.
(I'm sure you don't want the entire log file in each bug report. :-) )

Describe the solution you'd like

Use a human readable format for timestamp on log entries

Describe alternatives you've considered
deciphering the timestamp and creating a small program that I can run just to show the timestamp in readable form so that I can extract the useful part of the log.

[stevencohn]

In any system with workflow or long-running processes with changing state, timestamps are critical. But OneMore commands are all basically atomic operations and should complete in milliseconds if not one or two seconds. Beyond that, there's not much use.

[julie777]

I am not sure I was being clear. Assuming my log file has been running for months and I use OneMore commands frequently every day a quick glance doesn't show me what I just did that I want to include in an issue. I made a guess earlier today and just grabbed what looked like close together timestamps, even though I didn't know what the actual timestamp meant.

I might also be confused because it wasn't about running commands, as I was trying to report an update problem.

[stevencohn]

It's not a timestamp. The "num1:num2]" prefix of each line is actually the process ID of the dllhost process and the managed thread ID.

[julie777]

It's not a timestamp. The "num1:num2]" prefix of each line is actually the process ID of the dllhost process and the managed thread ID.

Now I remember you telling me that before.