[Wikipedia seems to prefer “Google Groups”][1] to “google groups”.

[1]: https://en.wikipedia.org/wiki/Google_Groups


I was not asking you to try and think of any exception the try/catch might catch, I was simply trying to explain how you should write new code, because this thread has gone on much longer than it should .. :p


I'm not sure what you mean; it looks like they're both on master...?


They are now. I swear they weren't a few minutes ago?


Never mind. It works and I don't know why.


Weird.

On Mon, Aug 10, 2015 at 2:02 PM, Tony Kelman <notifications@github.com>
wrote:

> They are now. I swear they weren't a few minutes ago?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/madeleineudell/SigmoidalProgramming.jl/commit/a6a8a5fd2ad336d7b932e20d493b0c35f6016664#commitcomment-12625301>
> .
>

--
Madeleine Udell
Postdoctoral Fellow at the Center for the Mathematics of Information
California Institute of Technology
www.stanford.edu/~udell
(415) 729-4115


Er, yeah. I should really add a commit hook to gripe about print statements.


thanks for updating the license option. i'll be adding it to the skeleton.


I have neither Linux nor OS X.


As a note, we do have [HHVM_REMOVE_MATCHES_FROM_LISTS](https://github.com/facebook/hhvm/blob/master/CMake/HPHPFunctions.cmake#L240) that makes doing this much shorter.

And, as a side note, Visual Studio and XCode targets won't show the header files in the targets if they aren't passed as sources to `add_library`, so it's best to add them when you do the initial configs :D

I'll submit a pair of PRs to adjust these two things later tonight. I'll also submit PRs to make these adjustments to the various other dependencies and add auto_source_group calls now that that PR has been merged into HHVM.


OK -- thinking about it I decided to go with the concurrent_unordered_map version. Seems less crazy in the end.


excellent javadocs. your api is now better documented than the rest of ours.


Random imports :smile_cat:


Not anymore. I changed the code that was using it.


I think that makes sense. Changing.


Current behavior is also to finish and restart remote requests, I should try using Retain Fragments so that these aren't killed because they don't need to be.


@inducer Ah, I didn't know that. Your fix looks good to me. Thanks!


Done. https://github.com/bitcoin/secp256k1/pull/287
(And removed from this PR.)


@willkuer
So why use libpng if this is a bitmap :P? Because is not, its included in resources as is, and as I see it is not included in Windows resources but in .rdata section. I think this is because png is converted to data array and saved to header file, then included in this file: https://github.com/PCSX2/pcsx2/blob/master/pcsx2/gui/AppRes.cpp and I think this is good idea, is portable.


That looks OK to me. I tested on a machine without GPU and on a machine with 1 GPU (during training it shows 0/1 GPUs available). One minor limitation is the fact that the status is not updated 'in real time' (i.e. without the page being refreshed). Would this limitation be removed in the job management page?

As a possible enhancement the information could be pushed through socketIO. Also maybe a new route could be created to expose this information through the REST API...


:-( you could always install Linux in a virtual machine I guess :-&


We want to remove `focus: true` before the final version of this is committed.


It's so pytest reports a better diff when the messages don't match. The only thing it changes is strings become unicode strings (which pytest reports as different, but `==` does not).


Main purpose of this commit is for debugging use - the thread pool hides some of the traceback when an exception is raised, even where number of threads = 1, making it hard to see why it didn't work. Hence the option of using a regular map in place of Pool.map.


Ahh... thanks for your explanations, I appreciate that you're helping me with this stuff :)


Ok, so please explain this in a comment ;)


These models were removed in 6c760b16968dd7d1fe75ba297e0c7a2a8fa365c7 and abd53cb4062c99849b4d3d88096bacea73b8712f.

Nothing to see here.  Move along.


:shipit:


I told emoose what games other games i had this issue with, all of them had Fmod in common, also it was fixed in later Fmod versions, http://www.fmod.org/files/revision_4.44.txt


see e.g. later commit where I do add various other projects...


Why is this an error? I usually allow empty blocks in my code as long as the author explains why they are empty regardless of what other blocks are present.


I tried to figure out what this could be, but did not find any similar ADDRMAN_..._COUNT.
Should I revert this?


TeamCity Ignite :: Ignite Cache 2 [Build 259](http://204.14.53.152/viewLog.html?buildId=59891&buildTypeId=Ignite_IgniteCache2&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 469, muted: 25 Build time: 00:23:56


TeamCity Ignite :: Ignite Cache Expiry Policy [Build 1162](http://204.14.53.152/viewLog.html?buildId=59894&buildTypeId=Ignite_IgniteCacheExpiryPolicy&guest=1) is now running


:+1:  looks good!


Looks fine. I'm crossing my fingers the fields don't change again :)


develop (axelstudios) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2189 of 2232 tests passed)

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


..and implements/copies `luaL_tolstring` for Lua 5.1?


hmm dunno.. but 100% good to have it ... but only if it'll not mess other things .. xD

That should minimize the mechanic stress on the mini-usb-port .. plug/unplug .... :-)


Fix #1


Don't forget appropriate method naming


Installer project is broken. Scripts updated some paths to use VS variable paths instead of ..\.

TODO: Improve install and package process using build server capabilities.


w00t w00t!


So needs a special git install?! Or custom configuration to our tests to pass?!

That doesn't seem right.  Git should not be changing files and making them OS dependent.

The test was originally test independent, but, due git changing the test_file the test become problematic.

or am I missing something?!

Also, if we go that way, everybody who ever decide to contribute to the project would need to reinstall git with some special non-default configuration.

IMO, you should reset this configuration and let files as they were.


this should be updated to libpng-1.5.23-1.cfg


The `else` block is empty and has no comment.


Вообще не уверен что `find`, `find_by`, `create`, `delete!` это методы Адаптера. Тут место для более низкоуровневых вещей, типа подготовка запроса, count(на месте), некая первичная обработка результата.


Curious, your style (reflected in the rest of the commit) tends to prefer breaking out imports `{ cloneElement }`, but here you've moved away from that style.  Any particular reason?


