But this PR https://github.com/arvidn/libtorrent/pull/53 is super minimal, @ssiloti  don't you think that unless the code becomes unmaintainable, having support for WinXP is still reasonable.


Ok, sounds good, feel free to make those updates.

On Wed, Jul 29, 2015 at 12:14 PM, Benjamin Goering
<notifications@github.com> wrote:

> wall has to do the same thing (I think?) but
> 1) triggers off window resize event
> 2) debounces before any dom reading
> https://github.com/Livefyre/streamhub-wall/blob/rc/src/wall-view.js#L55
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/Livefyre/streamhub-map/commit/adffb28426e58a3646c61e4806322ab1d8e35d36#commitcomment-12428868


just DRY-ing up using this data formatter as a value transformer. instead of duplicating this property, just return:

``` objc
+ (NSValueTransformer*)lastModifiedJSONTransformer... {
  return [[NSDateFormatter wmf_iso8601Formatter] dateFromString:value];
}
// or
+ (NSValueTransformer*)lastModifiedJSONTransformer... {
  return [NSValueTransformer transformerForDateFormatter:[NSDateFormatter iso8601DateFormatter]];
}
````


```
if (redisGetReply(conn->handle, (void **)&reply) != REDIS_OK)  break;
```


I personally don't like capitalizing titles like that. See "Basic usage", "Dates and times", and "Advanced usage" for prior art in this readme.


Once the API is finished, then we'll merge it in with the other shit.


http://i.imgur.com/sYfvDMk.jpg
http://i.imgur.com/7rrEMg4.jpg
http://i.imgur.com/Pg6f3cj.jpg

some screenshots


Out of curiosity why don't you like it?


Yeah. Not a big deal, but just wanted to make sure we were on the same
page.

On Wednesday, July 29, 2015, bgoodri <notifications@github.com> wrote:

> I see. We may have to return cov.scaled from stanreg or take the upper left
> block of covmat.
>
> On Wed, Jul 29, 2015 at 3:10 PM, Jonah Gabry <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
> wrote:
>
> > Yes but the output from stan_glm is the same as the output from stanreg
> > except maybe with x,y, and/or model removed. I think cov.scaled is
> included
> > in the list returned by stan_glm.fit, but that gets fed into stanreg
> before
> > being returned by stan_glm.
> >
> > On Wednesday, July 29, 2015, bgoodri <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> >
> > > Isn't the input to posterior_predict the output from stan_glm? In that
> > > case, cov.scaled is an element of that but not of the stanfit element.
> > >
> > > On Wed, Jul 29, 2015 at 2:38 PM, Jonah Gabry <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
> > > wrote:
> > >
> > > > Oops, sorry I meant cov.scaled not cov.unscaled. What I was trying to
> > say
> > > > was that if stanreg doesn't return cov.scaled then we can't recreate
> L
> > > > inside posterior_predict since the input to posterior predict is the
> > > output
> > > > from stanreg.
> > > >
> > > > On Wed, Jul 29, 2015 at 1:56 PM, bgoodri <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > >
> > > > > I am not seeing where cov.unscaled is used. We have an element
> called
> > > > > cov.scaled as part of the list and there is also covmat from
> > stanreg().
> > > > For
> > > > > posterior_predict, I guess you need to copy that part of stanreg()
> or
> > > > else
> > > > > we need to return stanmat also.
> > > > >
> > > > > On Wed, Jul 29, 2015 at 11:44 AM, Jonah Gabry <
> > > notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
> > > > > wrote:
> > > > >
> > > > > > @bgoodri <https://github.com/bgoodri> If we take stanfit =
> > > > > stanfit$stanfit
> > > > > > for non-mcmc models then we will lose things like cov.unscaled,
> > > right?
> > > > If
> > > > > > we're going to have posterior_predict work for non-mcmc then
> won't
> > we
> > > > > > need to recreate L?
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly or view it on GitHub
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12423867
> > > > > >
> > > > > > .
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly or view it on GitHub
> > > > > <
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12427070
> > > > >
> > > > > .
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428067
> > > >
> > > > .
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428248
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428781
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428967>
> .
>


Looks very nice :+1:
But will this change break thread-safety?


@peterhuene in your second sentence above, did you mean "only *non*-primitive types need to be moved"?


I've made this mistake so many times. Did it actually bite you, or did you just remember/learn about it and fix the issue?

Good catch either way!


if not check the result from redisGetReply, can get bad behaviors!
```
if (redisGetReply(conn->handle, (void **)&reply) != REDIS_OK)  break;
```


Also, you could have made a separate commit for `common-bq/src/main/scala/com/socrata/bq/soql/SoQLAnalysisSqlizer.scala` to commit the actual changes to the conversion, and put the changes to your tests in another commit. This just makes it more readable to someone looking at the pull request.


@jbowens No regexses, hah? :-)


is it really `2` we should be passing to `find_articles`? This seams like it will build `http://www1.folha.uol.com.br/ultimas-noticias/noticias-2.shtml` as the url, which exists, but I don't understand why it should be the one we look at.


Oh... Thanks!


Hi @jscaber, I am not sure why this change is necessary as it is not a transfor m operation, but a merge operation?


I'm +1 on that approach (drop unnecessary function, add a brief comment why).


Do we need to make this configurable?


Hello @brianchandotcom

Here I will try to explain why we need this:
The idea is that the developers will be able to configure the new JavaScript Loader we introduced recently.

Basically, when a developer works on a module, he will create a .js file with instructions, specific for the Loader. Then, using the code below, all these instructions will be collected and Loader will read them:

```
(function() {
	<liferay-util:dynamic-include key="com.liferay.portal.js.loader.modules.config" />
}());
```

That's why the name is "js.loader.modules.config" - to state that these instructions are for the Loader.

Thanks,


Was this just for debugging support, or do you want the user to see this? I was surprised to see it while playing the game.


@vr2262

error: "(builtins.ValueError) badly formed hexadecimal UUID string [SQL: 'INSERT INTO doko.answer_photo (id, the_allow_other, the_allow_dont_know, other, dont_know, main_answer) VALUES (%(id)s, %(the_allow_other)s, %(the_allow_dont_know)s, %(other)s, %(dont_know)s, %(main_answer)s)'

Submitting is causing a problem. I tried both webp and png base64 formats


The tests didn't catch it, but it wouldn't work when I was manually testing
it.

On Wed, Jul 29, 2015 at 2:24 PM Colin Jones <notifications@github.com>
wrote:

> I've made this mistake so many times. Did it actually bite you, or did you
> just remember/learn about it and fix the issue?
>
> Good catch either way!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/hkgumbs/tictactoe-java/commit/dafa75ca7fd9adc8333d94aa0ac1cd7015d8b421#commitcomment-12429076>
> .
>


Are you missing a Process_Mark_Stack() here? I am under impression that there could have some series left in the GC_Stack. or could you add an assert here?


