EnumerateFileSystemInfos uses EnumerationOptions

Summary of the Pull Request
Changed EnumerateFileSystemInfos to EnumerationOptions we don't have to catch the exceptions ourself. See #6922 for more information.
PR Checklist

[x] Applies to #6922
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #6922

Info on Pull Request
Other querying of fileSystem.
Validation Steps Performed
It doesn't break any tests.
Suggested tags

Product-Launcher

@crutkas is there a way to request a review for a PR myself? Notifying a bot or something?
Anyway this can be reviewed :)

The code looks good to me.  I just haven't had a chance to test it.  I'm okay with these changes going in if someone else can verify they've tested it.   If not I'll try to get to this later today.

@P-Storm Typing C:\ doesn't list down the folders on this PR. It is working fine on master. I have attached screenshots below :
This PR

Master

Apperently I have made an error with MatchType. This will search the Folders en Files again as it was.


CSV Namespace and Plugins

Here's an initial shim for #6
Please confirm that I've got this started properly. I think the template file should be good to go.
The tool itself is just a renamed clone from the network name space. I plan to write a tool that parses the CSV and pushes out each row as a message to RabbitMQ.

@pbronez structure and template looks great.  just update the app and dockerfile for the specific of csv as you mention and should be good to go.  thanks!

@pbronez looks good, is this ready to go, or still in progress?

Should be feature-complete, but haven't tested it yet. I pushed up to my fork so I could load it into my local vent instance. I'll ping you when I've confirmed it actually runs.

as an aside, once this is merged, it would probably be a good idea to update this: https://github.com/CyberReboot/vent/blob/master/README.md to be more inclusive than just PCAPs.

Per #26 , new plugins need to be on the Master Branch. I'll create a new PR.


image error in published main file display

The Issue
Thumbnail is not displayed correctly upon selecting published item, whereas is shown correctly under all published items
Steps to reproduce

Publish content
Check under Published, thumbnail is correct
Click said published item, error appears, no thumbnail :(

Expected behaviour
Thumbnail should be displayed as per screenshot "1"
Actual behaviour
Thumbnail is not displayed tho correctly published, as per screenshot "2"
System Configuration

LBRY Daemon version: daemon (lbrynet)    0.10.0
LBRY App version: Version 0.10.0 (<IP_ADDRESS>7)
LBRY Installation ID: 87CKm9XupPBoHgD3yGsG6pPayX9F2q2WXjVTDKRDUL5B5Xi6x6mMpKhAAkMHXscCHa
Operating system:  macOS sierra

Anything Else
Reported for user @heymattsokol in Slack
-these uploads are .zip files, not videos
-each zip contains the mp3s of the album thumbnail is a .jpeg
Screenshots

oops

We're redesigning our UI, and it's possible that this issue is already fixed. @alexliebowitz is our UI expert. He'll take a look to make sure.

Yep, looks like this is working in the current UI (quite possibly thanks to your report). Thanks!


Playbooks typo

Just a minor documentation typo

Hello @ShrootBuck,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Add generic aggregate process

Based on aggregate_temporal.
Origin of the discussion: https://gitlab.ogc.org/ogc/T20-GDC/-/issues/32#note_34824 (likely access restricted)
Rendered version:

https://gitlab.ogc.org/ogc/T20-GDC/-/issues/32#note_34824 (likely access restricted)

Indeed I don't have access


Compatability with capybara 2.8

Hi!
Much appreciate all your work on this!
The Capybara gem was updated to 2.8 which the current version of capybara-webkit does not support, which means capybara-webkit will be downgraded to the very old version 1.1.
Please update this gem to support the latest Capybara version.
Best regards,
Thomas.

The Capybara gem was updated to 2.8 ..

The latest version of capybara is now 2.9.2, as of 2016-09-29.
Are there breaking changes in 2.8 or 2.9, or is the gemspec constraint just a precaution?
s.add_runtime_dependency("capybara", ">= 2.3.0", "< 2.8.0")

@mhoran You were the last one to edit that line of the gemspec. Do you happen to know? Thanks!

capybara-webkit is not yet compatible with Capybara 2.8, due to a change in the API. Unfortunately we're currently blocked on adding support due to broken CI, but that's being worked on.

@mhoran  the old frame API will still be used by capybara if the new one isn't implemented, so technically capybara-webKit should work fine with 2.8, 2.9, and the soon to come 2.10 which are all mainly flexibility in finders/matchers/selectors releases

Thanks for the clarification, @twalpole. I'm still hesitant to release the version lock without CI.
On October 4, 2016 4:24:32 PM EDT, Thomas Walpole<EMAIL_ADDRESS>wrote:

@mhoran  the old frame API will still be used by capybara if the new
one isn't implemented, so technically capybara-webKit should work fine
with 2.8, 2.9, and the soon to come 2.10 which are all mainly
flexibility in finders/matchers/selectors releases
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/thoughtbot/capybara-webkit/issues/937#issuecomment-251502185

--
Sent from my mobile device.

I'm hesitant to release the version lock without CI.

CI is passing now, as of https://github.com/thoughtbot/capybara-webkit/commit/b22df5fe67bfae0f26d7ccf97f55ee48ab7ca8fb
Would a PR that updates the tests to run against the latest capybara-webkit help?  As of today, the latest is 2.10.1.

I just bumped the capybara dependency on the bump-capybara branch. Unfortunately there are two failures -- one to lack of implementation of the new frame API, and another due to an incompatible behavior on closed frames with the other drivers. Likely the second issue is easily fixed, but I haven't had the time to look into the new frame API.

Thanks for starting a branch, Matthew.

.. there are two failures ..

For convenience, here are those two failures, copied from https://travis-ci.org/thoughtbot/capybara-webkit/jobs/172622648
1) Capybara::Session webkit #within_frame works if the frame is closed
     Failure/Error: @session.within_frame 'parentFrame' do
     Capybara::Webkit::InvalidResponseError:
       Already at parent frame.
     # ./lib/capybara/webkit/browser.rb:305:in `check'

  2) Capybara::Session webkit #within_frame should support the driver #switch_to_frame api
     Failure/Error: expect {
       expected no Exception, got #<Capybara::NotSupportedByDriverError: Capybara::Driver::Base#switch_to_frame> with backtrace:
         # /home/travis/.rvm/gems/ruby-2.1.9/gems/capybara-2.10.1/lib/capybara/driver/base.rb:56:in `switch_to_frame'

Would it be helpful if I create two separate issues? I don't know much about the frame API, and that's the only thing I could think of to help with :)

@jaredbeck Let's just track progress in this single issue, since the first failure is really all that needs to be addressed immediately. The second failure is an implementation detail, and we can just skip it for now to get the tests green.

@mhoran 👋  Have you looked at this recently?

Hey @iwz. I've not. It should be a simple fix, but I've not had the time to check it out.

Ok, I might take a stab on my next investment day. Thanks!

I offer my sincere and least-naggy encouragements since I need to upgrade to Capybara 2.11 and would just like to mention that the latest released version of Capybara is actually 2.11 so the lock on < 2.11 in this commit is not quite up-to-date.
AFAIK there are no additional breaking changes in 2.11 compared to 2.10: https://github.com/teamcapybara/capybara/blob/master/History.md#version-2110

capybara-webkit 1.12.0 has been released, which supports Capybara 2.8+.


feat: remove console.* eslint rule

Description

Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

Risk

Testing

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #2448   👈

This comment was auto-generated by Graphite.


jnp.broadcast_to is incompatible with masking

I want to call some vectorized functions from a masked function.
These functions commute with masking: f(x)[mask] == f(x[mask]) where mask = np.s_[:d0, :d1, ..., :dn]
But, I don't think JAX needs to know this.
Anyways, vectorize crashes when broadcasting a masked array:
import jax.numpy as jnp
import numpy as np

# Vectorized function, jnp.diag for simplicity:
diag3d = jnp.vectorize(jnp.diag, signature='(c,c)->(c)')
x = jnp.arange(8).reshape((2, 2, 2))
y = diag3d(x)
# Try calling it with masked inputs:
diag3d_masked = jax.mask(diag3d, in_shapes=['(t, c, c)'], out_shape='(t, c)')
np.testing.assert_allclose(diag3d_masked([x], dict(t=2, c=2)), y)

I get this error:
/usr/local/lib/python3.6/dist-packages/jax/numpy/vectorize.py in wrapped(*args)
    237       vec_shape = full_shape[-arg.ndim:] if arg.ndim else ()
    238
--> 239       vec_arg = np.broadcast_to(arg, vec_shape)
    240       vec_args.append(vec_arg)
    241

