Re: Add s390x support for Mesos CI

I'm not sure if the mentioned matrix is the right one. For ARM we have a different one. Maybe we need another one for the s390x? See: https://github.com/apache/mesos/blob/e79f6cb6ff82add9dfd7484d3f8f8253b76c0e91/docs/committing.md?plain=1#L31

Re: Seeking contributions to fix Mesos website build

It looks like job configuration has changed and it's using GitHub repo now and could not find revision so build does not even start. Now: > Cloning repository https://gitbox.apache.org/repos/asf/mesos-site.git > Avoid second fetch > git rev-parse origin/asf-site^{commit} # timeout=10 > git

Re: Apache Mesos CI on ARM64

@ > 2.4GHz, 16GB RAM and `make -j 4` takes 32 mins on it. > `sudo make check` hangs at the moment, so I cannot tell how much time it > takes. > > Do you think a similar VM could be useful for you ? > For example for running the build and tests once per day. > > Regards, > Mart

Re: Apache Mesos CI on ARM64

pache projects. You may need to contact > Apache Infra team to see how to make use of it. > > Regards, > Martin > > > > > On Thu, 1 Jul 2021, 17:15 Tomek Janiszewski, wrote: > > > > > It looks like we will not get a machine this month but I was poin

Re: Apache Mesos CI on ARM64

It looks like we will not get a machine this month but I was pointed to https://www.oracle.com/cloud/free/#always-free it will be super slow but we can try. wt., 29 cze 2021 o 14:59 Tomek Janiszewski napisał(a): > I can handle that. Let's wait for the machine, then we only need to cha

Re: Apache Mesos CI on ARM64

> > > On Tue, Jun 29, 2021 at 3:26 AM Tomek Janiszewski > wrote: > > > I created a request to Works On ARM > > https://github.com/WorksOnArm/cluster/issues/278 > > If you are interested about history of Mesos on ARM > > https://twitter.com/search?q=ARM%20%4

Re: Apache Mesos CI on ARM64

I created a request to Works On ARM https://github.com/WorksOnArm/cluster/issues/278 If you are interested about history of Mesos on ARM https://twitter.com/search?q=ARM%20%40janiszt pon., 28 cze 2021 o 19:40 Charles-François Natali napisał(a): > Hey, > > I'm not sure who can arrange that -

Re: Apache Mesos CI on ARM64