[The rules](https://en.wikipedia.org/wiki/Letter_case#Case_styles) are difficult and annoying, and the obscure which words are proper nouns. I use sentence case in my blog (https://github.com/tfausak/tfausak.github.io/commit/103e79c). I would use mid-sentence case, but that's weird enough that it would draw attention to itself.


Yes indeed :/ Edited to reduce confusion.


Are the brackets not needed, does this work with Dash?

Also, perhaps the `listContains` method should be responsible for the `[ -n "$1" ]` check.


what about multiple section "levels"?

- Section 1
  - Section 1.1
- etc...


Sure, will fix it.


It seems odd to write a method explicitly for unit testing only.


WIT Comments added


Well, the photo question backend was never completed. Are you trying to set your answer to the actual base64 image? The backend assumes that the answer is the UUID of a photo that already exist in the database... and there's no endpoint for that...


A few tests got deleted here - what's the reason? Do you lose any confidence in the test suite as a result? Why or why not?


ok, merged with some changes discussed with @ibriano


Yea youre right, we talked about this. Didn't know you already made the change to UUID's.


How much would it hurt to drop the `SERVER_RUNNING` variable and just call the `serverRunning` method twice?  The code would certainly look cleaner.


Sounds good


I'm not sure that works on non-*n*x operating systems.


1718_setpoint_managers (mbadams5) - x86_64-MacOS-10.9-clang: Tests Failed

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


I see. No problem, just a sanity check.


WIT Comment closed


> Note that I've done it that way to do the same as for traps. And for traps, the wooden door do not show "trap".

Ah I see. For me, the "trap" part in the "Spike trap" and "Boulder trap" is indeed part of the name, because they are the best definition for what the object is. On the other hand the "Cannon" and "Wooden door" don't need trap, as their names also define their function well enough. So for me the "trap" in "Spike trap" does not refer to the fact that the object is from the trap category, but that it's a trap with spikes... Not sure if I'm being clear here... Semantics :-P


Why the line space


Well actually it was always UUID: https://github.com/SEL-Columbia/dokomoforms/commit/d6fe1d23a109d993fba06a5332a115c13a2b8657#diff-137918e151cc8022a97135a5862c3f8bR130


IMO the current behaviour is fine as it is. The only problem is that current, researches are done very quickly, so indeed you might unlock a couple researches while designing your new tree, and that can be annoying if you would have prefered to put research points somewhere else. But for the time being it's good enough.


if not check the result from redisGetReply, can get bad behaviors!
```
if (redisGetReply(conn->handle, (void **)&reply) != REDIS_OK)  break;
```


Sure. No hurry. Let me know if I can help you with something. cu and good night :crescent_moon:


RadianceRefactor (rpg777) - Win64-Windows-7-VisualStudio-12: OK (2198 of 2215 tests passed)

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


That's true, so the gain is not as evident as I thought :)


Probably, but unfortunately it is not easily configurable.  I understand I just forked turnpike to unblock our UI guys, however, I would rather see something similar merged into the the origin repo than maintain this fork.  Long way of saying that I might submit a PR to the original code to make such modifications easier and configurable (along with some other things I'm working on)


We originally were gonna store photos directly in the db no?


ping @mmoreram please :)

Nice contribution :+1:


Shouldn't that be min, not max?


Well, thing is some things from the API you will need to finish this, and I don't want to hold you up from that


@psychon
> Is it really worth optimizing for non-visible tooltips?

At least that part was disrupting during my debugging.  Some of my widgets are called every few seconds, and since I do not use the tooltips with them 99% of the time, it appeared to be a waste of resources to me.

And generating the text could also be non-trivial (therefore I'd like to use the `.visible` check in my vicious formatting callback.

It would be possible to use the tooltip's timer interface/callback instead though - I've first thought that using a timer might be too much, but it's fitting my use case anyway.  I will try that instead (and remove this commit).

And I don't have a use case for `hide_callback` though.


And what about titlebars?


That sounds like a good plan.  Even if that PR isn't accepted it would still be better to handle this as a configurable option.  I don't think we'd want it on in production.


The actual training strike movements of the trainees are no simple emotes. there are new animkit set dbc's that contain all the emote datas.


Just use `$TRAVIS_PHP_VERSION` to check for the php-version, see e.g. https://github.com/symfony/symfony/blob/2.8/.travis.yml


Ack.  No worries about that right now, obviously...


Nah, ``fr_redis_response_print`` just needs to be moved past the check for ``REDIS_RCODE_SUCCESS``.  The code wouldn't do anything bad as it is, fr_redis_response_print just returns if passed a NULL reply.  But it is inefficient calling a function which might not do anything.


I'm not sure why the permissions are being changed.  Does a fresh backup/restore work without this?  This should be a separate patch anyway.


This should be resolved in the other direction the ```(0xffl & ...)``` is necessary. ```(long)...``` is a bug, leads to wrong results


best parts from all this shit

![Bild](http://i.imgur.com/WG3Z0hx.jpg)
![Bild](http://i.imgur.com/0lSd8fz.jpg)


To keep in line with other files there should be a newline at the end of the file.


Would be good to put a comment explaining this as it appears odd.
This controller is only used to create/manage Area Templates hence being restricted to people who can create new cap_area records.


Unfortunately so. Gonna hope and pray for an internal build to make its way to us. If so, it will be dramatically easier.


O horizonte de pesuisa é criar modelos de produção de audiovisual interativo telemático e televisivo digital a partir de um conjunto de princípios (investigativismo, colaborativismo/participacionismo, cibertextualidade, procedimentalidade/ludicidade, revesabilidade).

Eles provém de inferências sobre a história do audiovisual documentário - que é a minha praia. A história do avdoc manifesta uma luta por reconhecimento (honnethiana), na qual a "evolução moral" se realiza pela progressiva emancipação dos três polos actanciais: "diante da objetiva" o "ator social" ganha cada vez mais poder de determinar a produção da imagem e a sua apropriação social; detrás da objetiva, o "operator" tem cada vez mais compromisso com o ator social e legitimidade para manifestar pontos de vista situados, corporalmente marcados, não neutros (ou seja, um olhar corporificado em um que tem cor, gênero, idade, classe social, etnia, e outras marcas de não-neutralidade); e o "spectator" abandona uma posição de teórico sobre o mundo, passando a ser endereçado como um sujeito político, que é instigado, mobilizado, comovido, comprometido (que deixa de ser um "espectador" ao qual são dirigidas representações pretensamente omniscientes e heterodiegéticas - o filme sabe e ensina tudo de fora do mundo e da história, para se tornar um "apreciador" do qual são demandadas ações no mundo histórico e social). A idéia central é que a evolução das formas simbólicas é uma deriva história em que eticidade e estilística se co-determinam, ou seja, que se as poéticas são criadores de discursos e realidades políticas, a emancipação é sempre a projeção de arranjos experimentais de produção de representações políticas e de relações de produção econômicas. Uma deriva ético-estilística.

Na dimensão ética, os "novos sistemas" (para usar o termo do Maliévitch) se expressariam pelo...

1) "Investigativismo" -- Quem melhor pesquisa hoje  a vida social é o cidadão, ou a "ciência entusiástica" (ou 'amadora', como gosta o Henrique Parra); adeus aos campeões do esclarecimento: jornalistas, cientistas políticos, antropólogos (foi mal 9s, dançamos!). Principalmente porque o esforço para consolidar boa parte dos fatos de realidades sociais difusas mais relevantes exige tanto investimento e tanta diversidade de habilidades que quase não há mais grupo pesquisa ou equipe de jornalismo investigativo que o faça: só a própria sociedade civil pode se fazer saber sobre si mesma: crowdsourcing. (O caso mais paroxístico a respeito é o projeto free the files (do Pro Publica), mas todo o projeto do cmi ou das midias livres se apoia nisso, né?). Acredito que o avdoc interativo (tvdi e idocs) é uma ótima ferramenta para promover, agregar, consolidar e dar visibilidade a essa autopesquisa social.

e no...

2) Colaborativismo/participacionismo: a eticidade da produção de arranjos para ampliação reflexividade social e política não está só no que ela mostra sobre o mundo social e a história. Ela se estende para a criação de laços de solidariedade entre movimentos sociais de oposição (a tal "comunicação horizontal" de que fala o Downing, e cujo maior exemplo se encontra nos primeiros comuniqués no EZLN), assim como com cidadãos politicamente ativos autodependentes. Ao nos organizarmos para investigar, investigamos como nos organizar e passamos a ter mais disposição para compromissos com planos de ação coletiva de prazo mais longo.

(Quase não preciso lembrar que esses dois princípios éticos são corolarios, nas circunstâncias históricas atuais, dos princípios de "aberturidade" da ética hacker, do software libre e da autonomia democrática, né?)

Na dimensão estilística (não vamos chamar de "estética", porque este termo é saturado de pressupostos de espectatorialidade subjetiva individual que não nos interessam, nem ética, nem heuristicamente), esses princípios éticos se corporificam como enunciações que tendem a ter as seguintes características.

3) Cibertextualidade dinâmica, ou seja, além de uma não-linearidade navegável da superfície textual, teremos um uso coletivo do artefato que conduz a mutações no texto: na sua composição, na estrutura de conexões entre segmentos textuais e interface de acesso (design das affordances de uso).

4) Procedimentalidade/ludicidade, porque, se de um lado a participação de agentes heterogêneos, a capacidade de conexão coerente entre segmentos textuais (oriundos das contribuições dos públicos) depende de estes terem uma série de propriedades compartilhadas: jogar "cama de gato" é possível de muitas maneiras, seguindo uma gama bem ampla de percursos, mas não existe sem um anel de barbante, quatro mãos, duas pessoas, uma configuração de abertura e um punhado de operações de transformação. De outro lado, a procedimentalização / ludicização da produção leva à experiência da criação sem autoria individual, e a indução de uma corporeidade coletiva, o que realimenta afetivamente a ética colaborativa/participativa. Do ponto de vista do resultado, a procedimentalização/ludicização propicia a emergência de uma estrutura de conexões, formadas nos pontos de bifurcação de cada variante de um processo (já viram Smoking/Non-smoking do Alain Resnais?).

Há um campo de pesquisa poética bastante intrigante, trandisciplinar e trasmediático, a desbravar. Alguns de seus pontos de inflexão, porém, já delineam uma linhagem de tendência politicamente emancipatória, ligada à investigações meta-poéticas, interssadas na criação de artefatos simbólicos (ou "conceituais") de propósito político-prefigurativo (ou seja, de instauração de arranjos de relações de trocas de valores). Historicamente, essas investigações são tematicamente fragmentadas, compreendendo desde explorações sobre poéticas sobre a apropriação social do signo artístico ("Dos novos sistemas em arte", Maliévitch; "Six Years", Lucy Lippard; "I am in search of field character", Joseph Beuys; "Inserçoes em Circuitos Ideológicos", Cildo Meireles; "Proposições", Lygia Clark; &al.) até arranjos produtivos de economia política experimental - Rede Indymedia, coletivos de "artivismo" altermundista, Rede Fora do Eixo, SuperFlex, &alii. A vassalização dessas experiências a lógicas capitalísticas e político-concentratórias podem ser, em boa medida, serem devidas à sedentarização das práticas experimentais em campos preexistentes - com o abandono da transmedialidade/eticidade original. O ponto de contato em toda esta investigação reside no delineamento de um "protocolo" gerativo, uma sequência condicional de procedimentos de transformação material e simbólica (sinedóquica e catacrética) através do qual uma multidão de agentes autodependentes compõe um arranjo distribuído de sentidos. Alguns deles, sedentários, são distribuídos como jogos reais, com temporalidade cronológica linear (presente como passagem do passado para o futuro), distribuição estável de funções dramaturgicas (o que acarreta uma distribuição também sendentarizada de funções de representação política); tais gabaritos, porém, servem de fundamento para jogos imaginários, de temporalidade não-cronológica (do presente como irrupção de outros futuros e interrupção da projeção do passado). É da experiencia prática de oficinas de aprendizado de mídias audiovisuaisque o uso de jogos de improvisação orientada para a comunicação (ou seja, restituição do sentido do enunciatário na mente do apreciador) ocasiona interpretações diversivas (de eclosão de sentidos inexistentes na relação de enunciação, para enunciatários e enunciadores.)

5) Revesabilidade agencial é um horizonte estilístico de uma equivalência teória e prática entre quem grava, quem é gravado e para quem se gravam ou transmitem as imagens. Sempre achei meio estranho que a teoria do cinema falasse tanto da perspectiva do público espectador ou dos cineastas/autores/produtores, mas quase nunca da experiência de ser "ator social". Na verdade, essa perspectiva só entra no jogo catacrético da representação política por meios audiovisuais nos momentos em que o sujeito deixa de ser objeto do discurso alheio, seja como tema, seja como alvo.


ok, you have the comment here but I think it's better in the docstring for the whole controller as this is controller-wide


the hotkeying invalidates current language translations, are these & intended?


> And what about titlebars?

Good catch.. forgot to add that from my stash(es).  Added it.


90946736_SHRgt1_4567 (mjwitte) - i386-Windows-7-VisualStudio-12: OK (1776 of 1779 tests passed)

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


97902934_ZoneMixing (macumber) - i386-Windows-7-VisualStudio-12: OK (2202 of 2235 tests passed)

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


