Al Chu
TSIA. Maybe the only interesting side note is that until we solve #5367 (which should probably follow this one up) we don't yet have a friendly user interface for this....
Problem: Job-list constraints are not limited in their size. A nefarious user could cause a DoS of the job-list service by sending an extremely large constraint request. Solution: Set a...
Built on top of #5389. Per a random idea I once had in #4792, support a `flux resource watch` command that watches and outputs resource changes as they occur by...
it took me a little bit to figure out ``` usage: flux-resource drain [-h] [-f] [-u] [-i TARGETS] [-o FORMAT] [-n] [-L [WHEN]] [targets] ... positional arguments: targets List of...
As @grondo notes in #5656, "very large" constraints might have the ability to hang (or minimally slow down) the job-list service. We may wish to put a limit on the...
per my list in #5126, something like `flux jobs --query="userid:1234 name:foo states:pending` Possibly related work in #4186
Problem: The current python API functions that call `job-info.lookup` can take multiple keys for lookup. Users may want to get the keys for an updated value (i.e. R w/ eventlog...
in PR #5576, a fix is proposed to handle a unique scenario where `LC_ALL` exists in the primary flux instance for testing (set via `sharness.sh`) but it disappears when `flux...
Something I was just thinking off randomly. We default since to 0 to say "consider all jobs that are inactive historically" when filtering jobs. This isn't a huge deal when...
I noticed in the following test in `libsubprocess`: ``` ok 16 - subprocess state == RUNNING after flux_local_exec ok 17 - flux_subprocess_kill SIGSTOP # state_change_stopped: state = Stopped ok 18...