TeamCity LabkeyRelease15.3 :: Git postgres 9.4 [Build 19](https://teamcity.labkey.org/viewLog.html?buildId=283797&buildTypeId=LabkeyRelease153_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 34 (15 new), passed: 250 Build time: 01:24:19
### Failed tests
```
org.labkey.test.tests.DataFinderTest.testDatasetExport: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testImmuneSpaceStudySubset: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudySummaryWindow: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudyCards: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testSelection: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testNavigationDoesNotRemoveFinderFilter: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testSelectingEmptyMeasure: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testBackDoesNotRemoveFinderFilter: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStudyCardStudyLinks: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testFinderWebPartAndActionShareFilter: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testDisabledLoadAndSave: <no details avaliable>

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


jesus farid. monster


I don't think you really mean loopEnd-1 because that means 1 second from loopEnd since loopEnd is in seconds.


Are you sure this shouldn't be `Login.prototype.authLogger = AuthLogger.getInstance();`?


Could this be using `G_DEFINE_BOXED_TYPE()`?


This is a benchmark. Don't change its code.


On Mon, Nov 09, 2015 at 06:46:29AM -0800, Piotr Banaszkiewicz wrote:
> @wking `is_active` as a property was inherited from Django's
> `AbstractBaseUser`. It defaults to `True`.
> …
> The actual implementation will be a little bit different: if
> `person.has_unusable_password()` then they should be inactive.

Ah, maybe there's no need for special care with is_active then.  We
can leave this how you have it, and use our (existing?) unusable
password handling [1] to keep non-admins from getting access via
password-resets.

[1]: https://docs.djangoproject.com/en/1.8/topics/auth/default/#django.contrib.auth.views.password_reset


Never lagged for me :P
Tracking updates for a vanilla mob are around 3 (iirc) - sometimes to avoid render derps a lower (more frequent number) used to be required - this may well not be the case now :)


Cache use case again.


If you are happy with the results, I will drop all the JSON/Slurp commented out code.


whitespace


Shouldn't you also delete all the files now in https://github.com/Orckestra/C1-CMS/tree/b258d9414075a135e1de5198c239ac367b202dc2/Website/Composite/lib from sourcecontrol?


1° commit


Done:    e0c4307


I don't understand why command.concept.retired wasn't working.


Now the error is this:

```
Uncaught TypeError: result.forEach is not a function
```

Also you can now go to polls that don't exist. Which is also a major problem


I don't follow.  Pass a message where?  Can you be more specific?


The patternfly modal doesn't seem to be any different than the bootstrap one.  It might be better if we keep it associated with bootstrap and even contribute it to an ember-bootstrap project.  We could then build ember-patternfly on top of it without being directly coupled.

I think we should probably implement an open-if the same way the old one did so we're encapsulating the bootstrap/jquery related stuff in the component and not polluting our application.


capitalization of U and V


Wasn't there an issue about JSON ?


Почнму коммиттите не каждый из-под своего аккаунта?!


no need to change, but just for future reference we have a utility to run the same test on different settings
https://github.com/dimagi/commcare-hq/blob/master/corehq/util/test_utils.py#L160
https://github.com/dimagi/commcare-hq/blob/b3-tf/corehq/form_processor/test_utils.py#L61


fixed


fixed...


`de la longitud` instead of `del largo`


+1 for not pulling before start working :D


`vector` instead of `arreglo`
`fragmentos` instead of `pedazos`


nit: this could be an `any` call and that way it's a boolean


make both parameters final


I changed the default tracking updates of the mobs but mixed up the tar minion and thrown tar minion. It's not really necessary for mobs to send motion updates every tick, especially for slow ones


I think the 'issue' was just emails and comments in #59  I find no issue to 'close out' now that JSON is removed.

Ok, moving fwd....


LGTM.


Psssst! :tada:


final


This fixes non-team color skins on servers with ServerPackages access protection via GET.


datapath/vport-netdev.c previously included this directly. Looks like that #include is removed now, so this patch can be dropped.


Tive que alterar pois se tivesse dois pagamentos de um usuário utilizando o mesmo cartão violaria a chave primária!


Done ;)


Hey Tim. Class functions such as __construct() need to go inside the class body. e.g. class Image { /*in here*/ }

Also, try not to commit code with linting warnings. If you are using phpstorm they should show up as yellow lines and give you a warning when you commit.


optimize imports


Tnx


Spark


Could you please explain what is going on in this method (specifically, at this line)? The code is quite not self-explanatory. :)


Spark here and in the next few lines


@JayOfferdahl I left the individual div wrappers around those fields in the registration.html. Basically like I said previously it allows for easier manipulation of the fields individually. As it sits now, they are styled such that the labels and inputs are all the same size, it's just that some of the rows require some special attention. If you want to check out the styling pull that branch down and runserver. Let me know if this is good to merge.


noob


Кажется, что все эти свойства не используются снаружи, поэтому имеет смысл сделать их приватными


You need to add an argument to the argument parser e.g. `parser.add_argument('-o', '--local', type=bool, required=True, default=False, help='Use the local optimisation method')`


Adds offense antispam for Nar 3rd obj d spawn door.


You are correct. This is valid functionality that is simply not used by the app at this time. Will probably re-add at some point.

My other motivation for this change is that I could not have two constructors with params (String, String, String). We use GSON to encode the request and while it would support float/int params that would require some updates how the request is built in the SDK and the app so I punted those changes until a later time.

![image](https://cloud.githubusercontent.com/assets/464123/11041427/c4a4d046-86df-11e5-9f71-e3086947ea00.png)


cast is redundant?


final


Use `if local_optimization is True:` - easier to understand!


This doesn't feel quite right to me. We've started from a situation where all accesses to the filesystem were cached (for us by OIIO), and we were blissfully unaware of the #### substitution mechanism. And we've ended up with potentially a huge number of uncached filesystem accesses (for every channel of every tile), and explicit hardcoding of an assumption that the #### substitution mechanism is the only means by which the filename will vary from frame to frame.

I haven't been through the logic in detail, but I presume there is some reason we can't instead create a temporary context for the previous frame and then just pull on the fileNamePlug() to get a new candidate for hold mode? Is it because we don't know where to bottom out of the loop in the case of repeatedly not finding anything? To me this approach feels preferable if we can make it work - it would keep all the caching within OIIO and also make us compatible with other methods of varying filename with time (expressions etc).


Проверить принадлежность объекта к классу (как NickCommand у тебя) можно с помощью оператора instanceof.


you are overwriting any previous data here, is that what you want ? If yes, you should tell it on doc


Thank you, colundrum, for the fix. Indeed, the quotes were wrong.


#1 #2


I handle upstream patches using quilt. Can you test if removing line 95:
```using namespace std;//as suggested by Brian Ripley``` would resolve this issue?


Fixed in https://github.com/phoboslab/Ejecta/commit/3d0567b5bafa65807d4438d723c2ffad44b21d87. Thanks!


Must remove this `String dataset` parameter


Move these comments into the docstring (the triple quotes at the beginning of your procedure).


s/log4j/slf4j ?


Yes, I want this. I will make it clear in the docs.


1640-AddHVACPart1-tertiaryLoops (kbenne) - i386-Windows-7-VisualStudio-12: Build Failed

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


У последующих тестов последние три строки тоже по сути одно и тоже. Можно выделить функцию, в которую будут передаваться два дерева, и сравнивать внутри нее)


Blijkbaar heeft de Facebook API een oudere play-services nodig. Volgende commit zet dit terug op 7.8.


