Hi,
Can someone, please, shepherd MESOS-6207? It's about fixing Python
bindings build on systems with non-conventional SVN library
installation path. I've submitted a patch for review. Thanks!
--
Ilya Pronin
Michael,
I'm doing this wrong too and I have expensive laptop as well. I don't know
any better solution than interleave compilation with other work. This is
not always productive, hence
+1 for this change.
As a side note, we should probably revive the effort of a) splitting huge
.cpps into small
If we can split the test files sensibly, it will greatly enhance the module
testing/CI down the road. While we are on the topic, maybe, we can create
some static/shared tests-specific libs that can be installed along with
some headers to allow module devs to use gtest/gmock for testing! However,
it
Thanks for the +1 Alex!
Kapil, yes, I've spoken to Till around the pain of using Mesos internals
in modules, and how we might expose them from Mesos more sensibly.
I'm not directly aiming to tackle that problem in this effort, but drive-by
improvements would be awesome to better position ourselve
Hi Benno,
Thanks for taking the pains and putting in the effort to put up the
proposal. I think the proposal in general looks very reasonable for a
standalone IPv6 mesos stack. I had a few comments on the "network
isolation" section, namely adding support to `network/cni` isolator but
that can be
