I've pushed 4 review requests for this issue:
https://reviews.apache.org/r/49936/
https://reviews.apache.org/r/49937/
https://reviews.apache.org/r/49938/
https://reviews.apache.org/r/49939/
@Benjamin: I'm not sure I understand what you mean. Some of current Timers
have `statistics` to calculate
Hi Joris,
For `2x` number, can you please show more detail for how did you do and
evaluate the test? How did you compare the result? Did you have any test
code to share?
Thanks,
Guangya
On Mon, Jul 11, 2016 at 6:05 PM, Klaus Ma wrote:
> Hi Joris,
>
> For `Scalars`,
This doesn't look like a "Bug" (there are a bunch of other tickets that are
misclassified). Please be sure to set the appropriate "issue type". :)
Can you go through your tickets and update the types?
-- Forwarded message --
From: Alex Clemmer (JIRA)
Date: Fri,
I just ran a website update, you should see it now if you force a refresh.
On Mon, Jul 11, 2016 at 2:26 PM, Tomek Janiszewski
wrote:
> Page need to be manually generated and published.
>
> pon., 11.07.2016, 22:59 użytkownik Rich Bowen napisał:
>
> >
> >
>
Page need to be manually generated and published.
pon., 11.07.2016, 22:59 użytkownik Rich Bowen napisał:
>
>
> On 2016-07-07 12:36 (-0400), "Rich Bowen" wrote:
> >
> >
> > On 2016-07-07 11:58 (-0400), Vinod Kone wrote:
> > > Thanks
On 2016-07-07 12:36 (-0400), "Rich Bowen" wrote:
>
>
> On 2016-07-07 11:58 (-0400), Vinod Kone wrote:
> > Thanks Rich! The easiest is to just send a PR to our github repo:
> > https://github.com/apache/mesos
>
>
> Excellent. Will do.
>
>
I see
Have you considered introducing 'histograms' rather than 'timers'? Our
Timers are just a special case of a histogram. For example, you could have
a histogram of response sizes.
On Fri, Jul 8, 2016 at 3:32 PM, Tuan-Anh Hoang-Vu
wrote:
> Hi all,
>
> I've finished implementing
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/138
---
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
Jay, I'll shepherd the two detector/contender/network module changes.
On Mon, Jul 11, 2016 at 2:44 AM, Jay JN Guo wrote:
>
> Shuai,
>
> I think you are right. AFAIK, replicated_log interacts with zk in only
> following two ways:
>
> 1) replicated_log creates znode and
ASF CI: Yes that would be the goal.
Frequency: There is a limit to the number of submissions for the free OSS
Coverity scan: https://scan.coverity.com/faq#frequency. Happy to run that
daily, though...
On Mon, Jul 11, 2016 at 7:28 PM, Vinod Kone wrote:
> On Mon, Jul 11,
GitHub user yongtang opened a pull request:
https://github.com/apache/mesos/pull/138
Added Yong Tang to contributors list.
This PR added Yong Tang to contributors list.
You can merge this pull request into a Git repository by running:
$ git pull
Thanks Vinod! Done.
On Mon, Jul 11, 2016 at 10:31 AM, Vinod Kone wrote:
> Welcome to the community!
>
> Mind sending a PR to add yourself to
> https://github.com/apache/mesos/blob/master/docs/contributors.yaml ?
>
> On Mon, Jul 11, 2016 at 10:28 AM, Lawrence Wu
>
Welcome to the community!
Mind sending a PR to add yourself to
https://github.com/apache/mesos/blob/master/docs/contributors.yaml ?
On Mon, Jul 11, 2016 at 10:28 AM, Lawrence Wu wrote:
> Hi, I will be working on https://issues.apache.org/jira/browse/MESOS-5376.
On Mon, Jul 11, 2016 at 6:35 AM, Jörg Schad wrote:
> b) Furthermore, we will set up a weekly Coverity build for HEAD (and maybe
> we should also consider runs for RCs and releases).
>
I'm guessing this will be on ASF CI? Also, why weekly instead of
continuously?
Hi, I will be working on https://issues.apache.org/jira/browse/MESOS-5376.
idownes already added me as a contributor but I'm sending this email just
for reference.
None of the stable builds have SSL yet. The first SSL-enabled stable build
will be 1.0.0. Sorry for the confusion.
Kapil
On Mon, Jul 11, 2016 at 1:03 PM, Zhitao Li wrote:
> Hi Kapil,
>
> Do you mean that the stable builds from
> http://open.mesosphere.com/downloads/mesos
Hi Kapil,
Do you mean that the stable builds from
http://open.mesosphere.com/downloads/mesos is using the new configuration?
On Sun, Jul 10, 2016 at 10:07 AM, Kapil Arya wrote:
> The binary rpm/deb packages can be found here:
>
BEGIN:VCALENDAR
METHOD:REPLY
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
BEGIN:VCALENDAR
METHOD:REPLY
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
Folks,
We're working on some Mesos features that will allow frameworks to
control how partitioned tasks are handled [1]. As part of designing
how this will work, I'd love to hear from users and framework
developers about they handle partitioned tasks/agents. Specifically:
(a) Have you enabled
After Coverity upgraded their build system this weekend (
https://twitter.com/CoverityScan/status/751106512097914880) we can finally
use Coverity again for static code analyses!
a) There are many non-relevant issues right now (but Coverity is able to
learn and ignore them for future builds),
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/136
---
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/137
---
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
Done. Welcome!
On Sat, Jul 9, 2016 at 1:02 AM, Tim Harper wrote:
> I've submitted and worked on this issue:
> https://issues.apache.org/jira/browse/MESOS-5824 <
> https://issues.apache.org/jira/browse/MESOS-5824>
>
> Per the instructions <
>
Hi Joris,
For `Scalars`, yes, it's also dynamic allocated in
`Resources::mutable_scalar()`.
For `2x` number, do you have any patch to share? Tested cases this
afternoon: add resources including 100 roles (1 CPU for each); the
performance is downgrade a lot; so I agree with you to improve some
Github user jmlvanre commented on the issue:
https://github.com/apache/mesos/pull/127
It will get added to the website the next time it gets published.
We do that pretty regularly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20160714T20Z
DTEND:20160714T21Z
DTSTAMP:20160711T011909Z
ORGANIZER;CN=mach sagel:mailto:machsagel2...@gmail.com
Github user gggina commented on the issue:
https://github.com/apache/mesos/pull/127
Thanks.
How does this get added to
http://mesos.apache.org/documentation/latest/frameworks/ ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
+Dev
Hey Klaus,
Using Stout's `Optional` to represent the `optional` concept of a message
in protobuf is definitely a step in the right direction.
Regarding your comment in slack yesterday: From my version of the protobuf
generated code there definitely is dynamic allocation even for scalars.
29 matches
Mail list logo