Mark Grondona

> I know slurm can kill a job if one of the processes has a nonzero exit code. I haven't seen slurm kill a job because one of the processes...

Thank you for commenting!

We did fashion the behavior after our site default, so I'm not sure if disallowing a change of default behavior would be acceptable. All job shell options can currently be...

My opinion is that it would be going too far to disallow site changes to job shell behavior. Even if we disable writing to `shell.options` from the initrc, shell plugins...

I think the `...` refers to reason, but yeah probably a side effect of using argparse. There may be some way to fix it but it is probably pretty low...

Good catch, are the functions used as `flux.job.wait.wait` in the docs because the documentation is autogenerated?

The [zmq_ctx_term](http://api.zeromq.org/4-2:zmq-ctx-term) documentation states: > After interrupting all blocking calls, zmq_ctx_term() shall block until the following conditions are satisfied: > - All sockets open within context have been closed with...

If I "comment out" the last test in `t1000-dws-dependencies.t`, then the hang does not occur. In fact, the following test alone reproduces the issue by itself: ```sh #!/bin/sh test_description='Test dws-jobtap...

The cause here seems to be a leaked future in the dws-jobtap plugin. When the service fails to respond, the callback wherein the future is destroyed is not invoked, so...

> My concern is that having a background service that's constantly polling all available jobs, or polling at specified intervals, is too heavy for something that only a few users...