Jim Garlick
Jim Garlick
Oh thanks for that reference. To be honest I didn't follow it all, but I'm at least glad you're all over it. IMHO, would be nice if one got more...
This seems pretty interesting and useful. On the speed, well, this has got to be faster than grabbing everything and filtering on the client end, plus if we could identify...
Current procedure is apply this diff to rc1 (assuming you're running the test instance from the source tree) ```diff diff --git a/etc/rc1 b/etc/rc1 index dfb6b615d..72c5351e0 100755 --- a/etc/rc1 +++ b/etc/rc1...
One simple idea would be to add a way to add a temporary, named exception "capability" to the KVS under some name that the user would reference from their job...
> Another idea, perhaps writing a treeobj should be limited to instance owners, not guest users? Yes. I'll open an issue on that one. That would tighten things up considerably...
> And something that would end up in a ELOOP error could be pointed to some generally global "eloop ocurred" kind of error. And these error blobrefs could be easily...
Most likely obvious, but since I didn't immediately think of it: the mechanism to add a constraint based on the selected queue would also have to be implemented in such...
@grondo had the idea of moving the jobspec updates to the ingest module's validator plugins. That makes a lot of sense: it should scale better since ingest is loaded on...
Seems like it might be a good thing? it does seem more convenient to have the modified one most of the time. And we could add a way to access...