Jim Garlick

So let me understand: unchecked growth of the spec into as yet unidentified problem domains is acceptable as long as * there are no conflicts between proposed changes * everything...

> Fragmented support like that would introduce a lot of complexity and effort for the users of the PMIx standard (analogous to the complexity of Android development when the phone...

> presently in the content cache, if a backing store is not configured, a cache store request returns ENOSYS to the caller. I think you meant a `content.flush` request returns...

> Nope, I was specifically thinking about cache.store, b/c in the continuation... Ah sorry, I knew we supported running w/o a backing store e.g. `t0028-content-backing-none.t`, but I had forgotten that...

If we go that route, we should think about making it an optional feature or even a sqlite specific feature since the extra work in the other backing stores that...

I don't think garbage collection would be effective in the kind of situations we've seen - terabyte log files, huge crashdumps. In the log file case, any space we free...

> Unfortunately not super user friendly if you want to specify a fractional amount like 4 hours and 30 minutes (i.e., 270m in FSD). 4.5h would be valid FSD as...

Maybe the tiny FSD RFC should be updated with 1) NaN not allowed, and 2) decimal point optional. Jim On Fri, Jun 28, 2019 at 12:37 PM Stephen Herbein wrote:...

> flux run --nslots 4 --shape socket[2]>core[4] [oar](https://oar.readthedocs.io/en/2.5/user/usecases.html#examples-of-resource-requests) has a nice and very unslurmish way of expressing resource requirements on the command line FWIW.

I guess it's somewhat of a gap but our front end commands (batch/submit/run) don't take jobspec as input AFAICT. One idea might be to add a `--jobspec=FILE` option that by...