/usr/local/lib/python3.6/dist-packages/jax/numpy/lax_numpy.py in broadcast_to(arr, shape)
   1061   """Like Numpy's broadcast_to but doesn't necessarily return views."""
   1062   arr = arr if isinstance(arr, ndarray) else array(arr)
-> 1063   shape = tuple(map(int, shape))  # check that shape is concrete
   1064   arr_shape = _shape(arr)
   1065   if arr_shape == shape:

/usr/local/lib/python3.6/dist-packages/jax/interpreters/masking.py in __int__(self)
    209
    210   def __int__(self):
--> 211     assert self.is_constant
    212
    213     return int(next(iter(self.values())))

AssertionError:

It looks like may be more directly an incompatibility between broadcast_to and masking.

I think that particular issue was one of the missing masking features added in the rolled-back https://github.com/google/jax/pull/2017 (cc @j-towns), though there may be further issues after broadcast_to is fixed.

(ping @JuliusKunze who wrote #2017) I think that's correct, as it happens @mattjj messaged me yesterday about fixing up and re-merging that pr, so we may be able to fix this issue quite quickly.

Once https://github.com/google/jax/pull/2800 is merged, I can create another PR that should fix masking for most common primitives. The code is currently parked in https://github.com/JuliusKunze/jax/tree/masking-pcnn and needs some heavy updating to be compatible with the current jax version.

jax.mask is long gone. Closing as stale.


Fixing code continuity error.

Parsing error attributes in function declaration to match run and json functions

Beautiful. Thanks!


This page is showing the documentation code rather than the intended formatted output

The page is showing most of the content as HTML code rather than its intended formatted output.  It looks correct in GitHub, but not on docs.microsoft.com

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b1b01ebb-0239-2f68-9934-ee6690825af3
Version Independent ID: 893e002a-9da5-3cd9-3880-3365abc76474
Content: How to Deploy the App-V 5.0 Server Using a Script
Content Source: mdop/appv-v5/how-to-deploy-the-app-v-50-server-using-a-script.md
Service: w10
GitHub Login: @jamiejdt
Microsoft Alias: jamiet

Hi, the best way to get help is to contact Microsoft Support (https://support.microsoft.com/en-us/contactus/), or you can post in the Forum (https://social.technet.microsoft.com/Forums/windows/en-US/home?forum=win10itprogeneral).

Thanks for raising this issue - we've updated the article so the table is formatted correctly. Thank you!


Velodyne Puck (VLP-16)

Hi, the results on VLP-16 on pretrained models aren't obviously impressive. Has anyone managed to improve them with somehow? I mean for example one can think of:

Retrain on dataset reduced to 16 rings
Aggregate point clouds (taking into account odometry) to lower frequency, but more dense data?
Change the position or angle of the sensor?
Two or more sensors? Or even fusion with depth camera?
...

Regards,

Hi @soldierofhell I am looking for an application on an VLP-16 as well, have you found some good results or datasets to train?

So far, I've tested a little bit of 2., but the problem is that you can correct the points by movement of vehicle, but still you're left with movement of object ("blur effect"). I must do some more tests, but still I rather prefer to aggregate then reduce..

I guess you need to track the movement for making those corrections, but that will not have the same result as a 64 rings lidar because the points could superpose right?.
Have you tried to reduce the number of points in the kitti dataset?.

I guess you need to track the movement for making those corrections,

Yes, but that's no problem, you have to do this on real vehicle/simulator anyway

but that will not have the same result as a 64 rings lidar because the points could superpose right?.

Of course. You'll get denser cloud but the "structure" will be different

Have you tried to reduce the number of points in the kitti dataset?.

Not yet, but I think I'll start with Waymo

Hi, the results on VLP-16 on pretrained models aren't obviously impressive. Has anyone managed to improve them with somehow? I mean for example one can think of:

Retrain on dataset reduced to 16 rings
Aggregate point clouds (taking into account odometry) to lower frequency, but more dense data?
Change the position or angle of the sensor?
Two or more sensors? Or even fusion with depth camera?
...

Regards,

Hi， have you solved your problem? I have met a similar problem with a lidar of 32 lines.

Hi, could you kindly share the evaluation metrics obtained with point clouds from VLP-16?
I am using A2D2 dataset but the results are really bad.
Car<EMAIL_ADDRESS>0.70, 0.70:
bbox AP:27.9918, 27.9322, 35.5970
bev  AP:19.8531, 20.3522, 26.0223
3d   AP:11.2460, 11.5596, 13.6794
aos  AP:26.38, 26.32, 33.20
Car<EMAIL_ADDRESS>0.70, 0.70:
bbox AP:25.8497, 25.8407, 34.3857
bev  AP:13.8069, 14.9976, 21.5022
3d   AP:3.5310, 4.0570, 7.6144
aos  AP:24.21, 24.15, 31.86
Car<EMAIL_ADDRESS>0.50, 0.50:
bbox AP:27.9918, 27.9322, 35.5970
bev  AP:41.1764, 40.8807, 48.6118
3d   AP:35.0433, 34.2128, 41.3431
aos  AP:26.38, 26.32, 33.20
Car<EMAIL_ADDRESS>0.50, 0.50:
bbox AP:25.8497, 25.8407, 34.3857
bev  AP:38.4422, 38.9257, 45.9213
3d   AP:31.6660, 31.4929, 39.0600
aos  AP:24.21, 24.15, 31.86
I would like to understand if it is all the fault of low resolution or I am doing something wrong.


Add #[py_class] attribute proc macro

All the naming is up for debate, and also the solution for using proc macros inside rustpython_vm. I think it's a pretty good system, and I don't think there are really any other crates trying to use a proc macro in their own crate and in consumer crates.

In Rust 1.34, which will be released around mid-April, extern_crate_self will be stabilised(https://github.com/rust-lang/rust/pull/57407#issuecomment-452566839). This allows adding:
extern crate self as rustpython_vm;

Which solves the problem, as we can then write rustpython_vm::xxx from within the crate.

Oh, nice. This sort of hacky solution works for now, then.

Um... what are the benefits of this?
Because I'm not a fan of going back to zelf.

I would have kept self, but using impl PyStringRef with #[py_class] gave some weird internal rustc compiler error. We could put this on the back burner until arbitrary_self_types lands.

@adrian17

Um... what are the benefits of this?

Some that I can think of are:

It would provide a very nice way for users to implement their own native extensions for rustpython
We could derive __doc__ from rust doc comments
It makes it a bit clearer which methods are python methods and which are rust-only helpers.

@coolreader18

We could put this on the back burner until arbitrary_self_types lands.

I think that is the right thing to do. Also, while I think this is a good thing to have (see above reasons) I'm not totally convinced that using it for builtins / rustpython internals is the right thing to do.

Oh, I was about to write a new response, so...
I'm still not seeing benefits fully. Is it just moving type attribute definitions from init to attributes next to methods? I'm not sure this is worth all the extra complexity.

It would provide a very nice way for users to implement their own native extensions for rustpython

How does it make it easier?

We could derive doc from rust doc comments

I'd be cautious about putting Python-user-visible strings in the place that's normally used for implementation-level comments and docs.

It makes it a bit clearer which methods are python methods and which are rust-only helpers.

How? Before seeing your comment I was about to say that it's more confusing now; it seems like all methods are now implicitly exposed with their function name by default?

How does it make it easier?

Less familiarity with rustpython-specific APIs would be required. Ideally for native extensions the declarations are as close to just writing pure, idiomatic rust as possible. Having to write a bit of imperative code for each method feels like it's in opposition of that goal. PyO3 does something similar and it's been very positively received.

I'd be cautious about putting Python-user-visible strings in the place that's normally used for implementation-level comments and docs.

Implementation-level comments would use //, docs would use ///

How? Before seeing your comment I was about to say that it's more confusing now; it seems like all methods are now implicitly exposed with their function name by default?

Methods should definitely not be implicitly exposed. For example:
impl MyNativeType {
    fn helper_rust_only() {
        ...
    }

    #[pymethod]
    fn method_callable_from_python(self: PyRef<Self>) {
        self.helper_rust_only();
    }
}

The benefit is that you don't have to jump all the way to the init / make_module / whatever to figure out which ones are actual python methods. (In this example, the self: PyRef<Self> also serves that purpose, but I imagine eventually we could make it so we just take &self for methods that don't actually need to consume the ref).

Implementation-level comments would use //, docs would use ///

Alright.

Methods should definitely not be implicitly exposed. For example:

I was commenting about the current version of the code, which does it implicitly - if methods (and properties? :) ) become explicit, that'll be nice indeed.

The benefit is that you don't have to jump all the way to the init / make_module / whatever to figure out which ones are actual python methods.

I'm speaking mostly from my minor experience with CPython, where I rarely had a problem of "is this an exposed method?", and more often of "which (magic) methods does this type expose/override?". For this use case I felt like a centralized spot like this allowed for quicker lookups.
https://github.com/python/cpython/blob/2f54908afc5665937d763510b4430f10cf764641/Objects/tupleobject.c#L826-L833
Anyway, with explicit #[pymethod] and allowing for self I'll definitely feel much warmer towards this :)

Alright, I'll work on that then.

I would have kept self, but using impl PyStringRef with #[py_class] gave some weird internal rustc compiler error.

BTW, are you sure this isn't https://github.com/rust-lang/rust/issues/59406 ? Me and @OddCoincidence  encountered this multiple times, it's relatively easy to trigger when doing "covert X to new style args" commits. This appears to be a bug with error reporting, and can be encountered when there's a coding error (referring to PyXRef::func when func doesn't exist, but there happens to exist PyYRef::func). If this indeed is it, it may mean that you can actually make this work with PystringRef, just need to fix some bugs.

