WebUI: CORS in Mesos Design Doc + Discussion

Hi all, There has been a bit of discussion surrounding cross-origin resource sharing in Mesos and we would like to float a design doc to delineate/collect thoughts from the community and propose an implementation. For a bit of context: From the master WebUI we construct agent resource

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

We work around autotools and protobuf bugs and glibc is only harder for users and developers to upgrade. :) I agree that we can establish the minimum glibc version/linux distro releases etc we support but currently we don't and there are folks who use Mesos that depend on this version. We should

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

I saw this on ASF CI

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

Personally, I'm not convinced that we need to fix MESOS-7378. The problem is essentially a bug in glibc that was fixed 6 years ago. (As a point of reference, the oldest version of g++ we support was released 2 years ago... :) ) Neil On Mon, May 8, 2017 at 3:45 PM, Yan Xu wrote: > I

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

s/0.13.0/1.3.0/ :) --- Jiang Yan Xu | @xujyan On Mon, May 8, 2017 at 3:45 PM, Yan Xu wrote: > I am still hoping that we get https://issues.apache.org/ > jira/browse/MESOS-7378 fixed before shipping 0.13.0. :) > > --- > Jiang Yan Xu

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

I am still hoping that we get https://issues.apache.org/jira/browse/MESOS-7378 fixed before shipping 0.13.0. :) --- Jiang Yan Xu | @xujyan On Fri, May 5, 2017 at 6:31 PM, Michael Park wrote: > Hi all, > > Please vote on releasing the

Re: Choice between LOG(FATAL) and EXIT(EXIT_FAILURE)

> On May 8, 2017, at 2:02 PM, Zhitao Li wrote: > > Hi Vinod, > > I'm reviving this old conversation from last year. > > We are feeling some operational pain again, mostly due to journald > truncates the stderr of Mesos agent so we cannot see a full exit message > even

Re: Version numbers during development

We need to make sure that our release scripts in "support/" and CI jobs work with this change. Quite a few of them depend on the version number. Also, I know of at least one organization that does version parsing in their build scripts. I want to make sure we don't break such orgs. So we should

Re: Choice between LOG(FATAL) and EXIT(EXIT_FAILURE)

Hi Vinod, I'm reviving this old conversation from last year. We are feeling some operational pain again, mostly due to journald truncates the stderr of Mesos agent so we cannot see a full exit message even in journald, and the error is not in GLOG output at all. I filed

Re: Version numbers during development

Per offline discussion with mpark, he suggested a preference for "-dev" rather than "-devel", which sounds fine to me. Based on the lack of objections, I'll plan on making this change shortly: (1) changing the version number in master to "1.4.0-dev", and (2) updating the release process

Re: [4/6] mesos git commit: Checked validity of master and agent version numbers on startup.

There was an earlier thread on whether to ignore registration attempts from pre-1.0 Mesos agents: https://lists.apache.org/thread.html/f5e15f6d7a3f3b08d29e27455e2e1c801775418a148dded953c568e7@%3Cdev.mesos.apache.org%3E We didn't explicitly discuss what to do when the compiled-in version of Mesos

Re: [4/6] mesos git commit: Checked validity of master and agent version numbers on startup.

@Neil: Have we sent an email about this change to dev list? This might break people who were directly building off source and using a custom version number. On Fri, May 5, 2017 at 4:54 PM, wrote: > Checked validity of master and agent version numbers on startup. > > During

Re: documenting test expactations

My two cents: (1) I almost always need to read the test to understand/debug a test failure. (2) As long as the intent of the test is clear, I'm not picky about whether clarifying comments take the form of C++ comments or explanatory EXPECT messages. One thing I would be opposed to is adding

Re: documenting test expactations

> On May 1, 2017, at 4:28 PM, Benjamin Mahler wrote: > > Do you have some examples? I think that this: EXPECT_EQ(Bytes(512u), BasicBlocks(Bytes(128)).bytes()) << "a partial block should round up"; is a strict superset of this: // A partial block should round up.