Shouldn't this change be squashed on previous commit?


yo


For now, accre-gridftp doesn't do the deps right, so we may want to hold off (it requires packages that aren't either in the base repository or EPEL)


I'm a little wary of this one. I don't think we have code sensitive to it at the moment, but it seems a reasonable assumption that CompoundNumericPlugValueWidget uses NumericPlugValueWidgets internally, and even that we might want to add features based on that assumption in the future.


I didn't add pylarion since it's current internal.


Should be GAFFERIMAGE_


This has a side effect, since it invokes `get_or_create`, so it should be named to reflect that (or split into two functions, each doing one thing only).

I was confused by this when reading `test_deleting_all_group_permissions` on line 88 - it invokes this, but does not use the returned values.


This is still being worked out in jwilder/nginx-proxy#254. I'm hesitant to add documentation until we have something that's actually settled and generally usable.

I've come to the conclusion that it's not possible to support this feature properly the way that @jwilder would like without having a custom generator tool that extends `docker-gen`. That work is being tracked here: https://github.com/jwilder/docker-gen/issues/131

I've done a bit of work to break `docker-gen` out into a library to make it possible to create a custom `nginx-proxy` binary, but I haven't had time to get it fully working yet.


Shouldn't denormalizer be in todos-lib?


Can we forward declare this instead?


Тут пожалуй хотелось бы видеть код, который смог бы вычитать файл с markdown-разметкой, и получить html-файл


And this?


I hadn't thought of that at all actually. But yeah, how do we know when to stop trying to find a previous frame?


i would say "an SVD" throughout, but i'll leave this up to you...


My thought was to put short version in Readme.md to highlight the deploy process some and have a more detail version in the dedicated deploy doc.

I am open to doing it either way.


@bibryam Could you add "-h \`hostname\`". I faced the following problem. `32e9a5382d1d` is hostame of docker container.
```
18:21:16,940 ERROR [org.hornetq.core.client] (pool-1-thread-1) HQ214016: Failed to create netty connection: java.net.UnknownHostException: 32e9a5382d1d
```


1 Не называй переменные t,ta,ca - очень неудобно.
2 Два вложенных цикла while с readLine()!=null - довольно странная конструкция. Для чего?!


Esto no es una buena idea (performance wise)
.first() a nivel de la DB jala uno solo (aka LIMIT 1)
.all() jala todos los registros y luego en python saca el primero.


It just occurred to me that a throttle curve is also a new parameter :) but I guess that could be as simple as one parameter like THR_MID which specifies hover throttle for manual mode. The "curve" would implicitly be 2 linear segments with necessarily different slopes unless we allowed for multiple points like heli transmitters do (or perhaps something more sophisticated and requiring fewer parameters).
I agree that it's better to have all such functionality in the autopilot, since that places fewer requirements on the remote control. But it's also a duplication of functionality, and OpenTX supports separate curves for each flight mode...


optimize imports


I need to check a little bit more before upgrading dependencies..
Il 09/nov/2015 17:59, "Andrea Cosentino" <ancosen@gmail.com> ha scritto:

> Done. Sorry for the mistake..
> Il 09/nov/2015 17:48, "Andrea Cosentino" <ancosen@gmail.com> ha scritto:
>
>> I'll revert :-)
>> Il 09/nov/2015 17:45, "Ioannis Canellos" <notifications@github.com> ha
>> scritto:
>>
>>> curator 3.x is for zookeeper 3.5.x which is still alpha.
>>>
>>> even though we don't use zookeeper much these days, I am not sure if we
>>> should update.
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/fabric8io/fabric8/commit/f7f2a469aff6cd2d4ffbcf0ec081906eb1a50466#commitcomment-14281103>
>>> .
>>>
>>


`test_add_nonexistent_perms` could be refactored to use `create_groups_with_permission`.


final


Plerbean


Redundante,


LGTM


Ah, I see that this one at least is currently needed for OpenImageIOReader::ErrorMode. But perhaps if we want the error modes to be considered to be distinct, we shouldn't imply a direct equivalence in the headers? So OpenImageIOReader should be a hidden implementation detail?


This breaks ES3 (https://github.com/Microsoft/TypeScript/pull/5569) :no_good:


Yes, I thought of more comprehensive ways of doing it, but this simple and effective enough. Again, these are default base classes and default implementations, that could be overridden in any way.


Perhaps this too should be `errorModePlug()`?


It was not working because the getRetired() method had been removed and yet
the existing isRetired returns a Boolean instead of boolean.

On Mon, Nov 9, 2015 at 8:37 PM, Lluis Josep Martinez <
notifications@github.com> wrote:

> I don't understand why command.concept.retired wasn't working.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openmrs/openmrs-module-legacyui/commit/e74165eb6ba9d1ff3f9ad4f42152f0583d9cf3a6#commitcomment-14282547>
> .
>

--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.


Again, the simplest possible! :smile:


this function is also used to free `theWorkspace->global_tags`, so it would also have to have an associated free func


Достаточно большой метод. Тоже хочется разбить. Например то, что обрабатывается в ветке if - как один метод, что в else - как другой метод


only downside is the chance of one of these getting out of sync

```
<?php include 'deploy.php';?>
```


Do you have another suggestion for allowing per-element presets via a dropdown, while still keeping the desirable "all on the same row" and gang-able features?


Did you want an extra blank line here?


I'd rather ref/unref the whole TMSourceFile, as anyway here you'll share the actual tag array


I used the "appendix" model.  Please feel free to update this documentation.


TeamCity libpalaso :: palaso-win32-master Continuous [Build 3.0.574.4a69b295f3e32c134ae35638aec57742058b5d74](http://build.palaso.org/viewLog.html?buildId=65831&buildTypeId=bt223) outcome was **SUCCESS**
Summary: Tests passed: 3308, ignored: 125 Build time: 00:07:59


Why so self obsessed? ;)


Fix casing (DateAdd)


do we really need to specify *all* return type transfers?


Oops


The point is to make sure Extension Manager knows jcl-over-slf4j and log4j-over-slf4j "implements" commons-logging and log4j so that they are not installed as dependencies. There is already a slf4j Maven descriptor since slf4j is built with Maven. See the link for more details.


The use of a V2fPlug here seems awkward to me - a range and a two dimensional vector are two quite distinct things, and having start and end be called x and y seems confusing. I'm wondering if we've done this elsewhere already but I can't find a spot where we have. In ScriptNode we create a parent ValuePlug and add a start and end child to it explicitly, for a similar purpose to this one.

I'm also curious about the use of float values here rather than integers - is there any particular reason for that?


I believe `strings.Repeat` will panic here if `len(left) > colWidth`. Can you use the wrap-to-next-line strategy used for options below? This means that very long positionals would be printed as
```
  short                first help message
  verylongpositionalargument
                           second help message
```


@norcross I think following these guidelines would potentially be a good approach: https://make.wordpress.org/themes/2015/02/10/custom-css-boxes-in-themes/


Sweet :) So much better!!! Cheers!


Oje, hier habt ihr einen Merge-Konflikt nicht richtig aufgelöst. Daher nicht vergessen, vor eigenen Änderungen immer folgendes machen:
```
git pull --rebase origin master
```


John, since there was a lot of discussion on this PR and as it is not squashed yet, I recommend that you don't review the individual commits, but just the aggregate changes. Any changes to Assembly have been reverted already.


If it's usually called Init, then leave it as Init.


