Closed jamiegau closed 2 years ago
Thanks for the report @jamiegau, after reviewing the issue I think the code for date comparison was just simply wrong. We were just replacing the timezone of 'now' with the one from the DCP IssueDate but without any conversion (using datetime.replace(tzinfo=...)
instead of datetime.astimezone()
).
This should be solved in #207
This is a small bug but.. Created a DCP, tested against cliarmeta stright away. Transferred to a Ubuntu box.
Set the Linux box the the right time zone as I am in.. (It was UTC default) Error goes away when running the command.
This issue will only occur under the right circumstances within 24 hours of creation of the DCP.