Ronnie Dutta
Ronnie Dutta
That's OK, but the docs could do with that detail 
- Broadcasting `execution retry delays` does not cause a change when running in simulation mode - Also, in the Edit Runtime form, `submission retry delays` shows as `1` for some...
> > * Broadcasting `execution retry delays` does not cause a change when running in simulation mode > > I cannot replicate this on the command line. Given the context...
Genuine test failure presumably: `tests/f/modes/05-sim-trigger.t`
What is the problem with how it is currently?
How would you propose adding it to the schema?
Yeah that was my thought
> Note if we don't do this, we will need to be able to reliably strip the message severity in the UI. Currently messages are compared to configured task outputs...
I've narrowed this down to `pipe_poller` (by commenting out the first branch here and seeing the warnings disappear): https://github.com/cylc/cylc-flow/blob/8b2feaea91ac9fa1da80d87274781bb5a25ad30b/cylc/flow/install_plugins/log_vc_info.py#L257-L260 https://github.com/cylc/cylc-flow/blob/8b2feaea91ac9fa1da80d87274781bb5a25ad30b/cylc/flow/pipe_poller.py#L29-L30
> Is `proc.communicate` closing `proc.out` and `proc.err`? Yes looks like it. When it reaches the end of the file it closes it - https://github.com/python/cpython/blob/ecd9946c9d1df7cd1aa15d08d72bbcc0899d272d/Lib/subprocess.py#L1750-L1754