Bug: Incorrect human-readable dates for unix timestamps
Opened this issue · 0 comments
johngribbin commented
There seems to be an issue with the conversion of Unix timestamps to human-readable dates in the should_monitor_onchain_funds
object returned by the clboss-status
call. The now
and disable_until
values do not seem to correspond correctly with their now_human
and disable_until_human
counterparts.
Example response:
{
"status": "ignore",
"now": 1721640000,
"now_human": "UTC 2024-07-22 08:29:41.632",
"disable_until": 1721690000,
"disable_until_human": "UTC 2024-07-23 00:21:44.860",
"comment": "`clboss-notice-onchain` to resume managing onchain funds."
}
Issues:
- The
now
value of1721640000
converts to UTC time ofMon Jul 22 2024 09:20:00
. - The
disable_until
value of1721690000
converts to UTC time ofMon Jul 22 2024 23:13:20
.