William Hobbs

Happy to add a note about that. Although to be fair work authorization (and in this case citizenship) is a pretty common requirement for most jobs in the US.

I've run into this on our Flux system instance of RZAlastor. This is something I could see some of our Flux/ATS users wanting to use for their testing workflows. As...

This is what I've been using to run Flux on Lassen with `jsrun`: ``` #!/bin/bash #BSUB -q pdebug #BSUB -W 120 #BSUB -nnodes 10 #BSUB -J fluxsesh module use /usr/tce/modulefiles/Core...

@jameshcorbett and I are discussing which subfolders should be included in the RTD documentation and plan to bring this up at coffee hour today. Currently, I plan to use the...

As a note to anyone trying this: flux-framework/flux-docs#51 describes in more detail what is needed here.

I've tested and I believe setting `FLUX_CORE_PREFIX` and not using `./configure --prefix` will get us to the place we want to be: ``` FLUX_CORE_PREFIX=/g/g0/hobbs17/flux-core/install-tioga ./configure ... make -j4 ... make...

By the way, setting `FLUX_CORE_PREFIX` is not necessary if you're inside a flux session. Cmake is able to pick up the prefix of the first `flux` in `PATH`.

I was just setting `FLUX_CORE_PREFIX` above as a workaround to having to start a flux session to build flux-sched.

Note that some (but not all) of the `flux.job.wait` functions are documented (with working function calls) under the [Asynchronous event loop monitoring and submission documentation.](https://flux-framework.readthedocs.io/projects/flux-core/en/latest/python/job_submission.html?highlight=flux.job.result_async#flux.job.result_async)

This might be a dumb idea, but what if we just renamed `wait` to something else, i.e. `flux.job.sync.wait`? This wouldn't break any functionality if the `wait` call was still loaded...