This is 2 separate queries which I tink are better done as a single join?


Mark_Devices calls MARK_SERIES_DEEP, and MARK_SERIES_DEEP calls Process_Mark_Stack.  So at the end of MARK_SERIES_DEEP you expect the GC_Mark_Stack to be empty.  But there definitely should be assertions at the beginning and end of Recycle that the mark stack *is* empty, so I will add those!


In fact in this case the 2nd is completely redundant!?
The 2nd query is 'Give me all the IDs whose ID match this set of IDs!?!?!?


Hi @AndreasHeger, merge does not allow the use of "add_inputs".
Is there a better way to do this? I cannot see how it could be done with merge.


@NicholasBuse No problem! It was designed to make updates way faster, and it looks like it helped!


I would move all these below the if not r.record.
I know that that's a rare case to encounter but in general do work as late as possible...avoid doing it needlessly before a branch which doesn't use it...


I noticed setting banner to `nil` currently removes the useful Update/Revert buttons. Small fix to change that.


Checks a tree for what? Is it checking if levels are inside tree?


Think I introduced it myself before ;-)


Can in fact go below the permission check, which is a little more likely to be encountered.


I'm not sure anymore... It's not too late to do it that way, but that way still seems like trouble.


This type of function would be pretty trivial to unit test.  We could split up this file into being pure functions (i.e libdss.sh), source that from a `test.sh` that does e.g.

```
DATA_SIZE=42 check_data_size_syntax
DATA_SIZE=!@$!@ check_data_size_syntax
...
```

?


@EisenbergEffect Is this error message enough? Could we do it better? Here is how it looks like in the console:
```shell
C:\Users\Shuhel\Workspace\aurelia\skeleton-navigation (master)
λ aurelia bundle
info: Creating bundle ...

err  Multiple mathces found for module: 'github:aurelia/templating-binding'. Matches are:

       github:aurelia/templating-binding@0.12.0
       github:aurelia/templating-binding@0.12.2

     Try including specific version number. Or, resolve the conflict with manually with 'jspm'

Version conflict found in module names specified in `aureliafile`
```


Can't agree with you, already checked for that and didn't find something what could be used for them. Also we don't have these animations implemented, nor in SAI.


No, here log is only used to call `log.Fatal`, which isn't supported by cfssl/log.

@kisom @grittygrease It would be nice if there were a version of `log.Critical` that also called `os.Exit(1)`...


The new `given?` method is not just for checking `nil` vs not passed. It really says whether or not an argument was passed matching a particular filter. I'm not sure why you would, but you could use it even with defaults other than `nil`.

I'll suggest a slight change:

Optional inputs can be defined by using the `:default` option as described in the [Filters][#filters] section. Within the interaction provided and default values are merged to create `inputs`. There are times where it is useful to know whether a value was passed to `run` or the result of a filter default. In particular, it is useful when `nil` is an acceptable value. For example, you may optionally track your users' birthdays. You can use the `given?` predicate to see if an input was even passed to `run`.


So this is still hardcoded here...a little frustrating to have issues unaddressed in fresh requests to review.


I like these examples.


When is this error condition likely to be encountered?
I like comments explaining why this check is put in


@CHenrie Please review


Good Job :+1:


нашёл баг:
FAB теперь не опускается вниз


Do you think we will really have further reading for every type? If not, we'd rather not write "coming soon". Claiming something to "come soon" for months and years  doesn't give the best impression...


Hey,

So when building project with maven it generates a new protocol.json using protocol files in barchomat/src/main/message. Can you please commit those files too?


@rjledger [This](https://github.com/Saleslogix/argos-saleslogix/commit/29559e3c6b23e3445267f25fa82c1ebde00216f8) commmit reverts this change and comes up with a predictable date stamp at runtime.


Not sure about the places where anEdge.ordinal() is used -> review!


Why the explicit label? Is it different to the default?
In general minimise the numebr of places to have to modify if the label needs to change for some reason...


Same here


1718_setpoint_managers (mbadams5) - x86_64-Linux-Ubuntu-14.04-clang-3.5: Build Failed

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


+1 :-)


added `eventLabel` and made it a required prop since it's a required field for `ga.outboundLink` as well


Are you sure we want to actually remove this assert, are we certain that it is no longer useful for catching inconsistent state problems?


So as to avoid the merge conflicts.


5051_fix_local_win_test (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (743 of 743 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.11%25-green.svg)


Will all countries really have the same list of levels?
I would think it's better to go with the default & have this introspected based on the gis_hierarchy?


Test


better to be consistent about whether there are spaces around the = or not


They are not intended. I don't know what happened.


Python => should have a space around the =


useful to have space to indent the levels to be able to more easily see the nesting


Freaking sweet. Does this just do 2 columns though? Or can you specify number somehow? Can't look right now.


Wouldn't it be better to make using the agent the default? It's connman-**simplified** for a reason ;)
If this really works I'd rather throw out our old config file hack.

If you want to keep support for the hack I would try to minimize the repeated code. On first glance the difference is the following:
``` javascript
  //configFiles.create(ssid, passphrase, next);
  connman.Agent.on('RequestInput', function(service, fields, cb){
    callback({"Passphrase": passphrase});
  });
```
Maybe you could add a condition, controlled by an extra argument that's passed to the `join` function?


Sounds reasonable. So who is going to run these test cases? This is sort of automated test cases we could run every time we commit new code to make sure things are not broken?


@mfsny please rebase to avoid merge conflicts (or let me do the merging) :+1:


As soon this function max31855_process() get out of stack all of his stack variables will also be freed.

Just change buf_tx/rx to static is wrong, because user have 2 max31855 running at the same time.
-2


Added `eventLabel` and made it a required prop since it's a required field for `ga.outboundLink` as well.

Also `<OutboundLink eventLabel='foo' ...>` is a lot clear than `<OutboudLink args={label: 'foo'}>` and I think it's less likely that people will forget to pass that prop.


I think it'd be clearer to have the logic here be `return 0` like the others if it matches.  Then the default in no matches is `return 1.`


This change has broken the iOS behaviour, because there are linebreaks. These linebreaks are later also in the .plist file and so the given url scheme is not as expected and contains linebreaks.


Thanks! If you want me to standardize the names, I can do that next week. I had to name the RadioGroupTab class to TemplateRadioGroupTab because a similarly named class already existed in the namespace. For consistency, I can rename them all Template<TabName>. I figured this would be a low-priority item as the actual class type is generally abstracted through usage. Also, I can probably add the other tab types next week if you would also like to include those. I only added and tested the ones we specifically needed to work with, but would be nice to have all of them available if needed.


1718_setpoint_managers (mbadams5) - 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)


Maybe the best thing would be to make covmat in stanreg be cov.unscaled?
The only downside I see is that if someone does vcov() they will get the
variance-covariance matrix for the unconstrained parameters rather than the
parameters of interest.

On Wed, Jul 29, 2015 at 3:23 PM, Jonah Gabry <notifications@github.com>
wrote:

> Yeah. Not a big deal, but just wanted to make sure we were on the same
> page.
>
> On Wednesday, July 29, 2015, bgoodri <notifications@github.com> wrote:
>
> > I see. We may have to return cov.scaled from stanreg or take the upper
> left
> > block of covmat.
> >
> > On Wed, Jul 29, 2015 at 3:10 PM, Jonah Gabry <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
> > wrote:
> >
> > > Yes but the output from stan_glm is the same as the output from stanreg
> > > except maybe with x,y, and/or model removed. I think cov.scaled is
> > included
> > > in the list returned by stan_glm.fit, but that gets fed into stanreg
> > before
> > > being returned by stan_glm.
> > >
> > > On Wednesday, July 29, 2015, bgoodri <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> > >
> > > > Isn't the input to posterior_predict the output from stan_glm? In
> that
> > > > case, cov.scaled is an element of that but not of the stanfit
> element.
> > > >
> > > > On Wed, Jul 29, 2015 at 2:38 PM, Jonah Gabry <
> notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
> > > > wrote:
> > > >
> > > > > Oops, sorry I meant cov.scaled not cov.unscaled. What I was trying
> to
> > > say
> > > > > was that if stanreg doesn't return cov.scaled then we can't
> recreate
> > L
> > > > > inside posterior_predict since the input to posterior predict is
> the
> > > > output
> > > > > from stanreg.
> > > > >
> > > > > On Wed, Jul 29, 2015 at 1:56 PM, bgoodri <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > > >
> > > > > > I am not seeing where cov.unscaled is used. We have an element
> > called
> > > > > > cov.scaled as part of the list and there is also covmat from
> > > stanreg().
> > > > > For
> > > > > > posterior_predict, I guess you need to copy that part of
> stanreg()
> > or
> > > > > else
> > > > > > we need to return stanmat also.
> > > > > >
> > > > > > On Wed, Jul 29, 2015 at 11:44 AM, Jonah Gabry <
> > > > notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
> > > > > > wrote:
> > > > > >
> > > > > > > @bgoodri <https://github.com/bgoodri> If we take stanfit =
> > > > > > stanfit$stanfit
> > > > > > > for non-mcmc models then we will lose things like cov.unscaled,
> > > > right?
> > > > > If
> > > > > > > we're going to have posterior_predict work for non-mcmc then
> > won't
> > > we
> > > > > > > need to recreate L?
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly or view it on GitHub
> > > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12423867
> > > > > > >
> > > > > > > .
> > > > > > >
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly or view it on GitHub
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12427070
> > > > > >
> > > > > > .
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly or view it on GitHub
> > > > > <
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428067
> > > > >
> > > > > .
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428248
> > > >
> > > > .
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428781
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428967
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12429067>
> .
>


ups - you are right, forgot about changing them to be on the heap.


debug log?


Ok, will change.


Should `undef` for `$content->{$object}{$key}` receive special treatment here? e.g. delete the hash entry?


sure, sounds good. thanks @tranquilChaos


It's weird, because I haven't added any hotkeys. It looks like Qt Creator added them automatically. It doesn't make sense for me.


