----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68017/#review211986 -----------------------------------------------------------
Fix it, then Ship it! include/mesos/mesos.proto Lines 3158-3159 (patched) <https://reviews.apache.org/r/68017/#comment297565> Seems like this was added recently. Is this field only used when there is a default agent wide seccomp profile provided from the agent flag? and we reply on it to give an opportunity for user/framework to get rid of seccomp? (probably more comment needed) If it is the case, do we have other options for naming? e.g., `no_seccomp` (maybe more explicit) - Gilbert Song On Nov. 8, 2018, 7:24 a.m., Andrei Budnik wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68017/ > ----------------------------------------------------------- > > (Updated Nov. 8, 2018, 7:24 a.m.) > > > Review request for mesos, Gilbert Song, Jie Yu, James Peach, and Qian Zhang. > > > Bugs: MESOS-9033 > https://issues.apache.org/jira/browse/MESOS-9033 > > > Repository: mesos > > > Description > ------- > > See summary. > > > Diffs > ----- > > include/mesos/mesos.proto 2ef6ba3aef67cf34227569948fd3ddc8dfd5879d > include/mesos/seccomp/seccomp.hpp PRE-CREATION > include/mesos/seccomp/seccomp.proto PRE-CREATION > include/mesos/slave/containerizer.proto > 5b4dcdda0f55ea3355c78d1447c7be9ca54d9dc9 > include/mesos/v1/mesos.proto 1a701da65f653fe4191f92ff1fb1436809b50acb > src/CMakeLists.txt a574d449dc26b820cbef7ff0b5e94b42b6fe86cf > src/Makefile.am 188a47017221a931d8b965a4af5e033b77e6ce4e > > > Diff: https://reviews.apache.org/r/68017/diff/14/ > > > Testing > ------- > > > Thanks, > > Andrei Budnik > >
