[GitHub] mesos issue #113: Added a file to test PR notifications.

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/113 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #92: combine "src/uri/fetcher.hpp" into "include/mesos/uri/fetch...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/92 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #99: Increased status timeout for LinuxFilesystemIsolatorTest.RO...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/99 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #92: combine "src/uri/fetcher.hpp" into "include/mesos/ur...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/92 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #126: Question : mesos networking

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/126 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #126: Question : mesos networking

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/126 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #113: Added a file to test PR notifications.

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/113 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #99: Increased status timeout for LinuxFilesystemIsolator...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/99 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #75: Changes in support of MESOS-3690

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/75 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #88: Update FindApr.cmake

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/88 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #90: [MESOS-4370] Retrieve network mode and use that to g...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/90 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #79: Patch Docker containerizer for container name

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/79 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #82: MESOS-3307 Configurable size of completed task / framework ...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/82 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #81: Documentation: Fixed broken links for images and doc...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/81 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #81: Documentation: Fixed broken links for images and docs

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/81 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #54: Add Linkernetworks into powered-by-mesos.md

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/54 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #82: MESOS-3307 Configurable size of completed task / fra...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/82 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #88: Update FindApr.cmake

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/88 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #79: Patch Docker containerizer for container name

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/79 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #90: [MESOS-4370] Retrieve network mode and use that to get that...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/90 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #75: Changes in support of MESOS-3690

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/75 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #54: Add Linkernetworks into powered-by-mesos.md

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/54 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #46: fixed broken 404 doc link for torque on mesos

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/46 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #49: MESOS-2424 FIX: protobuf installs latest setuptools ...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/49 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #41: Update fs.hpp

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/41 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #52: Remove thread_tests.cpp from CMakeLists.txt as the file was...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/52 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #51: [MESOS-3170] Add $LIBS to build path of the CRAM-MD5...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/51 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #47: fixed doc link for older spark on mesos project

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/47 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #52: Remove thread_tests.cpp from CMakeLists.txt as the f...

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/52 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #47: fixed doc link for older spark on mesos project

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/47 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #46: fixed broken 404 doc link for torque on mesos

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/46 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #49: MESOS-2424 FIX: protobuf installs latest setuptools in Meso...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/49 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #41: Update fs.hpp

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/41 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #51: [MESOS-3170] Add $LIBS to build path of the CRAM-MD5 test

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/51 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #37: correcting typo in allocation module docs

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/37 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #38: correcting formmating annotations

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/38 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #39: Proposing addition of missing hashCode function

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/39 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #38: correcting formmating annotations

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/38 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #37: correcting typo in allocation module docs

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/37 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #39: Proposing addition of missing hashCode function

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/39 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #23: Clean help flags

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/23 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #34: Replace hardcoded 'http:' in webui code with window.locatio...

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/34 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #31: Modified recovery timeout message for clarity

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/31 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #23: Clean help flags

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/23 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #34: Replace hardcoded 'http:' in webui code with window....

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/34 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #35: Update mesos-architecture.md

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/35 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #31: Modified recovery timeout message for clarity

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/31 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #30: Updates download instructions to latest version

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/30 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos issue #35: Update mesos-architecture.md

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/35 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #30: Updates download instructions to latest version

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/30 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #22: added example form to attributes flag help message

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/22 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] mesos pull request #22: added example form to attributes flag help message

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/22 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #12: Delete logging-and-debugging.md

Github user jfarrell closed the pull request at: https://github.com/apache/mesos/pull/12 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos issue #12: Delete logging-and-debugging.md

Github user jfarrell commented on the issue: https://github.com/apache/mesos/pull/12 Closing per request at https://s.apache.org/V8r3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

Re: [VOTE] Release Apache Mesos 1.0.0 (rc2)

+1 (nonbinding) Tested by 1)running all tests on Mac OS, 2) perform upgrade and downgrade on a small test cluster for both master and slave. On Mon, Jul 11, 2016 at 10:13 AM, Kapil Arya wrote: > None of the stable builds have SSL yet. The first SSL-enabled stable build >

[GitHub] mesos pull request #139: Add Ammar Askar to contributors.yaml

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/139 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #139: Add Ammar Askar to contributors.yaml