Just realised my comments below apply to this one too.


why?


I would rather change this in the guidance opticflow module as well...


no harm to check it though... so I'm adding them.


I'm not sure what this is testing.

Is `get_perm` the only thing that we test? Maybe some comments to explain which part is setup and which part is testing would help.


Keine Ahnung, wo diese `config/ol.json` Datei herkommt, aber die funktioniert nicht. Ich sende euch einen Pull Request, der sie wieder behebt. Euer code sieht richtig aus, nur funktioniert mit dieser kaputten Konfigurationsdatei `npm install` und in Folge `npm start` nicht richtig.


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

```


Any reason this can't be achieved by a direct connection? We do propagate the emission of plugSetSignal() down output connections, so I would expect that to be sufficient to trigger the appropriate action in OpenImageIOReader.


@minimenchmuncher that is really strange for your battery to be like this.

Anyhow, let's close this pull-request and leave `upower` as it was before ;)


Sure ? Since this commit after Vim starts up hitting q closes Vim after a one second timeout, before it was instant. Can you verify that when adding nnoremap qq q to vimrc?


@mLuby  k lets use `id`


how the proxy are supposed to handle this?  it's tremendously important that all handlers get disconnected when the plugin is unloaded, otherwise… boom :)


Yep, these are very simple examples. But anything can be considered a location and checked for validity. The executable (without extensions) was the next thing that I prototyped. Check 5d71016b5863ad73cfb95b3bc3de78072a6d7f7e.

Again, the whole point of this proposal is to split the "possible test location" version "test inspection (including type)" in two very distinct phases. We may have overlapping results from multiple location discovery classes, that will then be filtered out by the test inspection mechanism on the test loader that support specific test types.

Does it make sense?


La idea es sólamente agregar una plantilla nueva que puedas usar.
La funcionalidad de pull to refesh no se puede agregar así, sino como una opción para el desarrollador. Hay que hacerlo configurable.


Let's not call them BrktHSM and BrktAPI. Let's call combine them into one entity and call them BracketBackend or BracketServices or something like that


One comment


These two lines appear multiple times. Maybe refactor them in a method? This would also improve the readability of `test_retrieving_permissions`.


Используй \r\n, а еще лучше Environment.NewLine


> No, it can't. Here is a working example: https://github.com/matklad/scope/blob/master/src/foo.rs

Oh, dear lord, that complicates things.


Yep, the giant collective brain (the web) told me about this, and it turns out to work fine for these use cases. Better (and more efficient) than `open`ing the files. But, it could be argued that it's not that Pythonic (could be done in shell with `mknod` too).


@tiborvass I am using df logic only if dm.fs is not specified. If user has specified an fs to be used, that fs should be used without question. If user has not specified an fs, then we do all this magic of df and try to come up with a default fs.


is this necessary?


No, I don't have any questions from this chapter :)


Instead of backup/restore, why not implement the following process: (simplified from a users PoV)
* install Signal on new device
* detects if number is already setup
* if yes, ask the user if he wants to migrate his identity
* old device will prompt user to confirm identity migration (showing some shared secrets or other means of preventing mitm)
* done: key is copied over or a new "version" of the public key is installed on the servers with a proof-of-migration (new key signed by old key)


Yeah, I noticed ScriptNode was doing that. It seemed nice because they're called start and end, but I've also found that annoying in the past because I conceptually think of it as a single plug (the frame range) but I always have to access them individually (`script->frameStartPlug()->getValue()` and `script->frameEndPlug()->getValue()`) when I'd rather access them how I think of them (`script->frameRangePlug()->getValue()`) and I access them as 0,1 rather than x,y. But I can switch it if you feel strongly. Also, I made if float because context->getFrame() gives a float.


Die `src/feedback_send.js` Datei ist aber ziemlich kaputt. Die habt ihr wohl falsch auf Github gespeichert. Habt ihr die noch irgendwo so, wie sie gedacht war?


You should not have merged your fork with the master.
How will you handle your squash? I suggest your cancel this commit.

Besides, you did not implement the last requirements about this issue.
Where are the default values? See #514

And your commits about this issue should include this exact string ``#514` so that they are referenced from the issues tracker.


Oh really? I thought it wouldn't for some reason... I guess I never actually tried apparently.


/* this is added line just for testing */


you should preserve the error of ``replace_uri`` and ``split_query``.
Just set ``r`` to -ENOMEM at the beginning and return ``r``


>Oh, dear lord, that complicates things.

Yes. I've been thinking about it, and I think that, *in theory*, it is impossible to do bottom up resolve in rust. *In practice* it should be pretty straight forward, but some knowledge of a project structure is required. That is, information from `Cargo.toml` is needed to determine the crate root.


Ach was, die füg ich auch im Pull Request dazu. Die braucht man eh nur aus meinem Projekt kopieren. Pull Request kommt gleich.


@mLuby hmm well using epoch would make it simple to manipulate the date on any UI to follow any format.  However, that can easily be done also using a string (just adds one more step).  I really like the idea of skimming the DB and knowing what the dob is since we wont have an admin tool... let keep the string as you have it.


Additional-report-variables-ZoneHVACIdealLoadsAirSystem (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1915 of 1963 tests passed)

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


cool


Looking again, I see the plugs on script are ints, so that change seems reasonable here too.


@urlsangel for sure! I will deploy a new version tomorrow


Ik
On Nov 9, 2015 11:40 PM, "srisurya95" <notifications@github.com> wrote:

> cool
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/TeamOrion/android_build/commit/ad1cfdd917e6fe09a651057253665a69e2b9369b#commitcomment-14283344>
> .
>


indentation seems off here, might want to run auto-formatter.


Unless I'm misunderstanding, this is a bit naughty - it's dirtying outPlug() based on changes to fileNamePlug() etc, although those don't directly affect the computation of outPlug(), it's the output of the ColorSpace node which does that (and therefore is indirectly affected by the filename etc). I don't recall which node it was, but I did the same thing recently and came to regret it.

It's best to play by the book, and create an input ImagePlug to receive the result from the ColorSpace node, and then declare the dependencies between that input and the outPlug().


Is `'1900.1'` supposed to be between the quotes? The name of the test (`...with_non_integer...`) suggests you'd want to test against a float value here.


This is strange i would assume it would work if the getter is named isRetired since it is a standard getter method for a boolean property as per the java beans spec


I think....

```java
String volume = this.targetProperties.get(OpenstackIaasHandler.VOLUME_SIZE_GB, "-1");
if( vsize>0 )
```

... would be better. :wink:
We cannot have unit tests on this part. So, the less lines and conditional branches we have, the better it is.
Besides, once you implement default values in #514, you code will look like...

```java
String useBlockStorage = this.targetProperties.get(OpenstackIaasHandler.USE_BLOCK_STORAGE, "false");
if( Boolean.parseBoolean( useBlockStorage  )) {
      String volume = this.targetProperties.get(OpenstackIaasHandler.VOLUME_SIZE_GB, DEFAULT_VOLUME_SIZE);
      ...
}
```


OK.


Additional-report-variables-ZoneHVACIdealLoadsAirSystem (JasonGlazer) - 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)


k


Well, this actually *breaks* whitespace handling for me. If there's trailing whitespace, this'll loop indefinitely.


@robinsharma this was a bad change. Should have left it in


@rhvgoyal: If existing container images are formatted with a filesystem that is not the host filesystem, df will report incorrect fs.


