Mark Grondona

> And is the idea of "jobtap" like you are tapping a job on the shoulder? tap tap, are you my dependency? 😆 Yeah, like you're "tapping" in to the...

flux operator - keeping your jobs on hold since 1967

That would be a neat little demo

Well, why not just do that on your submit line? ```console $ flux run --dependency=after:$(flux jobs -ac1 --name=job-a -no {id}) -vvv hostname jobid: fD1XCrosV 0.000s: job.submit {"userid":6885,"urgency":16,"flags":0,"version":1} 0.013s: job.dependency-add {"description":"after-start=fCC1iVf35"}...

> Oof, after: meaning after-start is a bit of a trip-hazard... Yeah, I agree. This syntax was borrowed directly from Slurm for ease-of-transition, so it was darned if you, darned...

> @vsoch mentioned in slack that part of her reason is so that it can be expressed declaratively in a file, say as part of jobspec. Oh, that makes sense....

Yeah, it would be nice to have a different scheme with simpler interface. BTW, there's also #5872. I've been pondering in the back of my mind how to expand the...

I think it was something like this: every Nth job they're ensemble is potentially converged so they want to release a dependent job after any N jobs to combine the...

This is actually going to be quite important on systems where most or all jobs run at the system instance level are batch or alloc jobs. This is because most...

> under the assumption of multiple "exec implementations", but that didn't appear to come to fruition, Well, there are already 2 implementations: a mock execution or testexec implementation, that doesn't...