Return type covariance is only supported for a pointer or reference type, which unfortunately `unique_ptr` or `shared_ptr` are not.  I'd have the base return `unique_ptr<abstract_config_value>` (naming side bar: that's a verbose way of saying what could be called `value` or `config::value`; "abstract" really shouldn't be part of a type name).  If the caller really needs a pointer to the derived type, then perhaps this shouldn't be virtual.  I know we're porting this from another language, so this seems like a construct that would be necessary in a language where users don't have explicit control over their memory, thus making "copies" of objects requires additional plumbing, while in C++ it's fairly trivial to do.


Fixed. Thanks!


Not sure about the syntax, it maybe like this?

string txt = @"~\SuperDealership-1\CarList.txt";


This change causes at least one downstream - HTCondor - to fail to compile, because it defines a pointer to `globus_gsi_cred_write_proxy` and so the change from `char` to `const char` causes an invalid conversion. This 7.9 update doesn't even seem to be announced at http://toolkit.globus.org/toolkit/advisories.html - surely a change like this should be a bit more prominently communicated?


THAT MAKES PERFECT SENSE!

Thanks Greg, I never would have considered that! I need to re seed it in
any case, or figure out how to have the JavaScript check for updates in the
txt file periodically. Any thoughts on how best to do that?

See you in the a.m.
Ashley

On Tuesday, July 28, 2015, Vidget <notifications@github.com> wrote:

> Awesome stuff Ashley, the Seeding from file work is exemplary!
> One thing I did notice that should probably be changed is this line of
> code in the Migrations/Configuration.cs
>
>   string txt = @"C:\Users\Ashley\Documents\Visual Studio 2013\Projects\SuperDealership-1\CarList.txt";
>
> to maybe something like this
>
>   string txt = @"\SuperDealership-1\CarList.txt";
>
> since it looks for the specific folder "Ashley" that may not exist on the
> users computer when seeding the first time.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/aKratzke/SuperDealership-1/commit/27efe41bd36f6aaea98b72e02ad943545de6a612#commitcomment-12410782>
> .
>


For your new scripts, please use the standard OpenEMR header:
http://www.open-emr.org/wiki/index.php/How_to_Document_Your_Code_Properly#Page-Level_DocBlock

(just change one for next revision to ensure it's correctly done; then can change the rest after that)


GroundDomainUpdate (sushobhit) - i386-Windows-7-VisualStudio-12: OK (1773 of 1777 tests passed)

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


Hmm. Looks like newlines were removed - any idea what setting I haven't set?


Test it out


change cocos2d-html5 engine -> Cocos2d JavaScript engine
             cocos2d-x engine -> Cocos2d C++ engine

thanks for correcting ; )


Hmmm.  I'll circle back around to this in the morning.


This should be fixed in d8690d1be6de61b0f7cc3a8b7fc76afb36936c07. Let me know if there are still problems on Travis.


I figured out why mine wasn't working after I download your copy. In your project file there are two TEMP databases it creates that weren't "included in project" at github.

These two files,

aspnet-SuperDealership-20150727044515.mdf
aspnet-SuperDealership-20150727044515_log.ldf

they should be in your project because yours worked fine, I had them in another version so I just dragged them in and everything worked perfect after that.

You may have to right-click on the file in the AppData folder and include it in the project as well.

Again excellent stuff!

Peace
greg


ahhh missed that sorry


I think it was because they didn't work so someone disabled it... I'll see if I can't find it for you...


I am determined to master github! Even if it doesn't make sense.


This is a test folder to keep random stuff. Hopefully some random stuff may be of value.


Should I keep the preventInContainer?


He said it wasn't implemented: https://github.com/OpenRCT2/OpenRCT2/pull/1686


2015 Unity Learning and Practice.


Super weird, I'm not currently seeing that error. Do you have the latest bower? (I think it's 1.4.1 or so) and make sure you have the right _Scroll-To_, bower is case sensitive.


第一版本


Cause the domain is taken ;-;
On Jul 28, 2015 9:28 PM, "gotjosh" <notifications@github.com> wrote:

> What?!?! Why?!?! The name was pretty cool already.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/huesitos/effdy/commit/00c8af61a6b5958642615567cea6b28562795a56#commitcomment-12410493>
> .
>


The general idea is that functions that work with absolute timestamps exist only in machine units versions, to help prevent floating point losses of precision. Time differences would be computed in machine units and *then* converted, e.g. mu_to_seconds(t2-t1).

This function will have problems if the device has been running for more than ~50 days at the latest.


@jaredpar probably added the newline by saving in vim.  Pretty sure VS always removes it (which we should fix)


会不会溢出？


just use qt5!  capybara-webkit is finally moving over to it.


We need to set first time gold file.


Should you pre condition at method entry or parameter access?


@racke try this branch out I also downloaded the google fonts and will try to add them in the morning.


@LionNatsu 我只是不知道怎么写好。。我也想遍历的


여기서 Volleyer, volleyer() , post 이런것들의 정체를 모르겠어요. 어디서온건지 라이브러리내에는 이런거가 없는거같은데?


@matthandlersux @a-wortman last round of comments addressed


전체적으로보면 LoginActivity 라는 클래스가 SplashLoginActivity 로 바뀌었고
LoginHelper 클래스가 새로 작성되서 삽입되었다고 보면 되는건가요?


Why is this `datasources` when the other package is called `sources`?


Got confused here thinking break always passed a value, but it sets it to "0" (NULL).  Due to null tolerance that winds up getting interpreted as an unset value later on, when I actually had it in my head that breaking a loop would return NONE! by default.

Yet returning UNSET! is better, and finesses the problem of "how would you break with an unset".  Combining that with the reminder that "break/with is a lot better than break/return or break/value", it seems that perhaps this points to a consistent solution for RETURN as well... to be zero arity and return UNSET! by default, and then have a /WITH refinement.

[Rambled in chat about it for a bit](http://chat.stackoverflow.com/transcript/message/24736070#24736070) because I felt like it was a sort of a *break/thru*.  But for the moment, I will patch this to return an UNSET!.


it got fairly confusing when two packages are named the same


ssssss


Fixed downloading of  FFMpeg, added downloading of MC, and additional environment variables.


No problem. I will add signed-off-by and create another PR.


fix_intel_compile_linux (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1775 of 1776 tests passed)

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


correct this when you have adequate data. .....:)
these days xda and others have been very very strict about GPL.


We can probably now remove the parens around `UIApplication.sharedApplication().windows`


fix_intel_compile_linux (mbadams5) - 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)


@droberts84 I'm struggling with Eager Loading bit.  Maybe we can discuss on Friday?  I'm currently getting the following error
> Missing partial users/_user with {:locale=>[:en], :formats=>[:html], :variants=>[], :handlers=>[:erb, :builder, :raw, :ruby, :coffee, :jbuilder]}.


I think you should chance this.


Here's a gameplay video someone recorded where the Mann Bros duo got the wrong companion:

https://www.youtube.com/watch?v=_o7brQyT-MY


Is this the expected output?

```
$ kubectl logs hello-world
hello”,”world
```


strange check


+1

As a matter of fact, I know that this will fail and I know why, but let's start by getting that failure reproducibly produced and documented.


looks like callback missed and you exit before it finishes.