Yes, it was that. How did you avoid it?

More specifically, for example, it occurs when eg I did by accident
impl PyTupleRef {
    fn tuple_count(...args...) {...}
}
...
extend_class!(context, tuple_type, {
    "count" => context.new_rustfunc(PyTupleRef::count),
}

Note the mismatch between tuple_count and count names. Rust can't find the PyTupleRef::count method, somewhere during the search it somehow stumbles upon PyListRef::count and ICEs. The solution was simple, fix the name tuple_count -> count.

Oh, you did it :)

Okay, I think I've addressed all concerns and the current version looks much nicer and more explicit.

I think that would be possible, and it would make code reuse like that much easier and more intuitive.

I'll work on trait #[pymethods] in a separate PR.

The macro implementation is beyond my understanding. I will have to learn this.
A single list of functions for an object has its benefits. Marking a method as such, also has benefits. I'm fine with both. In general, I'm for keeping things simple at the cost of some extra lines of code.
That being said, I leave it to others to judge this PR. For me, its fine :).

@windelbouwman is the naming better now? I renamed _extend_class to impl_extend_class, which I feel better explains what it does, while extend_class is a little convenience method that should be called from the outside in most cases.

@adrian17 I have trait support (probably) ready to go under coolreader18/pyimpl-on-trait with fbe37d0749130f3ac0cf9637d935797b121cc715, but I'll probably wait on a PR until #765 or #770 are merged so that I can try it out on a real "Protocol".

@windelbouwman @OddCoincidence Is this good to merge now?


Where can I find the Temporal Shift Setting&Exposure Shift Setting dataset？

Thank you for your interest in our work. I have uploaded the datasets used in the implementation of the paper to the repository. You can find it in the OOD_data.


Task reconciliation does not work after leader reelection

I'm running a cluster of 5 mesos-masters/zookeeper/marathon.
I'm running most of my apps as docker containers.

Marathon 0.8.2 (I experienced this bug in any version of 0.8.x)
Mesos 0.22.1
docker 1.6.2
RHEL 6.5

Every time the marathon leader gets reelected, it's failing the task reconciliation for most of the tasks. You can see it killing nearly every task and spawning new instances shortly after.
It does not matter, how/why the leader gets reelected.
I was able to reproduce this behavior in vagrant boxes:

1x mesos-master/zookeeper/marathon
1x marathon
1x mesos-slave
1x task running "while true ; do sleep 10 ; date ; done"
1x task running yhttp in a docker container "felixb/yocto-httpd"

I forced marathon to reelect the leader via REST-API.
The interesting part is, that task reconciliation works fine, when no docker task is running.
But as soon as there are multiple containerizers, only the oldest task stays alive.
I'm running the mesos-master with the following options:
/usr/sbin/mesos-master --zk=zk://localhost:2181/mesos --port=17100 \
    --cluster=mesos develop --quorum=3 --roles=marathon,chronos,spark \
    --webui_dir=/usr/share/mesos/webui --work_dir=/var/opt/data/mesos

The slaves starts with multiple containerizers:
/usr/sbin/mesos-slave --master=zk://.../mesos --hadoop_home=/var/opt/hadoop \
    --cgroups_enable_cfs --cgroups_hierarchy=/cgroup --cgroups_limit_swap \
    --containerizers=docker,mesos --docker_stop_timeout=30secs \
    --executor_registration_timeout=2mins --isolation=cgroups/cpu,cgroups/mem \
    --port=17100 --recovery_timeout=2mins --strict=false --work_dir=/var/opt/data/mesos \
    --attributes=cluster:KGHAM1;datacenter:Hamburg;environment:shop;resourcepool:develop

Marathon is running with the following options:
java -jar /var/opt/marathon/bin/../target/scala-2.11/marathon-assembly-0.8.2.jar \
    --master zk://localhost:2181/mesos --zk zk://localhost:2181/marathon --mesos_role marathon \
    --mesos_user marathon --http_port 8080 --checkpoint --event_subscriber http_callback --ha \
    --failover_timeout 75 --reconciliation_interval 75000

mesos-master log file
I0612 14:26:02.232628  5511 http.cpp:516] HTTP request for '/master/state.json'
I0612 14:26:04.351080  5504 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:04.358263  5508 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2347 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:04.358814  5508 hierarchical.hpp:648] Recovered cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000] (total allocatable: cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000]) on slave 20150612-105616-1160423616-17100-5468-S44 from framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:10.355249  5507 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:10.366829  5511 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2348 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:10.367063  5511 hierarchical.hpp:648] Recovered cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000] (total allocatable: cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000]) on slave 20150612-105616-1160423616-17100-5468-S44 from framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:12.272161  5508 http.cpp:516] HTTP request for '/master/state.json'
I0612 14:26:14.755897  5504 master.cpp:3522] Performing explicit task state reconciliation for 2 tasks of framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:14.758635  5504 master.cpp:3461] Performing implicit task state reconciliation for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:16.361681  5506 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:16.368597  5507 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2349 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:16.368785  5505 hierarchical.hpp:648] Recovered cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000] (total allocatable: cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000]) on slave 20150612-105616-1160423616-17100-5468-S44 from framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:22.328002  5510 http.cpp:516] HTTP request for '/master/state.json'
I0612 14:26:22.366937  5509 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:22.384783  5509 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2350 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185
I0612 14:26:22.385000  5509 hierarchical.hpp:648] Recovered cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000] (total allocatable: cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000]) on slave 20150612-105616-1160423616-17100-5468-S44 from framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:26.933971  5509 master.cpp:1711] Received re-registration request from framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:26.934072  5509 master.cpp:1764] Re-registering framework 20150611-103128-1160423616-17100-12472-0001 (marathon)  at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:26.934095  5509 master.cpp:1783] Updating info for framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:26.934114  5509 master.cpp:1798] Framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-c38256f0-c3a0-4946-b883-25400d5b8f7a@<IP_ADDRESS>:35185 failed over
I0612 14:26:28.372448  5510 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:28.381594  5506 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2351 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:28.381857  5509 hierarchical.hpp:648] Recovered cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000] (total allocatable: cpus(*):3.7; mem(*):6587; disk(*):227114; ports(*):[31000-31794, 31796-32000]) on slave 20150612-105616-1160423616-17100-5468-S44 from framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:32.369503  5511 http.cpp:516] HTTP request for '/master/state.json'
I0612 14:26:34.377359  5504 master.cpp:3760] Sending 1 offers to framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:34.386256  5505 master.cpp:2273] Processing ACCEPT call for offers: [ 20150612-105616-1160423616-17100-5468-O2352 ] on slave 20150612-105616-1160423616-17100-5468-S44 at slave(1)@<IP_ADDRESS>:17105 (<IP_ADDRESS>) for framework 20150611-103128-1160423616-17100-12472-0001 (marathon) at scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340