Changed [here](https://github.com/NetLogo/Tortoise/commit/78bf6f09f169e9b05ea3789f358f44812876bff8#diff-8b1c18f07745bba1d7fe7db3a8c867d3R51)


While you are probably right i am always careful using human logic to understand compilers...

That it is a png when it passes the library doesn't necessarily mean that it's saved as png at compile time or? Maybe it's converted before loading to png. I would at least guess compressing all images in one container is much more efficient than containern of compressed images.


TeamCity Ignite :: Ignite Cache [Build 1691](http://204.14.53.152/viewLog.html?buildId=59890&buildTypeId=Ignite_IgniteDataGrid&guest=1) outcome was **FAILURE**
Summary: Tests failed: 3 (3 new), passed: 512, muted: 76 Build time: 00:45:22
### Failed tests
```
org.apache.ignite.testsuites.IgniteCacheTestSuite: org.apache.ignite.cache.affinity.fair.IgniteFairAffinityDynamicCacheSelfTest.testStartStopCache: java.util.concurrent.TimeoutException: Test has been timed out [test=testStartStopCache, timeout=300000]
	at org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1596)
	at junit.framework.TestCase.runBare(TestCase.java:141)

org.apache.ignite.testsuites.IgniteCacheTestSuite: org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest.testReplicated: org.apache.ignite.IgniteCheckedException: Failed to find server node for cache (all affinity nodes have left the grid or cache was stopped): null
	at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6808)
	at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)

org.apache.ignite.testsuites.IgniteCacheWithIndexingTestSuite: org.apache.ignite.internal.processors.cache.ttl.CacheTtlOnheapAtomicPartitionedSelfTest.testDefaultTimeToLivePreload: junit.framework.AssertionFailedError: Unexpected size, node: 0 expected:<5> but was:<0>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

```


TeamCity Ignite :: Ignite Cache Failover [Build 1878](http://204.14.53.152/viewLog.html?buildId=59895&buildTypeId=Ignite_IgniteDataGridFailover&guest=1) is now running


TeamCity Ignite :: Ignite Cache 4 [Build 257](http://204.14.53.152/viewLog.html?buildId=59893&buildTypeId=Ignite_IgniteCache3_2&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 236, muted: 4 Build time: 00:20:10
### Failed tests
```
org.apache.ignite.testsuites.IgniteCacheTestSuite4: org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.testLocalClose: java.lang.IllegalStateException: Cache has been stopped: cache_local
	at org.apache.ignite.internal.processors.cache.GridCacheGateway.checkState(GridCacheGateway.java:83)
	at org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:173)

```


TeamCity Ignite :: Ignite Cache Failover Multi JVM [Build 111](http://204.14.53.152/viewLog.html?buildId=59896&buildTypeId=Ignite_IgniteCacheFailoverMultiJvm&guest=1) is now running


Maybe they should all return `Try` (instead of throwing `IllegalStateException`).


l g t m


#CodeSchool's NodeJs Tutorial: real-time-web-with-nodejs
[https://www.codeschool.com/courses/real-time-web-with-node-js](https://www.codeschool.com/courses/real-time-web-with-node-js)


It's technically possible, but not something I'd expect us to ever do. In general, anything that's an 'error' probably won't even have a signing severity, since they're expected to apply to anyone, listed or not.


develop (axelstudios) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Thanks, I'll have to look closer at the codebase to see what we can do in this regard. By the way your method can be achieved just by doing a cast instead of using `.map`:

```java
return (Observable<WatchEvent<T>>)(Observable<?>) from(file, null, kinds);
```


@peckomingo
Problem bei den Travis Test war nur ein Typo: 'sideFlag' statt 'sideflag'. Komischerweise lief das bei mir lokal aber problemlos so..


Update : previous builds 7000-7551 have been imported

2015-08-10 15:28 GMT+02:00 Dieter Adriaenssens <
dieter.adriaenssens@gmail.com>:

> Hi Alex,
>
> A few improvements to the charts :
> - pull_requests data is stored when build data is processed :
> build_trigger property
> - added a filter option to only show pull request build jobs
>
> I've also imported a few builds (7020-7100) around the build where you
> introduced the change :
>
> https://travis-ci.org/angular/angular/builds/72039309 : build 7042 : 18
> min
>
> On first sight, it seems that the changes in that PR reduced the buildtime
> to ~18min, for the following builds. Later today I'll import builds
> 7101-7551. Hopefully that will show in which build the improvement is
> undone.
>
> BTW : the builds between 7552 and about 8230 don't have build_trigger
> property, so they don't show up if you filter on pull-request. This is
> because they were imported before I introduced the feature to get
> pull_request data.
>
>
>
> 2015-08-06 20:59 GMT+02:00 Dieter Adriaenssens <
> dieter.adriaenssens@gmail.com>:
>
>>
>>
>> 2015-08-05 19:46 GMT+02:00 Alex Eagle <notifications@github.com>:
>>
>>> On Wed, Aug 5, 2015 at 9:57 AM Dieter Adriaenssens <
>>> notifications@github.com>
>>> wrote:
>>>
>>> > > Thanks, I just noticed that on our big screen and was playing. I
>>> don't
>>> > > understand why our dart stable build seems tri-modal (four if you
>>> count
>>> > > fast failures).
>>> > >
>>> >
>>> > I've added a filter for build results, so now you can filter out the
>>> > failures.
>>> >
>>> >
>>> > > Bigger problem is the graph doesn't go back far enough in history to
>>> show
>>> > > me when the time increased.
>>> > >
>>> >
>>> > Do you have a rough idea how long ago you were still seeing the 18
>>> minute
>>> > builds?
>>> > I can manually import some older builds, if you like. But let me first
>>> > change the code so it save if it is a PR.
>>> >
>>>
>>> It was 15 days ago when I'm sure it was 18m
>>> https://github.com/angular/angular/pull/3174
>>> but we only started sending you the data 9 days ago:
>>> https://github.com/angular/angular/pull/3302
>>>
>>> Actually I think it would be a really useful feature if you could use the
>>> travis API to backfill data for the time period before the webhook was
>>> added. Most users of this thing are probably adding it because they
>>> already
>>> have a problem, and you won't be able to solve that problem with the
>>> current model, only subsequent ones.
>>
>>
>>
>> I have that in place already, but so far it's a manual process (entering
>> every build ID by hand). It's on my todo list to allow to import data of
>> multiple builds.
>>
>>
>>>
>>> > BTW : Any chance you could send me a picture of the Buildtime Trend
>>> > dashboard on the big screen in your office? ;)
>>> >
>>> Photo of Victor Savkin with the screen hovering over his head :)
>>> https://goo.gl/photos/qqUAXLixGnxWb5gU8
>>
>>
>> Great! Thanks. :)
>>
>
>
>
> --
> Kind regards,
>
> Dieter Adriaenssens
>

--
Kind regards,

Dieter Adriaenssens


TeamCity Ignite :: Ignite Cache Failover Multi JVM [Build 111](http://204.14.53.152/viewLog.html?buildId=59896&buildTypeId=Ignite_IgniteCacheFailoverMultiJvm&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:03:33


TeamCity Ignite :: Ignite Cache Failover2 [Build 123](http://204.14.53.152/viewLog.html?buildId=59897&buildTypeId=Ignite_IgniteCacheFailover2&guest=1) is now running


Since there aren't any changes to _CUITe.csproj_ the new class won't be a part of the compiled assembly, or am I wrong?


опять же где эксепшены?


TeamCity Ignite :: Ignite Cache 3 [Build 258](http://204.14.53.152/viewLog.html?buildId=59892&buildTypeId=Ignite_IgniteCache3&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 996, muted: 24 Build time: 00:27:15


TeamCity Ignite :: Ignite Cache Full API [Build 1186](http://204.14.53.152/viewLog.html?buildId=59898&buildTypeId=Ignite_IgniteCacheFullApi&guest=1) is now running


i just use isSquareAttacked for several squares. Not sure you can optimize if you modify this functions to compute several square at a time


mas eh exatament isso que esta sendo feito

Em 10 de agosto de 2015 17:54, Alberto Luiz Souza <notifications@github.com>
escreveu:

> Lembre de não produzir o EntityManagerFactory o tempo inteiro? O
> processamento dele é um pouco mais pesado. Produza ele em outra classe,
> ApplicationScoped, e o receba injetado na sua EntityManagerProducer.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625141>
> .
>


sweeet! `build199` coming.


In C++ you should use "inline", reference passing and const for these kind of thing.


Yes. I moved it from the `render` call at the end of the function and didn't feel like rewriting every key. :)


Change 'two-hand' to 'two-handed'


RoomAirflowNetwork (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1273 of 1273 tests passed)

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


adicionado bro
segue meu github

se puder fazer um clone para verificar este caso do entitymanagerfactory

https://github.com/ivobarcelos/Jornada-Submissao-Palestras

Em 10 de agosto de 2015 18:25, Ivo Barcelos <ibs2006@gmail.com> escreveu:

> mas eh exatament isso que esta sendo feito
>
> Em 10 de agosto de 2015 17:54, Alberto Luiz Souza <
> notifications@github.com> escreveu:
>
>> Lembre de não produzir o EntityManagerFactory o tempo inteiro? O
>> processamento dele é um pouco mais pesado. Produza ele em outra classe,
>> ApplicationScoped, e o receba injetado na sua EntityManagerProducer.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625141>
>> .
>>
>
>


This is interesting, how has it been working out for you?


I don't think that the client should specify the request type. You could create a issue for this, because at the moment only application/json requests are parsed.

Also when using -d with curl the default method is POST.

Good catch with the parsing issue!


we do need #: here for documentation (sphinx) use. I know this is contradictory with pep8, but its what sphinx uses!


normal string interpolation does this automatically, btw


I would not change quark to quarkjs in the examples, only when requiring the module.


Yes, I see now, it doesn't look straightforward but anyways looks like using $rootScope's $destroy is useless ([here] (https://github.com/Urigo/angular-meteor/blob/master/modules/angular-meteor-collection.js#L300)), we need a controller local scope which is not available in factories. So looks like API docs need to be updated to say e.g.  'one is mandatory to call collection.stop on $destroy'. @Urigo what do you say?


The test cases look amazing! As far as I was able to understand it, a domain is what you are counting and the key is stuff that you are pushing into a domain and the value is the count. What do you think?


this is not needed, its autogenerated


Mainly because I was thinking of it from a database perspective. If it's unset, it's clearer to check for `NULL` rather than `''`. But I'll change it to `default=''`


Hi Igor,

you can commit the script with +x privileges directly, then this is not necessary. Another alternative is simply
```
WatchDogIntelliJPlugin/fetchIdea.sh
```


Ello and ADN are social networks too!

We Are One Social Network, The Human Social Network. #AllSocialNetworksMatter


As for what it does, it stores the original hash of the file, before we sign it, or make any other changes. It's so that annotations can always be tied to the original file, and will apply to any file from the same version with the same original hash. I'll add a comment.


1 The Evolution of Cooperation by the Hankshaw Effect
Sarah P. Hammarlund1,2*, Brian D. Connelly1
*, Katherine J. Dickinson1
, and Benjamin Kerr1,3 2
3
1 4 Department of Biology and BEACON Center for the Study of Evolution in Action, University of
5 Washington, Seattle, Washington, 98195, USA
2 6 Current Address: Department of Zoology, University of Oxford, Oxford OX1 3PS, United Kingdom
3 7 Corresponding author: kerrb@uw.edu
8 * these authors contributed equally
9
10 Further contact details: SPH, sarahham@uw.edu; BDC, bdcx@uw.edu; KJD, katiejd8@uw.edu; BK,
11 kerrb@uw.edu, ph +1 206 221 3996
12
13 Running title: Cooperation and the Hankshaw Effect
14 Keywords: Social Evolution, Adaptation, Mutations, Hitchhiking, Population Structure, Models/Simulations
15 Word count: 3717
16 Number of Tables: 1
17 Number of Figures: 3
18 Supporting information: 1
19 Data archiving doi: 10.5281/zenodo.17423
2
20 Abstract
21
22 The evolution of cooperation—costly behavior that benefits others—faces one clear
23 obstacle. Namely, cooperators are always at a competitive disadvantage relative to
24 defectors, individuals that reap the benefits, but evade the cost. One solution to this
25 problem involves genetic hitchhiking, where the allele encoding cooperation becomes
26 linked to a beneficial mutation. Here we explore hitchhiking in the context of adaptation
27 to a stressful environment by cooperators and defectors with spatially limited dispersal.
28 Under such conditions, clustered cooperators reach higher local densities, thereby
29 experiencing more opportunities for mutations than defectors. Thus, the allele encoding
30 cooperation has a greater probability of hitchhiking with alleles conferring stress
31 adaptation. We label this probabilistic enhancement the "Hankshaw effect" after the
32 character Sissy Hankshaw, whose anomalously large thumbs made her a singularly
33 effective hitchhiker. Using an agent-based model, we reveal a broad set of conditions
34 that allow the evolution of cooperation through the Hankshaw effect. Additionally, we
35 show that spiteful behavior can evolve by the Hankshaw effect. The primary elements of
36 our model, including genetic hitchhiking and population structure, have been discussed
37 separately in previous models. However, the combination of these elements has not
38 been appreciated as a solution to the problem of cooperation.
3
39 Introduction
40
41 Natural selection is predicted to eliminate deleterious alleles. However, a detrimental
42 allele can actually increase in frequency if it is physically linked to a beneficial allele
43 (Maynard Smith and Haigh 1974). Such genetic hitchhiking is often viewed as a passive
44 process—the deleterious allele becomes associated with a positively selected allele
45 purely by chance. In some cases, however, the hitchhiking allele can play an active role
46 by increasing its probability of catching a ride. For instance, an allele that increases the
47 genomic mutation rate may lift its chances of hitchhiking by raising the incidence of
48 beneficial mutations, despite the deleterious mutations it also generates (de Visser
49 2002). If a property of an allele increases its likelihood of hitchhiking, we term this the
50 “Hankshaw effect,” after the character Sissy Hankshaw from Tom Robbins’ novel Even
51 Cowgirls Get the Blues. Hankshaw was born with oversized thumbs and uses this
52 attribute to become a prolific hitchhiker. For Hankshaw, a trait that was initially an
53 impairment becomes her salvation on the open road. In the same way, the cost of a
54 deleterious allele can be offset if the allele improves its own chances of hitchhiking.
55 Here, we explore how the Hankshaw effect can promote the evolution of one costly trait
56 that has received a great deal of attention: cooperation.
57
58 We define cooperation as costly behavior that improves the fitness of others. For
59 instance, the production of costly secreted enzymes by microbes can liberate critical
60 resources or detoxify harmful substances present in the environment. In these
61 instances, such exoenzymes constitute public goods (Greig and Travisano 2004; West
62 et al. 2007a; Sandoz et al. 2007; Dugatkin et al. 2005). It is the cost of cooperative
4
63 behavior that makes its evolution so problematic. Specifically, a population of
64 cooperators is susceptible to invasion by defectors—individuals that forego the costs of
65 cooperation but still receive its benefits (Hardin 1968; Velicer et al. 2000; Strassmann et
66 al. 2000; Rainey and Rainey 2003; Travisano and Velicer 2004). One recently proposed
67 solution to this subversion problem involves genetic hitchhiking (Waite and Shou 2012;
68 Morgan et al. 2012; Asfahl et al. 2015). In these studies, bacteria or yeast that produce
69 public goods (cooperators) compete against non-producers (defectors) in a novel
70 environment. If a beneficial mutation happens to arise first in the cooperative strain, and
71 if the selective advantage of this mutation outweighs the cost of cooperation, this
72 adapted cooperator can displace defectors through genetic hitchhiking. These previous
73 studies have focused on this hitchhiking process in well-mixed populations of
74 cooperators and defectors. Under such conditions, cooperators do not have a greater
75 chance of acquiring a beneficial mutation.
76
77 However, there are circumstances where cooperators can increase their chances of
78 adaptation. Specifically, if the population is spatially structured (in which limited
79 dispersal leads to clustering of like-types) the benefits of cooperation will be
80 disproportionately experienced by cooperators, and cooperator-rich regions will reach
81 higher densities. Consequently, cooperative lineages expanding within a structured
82 population will experience more reproduction than defector lineages and therefore more
83 opportunities for a beneficial mutation. Because cooperators adapt more rapidly, they
84 are able to competitively displace defectors when the two types meet. That is,
85 cooperator alleles hitchhike with the beneficial mutations that are more likely to occur in
5
86 their presence. In structured populations, such evolution of cooperation by the
87 Hankshaw effect can occur as long as there is room for evolutionary improvement.
88
89 There is ample opportunity for adaptation under stressful environmental conditions, as
90 organisms experiencing such conditions are, by definition, maladapted to their
91 environment. Evolution under harsh conditions can involve selection for mutations that
92 allow organisms to better tolerate the stress. Stressful conditions can also thin and
93 fragment a population, which can lead to clustering of like-types if dispersal and
94 migration are spatially restricted. This combination of positive assortment and
95 opportunities for adaptation sets the stage for the Hankshaw effect. Here, we build a
96 simulation model to explore the evolution of cooperation in stressful environments.
97
98
99 Methods
100
101 In our agent-based simulation, evolution occurs in a population consisting of
102 subpopulations connected by limited migration (i.e., a metapopulation). There are two
103 types of individuals within these subpopulations: cooperators and defectors.
104 Cooperation is costly, but increases the productivity of the subpopulation. The onset of
105 stressful conditions thins the population at the beginning of the simulation, and then
106 surviving lineages can acquire fitness-enhancing mutations to adapt to the stress.
107
6
108 Individual genotype and fitness
109 The genotype of each individual is a binary string. The value (allele) at the first locus,
110 designated locus zero, determines whether the individual is a cooperator (allele 1) or a
111 defector (allele 0). We refer to this first locus as the “cooperation locus.” Cooperation is
112 costly, reducing individual fitness by � (model parameters and their values are listed in
113 Table 1). Alleles at the next � positions (loci 1 through �) determine the individual’s level
114 of adaptation to the stressful environment. We refer to these loci as “adaptive loci.” A
mutation from 0 to 1 at adaptive locus � will improve individual fitness by �! 115 regardless of
116 the allelic states of other loci (i.e., there is no epistasis). We assume that
{�!, �!, �!, … , �! 117 } are independent and identically distributed random variables with
�! ∼ unif(�!"#, �!"#). Thus, if the allelic state of locus � is denoted �! 118 (with �! ∈ {0,1}),
119 then the fitness of an individual is
120
121
� = � − �!� + �!
!
!!! �! 122 , [1]
123
124
125 where � is a baseline fitness (the fitness of an individual with zeros at every locus). If
126 there are no adaptive loci (� = 0), then the fitnesses of a cooperator and a defector are
127 � − � and �, respectively.
128
129 Overview of the population and the basic simulation cycle
Simulations using this model track a single population with �! 130 patches arranged as an
131 �×� bounded lattice. Each patch can potentially hold a subpopulation. Simulations are
7
132 run for � cycles, and all subpopulations cycle synchronously. Each cycle consists of
133 population growth, mutation, migration, and dilution.
134
135 Population growth
136 If � is the proportion of cooperators in a given subpopulation at the beginning of a
137 growth cycle, then that subpopulation grows to size �(�), where
138
139
140 �(�) = �!"# + (�!"# − �!"#)�. [2]
141
142
143 Therefore, a subpopulation consisting entirely of defectors (� = 0) reaches size �!"#,
while a subpopulation of cooperators (� = 1) reaches a size of �!"# 144 (with �!"# ≥ �!"#).
145 The function �(�) gauges the benefit of cooperation, as subpopulation size increases
146 linearly with the proportion of cooperators. During subpopulation growth, competition
147 among genotypes occurs. Specifically, genotypes fill the �(�) “slots” according to a
148 fitness-weighted lottery (using Equation [1]). We are therefore modeling a form of
149 fecundity selection in an asexually reproducing population. Such selection occurs at
150 every occupied patch in the population.
151
152 Mutation
153 For simplicity, mutation occurs after population growth. For each individual, every locus
mutates independently. The cooperation locus changes allelic state with probability �! 154 ,
155 while each adaptive locus changes allelic state with probability �!.
8
156 Migration
157 Following mutation, individuals can migrate to new subpopulations. For each populated
158 patch, a neighboring destination patch is chosen. For a focal patch in the lattice, its
159 destination patch is in its Moore neighborhood, consisting of the 8 nearest patches. The
160 population lattice has boundaries; therefore, a focal patch on the edge or corner of the
161 lattice has fewer neighboring patches. Each individual in the focal patch moves to the
162 destination patch with probability �.
163
164 Dilution
165 After migration, subpopulations are diluted to allow for growth in the next cycle. Each
166 individual, despite its genotype, survives dilution with probability �.
167
168 Stress survival and adaptation
169 Environmental stress has multiple effects. First, the subpopulations undergo a dramatic
170 thinning event. For most runs, this bottleneck occurs only at the beginning of the
171 simulation (but see the next section). This stress-induced thinning is distinct from the
172 mild dilution that occurs every cycle. Individuals survive the onset of the stress with
probability �! 173 , which represents the likelihood of acquiring a mutation conferring stress
tolerance (where �! ≪ �). Second, the allelic state �! 174 is set to 0 at each adaptive locus,
175 as individuals are not adapted to the new stressful conditions. Third, the fitness
increments tied to adaptations at each locus (�! 176 ) are determined as described above. All
177 simulations begin by applying these effects to full subpopulations initiated at each patch
178 with cooperator proportion �!.
179
9
180 Changing environments
181 For some simulation runs, the population experiences a series of distinct stressful
182 conditions. The three effects described in the previous section are applied periodically
183 at some defined interval �. Thus, when new stressful conditions are experienced, any
184 fitness effects associated with adaptation to previous stress are removed.
185
186 Removing population structure
187 Population structure can be removed by merging the entire population into a single
188 patch, creating a well-mixed population. To control for total population size between
189 such "unstructured" runs and the lattice runs described above, we let the size of the
190 well-mixed population after growth be
191
192
�(�) = �! 193 �!"# + (�!"# − �!"#)� . [3]
194
195
196 With the exception of the migration step (which is now absent), all other steps in the
197 simulation cycle proceed as above.
198
199 Software environment, source code, and data archiving
200 Simulations used Python 2.7.3, NumPy 1.9.0, and NetworkX 1.9.1 (Hagberg et al.
201 2008). Data analyses were performed with R 3.2.0 (R Core Team 2015). The simulation
202 software, configuration files, data, and analysis scripts are available at doi:
203 10.5281/zenodo.17423.
10
204 Results
205
206 The major components of our hypothetical process are (1) stressful conditions create
207 opportunities for adaptation, and (2) cooperators have more chances to adapt due to
208 their relatively greater reproduction that occurs in a spatially structured population. To
209 illustrate the importance of these components, we begin by exploring the evolution of
210 cooperation when stress adaptation and spatial structure are either present or absent.
211
212 Without the opportunity for stress adaptation (� = 0), defectors fix rapidly (Figs. 1A and
213 1C). A structured population does have a slight initial lift in cooperator proportion (Fig.
214 1C). This pattern occurs because stress thins the population, leading to isolated
215 subpopulations of either cooperators or defectors. The initial lift in cooperator proportion
216 reflects the greater productivity of cooperator subpopulations compared to defectors.
217 However, once migration mixes these subpopulations, cooperators are outcompeted by
218 defectors due to the cost of cooperation. Thus, without the possibility of stress
219 adaptation, spatial structure does not strongly affect the dynamics—cooperators
220 experience rapid extinction in both cases.
221
222 Without spatial structure, the only attribute that initially distinguishes cooperators and
223 defectors is the cost of cooperation; therefore, defectors have immediate advantages
224 (Figs. 1A and 1B). However, when organisms can adapt to stress (� = 8) in a well-
225 mixed population, cooperators decline less rapidly (Fig. 1B). The large variance in
226 Figure 1B reflects the fact that in some replicate runs, cooperators happen to gain the
227 first beneficial mutation, while in other runs, defectors are first. The benefits of
11
228 cooperation are experienced equally by both types in a well-mixed population. Because
229 cooperators incur a cost, defectors actually have a greater chance of adapting, which is
230 why the average proportion of cooperators falls from its initial value over the first 1000
231 cycles. Cooperators in all replicate populations go extinct eventually; in the cases where
232 cooperators adapt first, the rise of de novo adapted defectors from adapted cooperators
233 leads to cooperator extinction.
234
235 When both the opportunity to adapt to stress and spatial structure are present, a
236 dramatically different picture emerges (Fig. 1D). The greater productivity of the isolated
237 cooperator subpopulations creates more mutational opportunities, enabling a faster rate
238 of adaptation to the stress. When cooperators and defectors meet through migration,
239 the fitter cooperators can now competitively displace the defectors despite the cost of
240 cooperation. More generally, cooperator subpopulations are epicenters of rapid
241 adaptation spreading and displacing defector-dominated subpopulations.
242
243 Although cooperators rise to high proportions, this increase is ultimately transient.
244 Because the number of adaptive loci is finite, cooperators eventually discover the
245 genotype that is most adapted to the stress. At this point, any de novo defectors will be
246 equally stress-adapted but will save on the cost of cooperation, and thereafter displace
247 cooperators. We note that if mutation at the cooperation locus does not occur (�! = 0),
248 then cooperators can be maintained at high proportion indefinitely (see Supplemental
249 Figure S1).
250
12
251 Given the threat of de novo defectors (�! > 0), cooperator success is transient. Thus,
252 we use the area under the cooperator proportion curve (from time � = 0 to � = 2000) as
253 a measure of cumulative cooperator presence (Fig. 2A). As cooperators spend more
254 time at high proportions, this integral increases. By this metric, cooperators fare better
255 as the number of adaptive loci increases (Fig. 2B). Not surprisingly, cooperator
256 presence also increases as the benefit of cooperation increases (Fig. 2C) or as the cost
257 decreases (Fig. 2D).
258
259 Matters are more complicated with the rate of migration, where cooperator presence
260 peaks at intermediate levels (Fig. 2E). At high migration rates, cooperators have
261 insufficient time to adapt to the stress before mixing with defectors. Conversely, with low
262 rates of migration, there is sufficient time for cooperators to adapt to stress but
263 insufficient export of adapted cooperators into less adapted defector subpopulations.
264
265 The effects of mutation rate are also complex (Fig. 2F). At low mutation rates, we see
266 high variance in cooperator presence—in some cases cooperators fare well (if they are
267 the first to discover an adaptive mutation) while in others they do poorly (if they are not).
268 As mutation rates increase from low levels, cooperator presence decreases. There are
269 two contributing factors to this pattern. First, de novo defectors are more likely to arise
with higher rates of mutation at the cooperation locus, �! 270 . Second, the isolated defector
271 subpopulations are better able to adapt to the stress with higher rates of mutation at the
272 adaptive loci, �!. As mutation rates continue to increase, cooperator presence
273 increases due to a higher cooperator proportion at mutation-selection balance (see
274 Supplemental Figure S2).
13
275 For all of the results above, the population adapts in response to a single stressful
276 environment. If the population instead faces a series of stressful environments, we see
277 that cooperator proportion can be maintained at high values (Fig. 3A). However, the
278 frequency at which environmental changes occur is crucial. This frequency must be
279 greater than a critical value in order for cooperators to avoid extinction (Fig. 3B). As the
280 frequency of change increases above this value, a fresh round of adaptation salvages
281 an otherwise doomed cooperator lineage. At the highest frequencies of environmental
282 change, there is not sufficient time for adaptation to any new stress (given the rapid
283 barrage of changing harsh conditions). Cooperators fare well in these quickly changing
284 environments solely due to the continual thinning effect associated with stress and the
285 ensuing positive assortment (see Supplemental Figure S3).
286
287
288 Discussion
289
290 In our model, cooperation evolves through a form of hitchhiking. In order for this costly
291 trait to hitchhike, there must be “rides” available; that is, there must be opportunities to
292 gain beneficial mutations. In our simulated scenario, a stressful environment provides
293 such opportunities for adaptation. However, evolution by the Hankshaw effect involves
294 more than simple hitchhiking; rather, it requires that cooperators have a greater chance
295 of catching a ride than defectors, which can occur if cooperators have more
296 reproductive opportunities (Fig. 2C). In our simulation, the combination of stress-
297 induced population thinning and spatially limited dispersal produces positive assortment
14
298 and higher cooperator productivity follows. With opportunities to adapt to stress and with
299 limited dispersal, cooperators can experience sustained increases in frequency (Fig. 1).
300
301 In the process we have outlined, the cooperation allele is a hitchhiking passenger with a
302 “driving” allele that confers stress adaptation. While the pace of stress adaptation
303 depends on social traits, the stress adaptation itself is inherently non-social. The idea
304 that adaptation to non-social aspects of the environment can affect social evolution has
305 been explored both empirically (Waite and Shou 2012; Morgan et al. 2012; Asfahl et al.
306 2015) and theoretically (Quigley et al. 2012). These previous studies focus on well-
307 mixed populations of cooperators and defectors, where a beneficial mutation can arise
308 in either background. If this mutation occurs in the cooperator background, and if the
309 benefit of this mutation outweighs the cost of cooperation, then cooperators may
310 displace defectors. This process has been termed an “adaptive race” in the sense that
311 the cooperator and defector are in a race to gain the first adaptive mutation (Waite and
312 Shou 2012). In the adaptive race, the cooperation allele does not have a greater chance
313 of hitchhiking than the defection allele. Consequently, the average proportion of
314 cooperators (e.g., across many replicate populations) is not expected to increase (see
315 Fig. 1B). In contrast, in a spatially structured population, the cooperation allele directly
316 increases its probability of catching a lift, leading to an actual increase in the average
317 cooperator proportion (see Fig. 1D).
318
319 Since Hamilton's pioneering work (Hamilton 1963; 1964), it is well known that any
320 mechanism that enables cooperators to cluster together facilitates the evolution of
321 cooperation (Hamilton 1975; Wilson 1975; Pepper and Smuts 2002; Nowak 2006; West
15
322 et al. 2007b; Fletcher and Doebeli 2009; Nadell et al. 2010). In our model, there are two
323 features that lead to spatial clustering. First, at the beginning of each simulation, only a
324 few individuals survive the onset of the stressful conditions, and the majority of
325 subpopulations are founded by single individuals. Reproduction within such
326 subpopulations will create immediate positive assortment of types. Second, spatially
327 restricted dispersal within the population maintains this clustering. Interestingly,
328 cooperators can still fare well if these features are removed or diminished. Even in the
329 absence of the initial stress-induced thinning, an adaptive race can jumpstart cooperator
330 success (see Supplemental Figure S4). Additionally, as dispersal becomes less
331 restricted (by connecting more subpopulations through migration) cooperators continue
332 to reach high proportions (see Supplemental Figure S5). While some degree of
333 population structure is required, the Hankshaw effect is robust to the exact form of this
334 structure.
335
336 While it remains to be seen whether our process can operate in natural systems, our
337 model suggests that the evolution of cooperation by the Hankshaw effect can occur
338 under a broad set of conditions. Indeed, the basic assumptions of the model are
339 fundamental features of many biological populations. For instance, cooperation in the
340 form of public good production or competitive restraint in the use of common resources
341 has been shown to increase population size (Kerr et al. 2006; Diggle et al. 2007;
342 Eshelman et al. 2010; Xavier et al. 2011; Drescher et al. 2014), a critical assumption of
343 our model. Moreover, many populations are naturally structured, from microbial biofilms
344 to passively dispersed plants to sessile or territorial animals (Hutchings 1997; Tilman
345 and Karieva 1997; Nadell et al. 2009). Finally, in natural systems, harsh environmental
16
346 conditions can impact the survival and reproduction of organisms. In fact, the edges of a
347 species’ range can be delimited by stressful conditions (Connell 1961; Sexton et al.
348 2009; Hargreaves et al. 2014). It is likely that these assumptions will be simultaneously
349 satisfied in many natural contexts.
350
351 Cooperation is not the only kind of social trait that can evolve by the Hankshaw effect. It
352 is possible that spiteful traits (i.e., phenotypes that harm others at a personal cost;
353 Hamilton 1970; Gardner and West 2006) may also create opportunities to hitchhike
354 within structured populations. For example, the production of toxins by bacteria
355 (bacteriocins; Chao and Levin 1981; Riley and Wertz 2002; Kerr et al. 2002; Inglis et al.
356 2009) or characteristics that enhance flammability in plants (Mutch 1970; Williamson
357 and Black 1981; Schwilk 2003) are spiteful traits that could evolve through the
358 Hankshaw effect. Specifically, individuals with these traits create empty patches in their
359 population at an extreme personal cost (by lysing or burning); and adaptation by
360 relatives (clone mates or offspring) may therefore occur at a higher rate (see Schwilk
361 and Kerr 2002 for a full treatment). In the Supplement, we adjust our model to explore
362 spiteful interactions, and demonstrate that spite can also evolve by the Hankshaw effect
363 (Supplemental Figure S6).
364
365 In our model, the success of costly social traits (cooperation or spite) is merely transient
366 when mutants that evade the costs (i.e., defectors or non-spiteful types) can arise and
367 stress adaptation is limited. However, these social traits can experience more than
368 transient success if the environment changes continually (Fig. 3 and Supplemental
369 Figure S6B). Environmental change is ubiquitous in natural systems; indeed, periodic
17
370 change (e.g., diurnal or seasonal cycles) is experienced by many biological populations
371 (Fretwell 1972; McClung 2006). Additionally, organisms themselves can alter their
372 environment, a process termed “niche construction” (Odling-Smee et al. 2003; Laland et
373 al. 1999). As a result, cycles of environmental change can be generated by the evolving
374 system itself. For instance, suppose that as population density increases, new stressful
375 conditions become more likely (e.g., at high population density, new pathogens may be
376 more likely to spread, creating new selective pressures for the host population).
377 Extending upon the approach used here, we have shown elsewhere that when
378 individuals alter their local environments in ways that generate new adaptive
379 opportunities (i.e., negative niche construction), cooperation can be maintained at high
380 proportion indefinitely (Connelly et al. 2015).
381
382 In summary, we have explored a scenario where an allele improves its own prospects
383 for hitchhiking. While the most straightforward case involves direct effects of the allele
384 on its owner (e.g., a mutator allele), here we have explored a more subtle case.
385 Specifically, the increased probability of hitchhiking of our focal allele occurs due to its
386 social impact within a structured population. In the process, the social behavior
387 increases in proportion despite its costs. Common explanations for the evolution of
388 costly social traits, specifically genetic hitchhiking and positive assortment, are elements
389 of our model. However, the effect of bringing these elements together has remained
390 unexplored before this study. Our theoretical results reveal this unification to be
391 synergistic. Given the biological plausibility of our theoretical assumptions, the
392 Hankshaw effect will be an important consideration in future studies of social evolution.


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1272 of 1272 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)


TeamCity Ignite :: Ignite Cache Expiry Policy [Build 1162](http://204.14.53.152/viewLog.html?buildId=59894&buildTypeId=Ignite_IgniteCacheExpiryPolicy&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 91, muted: 22 Build time: 00:22:13


TeamCity Ignite :: Ignite Cache Full API Multi JVM [Build 135](http://204.14.53.152/viewLog.html?buildId=59899&buildTypeId=Ignite_IgniteCacheFullApiMultiJvm&guest=1) is now running


@vaihtovirta
В целом не плохо. Я к сожалению не в курсе всех тонкостей задания, но лично мне не хватает нескольких вещей, а именно:
- что нужно немного поработать над архитектурой;
- Модель должна быть Моделью а Адаптер - Адаптером;
- добавить Exceptions (в простейшем виде, но без них никак);
- тесты, тесты, тесты

Пиши, задавай вопросы, рад буду помочь.


Yes. I wound up doing that in my file viewer changes, but wasn't sure it was a good idea to go back and change this.


Would it make more sense to put this check in the event handler rather than in the matches?


@datahead8888 Noted.


This seems to solve the problem that I was having (I think). At least, I've tested it several times in a row and it appears to work.


The event is being applied on the local $scope, since it's being defined on the prototype, not the instance


Oi Ivo,

Queria o link do trello. Entendi agora, você trocou a injeção porque estava
vindo nulo. De toda forma, nesse momento você está abrindo o EMF o tempo
inteiro e não por aplicação.

Em seg, 10 de ago de 2015 às 18:28, ivobarcelos <notifications@github.com>
escreveu:

> adicionado bro
> segue meu github
>
> se puder fazer um clone para verificar este caso do entitymanagerfactory
>
> https://github.com/ivobarcelos/Jornada-Submissao-Palestras
>
> Em 10 de agosto de 2015 18:25, Ivo Barcelos <ibs2006@gmail.com> escreveu:
>
> > mas eh exatament isso que esta sendo feito
> >
> > Em 10 de agosto de 2015 17:54, Alberto Luiz Souza <
> > notifications@github.com> escreveu:
> >
> >> Lembre de não produzir o EntityManagerFactory o tempo inteiro? O
> >> processamento dele é um pouco mais pesado. Produza ele em outra classe,
> >> ApplicationScoped, e o receba injetado na sua EntityManagerProducer.
> >>
> >> —
> >> Reply to this email directly or view it on GitHub
> >> <
> https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625141
> >
> >> .
> >>
> >
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625803>
> .
>


overwritten


Hilarious. Maybe I'd been eating quinoa.


They're acting on different elements. I'd rather just append the input and text in the same call, but then jQuery would treat the text as HTML. I'm really waiting to just switch to a proper template library, so making do with a little bit of ugly for the moment.


I allocate 8 bytes on cuda too as seen here: https://github.com/Theano/libgpuarray/pull/63/files#diff-c72babbe84e1c21afb2ad632a1a17d2dR93


I'm fine changing this from `auto` to `int`, but since `ownerCountDelta` no longer returns `size_t` using `auto` would be OK here too.


@JordanCheney Can you provide a post-commit review? The intent here is that certain applications (like the one I'm writing) sort detections by confidence and then retain only the top _k_. In the absence of a better confidence metric, we select the largest _k_ faces.


`SocketIO` is definitely the right tool for real-time updates. I decided to do just a quick hack for now, since none of the home page gets `SocketIO` messages anyway. Yes, I'm hoping all these things will be fixed with the real job mgmt page.

Fair point about the REST API. I don't think it's worth the bother at the moment since only Andrew is interested in this stopgap fix.


It works, I tested it. Unless I want to reimplement all of the overloads in MixinExtent I have to make this a mixin target and use Implements to implement the rest of the methods without having to make this abstract (necessary so I can create instances).


Looks good.


I am using Qt 5.5.0, do you use an older version?


Alas, yes, 5.4.2.


isso mesmo como tava vindo nulo, eu mantive de uma maneira que funcionasse
pra continuar os trampos

me dah um exemplo de como fazer isso, de como abrir o emf apenas na
aplicacao

link do trello
https://trello.com/b/d9xATU2T/jornada-submissao-de-eventos-ivo

Em 10 de agosto de 2015 18:36, Alberto Luiz Souza <notifications@github.com>
escreveu:

> Oi Ivo,
>
> Queria o link do trello. Entendi agora, você trocou a injeção porque estava
> vindo nulo. De toda forma, nesse momento você está abrindo o EMF o tempo
> inteiro e não por aplicação.
>
> Em seg, 10 de ago de 2015 às 18:28, ivobarcelos <notifications@github.com>
> escreveu:
>
> > adicionado bro
> > segue meu github
> >
> > se puder fazer um clone para verificar este caso do entitymanagerfactory
> >
> > https://github.com/ivobarcelos/Jornada-Submissao-Palestras
> >
> > Em 10 de agosto de 2015 18:25, Ivo Barcelos <ibs2006@gmail.com>
> escreveu:
> >
> > > mas eh exatament isso que esta sendo feito
> > >
> > > Em 10 de agosto de 2015 17:54, Alberto Luiz Souza <
> > > notifications@github.com> escreveu:
> > >
> > >> Lembre de não produzir o EntityManagerFactory o tempo inteiro? O
> > >> processamento dele é um pouco mais pesado. Produza ele em outra
> classe,
> > >> ApplicationScoped, e o receba injetado na sua EntityManagerProducer.
> > >>
> > >> —
> > >> Reply to this email directly or view it on GitHub
> > >> <
> >
> https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625141
> > >
> > >> .
> > >>
> > >
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625803
> >
>
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ivobarcelos/Jornada-Submissao-Palestras/commit/f0ddf92384ca32e191250d61affb339af2e752c3#commitcomment-12625949>
> .
>


now this line is executed twice


@ukstv Опровергни, что нибудь))


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1272 of 1272 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)


<img width="631" alt="screen shot 2015-08-10 at 2 42 55 pm" src="https://cloud.githubusercontent.com/assets/4617414/9185083/2068cb1c-3f6e-11e5-8049-7748aef4f01d.png">


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/18891/testReport/) for this commit**


@kstrack-grose
all looks great! great work!
Question, why did you use .count on line 26? I'm guessing that's to see if there is already one user taken?
As a suggestion, let's try to leave as complete comments as possible as we need to make sure we document everything for the legacy project (I think you're already doing a good job there, it's just this one line that it took me a second to figure out :) )


better cache as something like this.titleEl in render


<img width="635" alt="screen shot 2015-08-10 at 2 44 06 pm" src="https://cloud.githubusercontent.com/assets/4617414/9185107/4682627c-3f6e-11e5-94a3-f81645f63907.png">


think of a better way than to check on dom element


this works (I hope :)
but you could also look into the path module.
https://nodejs.org/api/path.html

really, any joining should be done with that too, so that paths are x-platform from day one.


@vaihtovirta Не используешь эти файлы, удаляй. Придёт ночью Вильгельм из Оккама и отрежет что-нибудь, если будешь мусор оставлять.


@vaihtovirta, Ну а ты как бы поступил и почему?


accessing database directly from view is a bad practice


develop (Myoldmopar) - 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)


You probably can. I will try it


lgtm


no need to reinvent the wheel, better read documentation on the tools you have http://underscorejs.org/#uniqueId


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


@nttaylor, thanks for this!  One comment: there's no need to leave commented-out lines.  Thanks to version control, you'll always have them if you need them again (I'm looking at lines 891-894, 901-902 and the 402/404 pair).  This was a hard habit for me to break, but it was actually very freeing once I did.


yo


@Mantish, ¿así se ponen los nuevos tamaños?


Let's work out the updated API for this together.


Just a quick note, writeX can't be less than 0, it's unsigned. Even though it contains a signed value, treating as an unsigned value was an optimization to reduce the number of comparisons in the loop. See line 175.


public folder should be gitignored


C/P error: I think it should be `def test_command_spiritupgrade(self)`.
Now we have two times `def test_command_spiritinstall(self)`.


Only mentioning because I expect this is in a tight loop that gets called a lot during the solve?

Evaluating `y[:numCoreSpecies]` twice within the loop like this may be more costly than evaluating it once and storing it in a new variable (if you have type declared said variable for Cython).

Also, we should check that `for i in range(some_variable_not_cdef_declared)` is C optimized. (i.e. check the html file made by Cython). And does it work with our `cdef int i` or does it need `cdef size_t i`?


Given a 4-digit build sequence number, do you know how to get the longer
UID that travis puts in the URL? I'm not sure how to find build 7000 for
instance.

On Mon, Aug 10, 2015 at 2:22 PM Dieter Adriaenssens <
notifications@github.com> wrote:

> Update : previous builds 7000-7551 have been imported
>
> 2015-08-10 15:28 GMT+02:00 Dieter Adriaenssens <
> dieter.adriaenssens@gmail.com>:
>
> > Hi Alex,
> >
> > A few improvements to the charts :
> > - pull_requests data is stored when build data is processed :
> > build_trigger property
> > - added a filter option to only show pull request build jobs
> >
> > I've also imported a few builds (7020-7100) around the build where you
> > introduced the change :
> >
> > https://travis-ci.org/angular/angular/builds/72039309 : build 7042 : 18
> > min
> >
> > On first sight, it seems that the changes in that PR reduced the
> buildtime
> > to ~18min, for the following builds. Later today I'll import builds
> > 7101-7551. Hopefully that will show in which build the improvement is
> > undone.
> >
> > BTW : the builds between 7552 and about 8230 don't have build_trigger
> > property, so they don't show up if you filter on pull-request. This is
> > because they were imported before I introduced the feature to get
> > pull_request data.
> >
> >
> >
> > 2015-08-06 20:59 GMT+02:00 Dieter Adriaenssens <
> > dieter.adriaenssens@gmail.com>:
> >
> >>
> >>
> >> 2015-08-05 19:46 GMT+02:00 Alex Eagle <notifications@github.com>:
> >>
> >>> On Wed, Aug 5, 2015 at 9:57 AM Dieter Adriaenssens <
> >>> notifications@github.com>
> >>> wrote:
> >>>
> >>> > > Thanks, I just noticed that on our big screen and was playing. I
> >>> don't
> >>> > > understand why our dart stable build seems tri-modal (four if you
> >>> count
> >>> > > fast failures).
> >>> > >
> >>> >
> >>> > I've added a filter for build results, so now you can filter out the
> >>> > failures.
> >>> >
> >>> >
> >>> > > Bigger problem is the graph doesn't go back far enough in history
> to
> >>> show
> >>> > > me when the time increased.
> >>> > >
> >>> >
> >>> > Do you have a rough idea how long ago you were still seeing the 18
> >>> minute
> >>> > builds?
> >>> > I can manually import some older builds, if you like. But let me
> first
> >>> > change the code so it save if it is a PR.
> >>> >
> >>>
> >>> It was 15 days ago when I'm sure it was 18m
> >>> https://github.com/angular/angular/pull/3174
> >>> but we only started sending you the data 9 days ago:
> >>> https://github.com/angular/angular/pull/3302
> >>>
> >>> Actually I think it would be a really useful feature if you could use
> the
> >>> travis API to backfill data for the time period before the webhook was
> >>> added. Most users of this thing are probably adding it because they
> >>> already
> >>> have a problem, and you won't be able to solve that problem with the
> >>> current model, only subsequent ones.
> >>
> >>
> >>
> >> I have that in place already, but so far it's a manual process (entering
> >> every build ID by hand). It's on my todo list to allow to import data of
> >> multiple builds.
> >>
> >>
> >>>
> >>> > BTW : Any chance you could send me a picture of the Buildtime Trend
> >>> > dashboard on the big screen in your office? ;)
> >>> >
> >>> Photo of Victor Savkin with the screen hovering over his head :)
> >>> https://goo.gl/photos/qqUAXLixGnxWb5gU8
> >>
> >>
> >> Great! Thanks. :)
> >>
> >
> >
> >
> > --
> > Kind regards,
> >
> > Dieter Adriaenssens
> >
>
>
>
> --
> Kind regards,
>
> Dieter Adriaenssens
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/angular/angular/commit/30bd2a3fc72f8f1cdb0ffc4b9d11b4ca42e9ece7#commitcomment-12625713>
> .
>


TeamCity Ignite :: Ignite Cache Failover2 [Build 123](http://204.14.53.152/viewLog.html?buildId=59897&buildTypeId=Ignite_IgniteCacheFailover2&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 53 Build time: 00:27:08


TeamCity Ignite :: Ignite Cache Restarts [Build 1811](http://204.14.53.152/viewLog.html?buildId=59900&buildTypeId=Ignite_IgniteDataGridRestarts&guest=1) is now running


Sorry for the very long delay. Overall it looks pretty good. Some initial thoughts from a quick scan, before I dive too deep into the code:

1. In general it shouldn't be necessary to include limit and next as parameters to the TableHead enum, as this info is stored in the tag stack. Maybe there's a little more plumbing to get access to it, but I think that's better than exposing it to the public renderer interface.

2. Since tables are (currently) a CommonMark extension, I'd prefer a flag to enable them, default off.

3. I think I'd like the table_spec.txt data in a separate subdir. I probably want to add a bunch more of this, it's just that for most of the development cycle I've just been working from the spec text from cmark.

4. I think you need to do the Google CLA, as described in CONTRIBUTING.md.

If there are any of these (except the last) you'd rather me do, let me know.


Potential infinite loop here, but it would mean that events come in faster than we can dequeue them. It will clearly never be the case for node events, and even for schema change events "storms" I doubt it will be that fast.
We should probably add a limit anyway, but then it's tricky because the count stays above maxPendingEvents, so only delayed deliveries get scheduled in eventReceived.


You can move the `case` into the `fun` “as clauses”.


How much work would it be to remove `note` wherever it's used? That should be automatable.


Если в классе есть class << self или self.method, это скорее всего значит, что с проектированием что-то не так было. Лучше классовые методы убрать в миксин, а ещё лучше извернуться и сделать на старых добрых переменных. Карандаш и пачка бумаги тоже помогают проектировать.


Sure, no rush from me. We can go over the git stuff that @lwjohnst86 proposed at the next meeting.

Also, just so you know, GitHub is not a mailing list. You have just posted a comment on a completely unrelated commit.


Use `${` instead of `123`, for readability maybe?


Why not replace uses of `match-err` with `regexp-match?`?


Downgrading to 5.4.2 did not fix the segfault and the quit action is also not visible.


^Bump


Could you delete that commented-out code?


This made it impossible to validate the form. It expected some data with key ['mail_form'], but as this is not actualy an import field, it will never has data. The fields of this subform are still required by the 'required' attribute in that form.


don't mix single and double quotes - chose one.
`typeof shapesData !== 'undefined'` is probably an overkill of a check - simplify.


luster -> lustre :-)


@vaihtovirta Это точно работает?


@ukstv тут уже побывал, поэтому мне остается тыкать на подобные штуки ;) Настрой редактор, ну правда :grimacing:


Thanks, will add this in the next commit. I'd prefer this alternative solution.


TeamCity Ignite :: Ignite Cache Failover [Build 1878](http://204.14.53.152/viewLog.html?buildId=59895&buildTypeId=Ignite_IgniteDataGridFailover&guest=1) outcome was **FAILURE**
Summary: Tests failed: 2 (2 new), passed: 33 Build time: 00:35:58
### Failed tests
```
org.apache.ignite.testsuites.IgniteCacheFailoverTestSuite: org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicClientInvalidPartitionHandlingSelfTest.testClockFullSync: junit.framework.AssertionFailedError: Failed to check value for key [key=88637, node=20247ece-c905-4d8b-9c00-3eb56e070002, primary=true, recNodeId=10b0a436-3f6b-4105-a536-a6d183899001] expected:<-2099265487> but was:<0>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

org.apache.ignite.testsuites.IgniteCacheFailoverTestSuite: org.apache.ignite.internal.processors.cache.GridCacheIncrementTransformTest.testIncrementRestart: junit.framework.AssertionFailedError: expected:<1052> but was:<1053>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

```


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 255](http://204.14.53.152/viewLog.html?buildId=59901&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) is now running


we should probably stay consistent on apiKey or apikey. I guess we'll go with camelcase.
i'll do a small fix


looking for http://underscorejs.org/#bindAll ?


Ну и метапрограммирования бы чуть-чуть


Just checking: this isomorphism checking isn't done inside a tight loop in the solver? I don't *think* it is, but wanted to be sure...


nice carriage return


Hmmm.  I'm just trying to understand what's happening here.  I'm guessing that the original code was constructing a `jtx::require` object (https://github.com/ripple/rippled/blob/develop/src/ripple/test/jtx/require.h#L78).  But the function call operator of the `jtx::require` object never gets called, so anything within the constructor arguments never gets validated.  Is that your reading of the code?

If that's correct, then your fixes are clearly correct.  Good catch.


Another minor documentation note. Can you add something right below the version descriptor the effect of "No breaking changes. Recommended update."?


TeamCity Ignite :: Ignite Cache Full API [Build 1186](http://204.14.53.152/viewLog.html?buildId=59898&buildTypeId=Ignite_IgniteCacheFullApi&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 8384, muted: 27 Build time: 00:35:11


TeamCity Ignite :: Ignite Cloud [Build 283](http://204.14.53.152/viewLog.html?buildId=59902&buildTypeId=Ignite_Cloud&guest=1) is now running


Нравится. Тестов бы еще :neckbeard:


nit: fix typo -> verifying


А ещё запрос из коммита, если его повторять кучу раз, а его повторять придётся, потому что он не ленивый, на достаточно большой базе угробит быстродействие.


I can't tell here...did the alias for `Kernal` get removed or added? Although I suspect if it got removed the lib wouldn't have passed the test. I'm not able to see your public branch at the moment to double check.


Radical


@workshur Я согласный, опровергать не буду.


Actually, part of the change (aside from the octothorpe fiasco) that this commit had implemented was switching the nesting of the loops so all adjustment commands were checked against all commands (rather than all commands checking against all adjustment commands), and if there wasn't a command already present it would add it (the latter being the sanity check I made reference to).

Still, though if the new implementation works it's cleaner than this in any case, so that's good.

Also, depressingly, the adjustmentcommand fix to end all adjustment command needs another fix on top of it, or else we need to add a #fixedrescost tag (that latter might be more intuitive so as not to water down the meaning of #adjustmentcommand, although I suppose the opposite argument could be made that adjustmentcommand should be changed to keep Dominions from watering down the meaning of #rcost 1), IOT get around Dominions' horrid and unique way of handling #rcost.


I think we are going to move away from the word domain. From now on domain will be called key. Hopefully the API documentation helps make things clear, if not then we obviously need to improve it: https://github.com/seiflotfy/counts/blob/master/README.md#api-documentation


Didn't you put the space there?


Will try installing Xfce here and check...


AFAIK the combat timer gets reset after teleporting to town, so your first approach would be a bit better IMO.


either `deleted` needs to be set to true inside the loop, or (better) just move L540 up into the `if pod.DeletionTimestamp...` block and remove `deleted` entirely. otherwise this will add all pods after the first undeleted one.


TeamCity Ignite :: Ignite Cloud [Build 283](http://204.14.53.152/viewLog.html?buildId=59902&buildTypeId=Ignite_Cloud&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 2, muted: 2 Build time: 00:03:43


TeamCity Ignite :: Ignite Compute Grid [Build 1754](http://204.14.53.152/viewLog.html?buildId=59903&buildTypeId=Ignite_IgniteComputeGrid&guest=1) is now running


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 14](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=37&buildTypeId=Xbim_XbimGeometry_XbimGeometry) is now running


This line 102 gives error "Uncaught TypeError: Cannot read property 'getDOMNode' of null" !


After merging with master it was always throwing an error when it hit this try/catch. I added a guard here and that seemed to fix it. Please review and make sure that's the right thing to do.


i add the elseif promotion and value == 1 then ... and accounts no login more in server....


The switching of nesting made sense completely. It was just dumb code from me previously.

But yes, #fixedrescost on top of it was to be expected. Also very simple thing I can add right now in a few minutes provided getResCost() works (which I have never verified exactly)


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 14](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=37&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:01:03


Little mistake right here, should probably be "audio-change".


awesome stuff mate, looking forward to trying it out


I'm hoping we can tease apart the difference between using the transport and expecting GetThreadContext to fail when we do. For example maybe we would use the transport on some other platform that does support GetThreadContext in the future, or maybe we will eventually get rid of the transport but GetThreadContext still fails.

What if we change this logic to be something like:
if(m_pTarget->GetThreadContext() == SOME_SPECIFIC_UNSUPPORTED_ERROR)
{
     // now fallback and search the frame chain
}


you can use equalizer for the dataset, it gives you `==` and others. if not, you may want to add `other.is_a?(self.class) && ...`


@ilyakatz I need help. When the user, for example, guy, presses on the male symbol, the male avatar is supposed to show, but it is not showing.


TeamCity Ignite :: Ignite Cache Tx Recovery [Build 255](http://204.14.53.152/viewLog.html?buildId=59901&buildTypeId=Ignite_IgniteCacheTxRecover&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 74 Build time: 00:13:00


TeamCity Ignite :: Ignite Data Strucutures [Build 1787](http://204.14.53.152/viewLog.html?buildId=59904&buildTypeId=Ignite_IgniteDataStrucutures&guest=1) is now running


можно по модному keyword arguments юзать
https://robots.thoughtbot.com/ruby-2-keyword-arguments


RoomAirflowNetwork (lgu1234) - Win64-Windows-7-VisualStudio-12: OK (1796 of 1796 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)


nice. This repo needs a better hadleyesque name to convey this is db orientated.


I think Dave likes double quotes (") rather than single (') for html... LOL


Oh bravo a_ferron la gloire !


kde-misc/kdiff3 needs for qt5 builds -kde too


Is this still pending, or should the test go away?


FYI - The page on the tutorial for this appears to be unavailable.  The page before is:

http://guides.emberjs.com/v1.10.0/getting-started/accepting-edits/
(*this works*)

The page for this step is:

 http://guides.emberjs.com/v1.10.0/getting-started/deleting-todos/
(*I just see a blank page*)

The following page is:

http://guides.emberjs.com/v1.10.0/getting-started/adding-child-routes/
(*this works*)


Meat is all here.


@sophron The README still says MIT License.


Like database...ic?


I like to see this... No - I love to see it


Please declare a final static constant RANDOM and use RANDOM.nextInt(Integer.MAX_VALUE).
A random double like this is hard to predict the format, e.g., does it contain '.' or not? This may make it hard to parse.


Yarr


Looks like a mistake, closing.


Você quer fazer build toda vez? Não seria melhor baixar a imagem a partir da nuvem? Tem como integrar os dockerfiles aqui do github para fazer build automaticamente na nuvem. Se quiser lhe ajudo nisso.


Note to self: this is safe against directory traversal because `encodeURIComponent` transforms `/` to `%2F`.


TeamCity Ignite :: Ignite Cache Full API Multi JVM [Build 135](http://204.14.53.152/viewLog.html?buildId=59899&buildTypeId=Ignite_IgniteCacheFullApiMultiJvm&guest=1) outcome was **FAILURE**
Summary: Tests failed: 2 (2 new), passed: 4885, muted: 278 Build time: 00:36:23
### Failed tests
```
org.apache.ignite.testsuites.IgniteCacheFullApiMultiJvmSelfTestSuite: org.apache.ignite.internal.processors.cache.multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll: junit.framework.AssertionFailedError: expected:<64> but was:<8>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

org.apache.ignite.testsuites.IgniteCacheFullApiMultiJvmSelfTestSuite: org.apache.ignite.internal.processors.cache.multijvm.GridCacheAtomicNearEnabledFairAffinityMultiJvmFullApiSelfTest.testPutAllPutAll: junit.framework.AssertionFailedError: expected:<9> but was:<3>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

```


TeamCity Ignite :: Ignite Examples [Build 1608](http://204.14.53.152/viewLog.html?buildId=59905&buildTypeId=Ignite_IgniteExamples&guest=1) is now running


note: trap_Cmd_ExecuteText will not be sent to network players.


Seria melhor tirar esse peso do usuário e a build fazer a partir do commit.


:+1: thanks. I thought the error was from the other block.


**[phpUnit_trunkUnit run failed](http://qa-s2.wikia-prod:8080/job/phpUnit_trunkUnit/8065/testReport/) for this commit**


Why did you remove that constraint?


idem


@alanhamlett The solution discussed over email was more like:

```python
directory = os.path.dirname(file_name)
available_files = os.listdir(directory)
available_extensions = zip(*map(os.path.splitext, available_files))[1]

if extension.lower() == 'h':
    if  '.cpp' in available_extensions:
        return 'C++'
    if '.c' in available_extensions:
        return 'C'
```


If we are using any CONTEXT at all, we should have confidence that it is the leaf managed context. I'd return a failure code or an all zero context vs. returning a non-leaf CONTEXT. If getting that confidence requires changes in how we suspend managed threads then we should investigate what is necessary.


Yes...... Yes I did


www-client/qupzilla needs for qt5 build -kde too


window.alert please


@acidprime I have more changes to come and once I get a better version I will create a PR.  Until then this is primary for my use.  The plan is to get away from using the binary and try and use the r10k gem directly.
Also I am not storing data in the r10k yaml file I only added it as I thought it was required when using the r10k gem directly.   The configuration for this agent should be in the server.cfg mcollective file.


Thanks, fixed.


"uneeded"


Just found that this is an undefined variable when trying to run raven.


Changed "uneeded" -> "unneeded"


please use `nextInt(Integer.MAX_VALUE)` to generate non-negative integers.


TeamCity Ignite :: Ignite Compute Grid [Build 1754](http://204.14.53.152/viewLog.html?buildId=59903&buildTypeId=Ignite_IgniteComputeGrid&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 200 Build time: 00:15:46
### Failed tests
```
org.apache.ignite.testsuites.IgniteComputeGridTestSuite: org.apache.ignite.internal.GridProjectionLocalJobMultipleArgumentsSelfTest.testCall: junit.framework.AssertionFailedError: expected:<3> but was:<2>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.failNotEquals(Assert.java:329)

```


TeamCity Ignite :: Ignite GCE [Build 243](http://204.14.53.152/viewLog.html?buildId=59906&buildTypeId=Ignite_Gce&guest=1) is now running


No it won't be rechecked in the solver.  That was whole reason I created a
`getEffectiveCollisionEfficiencies` function rather than using
`getEffectivePressure` every time.  That way it is called in the
ReactionSystem.initializeModel step, and then the coefficients are stored
there until integration to t_end is completed.

On Mon, Aug 10, 2015 at 5:56 PM, Richard West <notifications@github.com>
wrote:

> Just checking: this isomorphism checking isn't done inside a tight loop in
> the solver? I don't *think* it is, but wanted to be sure...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ReactionMechanismGenerator/RMG-Py/commit/bf33b5fda9051844a07f5a709b1c5201c763ef24#commitcomment-12626336>
> .
>

--
Connie Gao
connieg@mit.edu || homepage <http://www.conniegao.com> || 978-500-5197
Chemical Engineering PhD Candidate
Massachusetts Institute of Technology


I think there is a error, it should be Router.route('/', {name: 'postList'});


@alanhamlett Sorry, my bad. I went over the email again, and it is as you have implemented it. I didn't read it properly, thought you will check for the presence of a `cpp` file, which is the solution that would work for me.


Whoops. Fixed.

On Mon, Aug 10, 2015 at 3:18 PM, Ziyang Liu <notifications@github.com>
wrote:

> please use nextInt(Integer.MAX_VALUE) to generate non-negative integers.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/xkrogen/gobblin/commit/fecd99ddf8980f5d50c40d92fe244870c355fc09#commitcomment-12626704>
> .
>


So, this whole selection and object thing, why even have the selection variable inside the function, why not just use the object parameter?


deprecate != depreciate :)


I need to take a closer look at the semantics of io.ReadAt(), but I suspect the EOF behavior here deviates slightly.  This is probably supposed to return an UnexpectedEOF error when a ReadAt() comes in requesting more bytes than is available at the offset.  Something to look at later...


Which variable is undefined for you? ``lines`` is declared immediately in this function


@ouchadam one thing the design library actually made easier..

![scrollingappbar](https://cloud.githubusercontent.com/assets/2678555/9185783/ba688250-3fb6-11e5-8b0d-ca9f0b3e73ea.gif)


Why did you change it back to != ? You could fix the problem without doing that, and it better supports future updates to use the method. Comparing pointers may not always work.


TeamCity Ignite :: Ignite GCE [Build 243](http://204.14.53.152/viewLog.html?buildId=59906&buildTypeId=Ignite_Gce&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1 Build time: 00:03:51


TeamCity Ignite :: Ignite Geospacial Indexing [Build 1577](http://204.14.53.152/viewLog.html?buildId=59907&buildTypeId=Ignite_IgniteGeospacialIndexing&guest=1) is now running


TeamCity Ignite :: Ignite Examples [Build 1608](http://204.14.53.152/viewLog.html?buildId=59905&buildTypeId=Ignite_IgniteExamples&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 73, muted: 1 Build time: 00:12:26


TeamCity Ignite :: Ignite H2 Indexing [Build 1594](http://204.14.53.152/viewLog.html?buildId=59908&buildTypeId=Ignite_IgniteH2Indexing&guest=1) is now running


That's why the server crashed with EssentialsPE! D:


what vendor branch should i be using?


Whoops!
That'll be fixed in the next push, I'll wait to see what else needs doing first so as not to thrash the builders all day.


Type system? What's that? O.o


I know that the commit says "still needs some work", but just in case you didn't notice, the values of higher \sigma are 0.2, shouldn't be 0.1? and also I think the \ref to figures are to the old ones .


This is the same line as below? So remove this?


Hey man thanks for doing all this. I'm sorry I dropped off the map again,
it really is hard for me to find time for hobbies like this, but if I can
still help in any way I am happy to.

On Sunday, 9 August 2015, Jaka Kranjc <notifications@github.com> wrote:

> Oh and just want to repeat what a gold mine your bug list is. Thanks
> again! Now that I have some will to work on pst, things are improving
> rapidly.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/chilvence/gemrb/commit/f7dfefe9d1ae1bf235b19c3c75eae0c51143ef19#commitcomment-12605059>
> .
>


@michaelficarra What would you suggest as an alternative?


What does dis do? :3 Something about N3DS support, I see...


Out of curiosity, why don't we leave a trailing comma on the array here, so adding new indices doesn't need to also modify the prior line by adding a comma there?


Why would frame be `undefined` in this case? I think this is not a good fix. If frame ever is undefined, we should find the cases when it is true and fix those instead.


It detects n3ds emunand ;)


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (747 of 747 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-7.2%25-green.svg)


TeamCity Ignite :: Ignite Data Strucutures [Build 1787](http://204.14.53.152/viewLog.html?buildId=59904&buildTypeId=Ignite_IgniteDataStrucutures&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 418, muted: 92 Build time: 00:18:49


TeamCity Ignite :: Ignite Hadoop [Build 1628](http://204.14.53.152/viewLog.html?buildId=59909&buildTypeId=Ignite_IgniteHadoop&guest=1) is now running


Awe yeah! I'm slightly excited even though I don't have a N3DS 0~0