Fixed4
A file whose storage term has already ended no longer appears in the expiry warning as “ends today” with an Extend button.
The warning counted every file whose term ended before the warning window, which included files whose term was already over, and it showed their remaining time as zero. Those files now have their own notice under the warning, listed by name, that says the storage network no longer holds them and that they cannot be recovered or extended. The warning itself counts only files that still have time left.
“Extend the term” is no longer offered for a file whose term has ended — in the row menu, the detail panel or the extend screen.
Walrus does not extend a term that has already ended, so the button could only fail after asking you to pay. The extend screen now says in which epoch the term ended instead of offering durations, and the detail panel shows the end date as a past date.
A file whose term was never recorded is no longer listed as expiring today.
A credit upload made while the storage network's clock could not be read keeps its term as unknown. The server counted that as an epoch of zero, which put the file at the top of the warning. Unknown terms are left out of the warning; the file's row still says its term is not recorded.
When the storage network cannot be reached and the clock is estimated from the last reading, a file is called ended only when that is certain.
The estimate rounds the current epoch up on purpose, so that warnings come early rather than late. The same rounding also made a file with up to one whole epoch left read as ended. Warnings still come early; “ended” now needs the estimate to be past the term by a full epoch.