GitHub user ammaraskar opened a pull request: https://github.com/apache/mesos/pull/139 Add Ammar Askar to contributors.yaml You can merge this pull request into a Git repository by running: $ git pull https://github.com/ammaraskar/mesos master Alternatively you can review

Re: Disabling the --registry_strict flag in 1.0

Hi Neil, Does this mean that we'll have to cut another 1.0 RC just for that? If we were to cut another RC (e.g., due to bugs, which is likely), I would be happy to include the patch that disables the flag in the new RC. But if not, personally, I don't think this is necessary. As far as I know,

Re: Mesos docker image can't be started by docker-py

Zhiwei, >From the log, looks like Mesos received a SIGTERM from containerd, thus terminating. Can you check Docker's log as well. Can you also create a ticket to paste the log there? Thanks! - Jie On Tue, Jul 12, 2016 at 3:20 AM, zhiwei wrote: > Hi team, > > I can use

Disabling the --registry_strict flag in 1.0

Hi folks, I'd like to propose that we disable the --registry_strict flag for 1.0. You can find the rationale for this change here: https://issues.apache.org/jira/browse/MESOS-5833 Please let me know if you have any thoughts on whether we should make this change. Thanks, Neil

Fwd: ApacheCon Europe Call For Papers Open

FYI. - Original message - From: Rich Bowen To: gene...@incubator.apache.org Subject: ApacheCon Europe Call For Papers Open Date: Tue, 12 Jul 2016 19:00:19 - As you are no doubt already aware, we will be holding ApacheCon in Seville, Spain, the week of November

Re: getting added to contributors

I don't think it's a requirement but I agree that let's also make it explicit (Vinod already made it clear in the initial announcement but we could also be explicit when asking individual contributors whether they'd like to be added) so it's not perceived as one. --- Jiang Yan Xu |

Re: Lambdas: caveats, do's and don'ts

Now that you touch the topic, I think that we need to expand our style guide concerning lambdas. The rules do not cover all the cases, e.g. ``` auto lambda = [a, long, number, of, captures](a, long, number, of, parameters) -> ExplicitReturnType { } ``` so far, the formatting has been done

Re: [Action Required] Stale Reviews

Seems like the discussion has died down on this, unless anyone objects i'll run through and close out all marked pull requests in this doc later today -Jake On Sat, Jul 9, 2016 at 9:43 PM, Joris Van Remoortere wrote: > I've discarded almost all reviews older than 3

Mesos docker image can't be started by docker-py

Hi team, I can use `docker run` command to start a Mesos Agent container, but can't use docker-py to start. When I use docker-py to start the Mesos Agent container, the error message: I0712 09:44:28.624933 24919 docker.cpp:775] Recovering Docker containers I0712 09:44:28.625036 24918

Re: [Tech-debt] Introduce regex into Mesos

is header-only On Tue, Jul 12, 2016 at 5:43 PM, Klaus Ma wrote: > C++11 support regex in `std` which we'd like to use; but it seems only gcc > 4.9+ support it well. For the binaries, do you mean c++11's regex also need > libraries? > > > Da (Klaus), Ma (马达) | PMP®

Re: [Tech-debt] Introduce regex into Mesos

C++11 support regex in `std` which we'd like to use; but it seems only gcc 4.9+ support it well. For the binaries, do you mean c++11's regex also need libraries? Da (Klaus), Ma (马达) | PMP® | Software Architect Platform OpenSource Technology, STG, IBM GCG +86-10-8245 4084 |

Re: [Tech-debt] Introduce regex into Mesos

That was discussed in the past. The main issue is Mesos only bundles header only libraries and regex is a binary one. > On 05 Jul 2016, at 19:53, haosdent wrote: > >> As Joseph said, regex works well in llvm 7.3 & gcc 5.3, but does not work > in gcc 4.8.4; also try "" in gc

Re: getting added to contributors

Do we really want everyone who wants to be assigned a JIRA to also add themselves to the YAML file? To me, this adds another step to a contribution process that probably has too many steps already. Neil On Mon, Jul 11, 2016 at 7:31 PM, Vinod Kone wrote: > Welcome to the

Re: MESOS: Improve the performance of Resources.

I used callgrind to instrument the `allocate` function during one of the iterations of the allocator benchmarks. The ~2x came from the cpu cycle count reduction. As I said, that number wasn't within the range I was interested in, so I didn't spend much time on it. Rather I was using the callgrind