Mark Grondona

Results 625 comments of Mark Grondona

Another approach might be to develop a format specifier or other indicator that sets the width of a field to the minimum width that would not result in the field...

Ok, now that #6284 has been merged, we can safely change the behavior of `flux resource list` to combine all empty sets into one (by adding all queues to one...

Looking back, it is a bit confusing that non-empty sets that overlap are combined (e.g. all,debug) and not the empty set. Though admittedly an empty set is a special case...

I haven't looked into how difficult this would be, but maybe `flux resource status` could be augmented to show nodes that are currently in housekeeping? That might be more straightforward...

It is trivial to add a new `housekeeping` state to `flux resource status`, e.g.: ``` $ src/cmd/flux resource status STATE UP NNODES NODELIST avail ✔ 101 corona[171,173-186,188-194,196-207,213-214,219,221-230,232-250,252-253,255-259,261-269,272-275,277-278,280,282-285,287-290,292-294,296] exclude ✔ 4...

Another idea is to just make a `flux systemctl` wrapper that sets `DBUS_SESSION_BUS_ADDRESS` appropriately for the `flux` user so that it could be used locally without needing to run under...

I started looking into this and part of the problem seems to be that this is a bit of a nightmare input for `quicksort()`, especially because `hostrange_cmp()` returns 0 when...

If I understand correctly, you are proposing an [evolving](https://flux-framework.readthedocs.io/projects/flux-core/en/latest/guide/glossary.html#term-evolving) job that would request a base amount of memory per task at job submission, but could grow at runtime if memory...

Unfortunately job dependencies are not going to be easy to support with the current job update method. The RFC 21 [jobspec-update event](https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_21.html#jobspec-update-event) uses a period-delimited key, e.g. `attributes.system.duration`, but this...

Yeah, this is pretty promising. We could have a new `jobspec-patch` event that supports this format possibly. For updating a dependency, that json patch object could first delete the existing...