Ronnie Dutta
Ronnie Dutta
I think this is pretty much good to go 🎉 Just got a conflict to resolve + my suggestion above
I've got a deconfliction here: https://github.com/wxtim/cylc/pull/70 I've checked it carefully, should be correct.
I have a branch (see https://github.com/cylc/cylc-flow/commit/f8cf9bfb76ccc282c02b16c6f50896f0b5b5652e) that attempts to fix this, however the fix results in traceback causing functional tests to fail which I don't understand. E.g. `tests/f/spawn-on-demand/06-stop-flow-2.t`
Lint failure fixed in #6188
Fixed by https://github.com/vuetifyjs/vuetify/pull/21145
I can still reproduce on 8.3.2 and 8.3.x as of dc9f01b72ecb022e12d024aaf7c0c0a32a5c6625, from copying the example above.
Option 2 is no worse than the current behaviour so could at least be implemented as a quick address of the issue. Edit: however, with the option 2 patch, I've...
It aborts, however the workflow status gets stuck as reloading
I don't think it matters what users use on the command line? According to [the docs](https://cylc.github.io/cylc-doc/nightly/html/reference/config/workflow.html#flow.cylc[scheduler]cycle%20point%20format) > The time zone you specify here will be used only for writing/dumping cycle...
Argh, clearly I needed more coffee yesterday ☕