In the DART log file, times are always 4 hours ahead of my local time (Eastern). If the logger could use the clock of the computer on which it is running, that would be convenient. I can understand using Universal Time for timestamps that end up in the APTrust repository, but this is just a log file on the local computer.
Interestingly, in DART Runner’s JSON output file, the times are correct. For example, if the DART log has this, which is UTC:
2026/06/03 19:33:48 [INFO] Finished S3 upload of …
the DART Runner JSON output file has this, which is local time:
"completed": "2026-06-03T15:33:48.599108-04:00"
Note the -04:00 on the end.
Looks like the time is also 4 hours ahead in the bag-info.txt file, for example:
Bagging-Date: 2026-06-03T19:33:48Z
That makes sense, since that file ends up in the repo.
In the DART log file, times are always 4 hours ahead of my local time (Eastern). If the logger could use the clock of the computer on which it is running, that would be convenient. I can understand using Universal Time for timestamps that end up in the APTrust repository, but this is just a log file on the local computer.
Interestingly, in DART Runner’s JSON output file, the times are correct. For example, if the DART log has this, which is UTC:
2026/06/03 19:33:48 [INFO] Finished S3 upload of …
the DART Runner JSON output file has this, which is local time:
"completed": "2026-06-03T15:33:48.599108-04:00"
Note the -04:00 on the end.
Looks like the time is also 4 hours ahead in the bag-info.txt file, for example:
Bagging-Date: 2026-06-03T19:33:48Z
That makes sense, since that file ends up in the repo.