Mark Grondona

I think the most complete solution might be to require both a cores and nodes limit for jobs, and if either is exceeded the job is rejected. This is what...

I was thinking you'd check both values and if either exceeded the configured limit then the job is rejected. If you can't tell how much of a resource is in...

Very good points @ryanday36. @cmoussa1 apologies, I had lost sight of the overall goal for the accounting limits. My apologies. I think you seem to be headed on the right...

To answer your original question, you can get access to the resources in an instance by fetching `resource.R` from the KVS. You'll have to parse the result yourself though, we...

> I should note that I was working on a patch (but haven't finished yet) as @trws recommended in Slack that would make strip = from options in lines 62-70...

Also the prefix should probably be `docker:` or `test:` instead of `scripts:`, though it doesn't really matter that much

> I used echo but this will show up every time someone runs this on a mac. That might clutter things unnecessarily... Yeah, I'd rather not see that when I...

Could the backup queue idea be implemented instead in jacamar? It could check if all the nodes in a queue are down and submit instead to the 2nd choice? Jacamar...

I think the main problem here is the constantly updating timer on the right hand side. If we just print a status line if the command waits for >2s in...

We should decide if adding the constraint query support to `-f, --filter` is the right approach. It is more powerful, and `flux-jobs(1)` automatically gets support for the match operators supported...