Thank you guys. Should have been more careful to avoid this.
On Wed, Feb 3, 2016 at 9:17 PM, Jie Yu wrote:
> Thanks James. Just committed a fix.
>
> On Wed, Feb 3, 2016 at 8:54 PM, James Peach wrote:
>
> >
> > > On Feb 3, 2016, at 5:45 PM, ji...@apache.org wrote:
> > >
> > > Plugged in docker r
Thanks James. Just committed a fix.
On Wed, Feb 3, 2016 at 8:54 PM, James Peach wrote:
>
> > On Feb 3, 2016, at 5:45 PM, ji...@apache.org wrote:
> >
> > Plugged in docker runtime isolator.
> >
> > Review: https://reviews.apache.org/r/43036/
> >
> >
> > Project: http://git-wip-us.apache.org/repos
> On Feb 3, 2016, at 5:45 PM, ji...@apache.org wrote:
>
> Plugged in docker runtime isolator.
>
> Review: https://reviews.apache.org/r/43036/
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/0b0a3dc5
> Tree: http://g
sure.
2016-02-04 1:52 GMT+08:00 Erik Weathers :
> A. Thanks Tommy. So I see that the Apache community doesn't release
> binary packages, just versioned source code tarballs:
>
>- https://mesos.apache.org/downloads/
>
> I'll follow up with Mesosphere directly, thanks!
>
> - Erik
>
> On We
And here is the blog post: http://mesos.apache.org/blog/mesos-0-27-0-released.
On Wed, Feb 3, 2016 at 4:48 PM, Michael Park wrote:
> Kapil is currently working on it. We'll publish it shortly :)
>
> On 3 February 2016 at 13:41, Benjamin Mahler wrote:
>>
>> Great! Is a blog post on the way?
>>
>>
Kapil is currently working on it. We'll publish it shortly :)
On 3 February 2016 at 13:41, Benjamin Mahler wrote:
> Great! Is a blog post on the way?
>
> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park wrote:
>
> > Hi all,
> >
> > The vote for Mesos 0.27.0 (rc2) has passed with the
> > following
Great! Is a blog post on the way?
On Sun, Jan 31, 2016 at 5:39 PM, Michael Park wrote:
> Hi all,
>
> The vote for Mesos 0.27.0 (rc2) has passed with the
> following votes.
>
> +1 (Binding)
> --
> Vinod Kone
> Joris Van Remoortere
> Till Toenshoff
>
> +1 (Non-binding)
Done. Welcome!
On Wed, Feb 3, 2016 at 1:07 PM, Erik Weathers wrote:
> Please add me as a contributor in the Mesos JIRA project.
> Apache JIRA username: erikdw
>
> Thanks!
>
> - Erik
>
Please add me as a contributor in the Mesos JIRA project.
Apache JIRA username: erikdw
Thanks!
- Erik
Done. Welcome to the mesos community!
On Wed, Feb 3, 2016 at 11:25 AM, Michael Browning
wrote:
> Hello,
>
> I'd like to be added as a Mesos contributor in JIRA, username "mrbrowning".
>
> Thank you,
> Michael
>
Hello,
I'd like to be added as a Mesos contributor in JIRA, username "mrbrowning".
Thank you,
Michael
A. Thanks Tommy. So I see that the Apache community doesn't release
binary packages, just versioned source code tarballs:
- https://mesos.apache.org/downloads/
I'll follow up with Mesosphere directly, thanks!
- Erik
On Wednesday, February 3, 2016, tommy xiao wrote:
> it belong to meso
it belong to mesosphere concerns, not apache community's scope.
2016-02-03 9:23 GMT+08:00 Erik Weathers :
> I've noticed that in the published mesos packages [1] & docker images [2]
> that the version name isn't simply:
>
>- mesos_0.27.0.ubuntu1404_amd64
>
> Instead it has the form of:
>
>
>Should Docker::inspect return to the caller on timeout, or follow a retry
system like it does with a non-zero exit code?
Yes, this depends how you implement your timeout logic in `after`. If you
discard future and return Failure in `after`, you would not continue the
future chain. But you also cou
Done. Welcome to the community!
On Wed, Feb 3, 2016 at 7:17 AM, Evers Benno wrote:
> Hi,
>
> can you please add me as a contributor in JIRA? My username is "bennoe".
>
> Thanks,
> Benno
Thanks haosdent, that makes sense to allow the inspect command to time out on
its own. Should Docker::inspect return to the caller on timeout, or follow a
retry system like it does with a non-zero exit code? If the latter, should it
retry forever if it times out every time?
Are you suggesting t
Hi,
can you please add me as a contributor in JIRA? My username is "bennoe".
Thanks,
Benno
Hi, Hegner. I think Joly means we change Docker::inspect from
```
s.get().status()
.onAny([=]() { __inspect(cmd, promise, retryInterval, output, s.get());
});
```
to
```
s.get().status()
.after(timeoutSeconds, []() {...})
.onAny([=]() { __inspect(cmd, promise, retryInterval, output,
At the risk of sounding like a complainer: I feel that there is a very high
barrier to entry when trying to help with this project. Perhaps many users are
spoiled by github (myself included) because it's easy to suggest and discuss
changes. At the risk of sounding lazy: I did read the submit-a-p
Thanks Jojy,
I agree that my current patch is not the most ideal solution, as it was
intended as a proof of concept to ensure that it was in fact the timing that
was causing the problems I've been experiencing. Perhaps I didn't make that
clear enough in the JIRA. That is also the reason I haven
Hi,
I have submitted the patch again modifying as per the review comment.
The link is https://reviews.apache.org/r/43032/
Please, have a look on it.
Jie, tim
Can you please shepherd this issue or redirect me to someone else whom I
can ask for shepherding?
Thanks,
Abhishek Dasgupta
On Sunday
But before we switch to version specific docs, I would like to keep the
version when a certain feature was introduced. This information should not
necessarily open the doc, but should be present somewhere, perhaps as a
side note.
On Wed, Feb 3, 2016 at 11:04 AM, Alexander Rojas
wrote:
> I actual
I actually like the idea to have version specific documentation, since it is
kind of the standard way of going about things.
+1 to that.
> On 03 Feb 2016, at 01:53, Neil Conway wrote:
>
> I agree we should remove this text after some period of time has
> passed since that version of Mesos was
Hi, All:
I submit a patch, please take a time to review, if have any problem please
let me know, Thanks!
https://reviews.apache.org/r/43136/diff/1#index_header
[cid:image001.png@01D0E8C5.8D08F440]
Bingqiang Pang 00278970
Distributed Software Lab
Huawei Technologies Co., Ltd.
Email:pangbi
24 matches
Mail list logo