Thomas Gazagnaire

I think this should now be fixed with the HEAD version of functoria, which should be compatible with the HEAD version of mirage when #849 is merged.

@yomimono: I guess functoria needs to be released first and then mirage. Or I didn't understand your question :-)

Hum Indeed. I think I just checked that "configure -> build" was working as expected and assumed it would work for `describe` ... and we are not definitely not testing...

@Drup do you remember why you separated the `eval` of `eval_cached` in https://github.com/mirage/functoria/commit/9b742801b2ef5720c42c60fd8cebd601961ff6f4 ? Can't `describe` just use `eval_cached` as well?

Do you remember which case of failures? I will try to add some tests, so keen to test the failure modes as well.

Partially done in #43 : we can choose which store to store a given key/value pair (using the right functions). We still need to be able to do the same...

This is clearly not blocking the 4.0 release (and maybe we should disable warning in the generated dune file).

We still have a low-level CRUD API in Irmin 1.0 (using `ocaml-webmachine`), that are used by the `AO` and `RW` backends. We could add some kind of oauth there, as...

Not critical to have for 1.0.0 so moving the issue out of the Milestone.

Is there any hope to have a common HTTP/1 et HTTP/2 interface for unikernels? I know @TheLortex tried to have a common API the cohttp and httpaf but I'm not...