Jason Dusek

At present, Deimos just hands all container infos to the Docker containerizer. A while back, I did a refactor, where all the proto parsing was handled by a router that...

It isn't really clear that mounting the `fs` (where the URLs are unpacked) under `WORKDIR` is safe in general...but not adding `-w` when there is a `WORKDIR` seems easy enough.

These auto-incremented ports are actually provided by Mesos, at Marathon's request. Deimos just maps the ports it sees in the `TaskInfo` -- it doesn't have any port management logic. That...

I'm just not sure what the right thing to do is. Deimos puts URLs from the Mesos task in a directory which it mounts at `/tmp/mesos-sandbox` so tasks can find...

I believe that `libmesos` gets placed in `/usr/local/lib` by default; or at least, that used to be the case. (The `libmesos/ubuntu` container was built against an RC for Mesos 0.19.0.)...

👍

This has to do with the long run deprecation of the `ATOMIC_VAR_INIT` macro. At present, it shows up in only two places in Koka ([`kklib.h:126`](https://github.com/koka-lang/koka/blob/b1670308f88dd1fc6c22cad28385fcb185d5b27d/kklib/include/kklib.h#L126) and `kklib.h:127`): ```c #define KK_HEADER(scan_fsize,tag)...

Making these changes to [kklib.h:126](https://github.com/koka-lang/koka/blob/b1670308f88dd1fc6c22cad28385fcb185d5b27d/kklib/include/kklib.h#L126) and kklib.h:127, and then fixing two lines in what is probably an older version of `mimalloc`, does eliminate these errors for me. Whether the resulting...

The particular line highlighted above -- panicing on a non-existent change type -- might be better handled with logging. I suspect it is impossible in practice -- what there is...

Signed.