mesos-slave logfile
I0612 14:26:26.926584 11071 slave.cpp:1945] Updating framework 20150611-103128-1160423616-17100-12472-0001 pid to scheduler-001537a2-628d-4a4c-8f96-9c69c9eedde4@<IP_ADDRESS>:37340
I0612 14:26:26.926962 11071 status_update_manager.cpp:178] Resuming sending status updates
I0612 14:26:33.999011 11072 slave.cpp:3648] Current disk usage 23.96%. Max allowed age: 4.623004749876655days
I0612 14:26:41.958184 11070 slave.cpp:1581] Asked to kill task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.080211 11065 slave.cpp:2531] Handling status update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001 from executor(1)@<IP_ADDRESS>:38521
I0612 14:26:42.080806 11068 mem.cpp:319] Updated 'memory.soft_limit_in_bytes' to 32MB for container 4911e40a-8785-44b6-8101-425cc9cbd9e2
I0612 14:26:42.080827 11072 cpushare.cpp:377] Updated 'cpu.shares' to 102 (cpus 0.1) for container 4911e40a-8785-44b6-8101-425cc9cbd9e2
I0612 14:26:42.081543 11072 cpushare.cpp:399] Updated 'cpu.cfs_period_us' to 100ms and 'cpu.cfs_quota_us' to 10ms (cpus 0.1) for container 4911e40a-8785-44b6-8101-425cc9cbd9e2
I0612 14:26:42.081663 11069 status_update_manager.cpp:317] Received status update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.081696 11069 status_update_manager.hpp:346] Checkpointing UPDATE for status update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.086590 11066 slave.cpp:2776] Forwarding the update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001 to master@<IP_ADDRESS>:17100
I0612 14:26:42.086659 11066 slave.cpp:2709] Sending acknowledgement for status update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001 to executor(1)@<IP_ADDRESS>:38521
I0612 14:26:42.093179 11069 status_update_manager.cpp:389] Received status update acknowledgement (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.093250 11069 status_update_manager.hpp:346] Checkpointing ACK for status update TASK_KILLED (UUID: a55df415-acde-4c2c-95b5-8b9fc5522ae5) for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.387437 11065 slave.cpp:1144] Got assigned task sleep.483a0e86-10fe-11e5-898b-080027a4f769 for framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.387725 11065 slave.cpp:1254] Launching task sleep.483a0e86-10fe-11e5-898b-080027a4f769 for framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.390823 11065 slave.cpp:4208] Launching executor sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001 in work directory '/home/flx/tmp/mesos/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.483a0e86-10fe-11e5-898b-080027a4f769/runs/18441293-386e-4c40-b810-820fbb208087'
I0612 14:26:42.391315 11071 docker.cpp:598] No container info found, skipping launch
I0612 14:26:42.391487 11069 containerizer.cpp:484] Starting container '18441293-386e-4c40-b810-820fbb208087' for executor 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' of framework '20150611-103128-1160423616-17100-12472-0001'
I0612 14:26:42.393004 11067 cpushare.cpp:377] Updated 'cpu.shares' to 204 (cpus 0.2) for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.393188 11065 slave.cpp:1401] Queuing task 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' for executor sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework '20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.393698 11067 cpushare.cpp:399] Updated 'cpu.cfs_period_us' to 100ms and 'cpu.cfs_quota_us' to 20ms (cpus 0.2) for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.394875 11069 mem.cpp:487] Started listening for OOM events for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.395299 11069 mem.cpp:319] Updated 'memory.soft_limit_in_bytes' to 64MB for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.395860 11069 mem.cpp:354] Updated 'memory.limit_in_bytes' to 64MB for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.396847 11069 linux_launcher.cpp:213] Cloning child process with flags = 0
I0612 14:26:42.398118 11069 containerizer.cpp:694] Checkpointing executor's forked pid 13248 to '/home/flx/tmp/mesos/meta/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.483a0e86-10fe-11e5-898b-080027a4f769/runs/18441293-386e-4c40-b810-820fbb208087/pids/forked.pid'
I0612 14:26:42.400061 11069 slave.cpp:3165] Monitoring executor 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' of framework '20150611-103128-1160423616-17100-12472-0001' in container '18441293-386e-4c40-b810-820fbb208087'
I0612 14:26:42.522264 11072 slave.cpp:2164] Got registration for executor 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' of framework 20150611-103128-1160423616-17100-12472-0001 from executor(1)@<IP_ADDRESS>:47995
I0612 14:26:42.523583 11072 cpushare.cpp:377] Updated 'cpu.shares' to 204 (cpus 0.2) for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.525938 11072 cpushare.cpp:399] Updated 'cpu.cfs_period_us' to 100ms and 'cpu.cfs_quota_us' to 20ms (cpus 0.2) for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.525087 11066 mem.cpp:319] Updated 'memory.soft_limit_in_bytes' to 64MB for container 18441293-386e-4c40-b810-820fbb208087
I0612 14:26:42.526494 11066 slave.cpp:1555] Sending queued task 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' to executor 'sleep.483a0e86-10fe-11e5-898b-080027a4f769' of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.531574 11072 slave.cpp:2531] Handling status update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001 from executor(1)@<IP_ADDRESS>:47995
I0612 14:26:42.531791 11071 status_update_manager.cpp:317] Received status update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.531944 11071 status_update_manager.hpp:346] Checkpointing UPDATE for status update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.541491 11071 slave.cpp:2776] Forwarding the update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001 to master@<IP_ADDRESS>:17100
I0612 14:26:42.541638 11071 slave.cpp:2709] Sending acknowledgement for status update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001 to executor(1)@<IP_ADDRESS>:47995
I0612 14:26:42.564708 11071 status_update_manager.cpp:389] Received status update acknowledgement (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:42.564769 11071 status_update_manager.hpp:346] Checkpointing ACK for status update TASK_RUNNING (UUID: ad73f97e-d43e-4216-b8d5-8ea1ec30471d) for task sleep.483a0e86-10fe-11e5-898b-080027a4f769 of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:43.117852 11069 containerizer.cpp:1123] Executor for container '4911e40a-8785-44b6-8101-425cc9cbd9e2' has exited
I0612 14:26:43.117887 11069 containerizer.cpp:918] Destroying container '4911e40a-8785-44b6-8101-425cc9cbd9e2'
I0612 14:26:43.118870 11066 cgroups.cpp:2251] Freezing cgroup /sys/fs/cgroup/freezer/mesos/4911e40a-8785-44b6-8101-425cc9cbd9e2
I0612 14:26:43.119798 11069 cgroups.cpp:1418] Successfully froze cgroup /sys/fs/cgroup/freezer/mesos/4911e40a-8785-44b6-8101-425cc9cbd9e2 after 897024ns
I0612 14:26:43.120686 11067 cgroups.cpp:2268] Thawing cgroup /sys/fs/cgroup/freezer/mesos/4911e40a-8785-44b6-8101-425cc9cbd9e2
I0612 14:26:43.121527 11067 cgroups.cpp:1447] Successfullly thawed cgroup /sys/fs/cgroup/freezer/mesos/4911e40a-8785-44b6-8101-425cc9cbd9e2 after 804864ns
I0612 14:26:43.124860 11071 slave.cpp:3223] Executor 'sleep.0b5119ae-10fe-11e5-b846-0800276a3382' of framework 20150611-103128-1160423616-17100-12472-0001 exited with status 0
I0612 14:26:43.124912 11071 slave.cpp:3332] Cleaning up executor 'sleep.0b5119ae-10fe-11e5-b846-0800276a3382' of framework 20150611-103128-1160423616-17100-12472-0001
I0612 14:26:43.125069 11072 gc.cpp:56] Scheduling '/home/flx/tmp/mesos/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.0b5119ae-10fe-11e5-b846-0800276a3382/runs/4911e40a-8785-44b6-8101-425cc9cbd9e2' for gc 6.9999985528237days in the future
I0612 14:26:43.125115 11072 gc.cpp:56] Scheduling '/home/flx/tmp/mesos/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.0b5119ae-10fe-11e5-b846-0800276a3382' for gc 6.99999855237037days in the future
I0612 14:26:43.125141 11072 gc.cpp:56] Scheduling '/home/flx/tmp/mesos/meta/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.0b5119ae-10fe-11e5-b846-0800276a3382/runs/4911e40a-8785-44b6-8101-425cc9cbd9e2' for gc 6.99999855211852days in the future
I0612 14:26:43.125157 11072 gc.cpp:56] Scheduling '/home/flx/tmp/mesos/meta/slaves/20150612-105616-1160423616-17100-5468-S44/frameworks/20150611-103128-1160423616-17100-12472-0001/executors/sleep.0b5119ae-10fe-11e5-b846-0800276a3382' for gc 6.9999985518963days in the future
I0612 14:27:34.000224 11070 slave.cpp:3648] Current disk usage 23.96%. Max allowed age: 4.622995095040417days

