Re: Mesos CLI

> > The best option may still be for it > to be in Python, this is why I'm asking if there are particular things that > our helper libraries don't provide which you are leveraging in python. > One thing we rely heavily on that is missing is `docopt`. We use docopt for convenient / standardized

Re: [Protobuf] Why do we mark field as 'required'

+1 Proto3 killed 'required' keyword. On Wed, Jun 22, 2016 at 5:15 PM, Jay JN Guo wrote: > > > Hi, > > I find marking protobuf field as 'required' sometimes causing trouble: > serializing a message without filling up required field generates errors > and this is hard to

[Protobuf] Why do we mark field as 'required'

Hi, I find marking protobuf field as 'required' sometimes causing trouble: serializing a message without filling up required field generates errors and this is hard to change due to backwards compatibility. And this message type is actually discouraged by protobuf:

Re: [VOTE] Release Apache Mesos 0.26.2 (rc1)

+1 (binding) Make check on OS X 10.11.5. On Mon, Jun 20, 2016 at 5:10 PM, Kapil Arya wrote: > +1 (binding) Internal CI build. > > Here is a link to the deb/rpm packages: > > http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.26.2-rc1 > > > > On Mon, Jun 20, 2016

Re: Mesos CLI

> > Is there strong opposition to python for any > reason other than code parity? For me the history of a shortage of python maintainers / committers is the concern. As this tool gains popularity I would worry that new feature requests would be slow to get merged based on when the python experts

Re: Mesos CLI

Here is a link to the design doc: https://docs.google.com/document/d/1r6Iv4Efu8v8IBrcUTjgYkvZ32WVscgYqrD07OyIglsA/edit?ts=57573bba# It sounds like people would like to see the CLI written in C++. However, the reference implementation we have is written completely in python. Please see the section

Re: Mesos CLI

+1 for maintaining in repo. +1 for C++. Are the tools in libprocess not sufficient to make this easy to write? What is missing that would make it easier to write in C++? — *Joris Van Remoortere* Mesosphere On Wed, Jun 22, 2016 at 2:24 AM, Zhou Z Xing wrote: > +1 for

Re: [GPU] [Allocation] "Scarce" Resource Allocation

I see. This is good to know for current development work. Thanks for clarifying, Guangya and Kevin.  Elizabeth Lingg > On Jun 22, 2016, at 3:02 AM, Guangya Liu wrote: > > Hi Elizabeth, > > Just FYI, there is a JIRA tracing the resource revocation here >

Re: [GPU] [Allocation] "Scarce" Resource Allocation

Hi Elizabeth, Just FYI, there is a JIRA tracing the resource revocation here https://issues.apache.org/jira/browse/MESOS-4967 And I'm also working on the short term solution of excluding the scarce resources from allocator (https://reviews.apache.org/r/48906/), with this feature and Kevin's