No, it is not TM tweak. It looks more like bad design to have search dependent on time.  When running analysis stockfish will depend differently. I don't think even if patch passes it will be accepted. I think it should be respined in term of depth dependence.


TeamCity LabkeyRelease15.3 :: Git sqlserver 2014 [Build 17](https://teamcity.labkey.org/viewLog.html?buildId=283809&buildTypeId=LabkeyRelease153_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:05:36


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

```


You have this check twice. And here it will never be true since you just added the scheme in the line above.


Ignorant question: any chance of "NOT OK" or something like that coming up as the result of a failed `dpkg` command execution?


So given the requested change to non-V2i plugs, do you think it should still be organized by range and modes or should the 2 values pertaining to the start be  grouped together and the 2 values pertaining to the end be as well?

`node.frameRangeMask.start`
`node.frameRangeMask.end`
`node.frameRangeMaskMode.start`
`node.frameRangeMaskMode.end`

or

`node.startFrameMask.frame`
`node.startFrameMask.mode`
`node.endFrameMask.frame`
`node.endFrameMask.mode`

or something else?


@josephsavona I don't *reeeaalllyy* like this, but... mutations currently seem pretty adamant on having `this.props`...


Closes issue 5.


Yes. I also thought to add the open-if functionality.  This was just a
first take.
On Nov 9, 2015 7:38 PM, "Christopher Chase" <notifications@github.com>
wrote:

> The patternfly modal doesn't seem to be any different than the bootstrap
> one. It might be better if we keep it associated with bootstrap and even
> contribute it to an ember-bootstrap project. We could then build
> ember-patternfly on top of it without being directly coupled.
>
> I think we should probably implement an open-if the same way the old one
> did so we're encapsulating the bootstrap/jquery related stuff in the
> component and not polluting our application.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/isratrade/fusor/commit/f3fd8dbd6c00d677ac61c2bff70e6b29c4b70a36#commitcomment-14282562>
> .
>


TeamCity libpalaso :: palaso-precise64-master Continuous [Build 3.0.555.4a69b295f3e32c134ae35638aec57742058b5d74](http://build.palaso.org/viewLog.html?buildId=65832&buildTypeId=bt322) outcome was **FAILURE**
Summary: Tests passed: 3287, ignored: 106; exit code 163 (new) Build time: 00:29:10


I took a look in the OIIO docs and found this about the oiio:ColorSpace metadata :

> The "oiio:ColorSpace" attribute may take on any of the following values:
"Linear" indicates that the color pixel values are known to be linear.
￼￼"GammaCorrected" indicates that the color pixel values (but not alpha or z) have already been gamma corrected (raised to the power 1/γ), and that the gamma exponent may be found in the "oiio:Gamma" metadata.
"sRGB" indicates that the color pixel values are in sRGB color space.
"AdobeRGB" indicates that the color pixel values are in Adobe RGB color space. "Rec709" indicates that the color pixel values are in Rec709 color space.
"KodakLog" indicates that the color pixel values are in Kodak logarithmic color space.

It seems that not all of those are supported by the ColorSpace node (at least not with the default OCIO config we ship with), and the "GammaCorrected" value would require the use of the Grade node internally. It seems like this should probably be a concern? I suspect we may also need a way for the user to say "OIIO is wrong, it's in _this_ colorspace, I promise".


Hmm, something might be still wrong. I used the extract-feature-segments with the latest Karel's commit and rerun my experiment -- the WER went up. My scenario is opposite to what Karel described in https://github.com/kaldi-asr/kaldi/commit/f87f27a3a58a56f6426639b4a231e329aa032a49#commitcomment-14265043: I have a system bootstrapped on Kaldi features, and then want to switch to HTK style bottleneck features, using existing alignments.


why not parsing <var>payload</var>


1.0.x does not work on npm yet.


Getting this error being raised using the following:
```python
'''
Results in the following error:

Traceback (most recent call last):
  File "broken_test.py", line 25, in <module>
    optimal_trajectories=10, local_optimization=True)
  File "SALib/SALib/sample/morris.py", line 88, in sample
    local_optimization)
  File "SALib/SALib/sample/morris.py", line 180, in compute_optimised_trajectories
    local_optimization)
  File "SALib/SALib/sample/morris_util.py", line 375, in find_optimum_combination
    maximum_combo = find_local_maximum(input_sample, N, num_params, k_choices, groups)
  File "SALib/SALib/sample/morris_util.py", line 331, in find_local_maximum
    i_max_ind = get_max_sum_ind(indices_list,row_maxima_i)
  File "SALib/SALib/sample/morris_util.py", line 285, in get_max_sum_ind
    raise ValueError("indices and distances are lists of different length")
ValueError: indices and distances are lists of different length
'''

import sys

from SALib.analyze import morris
from SALib.sample.morris import sample
from SALib.test_functions import Sobol_G, Ishigami
from SALib.util import read_param_file

import numpy as np

sys.path.append('../..')

problem = read_param_file('../../SALib/test_functions/params/Sobol_G.txt')

param_values = sample(problem, N=1000, num_levels=4, grid_jump=2, \
                      optimal_trajectories=10, local_optimization=True)
```


just a quick note as you continue on this - anything that requires calling a private method should really just be converted to public API. so `RelayStore.prototype.initializeGarbageCollector`


Is this password strength field going onto the setup -> user setup panel too?


Agreed :+1:


I don't think this remark in the brackets is necessary; we'd have to put it near almost every support comment. Writing:
```js
// Support: IE 9 only
```
would be enough.


This is how:

Let manifest be the result of parsing text. If parsing throws an error.

So we could do

```
Let <var>payload</var> be <var>ndef.PAYLOAD</var> converted to UTF-16, and set <var>record</var>.data to the result of <a data-lt="JSON.parse">parsing</a> <var>payload</var>. If <a data-lt="JSON.parse">parsing</a>  throws an error, skip to the next <a>NDEF record</a>.
```


you need to commit your radish logo and bill's photo


Hi,

  As Ben Hale mentioned in the other issue you raised, the 12.1.1.1 is a local address for a sample file server that can serve the weblogic binaries. You can have a local file server or a java webapp serve the same binaries (for weblogic and jdk/jre) and let it listen on 8080 or 7001 as the case may be and have your repo refer to http://localhost:8080/fileserver/jdk for jdk and  http://localhost:8080/fileserver/wls for weblogic. Once you have the index.yml file for the jdk and wls that references the binary with right version etc, you can create the offline buildpack that would download and bundle the binaries.

Check the documentation on this local setup here: https://github.com/pivotal-cf/weblogic-buildpack/blob/master/docs/container-wls.md

-Sabha


Any reason we hash these even though they're not used in the corresponding compute?


I know the "throws an error" more than the past tense "threw an exception"


Oh, my bad. `q` belongs to the dynamically created mappings due to some technical details. I'll extend `s:register()` and push a fix in some minutes.


@zednis How does it look like now?


Yes that is part of why I made it a suggested package rather than a dependency. Plus the dependencies are pretty massive so even after everything works right I could see an argument for not installing accre-gridftp automatically by default.


This feels a bit awkward. How about we just make Context::Scope a no-op if NULL is passed? That way we don't need any branching here.


That would be grand


you left an orphaned whitespace in the tag


glad to see you are making progress!


Maybe add the counterpart - that no email is sent when the form is invalid.


This is actually a small code change, not a documentation change. The commit is therefore mislabelled, but I'm too inept to be able to figure out how to adjust it.


Yeah, completely agree, map key->true looks silly. I just didn't want to tinker too much with this code for this fix.


Since the compute is doing a direct pass-through of an input value, we should just be assigning directly to the hash to signify that. We'll then end up with only one entry in the cache.

`h = colorSpace()->outPlug()->formatPlug()->hash( h );`

Because we're doing this direct assignment, we also have no need to call the base class implementation first.


This could be a question of, you would benefit from label delay or
something like that.  I don't think we should be using WER to compare this
kind of change.
Dan

On Mon, Nov 9, 2015 at 1:19 PM, Tanel Alumäe <notifications@github.com>
wrote:

> Hmm, something might be still wrong. I used the extract-feature-segments
> with the latest Karel's commit and rerun my experiment -- the WER went up.
> My scenario is opposite to what Karel described in f87f27a
> #commitcomment-14265043
> <https://github.com/kaldi-asr/kaldi/commit/f87f27a3a58a56f6426639b4a231e329aa032a49#commitcomment-14265043>:
> I have a system bootstrapped on Kaldi features, and then want to switch to
> HTK style bottleneck features, using existing alignments.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kaldi-asr/kaldi/commit/7276702c457042367ef54fc3511c0281fdfa9dc6#commitcomment-14283519>
> .
>


This is a semantics thing, but maybe this page should be titled "Poems by Author" or something like that since they are basically just filtering the poems by author, rather than actually discovering authors.  Other than that I think this is great and should be merged into master.


This is interesting - it's the first test that suggests that permissions are formatted as `model.perm`. If this is the case, maybe it would be good to have some tests that cover that (check that permission names are created as expected). If this isn't the case, maybe a comment here explaining where `contacts.{0}` comes from.


Decided to decouple the vote results from the implementation. It willl still happen, just not in this release.


Disable your origin for pushing:
```
git remote set-url --push origin no_push
```
Then this mistake cannot happen. Ah I see, we are pushing into branches it the main repository. @ahmadia recommended that approach, but I think we should stop doing that, and rather use our own forks for that.


No, definitely no reason for the change, stupid oversight on my part. Will try to get a patch out today.


I think that silly leftover from a time I was tearing my hair out trying to figure how to get the output to update


Although of course we wouldn't be using colorSpace()->outPlug() directly like this, we'd have connected it into a private input on our node.


You might as well convert this entire file into tab in a separate patch. So that we can gradually move on to consistently using tab.


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

```


Yep, the reasoning behind this is indeed correct. From the `apt-get` man page:

```
install is followed by one or more packages desired for installation or upgrading. Each package is a            package name, not a fully qualified filename (for instance, in a Debian system, apt-utils would be the          argument provided, not apt-utils_1.0.1ubuntu2_amd64.deb).
```


From the top of my head, I don't see anything wrong with your code. Do you have any questions on this chapter?


This seems to contain identical logic to the above. Would it be possible to implement it all in hash()/compute(), for any time the plug in question is a child of outPlug()? I see the logic is slightly different for the metadata, but still it might be clearer to have this all in one place (with one special case in that one place) than to have multiple duplicate implementations.


Thanks @michaelrshannon! I'll take a look at this tomorrow or the day after and get back to you with some feedback.


If these become instance methods on `RelayStore`, is there any reason to keep `RelayGarbageCollection` around? (i.e. `RelayStore.prototype.scheduleGarbageCollection` and remove `RelayGarbageCollection` entirely)


You can delete this time actually, since I removed it. since the clock res is not needed or used.


TeamCity LabkeyRelease15.3 :: Git sqlserver 2014 [Build 18](https://teamcity.labkey.org/viewLog.html?buildId=283812&buildTypeId=LabkeyRelease153_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:25


sorry about that, it was the oddball 'not found' message that was missing the !


Merging this but will update `bench.py` to properly format columns tonight.


Search iterations are only started when there should be enough time to complete them... Search depends on time, otherwise time management would way worse!


Tu as fix ton problème de test grunt. Un problème d'import des js , ou des data lors du state ?


In an related comment, using `dpkg` directly can lead to some strange scenarios, such as packages installed (directly from files) but not configured **due to missing deps**:

```
$ dpkg -i zsh-static_5.1.1-1ubuntu1_amd64.deb
Selecting previously unselected package zsh-static.
(Reading database ... 64543 files and directories currently installed.)
Preparing to unpack zsh-static_5.1.1-1ubuntu1_amd64.deb ...
Unpacking zsh-static (5.1.1-1ubuntu1) ...
dpkg: dependency problems prevent configuration of zsh-static:
 zsh-static depends on zsh; however:
  Package zsh is not installed.

dpkg: error processing package zsh-static (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Errors were encountered while processing:
 zsh-static
```

Well, their design... their decisions...


why is this comment here?


I'm wary of this one - I suspect it's entirely possible for those child widgets down below to actually be inside another PlugLayout, which is also doing its own activation management. PlugLayout was designed to operate on the direct children of the parent only, and defer to PlugValueWidgets below this to work independently.


@anusha-ragunathan So one can change underlying filesystem of /var/lib/docker while there are already containers in there? This would be possible if we had a container migration infrastructure where we could
migrate containers from one fs type to other. In that case we should be able to save a metadata file for default fs and try to enquire the fs of /var/lib/docker/devmaper only first time docker starts.


You could vectorise this procedure.  For example, instead of the for loop over combs, use the (2xN) matrix to index `distance_matrix'.
So, the whole procedure becomes something like `np.sqrt(np.sum(np.square(distance_matrix[combs]), axis=0))`


Wondering what the reasoning is for `require` being cleaner? Later on in the handouts you send up going with `import` anyways.


@dianakhuang, let's chat about the waiting logic sometime. This commit/file in particular feels clunky, with explicitly checking every possible combination of `peer`, `ai`, and `staff`.


missing a 'p' on the first `private`


I tried doing something like originally, the problem being that each compute method returns a different type of object, and you can't just cast things from ObjectPtr because ValuePlug->getValue() doesn't actually exist. Also, there are 2 versions of the logic. format/dataWindow use one version of it, and metadata/channelNames/channelData use the other.


weird, because my latest commit acutally looks like that: https://github.com/tehcyx/Vox/blob/master/source/VoxGame.cpp#L53-L57


@rhvgoyal the loopback does not have to match the host filesystem type.  If the issue is that ext4 is slow with the loopback and DM then we can use xfs by default same as if the user specified xfs for the loopback.


.collect(Collectors.toMap(...)) does not seem to work with IntStreams....
yet I can simply boxed the IntStream into a Stream<Integer> an do as usual.


A minor note: the message may lead to user to believe that this cannot install packages (from whatever source) locally (as in *this system*). Maybe be more clear about it: *SoftwareManager AptBackend can not install packages from local ".deb" files unless...*


I realize that response was all about compute() and not hash(), but since we want them to be paired side by side in the code, and I couldn't figure out how to generalize the computes, it seemed clearer to leave the hashes in place as well.


1300 dowloads more and you will have to register you NPM as bloger identity XD. \#MotherRussia


I don't see the powerline problem over in [my branch](https://github.com/jeffkowalski/nyan-mode/network)
My branch is up to date with all of your changes and has a few of the other enhancements built in as well.  It may be useful to you as a debugging baseline, or if you'd like I'd be happy to put up a pull request.


i have no clue why this is showing up in my home directory.


Ah, how wonderfully inconsistent of me :). I usually like using `$` if I make sure it's just an alias to `jQuery` within the current scope, but I guess I wasn't 100% sure on how to do this with this Coffeescript module pattern (this was my first Coffeescript project).

For consistency, I think we'll still with `jQuery` for the project as that seems to be the predominant pattern.


@Konfekt Thanks again for reporting.


Uh oh. The Travis build failed because we upgraded to Java 8: https://travis-ci.org/IQSS/dataverse/builds/90152574

I think we'll need to update our .travis.yml file per http://blog.travis-ci.com/2013-11-26-test-your-java-libraries-on-java-8/

@sekmiller do you want me to go ahead?


TeamCity libpalaso :: palaso-precise64-master Continuous [Build 3.0.556.4a69b295f3e32c134ae35638aec57742058b5d74](http://build.palaso.org/viewLog.html?buildId=65843&buildTypeId=bt322) outcome was **SUCCESS**
Summary: Tests passed: 3287, ignored: 106 Build time: 00:17:04


Good point... yeah I do it to avoid a O(n^2) but I guess that most of the time is going to be just a single sample so it might just be better to remove the optimization, will do.


Move this below the check for values/nulls that are not the same length?


Do you suggest I should send the float structure with the derotated velocities and one with the the noise model directly from the optical flow module? As in make a different/separate abi message?

Op 9 nov. 2015 om 19:01 heeft Felix Ruess <notifications@github.com<mailto:notifications@github.com>> het volgende geschreven:

I would rather change this in the guidance opticflow module as well...

—
Reply to this email directly or view it on GitHub<https://github.com/knmcguire/paparazzi/commit/b0cfb6160fa5efdccdcd921348b9c7282c1bc8be#commitcomment-14283147>.


@geodotka -  zadanie domowe odrobione


Thanks @amgad-naiem!  I've updated the URLs on the `staging` branch.


Ok, we can remove this, but lfn_open needs to return the Index object and keep it alive -- it's an implicit lock.  This commit introduces unpleasant races which can crash the osd.


Can we eliminate `num_rows` as an arg and do `len(values)`?  Or are you worried about extraneous `len` calls?


I see your point, but it seems a pitty (and incredibly unintuitive to a MyNodeUI.py file creator filling out metadata) to not be able to specify activators on grandchildren. Would you rather require that any multi-plug widget know how to respond to activators on its own?


Thanks; I had run into test errors with 2.10 and had put this on hold until I had time to investigate; but that saves me some time! I'll roll back to 2.9.3


It needs to be modified to account for more than two regions.


ACK


:muscle:


https://github.com/JuliaOpt/CoinOptServices.jl/pull/5 has been open for a while, and the upstream tarballs were a little wrong until today ref https://github.com/coin-or/OS/issues/1


This was not an issue for me, somehow this directory was created during the install. But it does not hurt at all to be safe, so :+1:.


Should the `Cursor` constructor take the `convert_types` arg instead?


The problem is that plugin_context is not available when called via the l3 router function update_floatingip.  Therefore, _update_port either needs to accept both, or write a separate function that does the same thing.


@mLuby  shouldn't we validate the address before creating the transaction?


Isn't it just .se now?


`user='" . $user . "'` can still become `user='$user'`, or whatever other way you want to quote it like with the backticks earlier

``SELECT `user` `` is good though.


Yeah pointerEvents="none" works perfectly. Thank you, much better to have a consistent approach.


I understand that, just me and git don't always get along


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

```


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.103.227842c776b5f08ec54b10d1683a405b0bed2930](http://build.palaso.org/viewLog.html?buildId=65839&buildTypeId=bt2) outcome was **SUCCESS**
Summary: Tests passed: 939, ignored: 50 Build time: 00:38:34


Yes please.


Interesting, I'm not mirroring sources come to think of it.

Can you share the deb lines from your mirror.list?


what you said about the constant "table" makes sense, but is there a reason to put 'plx.google:m_lab.ndt.all' into the format() call instead of directly into the built_query_format string?


Additional-report-variables-ZoneHVACIdealLoadsAirSystem (JasonGlazer) - i386-Windows-7-VisualStudio-12: OK (1915 of 1963 tests passed)

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


Yeah, both classes on the body is no problem.


That's the tricky bit I'm not at all sure about, but I also don't feel that what we have now is right. If the error handling and frame range mask were combined, would that give us what we need? Or is it important to have a no-effect mode for the frame range mask?


As far as I know, that's a different team.


@prallabh the return there is unrelated to the error case. The return is because in the case we need to handle user manifest we do that when calling handle_user_manifest(), and at that point we're done with the processing. We were missing the finish_get_obj() call I think, but note that we don't have that problem with the current code (since hammer).


[SaguaroQL->fetch_array()](https://github.com/spootTheLousy/saguaro/blob/master/_core/mysql/mysql.php#L56)

However, `SaguaroQL->fetch_assoc()` would be better since we're accessing the columns by name and not index.
Fetching the array returns the row with indexes and column names.


@bgoodri I think these changes should give us the right output for posterior_predict for stan_glmer models.

* `.pp_data_mer` now returns `cbind(X,Z)` instead of `X` and `Z` separately
* `posterior_predict` uses the new `as.matrix` method for getting posterior draws, which automatically drops the extra reTrms

Does that seem right?


:joy:


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.105.8579094d17841ca988ca32bdbb28fd31fc089a8d](http://build.palaso.org/viewLog.html?buildId=65849&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj (new) Build time: 00:01:35


@crosbymichael I think we can ignore this patch for now. This is a proof of concept patch only. And will be meaningful only if we can make both ext4 and xfs reaosnably well.

For now, let us focus on figuring out why mkfs.ext4 is slow in certain configurations and is there a way to handle it. Right now I have following up this issue with ext4 developers inside redhat. Lets see if something good comes out of it.


The rest of this list is alphabetized, so probably stick with that precedent.  And you'll want to update the [README's model list][1] too.

[1]: https://github.com/azurestandard/azure-angular-providers/blob/968e28d9a11fc57840a873aefb53747ea5437a98/README.md#azureapi


No, exe version - old.


Hey Brian,
I'll get my errors cleaned up. I was also wondering if we should allow the user to crop the image they upload(via a new window which they can move a fixed box to crop the image)?
Sorry about the commit with warnings, I should be more cautious.


Use constants instead magic numbers.


Additional-report-variables-ZoneHVACIdealLoadsAirSystem (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (889 of 889 tests passed)

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


Are these valid? I don't trust GitHub's syntax highlighting.

You'd either have to swap out `"` with `'` or change the outer double-quotes to single quotes.


EventLogger?


This compiles? oO


107712554-FixRefrigerationCondenserWaterCooledNotRegistering (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1426 of 1426 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-70.47%25-green.svg)


Does writer need to be exported?


very nice!


shouldn't this line be "return null;" instead ? A message with an invalid/null chunk may be valid ?


It looks like the `gdebi` package includes a bunch of graphical utilities, and the requirements are quite extensive. Package `gdebi-core` looks like it's more appropriate here, as it includes `/usr/bin/gdebi` and it's what you're checking for on 9e3227f643b5e5de6035ec5b6ec92481ac8e83f4.


Why all the sudo?


You only added it to the Debian OS?


Oh, you're right, sorry


Yes, although we need to add that ability to posterior_predict with the
extra reTrms for unknown groups. You may be able to call factor() on the
new grouping levels with levels set to the levels including "_NEW_"
whatever. That might cause any unknown groups to come up as NA, in which
case you can replace them with "_NEW_" whatever.

On Mon, Nov 9, 2015 at 1:48 PM, Jonah Gabry <notifications@github.com>
wrote:

> @bgoodri <https://github.com/bgoodri> I think these changes should give
> us the right output for posterior_predict for stan_glmer models.
>
>    - .pp_data_mer now returns cbind(X,Z) instead of X and Z separately
>    - posterior_predict uses the new as.matrix method for getting
>    posterior draws, which automatically drops the extra reTrms
>
> Does that seem right?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/66c4cd69e4b2b280e993014ef0cab24949305c51#commitcomment-14284093>
> .
>


You are a life saver... Thank you!


OK!


This test would be easier to understand if you added some values to the event then checked the actual string written . . .


Не хватает теста на параграфы, какого-нибудь большого сложного теста, на подчерки внутри текста с цифрами


1640-AddHVACPart1-tertiaryLoops (kbenne) - Win64-Windows-7-VisualStudio-12: Build Failed

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


yes and the infos in there are just for your file system. They do no good when I have them. Keep them in the .gitignore and remove them from tracking.


LGTM


Just use `fetch_assoc()`.


It might also be useful to introduce people to `npm ls` at this point, although it's a good idea to have people use the OS's tools to verify their understanding of what npm's doing. (Also, `npm@2` and `npm@3` users are going to see different things in this directory, because of default flattening.)


@mLuby  any reason for not putting `completePendingTransaction` into a service?


I mean, Nuke doesn't have the no-effect mode on the mask, so obviously pro-compers don't seem to mind. But personally, I find it to be a heinous oversight. You browse for a file sequence, select it, and it locks down your read node to that range automatically. Say you did that in the middle of a render. Your read node is still locked to the range at browse time, and you never notice you have new frames. Personally I'd always use the reader in no-mask mode, except in very specific setups with known range limits.

Also, @hughmacdonald seemed to think ErrorMode and FrameMaskMode should be thought of as distinct things. I'm not sure if he just meant, we also need the range masking it can't just be error handling, or if he meant the same thing I'm saying about wanting a no-mask mode.

What if we short-circuit the lookback when you go past script.framerRange.start? I guess that might be undesirable in some cases though...


why do these things keep happening to me


107712554-FixRefrigerationCondenserWaterCooledNotRegistering (JasonGlazer) - i386-Windows-7-VisualStudio-12: OK (1961 of 1962 tests passed)

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


I'd word this as as "Unix systems, including OS X" – the problem with `*nix` there is that it appears to be triggering Markdown weirdness.


I gave a detailed explanation why `fetch_assoc()` is preferred over `fetch_array()`.


You can use `ValuePlug::setFrom( otherPlug )` within `compute()` to transfer values from the input to the output - that's what things like the Switch and ContextProcessor nodes do.


There are a number of queries made by a new `Order` (e.g. `Order._drop` and `Order._stop` both make queries), so you probably want a less generic name for this promise.  Neither `Order.orderLinePromise` nor `Order.promises.orderLine` feels like quite the right name to me, but I can't think of anything better, and I'm ok with both of those.  You'll also want to document this new public property in the README section on `AzureOrder`.


I think you typically want to stack multiple CSS selectors, rather than keep them all on the same line.  This will improve readability.  Like so:
```
h1,
h2,
h3,
h4 {
    /* some stuff */
}
```


Had to cut corners. Thx for fixing.


This can still be `class='$class'`


Yay for buggier manual ;P


@Sandy4999 maybe should check to see if initialized here?


Thanks, that's actually a major bug. I have it corrected in my local version.


Wow, the fix was fast ! :thumbsup:
I wonder if a message with a null chunk can be valid though.


Although, the redirect wouldn't help much anyway as the entire system has changed. But at least now there's an API: https://opendata.bayern.de/ckan-api?9


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

```


No need to post them on both branches, one is sufficient!


Yeah, this was just to get it working. Haven't done the new levels yet.

On Mon, Nov 9, 2015 at 1:52 PM, bgoodri <notifications@github.com> wrote:

> Yes, although we need to add that ability to posterior_predict with the
> extra reTrms for unknown groups. You may be able to call factor() on the
> new grouping levels with levels set to the levels including "_NEW_"
> whatever. That might cause any unknown groups to come up as NA, in which
> case you can replace them with "_NEW_" whatever.
>
> On Mon, Nov 9, 2015 at 1:48 PM, Jonah Gabry <notifications@github.com>
> wrote:
>
> > @bgoodri <https://github.com/bgoodri> I think these changes should give
> > us the right output for posterior_predict for stan_glmer models.
> >
> > - .pp_data_mer now returns cbind(X,Z) instead of X and Z separately
> > - posterior_predict uses the new as.matrix method for getting
> > posterior draws, which automatically drops the extra reTrms
> >
> > Does that seem right?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/stan-dev/rstanarm/commit/66c4cd69e4b2b280e993014ef0cab24949305c51#commitcomment-14284093
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/66c4cd69e4b2b280e993014ef0cab24949305c51#commitcomment-14284180>
> .
>


Until this is done correctly in CSS:
````PHP
$class = 'row' . ($j % 2 + 1);
````

Test this first, it may have problems combining the string and number.


If you're going to mention this, you should probably either document or link to the documentation for `init.author.email`, `init.author.name`, and `init.license`, so that people will end up with useful `package.json`s after running `npm init -y`.


Should mention that every package *must* have a `name` and a `version` (I notice that your example below is missing a `version`).


Since azurestandard/beehive#1244 and #16, order-line price handling in azure-angular-providers is obsolete, so we can probably just drop this commit.


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

```


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

```


Per conversation with @bengolder we shouldn't put these API keys in the settings file; they should be a config file instead for security reasons.


I think abort() takes a message. (I didn't know about abort() until I saw you use it, so I looked up the docs.)


Per conversation with @bengolder we shouldn't put mail user names and passwords in the settings file, even if they're just for development purposes; they should be a config file instead for security reasons.


Hmm, nothing comes to my mind so I think I don't have.   :palm_tree:


Я знаю что ты разговариваешь по Русски... Пожалуйста помоги мне в создании такого же бота :)) наверное в github нельзя отвечать на комментарии, по этому пожалуйста напиши мне в телеграмме мой ник - @SPUZ_FEED


Ah, you're right-- I should have added it to defaults.yaml. I'll make the change, just a minute


Actually there should be no scaling needed at all...
It should be properly calculated in opticflow_calculator.c opticflow_calc_frame(), if not then some of the camera parameters are wrong.


May be we can output "Base device is already initialized to size %s, new value of base device size %s will not take affect."


 [{name: 'Jack'}, {name: 'Jim'}, {name: 'John'}][0]
# => {name: 'Jack'}

return entry if name == entry.name


name = 'Jack'
entries = [{name: 'Jack'}, {name: 'Jim'}, {name: 'John'}]
entries.each_with_index do |entry, index|


s/affect/effect


(closes #7 )


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.106.8579094d17841ca988ca32bdbb28fd31fc089a8d](http://build.palaso.org/viewLog.html?buildId=65854&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj Build time: 00:03:23


This broke mocking __toString to return anything **except** `''`, since the return from the match is only used when $hasReturnValue is false.


see comment above about access to ApacheSingularValueDecomposer; would have to change this accordingly


remove comment?


ditto


whitespace


Sanity test:
before running the code to be tested, confirm data was set up correctly:

  expect(book.entries.size).to eq 3


optimize imports


Shouldn't this be wrapped in `save-match-data`?


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.104.9fb392461b836e64ea080d4cecb560194578e62c](http://build.palaso.org/viewLog.html?buildId=65846&buildTypeId=bt2) outcome was **SUCCESS**
Summary: Tests passed: 939, ignored: 50 Build time: 00:38:15


make parameters final


TeamCity Chorus :: chorus-precise64-master Continuous [Build 2.6.523.9fb392461b836e64ea080d4cecb560194578e62c](http://build.palaso.org/viewLog.html?buildId=65847&buildTypeId=bt323) outcome was **SUCCESS**
Summary: Tests passed: 927, ignored: 54 Build time: 00:22:52


final


You're right, I got confused with the need of making onShutdown robust to onStartup on non-GATKTool tools, nothing to do with walker nor with onTraversalStart/Done pair. Will clean up.

Also I realized I don't need to keep track of the outputWriter in a field, so removing that too.


I do feel strongly about this one. Although I do see your argument about programmer convenience in using `[0]/[1]` (and I feel like I've done it myself somewhere too), the user sees plugs only by name, and the x/y there is going to be real weird.

The frame is a float in the context because it's used there to represent continuous time. But the ImageReader (and ScriptNode) are about discrete frames, so I think the int is more appropriate there.

To me it seems logical to associate the frame number and mode strongly by making them siblings - so something like the latter of your two options I think. Does that sound OK to you @hughmacdonald? I also suspect that by doing it that way, we can create a little custom PlugValueWidget to hold the two child widgets and deal with the activations, and then we can survive without the UI stuff I'm uneasy about.


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.107.9afed817a3ed30441db5808c19a1c39dcd3b749c](http://build.palaso.org/viewLog.html?buildId=65856&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj (new) Build time: 00:02:00


Of course it's not valid Kotlin code, because quickfix is intended to fix invalid code :smirk:
Hovewer if you're sure that it's far-fetched case, I can remove it


In this case, `boost::this_thread::thread_id()` returns a `thread::id` type object; AFAICS this is the best way of getting the thread id out of that object (since that `<<` overload is provided)


Closes #6


@sam3000 @Decad3nce none of these init or selinux changes were needed the files are all in /vendor...

for reference http://tinypic.com/r/6f2ryb/9


Can we make the fruit-names lowercase, and remove Passionfruit since I suspect the two words may create problems?


fixes Star Wars galaxies as well with no color issues that I see


When using version control you should only commit your source files.  Files such as these should never be committed.  Same goes for binaries. The reason is that these files can be user specific and if someone were to fork/pull/fetch your repo it would pollute their system and cause issues.


@clebergnu I could have sworn I added gdebi-core there. I'll fix this ASAP, thanks!


TeamCity Chorus :: chorus-precise64-master Continuous [Build 2.6.524.9afed817a3ed30441db5808c19a1c39dcd3b749c](http://build.palaso.org/viewLog.html?buildId=65850&buildTypeId=bt323) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:04


I don't believe so


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

```


I agree, I'll check it out tomorrow. Freek (fvantienen) explained to me why the module worked with cm/s once, but I'll ask him again where this scaling takes place. Also when the reference speed is used in de optical flow guidance module, it is definitely not in m/s, so this scaling is causing quite some confusion.

Verstuurd vanaf mijn iPhone

Op 9 nov. 2015 om 20:02 heeft Felix Ruess <notifications@github.com<mailto:notifications@github.com>> het volgende geschreven:

Actually there should be no scaling needed at all...
It should be properly calculated in opticflow_calculator.c opticflow_calc_frame(), if not then some of the camera parameters are wrong.

—
Reply to this email directly or view it on GitHub<https://github.com/knmcguire/paparazzi/commit/b0cfb6160fa5efdccdcd921348b9c7282c1bc8be#commitcomment-14284383>.


Why were unrelated patches removed by this commit? For example:
- patches/uClibc/0.9.30.2/200-clean-up-O_CLOEXEC-handling.patch
- patches/uClibc/0.9.33.2/200-fix-kernel-3.4plus-build.patch

The removal of the latter broke all the uClibc sample configurations.


Addresses #12


final


If we did that, we'd still have to pass in a non-plugin context or make a duplicate function that does the same thing for each type of context.


Different Color for the Maze


that produces are rather ugly log format , no?


@rhvgoyal Do you know why it only happens on AWS?

Also, do you know if passing `--storage-opt dm.fs=xfs` on a host where `/` is ext4, will result in performance penalty? Is it recommended?


This is only necessary because of the bug in `CompilerDirectives.isCompilationConstant()` (I've run into a few wrongly reported cases while poking around). There is no difference in the assembly.

Maybe a TODO to remove it if/when `CompilerDirectives.isCompilationConstant()` is fixed?


I know this wasn't the point of your commit, but why not drop the `.. = 0, .. = 1, .. = 2, ...` ?

It's an enum{} after all, so you could just do `enum { Normal, Normal_NoSysCheck, ... }` without doing the = 0, = 1, ... and it would automatically assign 0, 1, 2 etc. based on the order without you having to explicitly type the values.  This would make it more maintainable in case you wanted to revise the order of the lines without also having to re-type all the numbers each time.

Unless there is some explicit reason why exactly 0, 1 and 2 must be assigned?


Haha.  Yeah, I didn't want anyone to access the `BP_Follow_Updater` class unnecesarily.

But, that unfortunately means that unit tests are harder to set up.  See what I did here in BP Follow:
https://github.com/r-a-y/buddypress-followers/blob/master/tests/phpunit/includes/bootstrap.php#L40


Yeah a default no-effect mask seems more natural to me too, although I'm not sure if that's just because it's what we've had for so long. We can't really use the script frame range though - that's external to the ImageReader, and a script node isn't even guaranteed to exist. I'm going to sleep on this one a bit, and see if you and @hughmacdonald have any other thoughts. I will say though, I think I might be willing to compromise a bit on something like the no-effect mask in order to get away from all the file sequence assumptions and direct filesystem accesses...


I think is preferable to do repetitive increments of 1 on a integer or long variable rather than a double or float one.
Perhaps the failure here is that ReadCountRecord does not handle long[] arrays.


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.108.9afed817a3ed30441db5808c19a1c39dcd3b749c](http://build.palaso.org/viewLog.html?buildId=65858&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj Build time: 00:01:30


`Он состоит из состоит` дубляж)


Your code itself is nice and readable. However when we write software, it is good practice to keep modularity in mind. I realize that this code will not be published and released, but it is good practice to keep things modular.  Program.cs is the main entry point of your application, and should only contain your 'Main' function.  Try to break off the rest of the functions into their own classes.  When you go back and want to edit or update this it will be much easier if it is modular.  The main function itself is well written.


Sorry, bad habit. It would be nice to have something like linter in order to enforce consistent formatting


Yes and no.

When supporting meta-annotations, it is not sufficient to use `AnnotatedElement.getAnnotations()` since that will return `@Inherited` annotations as well. If you invoke `getAnnotations()` you will get back mixture of directly and indirectly present annotations. If a user locally declares a composed annotation that is meta-annotated with the target annotation (i.e., the one we are currently searching for), we might accidentally find an inherited target annotation before the locally declared one (that is meta-present), and that will definitely **not** be what the user expects or wants.

We therefore have to be very specific about the algorithm we implement when supporting meta-annotations as first-class citizens in the programming. The JDK unfortunately does not support us in this regard, but fear not... I have extensive experience in this regard. So I'll get it all straightened out. ;)


Done: 93a3be5