Mark Grondona

> Maybe it makes sense to rewire the intree support to be relative? That may work for some paths, but for autotools it is often the case that `sysconfdir` is...

It might help us to understand why Julia needs to run in this way. I still feel a bit lost. If you are making a Julia bindings package, my assumption...

Ah, is it because of: https://julialang.github.io/Pkg.jl/v1/environments/ Are there Julia Slurm bindings? Do they also install a copy of Slurm and run it from the side-installed path? How will this work...

Ah, I missed that one. You can try removing that command in `rc1` when you are running the Julia-only version of flux-core. It pushes some cleanup commands into the broker...

> I don't really know what that looks like. (Will job-list need to answer queries about jobs that ran 5 days ago?) I think this will be pretty common. In...

> returns all data job-list data into a json object and returns it. This would be useful also with some of the Python API and some frontend commands which currently...

The key statement from the initial proposal is this: > if we can one day open up access to the job-archive database for more advanced queries. i.e. we're hoping the...

This work still needs to be done, but some of the requirements have changed. * Now that the strategy to support broker restart includes `libsdprocess`, moving execution of the job...

There are several problems I've observed here: * The broker gets SIGTERM more than once. This is probably because the top-level broker sends SIGTERM to the shell at job termination...

Another possible issue: When a job is terminated, SIGTERM is sent to all ranks. For a multi-rank Flux instance, this means all brokers get SIGTERM (possibly multiple times, see above),...