You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems any duration >= 60min and <= 1h59m may be displayed as "an hour" in copr web UI.
Which can be quite misleading/confusing sometimes.
eg One of my builds just went from 50min to 90min, so copr now says it took "an hour".
Another example, a build started just over 2 hours ago was displayed as:
Submitted:
2025-02-03 09:12 UTC (2 hours ago)
Started:
2025-02-03 09:13 UTC (an hour ago)
which doesn't really make sense.
A simple suggestion would be at least show minutes up to 2 hours, though I would prefer always to see hours and minutes 2h 15m.
Failing that, at the very least there should be rounding to the nearest hour.
The text was updated successfully, but these errors were encountered:
this is the intended behaviour of humanize.naturaldelta which we use to display the timestamp delta to users. I personally don't care that much about this one, but I'd like to avoid displaying seconds in the "human" format if delta > 60 so the time ago in the UI is not bloated
we can do something like this instead...
>>> humanize.precisedelta(5000, minimum_unit="minutes", format="%.0f")
'1 hour and 23 minutes'
It seems any duration >= 60min and <= 1h59m may be displayed as "an hour" in copr web UI.
Which can be quite misleading/confusing sometimes.
eg One of my builds just went from 50min to 90min, so copr now says it took "an hour".
Another example, a build started just over 2 hours ago was displayed as:
which doesn't really make sense.
A simple suggestion would be at least show minutes up to 2 hours, though I would prefer always to see hours and minutes
2h 15m
.Failing that, at the very least there should be rounding to the nearest hour.
The text was updated successfully, but these errors were encountered: