This is to initiate a conversation about a certain commit.
Also serves as a test.


l'autre exo c'est : Given an infinite number of quarters (25 cents), dimes (10 cents), nickels (5 cents) and pennies (1 cent), write code to calculate the number of ways of representing n cents.


I know but there was unfortunatelly no way to do that efficiently - we would have to use reflection to detect if the constructor exists and has some non-optional arguments or not.


git init
git clone https://github.com/douaeMAHROUG/courriers
git add .   (tu ajoute tout les nouveaux fichier)
git comit -m "mon message"
git push


Minor, but is it worth lifting this magic number out of here?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5579](https://teamcity.mesosphere.io/viewLog.html?buildId=77060&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:51


Does the MimeTypes text/x-c and text/x-c++ exist? Cannot find them on Debian testing/stable or Ubuntu 14.


I thought we were using 3 digits? "2.0.0"?


Another possibility (and I prefer this one) is put the Configurator instance as a member in MainController:
```
class MainController{
   public:
        MainController( APPTYPE appType, other params)
            : configurator( Configurator( appType ) {

         }
protected:
    Configurator configurator;
}
```
And in StandaloneMainController constructor we can pass the correct APPTYPE for the base class (MainController) and do the same in VSTPluginMainController.

I prefer this solution, because we have no singletons, no statics, and no pointers, no leaks, etc. Configurator instance will be destroyed when MainControlller is destroyed.


Funky (grammatical) sentence structure!? Missing a 'have' I think? Especially together with 'moderating' on the next line, should that be 'moderate'?


haha


"Explicit is better etc."
On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com> wrote:

> Is fail in a do block much better than let pattern failure?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345>
> .
>


Sure they are, if you like code that moves between the new style and hash rockets just because of object keys and string keys (talk about inconsistent code, I thought style guides were meant to stop that? :wink:,) or if you like confusing the distinction between keyword arguments and hashes (aren't style guides supposed to make code more understandable? :stuck_out_tongue_winking_eye:)


Not commented correctly, removed continue as it gave errors


But the fail is still just as implicit
On Nov 17, 2015 23:05, "Noam Lewis" <notifications@github.com> wrote:

> "Explicit is better etc."
> On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com> wrote:
>
> > Is fail in a do block much better than let pattern failure?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455526>
> .
>


One could also add text/x-cmake and text/x-objcsrc


 We don't have a way to capture native stdout. And the value would
 differ anyway


Ok, so this change does not have any purpose to you but it has meaning for other developers. Does changing it bother you?


@duncanjbrown this is a bit ambiguous... presumably you mean filling in the publisher interest form? Is it worth deep-linking here?


Yes!


Now includes profanity!


^ :+1: on what @Bartuz said.


tu en penses quoi? l'exo 2 c'est dans la partie récursive mais je ne vois pas pourquoi ce serait plus simple en récursif.


Should use a constant here (similar to FMT_SC), perhaps FMT_MAX_SC?


я не вижу смысла хранить стейт именно в гите к тому же со всем содержимым инфраструктуры навиду.
А вообще да, как я понял у них есть отдельный сервис атлас ( https://atlas.hashicorp.com/ ) в том числе для сохранения стейтов и их версионирования.

К тому же опираясь на мой стейт терраформ бы падал не с моими AWS ключами


This could work *if* the loop is unrolled, as we don't support iteration
over non-uniform containers.


You can grep "error" to find it. Not implicit
On Nov 17, 2015 11:06 PM, "Eyal Lotem" <notifications@github.com> wrote:

> But the fail is still just as implicit
> On Nov 17, 2015 23:05, "Noam Lewis" <notifications@github.com> wrote:
>
> > "Explicit is better etc."
> > On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com> wrote:
> >
> > > Is fail in a do block much better than let pattern failure?
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455526
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455540>
> .
>


d


seems not, it's just manipulating the types, whatever their implementation?


I'll probably use this to call for lunch tomorrow


Should this mention how to install the plugin from GitHub?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5580](https://teamcity.mesosphere.io/viewLog.html?buildId=77066&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:43


This method was being called from ```FileAttachment```. Now that they're in different packages the method needs to be public. I also renamed it to ```streamAttachment```.


не понял, что имелось ввиду под region-agnostic, но это же просто дефолтное значение переменной, оно может быть переопределено


More importantly it serves as documentation that we are handling the error
(by failing on it) not just forgot to handle a pattern
On Nov 17, 2015 11:07 PM, "Noam Lewis" <lenoam@gmail.com> wrote:

> You can grep "error" to find it. Not implicit
> On Nov 17, 2015 11:06 PM, "Eyal Lotem" <notifications@github.com> wrote:
>
>> But the fail is still just as implicit
>> On Nov 17, 2015 23:05, "Noam Lewis" <notifications@github.com> wrote:
>>
>> > "Explicit is better etc."
>> > On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com>
>> wrote:
>> >
>> > > Is fail in a do block much better than let pattern failure?
>> > >
>> > > —
>> > > Reply to this email directly or view it on GitHub
>> > > <
>> >
>> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345
>> > >
>> > > .
>> > >
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455526
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455540>
>> .
>>
>


I'm referring to pattern match in do stmt instead of pattern match in
"let". No fail/error

On Tue, Nov 17, 2015, 23:08 Noam Lewis <notifications@github.com> wrote:

> You can grep "error" to find it. Not implicit
> On Nov 17, 2015 11:06 PM, "Eyal Lotem" <notifications@github.com> wrote:
>
> > But the fail is still just as implicit
> > On Nov 17, 2015 23:05, "Noam Lewis" <notifications@github.com> wrote:
> >
> > > "Explicit is better etc."
> > > On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com>
> wrote:
> > >
> > > > Is fail in a do block much better than let pattern failure?
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > >
> >
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345
> > > >
> > > > .
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455526
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455540
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455596>
> .
>


Есть штука https://terraform.io/docs/providers/aws/r/key_pair.html
Она сама все зарегистрирует.


```validateAndEmitRequest()``` is not public. Overloaded ```execute()``` to take in an ```OutputStream``` as a way to expose it.


TeamCity pull requests :: netty [Build 675](https://garage.netty.io/teamcity/viewLog.html?buildId=3326&buildTypeId=pulls_netty&guest=1) is now running


Updated bio


In the grandscheme of things that this software has that will slow down code, this is probably the least of those.


Looking at the project description it still wasn't clear to me what this did. When looking into why it was failing I did find that it doesn't support Java 8 yet. That was enough for me to remove it.

Besides, I don't trust something with a name like animal sniffer.


This commit slightly re-works the error handling to once again get around method calls we were making to protected methods that are no longer visible.


Explicit error is nice. At least one case was converted from implicit let
to implicit do binding

On Tue, Nov 17, 2015, 23:09 Noam Lewis <notifications@github.com> wrote:

> More importantly it serves as documentation that we are handling the error
> (by failing on it) not just forgot to handle a pattern
> On Nov 17, 2015 11:07 PM, "Noam Lewis" <lenoam@gmail.com> wrote:
>
> > You can grep "error" to find it. Not implicit
> > On Nov 17, 2015 11:06 PM, "Eyal Lotem" <notifications@github.com> wrote:
> >
> >> But the fail is still just as implicit
> >> On Nov 17, 2015 23:05, "Noam Lewis" <notifications@github.com> wrote:
> >>
> >> > "Explicit is better etc."
> >> > On Nov 17, 2015 10:57 PM, "Eyal Lotem" <notifications@github.com>
> >> wrote:
> >> >
> >> > > Is fail in a do block much better than let pattern failure?
> >> > >
> >> > > —
> >> > > Reply to this email directly or view it on GitHub
> >> > > <
> >> >
> >>
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455345
> >> > >
> >> > > .
> >> > >
> >> >
> >> > —
> >> > Reply to this email directly or view it on GitHub
> >> > <
> >>
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455526
> >> >
> >> > .
> >> >
> >>
> >> —
> >> Reply to this email directly or view it on GitHub
> >> <
> https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455540
> >
> >> .
> >>
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ElastiLotem/buildsome/commit/c676061cf8698b8238cc08d6f9d55565f28bb075#commitcomment-14455632>
> .
>


Moved the attachment response byte parsing to here.


This seems fine here, since the `err` should have handled the case above. It really would make no sense to get here.


I didn't see any other way to get to this.


I think that there should be a documentation update (at the top of the same file) to accompany this functional change. I would also be interested to see a (small) description of a use-case in the changelog.


Not sure. haven't seen a TCGA build with Individual as subject yet. Again, this just provides an alternative way to get TCGA patient_id if individual upn is not available or not starts with TCGA-


Am I missing something, or is this value not used again? ```attr == increased``` should only happen once, and ```incr_value``` is only used in this condition?


This is simplified due to the above change.


@avalanche123 is this really an issue?
```
php-driver/ext/src/Cassandra/Rows.c:308:5: warning: Access to field 'value' results in a dereference of a null pointer (loaded from variable '__zv')
    RETURN_ZVAL(self->future_next_page, 1, 0);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/php/Zend/zend_API.h:638:40: note: expanded from macro 'RETURN_ZVAL'
#define RETURN_ZVAL(zv, copy, dtor)             { RETVAL_ZVAL(zv, copy, dtor); return; }
                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/php/Zend/zend_API.h:626:38: note: expanded from macro 'RETVAL_ZVAL'
#define RETVAL_ZVAL(zv, copy, dtor)             ZVAL_ZVAL(return_value, zv, copy, dtor)
                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/php/Zend/zend_API.h:603:3: note: expanded from macro 'ZVAL_ZVAL'
                ZVAL_COPY_VALUE(__z, __zv);                             \
                ^~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/php/Zend/zend.h:768:16: note: expanded from macro 'ZVAL_COPY_VALUE'
                (z)->value = (v)->value;                                \
                             ^~~~~~~~~~
```


This new functionality looks good to me.

Could you update the patch to add some documentation (earlier in the same file)?


зачем тебе такой?


IDL


https://github.com/peanig/terraform/blob/master/vpc.tf#L19 - а и это тоже переопределится?


:heart: :heart: :heart: :heart:


I have changed the version of the plugin to 1.0.0-SNAPSHOT which will result in 1.0.0 final release.


heb dat gedaan maar krijg:

NameError in DimItems#index
Showing /Users/malcolm/ruby_files/rails_studio/webdev_roo/app/views/dim_items/index.html.erb where line #7 raised:

undefined local variable or method `type' for #<#<Class:0x007fc2b5ab6178>:0x007fc2b6b4ad18>
Extracted source (around line #7):
4
5
6
7
8
9
10

  <ul>
     <% @dim_items.each do |i| %>
      <li> <%=i.dimensie_code%> | <%=i.dimension_id%> | <%=i.item_sleutel%> | <%=i.item_naam%> | <%=i.item_omschrijving%> |
      <%=link_to 'koppelingen', dimension_dim_item_format_item_links_url(@dimension, i, type::dim)%> </li>
     <%end%>
  </ul>

Moet ik type nog ergens anders declareren. En wat is de scope van type? Is blijkbaar iig bekend binnen FormatItemLinkController


Right on. I'll need to look if there are any other changes I need to make to follow PyDisdrometer conventions.


:sunglasses: Gracias


I'm not sure how to implement this, as the current checked in implementation throws an NullReferenceException. So I handle now both cases and the last else clause should never be triggered, but just in case I'm defaulting to "unknown". What do you think?


I thought this was still wishy washy could be interpreted either way. Seems kind of odd to go against the grain of the established de-facto (trimLeft/trimRight) and use `start` and `end`.


TeamCity pull requests :: netty [Build 675](https://garage.netty.io/teamcity/viewLog.html?buildId=3326&buildTypeId=pulls_netty&guest=1) outcome was **FAILURE**
Summary: Tests failed: 12 (12 new), passed: 4776, ignored: 16 Build time: 00:05:37
### Failed tests
```
io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingSingleMessage: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingMultipleMessages: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingSingleEmptyMessage: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.deflateEncodingWriteLargeMessage: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.connectionWindowUpdateShouldSendFrame: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.flowControlledWriteCompleteThrowsAnException: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.nonWritableChannelDoesNotAttemptToWrite: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.initialWindowSizeWithNoContextShouldNotThrow: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.successiveSendsShouldNotInteract: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.payloadSmallerThanWindowShouldBeWrittenImmediately: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.contextShouldSendQueuedFramesWhenSet: <no details avaliable>

##### there are 2 more failed tests, see build details
```


We need to fix these tests not to leak file handles, not just put this band-aid on them.


not sure what you mean, looks like we're missing another `MAKE_STD_ZVAL(self->future_next_page);` on https://github.com/datastax/php-driver/blob/e323f052fccfa8de9e0af14bd2d81d9713da2599/ext/src/Cassandra/Rows.c#L305


с этим косяк, да. В переменные надо отдельно зоны заносить


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5581](https://teamcity.mesosphere.io/viewLog.html?buildId=77067&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:10:34


I'd be happy to merge it in if you're willing to verify and create a pull request


не подумал, да, можно заюзать


TeamCity pull requests :: netty [Build 676](https://garage.netty.io/teamcity/viewLog.html?buildId=3327&buildTypeId=pulls_netty&guest=1) is now running


This looks good to me.

I wonder how many other protocol checks don't honor the port configuration.


I'd like to understand under which scenario the current build is not able to find libexpat. For example, I just built i586-geode-linux-uclibc (just a random sample with DEBUG_GDB_NATIVE enabled) and:

````
$ ~/x-tools/i586-geode-linux-uclibc/bin/i586-geode-linux-uclibc-gcc -print-search-dirs
...
libraries: =/home/avn/x-tools/i586-geode-linux-uclibc/lib/gcc/i586-geode-linux-uclibc/5.2.0/:/home/avn/x-tools/i586-geode-linux-uclibc/lib/gcc/i586-geode-linux-uclibc/5.2.0/../../../../i586-geode-linux-uclibc/lib/i586-geode-linux-uclibc/5.2.0/:/home/avn/x-tools/i586-geode-linux-uclibc/lib/gcc/i586-geode-linux-uclibc/5.2.0/../../../../i586-geode-linux-uclibc/lib/:/home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/lib/i586-geode-linux-uclibc/5.2.0/:/home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/lib/:/home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/usr/lib/i586-geode-linux-uclibc/5.2.0/:/home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/usr/lib/
```
and libexpat.a is in the last directory of the search path:
````
$ ll /home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/usr/lib/libexpat*
-r--r--r-- 1 avn avn 206580 Nov 17 12:54 /home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/usr/lib/libexpat.a
-r-xr-xr-x 1 avn avn    880 Nov 17 12:54 /home/avn/x-tools/i586-geode-linux-uclibc/i586-geode-linux-uclibc/sysroot/usr/lib/libexpat.la*
````
native-gdb has been built successfully, and used libexpat by just supplying -lexpat to linker flags.


all identischi account amounts aggregiere


400mA - Pi2 with EDIMAX and RY835AI, gen_gdl90 from v0.4r4 running.
350mA - Pi2 with EDIMAX and RY835AI, gen_gdl90 NOT running.

675mA - Pi2 with EDIMAX, RY835AI, one R820T2, gen_gdl90 from v0.4r4 running.
600mA - Pi2 with EDIMAX, RY835AI, one R820T2, gen_gdl90 NOT running.

     #HDMI output off
     /opt/vc/bin/tvservice -o
     #HDMI output on
     /opt/vc/bin/tvservice -p


I had that idea too at the beginning , but i wanted to avoid to put my feets in your classes .
So being extern was a way to work in // with you .

That :
MainController( APPTYPE appType, other params)
            : configurator( Configurator( appType ) {....  }

is :+1:

And sounds very logical ... woaw !
But will it be as simple to use ?
In main.cpp for example , how it would work ?

**Configurator instance will be destroyed when MainControlller is destroyed.**
That is an important point to consider , sounds good to me .


her commection object is not private


CPU usage on gen_gdl90 down to about 2% when in idle state.


The general consensus was that since trimLeft/trimRight were the only examples of "left" and "right", and they're Annex B/legacy anyways, we could fix this mistake now. In addition, the trimLeft/trimRight proposal will also now add trimStart/trimEnd, which is filed as https://github.com/sebmarkbage/ecmascript-string-left-right-trim/issues/3


Yep, it looks like the tag is missing.


ja. aber das löst ja mis problem nöd...?


Added ability to restrict selection to a single day.


je bent de spatie vergeten tussen :type en :dim... type: :dim is een andere notatie voor :type => :dim


should you also ignore `tx` messages?


They've been around since ~2005 though. Will `trimStart` and `trimEnd` be different than `trimLeft` and `trimRight`?


kann weg. Problem behoben.


Jepp läuft :+1:


TeamCity pull requests :: netty [Build 676](https://garage.netty.io/teamcity/viewLog.html?buildId=3327&buildTypeId=pulls_netty&guest=1) outcome was **FAILURE**
Summary: Tests failed: 12, passed: 4776, ignored: 16 Build time: 00:04:48
### Failed tests
```
io.netty.handler.codec.http2.HttpToHttp2ConnectionHandlerTest.testRequestWithBody: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingSingleMessage: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingMultipleMessages: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.gzipEncodingSingleEmptyMessage: <no details avaliable>

io.netty.handler.codec.http2.DataCompressionHttp2Test.deflateEncodingWriteLargeMessage: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.connectionWindowUpdateShouldSendFrame: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.flowControlledWriteCompleteThrowsAnException: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.nonWritableChannelDoesNotAttemptToWrite: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.initialWindowSizeWithNoContextShouldNotThrow: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.successiveSendsShouldNotInteract: <no details avaliable>

io.netty.handler.codec.http2.DefaultHttp2RemoteFlowControllerTest.payloadSmallerThanWindowShouldBeWrittenImmediately: <no details avaliable>

##### there are 2 more failed tests, see build details
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5582](https://teamcity.mesosphere.io/viewLog.html?buildId=77068&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:10
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Well, I'm nearly sure the code is only called once.


Sorry, you were right. I did miss a commit. No issue now. Thank you.


@cheesegrits sure thing!  I have it in my fork as well...but didn't include it here.


I want to be sure I understand why `a[i]` could be nil even though `< len(a)`. The slice has sufficient storage for the entry, but for some reason there is a nil entry there. Is this just protecting against the caller setting the entry to `nil` for some reason?


@rushi what happens if you send the additional data as well?


it sure looks like you did more than what the commit message suggests :p


This is OK :smile: Like, division between social links


type is gewoon een symbol en wordt Rails maakt er een parameter in de url van. In de controller kun je vervolgens met de params Hash de waarde van deze (en willekeurig andere) parameters opvragen. type is dus niets bijzonders, je kunt ook :format_item_type o.i.d. als naam gebruiken.


Template for me, not for you :)


Yes, basically.


nice, make it lowe camel case


@srisurya95  wrong commit dude


TeamCity LabkeyRelease15.3 :: CDS postgres 9.4 [Build 11](https://teamcity.labkey.org/viewLog.html?buildId=285785&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 18 (1 new), passed: 8 Build time: 00:44:14
### Failed tests
```
org.labkey.test.tests.CDSLoginTest.testLoginPage: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSVisualizationTest: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyColorStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyDensePlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyTimeAxisWithMultipleSchedules: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAntigenBoxPlot: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBasic: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyTimeAxisBasic: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAxisSelectors: <no details avaliable>

##### there are 8 more failed tests, see build details
```


**I prefer this solution, because we have no singletons, no statics, and no pointers, no leaks, etc. Configurator instance will be destroyed when MainControlller is destroyed.**
But what you'll do with LogHandler in that case ?


comment from Git hub


Hm... What is wrong with this text?


Agree!


you might want to use multi-line, please see:
https://github.com/apache/spark/blob/master/R/pkg/R/DataFrame.R#L1783

note the use of `\cr` - otherwise roxygen2 would collapse all lines


The rest corrections are good! Thanks!


please see my comment for Peter on how to make this more compact


I think this discussion illustrates exactly the problem of multiple opinions :) One person prefers hash rockets and the other prefers no hash rockets. In the end I've decided for myself to side with Rubocop's defaults and have slept a lot better ever since ;)


5321-GroundDomain_RDD (mmatts) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


but the script is /bin/bash. And I'm afraid it won't redirect stderr. (btw never have issue with zsh for this syntax)


you may want to start the comments with a space for readability


Just so I understand correctly, this `confine_block` can be removed because `solaris` will now be tested in the block starting at line 34? I'm also curious how this is related to the commit message...is this now possible because of the `set_env` refactoring?


Why do we need global variables. I think we should avoid those where possible. I suggest we should return a type that contains this kind of information. AFAIK R does that too [reference](http://h2o-release.s3.amazonaws.com/h2o/rel-lambert/5/docs-website/Ruser/rtutorial.html)


TeamCity TripleA :: UnitTest [Build 123](http://188.177.191.210/viewLog.html?buildId=191&buildTypeId=TripleA_UnitTest&guest=1) is now running


nice :)


TeamCity TripleA :: UnitTest [Build 123](http://188.177.191.210/viewLog.html?buildId=191&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\CashRegister\CashRegister.csproj (new); number of tests is too small: 0 (new) Build time: 00:00:06


Ah ! Also , configurator could take the funk that defines the vst paths , don't you think ?
And also take in charge that kind of stuff :
void MainController::saveLastUserSettings(const Persistence::InputsSettings& inputsSettings){
    settings.save(inputsSettings);
}

?


do którego to jest ticketa?


Ok en plus de mettre l'énoncé, tu peux mettre la partie du bouquin?

—
Sent from Mailbox

On Tue, Nov 17, 2015 at 1:07 PM, maximesab <notifications@github.com>
wrote:

> tu en penses quoi? l'exo 2 c'est dans la partie récursive mais je ne vois pas pourquoi ce serait plus simple en récursif.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/maximesab/exo-info/commit/d94fcf2e28439c1d9918d496db039defa06ae027#commitcomment-14455569


Ember-cli uses a completely different pipeline for assets, based on javascript. It's kind of 'rails-for-ember' in that it organizes your ember app according to convention-over-configuration and provides its own asset pipeline.

It uses a mix of bower, npm and broccoli for different purposes.  The net-net though is that there's no ERB preprocessor so actioncable's embedding the internal references in cable.coffee.erb requires sprockets to be in the pipeline somewhere.

This effectively limits non-rails-based javascript UIs from being actioncable clients, and I wonder if that is worth gaining the value of injecting these internal values from the ruby code.

Fortunately for me, there is ember-cli-rails which serves ember-cli based clients via the rails asset pipeline -- after some fiddling and cursing I managed to get this working :)


Performance aside, unwrapping these makes it completely unambiguous.

There're cases where most ruby developers will get this wrong. For example, what is the result of `a, b = b, a`? Another example is https://github.com/bbatsov/rubocop/pull/2344, which I totally got wrong myself. Ruby evaluates right to left and when `output` or `attribute` are functions you can get all kinds of side effects that the next developer will never understand.


And with 2 rtl-sdrs?

Reason I ask is I have 2.1 amps (available) going into the mini-USB
power in on Pi2 but that is not enough to drive it.  Have to add another
power-in cable (also 2.1 amps available) via one of the large USB
connectors.
Only hardware differences are 1) standalone MPU6050 chip, and 2) serial
GPS chip (Adafruit "Ultimate GPS."

The power entering the stratux on the mini-USB only is not enough to
drive that combo.

Pi 2, 64GB sd card, 2 rtl-sdr's, and above mentioned IMU and GPS.

GPS via straight serial NOT working at all in stratux.  Works just fine
in minicom and custom software where I used open() and not fopen().

David

On 11/17/2015 03:18 PM, cyoung wrote:
>
> 400mA - Pi2 with EDIMAX and RY835AI, gen_gdl90 from v0.4r4 running.
> 350mA - Pi2 with EDIMAX and RY835AI, gen_gdl90 NOT running.
>
> 675mA - Pi2 with EDIMAX, RY835AI, one R820T2, gen_gdl90 from v0.4r4
> running.
> 600mA - Pi2 with EDIMAX, RY835AI, one R820T2, gen_gdl90 NOT running.
>
> | #HDMI output off
>  /opt/vc/bin/tvservice -o
>  #HDMI output on
>  /opt/vc/bin/tvservice -p
> |
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cyoung/stratux/commit/ec88895038b642a1a41b0e7b0e11091965fb2b25#commitcomment-14455826>.
>


Have you considered a/b testing this change? It has potential user growth implications.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5583](https://teamcity.mesosphere.io/viewLog.html?buildId=77071&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 202 Build time: 00:10:45


That's correct. Rubocop's autocorrect just points an unused variable out (and often will catch typos, we're not in a compiled language), if this is close to being merged I'll fix it by removing the block.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5577](https://teamcity.mesosphere.io/viewLog.html?buildId=77054&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout (new) Build time: 01:00:08


parties 8.7 et 5.1


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5585](https://teamcity.mesosphere.io/viewLog.html?buildId=77073&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:00


I don't understand the reasoning for this test...why did someone write a test that validates package upgrades fail on solaris? Was that behavior desirable?


Honestly mutex ought to be upgraded to C++11. But it is fine.


Yeah, it might cause problems with the fake player of pipeworks. But thats pipework's problem, not ours, so best you talk to @VanessaE about this.


Use absolute url instead of a relative path in the comment form action. Fixes #3.


Sounds like a ground issue, what exact cable and battery are you using?


If just a `make([]*FloatValue, 1000)` is passed in, the slice has a 1000 element capacity but each element is still nil.  Each element has to be initialized to a non-nil `*FloatValue` so lines 270/271 don't panic.


There's actually a good semantic reason why this was changed.

Signal exceptions using the `fail` method because you're failing explicitly. Use `raise` only when catching an exception and re-raising it (because here you're not failing, but explicitly and purposefully raising an exception).


Just read up and `trimStart` and `trimEnd` are intended to be aliases (so no new functionality).


I can deal with that argument, I've seen it happen before.  I'm :+1:


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5588](https://teamcity.mesosphere.io/viewLog.html?buildId=77076&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:01:28


why that? you should only need bcftools (incl vcfutils.pl) and samtools (all here: http://samtools.github.io/bcftools/) not BamTools.


Not a good idea, alsa file on linux will fail to compile. Code isn't enabled on linux, so maybe we can remove the dependency completely (if we don't build the code).


I thought this chapter had an interesting focus on hierarchy, specifically the visual relationship between parent/sibling links. I wonder how the different collection types came about, since at first glance the end result of "choice" and "unordered" look very similar. What was the process of deciding what collection types to add?


Still need to code findParent.


That's a yes and a no, it's a yes because I'll never adhere to it so ultimately when I commit it'll break the build, no because it at the end of the day it doesn't matter.


@davidaadams Is cloning the header necessary?  I haven't ever done it before, but maybe I've been putting my headers at risk.


Yeah I just got notified of that just a few minutes ago, it seems like there are lots of unused params we can clean out


Comment on a commit


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5584](https://teamcity.mesosphere.io/viewLog.html?buildId=77072&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:20
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


nit.


I think you could use a submodule for this, FWIW.


this syntax isn't quite right


despite that the snapshot version is used in the front end, more code in the front end is needed to make sure the graph updates with the latest version, which it does not yet do.


Thanks!


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5593](https://teamcity.mesosphere.io/viewLog.html?buildId=77099&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:02:15


what is PHANT args is not set? you need to check for that.


Где твои остальные коммты - после этого?!


Added random word on front page


See, isn't that nicer? :+1:


i'm guessing the seeds file won't work if you try to run it.  you're going to get an error message saying undefined local variable or method "advertisements".

Also, none of the advertisements you're creating will have prices.  We probably want them to have prices so we can simulate real data.


dis is dis


does this show page work?


TeamCity TripleA :: UnitTest [Build 125](http://188.177.191.210/viewLog.html?buildId=193&buildTypeId=TripleA_UnitTest&guest=1) is now running


Yup you're right. I meant to do the same thing I did with PrintLang which was also wrong, because I assumed each command was appending to the output with data other than the result of evaluation.


Part of #5734 I should add


I had started that way. I separated this because the variable filling is
going to get more complicated. The variables can be filled using the config
object and other sources as well.

On Tue, Nov 17, 2015 at 12:34 PM, dspattison-google <
notifications@github.com> wrote:

> i think this can be combined with expandRequests_; you'll just need to
> pass it the object of known variables
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/avimehta/amphtml/commit/b0904809aee126fd77950df95415598eeef0f248#commitcomment-14454860>
> .
>


TeamCity TripleA :: UnitTest [Build 125](http://188.177.191.210/viewLog.html?buildId=193&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:45


I was thinking that if we assume that the application name is used to create a new directory then we should very rarely ever have existing files (we would never have them if we ensured that the application directory itself had to be new).


we should test if it can respond to the :price attribute as well


Don't need to. Will fix in next commit.

On Tue, Nov 17, 2015 at 12:32 PM, dspattison-google <
notifications@github.com> wrote:

> why do you need to copy it?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/avimehta/amphtml/commit/b0904809aee126fd77950df95415598eeef0f248#commitcomment-14454820>
> .
>


This is probably most useful in case of custom tags. Will keep it around
but can remove if it gets unwieldy.

On Tue, Nov 17, 2015 at 12:46 PM, dspattison-google <
notifications@github.com> wrote:

> it is a lot of extra work to make recursive requests. maybe just drop
> that? if you want to keep it, Please add this to the design doc. I see the
> Intent has it in the example.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/avimehta/amphtml/commit/b0904809aee126fd77950df95415598eeef0f248#commitcomment-14455087>
> .
>


This looks like a good change. :+1:


I am following how it is set in jscs so that it works the same here. Yes if it equals any of "false" or "null"  then the rule should be disabled like it does in jscs.


`tap --coverage --reporter=spec --timeout=150`


No need for tap-spec anymore, the one built into tap is good.


I don't know if this is quite right. Sometimes the "clientInfo" is a value that's used in composing a message on the client rather than a full message in and of itself. I'd keep this out of SimpleRequestCallback **or** alternatively add a constructor parameter asking SimpleRequestCallback explicitly to use clientInfo as an alternate error message.


Необходимо добавить комментарии и шапку описания модуля с кратким описание работы, назначения, портов, назначения параметров и т.д.


@Cybermaxke

This mimics Vanilla's structure. Has no bearing on AI.


5321-GroundDomain_RDD (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (894 of 894 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-25.13%25-green.svg)


hey

you can re-enable the colours via gui.STYLE.withColours -- i got a bit
tired of looking at them so i reverted to greyscale, but didn't have time
to find a more pleasant theme.

yes, the scanlines should be accurate, with these caveats:
  -  i read&draw them every 100 samples (that was just a random number i
picked, didn't really experiment)
  - there is some latency of actually putting them on the screen by which
time the sound would have moved further
  - finally, at higher iterations, there are far more samples then there
are pixels on the screen -- so i suspect there is always some mismatch /
uncertainty between what we see and hear.

but if you think the uncorrelated moments you're noticing aren't explained
by these, then i'm curious about what else it could be of course.

also: though there is undeniably an audio-visual relationship between the
pattern we control and the fractal pattern we generate&sonify, i don't
actually think the latter helps a great deal about revealing or predicting
something about the sound.

next time i have some time, i'm going to explore different ways of
visualising the sound.

On Tue, Nov 17, 2015 at 9:51 PM, Louis Pilfold <notifications@github.com>
wrote:

> Those lines are really cool. What happened to the colours?
>
> Are the lines entirely accurate? Occasionally I seemed to get sounds that
> didn't really correlate with what was happening on screen.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AVUIs/cantor-dust/commit/08d65cf66b54e17cb0ed395a07d41d4579926f06#commitcomment-14456639>
> .
>


if the save fails, we need to redirect or render something for the user as a fallback.


same here...we need to have a redirect or render


showErrorMessage has an overlay that let's you pass a control to be focused after it's dismissed.


Sounds good -- I think I'll go the route of making a new constructor parameter.


I agree on using AblyAuthException. About removing the conditional, I'm not sure that the only use case that could raise an AblyAuthException here is this one, I would rather be safe.


train = train here fixed our "can't find 'end.dep'' problem


we probably want to replace this text with an edit form like our other resources


TeamCity TripleA :: UnitTest [Build 126](http://188.177.191.210/viewLog.html?buildId=194&buildTypeId=TripleA_UnitTest&guest=1) is now running


similarly, lets replace this text with a more typical index view like our other resources


and a new form


My bad, we do need JS - but it seems not for redirecting (can do that without JS) but to auto-save before opening pedigree. If auto-save could be done without JS, we would not need JS I think


I see. Then +1 when "no pedigree image & no edit rights -> hide pedigree section" is fixed


sort by CustomerID since we're binding and not joining


we should create this question with some real data for our tests


I'm a little bit torn on this one because as a user I find it really annoying that e.g. this fails (for `devtools`, but highlights the bit of tension, I think):

```sh
mkdir foo
R -e "devtools::create('foo')"
```


Sort basetable by CustomerID since we're binding and not joining.


Ich weiss ned, was gnau dis problem isch, aber das vereifacht de code insofern, dass de iterator implizit gä isch im hindergrund ohni dasses en explizit im code brucht.


Seems like the “of” here is superfluous?


at this speed, the crossings of the scanline and the beats looks/sounds
pretty faithful:

http://localhost:3333/#STATE:%5Bnull,null,null,%7B%22iterations%22:7,%22pattern%22:%5B0.8900000000000003,0.5,0.5,0.5%5D,%22pitch%22:0.0220970869120796,%22phase%22:16383.177984289669%7D%5D

can you isolate a case where it doesn't and send a url?

On Tue, Nov 17, 2015 at 10:07 PM, Berkan Eskikaya <berkan.eskikaya@gmail.com
> wrote:

> hey
>
> you can re-enable the colours via gui.STYLE.withColours -- i got a bit
> tired of looking at them so i reverted to greyscale, but didn't have time
> to find a more pleasant theme.
>
> yes, the scanlines should be accurate, with these caveats:
>   -  i read&draw them every 100 samples (that was just a random number i
> picked, didn't really experiment)
>   - there is some latency of actually putting them on the screen by which
> time the sound would have moved further
>   - finally, at higher iterations, there are far more samples then there
> are pixels on the screen -- so i suspect there is always some mismatch /
> uncertainty between what we see and hear.
>
> but if you think the uncorrelated moments you're noticing aren't explained
> by these, then i'm curious about what else it could be of course.
>
> also: though there is undeniably an audio-visual relationship between the
> pattern we control and the fractal pattern we generate&sonify, i don't
> actually think the latter helps a great deal about revealing or predicting
> something about the sound.
>
> next time i have some time, i'm going to explore different ways of
> visualising the sound.
>
> On Tue, Nov 17, 2015 at 9:51 PM, Louis Pilfold <notifications@github.com>
> wrote:
>
>> Those lines are really cool. What happened to the colours?
>>
>> Are the lines entirely accurate? Occasionally I seemed to get sounds that
>> didn't really correlate with what was happening on screen.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/AVUIs/cantor-dust/commit/08d65cf66b54e17cb0ed395a07d41d4579926f06#commitcomment-14456639>
>> .
>>
>
>


TeamCity TripleA :: UnitTest [Build 126](http://188.177.191.210/viewLog.html?buildId=194&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:01:49


You killed my changes =(


You might want to put the changes to this file in the previous commit.


I missed that -- thanks!


@unho please see comment in flowdock asap 8)


https skal være up and running nå! \o/
Er bare mange eksterne ressurser som går rett mot http som da ikke lastes i diverse apps, som må fikses etter hvert.


+1 cf67471


It worked for me, but it's a hacky fix.  You need to determine what instance of jQuery is getting the `daterangepicker` function/plugin assigned to it.  This only helps in the case that there's a `window.jQuery` already in scope before importing `react-bootstrap-daterangepicker`.  Otherwise it uses the `$` imported with this module.  Maybe you can provide a gist showing your use-case?  This has been merged in the original repo, so are you running 1.0.5? (they just bumped the npm version)


I have a sneaky suspicion that either this, or a3e3506c00c0a68a72641209623c0b65a9da9785 might be responsible for the appveyor win64 timeouts we've been seeing so much of lately


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5594](https://teamcity.mesosphere.io/viewLog.html?buildId=77100&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 0, ignored: 199 Build time: 00:13:04
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity TripleA :: UnitTest [Build 127](http://188.177.191.210/viewLog.html?buildId=195&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 127](http://188.177.191.210/viewLog.html?buildId=195&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:30


TeamCity TripleA :: UnitTest [Build 128](http://188.177.191.210/viewLog.html?buildId=196&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 128](http://188.177.191.210/viewLog.html?buildId=196&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:32


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5595](https://teamcity.mesosphere.io/viewLog.html?buildId=77106&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:57


I've been using "Charger Doctor" - http://amzn.to/1MQN1Ki

I order a couple of them so I can see both in incoming V&A to the RPi as well as look at the V&A going to any USB connected device.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5587](https://teamcity.mesosphere.io/viewLog.html?buildId=77075&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:45:21


cpsc312 Project1 Starter Files/312-pess-grammar.pl

we need to put this change back


@corsmith is looking at it tonight as time permits.


we need to put this change back


How did that end up on that branch? :)

I'll fix it.


TeamCity TripleA :: UnitTest [Build 129](http://188.177.191.210/viewLog.html?buildId=197&buildTypeId=TripleA_UnitTest&guest=1) is now running


Still cannot mount /system !
surdu@root:~$ adb shell "mount -o remount,rw /system"
mount: '/dev/block/bootdevice/by-name/system'->'/system': Permission denied

Anyway thanks for your help !


TeamCity TripleA :: UnitTest [Build 129](http://188.177.191.210/viewLog.html?buildId=197&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:29


should we check if ```recovered_v == v```?


This should be some type of Exception


The screen looks like that:

![screenshot_2015-11-18-00-12-58](https://cloud.githubusercontent.com/assets/15831041/11226666/0abcedba-8d8a-11e5-83a6-02b789f86788.png)


Returning a connection type is fine, one object instead of two. In R, the connection is a global variable if you assign it; without the assignment.

For me, as long as the variable can be changed/accessed, I'm fine with whatever. In the Hadoop use case, the IP/Port is always different, so it's convenient to be able to quickly print it out.

> On Nov 17, 2015, at 4:28 PM, Christof Stocker <notifications@github.com> wrote:
>
> Why do we need global variables. I think we should avoid those where possible. I suggest we should return a type that contains this kind of information. AFAIK R does that too reference
>
> —
> Reply to this email directly or view it on GitHub.
>


@EdHurtig You might want to also remove this from the kitchen yaml


For my own edification, is there something wrong with Marshal::dump/load?


Devin, do you know what compilers are affected by this issue? Is it an issue you discovered when you started doing the 64-bit builds, or does it affect 32-bit builds?


And I don't think that's a helpful error message.  How about "Cannot save %s to config.  Only values that can be
successfully evaluated are allowed"?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5597](https://teamcity.mesosphere.io/viewLog.html?buildId=77108&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:20


TeamCity TripleA :: UnitTest [Build 130](http://188.177.191.210/viewLog.html?buildId=198&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 130](http://188.177.191.210/viewLog.html?buildId=198&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:26


Not everything is used in the extension that the app drawBot requires

On Tuesday, 17 November 2015, Adrien Tétar <notifications@github.com> wrote:

> I think you could use a submodule for this, FWIW.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/typemytype/drawBotRoboFontExtension/commit/652573e4d0c1c97924ba8814db8082b2fe0f72ae#commitcomment-14456825>
> .
>

--
gr Frederik
www.typemytype.com


So the reason your animation isn't working is because the path to the animate.css file is incorrect. Remember the paths are relative to the actual file. In this case, your animate.css file is in css/animate.css. Also, the filename you're using is incorrect based on what's in your current css folder.


graaficas con chatjs


lgtm


Hi,

    I'm sorry but sortbydiscount does not work at all, can you please check and give advice to see how's working?

thank you,


How come this now?


LGTM


Nit: incur -> occur


Nit: `a inclusivity` -> `an inclusivity`


yes, this would be an easy one to cherry-pick onto master


Before committing code, ensure you're not adding unintended changes. The `.sass-cache folder` and `Gemfile.lock` file are not necessary.


BTW maybe the bug about scrolling can be closed, I don't see it anymore.
Apart from this it's more a feeling rather than actual measurament, but files (even small ones) take around 1 second to open, switching desktops on linux makes spyder refresh the editor and it takes another second. There is also the problem about autocompletion which sometimes creates small freezes.
I'd like to try profiling the repaint function(s), but I don't know how yet.


a3e3506 is unix-only changes, so i think you can quickly rule that one out


that line was the one I meant and you fixed it properly


this line was ok as is without the sprintf. sorry for the confusion


`|direction|`


The empty string case is a bit tricky to understand for a thrown exception. Could we have an additional error to cover this?


Why did you switch the default encoding to CP1252? We want JabRef 3.0 be modern and have UTF-8 as default. The current latex tooling is UTF8 capable.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5596](https://teamcity.mesosphere.io/viewLog.html?buildId=77107&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:05
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


namiesto > ma byt >=
#if (OPENSCENEGRAPH_MAJOR_VERSION>=3 && OPENSCENEGRAPH_MINOR_VERSION>=2)


This is not how bower installs this dependency for me, and I've tried many times to re-install. What version of bower are you using?


remove this


:+1: yes, thank you


The appveyor also freeze sometimes before the build starts which would not be something on oir side.


Why is the ` && !isArray(nextSegment` necessary if we already know that it's a stringmap.


:hankey:


I would put this things maybe in a wiki in the Github repo ;)


What happens now when you press the `X` when in _Add Family_ form triggered from the LHS action bar?


I think the bug that's being fixed here is that the src arrays are not symmetric.  This patch fixes that differently from how the bug was fixed upstream.  Upstream, the src and dest arrays are not exchanged; src arrays have just been marked as static, making them symmetric.


Right, some of them are clearly AppVeyor issues, but for the ones that have the characteristic behavior where one of the test workers freezes early on, but the other completes all remaining tests - that looks more like a Julia bug.


let


technically, the `presence: true` part of this validation is redundant.  Because you're require the name to have at least 5 characters, it can't be 0 characters and therefore must be present.  If you wanted to allow nil, but require a minimum length if it's present, you can pass an option `allow_nil: true`.


The int8 test is supposed to test shmem_get8.  This change seems incorrect.


Do we really need these nonsense sections? It's clear from the signature that the function takes no arguments, and in the doc it's also clear. Or does Spinx complain?


Hello. The problem is that we currently base our hostOS on fido yocto (13.0.0) which doesn't have this patch. Would you be able to use that specific tag?


This loop could use some comments. It's tricky to understand with all the array indexing that's going on.


Not the right fix.  Fixed upstream with shmem_get8().


Why?


Texture loading fix confirmed as working.


TeamCity TripleA :: UnitTest [Build 131](http://188.177.191.210/viewLog.html?buildId=199&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 131](http://188.177.191.210/viewLog.html?buildId=199&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\CashRegister\CashRegister.csproj (new); number of tests is too small: 0 (new) Build time: 00:00:04


You see the LHS contact list again. `$state.go('contacts.detail', { id: null })` is effectively the same as clicking the tab at the top of the page.


cool!


I'll move this discussion in the pull request.


saw approval from erikleitch
at https://github.com/basho/riak_pb/commit/cf67471cafb52dacae5e3b9347ad93ed5220c569


merging basho/riak_pb/feature/az/ts-list_keys = cf67471c into borshop-integration-162-feature/az/ts-list_keys


basho/riak_pb/feature/az/ts-list_keys = cf67471c merged ok, testing candidate = e7ad7292


@justinedelson do we need to flush here? appears this commits the response.

/cc @andrewmkhoury


Hello @lwahlmeier , please take a look at the wrapDate method in javax-net-ssl.cpp
I'm going to figure out how to test it.
@d2chau @flipontheradio @longcinusa


Perhaps. But who reads a wiki?!


fixes issue #15


why?


I initially thought it was a gcc 4.9.2 / 4.9.3 issue (which I had updated to from 4.9.1 when starting the 64-bit builds, though it also affected 32-bit builds as well). Then I reverted to the last MinGW-builds release to be based on 4.9.1 and the issue persisted. I don't remember exactly which MinGW-builds release I was using before (but it was one of the 32-bit dwarf-2 versions, which doesn't seem like it should have made a difference...)

As for symptoms, keyboard and mouse input through the rawinput driver are effectively completely ignored when *any* optimization level is used, but I didn't have time to puzzle out exactly what the cause was other than having optimization enabled.


this gets fixed in my latest commit when I pull in upstream changes


why did you take out thingz


ich bin dagegen für die triviale 3er Option vom Django Standard abzuweichen, eine unnötige extra Abhängigkeit (django-enumfield) einzubauen und zudem diesen in der Datenbank mit einem schwer interpretierbaren Integerwert zu speichern. Dem stehen keinerlei Vorteile gegenüber. KISS

Kosmetische Änderungen zu diesem Zeitpunkt stören zu diesem Zeitpunkt nur beim mergen. Abgesehen davon ist das nicht mein Codingstyle.


Is there value in keeping the Docker stuff around at all? This file was introduced with all the changes supporting Docker in mid July. Is it still needed?


This was introduced by a bad merge. I've submitted a fix that includes the RestorePackages property back to the file.


I was seeing test failures where the previous run’s databases were still around. Making sure we always started clean solved things.

Perhaps terminating the process doesn’t run cleanup? Unplugging the device, for example.


Python 2 Unterstützung kann ich nicht schaden, aber wenn man downgraden will, ist "from __future__ import unicode_literals" einfacher


TeamCity TripleA :: UnitTest [Build 132](http://188.177.191.210/viewLog.html?buildId=200&buildTypeId=TripleA_UnitTest&guest=1) is now running


As noted in the block comment above:

```

+// v8, 02c08ddc6d805d853bbe053884725dc971ef37d7. Favicons.
+//
+// v10, 4428c7d181ff4779ab1efb39e857e41bdbf4de67. Mirroring. We skipped v9.
```


TeamCity TripleA :: UnitTest [Build 132](http://188.177.191.210/viewLog.html?buildId=200&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:26


The barrier tests were dropped from the UH test suite in openshmem-org/tests-uh 899d856c7b0fe58c54669f9607f2c36f1e8ef36b.  Weird...


This is likely going to cause an error. React expects the array to be an array or elements versus objects.

```diff
render: function() {
+ const repos = this.props.repos.map(repo => <div>{repo.name}</div>)
render (
```


xit


Please revert. Look at the master branch (I fixed your tests and implemented the test). Also, please do not use this branch for developing tests


TeamCity Xbim :: Xbim Windows UI :: Xbim Windows UI [Build 55](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=489&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) is now running


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5599](https://teamcity.mesosphere.io/viewLog.html?buildId=77122&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:11
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity Xbim :: Xbim Windows UI :: Xbim Windows UI [Build 55](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=489&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:23


Fixed properly.  Had to move ' Exiting ...' to the next line to avoid pep8 warning.
```
                if not os.path.exists(config_dir):
                    logger.error('Unable to create config directory: {0}.'
                                 ' Exiting ...'.format(config_dir))
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5598](https://teamcity.mesosphere.io/viewLog.html?buildId=77112&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 143 (new)) Build time: 00:24:48


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5600](https://teamcity.mesosphere.io/viewLog.html?buildId=77131&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 143 (new)) Build time: 00:01:46


Anyway, here you're only adding up
    0.1823 * log(mc) / K[pv][1];
(whose upper bound is ~1.566) that has no dependency on d :-)


this is the value they use upstream


The backstory is that v9 lived in a branch, and I bumped to another version before it even merged. Sometimes I'm too thorough :)


> A compiler warning will be emitted to encourage people to check the return value. But they remain free to ignore it if they understand the implications and are confident in their protocol design.

This seems to be the way the CFRG is going with their new curve recommendations too, a MAY vs a MUST check. While it may not be necessary for X25519, I worry about implementers taking the wrong lessons from one curve implementation and applying them to another curve (ie: not checking for small order points). So I'm glad to see it here.

> I'm still not satisfied with having nothing but crypto_scalarmult() in the library in order to perform a key exchange. ...But all of that shouldn't be users' responsibility. We should probably introduce a higher-level API at some point.

Agreed. The ```scalarmult``` implementations are described in the docs as a Diffie-Hellman implementation, but I could see a higher-level api in the future that would be along the lines of ```secret_box``` in terms of simplicity and be a ECDH or just `key_exchange` best practice, with all the extra checks and specific nonce usage etc. taken care of.


You have to guess them, from the C header.  Also this is not exposed in the python API (I think).


I'm guessing these get fixed in the follow-up commits.


FYI @andy-armstrong. These are the spots you called out in the main PR, I'll add the test checks here once the logic is in place to verify it's working as expected.


Build 7 test results:  26 passed, 0 failed, 0 errored, 26 total Add example project


Maybe 'use'


Build 8 test results:  26 passed, 0 failed, 0 errored, 26 total Merge pull request #28 from buzzfeed/feature/example-project

Add example project


TeamCity TripleA :: UnitTest [Build 133](http://188.177.191.210/viewLog.html?buildId=201&buildTypeId=TripleA_UnitTest&guest=1) is now running


TeamCity TripleA :: UnitTest [Build 133](http://188.177.191.210/viewLog.html?buildId=201&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:25


It's accidental - probably because the units in my work with the Schafer lab code always used micron as units.  I'm happy to change the Python code to be millimetres.  I'll do this in my next pull request - thanks!


instead of mymodule, we can have a better name/location.


Hi, I see there's been a flurry of activity on pyBASEX (or pyABEL as I should call it now). I'll see if I can contribute something to the main codebase. I've been looking into the scaling issue as well, but don't have anything fundamental to report apart from the fact that the scaling factor is different (i.e. not 8.86) in my applications for some reason.

The transforms and basis sets generate and run just as fast now as before, but for my application I save a lot of time by separating the sets. When the transforms assumed up/down symmetry, I had to pass my images row-by-row, which took forever. With the decoupling of the horizontal and vertical cases, the generation of the horizontal sets is the same as before, while the vertical sets are much quicker (no need to do the forward Abel transform), and the actual transformation is practically instantaneous, even for very large images (1500 x 1500 or bigger).


这里可否为"斩杀阶段"之类的呢?

实际效果是这个样子:
Strategy Room -> Maps

![2015-11-17_174617_3360x1080_scrot](https://cloud.githubusercontent.com/assets/1096354/11227306/359b15ca-8d53-11e5-87a7-ec46dbabcc5a.png)

看文字总觉得有点已经斩杀了的意思.


hmm may wanna make this a constant


the 57


This looks a little odd: should we have WT_TEN_THOUSAND?


@peggyl if this repo is public, why did we switch to publishing it as a private package?


whyre you doing 57?


RegEx 2.0 and cheatsheet http://regexr.com/


this is what I get for not testing locally


Yes, the dockerfile item template still works


Du meinst also bei Aufgabe a die ```b^*``` davor und dahinter sollen entfernt werden.


rephrase to "on the output columns of ``UNNEST``"


```
Uncaught Exception:
TypeError: Cannot set property 'checked' of undefined
    at EventEmitter.<anonymous> (Mancy/build/main/MancyApplication.js:232:22)
    at emitTwo (events.js:87:13)
    at EventEmitter.emit (events.js:172:7)
    at EventEmitter.<anonymous> (Mancy/node_modules/electron-prebuilt/dist/resources/atom.asar/browser/api/lib/web-contents.js:85:27)
    at emitTwo (events.js:87:13)
    at EventEmitter.emit (events.js:172:7)
```


Boa noite, tudo certo?
Estou realizando e separando todo projeto colocando em um padrão conforme citado abaixo;
Não estou conseguindo realizar acesso ao banco de dados, pois falta tratamentos. Você tem estes métodos dos formulários .form ? que realiza a parte de inserir, excluir, alterar, reconsulta?

•Conexao –
Conexão com o banco(endereço)

•Principal
– Abrirá o jFmenu com
as opções

•DaoTabelas – Metodos /SQL
– Acessa banco

•Formularios –
Parte gráfica

•Tabelas
– Set e Get de
cada tabela
Aguardo retorno.

Date: Sat, 7 Nov 2015 12:52:30 -0800
From: notifications@github.com
To: Consultorio@noreply.github.com
CC: william_psy_@hotmail.com
Subject: Re: [Consultorio] fase 4 - conexão com banco de dados (62d1354)

Respondido por email

—
Reply to this email directly or view it on GitHub.


True. But it gets it wrong and will break come JDK 1.80 :-)


@rgarcia I don't remember the details why, but I think it might have been to avoid a naming conflict with https://www.npmjs.com/package/discovery.


Import not used


I think this was supposed to be in the integers section. It doesn't look like a special note is needed, as there is an explicit range defined. Not sure where those 53s came from...


fuck


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5601](https://teamcity.mesosphere.io/viewLog.html?buildId=77133&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:13:42


WrappedException not used


Il n'y a rien de décimal dans les bits, c'est tout en base 2


Only `Map` is used.


I think for using clockwork correctly you need wrap each task separately in the `every` time syntax.  But perhaps you can confirm this.


Oops

On 18:25, Tue, 17 Nov 2015 Geraint White <notifications@github.com> wrote:

> Why is this in multiplayer?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/itsapi/pycraft/commit/602fc428256956cc8d940a348a6fcddf82cd3164#commitcomment-14451575>
> .
>


It might fail if keystonerc_admin is not present. Is there anything we can do for this? Or, in the controller_common.pp, add a dependency of keystonerc_admin file.

class {'moc_openstack::keystone_all_semodule':
  require => [something-here],
}


TeamCity TripleA :: UnitTest [Build 134](http://188.177.191.210/viewLog.html?buildId=202&buildTypeId=TripleA_UnitTest&guest=1) is now running


False alarm, just a strange way to report a syntax error on shvset string


@francesco-romano `Zeros` are no longer used.
They have been replaced by `CalibrationZero` and `CalibrationDelta` parameters (in the `calibrators` folder). User should edit only `CalibrationDelta`.


TeamCity TripleA :: UnitTest [Build 134](http://188.177.191.210/viewLog.html?buildId=202&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Compilation error: Software\TripleA\CashRegister.Test.Unit\CashRegister.Test.Unit.csproj (new); number of tests is too small: 0 (new) Build time: 00:00:07


Ah, looks like we got some tabs in here; can you refactor to use two spaces instead?


Вообще, чем меньше привязок к особенностям доменов, тем лучше.


Дурным, не дурным, а на куче борд такая привязка есть. Плюс нужно точно
знать когда загрузка капчи завершилась, а без подобного кода там костыли
покруче будут, вроде MutationObserver, которые ещё и в некре не работают, а
с аналогами страница будет дико тормозить.

18 ноября 2015 г., 1:57 пользователь Sthephan Shi <notifications@github.com>
написал:

> Да ну нафиг. Не хватало обезъяньего кода здесь. Я считаю дурным тоном так
> привязываться к борде.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Y0ba/Dollchan-Extension-Tools/commit/2b01966b680c13f2b7a272fa5abf5b7e1221c0f0#commitcomment-14458019>
> .
>


`ResolvedInstruction` not used


`Instruction` not used


Nobody disputed it was faster, the dispute was whether or not that micro-optimization matters in the grand scheme of this source not being big enough for it to matter.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5603](https://teamcity.mesosphere.io/viewLog.html?buildId=77134&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 199 Build time: 00:04:28


Sweet I understand how the tests work now :)


TeamCity TripleA :: UnitTest [Build 135](http://188.177.191.210/viewLog.html?buildId=203&buildTypeId=TripleA_UnitTest&guest=1) is now running


It was leftover from a previous commit...sorry it got mixed up.  I need this for the SymbolLayer..uh...symbol :)


5321-GroundDomain_RDD (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1429 of 1432 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.79%25-yellow.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-70.43%25-green.svg)


TeamCity TripleA :: UnitTest [Build 135](http://188.177.191.210/viewLog.html?buildId=203&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:25


Case 1: White d5 and Nc4, Black d6
 d6 cannot force the Nc4 out, since blocked by a pawn on d5
Case 2: Black Nc4 and Bd5, White c3 and d4
 c3 cannot force the Bd5 out, since blocked by a piece on c4

a) testing Case 1 + Case 2 is not great
    http://tests.stockfishchess.org/tests/view/5647f0530ebc5902cdc08174
b) testing Case 1 only seems worse
http://tests.stockfishchess.org/tests/view/564b84c10ebc5902cdc08248
c) Maybe testing Case 2 alone will give something.


commit those `node_modules`!


"PositionWithin" and update comment for behaviour.


Вот и плохо, что она много где есть. Потому что весь этот груз костылей трудно отслеживать.

> точно знать когда загрузка капчи завершилась

Пардон, зачем? Раньше это не было нужно.


The expectation here is that it will panic. We don't need to do anything about that. The comment can go away.


return (pos int, ok bool)


@kwonye since this is a `strong` reference, the `addSiteAlertController` will be retained even after it is dismissed later. Might suggest a `weak` reference instead, or cleanup with `= nil`.


TeamCity Xbim :: Xbim Windows UI :: Xbim Windows UI [Build 56](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=490&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) is now running


Quick point, simply as something to bear in mind: It is important to remember that while chartered working groups operate autonomously within the Node.js governance model, the public perception of Node.js is that the project is one whole body. Actions taken autonomously by this WG, or even individual members of this WG, will be viewed as "The Node.js Project" taking those actions. We can see evidence of this in the recent trolling behavior and comments around it.

Individuals operating within a Node.js Working Group (*any* working group) need to keep this thought in mind before any potentially controversial action is taken (and yes, I'm speaking to myself here as well). Ensuring an open communication process that encourages open collaboration with the entire base of collaborators *does not* limit the autonomy of the Working Group to take actions it feels it should take; but it *does* help the Working Group to understand the positive or negative impact those decisions may have on the project as a whole.


TeamCity Xbim :: Xbim Windows UI :: Xbim Windows UI [Build 56](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=490&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) outcome was **SUCCESS**
Summary: Running Build time: 00:00:58


En este caso "como" no lleva tilde, en general en pregunta o exclamación. Mira http://blog.lengua-e.com/2012/como-y-como/

Document Ready: Prefiero introducir el término en español en el título y que se explique su relación con $('document').ready() en la explicación.

En general tag lo traduzco como etiqueta.   script lo traduzco como programa.


@pmros Sorry about that. force pushing another commit


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5604](https://teamcity.mesosphere.io/viewLog.html?buildId=77137&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:05:43


looks good


test comment


develop (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2336 of 2370 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-98.57%25-yellow.svg)


i'm not sure i agree here. i think calling out that there is a focus on people from underrepresented groups is important.


people incur issues, people don't occur them
```
in·cur
become subject to (something unwelcome or unpleasant) as a result of one's own behavior or actions.
```


Should read `mp4a.40.5` in the comment not 1.


OUI J'AI PETE UN CÂBLE
Hard tab > Soft tab.

AND IT'S **MY** REPO, I DO WHAT I WANT TO DO


`message_id` of `0`? Is that correct?


5321-GroundDomain_RDD (mmatts) - Win64-Windows-7-VisualStudio-12: OK (1963 of 1968 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.75%25-yellow.svg)


`message_id` of `0`? That doesn't seem correct.


This is really puzzling me, because on my pc I see the correct capitalization on my local folder! Even more interestingly, if I try add another new file to this CORRECT folder, the commit log shows that a WRONG lowercase folder is used. I can only think that something got corrupted on my local repo, sorry...


I think it is worth it to keep, even though it requires some extra code.

Apart from the other servers sending it, clients do use it: for example, irssi replaces a bunch of ugly configuration options with TARGMAX values.


how about for(; src_index < src->capacity; ) { ... } This would prevent bad times in the case that, for example, all slices have length 0.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5602](https://teamcity.mesosphere.io/viewLog.html?buildId=77132&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 143 (new)) Build time: 00:28:52


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5605](https://teamcity.mesosphere.io/viewLog.html?buildId=77143&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:54


whoa. you read this far?

I'm not actively working off of this, but thanks for the heads up anyway!


LGTM other than the for(;;) comment


No - that is added by some JS in core/structure.js

This title is just because otherwise the new stylesheets put sheep across my screen for some reason.


LGTM other than seemingly spurious changes to gen_chttp2_stream_lists.py


Looks good to me


@romariorios @niltonvasques que delicia


You can do so by using almost that exact same language you just used in the comment. There is no need to try to enumerate what those underrepresented groups are, especially since by doing so you risk excluding groups you may not have considered originally or bikeshedding over specific terminology. There are benefits to being concise.


Whoops, yes, you're right, of course. I misread it as the backlash occurring, not the backlash being incurred by others.


Class UpdateGitMirror is missing a docblock.


* TODO: rewrite this as it is doing way too much and is very messy now.


// FIXME: Delete tar file if it exists


exit 0 # FIXME: Not sure why I need this, otherwise it fails


I recommend against using patches from our (KoNode's) fork -- some of them break features in order to get the exact behaviour we're after (as you've noticed).  We're doing our best to submit the useful changes to upstream :)


I'm going to suggest rewording it. incur / occur may be confusing to non native English speakers


Al igual que en https://developer.mozilla.org/es/docs/Web/HTML/Elemento  traduzco "tag" como "etiqueta", haciendo  referencia bien a una de apertura (como <script>) o a una de cierre (como </script>)  mientras que traduzco "element" como elemento haciendo referencia a un nodo completo del árbol del documento HTML, que incluye con etiquetas y contenido (e.g <script>alert(1)</script>).


Fixed in 2136b17


Si se lee mejor.


Look's like this is just a cleanup of the whitespace formatting?


all_ships = {
    "Yours generated"    :
    "Hermes"             :
    "Ares"               :
    "Zeus"               :
    "Agressive Marketing":
    "Contract Negotiator":
    "Buyer's Remorse"    :
    "Serpentine"         :
    "Cobra"              :
    "Aliriki's Wrath"    :
    "Homeward Bound"     :
    "Sandersons_Claws"  :
    "Caveat_Emptor"      :
    "Zippy Ralpheta"     :
    "Sally Jane"         :
    "Torentulus"         :
    }

#function to determine if the genreation will be used.
determine1 = input("What ship do you want? Enter 1 for a pregenerated ship, or 2 to make your own ship.")
if determine1 == "1":
    determine2 = input("Enter 1 for a Terran ship, 2 for a corperate ship, 3 for a alien ship, 4 for a trader ship and 5 for a corsair ship"
    if determine2 == 1:
        determine3 = input("Enter 1 for a battlecruiser and 2 for a patrol ship.")
        if determine3 == 1:
            YourShip = Hermes
        elif determine3 == 2:
            YourShip = Ares
        else
            determine3 = input("Enter 1 for a battlecruiser and 2 for a patrol ship.")
    elif determine2 == 2:
        determine3 = input("Enter 1 for a security ship and 2 for a factory ship.")
        if determine3 == 1:
            YourShip = Agressive Marketing
        elif determine3 == 2:
            YourShip = Contract Negotiator
        else
            determine3 = input("Enter 1 for a security ship and 2 for a factory ship.")
    elif determine2 == 3:
        determine3 = input("Enter 1 for a harassment ship and 2 for an attack ship.")
        if determine3 == 1:
            YourShip = Serpentine
        elif determine3 == 2:
            YourShip = Cobra
        else
            determine3 = input("Enter 1 for a harassment ship and 2 for an attack ship.")
    elif determine2 == 4:
        determine3 = input("Enter 1 for a merc ship or 2 for a freighter.")
            if determine3 == 1:
                YourShip = Sandersons claws
            elif determine3 == 2:
                YourShip = Homeward_Bound
    elif determine2 == 5:
        determine3 = input("Enter 1 for a gunship and 2 for a cruiser")
        if determine3 == 1:
            YourShip = Sally_Jane
        elif determine3 == 2:
            YourShip = Zippy Ralpheta
        else
            determine3 = input("Enter 1 for a gunship and 2 for a cruiser")
else
    determine1 = input("What ship do you want? Enter 1 for a pregenerated ship, or 2 to make your own ship.")


I don't know why I typed that summary, but the icons will all keep the same font. There's no point in making them all into their own.


TeamCity TripleA :: UnitTest [Build 136](http://188.177.191.210/viewLog.html?buildId=204&buildTypeId=TripleA_UnitTest&guest=1) is now running


Oh, nice, thanks.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5606](https://teamcity.mesosphere.io/viewLog.html?buildId=77144&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:43


TeamCity TripleA :: UnitTest [Build 136](http://188.177.191.210/viewLog.html?buildId=204&buildTypeId=TripleA_UnitTest&guest=1) outcome was **FAILURE**
Summary: Tests failed: 2 (2 new), passed: 50 Build time: 00:00:27
### Failed tests
```
CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_CallingAddProductOrderController_OrderControllerAddingProductIsCalled: <no details avaliable>

CashRegister.Test.Unit.dll: CashRegister.Test.Unit.Sales.SalesControllerUnitTest.SalesController_RemoveProductFromOrderList_OrderControllerAddingProductIsCalled: <no details avaliable>

```


I just realised that this adds the method to the OpenColorIOTransform base class - I think perhaps it would make more sense to put it on the ColorSpace node, closest to where the values are needed.


The committers and contributors list are not correct.  See http://incubator.apache.org/projects/trafodion.html for the most up to date list of mentors and committers.  It is unfortunate that these lists exist in different repositories making it necessary to keep two copies and do separate updates.  This means that the lists will be out of sync at times.
Also, need to get the current list of contributors.


Si de acuerdo con que pongas.
Escribo en español, pero agrego entre paréntis ayudas en inglés para vincular con el contenido del desafio.


// FIXME: Delete tar file if it exists


Just so I can convince myself that this is correct, is this documented anywhere else? Or how should I test this myself?


This is not necessary, I will remove the change.


fixed in b9d4e79


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5607](https://teamcity.mesosphere.io/viewLog.html?buildId=77145&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:01:46


En otras parte traduzco target (refiriendose a lo que llegan los selectores de jquery) como Elige, voy a emplear este término en todos los títulos más bien.  Gracias.


By and large, the website changes look good.  There are some changes I would like to see on existing pages - mostly editorial.  Will send these comments in a separate email.


Aww...


Good catch


pushed to master as 4e904a675cb1f4896ed1df8515fb536f233e2b2d


About to touch the RoomOverlay class oh dear....


Class UpdateGitMirror is missing a docblock.


Going to have to make some new classes :+1:


De acuerdo.


Estoy usando elegir.


Fixed in 06635f1


what? no... I just added this because of the YAJL call below.


Estoy usando elegir ahora.


Usando elegir de manera uniforme.


The issue I noticed occurs when a node loses leadership with `globalIndex` and `logIndex` both equal and the entry at that location in the log is a `NoOpEntry`.

In this state `AppendRequest` from the new leader will be rejected with the following error:

```
Rejected AppendRequest[term=2, leader=-1062706512, logIndex=5709, logTerm=1, entries=[1], commitIndex=0, globalIndex=0]: Request log term does not match local log term unknown for the same entry
```
This is because when this node tries to validate previous entry term, Log#get returns null since `NoOpEntry` was garbage collected. I wonder if major compactor should only be allowed to garbage collect entries upto `globalIndex - 1`? Or did I miss something?


Dejé "antes de la identificación"


Todo está redactado refiriendose al lector.  Cambié por
"haces que desaparezca"


I see. Publishing it privately nullifies a lot of the value of open sourcing it, which is a bummer.


The logic in the two big `try` blocks isn't right -- if any statement fails, it'll bounce to the `except` block. It would be better to make separate `try-except` statements for each variable.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5608](https://teamcity.mesosphere.io/viewLog.html?buildId=77151&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:05:03


@Fabrice7 In the following, I've started to describe in terms of RAML types (which exist since 1.0) how the JSON will look like. It's still incomplete, e.g., in line 54 I still need to flesh out how VAST types will look like in JSON. Even though it's not yet possible to generate a HTML page of this (the RAML toolchain has not caught up yet with 1.0 features), I think the document by itself already helps us quite a bit to agree on a common denominator.


Yup. `beffer.Write` makes two memory alocations.


As I'm going through the install process, I noticed that it's both tricky and crucial to copy both the HS address and fingerprint. Maybe we should still have them double verify the fingerprint except with the reason being human, not GPG error.


De acuerdo. Gracias.


The `generator_spec` gem uses ActiveSupport and Railties to permit testing of Rails generators using Rspec. As such, I needed to remove the namespace creation from the test because `::Rails` was already loaded into the context by the gem. The test remains and passes without the `before` and `after` step.


My preference is for less magic. I've changed it to reject those without a scheme.


Je veux dire le titre des chapitres :)

—
Sent from Mailbox

On Tue, Nov 17, 2015 at 1:31 PM, maximesab <notifications@github.com>
wrote:

> parties 8.7 et 5.1
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/maximesab/exo-info/commit/d94fcf2e28439c1d9918d496db039defa06ae027#commitcomment-14456119


@Fabrice7 So here you can see the new RAML type feature in action: by telling the spec that the result is of type `Result`, which is simply defined as `Event[]` in line 106 above, the exact structure of the corresponding JSON is well-defined.


Yeah sorry. I figured I needed to be honest about the status of the
project. I largely don't write python code any longer, and haven't managed
to find time to do even the simplest of maintenance tasks. I'm more than
happy for someone to fork the project and take over maintainance

On Wed, Nov 18, 2015 at 12:25 PM, Michael R. Bernstein <
notifications@github.com> wrote:

> Aww...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/brehaut/picoparse/commit/5e07c8e687a021bba58a5a2a76696c7a7ff35a1c#commitcomment-14458552>
> .
>


but but but
you always told us
test locally
how could you possibly
go against what you said
waaat


Massa! Achou onde?


Usando Elige de manera uniforme.


Me gusta más identificación.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5609](https://teamcity.mesosphere.io/viewLog.html?buildId=77153&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:46


Another thing that could follow here is the use of `gpg --edit-key` to set our key as ultimately trusted. That way GPG doesn't output potentially disconcerting errors later.


Si al en lugar de a el. Gracias.
Prefiero identificación.


@mbootsector Have you been testing or checking that idea?


@avram I'm gonna make all your dreams come true.


Bueno. Gracias.


Oh I see, this is supposed to be the same as the line before.


De acuerdo. Gracias.


LGTM


I think this needs to be updated to work on the appropriate databases, I'll do that in this PR.


De acuerdo.


This also needs to be updated to use multiple dbs.


Dejé "se volverá gris y no podrá pulsarse"


Thanks for fixing this!


Wow, Agda has display forms?


Get rid of this console.log?


`by_domain_doc_type/view` emits `[domain, doc_type]`
`domain/docs` emits `[domain, doc_type, date]`
So as long as only the first two are used, the views are interchangeable.


TeamCity LabkeyRelease15.3 :: CDS postgres 9.4 [Build 12](https://teamcity.labkey.org/viewLog.html?buildId=285815&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 15, passed: 10 Build time: 00:45:28
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSVisualizationTest: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyColorStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyDensePlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyTimeAxisWithMultipleSchedules: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAntigenBoxPlot: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBasic: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAxisSelectors: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyAntigenVariableSelector: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.CDSVisualizationTest.verifyLogAndLinearScales: <no details avaliable>

##### there are 5 more failed tests, see build details
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5610](https://teamcity.mesosphere.io/viewLog.html?buildId=77156&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:09:33


No problem. I posted some more thoughts in the issue. It took me a coupe days to find where your comment was, so I figured others might have a hard time finding it too :p


Considero que en este contexto "well" se refiere a pozo (que es la clase de un elemento div, pero no un elemento).  Agregué la traducción entre paréntesis


If ScrW() isn't used, why call it?


because I did test locally
I just forgot to run my tests


Not a big deal, but I think I would favor changing

features.filter(function(subDataset) {

to

features.filter(function(feature) {

I guess we have been using the variable name subDataset to describe the entries in the feature array in the context of some of our CreateTopojsonData scripts, but I think in a general context like this, feature is more appropriate.


We already have that for the wallet.


Como se está definiendo "encadenamiento" no conviene usar el mismo término para definirlo.


context_scheduler? ctx_sched like in cuda?


TeamCity TripleA :: UnitTest [Build 137](http://188.177.191.210/viewLog.html?buildId=205&buildTypeId=TripleA_UnitTest&guest=1) is now running


Usando elige de manera uniforme.


Did you mean to add hello world?


Note that you must not inline LINE_BUFFER_SIZE of data. The **total** length of a line must be at most LINE_BUFFER_SIZE. That includes username, linefeed, and hex or Base64 encoding wasting up to half of it.

BTW you should read #794 very carefully.


De acuerdo. Gracias.


TeamCity TripleA :: UnitTest [Build 137](http://188.177.191.210/viewLog.html?buildId=205&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:25


Just tell in which file too look at and maybe the first one, so people would easily find the section that define all of them.


Would you then also imagine a kill -HUP rereading the file?


(thumbsup) date picker dialog on new assignment activity

get the text from the name field in new assignment activity

get the text from the coursename field in the new assignment activity

get the date from the date picker in the new assignment activity

get the notes from the notes field in the new assignment activity

create an assignment object (public) out of all of the fields and pass it to the DB through AddAssignmentToAssignmentTable

Instructions for each activity on what to do and how to fill out (Exclude the overview activity and the mainactivity). Put all instructions at top and scoot everything
else down.

Home button on each activity to return to home screen.

Setup activity:

Add Course

Remove course

Reset course

Instructions: Input a course to have the course in the database.

Make setup activity look nicer


OK, I see you're doing fine here. Still, we should honor #794 with max default inline size and option to override it.


Hi,

This is what was in the pom.xml file. I just added my name to the list.
I'll update the pom.xml file to match the project page.

Thanks,

Gunnar

On Tue, Nov 17, 2015 at 4:23 PM, Roberta Marton <notifications@github.com>
wrote:

> The committers and contributors list are not correct. See
> http://incubator.apache.org/projects/trafodion.html for the most up to
> date list of mentors and committers. It is unfortunate that these lists
> exist in different repositories making it necessary to keep two copies and
> do separate updates. This means that the lists will be out of sync at times.
> Also, need to get the current list of contributors.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gtapper/incubator-trafodion/commit/81594fffe602a224c999c6edf1579d4a96c06c36#commitcomment-14458509>
> .
>

--
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*


La primera parte la deje como "Seguramente habrás entendido porque ".  La segunda la cambié de acuerdo a tu recomendación. Gracias.


:+1:

I almost spat my coffee over the keyboard. This made my day.


5321-GroundDomain_RDD (mmatts) - x86_64-MacOS-10.9-clang: OK (1957 of 1962 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.75%25-yellow.svg)


Hacking this way seems pretty dangerous. Becomes tricky when wish to re-enable. Is it possible to do some #define variable. Which can be easily grepped later and removed instead of just false.


So this is an issue. Not totally sure how CoordinateControl has a width and height to click but this doesn't.


I think [this](https://github.com/magnumripper/JohnTheRipper/issues/794#issuecomment-58934619) sums it up good.


Dejé "le asignarás". Gracias


Calling both ScrW and ScrH promotes equality.


Usando Elige de manera uniforme.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5611](https://teamcity.mesosphere.io/viewLog.html?buildId=77174&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 199 Build time: 00:04:53


Changes like this will break when used in versions of Jekyll less than 3.0. You should include a condition check for the Jekyll version if you wish to maintain backwards compatibility.


De acuerdo. Gracias.


Yay!

On Tue, Nov 17, 2015, 3:37 PM Anthony Grimes <notifications@github.com>
wrote:

> @avram <https://github.com/avram> I'm gonna make all your dreams come
> true.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/scopely/sqlquest/commit/1c6f2572b78efb7c80b4628bcc2287fdda26632e#commitcomment-14458790>
> .
>


We should get rid of the requirement that the topology must have 'countries' as a property name.


Thank you very much.  I prefer "Elegir" instead of "Apuntar" and "Referir".


TeamCity TripleA :: UnitTest [Build 138](http://188.177.191.210/viewLog.html?buildId=206&buildTypeId=TripleA_UnitTest&guest=1) is now running


Can you walk me through the logic of bailing out after adding the tx to inventory known?


Hm. Commit missing ?


TeamCity TripleA :: UnitTest [Build 138](http://188.177.191.210/viewLog.html?buildId=206&buildTypeId=TripleA_UnitTest&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 52 Build time: 00:00:24


I don't understand the purpose of this change, you bail out early when we're in blocks-only and not whitelisted above.


Ahh right. No I think you're totally right. This definitely needs to be implemented. I've seen that odd rejection of an AppendRequest before and never realized the cause.

Yeah this commit definitely wasn't a fix for that, it was just a fix for another potential problem (inconsistency in session expiration after leadership changes).

Actually, a similar restriction is already in place on log compaction. A segment can only be compacted if there's a non-empty segment with a committed entry later in the log. This ensures there aren't gaps in the log after compaction since one committed, uncompacted entry will always remain later in the log. You're right it seems the same needs to be done to ensure logIndex/logTerm can be checked in AppendRequest handling. I don't see any safety issues with this. Just like in log compaction where we slow down compaction by one entry, we're just making the globalIndex increase potentially one entry slower which is fine. Awesome catch! So glad that was figured out.

> On Nov 17, 2015, at 3:28 PM, Madan Jampani <notifications@github.com> wrote:
>
> The issue I noticed occurs when a node loses leadership with globalIndex and logIndex both equal and the entry at that location in the log is a NoOpEntry.
>
> In this state AppendRequest from the new leader will be rejected with the following error:
>
> Rejected AppendRequest[term=2, leader=-1062706512, logIndex=5709, logTerm=1, entries=[1], commitIndex=0, globalIndex=0]: Request log term does not match local log term unknown for the same entry
> This is because when this node tries to validate previous entry term, Log#get returns null since NoOpEntry was garbage collected. I wonder if major compactor should only be allowed to garbage collect entries upto globalIndex - 1? Or did I miss something?
>
> —
> Reply to this email directly or view it on GitHub.
>