[RESULT][VOTE] Release Apache Mesos 1.0.3 (rc2)

[Vinod Kone]

Hi all,


The vote for Mesos 1.0.3 (rc2) has passed with the

following votes.


+1 (Binding)

--

Vinod Kone

Adam Bordelon

Kapil Arya


There were no 0 or -1 votes.


Please find the release at:

https://dist.apache.org/repos/dist/release/mesos/1.0.3


It is recommended to use a mirror to download the release:

http://www.apache.org/dyn/closer.cgi


The CHANGELOG for the release is available at:

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.3


The mesos-1.0.3.jar has been released to:

https://repository.apache.org


The website (http://mesos.apache.org) will be updated shortly to reflect
this release.


Thanks,

On Mon, Feb 6, 2017 at 12:07 PM, Kapil Arya  wrote:

> +1 binding.
>
> Built rpm/deb packages on internal build jobs. Packages are available here:
>  http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.3-rc2
>
> On Mon, Feb 6, 2017 at 3:01 PM, Adam Bordelon  wrote:
>
> > +1 binding
> >
> > Tests passed against DC/OS 1.8.8 (prerelease), which is based on the
> Apache
> > Mesos 1.0.x branch.
> > https://github.com/dcos/dcos/pull/1210
> >
> > On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Tested on ASF CI
> > >
> > >
> > > *Revision*: c673fdd00e7f93ab7844965435d57fd691fb4d8d
> > >
> > >- refs/tags/1.0.3-rc2
> > >
> > > Configuration Matrix gcc clang
> > > centos:7 --verbose --enable-libevent --enable-ssl autotools
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> > 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> > 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Not run]
> > > cmake
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> > verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> > GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> > 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Not run]
> > > --verbose autotools
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> > exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Not run]
> > > cmake
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> > verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> > 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Not run]
> > > ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> > 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> > 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=clang,
> CONFIGURATION=--verbose%20--
> > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> > 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> > 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > cmake
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> > verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> > GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> > docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> > -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> > GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> > docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > --verbose autotools
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> > label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > [image: Success]
> > >  > Release/26/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
> > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> > label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > > cmake
> > > [image: Success]
> > >  > 

Re: Introduction of `int_fd`.

[Alex Clemmer]

It's great to see this shipped! Thanks, mpark.

As an aside: One of the impacts of this work is that it is the last
major change blocking the Windows Containers patches, which will be very
exciting to see finally lit up.

I will follow up this work with some more in-depth tests to prevent
regressions around some of the more subtle behavior of the Windows
codepaths. (The POSIX codepaths are supposed to remain unaffected, so
the risk is incurred only on the Windows side.)


__
Transcribed by my voice-enabled refrigerator, please pardon chilly messages.

On Mon, 6 Feb 2017, Michael Park wrote:


I'd like to announce that we've introduced an `int_fd` type in stout.
It is __not__ an RAII file descriptor type! It's actually not fancy
what-so-ever.

On POSIX, it's simply aliased to an `int`, so there's no change in usage at
all.
Just remember to use `int_fd` rather than `int` for file descriptors.

If you're wondering why we introduced this in the first place, continue
reading:

On Windows, `int_fd` is aliased to a type called `WindowsFD`. The reason is
that the abstraction on Windows has multiple types that represent
"file descriptors" from various APIs. Namely, WinCRT, Win32, WinSock.

Due to this, on Windows we have to deal with `int` from WinCRT, `HANDLE`
from Win32, and `SOCKET` from WinSock. In order to not require large changes
through the entire codebase, we've decided to rendezvous at the POSIX `int`.

`WindowsFD` is one of: `int`, `HANDLE`, and `SOCKET`, and tries its best to
provide the same API as the POSIX `int` file descriptor. Notably, the
comparison
operators are implemented to support expressions such as `fd < 0` and `fd
!= -1`.

Thanks to Daniel Pravat, Alex Clemmer, and Benjamin Hindman for helping out
with this work.

You know who you ping if you run into issues or have questions =D

Thanks,

MPark

Introduction of `int_fd`.

[Michael Park]

I'd like to announce that we've introduced an `int_fd` type in stout.
It is __not__ an RAII file descriptor type! It's actually not fancy
what-so-ever.

On POSIX, it's simply aliased to an `int`, so there's no change in usage at
all.
Just remember to use `int_fd` rather than `int` for file descriptors.

If you're wondering why we introduced this in the first place, continue
reading:

On Windows, `int_fd` is aliased to a type called `WindowsFD`. The reason is
that the abstraction on Windows has multiple types that represent
"file descriptors" from various APIs. Namely, WinCRT, Win32, WinSock.

Due to this, on Windows we have to deal with `int` from WinCRT, `HANDLE`
from Win32, and `SOCKET` from WinSock. In order to not require large changes
through the entire codebase, we've decided to rendezvous at the POSIX `int`.

`WindowsFD` is one of: `int`, `HANDLE`, and `SOCKET`, and tries its best to
provide the same API as the POSIX `int` file descriptor. Notably, the
comparison
operators are implemented to support expressions such as `fd < 0` and `fd
!= -1`.

Thanks to Daniel Pravat, Alex Clemmer, and Benjamin Hindman for helping out
with this work.

You know who you ping if you run into issues or have questions =D

Thanks,

MPark

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

[Kapil Arya]

+1 binding.

Built rpm/deb packages on internal build jobs. Packages are available here:
 http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.3-rc2

On Mon, Feb 6, 2017 at 3:01 PM, Adam Bordelon  wrote:

> +1 binding
>
> Tests passed against DC/OS 1.8.8 (prerelease), which is based on the Apache
> Mesos 1.0.x branch.
> https://github.com/dcos/dcos/pull/1210
>
> On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone  wrote:
>
> > +1 (binding)
> >
> > Tested on ASF CI
> >
> >
> > *Revision*: c673fdd00e7f93ab7844965435d57fd691fb4d8d
> >
> >- refs/tags/1.0.3-rc2
> >
> > Configuration Matrix gcc clang
> > centos:7 --verbose --enable-libevent --enable-ssl autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > --verbose autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > --verbose autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >
> > On Tue, Jan 31, 2017 at 11:46 AM, Vinod Kone 
> wrote:
> >
> >> Hi all,
> >>
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 1.0.3.
> >>
> >>
> >> 1.0.3 includes the following:
> >>
> >> 
> >> 
> >>
> >> * [MESOS-6052] - Unable to launch containers on CNI networks on
> >> CoreOS
> >>
> >> * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
> 

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

[Adam Bordelon]

+1 binding

Tests passed against DC/OS 1.8.8 (prerelease), which is based on the Apache
Mesos 1.0.x branch.
https://github.com/dcos/dcos/pull/1210

On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI
>
>
> *Revision*: c673fdd00e7f93ab7844965435d57fd691fb4d8d
>
>- refs/tags/1.0.3-rc2
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
> 
> [image: Not run]
> cmake
> [image: Success]
> 
> [image: Not run]
> --verbose autotools
> [image: Success]
> 
> [image: Not run]
> cmake
> [image: Success]
> 
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
> 
> [image: Success]
> 
> cmake
> [image: Success]
> 
> [image: Success]
> 
> --verbose autotools
> [image: Success]
> 
> [image: Success]
> 
> cmake
> [image: Success]
> 
> [image: Success]
> 
>
> On Tue, Jan 31, 2017 at 11:46 AM, Vinod Kone  wrote:
>
>> Hi all,
>>
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.0.3.
>>
>>
>> 1.0.3 includes the following:
>>
>> 
>> 
>>
>> * [MESOS-6052] - Unable to launch containers on CNI networks on
>> CoreOS
>>
>> * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
>>
>>
>> * [MESOS-6621] - SSL downgrade path will CHECK-fail when using both
>> temporary and persistent sockets
>>
>> * [MESOS-6676] - Always re-link with scheduler during
>> re-registration.
>>
>> * [MESOS-6917] - Segfault when the executor sets an invalid UUID when
>> sending a status update.
>>
>>
>> The CHANGELOG for the release is available at:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
>> lain;f=CHANGELOG;hb=1.0.3-rc2
>>
>> 

[GitHub] mesos pull request #:

[xujyan]

Github user xujyan commented on the pull request:


https://github.com/apache/mesos/commit/a1b86051d3d9120b8ef00a3e3ac18786a630dd76#commitcomment-20769217
  
In src/master/allocator/mesos/hierarchical.cpp:
In src/master/allocator/mesos/hierarchical.cpp on line 682:
Doesn't look like we need to make this copy here and the non-const ref 
`Offer::Operation& operation` below? (The adjustments are already made in the 
master?)


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,gcc,--verbose,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2) #3220

[Neil Conway]

I haven't seen this test fail elsewhere, but there's at least one
other instance of it failing on ASF CI. Unfortunately I couldn't fetch
the logs in either case (any chance we change the ASF Jenkins
configuration to keep logs for failing jobs for longer?). I'll keep an
eye out to see if I can get a log.

Neil

On Sat, Feb 4, 2017 at 1:24 PM, Benjamin Mahler  wrote:
> +neil
>
> Is this test flaky? I wasn't able to grab the logs since jenkins appears to
> be non-responsive at the moment.
>
> [  FAILED  ] RegistrarTest.PruneUnreachable
>
> On Sat, Feb 4, 2017 at 3:03 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> See > autotools,COMPILER=gcc,CONFIGURATION=--verbose,
>> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
>> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/3220/changes>
>>
>> Changes:
>>
>> [xujyan] Use the stout ELF parser to implement ldd.
>>
>> [xujyan] Add some simple ldd() tests.
>>
>> [xujyan] Use the stout ELF parser to collect Linux rootfs files.
>>
>> [benjamin.hindman] Replaced recursive implementation in http::Connection
>> with loop.
>>
>> [benjamin.hindman] Re-enabled disabled test.
>>
>> [benjamin.hindman] Replaced (another) recursive implementation with
>> process::loop.
>>
>> [benjamin.hindman] Re-enabled a test.
>>
>> [benjamin.hindman] Introduced process::after.
>>
>> [benjamin.hindman] Used process::after instead of process::RateLimiter.
>>
>> --
>> [...truncated 177912 lines...]
>> I0204 11:00:49.951364 30284 status_update_manager.cpp:203] Recovering
>> status update manager
>> I0204 11:00:49.951576 30279 containerizer.cpp:599] Recovering containerizer
>> I0204 11:00:49.952945 30290 provisioner.cpp:410] Provisioner recovery
>> complete
>> I0204 11:00:49.953316 30280 slave.cpp:5499] Finished recovery
>> I0204 11:00:49.953835 30280 slave.cpp:5673] Querying resource estimator
>> for oversubscribable resources
>> I0204 11:00:49.954129 30279 slave.cpp:5687] Received oversubscribable
>> resources {} from the resource estimator
>> I0204 11:00:49.957427 30284 process.cpp:3697] Handling HTTP event for
>> process 'slave(694)' with path: '/slave(694)/monitor/statistics.json'
>> I0204 11:00:49.958652 30289 http.cpp:871] Authorizing principal
>> 'test-principal' to GET the '/monitor/statistics.json' endpoint
>> I0204 11:00:49.962405 30280 slave.cpp:803] Agent terminating
>> [   OK ] Endpoint/SlaveEndpointTest.AuthorizedRequest/1 (31 ms)
>> [ RUN  ] Endpoint/SlaveEndpointTest.AuthorizedRequest/2
>> I0204 11:00:49.972606 30259 containerizer.cpp:220] Using isolation:
>> posix/cpu,posix/mem,filesystem/posix,network/cni
>> W0204 11:00:49.973045 30259 backend.cpp:76] Failed to create 'aufs'
>> backend: AufsBackend requires root privileges
>> W0204 11:00:49.973139 30259 backend.cpp:76] Failed to create 'bind'
>> backend: BindBackend requires root privileges
>> I0204 11:00:49.973171 30259 provisioner.cpp:249] Using default backend
>> 'copy'
>> I0204 11:00:49.976068 30278 slave.cpp:211] Mesos agent started on (695)@
>> 172.17.0.4:47679
>> I0204 11:00:49.976094 30278 slave.cpp:212] Flags at startup: --acls=""
>> --appc_simple_discovery_uri_prefix="http://; 
>> --appc_store_dir="/tmp/mesos/store/appc"
>> --authenticate_http_readonly="true" --authenticate_http_readwrite="true"
>> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
>> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
>> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
>> --cgroups_limit_swap="false" --cgroups_root="mesos" 
>> --container_disk_watch_interval="15secs"
>> --containerizers="mesos" --credential="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_2_WNyVh6/credential" --default_role="*"
>> --disk_watch_interval="1mins" --docker="docker"
>> --docker_kill_orphans="true" --docker_registry="https://
>> registry-1.docker.io" --docker_remove_delay="6hrs"
>> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns"
>> --docker_store_dir="/tmp/mesos/store/docker" --docker_volume_checkpoint_
>> dir="/var/run/mesos/isolators/docker/volume" 
>> --enforce_container_disk_quota="false"
>> --executor_registration_timeout="1mins" 
>> --executor_shutdown_grace_period="5secs"
>> --fetcher_cache_dir="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_2_WNyVh6/fetch" --fetcher_cache_size="2GB"
>> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1"
>> --hadoop_home="" --help="false" --hostname_lookup="true"
>> --http_authenticators="basic" --http_command_executor="false"
>> --http_credentials="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_2_WNyVh6/http_credentials" 
>> --http_heartbeat_interval="30secs"
>> --initialize_driver_logging="true" --isolation="posix/cpu,posix/mem"
>> --launcher="posix" --launcher_dir="/mesos/mesos-1.2.0/_build/src"
>> --logbufsecs="0" --logging_level="INFO" 
>> 

[GitHub] mesos pull request #202: Size of the favicon optimized.

[ArmandGrillet]

GitHub user ArmandGrillet opened a pull request:

https://github.com/apache/mesos/pull/202

Size of the favicon optimized.

The favicon now only contains two images: 16x16 and 32x32 (for Retina
displays). The size has been reduced from 361 KB to 5 KB.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ArmandGrillet/mesos smaller-favicon

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/202.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #202


commit 19741bd311d3b7f558939f172d01c1546d99
Author: Armand Grillet 
Date:   2017-02-06T14:39:59Z

Size of the favicon optimized.

The favicon now only contains two images: 16x16 and 32x32 (for Retina
displays). The size has been reduced from 361 KB to 5 KB.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---