Dashboard fixes: staleness, toner, layout
This commit is contained in:
@@ -65,10 +65,14 @@ def stalechains(days=None, limit=50):
|
||||
|
||||
rows = []
|
||||
for revision in latestperchain().values():
|
||||
# Rows written before lastseenat existed fall back to the timestamps
|
||||
# that do exist, so an old install reports something sane on day one
|
||||
# rather than every chain at once.
|
||||
seen = revision.lastseenat or revision.collectedat or revision.createdat
|
||||
# NULL means never confirmed since the column existed, and it is NOT
|
||||
# substituted with collectedat. That substitution is what the first
|
||||
# version did, and on a real fleet it reported every machine whose
|
||||
# config had simply been stable for months as a stopped backup - the
|
||||
# whole board lit up and said the site was broken when it was fine.
|
||||
# A chain becomes measurable the first time its PC posts; until then
|
||||
# this card says nothing about it, which is the truth.
|
||||
seen = revision.lastseenat
|
||||
if seen is None or seen >= cutoff:
|
||||
continue
|
||||
asset = db.session.get(Asset, revision.assetid)
|
||||
|
||||
Reference in New Issue
Block a user