marathon old leader log file:
[2015-06-12 14:26:14,743] INFO Expunging orphaned tasks from store (mesosphere.marathon.tasks.TaskTracker:170)
[2015-06-12 14:26:14,745] INFO Expunging orphaned task with key task:sleep:sleep.dfbc7be5-10fd-11e5-898b-080027a4f769 (mesosphere.marathon.tasks.TaskTracker:178)
[2015-06-12 14:26:14,753] INFO Syncing tasks for all apps (mesosphere.marathon.SchedulerActions:457)
[2015-06-12 14:26:14,754] INFO Requesting task reconciliation with the Mesos master (mesosphere.marathon.SchedulerActions:482)
[2015-06-12 14:26:14,757] INFO Received status update for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:14,761] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:14,764] INFO Received status update for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:14,767] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:16,367] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:16,367] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:22,382] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:22,383] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:26,828] INFO Abdicating (mesosphere.marathon.MarathonSchedulerService:312)
[2015-06-12 14:26:26,828] INFO Defeat leadership (mesosphere.marathon.MarathonSchedulerService:285)
[2015-06-12 14:26:26,847] INFO Stopping driver (mesosphere.marathon.MarathonSchedulerService:224)
I0612 14:26:26.847770 10494 sched.cpp:1589] Asked to stop the driver
I0612 14:26:26.848037 10477 sched.cpp:831] Stopping framework '20150611-103128-1160423616-17100-12472-0001'
[2015-06-12 14:26:26,848] INFO Driver future completed. Executing optional abdication command. (mesosphere.marathon.MarathonSchedulerService:195)
[INFO] [06/12/2015 14:26:26.829] [marathon-akka.actor.default-dispatcher-50] [akka://marathon/user/MarathonScheduler/$a] Suspending scheduler actor
[2015-06-12 14:26:26,848] INFO <IP_ADDRESS> -  -  [12/Jun/2015:12:26:26 +0000] "DELETE /v2/leader HTTP/1.1" 200 33 "-" "curl/7.38.0" (mesosphere.chaos.http.ChaosRequestLog:15)
[2015-06-12 14:26:26,854] INFO Defeated (Leader Interface) (mesosphere.marathon.MarathonSchedulerService:245)
[2015-06-12 14:26:26,855] INFO Defeat leadership (mesosphere.marathon.MarathonSchedulerService:285)
[2015-06-12 14:26:26,855] INFO Will offer leadership after 500 milliseconds backoff (mesosphere.marathon.MarathonSchedulerService:334)
[2015-06-12 14:26:26,860] INFO Stopping driver (mesosphere.marathon.MarathonSchedulerService:224)
[2015-06-12 14:26:26,863] ERROR Current member ID member_0000000016 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:26,867] ERROR Current member ID member_0000000012 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:26,868] ERROR Current member ID member_0000000014 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:26,871] ERROR Current member ID member_0000000018 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:26,877] ERROR Current member ID member_0000000010 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,371] INFO Using HA and therefore offering leadership (mesosphere.marathon.MarathonSchedulerService:341)
[2015-06-12 14:26:27,376] INFO Set group member ID to member_0000000020 (com.twitter.common.zookeeper.Group:426)
[2015-06-12 14:26:27,377] ERROR Current member ID member_0000000016 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,379] ERROR Current member ID member_0000000012 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,379] INFO Candidate /marathon/leader/member_0000000020 waiting for the next leader election, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:165)
[2015-06-12 14:26:27,380] ERROR Current member ID member_0000000014 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,381] ERROR Current member ID member_0000000018 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,382] ERROR Current member ID member_0000000010 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)

marathon new leader log file
[2015-06-12 14:26:26,851] INFO Proxying request to leader at mesos-dev-f999998.exampl.com:8080 (mesosphere.marathon.api.LeaderProxyFilter:62)
[2015-06-12 14:26:26,876] INFO <IP_ADDRESS> -  -  [12/Jun/2015:12:26:26 +0000] "DELETE /v2/leader HTTP/1.1" 200 33 "-" "curl/7.38.0" (mesosphere.chaos.http.ChaosRequestLog:15)
[2015-06-12 14:26:26,886] INFO Candidate /marathon/leader/member_0000000019 is now leader of group: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:152)
[2015-06-12 14:26:26,886] INFO Elected (Leader Interface) (mesosphere.marathon.MarathonSchedulerService:252)
[2015-06-12 14:26:26,905] INFO Migration successfully applied for version Version(0, 8, 2) (mesosphere.marathon.state.Migration:69)
[2015-06-12 14:26:26,905] INFO Elect leadership (mesosphere.marathon.MarathonSchedulerService:299)
[2015-06-12 14:26:26,906] INFO Running driver (mesosphere.marathon.MarathonSchedulerService:187)
[2015-06-12 14:26:26,906] INFO Reset offerLeadership backoff (mesosphere.marathon.MarathonSchedulerService:329)
I0612 14:26:26.906806 15169 sched.cpp:157] Version: 0.22.1
2015-06-12 14:26:26,906:14324(0x7f0a0216e700):ZOO_INFO@log_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5
2015-06-12 14:26:26,906:14324(0x7f0a0216e700):ZOO_INFO@log_env@716: Client environment:host.name=mesos-dev-f999996.exampl.com
2015-06-12 14:26:26,906:14324(0x7f0a0216e700):ZOO_INFO@log_env@723: Client environment:os.name=Linux
2015-06-12 14:26:26,906:14324(0x7f0a0216e700):ZOO_INFO@log_env@724: Client environment:os.arch=2.6.32-279.el6.x86_64
2015-06-12 14:26:26,906:14324(0x7f0a0216e700):ZOO_INFO@log_env@725: Client environment:os.version=#1 SMP Wed Jun 13 18:24:36 EDT 2012
[INFO] [06/12/2015 14:26:26.906] [marathon-akka.actor.default-dispatcher-6] [akka://marathon/user/MarathonScheduler/$a] Starting scheduler actor
[2015-06-12 14:26:26,910] ERROR Current member ID member_0000000013 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:26,912] ERROR Current member ID member_0000000017 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
2015-06-12 14:26:26,914:14324(0x7f0a0216e700):ZOO_INFO@log_env@733: Client environment:user.name=(null)
2015-06-12 14:26:26,919:14324(0x7f0a0216e700):ZOO_INFO@log_env@741: Client environment:user.home=/root
2015-06-12 14:26:26,919:14324(0x7f0a0216e700):ZOO_INFO@log_env@753: Client environment:user.dir=/
2015-06-12 14:26:26,919:14324(0x7f0a0216e700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=mesos-dev-f999998:2181 sessionTimeout=10000 watcher=0x7f0a2dd88eb0 sessionId=0 sessionPasswd=<null> context=0x7f09b4012b70 flags=0
[INFO] [06/12/2015 14:26:26.920] [marathon-akka.actor.default-dispatcher-20] [akka://marathon/user/MarathonScheduler/$a] Scheduler actor ready
[2015-06-12 14:26:26,925] ERROR Current member ID member_0000000011 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
2015-06-12 14:26:26,925:14324(0x7f099ffec700):ZOO_INFO@check_events@1703: initiated connection to server [<IP_ADDRESS>:2181]
2015-06-12 14:26:26,941:14324(0x7f099ffec700):ZOO_INFO@check_events@1750: session establishment complete on server [<IP_ADDRESS>:2181], sessionId=0x14de6fbddd0002b, negotiated timeout=10000
[2015-06-12 14:26:26,942] ERROR Current member ID member_0000000015 is not a candidate for leader, current voting: [member_0000000019] (com.twitter.common.zookeeper.CandidateImpl:144)
I0612 14:26:26.942391 14368 group.cpp:313] Group process (group(5)@<IP_ADDRESS>:37340) connected to ZooKeeper
I0612 14:26:26.942440 14368 group.cpp:790] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0)
I0612 14:26:26.942456 14368 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
I0612 14:26:26.945544 14368 detector.cpp:138] Detected a new leader: (id='3')
I0612 14:26:26.945794 14368 group.cpp:659] Trying to get '/mesos/info_0000000003' in ZooKeeper
I0612 14:26:26.958334 14368 detector.cpp:452] A new leading master (UPID=master@<IP_ADDRESS>:17100) is detected
I0612 14:26:26.958490 14368 sched.cpp:254] New master detected at master@<IP_ADDRESS>:17100
I0612 14:26:26.958529 14368 sched.cpp:264] No credentials provided. Attempting to register without authentication
I0612 14:26:26.964764 14368 sched.cpp:448] Framework registered with 20150611-103128-1160423616-17100-12472-0001
[2015-06-12 14:26:26,966] INFO Registered as 20150611-103128-1160423616-17100-12472-0001 to master '20150612-105616-1160423616-17100-5468' (mesosphere.marathon.MarathonScheduler:55)
[INFO] [06/12/2015 14:26:26.966] [marathon-akka.actor.default-dispatcher-6] [akka://marathon/user/$b] POSTing to all endpoints.
[2015-06-12 14:26:26,976] INFO Stored framework ID '20150611-103128-1160423616-17100-12472-0001' (mesosphere.mesos.util.FrameworkIdUtil:49)
[2015-06-12 14:26:27,409] ERROR Current member ID member_0000000013 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,411] ERROR Current member ID member_0000000017 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,412] ERROR Current member ID member_0000000011 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:27,414] ERROR Current member ID member_0000000015 is not a candidate for leader, current voting: [member_0000000019, member_0000000020] (com.twitter.common.zookeeper.CandidateImpl:144)
[2015-06-12 14:26:28,404] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:28,405] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:34,410] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:34,410] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:40,413] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:40,414] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:41,910] INFO Syncing tasks for all apps (mesosphere.marathon.SchedulerActions:457)
[2015-06-12 14:26:41,911] INFO Requesting task reconciliation with the Mesos master (mesosphere.marathon.SchedulerActions:482)
[2015-06-12 14:26:41,919] INFO Received status update for task sleep.dfbc7be5-10fd-11e5-898b-080027a4f769: TASK_LOST (Reconciliation: Task is unknown to the slave) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:41,942] INFO Already running 1 instances of /sleep. Not scaling. (mesosphere.marathon.SchedulerActions:545)
[2015-06-12 14:26:41,953] INFO Already running 1 instances of /yhttpd. Not scaling. (mesosphere.marathon.SchedulerActions:545)
[2015-06-12 14:26:41,974] INFO Task sleep.dfbc7be5-10fd-11e5-898b-080027a4f769 expunged and removed from TaskTracker (mesosphere.marathon.tasks.TaskTracker:107)
[2015-06-12 14:26:41,975] INFO Sending event notification. (mesosphere.marathon.MarathonScheduler:212)
[2015-06-12 14:26:41,975] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[INFO] [06/12/2015 14:26:41.975] [marathon-akka.actor.default-dispatcher-21] [akka://marathon/user/$b] POSTing to all endpoints.
[2015-06-12 14:26:41,980] INFO Need to scale /sleep from 0 up to 1 instances (mesosphere.marathon.SchedulerActions:521)
[2015-06-12 14:26:41,980] INFO Queueing 1 new tasks for /sleep (0 queued) (mesosphere.marathon.SchedulerActions:527)
[2015-06-12 14:26:41,982] INFO Received status update for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:41,986] WARN No task for ID sleep.0b5119ae-10fe-11e5-b846-0800276a3382 (mesosphere.marathon.tasks.TaskTracker:149)
[2015-06-12 14:26:41,987] WARN Killing task value: "sleep.0b5119ae-10fe-11e5-b846-0800276a3382"
 (mesosphere.marathon.MarathonScheduler:151)
