Jim Garlick

Hmm, yeah I know @grondo and I have discussed this in the past. I'm not finding an issue on it so maybe we ought to get one open (I'll do...

> @garlick proposed the idea of allowing updates to the expiration via the job eventlog. I don't actually remember what I proposed here but given that this is essentially a...

I can't think why this would be required. In the hello handshake where only R is provided, the resources need to be re-allocated immediately so no queueing should be needed....

That's essentially it. The rank 0 broker in this case is the first node of the batch/alloc job, whcih is a flux instance owned by the user. It's not necessary...

`flux-filemap` was replaced with `flux-archive` which no longer has the rank 0 constraint. Cray is aware of the change and is presumably reworking the CTI implementation for flux. Closing this.

This was a valiant attempt but I think since a couple of years have gone by without action due to other priorities, it's appropriate to withdraw the PR for now.

What about adding `__attribute__ ((deprecated))` to the C functions, and then logic in the python binding generation script to not generate bindings for functions with that attribute?

I thought there was already some code in the binding generator script to ingest multi-line function prototypes but I could be wrong.

Closing this. We can open issues against `flux-archive(1)` if there are still things missing.

Reworked PR coming soon, closing this one.