Alex Heneveld
Alex Heneveld
Hi @Foxandxss -- anything I can do to encourage you to merge this? thx!
@Foxandxss I don't think it breaks the API -- just expands it to accept `clear(list)` in addition to `clear(toast)` and `clear()` which both still work as before. and the contract...
I encountered this also. Seems `$destroy` doesn't always cause the element to be removed immediately. I think I've fixed this in #219 (at least in my case). Also added support...
test failure is clearly unrelated, maybe close and reopen to run again. meanwhile we should look at this /cc @aledsage : ``` org.apache.brooklyn.entity.software.base.test.autoscaling.AutoScalerPolicyNoMoreMachinesTest.testResizeDirectly (from TestSuite) java.lang.AssertionError: removed=[EmptySoftwareProcessImpl{id=NhzxGta6}] expected [2] but...
(easily fixed - the test was doing an immediate assert on something happening in another thread; PR to follow; @iyovcheva give it an hour or so for the other fix...
as @tbouron notes this shouldn't have the duplicate, and it should have picked up a bunch more version changes. i suggest closing this @nakomis and holding fire on updating license/notice...
@nakomis agree failure unrelated, have snuck an attempt to fix this in at #1171 btw this behaviour change seems reasonable as we normally want a load-balancer to be accessible. however...
(plus another test failure fix at #1174)
ugly failure this time. not one i've come across. probably nondet. @nakomix you're not having luck! ``` org.apache.brooklyn.AssemblyTest.checkBrooklynCoreFeature Failing for the past 1 build (Since Unstable#2472 ) Took 5.5 sec....