[2015-06-12 14:26:41,987] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:42,122] INFO Received status update for task sleep.0b5119ae-10fe-11e5-b846-0800276a3382: TASK_KILLED (Command terminated with signal Terminated) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:42,125] WARN Couldn't post event for value: "sleep.0b5119ae-10fe-11e5-b846-0800276a3382"
 (mesosphere.marathon.MarathonScheduler:123)
[2015-06-12 14:26:42,131] INFO Need to scale /sleep from 0 up to 1 instances (mesosphere.marathon.SchedulerActions:521)
[2015-06-12 14:26:42,131] INFO Already queued 1 tasks for /sleep. Not scaling. (mesosphere.marathon.SchedulerActions:531)
[2015-06-12 14:26:42,416] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:42,418] INFO Launched 1 tasks on 1 offers, declining 0 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:42,576] INFO Received status update for task sleep.483a0e86-10fe-11e5-898b-080027a4f769: TASK_RUNNING () (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:26:42,617] INFO Sending event notification. (mesosphere.marathon.MarathonScheduler:212)
[INFO] [06/12/2015 14:26:42.619] [marathon-akka.actor.default-dispatcher-21] [akka://marathon/user/$b] POSTing to all endpoints.
[2015-06-12 14:26:48,421] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:48,421] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:26:54,425] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:26:54,425] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:00,435] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:00,435] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:06,461] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:06,462] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:12,441] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:12,441] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:18,453] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:18,454] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:24,450] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:24,451] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:30,452] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:30,453] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:36,457] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:36,458] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:42,468] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:42,468] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:47,498] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:47,499] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:53,507] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:53,507] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:27:56,906] INFO Expunging orphaned tasks from store (mesosphere.marathon.tasks.TaskTracker:170)
[2015-06-12 14:27:56,909] INFO Expunging orphaned task with key task:sleep:sleep.0b5119ae-10fe-11e5-b846-0800276a3382 (mesosphere.marathon.tasks.TaskTracker:178)
[2015-06-12 14:27:56,916] INFO Syncing tasks for all apps (mesosphere.marathon.SchedulerActions:457)
[2015-06-12 14:27:56,917] INFO Requesting task reconciliation with the Mesos master (mesosphere.marathon.SchedulerActions:482)
[2015-06-12 14:27:56,934] INFO Received status update for task sleep.483a0e86-10fe-11e5-898b-080027a4f769: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:27:56,962] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:27:56,966] INFO Received status update for task sleep.483a0e86-10fe-11e5-898b-080027a4f769: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:27:56,969] INFO Received status update for task yhttpd.885a4b8c-10fc-11e5-b846-0800276a3382: TASK_RUNNING (Reconciliation: Latest task state) (mesosphere.marathon.MarathonScheduler:98)
[2015-06-12 14:27:59,510] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:27:59,510] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:05,515] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:05,515] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:11,519] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:11,520] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:17,522] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:17,522] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:23,595] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:23,596] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:29,534] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:29,534] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:35,541] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:35,542] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:41,545] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:41,547] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:47,552] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:47,553] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)
[2015-06-12 14:28:53,561] INFO started processing 1 offers, launching at most 1 tasks per offer and 1000 tasks in total (mesosphere.marathon.tasks.IterativeOfferMatcher$:124)
[2015-06-12 14:28:53,562] INFO Launched 0 tasks on 0 offers, declining 1 (mesosphere.marathon.tasks.IterativeOfferMatcher$:216)

@felixb Hey Felix. Thanks for the report.
I did some reelections on our staging cluster - the problem did not show up.
After digging in the logs you have provided, I think I found the problem:

you have a sleep task that has reached the sleep time and ended
the leadership election takes place, a new leader gets elected
the new leader starts task reconciliation, which means it synchronizes the local persisted state with the mesos master
at the same time the TaskTracker starts its work. It realizes that the sleep application has not enough tasks and starts a new tasks.
Mesos launches the sleep task and sends a TaskStatus
the TaskReconciliation process receives this TaskStatus and declares that Task as unknown (since there is no Reference from the last leader). In that case the TaskReconciliation process will kill the unknown task.
The TaskReconciliation process finishes
The TaskTracker again realizes, that there are not enough tasks for the application and starts another one

That said: you should see this problem (and the logs prove that) only for lost tasks and a new leader election  (e.g. task yhttpd is not killed and restarted). The title of this ticket is somewhat more drastic, so I want to make sure, we are on the same page.
Can you acknowledge this observation?

Sadly I cant. The sleep task is running forever. while true ; do sleep 10 ; date ; done is never finishing on it's own.
Also, you can see, that marathon is actively killing the sleep task:
[2015-06-12 14:26:41,987] WARN Killing task value: "sleep.0b5119ae-10fe-11e5-b846-0800276a3382"

(mesosphere.marathon.MarathonScheduler:151)
Any other ideas?

According to the old leaders log file, the task is considered as orphaned - I can not see the reason for this, since the log file starts just there. The observation remains the same: the TaskTracker and TaskReconciliation fight each other.
We definitively will fix that.
If you want, you can try a work around: try to increase the reconciliation delay with --reconciliation_initial_delay 300000. That will wait for 5 minutes (the default interval) instead of 15 seconds for reconciliation after leader election.

@aquamatthias If you want to reproduce this, you need to also make sure that you spawn some tasks after failing over from one leader to another.  Those are the tasks that will get killed when you fail over from the second back to the first.  Any tasks that existed at the moment you fail over from the first leader to the second will be fine since they already are cached in the TaskTracker.

@dkesler thats true. That also was my initial guess as I saw the sleep task: If you use something like sleep 1 then there is a high chance, that the expected count of apps is not met after one second. This will force the described behavior.

@dkesler: that was not the case in my observations:
I just had two tasks sitting there and running for a few minutes. Than I forced the leader to give up. There was no fresh deployment or what so ever.
@aquamatthias: I'll try to increase the timeout and let you know, what happens.

