[GitHub] mesos pull request #195: Update contributors.yaml

2016-12-14 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/195 --- 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

Re: Order of includes

2016-12-14 Thread Michael Park
I would vote to keep the "include yourself first" rule, for reasons that Benjamin points out. I think that we (committers) shouldn't be actively (and silently) going against the rules we have in place. Aside from that... the constructive thing I can suggest is to help enforcement by continuing

thread_local supported on Apple

2016-12-14 Thread Joris Van Remoortere
The time has come and we finally have `thread_local` support in the Apple tool chain: https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html In our code base we have a special exception for Apple that defines our thread local to be `__thread` rather

[GitHub] mesos pull request #195: Update contributors.yaml

2016-12-14 Thread bernadinm
GitHub user bernadinm opened a pull request: https://github.com/apache/mesos/pull/195 Update contributors.yaml Contributed: https://reviews.apache.org/r/53832/ https://reviews.apache.org/r/53324/ You can merge this pull request into a Git repository by running: $ git

Re: Command healthcheck failed but status KILLED

2016-12-14 Thread Tomek Janiszewski
Thanks Gastón. Do we have a shepherd for this? It's not critical but make it hard to distinguish task killed by failed health check from killed by scheduler. wt., 13.12.2016 o 16:55 użytkownik Gastón Kleiman napisał: > On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski

Re: [webui] Started show wrong time

2016-12-14 Thread Tomek Janiszewski
Thanks Haosdent. I described possible solution in ticket. If it's ok I can prepare a patch. śr., 14.12.2016 o 05:05 użytkownik haosdent napisał: > Hi, @Tomek. Thank you for your report. Create a ticket at > https://issues.apache.org/jira/browse/MESOS-6790, feel free to post