![](http://piskel-imgstore-b.appspot.com/img/71769a9c-359c-11e5-a7d4-a758a0855ca8.gif)
Took so long to create the Apple Logo


srly m8

On Tue, Jul 28, 2015 at 7:57 AM, Paul Keith <notifications@github.com>
wrote:

> Killed the whitespace
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/CandyDevices/local_manifests/commit/fdd5362d418d2fdfba02f9886f133b635111dd82#commitcomment-12395245>
> .
>


Thanks for the explanations.
I could have improved more the codes, but still need to study more. =//


Consider:

    auto const cancelAfter = ctx.tx[~sfCancelAfter];
    auto const FinishAfter = ctx.tx[~sfFinishAfter];

    if (! cancelAfter && ! finishAfter)
        return temBAD_EXPIRATION;

    if (cancelAfter && finishAfter &&
            *cancelAfter <= *finishAfter)
        return temBAD_EXPIRATION;


Nit: double semicolon


Antes de incorporar estos cambios ¿quisieras validar mis comentarios anteriores sobre la forma de hacerlo correr adecuadamente? La otra cosa ¿con que fin incorporas una instrucción print() en el archivo de configuración base? ¿Sera que querías ver el resultado pero olvidaste borrarlo después?


revealed shouldn't be static, static means shared amount all objects with the same class. In that case, all the different MagicSearchToLocationEvent will either all reveal or not reveal. We want them to have their own individual value, it the static keyword should not be there.

fixed in https://github.com/magarena/magarena/commit/f78c96ae70a62b85437afbbdcbc87a82177384e7


Works on Travis now. Thanks!


What are the cases where you'd have different impls of DatasetWriter that is not ClockReady?


thanks


Nit: double semi-colon.


@zooko Yeah, it fails on compiling pycryptopp.


Follow naming conventions.


Misspelling 'canola'


No ``if(enabled)`` checks needed?


this archive is outdated. it had issues with the translations...


Shit - you are right… we have to capture the indent level here… so this won't work - back to the drawing board.


Thanks, you are right, and I fired this away too quickly. It is actually a single file "transform".


Yes, I noticed that. But it's hidden behind a for and if statement inside a function, which makes it very easy to be missed out. What if another Mark_* which just calls PUSH_* to be added?

I would like a Process_Mark_Stack() here anyway.


definitely not! will make it configurable one way or another.


@brandonly101 The delete all button has the 'recycle-bin-button' class and in your YUI you are adding a confirmation to elements with the class 'recycle-bin-button'. Wouldn't it then also be redundant to add in a YUI event handler for the 'recycle-bin-delete-all' class as well?


There's a few more differences that appear in further commits - mainly to remove that event listener after joining.


Yes, actually I don't like this loop, it feels too error-prone. The idea is that every iteration through the loop, we 1) decrement the semaphore, then 2) pop the corresponding message off the queue.

If there aren't any messages on any other partition queues, that's it: we do this n times, and then the next iteration, we cannot `acquire`, so we end the loop. But if there are messages on other queues, the semaphore will yield again, so we enter the loop but now the queue is empty - that's the "put one back": we "stole it from another queue".


Not needed, we don't have any in ``OnPlayVolume()``


ROUTINE_FFI_ARG_TYPES(rot) is not a block, so it should be "MARK_SERIES_SHALLOW(ROUTINE_FFI_ARG_TYPES(rot));"


User


Shouldn't I split this into two separate commits, one with implementation, and one containing test case?


I'm basically just worried that if I drop the code things will randomly start breaking. But... I'll try it.


d3death,

Yes, I will commit them within an hour.
I am making a client... maybe we can work together?
Add me on skype: seppe123


Er, that was for debugging. I meant to remove it.


Is there a good way to contact you like hangouts? I'd like to work with you on some bionic commits.


You could move to self-hosted git. Also, for a nifty issue tracker, you could use pit (michaeldv/pit)


@shakyShane could you update the changelog as well? Currently only `2.7.11` shows up: https://github.com/BrowserSync/browser-sync/blob/master/CHANGELOG.md


Leve a line route


r+


TeamCity LabkeyTrunk :: CDS postgres 9.4 [Build 224](https://teamcity.labkey.org/viewLog.html?buildId=263402&buildTypeId=LabkeyTrunk_CdsPostgres93) outcome was **FAILURE**
Summary: Snapshot dependency failed: LabkeyTrunk :: build Build time: 00:00:00


Yep. Just clearing the space.


TeamCity LabkeyRelease15.2 :: CDS postgres 9.4 [Build 14](https://teamcity.labkey.org/viewLog.html?buildId=263397&buildTypeId=LabkeyRelease152_CdsPostgres93) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 22 Build time: 00:34:59
### Failed tests
```
org.labkey.test.tests.CDSTest.verifyHomePage: <no details avaliable>

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

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

```


LGTM


Not liking the `,` for multiple variables declaration anymore?


Tomorrow I will remove that hotkeys


yes, looks like auto generated, see hotkeys under menu > image
-> autohotkeying tries to find first occurence of not yet used capital
letter in any surrounding.
Not really desired, although it could be quite handy if we got ctrl +
??? as hotkeys for common things like save / load / settings / ...
You can add a shortcut as a property directly to an action in the
designer. This will also write the hotkey next to the entry.


Filesize Jed.


Push needed


@jed


I'd have preferred to add it to `cleanup`, but then the unbound function would be saved rather than the class method. I'm not entirely happy with this solution, though. I think I'm going to change it to `@register_cleanup...JSShell.cleanup()`


Imageoptim or whatever


I recommend filtering out `stopwords.english` from `words` right after you first create `words` in line 296 instead of checking for it here.


Push Wrong


This might not be reliable as the newly allocaed memory is not zero'ed out anymore. Probably the whole idea of allowing GC to be run during the construction of a data type is not good. It just makes it construction and GC code more tightly coupled and fragile.


`__del__` makes sense for terminating the process, yeah. Thanks.


i used the scariest file size i could muster. i guess it wasn't enough. :cry:


Pretty good. Needs a bit of grammar fix. Typo..should be "matches". Need to add an article and create composite sentence "Try including a specific version number or resolve the conflict manually with jspm"


Regarding the frequency, this is what we currently have after the fixes from @nwolek

Not all filters specify frequency in terms of the -3db rolloff point. For example Chebyshev Type-2 filters specify the frequency at the beginning of the stop band.

In this case there is a resonance, which is the distinguishing thing you hear, so I'd be inclined to think that the resonant frequency is what you would want to specify.

@trond -- do you have any insights here?


WIT comment


Corrected the same


TCP slow start ran away in terror.


Am 29.07.2015 4:34 nachm. schrieb "diversys" <notifications@github.com>:
>
> Out of curiosity, why do we use date in the recipe name? Isn't version
not enough?

In this case it doesn't really matter because we don't have a gcc5 branch
for the buildtools. The date has a patch level meaning, which is related to
the buildtools repository only. In the past Haiku configure script could
check this date as a requirement. Not sure whether it's still useful or not
for gcc4.

Bye
Jerome


No, but it got rid of a rogue `lambda` in the profile results. I just wanted to make sure this was the actual cause of it.


Writing this, I'm wondering if this would be a better implementation of `flush`:
```
# Swap _messages away so concurrent consume() calls won't see it anymore
tmp = self._messages
self._messages = Queue()
[self._messages_arrived.acquire() for _ in tmp.get_nowait()]
```
(And in the last line, I'm wondering if it's safe to use `tmp.qsize()` but the documentation-bit that only promises "approximate size" isn't very reassuring..)


this change is for ies


Don't make fun of the gits! I'm offended, and that gives me right to censor you! Shut up!


this change is for modelsim


Not a huge difference in overall time, but `_debug` was one of the highest functions for cumulative time-in-function, and this fixed that.


You're welcome, @philipstears. :grinning:


Just FTR: That's correct. SvLEN is the buffer length. SvCUR is the string length (and the length that char * foo = SvPV(SV *sv, STRLEN len) sets into len).


This is retarded.


FYI @AlexandreArpin @ginmrt


TeamCity LabkeyTrunk :: CDS postgres 9.4 [Build 223](https://teamcity.labkey.org/viewLog.html?buildId=263399&buildTypeId=LabkeyTrunk_CdsPostgres93) outcome was **FAILURE**
Summary: Tests failed: 6 (1 new), passed: 19 Build time: 00:36:15
### Failed tests
```
org.labkey.test.tests.CDSTest.verifyGrid: <no details avaliable>

org.labkey.test.tests.CDSTest.verifyHomePage: <no details avaliable>

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

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

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

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

```


How about transitioning XML features to pure JSON end-to-end?

[Here's my proposal.](https://github.com/jeffpar/pcjs/issues/23)


"AAA"


Let's make this object look like {"top_level": top_level "category": category} so we can index it by key later on (it's clearer)


Am 29.07.2015 4:32 nachm. schrieb "gus knight" <notifications@github.com>:
>
> The plan is to switch GCC4 out for GCC5, correct?

I dunno yet. It might make sense for x86_64 or arm. Bootstrapping is still
one issue for instance, compatibility another.

Bye
Jérome


I greatly thank you for helping me in this and give me your time appreciation much that and thank you for helping me in my same project thanks, as I had doubt that I'm not using any server http proxy, is the direct connection so my server but I have a question the clientID when you connect will be an ID logically once you connected to the server , connects another customer with the same ID that produces no disconnection problems? Sorry these questions always appreciate their help


Thanks!


this change is for questa


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.854.b06459a35995a688a022552e028f0083057270d7](http://build.palaso.org/viewLog.html?buildId=60192&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 396, ignored: 3 Build time: 00:03:14


I dont understand why change 'boardRotation[0][0] * x + boardRotation[0][1] * y + boardRotation[0][2] * z' to 'lrintf(boardRotation[0][0] * x + boardRotation[1][0] * y + boardRotation[2][0] * z)'.
This equation isnt rotationmatix * column vector. This equation is symmetric rotationmatix * column vector.


this change is for vcs


Thanks Kevin.

First things:
1. Remove the following files from the commit:
.npmignore
.travis.yml
timeseries.png
package.json.old

More to come.


In terms of naming, how consistent do we want to keep that with the original library? The ruby port kept the exact names and just switched out camelCase for snake_case, so I followed that model.

I believe the reason this method exists is to allow creation of a config_value that has the same attributes as the original, but with a different origin (which I think refers to where in the document it came from, along with any comments). Not sure *why* that's needed, but I don't think it's the same thing as just a straight-up copy.

I might leave these new_copy methods out till I find where they're used, then come back and decide how best to implement them.


Should this test still be renamed?


I would have set `WARNING` as `logLevel`.


Ah nevermind, I see that it has merely been split into two tests


this change is for xsim


Не обязательно добавлять get 'account/index', root все сам сделает). Так у Вас сейчас получается два пути, которые введут в одно и тоже место и дают один и тот же результат.


what is namespace? it should not be looking for `apps/` in the cwd


Look at my comment above for when you generate the content of positive_keywords. Use an object so you don't use number indices.


I think, this could be removed now.


We're using Google's standards for documenting js code, so take a look at this link for some more information about it: https://developers.google.com/closure/compiler/docs/js-for-compiler?hl=en.

This is almost correct already, but when using this standard we need to indicate in the param type if it can be null or not. Object types like **Event** are nullable by default. In the case of this function the **event** param can never be null though, so we should set its type to be `{!Event}` to indicate that.

Also, this function is not public, so `@protected` should be added to the end of the doc block.


Er, no, I just wasn't paying enough attention.


Typo, "draw" should be "drawn"


Right, previously I split it into two tests so I could skip just the part that needed skipping. We have (correctly) decided to skip neither. I like the idea of smaller semantic tests, but don't have strong feelings.


Seems like this method returns an Array, not a Collection


Youcan remove `as_tensor_variable`, since the tests should always be executed with `device=cpu`.
What you have to do is to make sure the GPU tests are executed, even when `device=cpu`, if `cuda_available` is True (even if `cuda_enabled` is False). In that case, use `float32_shared...`, and includ GPU opts in the mode.


Why not just `return ++m_max_id;` with `m_max_id` set to the biggest id currently used?  Also, the minedge and maxedge parameters are unused and the PcgRandom include still exists in the header.


he Sander, ik kreeg een aantal mails met meldingen van jouw wijzigingen, ik kreeg een link naar: https://github.com/delden08/interface/commit/163ef869d5ed23c617169691b96d426e81e39e79, waar ik kan zien wat je gewijzigd heb, verder kan ik via https://github.com/hani87/interface/network , precies zien wat je wanneer hebt gedaan. de readme.md bij mijn account is ongewijzigd.


@Snugug could we also update the changelog?


This would be a bit cleaner if it was instead:

```
if (!this.element.contains(event.target)) {
  this.hide();
}
```

No **return** statements needed.


Also, I might be wrong, but I think users would probably expect us to
include alpha instead of gamma in cov.scaled when it's used by predict,
right?

On Wednesday, July 29, 2015, bgoodri <notifications@github.com> wrote:

> Maybe the best thing would be to make covmat in stanreg be cov.unscaled?
> The only downside I see is that if someone does vcov() they will get the
> variance-covariance matrix for the unconstrained parameters rather than the
> parameters of interest.
>
> On Wed, Jul 29, 2015 at 3:23 PM, Jonah Gabry <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
> wrote:
>
> > Yeah. Not a big deal, but just wanted to make sure we were on the same
> > page.
> >
> > On Wednesday, July 29, 2015, bgoodri <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> >
> > > I see. We may have to return cov.scaled from stanreg or take the upper
> > left
> > > block of covmat.
> > >
> > > On Wed, Jul 29, 2015 at 3:10 PM, Jonah Gabry <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
> > > wrote:
> > >
> > > > Yes but the output from stan_glm is the same as the output from
> stanreg
> > > > except maybe with x,y, and/or model removed. I think cov.scaled is
> > > included
> > > > in the list returned by stan_glm.fit, but that gets fed into stanreg
> > > before
> > > > being returned by stan_glm.
> > > >
> > > > On Wednesday, July 29, 2015, bgoodri <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > >
> > > > > Isn't the input to posterior_predict the output from stan_glm? In
> > that
> > > > > case, cov.scaled is an element of that but not of the stanfit
> > element.
> > > > >
> > > > > On Wed, Jul 29, 2015 at 2:38 PM, Jonah Gabry <
> > notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>
> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>');>>
> > > > > wrote:
> > > > >
> > > > > > Oops, sorry I meant cov.scaled not cov.unscaled. What I was
> trying
> > to
> > > > say
> > > > > > was that if stanreg doesn't return cov.scaled then we can't
> > recreate
> > > L
> > > > > > inside posterior_predict since the input to posterior predict is
> > the
> > > > > output
> > > > > > from stanreg.
> > > > > >
> > > > > > On Wed, Jul 29, 2015 at 1:56 PM, bgoodri <
> notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>
> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>');>> wrote:
> > > > > >
> > > > > > > I am not seeing where cov.unscaled is used. We have an element
> > > called
> > > > > > > cov.scaled as part of the list and there is also covmat from
> > > > stanreg().
> > > > > > For
> > > > > > > posterior_predict, I guess you need to copy that part of
> > stanreg()
> > > or
> > > > > > else
> > > > > > > we need to return stanmat also.
> > > > > > >
> > > > > > > On Wed, Jul 29, 2015 at 11:44 AM, Jonah Gabry <
> > > > > notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>
> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>');>>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > @bgoodri <https://github.com/bgoodri> If we take stanfit =
> > > > > > > stanfit$stanfit
> > > > > > > > for non-mcmc models then we will lose things like
> cov.unscaled,
> > > > > right?
> > > > > > If
> > > > > > > > we're going to have posterior_predict work for non-mcmc then
> > > won't
> > > > we
> > > > > > > > need to recreate L?
> > > > > > > >
> > > > > > > > —
> > > > > > > > Reply to this email directly or view it on GitHub
> > > > > > > > <
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12423867
> > > > > > > >
> > > > > > > > .
> > > > > > > >
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly or view it on GitHub
> > > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12427070
> > > > > > >
> > > > > > > .
> > > > > > >
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly or view it on GitHub
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428067
> > > > > >
> > > > > > .
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly or view it on GitHub
> > > > > <
> > > >
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428248
> > > > >
> > > > > .
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > >
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428781
> > > >
> > > > .
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428967
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12429067
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12429690>
> .
>


90946736_SHRgt1_4567 (mjwitte) - Win64-Windows-7-VisualStudio-12: OK (1776 of 1779 tests passed)

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


おぉ、これ大事！サンクス！
コンテンツできていったら残りのリンクにも全部いれましょう。
今のところここで大丈夫だと思います。


remove space.


Applies to #339


this was because they've broken something in version 2.1.7, let's stick to version 2.1.6, see my commit that fixes it


Should be gradInput?


You are correct.


Btw, this should be in the coding guidelines, but you wanna leave spaces between operators: `a == b`


You are correct, again.


Should be gradWeights


Waiting for the day when Github rebrands itself as G**hub.


@alex-deaconu I was wondering, is the timeline parameter needed here? cheers


There is a typo : `version for API and core don't match`.


I think they're sufficient, but either way, I don't think these tests really had much bearing on it. It might be worth adding some tests for the control characters matched by the replacement function, but I honestly don't think it matters much. `.decode(...., errors="replace")` should take care of anything it misses.


`4. Floats are serialized with the horrible writeF1000 hack instead of IEEE 754.`


It wasn't specified, so I apologize about that, but can we make notes optional?


step 1/4: make sure the `i18n` module is included


step 2/4: identify a string that needs to be replaced


step 3/4: move the identified string to the proper location in the `en.json` file


Well, given that you read it to have the exact opposite meaning of what it has, I suppose I should add a comment, yeah.


I suggest to add a constructor to `EncodingHashBean(CodecSpec, DigestSpec)` that calls `EncodingHashBean(CodecSpec, DigestSpec, bollean)` using `false` in the last argument.


@sizzlemctwizzle
Once yer done twiddling this should be one folder level down in scripts and referenced from there... unless it can't be.


@mattrobenolt Watch out! You must respect the license. See #3508


Pass a `mode` to `verify_grad`, so the right optimization will be checked.


This should fix #44


step 4/4: call the `i18n.t()` function and pass in the path to the newly created string from `en.json`


Looks good need to split def's out into dataservices/trafviz


Does that retract the ref too?


@seratolgay did you delete all these lines? There are all kind of translation strings that are not found now. Please be careful when you're editing these files...


It's actually serialized as U16, which has a clearly defined size.  Perhaps U32 would be more appropriate though -- just to be safe.


It also shouldn't be included in the dev environment.
On Jul 29, 2015 3:26 PM, "Marti Martz" <notifications@github.com> wrote:

> @sizzlemctwizzle <https://github.com/sizzlemctwizzle>
> Once yer done twiddling this should be one folder level down in scripts
> and referenced from there... unless it can't be.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/OpenUserJs/OpenUserJS.org/commit/8dda6a5df828c45f57f3a5d9a35626ddc3fe1f45#commitcomment-12430317>
> .
>


O_RDONLY and open wasn't declared (travis). Probably missing some header. (or maybe typo). Anyway, both clang and gcc have some issues with this PR.


In fact shouldn't we basically discard gamma after fitting the model and
use alpha ('Intercept') for everything after?

On Wednesday, July 29, 2015, Jonah Sol Gabry <jgabry@gmail.com> wrote:

> Also, I might be wrong, but I think users would probably expect us to
> include alpha instead of gamma in cov.scaled when it's used by predict,
> right?
>
> On Wednesday, July 29, 2015, bgoodri <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
>
>> Maybe the best thing would be to make covmat in stanreg be cov.unscaled?
>> The only downside I see is that if someone does vcov() they will get the
>> variance-covariance matrix for the unconstrained parameters rather than
>> the
>> parameters of interest.
>>
>> On Wed, Jul 29, 2015 at 3:23 PM, Jonah Gabry <notifications@github.com>
>> wrote:
>>
>> > Yeah. Not a big deal, but just wanted to make sure we were on the same
>> > page.
>> >
>> > On Wednesday, July 29, 2015, bgoodri <notifications@github.com> wrote:
>> >
>> > > I see. We may have to return cov.scaled from stanreg or take the upper
>> > left
>> > > block of covmat.
>> > >
>> > > On Wed, Jul 29, 2015 at 3:10 PM, Jonah Gabry <
>> notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
>> > > wrote:
>> > >
>> > > > Yes but the output from stan_glm is the same as the output from
>> stanreg
>> > > > except maybe with x,y, and/or model removed. I think cov.scaled is
>> > > included
>> > > > in the list returned by stan_glm.fit, but that gets fed into stanreg
>> > > before
>> > > > being returned by stan_glm.
>> > > >
>> > > > On Wednesday, July 29, 2015, bgoodri <notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
>> > > >
>> > > > > Isn't the input to posterior_predict the output from stan_glm? In
>> > that
>> > > > > case, cov.scaled is an element of that but not of the stanfit
>> > element.
>> > > > >
>> > > > > On Wed, Jul 29, 2015 at 2:38 PM, Jonah Gabry <
>> > notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
>> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
>> > > > > wrote:
>> > > > >
>> > > > > > Oops, sorry I meant cov.scaled not cov.unscaled. What I was
>> trying
>> > to
>> > > > say
>> > > > > > was that if stanreg doesn't return cov.scaled then we can't
>> > recreate
>> > > L
>> > > > > > inside posterior_predict since the input to posterior predict is
>> > the
>> > > > > output
>> > > > > > from stanreg.
>> > > > > >
>> > > > > > On Wed, Jul 29, 2015 at 1:56 PM, bgoodri <
>> notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
>> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
>> wrote:
>> > > > > >
>> > > > > > > I am not seeing where cov.unscaled is used. We have an element
>> > > called
>> > > > > > > cov.scaled as part of the list and there is also covmat from
>> > > > stanreg().
>> > > > > > For
>> > > > > > > posterior_predict, I guess you need to copy that part of
>> > stanreg()
>> > > or
>> > > > > > else
>> > > > > > > we need to return stanmat also.
>> > > > > > >
>> > > > > > > On Wed, Jul 29, 2015 at 11:44 AM, Jonah Gabry <
>> > > > > notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
>> > > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
>> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>>
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > > @bgoodri <https://github.com/bgoodri> If we take stanfit =
>> > > > > > > stanfit$stanfit
>> > > > > > > > for non-mcmc models then we will lose things like
>> cov.unscaled,
>> > > > > right?
>> > > > > > If
>> > > > > > > > we're going to have posterior_predict work for non-mcmc then
>> > > won't
>> > > > we
>> > > > > > > > need to recreate L?
>> > > > > > > >
>> > > > > > > > —
>> > > > > > > > Reply to this email directly or view it on GitHub
>> > > > > > > > <
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12423867
>> > > > > > > >
>> > > > > > > > .
>> > > > > > > >
>> > > > > > >
>> > > > > > > —
>> > > > > > > Reply to this email directly or view it on GitHub
>> > > > > > > <
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12427070
>> > > > > > >
>> > > > > > > .
>> > > > > > >
>> > > > > >
>> > > > > > —
>> > > > > > Reply to this email directly or view it on GitHub
>> > > > > > <
>> > > > >
>> > > >
>> > >
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428067
>> > > > > >
>> > > > > > .
>> > > > > >
>> > > > >
>> > > > > —
>> > > > > Reply to this email directly or view it on GitHub
>> > > > > <
>> > > >
>> > >
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428248
>> > > > >
>> > > > > .
>> > > > >
>> > > >
>> > > > —
>> > > > Reply to this email directly or view it on GitHub
>> > > > <
>> > >
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428781
>> > > >
>> > > > .
>> > > >
>> > >
>> > > —
>> > > Reply to this email directly or view it on GitHub
>> > > <
>> >
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12428967
>> > >
>> > > .
>> > >
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12429067
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/stan-dev/rstanarm/commit/4dbf0063656745825898950d710bebd7bc5f7cad#commitcomment-12429690>
>> .
>>
>


Давай сделаем без возврата boolean, а то так не рекомендуют писать. Может что-то вроде такого:
public void create(Flower flower) {
    try {
        flowersDao.create(flower);
    }
    catch(FlowerNotCreatedException e)
    {
        // log exception with log4j
    }
}


This is a good catch, but not the right way to fix it.  We'll just forget to update this again.

See here for how to get the right info:
https://github.com/wdschei/api-checker/blob/master/core/src/main/scala/com/rackspace/com/papi/components/checker/wadl/WADLCheckerBuilder.scala#L60

Noe that you'll only get a valid non/null version number *after* you package things into a jar -- I haven't quite figured out how to test.

Please move this bit to another pull request.


Use `sortBoxVerticies` (`util/numeric.h`).


@rodrigopavezi nope. Good catch, will remove. Thanks!


Good catch fix the issue above and I'll accept.


Ich persönlich würde, da die drei Fälle hier sich gegenseitig ausschließen (Die Weide kann nicht voll und leer gleichzeitig sein), das Ganze als IF...ELSE IF...ELSE schreiben, um dieser Tatsache im Code auch Rechnung zu tragen. Dann sieht Scrutinizer das vielleicht nicht mehr als Wiederholung an...


testing a comment


I would raise `SkipTest` instead


Can you please remove this line (`versionnumber`), just to preserve the consistency, and use this `url` instead:
```
url "http://rephial.org/downloads/#{version.to_f}/Angband-#{version}-osx.dmg"
```


mne.utils?


hey that was easy


Curious what's the impact of not calling close() here? Will Mcrouter leave this connection open, even if its client has closed the connection?


@liggitt how much work is it to upstream the identity->user mapping and all the openshift identity providers?


I agree, will change that.


ah yes


Add a keyword for the class that is expected to be in the final graph, and a check that this is the case.
Also check that the abstract op is not in the graph anymore.


> It also shouldn't be included in the dev environment.

`{{#isDev}}` and `{{#isDbg}}` exist from [OpenUserJs/OpenUserJS.org@`8f23115`](https://github.com/OpenUserJs/OpenUserJS.org/blob/8f231154f5a4c2ecf4aa3a6d21a4aba10e30eb80/views/includes/header.html#L5) in https://github.com/OpenUserJs/OpenUserJS.org/commit/8f231154f5a4c2ecf4aa3a6d21a4aba10e30eb80 :)


TeamCity LabkeyTrunk :: CDS postgres 9.4 [Build 225](https://teamcity.labkey.org/viewLog.html?buildId=263428&buildTypeId=LabkeyTrunk_CdsPostgres93) outcome was **FAILURE**
Summary: Snapshot dependency failed: LabkeyTrunk :: build Build time: 00:00:00


OK.


Reverting Nathan's change gets us close to 1000Hz putting the resonance at 1000Hz.  Removing the multiplication by 1.16 gets us pretty much spot on -- as the first of the next 3 screenshots shows.  **However** look at what happens when the frequency is set to 8000Hz.  This explains why going to 10K will blow the filter.  Then note the change to resonance in the 3rd screenshot -- it affects the frequency.


I understand previously we weren't storing any metadata for the bit vector, but I think this addition could be a little clearer by at least commenting that these indexes are based on the order of the calls in getMetadataBuilder(). It would probably be worth it to add a comment up on the method itself that these additions are order sensitive.


thanks @zgramana


Yeah, it's handled internally. I have also kept the `max` check but I'm not sure why it's needed. It has always been there so...


@Aran85 not sure if this check is correct. It works for your specific use case, but the same can happen if we open a section and flush without providing more data. I think that the m_pretty check needs to go to where the sections are closed.


RadianceRefactor (macumber) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2182 of 2215 tests passed)

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


ok


@myoldmopar Could you comment on this? I think this is going to work but I would appreciate someone with some experience managing environment level variables to make sure I get everything setup/reset correct. Brent was saying that there would need to be a RunPeriod object to for it to march through the year. I have that in the file but right now I'm only seeing the sizing periods.

For now, I'm going to put this on hold and work on the rest of the model until I can collaborate with you on this.


Hey Mark,

Looks like maybe you forgot to paste the line that I should comment out.
Did you perhaps mean the following line:

[tableView deleteRowsAtIndexPaths:@[indexPath] withRowAnimation:
UITableViewRowAnimationAutomatic];}

Since [realm deleteObject:self.array[indexPath.row]]; is already telling
the cell to delete itself?

On Wed, Jul 29, 2015 at 1:06 PM, dothework <notifications@github.com> wrote:

> @Diego-F-Aguirre <https://github.com/Diego-F-Aguirre> Comment out this
> line and it works.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Diego-F-Aguirre/BlocNotes/commit/74275a2cffdbdc2dea984d505dfc5a8ba305f482#commitcomment-12425885>
> .
>

--
:::::::::::::::::::::::::
Diego F. Aguirre
973-885-0724

http://www.linkedin.com/in/diegoaguirre3d
http://diegoa3d.com/


square is working and pop up parameters as well


I am happy that it works well :-)


We should probably at least leave a comment as to why this was here originally and why it was removed and/or may re-enabled at some point. That or just remove it.


@rtibbles FYI. Causes error on the `/learn/` page.


Ah, I see, I didn't realise it was dual purpose, thanks for clearing that up.

My understanding was that "OT" mode was both embedded etcd, and single-server, but I now see that was wrong. I did eventually realise the meaning when looking at a config.properties file that it was pointing to an etcd server, which led me to try & find the root definition of that configuration string, which I guessed was this.

I agree, changing this doesn't make sense, but I might think about how to document it. Is it possible to add comments in a config.properties file?


In terms of "consistency" with the original library, I'm personally of the opinion that direct ports that try to maximize consistency between two very different languages leads to sacrifices that may not be worth it.  I understand the intention of trying to port the code directly, but when dealing with a language that has no runtime like C++, the decision made in the higher-level language may lead to fragile code in the C++ source base.

Good point that this isn't really a "copy" though as it is changing the origin.  I should probably better familiarize myself with hocon or the original implementation to be better qualified to comment on naming conventions or intentions of member functions.

Regardless, though, whatever we decide to implement needs to use smart pointers instead of raw pointers.  As you've discovered in the corresponding unit tests, C++ makes it trivial to leak memory and the diligent use of smart pointers helps remedy that.


Same as above in regards to these ordinals and their relationship to getMetadataBuilder().


<!doctype html>

      <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
      <meta http-equiv="content-language" content="pt-br" />
      <title>AngularJS: Single Page com ngView e ngRoute</title>
      <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css" />

   <!doctype html>

      <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
      <meta http-equiv="content-language" content="pt-br" />
      <title>AngularJS: Single Page com ngView e ngRoute</title>
      <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css" />

Home

Sobre

Contato

Página Home!

Página Informações!

Página Contato!


Thanks!


Spelling, you wanker. It's "consultation."


Feels like Reddit is leaking all over the net lately.


I mean, with a curly quote!

--
http://rrt.sc3d.org
On Jul 29, 2015 8:01 PM, "Markus Koller" <notifications@github.com> wrote:

> What do you mean, just "Today's" without " activities" at the end?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/projecthamster/shell-extension/commit/e04c4210e9ad6f1a5336ef77e7f307768f5e4129#commitcomment-12428572>
> .
>


Could you change this to `get(this, 'defaultSeparator')`?


please remove me from this distro list

     On Wednesday, July 29, 2015 4:06 PM, alifhamzah <notifications@github.com> wrote:

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


 Oli Motor Terbaik - Total Hi-Perf

Total should be proud to call Oli Motor Terbaik - Total Hi-Perf products as the best motorcycle oil of a little brand that could produce them. Brand of a multinational company based in Paris, France is already exist in the field of oil and gas since 1924. A long life that allows the company is able to develop the technology perpelumasan through experience.

At least, we can belanja di elevenia gratis voucher 1 juta measure the total reputation in the development of oil technology through a series of racing activities that they do. Formula 1, WRC, Dakar to Le Mans endurance race is not the usual race. But in the event-the event Oli Motor Terbaik - Total Hi-Perf that, where performance and durability jasa seo so challenged, Total was able to prove the reputation of its technological advances. Sederat the trophy was already achieved.

Oli Mobil Terbaik di Indonesia – Total Quartz ~ Pasung Musuh Mesin dengan Total Quartz 9000, Tahukah Anda bahwa terdapat tiga musuh besar bagi mesin mobil sekalipun kita secara berkala sudah mengganti oli? Ya, ketiga musuh yang akan selalu menghantui mesin adalah kehancuran akibat friksi, korosi, dan lemahnya proteksi.

Dan, apa yang jaket branded harus kita lakukan untuk  Oli Mobil Terbaik di Indonesia - Total Quartz mencegah terjadinya kerusakan dini pada mesin mobil? Cukupkah dengan lebih memperpendek jarak pergantian oli? Perlukah kita HRCentro Komunitas Sumber Daya Manusia Indonesia memangkas waktu penggunaan kendaraan, menghindari kemacetan, atau lebih sering melakukan perawatan berat?

Sepintas pertanyaan-pertanyaan pasang penangkal petir tersebut seperti bisa dijawaban dengan, “ya.” Dan, memang tak mudah menentukan jawaban “tidak” ketika oli yang kita anggap terbaik tetap berpotensi menghidupkan kursus online bersertifikat di indonesia musuh di dalam mesin. Hari ini, di saat persaingan bisnis oli semakin sengit, menentukan produk oli mesin mobil terbaik memang menjadi masalah tersendiri.

Tapi sejatinya problem itu hanya akan menjadi masalah bagi mereka yang tidak mengetahui adanya serial oli Total Quartz 9000. Sementara Beli Baju Online, Produk Dari Clothing Premium Indonesia Hanya di Moruka.com bagi mereka yang telah merasakan manfaat Total Quartz 9000 seolah selalu berkendara dengan mobil baru.

Ada banyak sekali keuntungan dan kelebihan yang anda maklon kosmetik bisa peroleh di salah satu situs jual beli online terbesar di Indonesia ini, diantaranya anda akan memperoleh berbagai Synthesis Development - Indonesia Developer Property macam diskon yang sangat besar pada semua barang yang dijual belikan dan mendapatkan promo besar-besaran yang tidak henti-hentinya diberikan oleh Elevenia. Salah satu keuntungan lainnya adalah Belanja online di elevenia semakin seru dengan gratis voucher 1 juta.


Can't wait to see it released :D I want to use webjars :D


RadianceRefactor (macumber) - 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)


Hi. Pretty sure you have to "unfollow" the distro from github

Date: Wed, 29 Jul 2015 13:44:40 -0700
From: notifications@github.com
To: freecodecamp@noreply.github.com
Subject: Re: [freecodecamp] change mobile to hikes (4c8a8a4)

please remove me from this distro list

     On Wednesday, July 29, 2015 4:06 PM, alifhamzah <notifications@github.com> wrote:

 User—

Reply to this email directly or view it on GitHub.

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


Have you gotten a success response to the back_account.verify from Stripe?  Because the are asking for the amounts in a different format in their documentation...


Yes, you are right 'cause ModuleID.fromString() is already contains an internal check for the MODULE_VERSION_SEPARATOR = "."


@alex-deaconu I have been noticed that we might be doing wrong if our E2E tests. Shouldn't this be isDisplayed instead of isPresent? In this way if startTime is on the DOM but hidden it will pass. cheers


这是第一版的翻译对照，有一位兄弟已经指出了你上面的一些问题，然后我完善并且提出了第二版，所以只修改了上面提出部分的意见，感谢。@polarlights


Yes. Exactly.
I thought I made my comment on the exact line of code we are referring to. GitHub allows for that. It didn't work?

Sent from Outlook

On Wed, Jul 29, 2015 at 1:38 PM -0700, "Diego-F-Aguirre" <notifications@github.com> wrote:

Hey Mark,

Looks like maybe you forgot to paste the line that I should comment out.

Did you perhaps mean the following line:

[tableView deleteRowsAtIndexPaths:@[indexPath] withRowAnimation:

UITableViewRowAnimationAutomatic];}

Since [realm deleteObject:self.array[indexPath.row]]; is already telling

the cell to delete itself?

On Wed, Jul 29, 2015 at 1:06 PM, dothework <notifications@github.com> wrote:

> @Diego-F-Aguirre <https://github.com/Diego-F-Aguirre> Comment out this

> line and it works.

>

> —

> Reply to this email directly or view it on GitHub

> <https://github.com/Diego-F-Aguirre/BlocNotes/commit/74275a2cffdbdc2dea984d505dfc5a8ba305f482#commitcomment-12425885>

> .

>

--

:::::::::::::::::::::::::

Diego F. Aguirre

973-885-0724

http://www.linkedin.com/in/diegoaguirre3d

http://diegoa3d.com/

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


Got the same error in chef 12.4.1

```
[2015-07-29T20:39:43+00:00] INFO: Running report handlers
[2015-07-29T20:39:44+00:00] ERROR: Report handler GraphiteReporting raised #<NoMethodError: undefined method `[]' for #<Chef::RunContext:0x00000004d000f8>>
[2015-07-29T20:39:44+00:00] ERROR: /var/chef/cache/chef-handler-graphite.rb:60:in `report'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:226:in `run_report_unsafe'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:214:in `run_report_safely'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:93:in `block in run_report_handlers'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:92:in `each'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:92:in `run_report_handlers'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/handler.rb:103:in `block in <class:Handler>'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/client.rb:416:in `call'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/client.rb:416:in `block in run_completed_successfully'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/client.rb:415:in `each'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/client.rb:415:in `run_completed_successfully'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/client.rb:284:in `run'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:270:in `block in fork_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:258:in `fork'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:258:in `fork_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:224:in `block in run_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/local_mode.rb:39:in `with_server_connectivity'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:212:in `run_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application/client.rb:402:in `block in interval_run_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application/client.rb:392:in `loop'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application/client.rb:392:in `interval_run_chef_client'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application/client.rb:382:in `run_application'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/lib/chef/application.rb:60:in `run'
[2015-07-29T20:39:44+00:00] ERROR: /opt/chef/embedded/apps/chef/bin/chef-client:26:in `<top (required)>'
[2015-07-29T20:39:44+00:00] ERROR: /usr/bin/chef-client:55:in `load'
[2015-07-29T20:39:44+00:00] ERROR: /usr/bin/chef-client:55:in `<main>'

```


Can't you just make the names all lowercase?


dunno, it's been too long since i commited this. But it's all very basic math.


Justin and I paired on this together


No problem. Done & force pushed


why in gods name are you hitting xem for each show. this is not how its designed and a good way to get yourself banned. you hit the api to see what shows have mappings. cache that, use that info to dictate if you have a show in xem or not. not query each show a user has. most shows arent in xem. thus if a user has 1000 shows in SR, theres no reason you should be hitting xem 1000 times. please address this before banning starts taking place.


We're far from XHTML compliance but the `async` attribute shouldn't be minimized... still a good practice to keep things XHTML compliant for parsing. :)

See also:
* http://www.w3schools.com/tags/att_script_async.asp


Yes, you need to unfollow the repository on github.


@alex-deaconu I think it will fail on the jshint as it is not single quote. Also, what do you think about changing this constant string to a constant variable? cheers


Let's fix this before the next release so we don't immediately have to break a published API.


ok, i get it


It would be nice if we create a stub secrets.json with placeholder fake username and password.
The file secrets.json is already mentioned in .gitignore, so it won't be an issue when users would fill it in with their own credentials.


change color


I think we should add here that the Examiner will look for the configuration in the usual places by default.


Maybe, but I think a "configuration" document in the `docs/` directory might be better?


Given the code below that would be in the current working directory.


:fireworks: indeed!


This is new behavior


msm8226-common ?


I've added a makefile for the example code, so you should be able to follow the instructions in the readme to compile the example.


chang color for icon


Yes, a little typo because I initialy use Alberto "Blobs upgrade commit"
Sorry


@pbrisbin do you plan to update the brew formulae so 0.2.x can be installed through brew?


list<Agent*> agents □□□□□□□□□
□: Agent*

getAgent :
want to return a element of the "agents"

In this version "getAgent" returns "iterator" of "agents".

"getNode" too.


OK... but refactor the time setting beneath as `"{}:{}".format(hour, minute)`


Sorry, fixed now!


you don't need to store this anywhere else, drop self. Also split it directly here:
```python
hour, minute = self.timer.get_configuration()
```


Updating data service with signature validation


Pulled in this optimization which ignores detected collisions with no area. This was integrated from @dsmorse fork.


The comment above should go too


THX @MorrisJobke


This was my initial change with causes any stale instance of gridster to go dormant. I left this in just in cause the discarded instance somehow hangs around.


I'm bummed by Github's decision to start removing words that they don't agree with. A vocal minority is unfortunately steering the boat around here, and the only recourse is going to be to abandon ship.


97902934_ZoneMixing (macumber) - Win64-Windows-7-VisualStudio-12: OK (2205 of 2235 tests passed)

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


TeamCity FubarDev.AfA :: Test-Build für Pull-Requests [Build 3](https://build.fubar-dev.com/viewLog.html?buildId=48&buildTypeId=FubarDevAfA_TestBuildFRPullRequests&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 10 Build time: 00:00:12


5051_fix_local_win_test (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1261 of 1261 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-69.96%25-green.svg)


No, I refactored it a bit and the output slightly changed, but it's still generated.
I checked against the original list and there has been some additions and some duplicates removal.


I can test anything you give me or give you access to the beta universe I have setup.
let me know


Please do abandon ship. Get out.


This change is pulled in verbatim from @dsmorse branch patch which is specifically for cleaning up gridster destroy. This removes stray/stashed data left around and cleans up the DOM.


Please break down pieces of `classify()` into smaller helper functions for readability.


Also added dunst


I get an error on this import - where can the NatPredicates module be found?


This was pulled from @dsmorse branch patch for cleaning up upon destroy.


typo: "To do a thing"


I wonder why you started using this "get-in"?


If newIndex ends up as 0, won't this return false?


top_level is a string. Please initialize it as such.


This is great and generally useful. Let's add it to autopkg's built-in processors. Can you make a PR?


It's confusing that this variable has the same name as `top_level` above. Probably want to rename one of them


`sub_level` is also a string, not a boolean.


I concur with some people here: you should probably go over to gitlab or something and replace this repository with a message "We moved to GitLab, because github is shit (or an explanation)"

Don't encourage them by complying with their request when it's so easy to just leave them. You staying here brings your users here, making them more popular.


This was my initial change with causes any stale instance of gridster to go dormant. I left this in just in cause the discarded instance somehow hangs around, since it stopped extraneous event callbacks resulting in state corruption in gridster and our app.


this will need to be inside the ns macro (without the quote) adjacent to the import.  If this worked, it's probably because the namespace was already loaded.


Good job, but don't merge yet. We will do that tomorrow when we fix the issue of having previous commits exist in your pull request