Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/189
---
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 user xiaohui opened a pull request:
https://github.com/apache/mesos/pull/189
add UCloud to `powered by mesos` list.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xiaohui/mesos master
Alternatively you can review and
The continuation needs to go through the process manager once again to
obtain a reference to the process that we'd like to deliver the message to.
One thing we could have done to avoid capturing 'this' is to grab the
ProcessReference early and pass it through to the continuation.
Unfortunately the
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/181
---
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 user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/187
---
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 user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/188
---
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 user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/185
---
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 user terrymanu commented on a diff in the pull request:
https://github.com/apache/mesos/pull/181#discussion_r89080820
--- Diff: docs/frameworks.md ---
@@ -30,6 +30,7 @@ layout: documentation
* [Chronos](https://github.com/mesos/chronos) is a distributed job
Hi,
just came across this with our `mesos-this-capture` clang-tidy check:
> +// It is guaranteed that the continuation would run before the next
> +// request arrives. Also, it's fine to pass the `this` pointer to the
> +// continuation as this would get executed synchronously (if
