Jim Garlick

If the jobspec could be provided on the command line as well then I think the [RFC 36](https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_36.html) triple quote support would let that just work. Edit: responding to @trws's...

That idea may have been a little half-baked. I was equating jobspec with the resource request in my head, not taking into account the tasks and attributes sections. The currently...

Great points @ryanday36 and I agree we should not be too hasty here and should revisit those use cases. It is sort of appealing to have a queue be directly...

I think we've viewed the spec files as something that belongs to our TOSS build farm and not to flux proper, because spec files are typically not very portable (and...

> When a node is lost, the job shell is lost too so the exit timer is started. I had to go look at code to find out why this...

As I reread my statement above, maybe it is correct the way it is. tasks did "exit" after all. So disabling the doom plugin is probably the correct approach.

Pondering :-) I guess two concerns, not show stoppers at all: - inconsistent behavior if exit-timer is armed and a non-critical node dies (exit timer is NOT started) vs exit-timer...

> This is an interesting idea. Maybe this would handle the general case of jobs that modify their critical-ranks set rather than only batch/alloc jobs? Oh I see we have...

That sounds good. It would need to get a starting value though.

Wow that is really strange. It's almost as if the job manager's running job count is just wrong. Looking through that code, it's hard to see how it could be,...