David Sutherland

> And for me, it shuts down prematurely after the 2015 point, but I haven't seen it stall. (Mind you, premature shut down is even worse!) Yes, sorry, fixed description

> Hmm, I can't replicate `tests/f/cylc-show/06-past-present-future.t` failure locally I can unfortunately

> It seems to be marking a succeeded task as failed: https://github.com/cylc/cylc-flow/actions/runs/9301382754/job/25601035801?pr=6115#step:17:3293 > > Reporting on the task status from the wrong flow? I think a delta is being overwritten...

Ah, I think I know what's happening.. ``` [scheduler] allow implicit tasks = True [[events]] inactivity timeout = PT1M abort on inactivity timeout = True [scheduling] [[graph]] R1 = """...

> Why is the test passing for me locally though? (on [e11df86](https://github.com/cylc/cylc-flow/commit/e11df86befcb5c7a192e7dc03c8b5e8fd5c4ebde)) Not sure why, but tests are passing now, and it passed locally

> (@dwsutherland, one unresolved review comment above) Replied.. hopefully this convinces you @MetRonnie

I thought #7075 may have fixed this, so I checked.. However, it appears to be already working correctly on `8.6.x`: @hjoliver - Can probably close this (likely fixed with one...

I think the whole data-store window creation (...etc) may have changed since `8.3.6`

I'm gonna throw in a different take: Users should be able to tell which tasks are active/n=0 and which are inactive/window/n>0, at a glance.. I'm not sure what the solution...

Well, I'm not sure it is an entirely separate issue; it means users can clearly see what tasks matter WRT being stuck/halted runahead or otherwise. And it doesn't make a...