@felixb Were you failing back and forth between multiple marathon leaders?  It looks like the 'new marathon leader' in your example logs has a reference to an old 'sleep' task (sleep.dfbc7be5) which it expunges as the mesos task no longer exists while it also kills a different sleep task (sleep.0b5119ae) because it has no task with that ID.  It then spawns a new sleep task since none are running.
I'm not sure how you got into the state to begin with, but once you get into a state where marathon instances are out of sync, every time you fail over from A to B, the task that A knew about (but B doesn't) gets killed and replaced by a task B spawns.  Then when you fail over back to A, A expunges its old task, kill's B's task (which was created after A lost leadership), and spawns a new task.  Thus a new sleep task is in fact being created every time a marathon leader fails over, even though you're not explicitly spawning one.  (and also ensuring that the cycle continues one very leadership failover).

Well, I have only two instances running and switching the leader back and forth.

I started to get strange when I added the docker task.
Is there any way to break out of the state you mentioned in #1553 without removing the complete state?

You can fix the state by restarting the non-leader marathon instances.  The problem is that TaskTracker starts out empty and gets hydrated when the app first becomes leader.  However it only keeps it up to date as a result of performing it's leaderly duties.  So if it loses leadership and later becomes leader again, it is running with outdated data in the TaskTracker that reflects the state of tasks at the moment it lost leadership.  If you restart the non-leader marathon instances, they won't have stale data in their TaskTracker (they won't have any data, in fact), so when they gain leadership they'll hydrate the TaskTracker.

I can verify, that my issue is in fact #1553. In some cases a fresh master would start additional instances for an app, than scaling it down after reconciliation. But it would not kill any existing tasks.
Thanks for your help guys.


Some logics and arts

Enjoy some fun snake photos.

@vokal/ios-developers Anyone wanna tell me I'm swifting it wrong in the morning?

that's all from me

Dat's it from me

@chillpop @bryanluby changes pushed

LGTM

LGTM unless you want to delete unused functions

Unused methods nuked :bomb:

:shipit:


Deployment Steps

Hi,
It would be very nice to see some deployment steps to Azure.
https://github.com/OfficeDev/generator-office/issues/490
Because I just tried to deploy it and got  the following errors:
Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: Platform not supported: linux.
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a6ed3136-1d12-66c2-a8b1-1e7e43553aae
Version Independent ID: 0e40308a-2d3d-a27b-04d5-1bdd7c09b501
Content: Build your first OneNote task pane add-in - Office Add-ins
Content Source: docs/quickstarts/onenote-quickstart.md
Product: onenote
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@bwong199 Thanks for asking about this. Please see if this article about hosting an Office Add-in on Microsoft Azure helps.
I'll close this issue for now but if you hit further issues or have other feedback, let us know.
Thanks.


When inputing a single image

I appreciate your work very much. I would like to ask you about the reconstruction of a single image, because the model is suitable for any number of inputs, so can the network be extended to the reconstruction of a single image without considering optical flow correction?  Thank you.

You can try single image by copying the same image and passing it to each of the encoders. But we didn't try that and can't say what the results would be and I don't personally think it would be able to fill in the missing details or correct noise as loss functions never encouraged it to do that.


Incorrect error reported when calling a function returned from another function

Given the following code:
<?php

function getEchoFunction()
{
    return function ($message) {
        echo($message);
    };
}

getEchoFunction()('hey');

An error is reported. It looks like it doesn't like calling functions inline like that.

Error: ';' expected. Line 10:18

Changing the code to:
$echo = getEchoFunction();
$echo('hey');

works as expected.
(Copied from https://github.com/atom/ide-php/issues/26)

@roblourens This can be closed, can't it?

@roblourens When do you schedule the next release? I'd love to see the improved parser version in daily usage. :)

Just pushed 0.0.9 👍


(x86asm) Highlightblock Does not automatically detect the assembly language and takes it as "properties"

When applying the hljs.highlightBlock function, it does not automatically detect the assembly language and takes it as a "properties" language, causing the colors not to be rendered. I have tried other languages and if you have taken them well so far
This happens with x86asm but applying the tag to autodetect.This happens with x86asm but applying the tag to autodetect. I know it's really hard to get 100% to match the language, but I think it could be detected with the comments starting with ';'.
For example somehow detect ';COMMENT .asm' or if someone has done it in a custom way with another language
This is highlightAuto 📌
Sample Code to Reproduce
//It is an example of the code but this is developed with a component language dynamically

//Html Template with pre
             ;Author: xxxx xxxx
             ;Bitcheck.asm

             .INCLUDE "../../include/m32def.inc"

             .ORG 0

             ;SETTING THES STACK POINTER
             LDI R16, LOW(RAMEND)
             OUT SPL, R16
             LDI R16, HIGH(RAMEND)
             OUT SPH, R16

             LDI R16, 0xFF
             OUT DDRC, R16 ;PORTC IS OUTPUT

             LDI R17, 0x00
             OUT DDRD, R17 ;PORTD IS INPUT

//JS Controller
      this.template.querySelectorAll('pre').forEach((block) => {
              hljs.highlightBlock(block);
      });

What I hope is to detect the assembly type automatically or customize the class to detect it in some way, I have read the comment that for highlightAuto there is not much that can be done but I leave this issue in case someone has achieved it
The image is of the language it detects and the colors it renders:

I have updated to the latest version and my problem has been corrected. Thanks all!


MAINT: changed repr of data store instances

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 91.437%

Files with Coverage Reduction
New Missed Lines
%

.nox/test-3-9/lib/python3.9/site-packages/cogent3/app/data_store_new.py
15
93.61%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
179777

Relevant Lines:
196612

💛  - Coveralls


document exception types

why not to use SyntaxError and the diff between pepper errors

Closing #46, fixed in #51


Images are incorrect

Hi authors,
I think the images are little bit old.
(Actually the size of workspace is 10GB)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e0947245-d1c6-486a-94a1-f8622a4f7efc
Version Independent ID: c837d3a1-75f5-ffd4-a32a-541bab72ffa7
Content: Manage data storage in your workspaces - Power BI
Content Source: powerbi-docs/admin/service-admin-manage-your-data-storage-in-power-bi.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @Hyamyam. This issue has been assigned to the doc author for review.

Hi @Hyamyam, thanks for this input. I myself noticed this recently and am in the process of going over this article. So I am going to close this issue here now. Thanks again for taking the time to point this out!


fix: anyOf on querystring

Status
READY
Description
Fix https://github.com/anymaniax/orval/issues/884.
Tests were also added. I'm not familiar enough with the orval codebase (for now haha), but I think this fix is enough. Also tested on our production codebase and can confirm the problem was fixed.
Todos

[x] Tests
[x] Documentation
[ ] Changelog Entry (unreleased)

What should I do to create add a changelog entry?

That I don't know I have never done one so I think your PR is ok for now.


Adding support to define SecurityContext

Is your feature request related to a problem? Please describe.
Integrating the PVC of ActiveMQ Artemis with some storage providers sometimes requires to be able to define the SecurityContext which should be used for the Pod.
Describe the solution you'd like
It should be possible to define an optional SecurityContext in the ActiveMQArtemis deploymentPlan spec.
apiVersion: broker.amq.io/v2alpha4
kind: ActiveMQArtemis
metadata:
  name: example
spec:
  deploymentPlan:
    size: 1
    image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.0
    securityContext:
      runAsUser: 1000
      runAsGroup: 3000
      fsGroup: 2000

The Operator should configure the StatefulSet to use the SecurityContext in the PodTemplate.
Describe alternatives you've considered
Using mutating webhooks to modify the created Pods. But it would be much nicer to have this possibility built-in.

with #73 there is already  the possibility to set
securityContext:
  runAsUser: 185

by setting
podSecurity:
  runAsUser: 185

runAsGroup and  fsGroup is still missing.


fix(stripe): Add API key to correct location and configure success pa…

…ge routing  Added the Stripe API key to the correct location in the backend to ensure proper authentication. Also configured the routing in main.jsx to include a success page that handles redirection after successful payment processing.
fix(stripe): Add API key to correct location and configure success page routing
Added the Stripe API key to the correct location in the backend to ensure proper authentication. Also configured the routing in main.jsx to include a success page that handles redirection after successful payment processing.

Thanks David!


If administrator prevents login, users get stuck being logged in to stroom auth

To recreate

As admin, set the stroom.maintenance.preventLogin flag to true.
Logout and log back in as another user.
Login to stroom-auth works, but the stroom ui then prevents you doing anything and displays an error
This means it's impossible to log back out, which you may want to do so that you can log back in as admin to do stuff.

It seems possible that this is not actually a realistic scenario in production? Obviously as a tester I am logging in and out as different users all the time.

MAINT002
Prevent Login


removed the slide transition from the default template

resolves issue #7

Hi @elstamey! We have decided to close issue #7, so I am also closing the PR. Thank you!


[CMAKE] Add MKL to PATH

Currently, instead of adding mkl_BIN_DIRS to the path, the path is replaced by mkl_BIN_DIRS.  I was getting weird errors from the generated command because my PATH was now gone. This PR adds the MKL binary path to the front of PATH  instead of replacing PATH .
Brief discussion of why this wasn't done before is in the CMake file comments. Refer to those comments for details. It appears there were some issues with having more than one path in PATH. I've tested this on Windows to generate the correct syntax, but haven't tested on a Linux build.
@LoSealL @mrry It looks like both of you worked on that section.  What kinds of issues were happening with multiple items in PATH? With only MKL on the path, generated commands fail for me at importing numpy.
If the command fails it shows up in the build log as error MSB6006: "cmd.exe" exited with code 1.
BTW, the other minor changes are from tab to space.
Cheers

Yes, you're right. The previous PR is just a work around.
But I noticed that the build failure is caused by the project estimator_python_api, which was introduced later after the PR, and this project needs the path of MKL to locate the libraries.
Hence in my new PR, I changed this part of logic, just by copying MKL libraries into python package, so the generating script could locate the MKL libraries correctly without assigning a path explicitly. I think this could be a better way to handle the path to MKL libraries, and the built distributed python package (.whl) could installed MKL to system, while in the previous CMAKE script one needs to copy MKL libraries into system path explicitly after installing .whl package.

And when I executed command like cmake -E env PYTHONPATH=$a $b $c ... or cmake -E env PYTHONPATH=$a;$b;$c ..., neither of them is correctly executed in cmake building process. The correct pattern I think is cmake -E env PYTHONPATH="$a;$b;$c" ... but I found the cmake interprets it as PYTHONPATH=$a $b $c or something like PYTHONPATH=\"$a $b $c\" which definitely incurs errors

@LoSealL The standard quoting would be PATH="a;b;c" or "PATH=a;b;c". The command this generates looks odd but actually parses correctly (at least in my testing): cmake ... "PATH=a";"b";"c" ....
Makes a lot of sense to get everything in the same directory and not rely on the PATH. That way it can coexist with other things on my system. I'm using MKL and MKLDNN for other things, too, so it would be nice to be sure I'm loading the right MKLDNN in tensorflow without relying on the PATH.


Programatically determine the range of years with data

This is currently a hardcoded array.

Fixed in 669a6e7460871000cf65570415b20ccf191f8cba.


Implement history quick pick

This PR closes #1692

Implemented algorithm to group chats by last interaction timestamp.
Added an icon in the editor panel to display history chats as a quick pick, separated by the group.
Updated the history chats in the Treeview provider to render them as grouped chats.
Remove createCodyChatTreeItems, use the updateTree method of TreeViewProvider to update the list instead.

Test plan
https://github.com/sourcegraph/cody/assets/44617923/5804d8da-a629-4670-8de9-ff3b3da61e25

@toolmantim @philipp-spiess @abeatrix Can I have a review please?

@toolmantim @philipp-spiess Tested with the updated rename chat feature, too, it works fine. All good to test for now!

@dominiccooney Thanks for the review. I have made all the changes as per the review!

@toolmantim Thanks a lot for the detailed review and comments. I will soon make those changes :)

@toolmantim I have fixed the bug you mentioned and made all the suggested changes except one to expand the group when the chat is revealed. I have implemented one solution for this, but it does not expand the tree when rebuilding it. I also tried a few other workarounds, but it didn't work.
@philipp-spiess I would appreciate some help on this: The issue is when the chat is being revealed, I am updating the collapsible state of the tree when calling the updateTree method, but it is not expanding the tree. Even though I have attached an event listener to it, it still doesn't work.
https://github.com/sourcegraph/cody/assets/44617923/dabd5e28-70ef-4345-b5a5-16900e94173b

@dominiccooney I have made the requested changes to calculate the groups using the date calculation.
Also, would you mind taking a quick look at the abovementioned issue related to the collapsed state when chats are revived and I recreate the items?

This one: @philipp-spiess I would appreciate some help on this: The issue is when the chat is being revealed, I am updating the collapsible state of the tree when calling the updateTree method, but it is not expanding the tree. Even though I have attached an event listener to it, it still doesn't work.

@toolmantim @dominiccooney This is all good to go now, after the recent change of using authStatus to load chats this PR was having issue. I have taken care of it now, and it works all good as expected. Can you please add your final review for this?

@toolmantim @dominiccooney Thanks for the review, I will just resolve the conflicts now and it should be good to go!

@deepak2431 I hit approve on the Actions runs, and it looks like there's a few other things that need fixing due to changes

@toolmantim I see, do let me know I can make those changes.

@deepak2431 apologies, I thought you could view them! Error: src/services/TreeViewProvider.test.ts(72,53): error TS2339: Property 'label' does not exist on type 'Uri'. on both pnpm test:unit and pnpm test:e2e

@toolmantim No problem; I thought there might be some UI changes due to the coming updated Chat UI.
All the unit tests are passing for me successfully:

Looks like the test being flaky, but yeah let me check it again on my side!

@toolmantim Fixed the test issue, all tests are passing without any issue now!

@deepak2431 thank you! Tests look green but pnpm exec biome ci --error-on-warnings . seems to be exiting with an error. Can you check that locally too? If we get it fixed today we can get it into this week’s release!

@toolmantim Fixed the biome lint errors :)

