diff options
author | Vito Caputo <vcaputo@pengaru.com> | 2024-11-30 14:29:34 -0800 |
---|---|---|
committer | Vito Caputo <vcaputo@pengaru.com> | 2024-11-30 14:29:34 -0800 |
commit | 3ec67cdd5d4ec82ed10b6df20dc22db9242a322e (patch) | |
tree | 32a13f953d86312a491a7d19d55f2e1412473807 /m4 | |
parent | 0e04a75e828f8a336d361303e68775d2603945e4 (diff) |
charts: assert that descendents of stale are stale
This is really how things are implemented today, which may
actually be incorrect in some edge case scenarios... but let's
assert it holds true currently to aid debugging some spurious
asserts in vcr_shift_below_row_up_one() about row vs.
hierarchy_end.
The potential issue I see with this assumption as-is is it's
entirely possible to have descendants survive a parent's demise,
grandchildren don't have to exit when a parent does. But it
might be OK to treat it that way, as they'll be rediscovered as
children of PID 1, and there's no strict need to preserve
continuity of their associated charts state across that
transition. It's rare enough that I don't think it's worth
worrying about, but maybe this is what's happening with the
asserts during startup specifically; when things are daemonizing
/ double forking etc.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions