Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

There is a reverse proxy for Google Forms in China by GDG China. Replace the *docs.google.com * to *www.gdgdos.org * will make Google Forms accessible from China. The project page: https://github.com/GDGNanyang/gdgdocs On Tue, Sep 20, 2016 at

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

Hi David, Looks great. I really suggest that we can have one meeting to talk about proposals, it's supposed to be included some guys in China, and diversity, for example the company who is using Mesos, the company who is providing Mesos solution, developers, architect, QA, super users,

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

https://www.surveymonkey.com should be ok to China contributors :). Da (Klaus), Ma (马达), PMP® | Software Architect IBM Spectrum Conductor Development & Support, STG, IBM GCG +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me On Sep 20, 2016, at 11:20, Yan Xu

Coverity Scan: Analysis completed for Mesos

Your request for analysis of Mesos has been completed successfully. The results are available at

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

+1. Count me for survey as well. Surveymonkey is good choice, considering Google Forms could be blocked. Thanks! Regards, Vivek Juneja Developer / Architect / Technology Evangelist *My Home on Web : www.vivekjuneja.in | **www.cloudgeek.in

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

Would surveymonkey.com be more accessible? On Monday, September 19, 2016, Yan Yan YY Hu wrote: > We need proxy to access Google in China mainland. But I guess this won't > be a problem for us since there are many tools can help to cross the > GreatFireWall :) > > Best

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

We need proxy to access Google in China mainland. But I guess this won't be a problem for us since there are many tools can help to cross the GreatFireWall :) Best regards! ** Yanyan Hu(胡彦彦) Ph.D. Cloud Infrastructure & Technology Team Building 19 Zhongguancun

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

Specifically, we want to make sure that everyone will be able to access the forms if we put them on Google forms/docs. On Mon, Sep 19, 2016 at 7:04 PM Hechen Gao wrote: > Hey David, > > I would love to contribute to your survey about the MesosCon, please count > me in.

[GitHub] mesos pull request #168: Update contributors.yaml for gradywang.

Github user gradywang commented on a diff in the pull request: https://github.com/apache/mesos/pull/168#discussion_r79523013 --- Diff: docs/contributors.yaml --- @@ -402,13 +402,13 @@ jira_user: yanyanhu reviewboard_user: yanyanhu -- name: Yong Qiao Wang

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

Hey David, I would love to contribute to your survey about the MesosCon, please count me in. Best regards, Hechen Gao Senior Software Engineer, Cloud Platforms - Engineering Core Services Autodesk, Inc. The Landmark @ One Market, Suite 500 San Francisco, CA 94105

Re: 中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

+1 在 2016年9月20日 上午8:22，David Greenberg 写道： > 作为此次MesosCon大会的主席，我希望你们能够在今年杭州的MesosCon大会中听到你们喜欢的演讲和分享。所以，我们正在准备发出一个Google > Forms的调查，这个调查将会帮助我们更好的决定演讲和分享的内容。希望你们能够积极参与这个调查。你们的意见对我们很重要。 > > > David Greenberg, co-chair of MesosCon 敬上 > -- Deshi Xiao Twitter: xds2000

中国的Mesos爱好者们，关于今年在杭州的MesosCon大会

作为此次MesosCon大会的主席，我希望你们能够在今年杭州的MesosCon大会中听到你们喜欢的演讲和分享。所以，我们正在准备发出一个Google Forms的调查，这个调查将会帮助我们更好的决定演讲和分享的内容。希望你们能够积极参与这个调查。你们的意见对我们很重要。 David Greenberg, co-chair of MesosCon 敬上

[GitHub] mesos pull request #168: Update contributors.yaml for gradywang.

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/168#discussion_r79516117 --- Diff: docs/contributors.yaml --- @@ -402,13 +402,13 @@ jira_user: yanyanhu reviewboard_user: yanyanhu -- name: Yong Qiao Wang

[GitHub] mesos pull request #167: Add Mao Geng into contributors.

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/167 --- 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 #168: Update contributors.yaml for gradywang.

GitHub user gradywang opened a pull request: https://github.com/apache/mesos/pull/168 Update contributors.yaml for gradywang. Update contributors.yaml for gradywang. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gradywang/mesos

对于那些在中国问题

我们希望您对这些演讲的喜好会在MesosCon Hangzhou。您可以使用Google Forms，或做你喜欢不同的东西？目前，我们正在准备调查。 此致 敬礼 David Greenberg, co-chair of MesosCon 敬上

[GitHub] mesos pull request #166: Add Ilya Pronin to contributors

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/166 --- 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 #167: Add Mao Geng into contributors.

GitHub user gengmao opened a pull request: https://github.com/apache/mesos/pull/167 Add Mao Geng into contributors. In order to contribute my first mesos patch - https://reviews.apache.org/r/52048/ cc @kaysoky @Gilbert88 @karya0 You can merge this pull request into a Git

Accepted: Updated Invitation: Community Meeting @ Every 8 weeks from 9am to 10am on Thursday except Thu Sep 22 9am (PST) (Apache Mesos)

BEGIN:VCALENDAR METHOD:REPLY PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:America/Los_Angeles BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Updated Invitation: Community Meeting @ Every 8 weeks from 9am to 10am on Thursday except Thu Sep 22 9am (PST) (Apache Mesos)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

Re: mesos git commit: Fixed a bug in getRootContainerId due to protobuf copying issue.

Here is another problematic use case that I ran into a few weeks back: Running the following ends up enteringa recursive loop and blowing up the stack: ``` container.id.mutable_parent()->CopyFrom(container.id); ``` If you look at the body of `MergeFrom()`, which is called from

[GitHub] mesos pull request #166: Add Ilya Pronin to contributors

GitHub user ipronin opened a pull request: https://github.com/apache/mesos/pull/166 Add Ilya Pronin to contributors You can merge this pull request into a Git repository by running: $ git pull https://github.com/ipronin/mesos add-contributor Alternatively you can review and

Re: mesos git commit: Fixed a bug in getRootContainerId due to protobuf copying issue.

>From mesos.pb.h/mesos.pb.cc ``` inline ContainerID& operator=(const ContainerID& from) { CopyFrom(from); return *this; } void ContainerID::CopyFrom(const ::google::protobuf::Message& from) { if ( == this) return; Clear(); MergeFrom(from); } ``` On Mon, Sep 19, 2016 at 4:32

Re: mesos git commit: Fixed a bug in getRootContainerId due to protobuf copying issue.

@Neil, when ``` rootContainerId = rootContainerId.parent(); ``` protobuf would try to call `ContaienrID::Clear()` first and then perform `ContainerID::CopyFrom`. Because the parent has been broken after `ContainerID::Clear()`, so the `ContainerID::CopyFrom` would get an empty value. I think this

Fwd: mesos git commit: Fixed a bug in getRootContainerId due to protobuf copying issue.

Hi Jie, Do you have more details on what exactly the problem is here? If protobuf is unable to copy/merge nested messages in general, that seems like something that might crop up elsewhere. Perhaps we can (a) file a JIRA (ideally with a self-contained test-case), and/or (c) report the problem to