Hilary James Oliver comments

Results 328 comments of


                                            Hilary James Oliver

Task hold/release needs to be flow-specific

Yes, correct (I'll update the title).

Task hold/release needs to be flow-specific

The merged task will be held, I think. Similarly, if you hold flow 3 (say) a merged task belonging to flows (2,3) should be held.

Other ways to terminate a (re)flow?

See #3745 comments on `hold` as well.

scheduler: restarting completed workflows

> Make it easier to restart a completed workflow. Is the existing timeout PR not sufficient in your opinion? #5231 > Make it more obvious why a completed workflow shuts...

cylc commands from a directory that does not exist should not cause failures (generally)

Huh, good spotting. That `getcwd()` call was introduced very recently: we now move to the workflow directory during file parsing, to make workflow files easily available to the template processor....

cylc commands from a directory that does not exist should not cause failures (generally)

We could put @ColemanTom 's fix in, but I've discovered it is not sufficient at least in some environments: in a Python venv on my laptop VM under WSL, and...

cylc commands from a directory that does not exist should not cause failures (generally)

Well, let's merge your fix at least. (I've posted it as a PR).

cylc commands from a directory that does not exist should not cause failures (generally)

It fails for all commands, for me. But Tom's post suggests it (with his code tweak) doesn't fail in his environment?

job script `mkdir` tweak

Thanks for responding @matthewrmshin ! Good point on networked filesystems, makes sense. We might have to investigate a bit...

Add, subtract, or override semantics for repeated config items

@trwhitcomb & @matthewrmshin - agreed, we'll allow both. I like += for append (list or string) and = for override (since == is typically a comparison operator).