Dong H. Ahn
Dong H. Ahn
Sounds good to me!
Sounds reasonable to me. As far as adding new vertices and edges does not result in resizing of the underlying std::vector, this would be as good as you get. At...
@milroy and I discussed this after our meeting yesterday. Two things: We agreed it would be better to use `attach` amd `detach` instead of our initial `grow` and `shrink` because...
@milroy and I chatted about this yesterday. This is also highly related to our work on resiliency (which is my next task to complete). Issue #470.
@milroy: I'm going to group together issues that support elasticity with a new label.
Thanks @garlick. This captures our coffee discussion very well and thank you for opening up the issue to capture our discussion. For the case we have multiple queues with overlapping...
>Also, each queue can easily have per-queue specific control (e.g., queue-depth) which is also extensible, they can serve as devising/innovating Flux-specific cross-queue fairness for overlapping resources. Maybe we could still...
Using this ticket to collect more thoughts per https://github.com/flux-framework/rfc/pull/332#issuecomment-1128925343. Two things that one can possibly make some incremental progress while observing the effects: 1. Assign a priority to each queue...
Thanks. We should add an range check into our jobspec parser
At least how `qmanager` handles the parse error from Jobspec has been improved by PR #652