Mark Grondona

Ah, yeah, that makes sense. Probably we were only lucky to get away with it previously.

Well that change overwrites the previous setting on any configuration reload with the defaults. However, probably not a big deal since these are mostly used only for testing at this...

This is a known issue (fixed in 0.62.0): #5885. Unfortunately, it also means the hostnames can actually be incorrect... :grimacing:

Closing as a duplicate of #5885. Please reopen if we're still seeing any issues with 0.62.0.

Oh, these occur in spots that are watching `resource.R` for potential updates of resource expiration. Makes sense in each case to check if the value changed (though these are LOG_DEBUG...

This came up again with the notification service proposed in flux-framework/rfc#414. While job shell options are not that onerous to specify on the command line, e.g. `flux run -o mpibind=ARGS...`,...

Another use case has come up recently: Sysadmins would like to add functionality to the job prolog which is optionally enabled by a jobspec attribute, but use of this functionality...

I did some prototyping on this issue recently (see my [cli-plugins](https://github.com/grondo/flux-core/tree/cli-plugins) branch) This adds a `CLIPlugin` abstract base class from which a plugin should derive ```python class CLIPlugin(ABC): # pragma...

Here's an example of what I was talking about on the call of a validate-only plugin. This one validates the shell `signal` option, which can either be an integer, or...

A prefix option is a good idea. I might try to redo the prototype with that idea and see how it turns out.