Hi Unfortunately after the havoc around Mesos future Packet decided to take back ARM CI instance. AFAIk PPC64LE is a runner that calls another job that runs on ARM but now there is no ARM machine for this project so it fails :( https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-ARM/

Re: [BULK]Re: [BULK]Call for active contributors

I'm in I can help with ARM CI, UI and some C++ czw., 4 mar 2021 o 16:04 Thomas Langé napisał(a): > Same for me, I'm available to share my knowledge and actively contribute > to Mesos project. > > Thomas > -- > *From:* Haijiang Chen > *Sent:* Thursday, 4 March 2021

Re: Next Steps

s sound like a good starting point for that >>> discussion, I'll try to answer them from my committer/PMC member >>> perspective when I have enough time. >>> >>> On Thu, 18 Feb 2021 at 12:49, Charles-François Natali >>> wrote: >>> > >>

Re: Next Steps

Moving to attic is making project read only https://attic.apache.org/ https://attic.apache.org/projects/aurora.html czw., 18 lut 2021, 11:56 użytkownik Charles-François Natali < cf.nat...@gmail.com> napisał: > I'm not familiar with the attic but would it still allow to actually > develop, make

[GSoC] Google Summer of Code

Hi It looks like Apache Foundation was selected to Google Summer of Code https://summerofcode.withgoogle.com/organizations/5718432427802624/ Do we plan to submit any project related to Mesos. I was thinking about a project to refresh Mesos UI (catch up with features, upgrade to latest Angular (or

Re: Introducing `support/mesos-build.sh`

użytkownik Ed Vielmetti <e...@packet.net> napisał: > Congratulations Tomek and good job. > > How does build time on this system compare to other systems? > > When you have something packaged for release I'd love to give it a try. > > On Tue, Mar 20, 2018 at 8:54 AM, Tomek Jan

Re: Introducing `support/mesos-build.sh`

> Done. > > > On Mar 20, 2018, at 10:46 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > > Thanks for merging. Can we push this image to dockerhub tagged as > > ubuntu-16.04-arm? Then we will need to update CI configuration to: > > JOBS=

Re: Introducing `support/mesos-build.sh`

MESOS_VERBOSE=1' ../mesos-build.sh or JOBS=16 OS=ubuntu-16.04-arm BUILDTOOL=autotools COMPILER=gcc CONFIGURATION='--disable-java --disable-python --disable-libtool-wrappers' ENVIRONMENT='GLOG_v=1 MESOS_VERBOSE=1' ./support/mesos-build.sh pon., 19 mar 2018 o 16:24 użytkownik Tomek Janiszewski <j

Re: Introducing `support/mesos-build.sh`

Dockerfile for ARM with CMake support https://reviews.apache.org/r/66138/ pon., 12 lut 2018 o 15:41 użytkownik Tomek Janiszewski <jani...@gmail.com> napisał: > How can I use it for our ARM CI? > > JOBS=16 OS=arm64v8/ubuntu:16.04 ./support/mesos-build.sh > + set -e &

Re: [MoA] Update Jenkins ARM configuration

disable-java%20--disable-python,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1%20%20MESOS_TEST_AWAIT_TIMEOUT=60secs,label_exp=arm/442/display/redirect?page=changes > pt., 16.03.2018, 19:17 użytkownik Tomek Janiszewski <jani...@gmail.com> napisał: > Thanks, I hope this fix ARM builds > >

Re: [MoA] Update Jenkins ARM configuration

Thanks, I hope this fix ARM builds pt., 16.03.2018, 18:35 użytkownik James Peach <jpe...@apache.org> napisał: > > > > On Mar 16, 2018, at 8:27 AM, James Peach <jpe...@apache.org> wrote: > > > > > > > >> On Mar 16, 2018, at 5:11 AM, Tomek Jan

[MoA] Update Jenkins ARM configuration

Hey Who can edit Jenkins configuration? I noticed we run tests with the wrong configuration (we miss --disable-libtool-wrappers') it should be CONFIGURATION='--disable-java --disable-python --disable-libtool-wrappers' Can you fix it, please? https://issues.apache.org/jira/browse/MESOS-7500

Re: Introducing `support/mesos-build.sh`

How can I use it for our ARM CI? JOBS=16 OS=arm64v8/ubuntu:16.04 ./support/mesos-build.sh + set -e + set -o pipefail + : arm64v8/ubuntu:16.04 + : autotools + : gcc + : '--verbose --disable-libtool-wrappers' + : 'GLOG_v=1 MESOS_VERBOSE=1' + : 16 ++ git rev-parse --show-toplevel +

Looking for shepherd

I need someone to review and merge this change https://reviews.apache.org/r/65569/ It should fix ARM tests.

Re: Flaky executor tests on ARM

użytkownik Tomek Janiszewski <jani...@gmail.com> napisał: > Thanks, I'll take a look at this after the weekend. > > pt., 24.11.2017, 00:35 użytkownik Alex Rukletsov <a...@mesosphere.com> > napisał: > >> Might be libtool wrappers. Have a look at [1] and c

Re: Flaky executor tests on ARM

ttps://github.com/apache/mesos/commit/d863620e5cb82b7f22cade0da0a0d18afbdf9136 > [3] > > https://github.com/apache/mesos/commit/74121798f24fca372180b8c4bc00b4df07d46240 > [4] > > https://github.com/apache/mesos/commit/cd516ab65b03045dba7f1cbfd40e72a1d5267539 > > On Thu, N

Flaky executor tests on ARM

Hi I found following 5 tests are flaky. They fail when run together but pass alone. CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled DefaultExecutorCheckTest.CommandCheckDeliveredAndReconciled DefaultExecutorCheckTest.CommandCheckStatusChange

Re: .deb packages of mesos releases

> Well that's not really a problem, I can provide 1.1.x packages if your > > interested in. > > > > Regards, Adam. > > > > On September 8, 2017 10:47:23 AM GMT+02:00, Tomek Janiszewski > > <jani...@gmail.com> <jani...@gmail.com> wrote: > >&

Re: Sandbox life cycle /age

=.2 --gc_delay=2hrs”. Is there any downside of the > going with very low GC delay? > > Thanks, > Venkat > > > > On Oct 26, 2017, at 4:28 PM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > >> gc_delay * max(0.0, (1.0 - gc_disk_headroom - disk usage))

Re: Sandbox life cycle /age

> gc_delay * max(0.0, (1.0 - gc_disk_headroom - disk usage)) *Example:* gc_delay = 7days gc_disk_headroom = 0.1 disk_usage = 0.8 7 * max(0.0, 1 - 0.1 - 0.8) = 7 * max(0.0, 0.1) = 0.7 days = 16 h 48 min Can you show some logs containging information about GC? pt., 27 paź 2017 o 00:43 użytkownik

Re: [Proposal] Mesos on ARM

side Mesosphere for that. > > On 26 September 2017 at 14:39, Tomek Janiszewski <jani...@gmail.com> > wrote: > >> Hi all >> >> I'd like to propose to add ARM64 support in Mesos. Currently, the only >> Agent can run on ARM but it's not officially supported. This m

[Proposal] Mesos on ARM

Hi all I'd like to propose to add ARM64 support in Mesos. Currently, the only Agent can run on ARM but it's not officially supported. This means build failures on ARM are not considered as a bug. I know there were a couple of tries to run Mesos on ARM (mostly on Raspberry PI) but this process is

Re: protbuf to json not compatible

I have a similar problem with protobuf and json. In my case numbers were incorrectly unmarshaled. Here is an issue https://issues.apache.org/jira/browse/MESOS-970 and review https://reviews.apache.org/r/50851/ czw., 23.03.2017, 09:54 użytkownik Olivier Sallou napisał: >

Re: MESOS-7233: Looking for shepherd

OK, I discovered it myself, this test uses absolute paths. @Benjamin You were right it's not backward compatible. I'll work on this. mesos 1.3.0 framework failed with mesos 1.3.48291 master and mesos 1.3.0 agent pt., 17 mar 2017 o 13:44 użytkownik Tomek Janiszewski <jani...@gmail.

MESOS-7233: Looking for shepherd

Hi I'm looking for shepherd for MESOS-7233 — Use varint comparator in replica log. JIRA: https://issues.apache.org/jira/browse/MESOS-7233 Review: https://reviews.apache.org/r/48291/ Thanks Tomek

Re: mesos git commit: Upgrade leveldb to 1.19.

lying the patch to evaluate the write performance. > > > > We probably should add a BENCHMARK test to our test suite so that this > can > > be automated. For instance, initialize a replicated log with a single > > replica, and perform a bunch of writes with ran

Re: mesos git commit: Upgrade leveldb to 1.19.

Test summary and comparison between 1.4 and 1.19 https://docs.google.com/document/d/1fv2OMvH6hVm6waacOejSrTJwUuDQeXlqqPDZjBmbcKU/edit#heading=h.ewfisffoslz3 pon., 20 lut 2017 o 11:28 użytkownik Jie Yu napisał: > Do we have some benchmark numbers to vet this change? We have

Re: Mesos-go status

lly place the fork into that package namespace > for you. > > -Jake > > > [1]: https://glide.readthedocs.io/en/latest/glide.yaml/ > > On Fri, Feb 3, 2017 at 6:54 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > I know but I'd prefer to avoid to double wor

Re: Mesos-go status

xiao <xia...@gmail.com> napisał: > you can forked it>>> > > 2017-02-03 18:43 GMT+08:00 Tomek Janiszewski <jani...@gmail.com>: > > > Hi > > > > What is the status of https://github.com/mesos/mesos-go It looks like > it's > > abando

Mesos-go status

Hi What is the status of https://github.com/mesos/mesos-go It looks like it's abandoned. Useful pull requests are awaiting merge and issues need to be fixed. Who is the owner of this repo? I can volunteer to continue this project especially the executor module. Thanks Tomek

Re: Command healthcheck failed but status KILLED

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 <gas...@mesosphere.io> napisał: > On Mon, Dec 12, 2016 at 12:47 PM, Tomek Ja

Re: [webui] Started show wrong time

free to post a > patch > if you have idea for it. > > On Wed, Dec 14, 2016 at 7:25 AM, Alex Rukletsov <a...@mesosphere.com> > wrote: > > > This looks like a bug. Tomek, could you please file a JIRA? > > > > On Tue, Dec 13, 2016 at 1:02 PM, Tomek J

[webui] Started show wrong time

Hi When task has enabled Mesos healthcheck start time in UI can show wrong time. This happens because UI assumes that first status is task started [0]. This is not always true because Mesos keeps only recent tasks statuses [1] so when healthcheck updates tasks status it can override task start

Re: Command healthcheck failed but status KILLED

<a...@mesosphere.com> napisał: > Technically the task hast not failed but was killed by the executor > (because it failed a health check). > > On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > Hi > > > > What is d

Command healthcheck failed but status KILLED

Hi What is desired behavior when command health check failed? On Mesos 1.0.2 when health check fails task has state KILLED instead of FAILED with reason specifying it was killed due to failing health check. Thanks Tomek

Re: Mesos V1 Operator HTTP API - Java Proto Classes

I suspect jar is deprecated and includes only old API used by mesoslib. The goal is to create HTTP API and stop supporting native libs (jars, so, etc). I think you shouldn't use that jar in your project. wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan < vijikar...@yahoo.com> napisał: >

Re: Which service discovery mechanism could be used with mesos?

Hi Take a look at this SO answer http://stackoverflow.com/a/37822870/1387612 Service discovery could be Mesos agnostic by implementing registration/quering mechanism in application. On the other hand using discovery service that integrates with Mesos will reduce in application code. If you need

Re: Features missing in the webui

At MesosCon EU we were working on bringing Maintenance Mode to the UI. Maintenance of nodes will be presented in a table. Code is on github but need some tweaks and tests with large maintenance json. I'll prepare patch shortly (when github DDoS will be over).

Re: Shepherd for MESOS-970

osd...@gmail.com> napisał: > Hi, @janiszt. I remember you mentioned it has problems when > use test-upgrade.py to test upgrading from leveldb 1.4 to leveldb 1.19. Is > it still a problem now? > > On Mon, Sep 19, 2016 at 1:28 AM, Tomek Janiszewski <jani...@gmail.com> > wrote

Shepherd for MESOS-970

Hi I'm looking for shephard for: https://issues.apache.org/jira/browse/MESOS-970 Patch: https://reviews.apache.org/r/51053/ Best Tomek

Re: How could Mesos work with docker?

Hi Docker support is described here http://mesos.apache.org/documentation/latest/docker-containerizer/ Best Tomek wt., 9.08.2016 o 16:04 użytkownik Yu Wei napisał: > Hi guys, > > I start learning mesos. > > How could mesos work with docker? Is there any document about

Re: Protobuf long number JSON serialisation

Created a patch https://reviews.apache.org/r/50851/ Looking for shepherd. pt., 5.08.2016 o 09:49 użytkownik Tomek Janiszewski <jani...@gmail.com> napisał: > I reported issue for this https://issues.apache.org/jira/browse/MESOS-5995 > > pt., 5.08.2016 o 02:35 użytkownik

Re: Protobuf long number JSON serialisation

> > Thanks for reporting this. Looks like a bug in our JSON -> Protobuf > > parsing code. Mind filing a JIRA issue? > > > > -anand > > > > > > > On Aug 4, 2016, at 2:04 PM, Tomek Janiszewski <jani...@gmail.com> > wrote: > >

Protobuf long number JSON serialisation

Hi I have a problem with HTTP API. Proto2 does not specify JSON mappings but Proto3 does and it recommend to map 64bit numbers as a string. Unfortunately Mesos does not accepts strings in places of uint64 and return 400 Bad Request error Failed to convert JSON into Call protobuf: Not expecting a

Re: Patch for website

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

Re: Mesos Frameworks in any language

This languages has bindings to native Mesos library that is used to communicate with Mesos. But since we have HTTP API there is no need to link with this lib. We should update doc and link app frameworks development page with: http://mesos.apache.org/documentation/latest/scheduler-http-api/

Re: [Action Required] Stale Reviews

How about running CI on all reviews. If patch is stale it probably can't be applied, CI will post bad patch and if nobody do any action on that review we can close it. śr., 29.06.2016, 18:26 użytkownik Joris Van Remoortere napisał: > Hello developers, > > Over the last year

Re: Proposal: move content in Wiki to docs in code repo

It's working. Thanks czw., 9.06.2016 o 17:06 użytkownik Vinod Kone <vinodk...@apache.org> napisał: > Done. Let me know if you have edit access now. > > On Thu, Jun 9, 2016 at 11:01 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > @Vinod I've just create

Re: Proposal: move content in Wiki to docs in code repo

i.apache.org > > On Thu, Jun 9, 2016 at 4:48 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > >> @Jie could you sent me a markup from confluence editor. I have no edit >> access and it will be easier to work with markup than scraping web page to >> get data

Re: Proposal: move content in Wiki to docs in code repo

@Jie could you sent me a markup from confluence editor. I have no edit access and it will be easier to work with markup than scraping web page to get data. czw., 9.06.2016 o 09:37 użytkownik Tomek Janiszewski <jani...@gmail.com> napisał: > I'll post patches by the end of the week

Re: Proposal: move content in Wiki to docs in code repo

I'll post patches by the end of the week. czw., 9.06.2016 o 02:23 użytkownik Jie Yu napisał: > Great! Looks like we have a consensus here! > > Tomek, you mentioned that you're interested in helping the move. Thank you > so much. Can you start with moving the following wiki

Re: [C++11] Please use `nullptr`!

No, we left it untouched. I prepared simple check that could be reviewed here https://reviews.apache.org/r/48320/ It's far from perfect, but works in most cases. The real solution will be using clang-modernize. Best Tomek wt., 7.06.2016 o 01:15 użytkownik Benjamin Mahler

Re: Proposal: move content in Wiki to docs in code repo

+1 For a long time I didn't knew that wiki exists. It's hidden from a new users and search engines - I remember only one place where it's linked in docs. I can help with move. pon., 6.06.2016, 20:29 użytkownik Jie Yu napisał: > Hi folks, > > I am proposing moving our

Re: Completed executors presented as alive

has > bug when > reap task status. Could you find something in the executor stdout/stderr ? > > On Sat, Jun 4, 2016 at 6:08 PM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > Thanks. I just manually find that executor pid and killed it. Any idea > why >

Re: Completed executors presented as alive

s/blob/master/docs/executor-http-api.md#shutdown > to shutdown it. > If it is other type executor, seems don't have a api to shutdown executor > as I know. Not sure whether kill the executor in > Agent could resolve your problem or not. > > On Fri, Jun 3, 2016 at 4:33 PM,

Re: Completed executors presented as alive

c- > 13:33:35.918143 [status_update_manager.cpp:824] Checkpointing ACK for status update TASK_KILLED (UUID: eba64915-7df2-483d-8982-a9a46a48a81b) for task service.a3b609b8-27ec-11e6-8044-02c89eb9127e of framework f65b163c-0faf-441f-ac14-91739fa4394c- ... > 13:33:39.031054 [slave.cpp:2643]

Re: Completed executors presented as alive

completed executors only exists > in completed_frameworks.completed_executors > or frameworks.completed_executors in my side. > > In your side, does completed_executors exists in any other fields? > > On Thu, Jun 2, 2016 at 5:39 PM, Tomek Janiszewski <jani...@gmail.com> > wrote

Completed executors presented as alive

Hi I'm running Mesos 0.28.0. Mesos slave(1)/state endpoint returns some completed executors not in frameworks.completed_executors but in frameworks. executors. Is it normal behavior? How to force Mesos to move completed executors into frameworks.executors? Thanks Tomek

[WEBSITE] Readme update

Hi I think website readme is out of date. 1. It doesn't mention mesos-website-container 2. support/generate-help-site.py does not exists Am I right? How to generate full site (with

Re: [WEBSITE] Website refresh

@apache.org> wrote: > > > Great. Can you file tickets for these and submit patches? I can help > commit > > them. Would be great if people with front-end experience can review the > > changes though. > > > > On Tue, May 17, 2016 at 1:23 PM, Tomek Janiszewski <

Re: [WEBSITE] Website refresh

Tables still need scrolling but IMO it's OK There could be other issues I haven't noticed, but on the first sight making site mobile friendlier doesn't look hard. wt., 17.05.2016 o 21:19 użytkownik Vinod Kone <vinodk...@apache.org> napisał: > On Tue, May 17, 2016 at 10:18 AM, To

Re: [WEBSITE] Website refresh

In short term we could make it mobile friendly. Also first page could be less ascetic more like http://concord.io/ wt., 17.05.2016, 18:55 użytkownik haosdent napisał: > > Is there anything else we could do in the short-term? > > Add some case studies? May just a link to

Re: mesos website workgroup

Count me in. Tomek wt., 17.05.2016, 07:49 użytkownik Abhishek Dasgupta < a10gu...@linux.vnet.ibm.com> napisał: > I would be very much interested. I have some front-end experience as > well. Please, include me too. > > On মঙ্গলবার 17 মে 2016 02:32 পূর্বাহ্ণ, Vinod Kone wrote: > > Hi guys, > > >

Re: Running Mesos agent on ARM (Raspberry Pi)?

Cool. Did you hit any trubles with that setup? pt., 13.05.2016, 03:13 użytkownik Sharma Podila napisał: > We have Mesos agents running on Pi3's taking tasks from master running on > a Linux laptop. > > https://twitter.com/aspyker/status/730924571440779264 > > More info to

Looking for Shepherd for MESOS-2201

Hi Can anyone help shepherd MESOS-2201 – Fixed replica log restore tests. This issue is first step to upgrade leveldb. https://issues.apache.org/jira/browse/MESOS-2201 https://reviews.apache.org/r/47161/ Thanks Tomek

Re: Running Mesos agent on ARM (Raspberry Pi)?

Current master version should build on Pi3 but there still could be a problem with leveldb. wt., 3.05.2016 o 16:40 użytkownik Andreas Fritzler < andreas.fritz...@gmail.com> napisał: > Did anybody try to build and run Mesos on a Raspberry Pi3? Will that work > out of the box (due to the 64bit

Re: Looking for Shepherd for MESOS-5263

lude > #include > > int main(int argc, char const *argv[]) > { > std::cout << __NR_pivot_root << std::endl; > return 0; > } > ``` > > > On Wed, Apr 27, 2016 at 3:24 AM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > Lo

Looking for Shepherd for MESOS-5263

Hi, Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-5263? It's similar to https://issues.apache.org/jira/browse/MESOS-5121 and could be resolved in the same manner or it could be done in a way that'll support other platforms as well. Thanks Tomek

Re: Running Mesos agent on ARM (Raspberry Pi)?

; fix was to change %lu to %llu or something close to that. The stack trace >>>> when Mesos crashes should tell you. If you’re lucky enough to have an RPi3, >>>> this may not be necessary. >>>> >>>> Also, if you compile on the RPi make sure to cre

Re: Running Mesos agent on ARM (Raspberry Pi)?

As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR there was a problem only with master, agents runs smoothly (or pretend to). To run it on RPi you need to compile it for ARM. Easy but long solution is to compile it on rpi. Quick but a little bit harder cross compile it on

Re: Vote on #MesosCon proposals, deadline Friday March 25

@David Do you have results? pon., 21.03.2016 o 14:39 użytkownik David Greenberg napisał: > No, sorry--we'll collect the votes on Friday. > > Thanks, > David > > On Sun, Mar 20, 2016 at 9:01 PM Darren Haas wrote: > >> Hi David, >> >> We could always

Re: [jira] [Created] (MESOS-4993) FetcherTest.ExtractZipFile assumes `unzip` is installed

My bad. Fix is ready for review https://reviews.apache.org/r/45134/diff/2 - Tomek pon., 21.03.2016 o 22:03 użytkownik Benjamin Mahler napisał: > +jie, Tomasz > > Looks like this new test needs a filter. Can one of you follow up with a > fix? > > On Mon, Mar 21, 2016 at

Re: Contributor request

did you use (jani...@gmail.com does appear to be in the list of > registered users). > > Artem. > > On Fri, Mar 11, 2016 at 6:48 AM, Tomek Janiszewski <jani...@gmail.com> > wrote: > > > Please add me as contributor in the Mesos JIRA project. My Apache JIRA's > > username: janisz > > > > Thanks! > > >

Unzip should work in non interactive mode

Hi Consider situation when deployed zip file is malformed and contains duplicated files . When fetcher downloads malformed zip file, that contains duplicated files (e.g., dist zips generated by gradle) and try to uncompress it, deployment hang in staged phase because unzip prompt if file should

Re: Unzip should work in non interactive mode

Patch is ready https://reviews.apache.org/r/45057/diff/1/ pt., 18.03.2016 o 16:43 użytkownik Jie Yu <yujie@gmail.com> napisał: > I can shepherd it. Do you have a patch ready? > > - Jie > > On Fri, Mar 18, 2016 at 3:13 AM, Tomek Janiszewski <jani...@gmai

Re: GSoC query

Hi Unfortunately, I couldn't attend the meeting. I prepared GSoC proposal (Mesos on ARM) that I want submit to Apache Foundation https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit?usp=sharing Is anyone interested in collaboration/mentoring? Thanks Tomek pt.,

Contributor request

Please add me as contributor in the Mesos JIRA project. My Apache JIRA's username: janisz Thanks!

Re: GSoC query

Hi I also consider participating in GSoC. It will be great if shepard/mentors pick some issues that could be done during GSoC and bring value for community. Personally I'd like to work on https://issues.apache.org/jira/plugins/servlet/mobile#issue/MESOS-2021. Best Tomek czw., 3 mar 2016, 20:02

Re: Configuration file?

Hi all It looks simple for the first sight. Marco, I can work on it. - Tomek wt., 24 lis 2015, 17:49 Marco Massenzio użytkownik napisał: > Thank you for asking :) > > The idea is pretty simple (and not even original, it's the "Facade > pattern"): essentially we would