Finally got this one merged @deepak2431! Appreciate all of your work that went into this, and I'm sure users will too 🙏

Thanks, @toolmantim. Finally will get this shipped into this week's release!


strftime on unicode Python error on run

I've just newly installed vdirsyncer on FreeBSD from the prebuild packages so this is using python 2.7. When I run a sync, I get the following error:
Unhandled exception occured for oliver.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/cli/tasks.py", line 72, in sync_collection
    force_delete=force_delete
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/sync.py", line 158, in sync
    b_idents = _prepare_idents(storage_b, storage_a, b_href_to_status)
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/sync.py", line 113, in _prepare_idents
    hrefs = _prepare_hrefs(storage, other_storage, href_to_status)
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/sync.py", line 98, in _prepare_hrefs
    for href, etag in storage.list():
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/storage/dav.py", line 633, in list
    for caldavfilter in caldavfilters:
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/storage/dav.py", line 605, in _get_list_filters
    start, end):
  File "/usr/local/lib/python2.7/site-packages/vdirsyncer/storage/dav.py", line 591, in _get_list_filters
    start = start.strftime(CALDAV_DT_FORMAT)
AttributeError: 'unicode' object has no attribute 'strftime'

I'm guessing that start should be some sort of date object rather than of type unicode. Any idea what the cause of this might be? Thanks

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26925180-strftime-on-unicode-python-error-on-run?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github).

Could you post your configuration for that storage?

Seems the problem is related to these two lines copied from the website:
start_date = datetime.now() - timedelta(days=365)
end_date = datetime.now() + timedelta(days=365)

Full config is as follows. The intention is to sync between local storage for khal and owncloud.
[general]
status_path = /home/opk/.cache/vdirsyncer
[pair opk]
a = opk_local
b = opk_cloud

[storage opk_local]
type = filesystem
path = ~/.calendars/opk/
fileext = .ics

[storage opk_cloud]
type = caldav
url = "https://<IP_ADDRESS>/remote.php/calendarplus/calendars/opk/opk"
start_date = datetime.now() - timedelta(days=365)
end_date = datetime.now() + timedelta(days=365)
username = "opk"
verify_fingerprint = "F0:10:AD:EF:36:EF:9E:3E:81:A9:C5:3D:F2:71:76:40:30:4C:2A:1F"

These lines work fine for me. Which version of vdirsyncer are you using?

0.4.3
I hadn't realised how old the vdirsyncer in FreeBSD's ports was. It is Python 2.7 if that has any impact on it.

It should work fine with that version too, but according to pkgsrc the latest version is 0.6.0...

FreeBSD doesn't use pkg source though.

@okapia Have you tried upgrading vdirsyncer?

@okapia any updates on this?

Sorry, I had not upgraded yet because I was lazily hoping that it wouldn't be long before pkg update would upgrade it. It is still out-of-date there. I was also assuming that a manual upgrade would entail manual installs or upgrades of a whole load of python dependencies which discouraged me from trying.
Anyway, I've just tested a manual install of vdirsyncer from git and can confirm that the problem is gone. I had to make changes to the config file but that was essentially changes to reflect documented changes in vdirsyncer.
Thanks for your help and sorry for reporting the issue without first upgrading.

No worries, thanks for the response.