Thanks Reynold for reviewing the code!

Since the default mavenRepo will be decided by HIVE_METASTORE_MAVEN_REPO in HiveContext.scala, and always get passed in, so I was adding None merely for the consistent signature look with ivyPath parameter. Might not be a good idea. Have removed this now per your suggestion.


Was kinda expecting this to break everything but I guess it's all ok!
Still some more stuff to do with this but I think it's less-pressing than other stuff for now.


Is this eyes offset the distance between eyes or a relative attribute?


:smile_cat: You were really close on the solution for the last one!

```
function printEachSuperPlus(anArr, callback) {
  for(var i=0; i<anArr.length; i++) {
    var callbackResult = callback(anArr[i]);
    console.log(callbackResult);
  }
}

// calling
printEachSuperPlus(["apple", "toast", "cheese"], function(item){
    return item + "!";
});
```


forget the last comment, I was a bit confused.. :)


Can you add this tip?:
If you run jekyll instance on AWS instead of using Heroku, be sure to `export SESSION_SECRET=your_secret`. Otherwise, session variables won't be available after the callback redirect.

...it took a long time to debug this issue and finally it's working on a docker container on AWS :)


@mattheworiordan Done


Alright... more investigation is needed around build-deploy-gh-pages

since I am using a gh_token things typically just work, but I think there is clearly some other voodoo happening with the gulp tool we are using


This change causes a compile error:
```
==> edown (compile)
Compiled src/edown_lib.erl
/opt/local/zotonic/deps/edown/src/edown_doclet.erl:116: field packages undefined in record doclet_gen
/opt/local/zotonic/deps/edown/src/edown_doclet.erl:118: field filemap undefined in record doclet_gen
Compiling /opt/local/zotonic/deps/edown/src/edown_doclet.erl failed:
ERROR: compile failed while processing /opt/local/zotonic/deps/edown: rebar_abort
GNUmakefile:56: recipe for target 'compile' failed
make: *** [compile] Error 1
```


Files created by my IDE. I ignored them so there is no chance of uploading them to repository.


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


The method design is changed


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


I just wanted confirmation about `it never worked`. We have the exact same case for field that works, and we fixed it by keeping the current wrong alternate and adding the correct one too.


OK, I see what you mean now. Yes, rounding to three decimal places and print a warning for minor versions >= 1000 looks good to me. Thanks!


You mentioned the script becoming brittle so the additional check was CYA.


First commit - learning Git :)


weird stuff intensifies


radios.filter никак не выходит использовать, пробовал через [].prototype.call и просто filter, и перед этим slice(0) - никак.


okay. learn git to understand what just happened


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


I'm a little out of my scala depth here. What does the `: ClassTag` part of this mean?


@lrq3000 I was incorrect: of course, `_ for i in ..` is not the same as `i for i in ...` because `_` is not defined. How can it be used, is it some timeit-specific trick?

I was saying that `[i for i in range(1e8)]` creates a list of 1e8 different numbers, where each number is a different Python object, while `[0 for i in range(1e8)]` creates a list of 1e8 elements which all point to the same object (integer with value 0) - that's why it uses less memory.

Instead of list comprehensions one can use a regular for loop, it won't create a list. I'm not sure it worths a hassle, but that's another option :)


Keep up the great work!


there are no test recordings????


I have updates coming for several similar cards in a bit.


I made the change to the comment you suggested.

The only change that will be needed is to add the "CONNECTION_STRING" to the drillTestConfig file. I had a talk with jacques in the hangout and he mentioned that they have their own fork and also that we need not worry about affecting them. He said he might take a look if possible sometime today.

As you mentioned we are moving towards the right behavior and we did communicate to all parties interested and gave them time to respond. So I wouldn't worry about backward compatibility.


How will people find a cert at this location on their machine, when they run tests? How will this location work on Linux or mac os?


dodaj sprawdzanie czy prawidłowo się zapisały, czy liczba produktów się zgadza.... przecież tutaj nic nie testujesz


tutaj sprawdza czy usunięto (Czy get zwraca nulla)


How can I change the indentation inside the case statement and indent the case labels as a full level (with 4 spaces) ?


w sytuacjach kiedy nie znasz doceloweo rozmiaru listy używaj linkedlist: http://stackoverflow.com/questions/322715/when-to-use-linkedlist-over-arraylist

Plus nazwa zmiennych to małe litery (taka jest konwencja)


I'll open an issue so we can discuss further


@bontoJR looks good!


Fortunately, no, the direct command-line options take care of it, so nice work :) However, it did break my CI scripts and I had to port them, so I think it's technically a breaking change. Plus ember help test still says it's available, so at the very least that should be updated (but I agree with @stefanpenner that it would be nice to preserve the config file option).


@phase How's this?


Wie geil ist das denn :D


It's deprecated in C++17.
Use std::uncaught_exceptions: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4152.pdf
It's should be supported by VS15.


New-Fan-Object (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1435 of 1435 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.5%25-green.svg)


:smile_cat: Your solution for printEachSuperPlus is super close! But check the output when you run it - it gives you something like
```
dogsundefined!
catsundefined!
etc...
```
Try using input[i] as the argument that you pass into the callback on line 21 (so console.log(callBack(input[i])) instead of console.log(input[i] + callBack());)


Fixed in c654e909e0babd21b25ab67ba301a9650a6c2387 (hopefully Travis will prove so)


You're right, I've just checked by running a query against some test data and neither Postgres not MySQL return NULL records under these circumstances. One less thing to check for! :tada:


The good news is that this works in 2.4.2.3 too!


I had got a bug(None type). But it is already fixed.


Just read the specs of the hardware you are using. It talks on their product page about a custom ISM band transmission. It would be good if they would clarify the format for that.


In short, nothing.

But since you were pointing out code style issues, I looked in the file for other places where fields were being accessed from the options object, and they were evaluating for ```!= null``` rather than a basic truthiness check. It works for me either way, so you can let me know your preference.


currently tested for correct functionality of storage.
TODO:
     1)Initiation Loading
     2)Store New Society


ship it if no new comments after a day.

    On Tuesday, November 24, 2015 11:04 AM, Rahul Challapalli <notifications@github.com> wrote:

 I made the change to the comment you suggested.The only change that will be needed is to add the "CONNECTION_STRING" to the drillTestConfig file. I had a talk with jacques in the hangout and he mentioned that they have their own fork and also that we need not worry about affecting them. He said he might take a look if possible sometime today.As you mentioned we are moving towards the right behavior and we did communicate to all parties interested and gave them time to respond. So I wouldn't worry about backward compatibility.—
Reply to this email directly or view it on GitHub.


@asakusuma if there is no real usecase- other then compat, maybe we should warn that it will be removed?


oooh, default arguments.


:+1: awesome that you can change this for yourself!


Good question. We don't have a full writeup for Custom Auth yet, but the guidance for will be to turn on [App Service Authentication] (https://azure.microsoft.com/en-us/blog/announcing-app-service-authentication-authorization/) on your service. This will properly validate tokens sent via the X-ZUMO-AUTH header and set the Principal as Authenticated if they validate.

The inputs to your token generation need to match what App Service Auth expects, though. This means:
- The (secret) signing key needs to be read from the 'WEBSITE_AUTH_SIGNING_KEY' environment variable that is automatically set in your service.
- The Audience and Issuer need to match the url of the site, including the trailing slash.

App Service Authentication only works in the cloud, though, which is why we included the AppServiceAuthenticationMiddleware for local testing. This middleware can be used to locally test behavior that requires authentication.

Let us know what you think or if you bump into issues.


nice how this naturally fits into scala


Can we say that this byte is actually worthless, and remove it from the packet?  If you keep it should be specified that it should max out at 255 and not roll around. 255 meann it exceeded 255s


No transmit that I know of on their initial product due to FCC/FAA certification time constraints. I'll inquire regarding the website blurb about it. However, it will eventually be supported on this, or another vendor, so this msg needs to support it. Are you suggesting a change is needed to support that? If so, what?


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


Ugghhhh.. Geez Jeremy. Nevermind. You've beaten me down with your superior intellect and highfalutin argumentation style. I'll just keep my own fork or I'll decide if fmstandards will simply point to your authoritative designation for parameter passing.

Sure, you guys have invested a lot of time and effort, NOBODY disputes that, but I don't see you two as being the sole gatekeepers just because you wrote tests. I, along with everyone else who is using the code, is likely VERY appreciative of the time and effort invested.

I say again, NOBODY disputes the value of your discoveries about character bugs within FileMaker's Quote() implementation. However, if there is consensus among others on the list as to which "feature" is more useful, given that things don't break, then I'll go with that.

This is what I hate about communities which "attempt" to collaborate. A few people contribute things and then start to consider their contributions as paramount to the whole.

Hopefully, (or maybe not, as you'd likely argue) someday you'll realize that you don't have to prove things to yourself and other people by trying to sound so intelligent because you'll be comfortable with just knowing that you are.

Trust me, I have no intention of disturbing your "hackles" my friend. To respond...

> non-trivial inflection point

Really, that big huh? What makes it non-trivial? I must be having a hard time understanding.

> rebooted the functions from scratch

You did? I seem to remember they've evolved from a long line of smart people. Sure, you and Dan personally contributed a SIFNIFICANT amount. Nobody disputes that. I'm sure if there's a split about to happen many will continue to reference your fork because you're able to convey how yours is superior.

> You're asking us to release the ratchet

Nope, just asking you to be flexible and evolve something further. Besides, what's wrong with releasing the ratchet? What's the cost to you? A decrease in ego pride if something breaks or needs to be fixed?

> I'm not personally too fond of debating principles like these because it's too easy to interpret the same principle in favor of different positions.

Just like everything else in the world, anything can have opposing interpretations. Wow, even things considered sacred, like the Bible - go figure. Don't give me your "not too fond of debating", that's exactly what you're fond of. It's right here on this page.

> which is almost as rare a way to do things in FileMaker

Really, and how did you come to quantify this one? Do the developers you know and work with reflect all developers in the realm of FileMaker? As far as I'm aware, there are MANY different ways to do things and in the realm of FileMaker, this is even more so than other languages.

I'm sorry if this seems like a personal attack, I'm not attacking you as a person. I like the fact that we have someone so smart in the community of FileMaker. What I am attacking is how you respond to people and the intention behind that response. I'm not intimidated by your intellect. Jealous, yes. And always will be. But, only up to the point where it becomes painful to work towards solving problems.

Yes, I personally want this feature because of convenience. Do I want to create yet another # function just to deal with weakly formated Let input? No, because it doesn't make sense. #Assign is already decoding and is just fine doing a bit more to facilitate not having yet more Function ( WithinFunction ( WithinFunction ( ) ) ). Am I frustrated with this process?

I'm pretty sure you can infer that.


TeamCity pull requests :: netty [Build 739](https://garage.netty.io/teamcity/viewLog.html?buildId=3571&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5291, ignored: 21 Build time: 00:14:48


Good catch, thanks


I can amend the commit a bit later I was just clearing python indent warnings.


Agreed, will move the market maps into the Market class and reference from there.


We could do this as an `Either` as well, but I guess it doesn't really matter.


Sorry it's probably obvious, but why are you dropping this?


Root of the issue with Trie data structure is that it only checks node at first character in the string.

California, type 'c' and retrieves the state with typeahead (54 states). but typing 'l', 'i', 'for', 'li',... does not include California as a selective option or even nothing found.

In the current(Outdated) implementation of this stale Typeahead.js, the search does not result in matches for query of middle characters.


Yes, we want to avoid a so-called "side-channel" attack, where an attacker learns something about your password through non-standard means. I would expect the amount of time it takes `str.ljust` to execute to be dependent on the length of the original string. Instead, this generator expression should execute _exactly_ 1000 steps, regardless of input size.

Does that make sense?


Item is going to be a single item of clothing or accessory. An Outfit will be a collection of items. A WeatherCondition is a specific condition like "sunny", "rainy", or 52 degrees. Items will have many WeatherConditions and WeatherConditions will have many items, through the join table WeatherItems


Это в следующем задании, кстати, уже внедрено)


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


does `Array[Long]` not automatically get tagged as *w? I don't really know how scalabrad works.


typo @ networkas


yessssssß


Отлично!
Только теперь проект не компилится. :)


Could you mock up an ajax request here? It doesn't need to actually submit anywhere, but you'll need to deal with the submit request being asynchronous.


Not worthless, I'm just not doing anything with it right now in the initial driver. This tracks the last time the ADS-B receiver received the ADSB signal from the vehicle. Once received, the hardware will keep sending the vehicle info until it has some sort of internal timeout which I do not know. So, it tells you how stale the info is. The timer in APM is for the last time APM received the packet, which is every second. That does not tell us if the data is stale. Once a packet in the receiver becomes stale and drops off and is no longer sent. At that point the APM will time it out after 10 seconds and drop it off it's own list. That code could probably use some re-work.


Nothing else. -Jimmy

From: wcarthur1 [mailto:notifications@github.com]
Sent: Tuesday, November 24, 2015 12:17 PM
To: wcarthur1/TPM2.0-TSS
Cc: Wei, Gang
Subject: Re: [TPM2.0-TSS] Removed check for NULL sysContext in _Prepare. Moved this check into CommonPreparePrologue. (5da9e09)

Ok, I can remove that.

Any other issues?

Will Arthur
Intel Corporation
Server Security Firmware
803-216-2101

From: Gang(Jimmy) Wei [mailto:notifications@github.com]
Sent: Tuesday, November 24, 2015 11:07 AM
To: wcarthur1/TPM2.0-TSS <TPM2.0-TSS@noreply.github.com<mailto:TPM2.0-TSS@noreply.github.com>>
Cc: Arthur, Will C <will.c.arthur@intel.com<mailto:will.c.arthur@intel.com>>
Subject: Re: [TPM2.0-TSS] Removed check for NULL sysContext in _Prepare. Moved this check into CommonPreparePrologue. (5da9e09)

In InitSysContextFields()
SYS_CONTEXT->rval = TSS2_RC_SUCCESS;
SYS_CONTEXT->nextData = SYS_CONTEXT->tpmInBuffPtr; + SYS_CONTEXT->rval = TSS2_RC_SUCCESS;

Above is duplicated initialization to SYS_CONTEXT->rval.

—
Reply to this email directly or view it on GitHub<https://github.com/wcarthur1/TPM2.0-TSS/commit/5da9e09207226e34de86316b30262ef784caaa4c#commitcomment-14593124>.

—
Reply to this email directly or view it on GitHub<https://github.com/wcarthur1/TPM2.0-TSS/commit/5da9e09207226e34de86316b30262ef784caaa4c#commitcomment-14596800>.


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


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


2 Space Indentation in Ruby


ok


I suggest simply giving a warning message like "Tried to interpret value as a list, but failed".


the `10.minutes` thing makes me think of Ruby and I still don't think I like it but it sure does read nicely.


Yup! Good call.


In the future, let's do these updates as separate tickets. Also, I'm just thinking out loud here, but why should we store plugins in the repo? Could we just store the configuration needed for the jobs in git and use a regular jenkins download / install and overwrite the jobs and xlm configuration files?


Should add also:
```javascript
boolean none;
boolean active;
boolean slow;
boolean secure;
boolean explicitDiscoverable;
```
Are security/provisioning APIs also in scope JS spec v2?


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


well, that's _one_ way to make an array...


This cannot work because `cider-current-connection` returns a buffer and you can only propertize strings...


Ну не один, а 4, это управляет отображением "осталось заполнить - имя/отзыв", и сам блок вынимает из DOM, если и то, и другое заполнено.


Read Me file change


The common factor is that their user_id is null.


This is a way to tell the compiler that we need to know the actual class `T` that is being used in a particular call. The problem is that generic types are actually erased at runtime since the JVM does not have reified generics, but in this case we need to know the type `T` so that we can check whether the channel we look up is of the right type.

In java, you'd do this by passing the class explicitly:
```java
// method definition
T getChannel<T extends Channel>(Data data, Class<T> cls) { ... }

// when we call it, we provide the class
AnalogChannel ch = getChannel<AnalogChannel>(data, AnalogChannel.class)
```

Notice the repetition of AnalogChannel in the variable type, the generic type parameter, and the class parameter. It's kind of a pain. In scala obviously we can omit the variable type thanks to type inference, but it turns out that we can also omit the explicit class parameter, because the compiler can look up the class object _at compile time_ for a given generic type parameter.

The way this works is we actually declare an _implicit_ parameter that carries the class information, and then the compiler can create and supply that parameter. Of course, this has to happen at compile time because at runtime it'd be too late: the types have already been erased.

So, in scala we can write:
```scala
def getChannel[T <: Channel](data: Data)(implicit cls: ClassTag[T]): T = { ... }

// now, when we call the compiler fills in the cls parameter
val ch = getChannel[AnalogChannel](data)
```

This pattern of having an extra implicit argument that is specialized based on a generic type parameter turns out to be pretty common and useful in scala, so there's some syntactic sugar for it. adding `T: Foo` to a generic type parameter `T` is exactly equivalent to adding an implicit parameter `Foo[T]` to the method definition:

```scala
// the following are equivalent
def getChannel[T <: Channel](data: Data)(implicit cls: ClassTag[T]): T = {...}
def getChannel[T <: Channel : ClassTag](data: Data): T = {...}
```
In scala parlance, this is called a "context bound" on the type `T`. It's just a different kind of restriction on what types can be passed to a generic method. Just as `T <: Channel` is a bound that says `T` must be a subtype of `Channel`, so `T : ClassTag` is a bound that says there must be in instance of `ClassTag[T]` available in the implicit context at the call site.

As it turns out, `ClassTag` is a bit special because the compiler actually synthesizes them for you so there's always one available, provided you tell the compiler which type you mean, e.g. by calling `getChannel[AnalogChannel](data)` with a specific type `AnalogChannel` given for `T`.


So this should not be part of the patch?


Yep, but also want to get rid of redundant checks so that reading code is easier. So lets get rid of this check.


Hi @RobertCNelson ,

All installed and early indication is that it has solved the overruns issue, lets see if it still hangs!  I am in the UK so will leave running overnight and see what it is like in the morning and report back.

Will this only work with the dtb you supplied or would I be able to revert back to the cape overlay.  I only ask as ideally I would want the HDMI disabled and I know that config was working well!


$this->hotbarSlot?


This is still using the wrong Logger.


@zehortigoza what's the use case?  Until now we didn't need it, mostly because we go through DigitalSource that does the export for us.

That's one of the discussions we were having some weeks ago: when using gpio_sysfs, in order to let `hal.gpio->` path be as fast as the DigitalSource one we actually don't need to expose the `export_pins()`... we need to have a cache of file descriptors with the same size as the gpio array.. then we do everything needed to export/open the gpio when it's first used.  I'd argue the `/value` file is the only one worth caching, but @tridge raised a question that setting the direction should be fast, too.


Javascript Form Validation is used to make sites dynamic! Always validate with PHP/server-side for Security.


This will create the pan gesture recogniser, whether it is needed or not. Why not use an on-demand property initialiser which will be called whenever you use `self.panGestureRecognizer`:

    (UIPanGestureRecognizer *)panGestureRecognizer {
        if (!_panGestureRecognizer) {
            _panGestureRecognizer = [[UIPanGestureRecognizer alloc] initWithTarget:self action:@selector(panGestureRecognized:)];
            _panGestureRecognizer.delegate = self;
        }
        return _panGestureRecognizer;
    }

To remove it again, you'd call `self.panGestureReconizer = nil;`


słabo tutaj


i tu też


the backtick stuff is super cool but it always takes me like 3 tries to get it right.


Check: https://github.com/tmux-plugins/tmux-resurrect


dsadsadsa


Класс создает игру.


pfffff


aaaa


I honestly had no problem understanding that post without the quote. He even replied "gist up?" to give context about what he was asking about.

I am willing to change it if we could get some more examples. It would probably be better to bring this up on meta.discourse.org -- I imagine very few people have seen  this discussion here.


That's true. I was a little inconsistent here. I have some further changes queued up to more fully rely on scala types.


Automatic backup function...don't want to confuse backups with our snapshot UI feature


:+1: качественно!


This will not do for non-EN.
Please take a look at https://github.com/Wikia/app/blob/dev/extensions/wikia/PortableInfobox/services/Helpers/ImageFilenameSanitizer.php#L31-L50


Yes, `Array[Long]` would also work in this case.


no. It's not a hard limit... not breaking the string (unless it's way too long) is preferred.


Is that parser-state-safe ?


@yurem : Is this change with the one issue i raised for version 2.3.3 with GA Dev server upgradation?

i.e.
"metric":"ou=metric,o=%(inumOrg)s,o=gluu"


Woo hoo... great to see the project in GitHub... and multiple follow-up commits too!


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


they're -> their
hapily -> happily


Just returning `Array[Array[Array[Double]]]` would be best; I just need to make sure scalabrad deals with that properly.


Thx for your PR, but we working on a fix for Python 3, that will probably fix your issue, we will deploy it this week, possibly tomorrow


This collection could be used for more than just rule names; conceptually this is just a way of doing string interning on a per-scene basis.


Change only the other ones then ;-).  But the other ones here would be very few...


so much nicer


Absolutely.  I am currently traveling to Memphis for Thanksgiving so I will
have to get on this either tonight or in the morning.  I will shoot you a
message when I have it done.  Thanks.

On Tue, Nov 24, 2015 at 1:22 PM, Nathanael <notifications@github.com> wrote:

> Could you mock up an ajax request here? It doesn't need to actually submit
> anywhere, but you'll need to deal with the submit request being
> asynchronous.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Capocaccia/rocketFuel/commit/246beaa99d515a37388fecdb22bb982338609ddc#commitcomment-14598092>
> .
>


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


"Chupa-cabra é uma suposta criatura responsável por ataques sistemáticos a animais rurais em regiões da América, como Porto Rico, Flórida, Nicarágua, Chile, México e Brasil."
Essa frase não se encontra no original.


lol


Would it be more clear to use a guard and write:
```
case Message(src, ctx, msg, data) if msg == wiringMsg =>
```
?


Pra ficar consistente com o restante das traduções, usa "Chupacabra Cinza Enorme".


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


TeamCity LabKey :: LabkeyRelease15.3 :: Git postgres 9.4 [Build 94](https://teamcity.labkey.org/viewLog.html?buildId=287323&buildTypeId=LabkeyRelease153_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 11 (6 new), passed: 275 Build time: 01:38:13
### Failed tests
```
org.labkey.test.tests.CDSTest.testLearnAboutStudyProducts: <no details avaliable>

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

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

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

org.labkey.test.Runner: org.labkey.test.util.JUnitHeader: <no details avaliable>

org.labkey.test.util.JUnitFooter.afterJUnit: <no details avaliable>

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

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

org.labkey.test.tests.CDSMeasureStoreTest.testDemoMeasureStore: <no details avaliable>

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

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

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


@SirCmpwn Unfortunately, the chunk mesh being rendered _before_ lighting is updated would only mean lighting updates lag behind by 1 block change, not that it would fail to update completely. I've tried rearranging code and whatnot, to no avail.


Would there be a performance difference for the solvers we support? That's really the only concern I can think of


oops ;-P


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


you missed the $incrementing option which leads to problems on polymorph-many-to-many relations


Yes, but we can change this if you think there is a better place under the same encryption root. One option is making an exception for things under `/user/`.


По заданию требовались беззнаковые двухбайтовые (16-битные) числа.


removed other files apart from php.json


This is more of an information message. So should go to stdout instead of stderr?


fix in 92941bc


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


had not seen the `_*` before. cool.


The `incrementing` option is missing at the models standard properties


Given that we now have the capability to figure out which devices we had partitioned already, I think we can simply error out instead of skipping the device. So if user adds a device which is partitioned and not part of volume group, it is an error.


nice catch, fix in 4d3b3fa368850275f5a4183742bc99fe520e8d36


Lines #73, #80, #585~#616 can be removed again, do an amend.

https://github.com/AOSP-JF-MM/platform_frameworks_opt_telephony/commit/a957be4a6d910393fd15797697a27776f5f5226f
https://github.com/AOSP-JF-MM/platform_frameworks_opt_telephony/commit/9e64586fc3bb27af15758d5b25f9f2bba61f9ad1


I think both ECOS and SCS translate variable cones to linear constraints anyway.


[Flags]


there is typo in "def**ua**lt", should be "default"


Shouldn't '-1' be considered invalid as that index would never exist?


I agree with @lptr : having a way to declare such methods directly in a managed type has a big advantage: it will make user "extensions" consistent: one of the issues today is that everybody invents his own DSL for Gradle. With the ability to generate such methods in a "standard"/"supported" way will help users because they will see the same pattern everywhere.


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

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


uncomment it.


look good, do you have an other classes...


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


Why are we returning an error here? I think we can call this function only if there are some disks which require partitioning and get rid of this check completely.


У метода должно быть только 2 первых параметра


good job....I can not add any of my stuff because it is already completed and you  did just as good or better then I did....I deleted my copy and will use your copy....good job again........


The [API documentation](http://apidocs.cloudfoundry.org/225/apps/terminate_the_running_app_instance_at_the_given_index.html) makes no statements about valid values for `index`, therefore there is nothing for us to enforce.


app.getContactHelper().modifyContact(index, contact); - так должно быть


in java it's a good practise to put the { }


localization. change ru.xaml and cn.xaml as well. You can just copy the content from en.xaml, but you need make sure the keys are existed.


same above.


Looking at this slide it looks like we could create a ADSB MAVLink packet that can accommodate all the ADSB packet types. Would that not make sense to have a 56-bit ADS-B payload? The current proposal only support Airborne Velocity.
![adsb-modes-squitter](https://cloud.githubusercontent.com/assets/959994/11378564/b4289154-92a0-11e5-86dd-fd3fdf7a7be7.png)


@scuy Um bestehendes Verhalten in arachnefrontend nicht zu brechen und weil mir die Lösung auch so ganz gut gefiel, habe ich mich dazu entschieden, hier den extra param showContactInfo einzufügen, den man auf false setzt, wenn die contact info nicht gezeigt werden soll, z.B. weil es sich um einen Fehler handelt, den der User selbst beheben kann.


nice point


What exactly does this do? Has the server run on the same thread as the connection? I never really grokked executioncontexts. And do we have cxn as a global?


Пожалуйста, используйте *Format use AStyle* перед commit-ами.


Forgot to mention: Movement, animation and jumping are handled by base Actor. Need to eventually supply more interfaces and restructure variables.


1. you should use `result` and handle errors. e.g. display error message by MessageBox.
2. Why you show a `MessageBox` and set `SHERB_NOCONFIRMATION | RecycleFlag.SHERB_NOPROGRESSUI`. `MessageBox` is redundant if you remove these enum.


I think there is no way to reduce the fragment because both `MMWormholeSession` and `MMWormhole` classes import the rest of the headers in their `.h` public interfaces.


I would like it to be a small percentage because as we get many threads the chance of one or a small fraction of them searching an odd line goes up significantly.  This is for the same reason normal easy move stopped working on the TCEC machine when we had all threads resetting it.
https://github.com/official-stockfish/Stockfish/pull/458
We should however test the 90% actually works and the current test doesn't do that as you correctly point out.  If it passes I'll ask the maintainers what extra test they recommend.  Thanks!


Finally @AndroGeek974, it f***ing worked. Just don't ask me how much coffee it takes to write 160 lines of code at 1:00 in the night


I wanted to avoid some code duplication. the `clone()` method calls the `_setup_callback_methods()` which references
the `clone()` method. The `new()` and `clone()` methods are very similar, if you have an idea how to make use of this I'm open to suggestions.


Map


Does this retain set semantics? I.e. it won't let you conj in a dupe medium?


LGTM


@Stacy-D, еммм. а для чого кнопка, до якої доданий "слухач"? чому не просто посилання?


optString


please add comment that this item is valid for google tests only


@valib this looks good. Do you know when they added this? Is it in the versions of FFmpeg we use on OS X and Linux?


so, do we have to depend on a beta version of JSON.NET going forward?


@Optimusprimeums those speeds sound nice! Thanks for the builds :)


This fixes issue #5


I think, there should be v3.3.5. :+1:


This code was copying baseConfig and baseDevices into config and devices, so basically moving the expanded config into the container-local config, which is wrong.


Isn't this autocorrection wrong? Shouldn't the first `next` be indented at the same level as the second `loop`, and the second `next` at the same level as `something`?


Oops, fixing.


spaghetti code


Why are we adding above two lines?


I think "replaces" can be a bit confusing as the old syntax still works.


yes, that the name doesn't quite capture the meaning.


Эта функция печатает не байт, а двухбайтовое целое беззнаковое число. Оно состоит из двух байт, но может быть представлено в little-endian (с обратным порядком байт), как мы обсуждали на занятии. См. комментарий ниже, к чему это приводит.


Hi,
This plugin will be updated for next Gephi 0.9.
See https://gephi.wordpress.com/2015/11/02/announcing-gephi-0-9-release-date


@lucasdemarchi I got this problem when I was running some tests using GPIOTest, but this problem could happen right now on 17 places outside of Linux specific code, so I still think that it should be transparent to user.
About the fd cache, I can sent the commits but which ones? GPIO value fd,  DigitalSource direction fd and GPIO direction fd.


мені здалось, що там в докі як кнопка воно виглядає. Або потім, коли буде виглядати як полиця, то там буде обложка книги, а внизу кнопочка. Не так?


@fowlslegs [git-revert](https://git-scm.com/docs/git-revert)


i removed it cause the makefiles compile in 64bits only so it won't work anyway. we could have a template with glut for people who want to use it for compatibility reasons


Fixes issue #9


okay. I'll do some more _deep_ thinking to come up with a bettter one. suggestions welcome though


Yes, it always was strange that there was a blank run setting added and then mutated later.


помоему ты забыл закоммитить pom.xml
У меня не компилится твой проект


@Stacy-D, завжди можна накласти стилі і з будь чого зробити кнопку)


Minor style nit. Following might be little easier to read.

if [ -n "$P" ]; then
  create_disk_partitions "$P"
  create_extend_volume_group
fi


зробити посиланням, чи так залишити?


This is meant to prevent writing a date to the response stream while we're in the middle of updating it.


So for the type alias, you don't need to annotate it with `@Accept`. Does scalabrad automatically understand `Either`?


we can get rid of `ModelRegistryStore` as well.


Shouldn't this be logged at WARNING or ERROR?


Is font-lock-face really the right property here? For messages I usually use face.


I think there is now way to reduce this fragment because both `MMWormhole` and `MMWormholeSession` import the rest of the headers in their public interface.


Функция печатает не байты области памяти, а `uint16_t`, расположенные в ней. Поскольку младший байт расположен первым в памяти, каждая пара байт области памяти будет напечатана в обратном порядке. Например, если в памяти содержится `"ABC"`, то есть байты `41 42 43 00`, они будут рассмотрены функцией как `41 42` и `43 00`, то есть числа 0x4241 и 0x43, и будет напечатано `42 41 00 43`, что неправильно.


Свойства класса уже инициализированы, повторно этого делать не нужно.


It's safe to use float64 here. I utilized float to parse things like 1.5d (one day and half), 0.5h (30 mins), etc.


@SthephanShinkufag вроде удалось починить постинг на тинибоардах. Алсо, может и 420chan проверишь и вернёшь класс назад, если работает. Антибот срабатывал из-за разницы в виде поля файл (раньше скрипт отправлял его как простое поле, а теперь как поле с пустым файлом).
Было:
```
Content-Disposition: form-data; name="file"

-----------------------------6791168625768
```
Стало:
```
Content-Disposition: form-data; name="file"; filename=""
Content-Type: application/octet-stream

-----------------------------6791168625768
```


`cxn` is a member of the `Server` class, so that's why it's accessible here.

An `ExecutionContext` is just a thing that can execute code. It has one method we care about: `def execute(runnable: Runnable): Unit` that takes a runnable and runs it. In practice, this is usually a thread pool.

If you look at the methods on scala's [`Future`](http://www.scala-lang.org/api/current/#scala.concurrent.Future) for adding callbacks, like the `map` method, they generally take an implicit `ExecutionContext` as an extra context. What this means is that whenever we add a callback, we need to also have an `ExecutionContext` around that can actually run that callback, when the time comes. This gives us very fine-grained control over where code runs and how we manage resources like threads. Contrast this with twisted where there is one global, single-threaded reactor that runs all callbacks and so there is no need (and indeed no way) to specify where our callbacks should execute.

So, we need to have an implicit `ExecutionContext` in scope to run callbacks in response to requests like loading the wiring info. The idea here is that we're just reusing the thread pool that the `Connection` class uses for doing its networking business.


В исправленной версии этого не будет (см. комментарий ниже), но здесь не 16. Проверьте себя.


Кстати, зачем это нужно?


Minor nit. Should we call it "needs_partitioning" instead.


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


I believe it has been common practice to allow implicit dependencies to exist if they are met by other packages in the table file: e.g. pipe_base is setup by pipe_tasks.  This seems like a reasonable thing.  Are you suggesting that we should go through all our packages and fill out implicit dependencies or are obs_* packages special in this regard?


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


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


what about the ```cli``` option? It also needs to be sent forward.


Why did you remove the sort?


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


Not sure I get this test with the comments, it should be does higher idx lose elo even with same completed depth


newaddr should be in c0e7f14c6fd2572070b69714ba85cdfd52363268


is there a simpler way to detect iterator completion? (i.e. w/out stored flag)


Looks good to me


是的，这是一种比较简单（hack）的方式，在Chrome版本升级后（我也忘记是从什么版本升上去的了...），就发生了这个问题。
理论上这块也是个Bug，因为date.getFullYear()返回是Number类型，但在一些低版本的Chrome中没有问题。估计是JS引擎升级后，对这些地方进行的严格检测。


@jschall, Tridge told me this was added for solo and maybe the matrix is correct, but the description is wrong. Could you take a look?


prevent flag enums from getting out of sync


Nice work you've done here Predz!

There were some improvements to be made to the style of your code, just read the PEP8 and PEP257 a few more times if you want to understand the recommended style better. I believe the code is just a little cleaner and prettier now, but feel free to counter argument if any of my changes look silly! I already pushed https://github.com/Warcraft-GO-Team/Warcraft-GO/commit/f246885b375536845573d0754f34fe5d701b7024 regarding the style of the code. Notice that a folder with `__init__` is a package, while single files are modules. All of the docstring changes I've made are up for debate.

Also, while the style doesn't matter too much and is something that everyone will slowly improve at, there was one bug which actually *needed* a fix: https://github.com/Warcraft-GO-Team/Warcraft-GO/commit/4ec132eed2b481aa3d353cf999d0a307bc650e5b. You were shadowing the parameter `menu` with your `menu = choice.value` assignment, thus when you assigned the previous menu

    menu.previous_menu = menu

You were assigning the new menu's (`menu = choice.value`) previous menu to *itself*. I bevieve this wasn't the behaviour you were looking for, so that should be fixed now.

Other than that, thank you very much, nice job and keep the commits coming! :)


a[href*="twitter.com"]::before I use this myself.


Shouldn't these be ints to improve accuracy


Deixar esses arquivos do project.properties e project.xml interferem no meu repositório quando tento fazer o login, é mesmo necessário incluir esses arquivos nos commits? :/


org version triggers (correct) warning under gcc


I get ```undefined method `coupon?' for #<OpCart::Order:0x007fdb7c65be40>```


```csharp
where y != x
```


Or should this method be:
````java
@Override
protected void newObserver(Consumer<? super T> observer) {
    if (latestEvent == null) {
        observer.accept(initial);
    }
}
````


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


Good suggestion Mic92; I'll check rubocop's documentation and look for this option!


![It's the end of an era!](https://s-media-cache-ak0.pinimg.com/originals/20/04/0e/20040e0751b86ddb1bbcbfea63f0ed08.gif)


@Mumfrey I think this was intended to be `A collection of {@linkplain IMixinLaunchAgent launch agents}` instead.


Pipes work the other way around. The writer closes the writable end of the pipe, which will cause EOF on the readable end.


New-Fan-Object (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (894 of 894 tests passed)

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


And writing to a pipe whose readable end is closed yields SIGPIPE.


103643052-FiniteDifferenceFluxOutput (mjwitte) - x86_64-MacOS-10.9-clang: OK (1957 of 1966 tests passed)

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


i know this is annoying but you're probably going to have to update the migration in the previous commits. if you were to run `makemigrations` it'd generate another migration that changes the max length back. ideally we'd be in a state where `makemigrations` never generates new migrations unless something has changed


왜 path를 제한하나요? 권한 체크를 workspace 단위로만 하겠다는 뜻인가요?


i think the correct thing here is to actually keep the try catch and remove the `callback` call that was before the `try`. (the diff between this and master should show nothing


@philborman

http://pastebin.com/QwGChGBG

i dont know why but when lazy snatch a magazine i have 25 same download in sab ... strange ?


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


Won't this have the exact opposite of the intended effect?  If this is the problem you want to describe, then you'd have to change my description of the problem above too to match.  What I described was `control indicators are NOT pushing all the way to the extremes as it does so`.  Indicating that it's altering its angular velocity much slower than it should be.  Your solution sounds like its for a different problem than what I described.


oops!
It's my mistake.


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


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


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


@geoffmcl Unfortunately I don't have a simple test case to catch it.
Someone found it while browsing a page on Linux with edbrowse, which
crashes on account of corrupted memory.
I ran the same page through the tidy command-line tool under valgrind on
Linux.  The tidy tool didn't crash, but I could see in valgrind that it was
doing out-of-bounds writes and reads.
It was pretty easy to isolate.

My test page is:
https://www.indiegogo.com/projects/translation-of-the-book-play-to-live-volume-6


coomentario


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


Test comment! :leaves:


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


Because you probably have things in your local Maple archive which isn't
in the archive that's on the server.  At least, that would be my first
guess.

On 2015-11-23 8:27 PM, zaxtax wrote:
>
> So why are things failing? I find the error from TestHakaru when run
> through System.MapleSSH particularly perplexing.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/hakaru-dev/hakaru/commit/cc9623d89aaf751db8b0ab1410bb8c31a067d813#commitcomment-14576754>.
>


Qual a razão disso?


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


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


comentario 2


In order to verify your steps, I upgraded [Bubble Actions to the most recent version of the build tools](https://github.com/SamThompson/BubbleActions/pull/2). I ran into the same issue where it suggested I include the code here, but when I added the "platform-tools" and "tools" components to my `.travis.yml` the issue went away. I also tested locally, but didn't get lint errors, so it must be something on Travis CI's side.


ok this is wrong, should be  f (!string.IsNullOrEmpty(Project)) ...


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


s/doen/done, :)


request was taken away here...


requires ws (npm install ws) and serialport (npm install serialport)


This sounds like it's describing behavior exactly the opposite of what I thought PITCHTS and YAWTS do.  You are describing it as higher values = gentler use of controls, but if it was analogous to the meaning of MAXSTOPPINGTIME as I thought, then it would be that higher values = allowing more vigorous use of controls.  (That a value of 1 means don't allow an angular accelleration to achieve a value high enough to take more than 1 second to undo, and 2 means don't allow it to be big enough to take more than 2 seconds to undo, and so on.)


yeah I added those in a separate commit


@mmason16 yeah. Add flex hours. Mark what days they happened.


Fair enough


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


The comment can be changed to "# The following attributes are deprecated and will be removed in 2.2."


Nicely done, thank you.


It seems that we have fake_runtime.go? Why do we add a mock? :)


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


I guess it can't work that way, can it - since angular accelleration is immediate and reacts right away proportionally to control input deflection amount.  There's no such thing as taking time to slowly change angular accelleration - you can go instantly from -1.0 to +1.0 on the controls if you want.  So I guess yeah it can't work like I thought.

Might want to check everywhere else I said something about PITCHTS or YAWTS and make sure I didn't get it wrong anywhere else.


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


très triste @AbhinavMadahar


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


TeamCity LabKey :: LabkeyRelease15.3 :: CDS postgres 9.4 [Build 55](https://teamcity.labkey.org/viewLog.html?buildId=287196&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 12, passed: 35 Build time: 01:14:11
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyDensePlotBrushing: <no details avaliable>

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

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

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

org.labkey.test.tests.CDSLoginTest.testSessionTimeoutIntercept: <no details avaliable>

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

org.labkey.test.tests.CDSMeasureStoreTest.testDemoMeasureStore: <no details avaliable>

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

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

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

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

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


Done and force-pushed


kkkkkkkkkkkkkkkkkkkk


lllllllllllllll


something that will take the duration of the universe on my laptop


Fixes #70.


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


Our YAML requirements format doesn't support this yet. We will have to change the requirements schema to accommodate this.


Bit of a gotcha, but all of the services are ProperCase, to distinguish them from other things (ie, locals) upon being injected.


allSymbolReferences.AddRange(proposedReferences.Take(MaxResults - allSymbolReferences.Count))?


This commit is not on any branch.  You will need to fetch it by ID: **git fetch origin 2a428d88e49e452dfa3b22cda7568de580e93b19**.


In this file you can specify which files will be ignored by git and never added to the repository.


I was leary of doing that without being able to test it, but I found a few files that have those strings present, so I've added it in.


Grade for the Relaxr project: 16/16. Nice!


Yes. :) fixed it
https://github.com/okcscott/op_cart/commit/a9a75042e8a7ba7bd79a28fdc01babc25e14c364#diff-7b723b3ed321ea2a47779377a6755790R29


This defer will be called in the end of RunInNewTxn function or in dropTableIndex function?


Предыдущий коммит сломал подобный код:
```js
var p = new CancelablePromise(r => r(0));
p.then(a => console.log(a));
p.then(a => console.log(a)); // вываливался с ошибкой
```
В кукле такого нет, но мало ли.


That's right.  Think of settling time as the amount of time it takes the PID curve to settle to nearly flat.  So larger values of time mean a weaker response, which takes longer to smooth out but is generally a little more gentle
hich takes longer to smooth out but is generally a little more gentle.  I'll go through and double check again, but it looks like you were generic enough that you didn't say anything incorrect.  It looks like my documentation sections are the only ones that specifically mention the concept of "settling time"


Can this whole section be ProjectId-based instead of Project-based?


"Viable" is a weird word for this. Maybe "legal" or "possible" or "potential" or "GetReferenceableProjects" or something?


It's wired. I test this code on my 64 bit machine

#include <iostream>
using namespace std;
int main()
{
    const int i=5;
    cout<<"size = "<<sizeof(i)<<endl;
}

the output is:
size = 4

so no matter it's 32 bits or 64 bits.
it always 4 bytes.


I literally solved the whole thing while you changed all of it


基于类的视图


Here's the fix for the array serialization.  hasOrleansSerialization is called for elements of an array prior to attempting to serialize.


Dont you guys have the improved action button stuff?


What's the difference between runtime_mock and fake_runtime? :)


thx!


comentario 3


测试类继承自django.test.TestCase
测试方法必须以 test开头


I believe returning is fine...


this fixes https://alticast.atlassian.net/browse/TWCIPGW-277


@yaotung Huh? How is that related to this commit? :confused:


For version < 12, I cannot upgrade the database successfully...


resolve should be mfa (module, function, args) so the resolvers survive code reloading, i.e.: `resolve: {TestSchema, :greeting}`. You could also support appending the user's own args (in addition to the context passed in

 ```elixir
resolve: {TestSchema, :greeting, ["admin"]}`
...
def greeting([name: name], "admin")...
```


You don't need to do this, since the loggers print to System.out and System.err anyway..

Please test it before you remove it. >.>


Correct: version < 12


extra space before `type`


there is already an option to server files


It was throwing exceptions when I tested it so figured it was safe to remove it anyways.


adding a route just to trigger the graphql handler (and never call the controller action) need a different approach. `get` and friends actually accept any plug, so you should be able to do:

```elixir
    scope "/api", HelloGraphql do
      pipe_through :api
      get "/", GraphQL.Plug.GraphQLEndpoint, TestSchema.schema
    end
```


It's a pythonic case statement.  Actually, I just read about it in the little book @timj sent around ("How to make mistakes in python", p24), where they call it the "Strategy pattern":

> We start by extracting the contents of our if/elif/else structure into separate functions with identical interfaces. Then we can create a dictionary to map conditions to those strategy functions. The dictionary key doesn’t have to be a string. It can be anything hashable, so tuples and frozensets can be quite effective if we need richer conditions. Finally, our original function determines which key to use, plucks the appropriate strategy function from our dictionary, and invokes it.


fixes https://alticast.atlassian.net/browse/TWCIPGW-311


- [ ] No problem. However using diamond type(`<>`) is better. (overall)


So by the end the only things left are completely unrelated projects and things referenced strictly transitively. Is it always safe to reference these projects? Are there other conditions we should check for here (referenced assembly versions or something)?


one of my first R lines :) https://github.com/robertzk/microserver/pull/6


rename to `getSortedPublicPropNames`, I would guess it does filtering at call site.


Oh cool.  I missed that. :(


i think we can get rid of these


TeamCity pull requests :: netty [Build 740](https://garage.netty.io/teamcity/viewLog.html?buildId=3572&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5291, ignored: 21 Build time: 00:16:00


or given we are already in function create_disk_partitions(), we could simply call it "devs"


Wouldn't it be nicer to have an assembly on its own for C# rather than polluting the F# code with C#-isms?


we decided to completely remove this


I haven't commented so far because I haven't felt like there was much I
could add to the discussion -- at the moment, I've avoided using #Let
notation because of the use of `Evaluate()`, but I've certainly adopted
some of the inner workings (such as datatype detection) to use in my own
code.

The challenge seems to be less about whether /this specific/ change should
be incorporated into the main branch, and more about /how the community
decides what is important to include/ in the main branch. I know I
certainly couldn't point at the "Mission Statement" or intended audience
for `#Assign()`. Does anyone have experience working on other open source
projects that might provide some insight in that area?

Personally, if we're considering new FM developers as a key audience for
#Assign, I think it would be more beneficial to make `#Assign()` tolerate
weakly-delimited lists (i.e., no semicolon) than to have it auto-convert
carriage returns to spaces. The former seems like an error that a new
developer is likely to encounter if they are building their dictionary
without `#()` (for whatever reason) or trying to convert their data from
some other source (e.g., using `Substitute()` on something, or a rough PHP
script). The latter seems like it would require a fairly sophisticated
understanding of the `#()`-functions family to both comprehend and take
advantage of.

Separately, I wonder if it might be useful to adopt some kind of built-in
"pre-operation" and "post-operation" hooks (e.g., a
`userdefined_pre#Assign()` custom function) that community developers could
easily customize in their own solutions. While that wouldn't solve every
issue, it might at least make it more extensible without needing to nest
functions as Matt described in his last post, while also making it no
harder to update #-family CFs to keep up with the latest core release.

Just my $0.02. I'm interested to hear what others think.

~ Cristos

On Tue, Nov 24, 2015 at 2:17 PM Matt Petrowsky <notifications@github.com>
wrote:

> Ugghhhh.. Geez Jeremy. Nevermind. You've beaten me down with your superior
> intellect and highfalutin argumentation style. I'll just keep my own fork
> or I'll decide if fmstandards will simply point to your authoritative
> designation for parameter passing.
>
> Sure, you guys have invested a lot of time and effort, NOBODY disputes
> that, but I don't see you two as being the sole gatekeepers just because
> you wrote tests. I, along with everyone else who is using the code, is
> likely VERY appreciative of the time and effort invested.
>
> I say again, NOBODY disputes the value of your discoveries about character
> bugs within FileMaker's Quote() implementation. However, if there is
> consensus among others on the list as to which "feature" is more useful,
> given that things don't break, then I'll go with that.
>
> This is what I hate about communities which "attempt" to collaborate. A
> few people contribute things and then start to consider their contributions
> as paramount to the whole.
>
> Hopefully, (or maybe not, as you'd likely argue) someday you'll realize
> that you don't have to prove things to yourself and other people by trying
> to sound so intelligent because you'll be comfortable with just knowing
> that you are.
>
> Trust me, I have no intention of disturbing your "hackles" my friend. To
> respond...
>
> non-trivial inflection point
>
> Really, that big huh? What makes it non-trivial? I must be having a hard
> time understanding.
>
> rebooted the functions from scratch
>
> You did? I seem to remember they've evolved from a long line of smart
> people. Sure, you and Dan personally contributed a SIFNIFICANT amount.
> Nobody disputes that. I'm sure if there's a split about to happen many will
> continue to reference your fork because you're able to convey how yours is
> superior.
>
> You're asking us to release the ratchet
>
> Nope, just asking you to be flexible and evolve something further.
> Besides, what's wrong with releasing the ratchet? What's the cost to you? A
> decrease in ego pride if something breaks or needs to be fixed?
>
> I'm not personally too fond of debating principles like these because it's
> too easy to interpret the same principle in favor of different positions.
>
> Just like everything else in the world, anything can have opposing
> interpretations. Wow, even things considered sacred, like the Bible - go
> figure. Don't give me your "not too fond of debating", that's exactly what
> you're fond of. It's right here on this page.
>
> which is almost as rare a way to do things in FileMaker
>
> Really, and how did you come to quantify this one? Do the developers you
> know and work with reflect all developers in the realm of FileMaker? As far
> as I'm aware, there are MANY different ways to do things and in the realm
> of FileMaker, this is even more so than other languages.
>
> I'm sorry if this seems like a personal attack, I'm not attacking you as a
> person. I like the fact that we have someone so smart in the community of
> FileMaker. What I am attacking is how you respond to people and the
> intention behind that response. I'm not intimidated by your intellect.
> Jealous, yes. And always will be. But, only up to the point where it
> becomes painful to work towards solving problems.
>
> Yes, I personally want this feature because of convenience. Do I want to
> create yet another # function just to deal with weakly formated Let input?
> No, because it doesn't make sense. #Assign is already decoding and is just
> fine doing a bit more to facilitate not having yet more Function (
> WithinFunction ( WithinFunction ( ) ) ). Am I frustrated with this process?
>
> I'm pretty sure you can infer that.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/petrowsky/fmpstandards/commit/c97df1ca905f4c18c424caab613c46cd9b439525#commitcomment-14597969>
> .
>


Это для починки работы тинибоардов с выключенными скриптам на странице. Приятно, что после переделки капчекода куча борд стало работать с куклой с выключенными бордовскими скриптами. Теперь тинибоард тоже.


We could do this check before querying volume group for PVS. If we have a partition device name in DEVS, we can error out early.


This commit breaks the working IBAN sample from here: http://codepen.io/mkr/pen/jEmgeP on Android 4.4.4 (and others I don't recall exactly right now). The behaviour is that the caret jumps in front of the character that has just been written.


Пришлось заглядывать в код, чтобы понять: будет напечатан не начальный, не первый (first), а второй элемент!


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


Коммиттин аты кыйынго? %)


Yeah disabling by default sounds like a better way to alias it actually. A
couple aliases for php and phpunit with xdebug on sounds good then. If
someone wants to do a write up and PR the xdebug troubleshooting docs that
would be great.


minor nit. Can we use a name say "current_devices" instead of "partitioned". Little easier to understand in the context.


I wonder why you're looking at this code. Actually, why?


Wow, nice explanation, thanks. I read a bit on the consequences of type erasure but didn't get to any workarounds like this.


Broad phase


I think we should do like Hopac does as well, and have `Suave.Operators` alias in all the submodule operators, such as this one. Or even have the same in `Suave` plain and simple?


What I mean is can we drop the `Return` annotation altogether?


I think we should add "secure" to the ConnectionMode. We need to check the use cases for the rest (vs the OIC Core spec).


can you add this back, with the tooling api enabled (and no reuse of course)


No, this is idiomatic Scala (I gather) and when I see it I remember how it works, it's just that I seem to get scoping issues when I try to write it myself.


add this scenario back with tooling api and no reuse.


decied to remove the generic code of stratefy operations (struct of pointers to functions)

maybe meanwhile consider #ifdef 0


and here


Yeah it was scaffolded. I mentioned it to you on Tuesday I believe, I never new it existed because we didn't go over it in class. Didn't realize it was frowned upon since we had been doing all that stuff the week before, I figured it was just a faster way to get it done, whoops!

Yeah the migrations I did because I wanted to make sure I was doing the best practices, I definitely thought about modifying the migrations though.

I'm also kind of disappointed in myself with this project. I know I'm capable of a lot more. I got really hung up trying to integrate my PC with github and using both windows and mac. That turned out to be a nightmare really quick but I figured it out eventually so now I have it for future projects at least!

I'm glad were in javascript now again though. I feel a lot more comfortable, I was able to get through all the extra exercises in class today. I finished the assigned ones fast enough to move onto the others even when we didn't get time in class to do them, so I'm feeling really good about that.


Yes, scalabrad understands `Either` and can even deal with things like nested `Either`s if you have more than two possibilities. Of course, I think this is not the best way to define our interfaces, and it'd be nice if we keep this kind of thing to a minimum. In this particular case, I have martinisgroup/pyle#775 open to specify these channels always as `(String, String)` when calling, and then all this server code can get simplified considerably.


Ça marche toujours pas même en déplaçant, en changeant la ligne, avec la version 3.0.

De : Zangetsu38 [mailto:notifications@github.com]
Envoyé : mardi 24 novembre 2015 01:31
À : Zangetsu38/rpcs3 <rpcs3@noreply.github.com>
Cc : vlj <vljn.ovi@gmail.com>
Objet : Re: [rpcs3] Hack (6d4d0a4)

@vlj <https://github.com/vlj>  oublies pas apres avoir installer la maj de tout déplacer comme l'autre

—
Reply to this email directly or view it on GitHub <https://github.com/Zangetsu38/rpcs3/commit/6d4d0a4c0ab2997ddbd190198084901d5bb90f9b#commitcomment-14576024> .  <https://github.com/notifications/beacon/AGHcoyg72zV1hEJZC_NTZpoo-bcutfgRks5pI6cxgaJpZM4Gm0Z5.gif>


[Отсюда?](http://www.jbox.dk/sanos/source/lib/string.c.html) Придется подробно объяснять на защите.


Yes, :notification/medium from current is already a set when it's returned from datomic.


Ah, thanks. Now I remember how the execution contexts work, but I had never done anything more than the global one before.


Remove this line since you are getting the individual components of omega_dot as omega_dot_x/y/z


Perfect Legalese. Maybe i'll add this into mine as well


It should be possible, but I'll have to check on that.


The .gitignore should be in the repository, maybe a separate PR?


:(
On 24 Nov 2015 8:37 pm, "Flavien Raynaud" <notifications@github.com> wrote:

> lol
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/MrChoclate/facemash/commit/f1956b8385ddae2f540e16c78299e01a5c354ada#commitcomment-14598453>
> .
>


the note is still relevant, but could move to the notes in 'software-mode' about implementing reuse.


patch == PR?


I agree that I would like to see the colloquial variant used. It's, however, in the calendars that I've always seen it written as ਅਕਟੂਬਰ, which, while surprising, seems to give it some authenticity.


This is where the second free occurs. If line 2458 is hit then the code runs through to 2478, calling free on the same pointer.


Ниже допущена опечатка, из-за которой сохранить файл не удается. Сообщение об ошибке: `Input file extension!`.


Правда тестировал только на http://mlpg.co
А вот https://legacy.ronery.me/b/ судя по всему фикс не исправил :pensive:


Well, for example, we don't have to use the type annotation with the `Either` in the other comment thread, so I was thinking maybe we didn't need to here, either.


Is there a reason to change the existing check and replace with this one. IIUC previous one was matching basename. with only field 4 and now we are matching all the fields. Also given we are not parsing p, ORS= seems to be not needed.


Because every module should declare its dependencies. And while I don't think `phenotips-ui` is the right dependency, I'm sure there are other things that this depends on.


I was avoiding looping through $DEVS twice.  Do you see the call to pvs as that slow?


If it doesn't, I would recommend that we make an effort to implement Gurmukhi numerals in this translation.


I find this commit exciting!


What made me look here is [this commit](https://github.com/phenotips/phenomecentral.org/commit/9a45bfe34058416ff2777cd3b271c757838e9061).


I would usually save stdout for data to be piped to next program rather than messages of any kind.


108453024-FixLeedNumberOfHoursNotMet (JasonGlazer) - x86_64-MacOS-10.9-clang: OK (1965 of 1966 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)


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 118](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=517&buildTypeId=XbimEssentials_XbimEssentials) is now running


I can change it back. :)


Again CYA for a brittle script.


@Stacy-D, посиланням


Why not just do lighting updates syncronously? When block changes come in, flush lighting operations.


Здесь освобождается не вся выделенная память. На каждый оператор `new`/`new[]` должен приходиться `delete`/`delete[]`, на каждый `malloc()` --- вызов `free()`. Освобождая память под `proparray`, вы освобождаете только область с указателями. Области же, адреса которых хранятся в `proparray`, не освобождаются. Это нужно делать в цикле.


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 118](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=517&buildTypeId=XbimEssentials_XbimEssentials) outcome was **SUCCESS**
Summary: Running Build time: 00:01:29


This change is to address issue/28. this._.dasherize() prefixes upper case libraryName with - . e.g. "My New Library" became -my-new-library. So my solution is to convert the libraryName to lowercase before calling dasherize.


Ах, лол. Теперь я понял зачем этот код на тинибоардах: `Cfg.fileThumb = 0;`.


Committed: https://github.com/QuantConnect/Lean/commit/b71ca0a25ab9d35a845d76f157a858b30edf32f2


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


They must have been the result of cherry-picking a merge.  I'll remove them.  Sorry about that.


Whoah! Shivers down my spine!


@elbosio can we use "show" instead of "viewOrganizationDetail" for the action name? It seems this is the same as show but doesn't use the name by convention.


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


Alguma razão pra não traduzir "Woodman"?


I find these comments only add to the excitement!


возможно функцией логичней возвращать тип unsigned.


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


Because 1d should mean 1 day old, not 1 day in the future. Also the time.Time seems a bit poor to me. I haven't found a straightforward way to subtract duration. So I used Time.Add later.


Hi @arandall Do you know where that header did came from?
I'm currently working on stomp 1.2 support for https://github.com/stomp-php/stomp-php. This change might be something for a PR or Issue.


Непонятно, зачем эти две переменные.


Achei que Woodman seria mais adequado que Homem-Madeira. Você acha que deve ser traduzido?


Suggest defaulting to `False` so we don't get any nasty surprises


That is not the same behavior. create_extend_volume_group is only called when create_disk_partitions returns 0 with &&. Granted it should always return 0 now.  But that is more CYA for the brittle script.


К защите: чем `malloc()` и `free()` отличаются от `new` и `delete` по своему поведению.


I'm excited by @ernie's excitement about my excited comment on this exciting commit!


Acho que aqui Willow e Willowna logo embaixo poderiam ser traduzidos para Salgueiro e Salgueira. Sugestões?


Se temos tradução viável não vejo porque não usa-la.


Could be....code currently uses %lu


I'm open to suggestions as to the form/shape of the factory class and it's methods. Are you recommending a simple transplant of these static Generate methods to a different static class? Or are you recommending to creating potentially an interface `ISecurityIdentifierFactory` and then have various implementations for `EquitySecurityIdentifierFactory` `ForexSecurityIdentifierFactory`, ect...

I'm slightly hesitant to the idea and it's potential uses/advantages in the code base, but as always, open to suggestions!


@elbosio @ascuccimarra I thought we were removing COMPANY as an ORG TYPE and keep employer, clinic and hospital. We also need to add INSURER


Ok. Tem como mudar aqui ou devo fazer um novo pull?


What extra double quotes  - "%PRIu64" isn't going to work...


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


Try not to put the .idea folder on the git it's cleaner to my mind.


Whoops ;) Thanx for fixing that!


Updated to FontAwesome 4.5.0 :smile:


@elbosio @ascuccimarra be careful, we might remove COMPANY as ORG TYPE.


Do we need a lot of these i18n strings still, or can we remove from en.coffee?


Sweet


Just a heads up, @hmoco has taken over many file uploads from me and will have something for merge soon.  He's going to need at least 02e5b770 on treebeard develop for that.  Are you planning to merge your branch back into develop before then?


J'ai un problème avec ma liste d'unique_ptr, quand je compile j'ai une erreur de template et je parviens pas à comprendre d'ou elle vient ><


"Cockatrice" tem tradução pra português: https://pt.wikipedia.org/wiki/Cocatrice
Eu particularmente prefiro "Cocatriz".


Should this replace lines 63 through 67 instead?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 6603](https://teamcity.mesosphere.io/viewLog.html?buildId=80173&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Cannot start build runner Build time: 00:00:12


Eu percebo worm mais como verme do que minhoca pra esse bicho.


@billbonney that is only the 1090 KHz message. For 978 KHz there are about 114 bits. Plus, those messages are all split up and transmitted at different times. We don't want to make an ADS-B receiver parser, that works is for the hardwrae ot do and then have it transmit, over this mavlink msg, the logical data


@ppazos I could change it but that method was already there.

On Tue, Nov 24, 2015 at 5:12 PM, Pablo Pazos <notifications@github.com>
wrote:

> @elbosio <https://github.com/elbosio> can we use "show" instead of
> "viewOrganizationDetail" for the action name? It seems this is the same as
> show but doesn't use the name by convention.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/tarmac/pregnancy-control/commit/c64232cdfbff7ede19f70902b74dd4265046e8f3#commitcomment-14599323>
> .
>


Лучше запилить все под одну инструкцию var!


more edits Nov 24


нет смысла вводить переменную maxiter - newstr[size-1] = '\0'


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


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


static tileserver


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 6606](https://teamcity.mesosphere.io/viewLog.html?buildId=80176&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Cannot start build runner Build time: 00:00:15


This one's really odd and not immediately apparent, while ਸਵੇਰ and ਸ਼ਾਮ are. Both the forms (ਪੂ.ਦੁ. and ਸਵੇਰ, etc.) are equally imprecise since Punjabi doesn't have a narrative analogous to AM/PM way of defining time. We've got "it's 4'o clock of morning/noon/evening/night" narrative. Hence, ਸਵੇਰ and ਸ਼ਾਮ help narrate at least 2 quarters of the 24 hours day correctly. ਸਵੇਰ also serves before noon pretty well. ਸ਼ਾਮ serves until midnight as does the "good evening" greeting. ਪੂ.ਦੁ. and ਬਾ.ਦੁ. separate the day by noon, which is.. kind of unheard of in colloquial Punjabi if you ask me.

I'm sure it's not just me. Ignore it if I'm beating a dead horse though.

`keyboard warrior here detected` :neckbeard:


функция в параметрах должна принимать символ и позицию.


Внутри этого элемента было скрытое поле `<input name="firstname" value="" type="hidden">`. С включённой опцией превью файлов это поле удалялось и срабатывала антибот защита.


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


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


@elbosio there is a typo on Organziation and the ID selectedOrganzation


What do you think about using `repeat_exec` instead?


Aitpa!


Whoa! :100:


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


Ah, I see.


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


Faz outro commit pra mesma PR com as alterações.


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


You could just do `accelerator: 'Cmd+0'` to make this only apply to Mac


What do you suggest instead? Facilitates? Expands? Complements?


Rather than rely on list position, suggest using a dictionary in the form:
````
self.menu = {
    0: "Remote Control",
    1: "Three Point turn",
    ...
}
````
Even better, if we make each dictionary item another dict, we can just grab the relevant dict value and use the keys therein
````
self.menu = {
    0: {
        "title": "Remote Control",
        "log_text": "Entering into Remote Control Mode",
        "challenge_module": remote_control
    },
    1: {
        "title": "Three Point Turn",
        "log_text": "Starting Three Point Turn Challenge",
        "challenge_module": three_point_turn
    }

}

challenge = self.menu[self.challenge_id]
logging.info(challenge.log_text)
challeng.challenge_module.run()
````


move this to the top of the module as we'll always need it


Um, https://wiki.mozilla.org/Auto-tools/Projects  has nothing in it!


for - ом можно шагать до i <= size - 2, тогда у тебя будет копироваться \0 прямо в нем и не нужно будет совершать дополнительных действий


TeamCity pull requests :: netty [Build 741](https://garage.netty.io/teamcity/viewLog.html?buildId=3577&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5292, ignored: 21 Build time: 00:15:07


@martende How can I get your `1.5.1`?


As for benchmarks: loading this locally takes 130ms vs 1700ms. But heroku seems slower so maybe even bigger wins there.


byzare, moi ça marche bien


Edge DVS computers are unable to increase heap size past ~ 1GB.


Why do we need this? In what situations is this necessary? Why can't python create it's own expression statement in these cases?


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


Ok so whilst cat /proc/tty/driver/serial reports no overrun errors it seems that high throughput on UART2 will still lock up the the BeagleBone :-( Just had my first lockup.


If you allow `null=True` a default empty string is contra-productive. Should remove the default.


A static mechanism will destroy testing.


Is this fix still available in version 0.3.0 because the following code
@RequestMapping("/revisions/{ID}")
	@ResponseBody
	public List<Revision<Integer, Client>> getRevisions(@PathVariable("ID") String id,Pageable p)
	{
		Page<Revision<Integer, Client>> revisions = clientsRepository.findRevisions(id, p);
		return revisions.getContent();
	}

leads to the following exception when i pass a non-existent Client object ID.

Hibernate: select client_aud0_.REV as col_0_0_ from clients_AUD client_aud0_ cross join AuditRevisionEntity auditrevis1_ where client_aud0_.id=? and client_aud0_.REV=auditrevis1_.id order by client_aud0_.REV asc
Hibernate: select this_.id as id1_0_0_, this_.timestamp as timestam2_0_0_, this_.auditor as auditor3_0_0_ from AuditRevisionEntity this_ where this_.id in ()
23:27:06.893 [tomcat-http--32] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1


Hi Pat, et. al.

We now have implemented a preferences class and dialog, which will eventually be a non-modal window which can be docked.  This preferences dialog has an option for the two modes of viewing the session rows:  In-line and Master/Detail.  The tricky part was to make the switch-over virtually instantaneous.  This was done by having the DataAPLExecStmt and DataInterpResult classes inherit from a base class DataSessionRow.  In this way the Master/Detail view mode can be accommodated too. The xaml for the main form has two main data grids containing the session rows.  The Master/Detail data grid has a subordinate Details datagrid.  In the next modification we will reduce memory usage by filling the Master/Data and In-Line data grids only when the user has selected one or the other.  Currently they are being filled together, although one is always hidden.  We are experimenting to see if this latter modification is necessary because by default WPF datagrids are virtualized, so if one or the other is collapsed, there should be no 'double' memory usage.

Our next step will be to reestablish the special cursor actions of APL+Win which we have in the original prototype.  The prototype is working for the In-line case, so moving that to the project should be easy.  Setting up the special APL+Win cursor movement for the Master/Detail data grid will take more research.  We are considering using the default cursor behavior for the Master/Detail view since that will be entirely new to APL2K customers.  We should discuss this when we next meet.

Our next effort is to figure out branching in GitHub, so that we are not always pushing to the master.

We are still seeing the two APL64 repositories on the server-side and I don't fully understand why.  Next time I will share the screen so I can get other opinions or suggestions.

When you have time, explain how you are storing implementation notes and commentary in GitHub.  I was thinking of just using C# comment blocks, if there is no better suggestion.

Enjoy thanksgiving everyone,

Joe

________________________________
From: patrixion <notifications@github.com>
Sent: Tuesday, November 24, 2015 2:34 PM
To: APLNow-LLC/APLNext-APL64-Session-Solutions
Cc: Joe Blaze
Subject: Re: [APLNext-APL64-Session-Solutions] Initial commit (2adc5c1)

Woo hoo... great to see the project in GitHub... and multiple follow-up commits too!

-
Reply to this email directly or view it on GitHub<https://github.com/APLNow-LLC/APLNext-APL64-Session-Solutions/commit/2adc5c1f8d24b8521aee4eabe3f590f47cdee86b#commitcomment-14598387>.

[https://avatars2.githubusercontent.com/u/14003483?v=3&s=200]<https://github.com/APLNow-LLC/APLNext-APL64-Session-Solutions/commit/2adc5c1f8d24b8521aee4eabe3f590f47cdee86b#commitcomment-14598387>

Initial commit · APLNow-LLC/APLNext-APL64-Session-Solutions@2adc5c1<https://github.com/APLNow-LLC/APLNext-APL64-Session-Solutions/commit/2adc5c1f8d24b8521aee4eabe3f590f47cdee86b#commitcomment-14598387>
github.com


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


Would you mind renaming `tearDowns` to `registrants` while you're here?


@elbosio this service is called getPlanDef4Patient but it seems to get the names of plans that are not plans of the patient. I would change the name to something like getPlanDefNamesNotAssociatedWithPatient.

Also, we just need the names? Why don't we use the ids? If we use just the names to populate a select, and we don't have a unique constraint on the name, two plans can have the same name, so we might need to use the id.


NM, it seems https://wiki.mozilla.org/Auto-tools/Projects/ and https://wiki.mozilla.org/Auto-tools/Projects  are completly different pages


@bpostlethwaite @alexcjohnson this test and the ones below is a good place to start to review


Acho que bagworm nesse caso é so um apelido, visto que a página se refere à uma mariposa. O  mais próximo seri traça (bookworm). Deve ser algo parecido mas também não cosigo pensar em nenhum bixo que eu conheça. Acho que verme-bolsa está de bom tamanho


знак указателя требовали располагать сразу после типа - char* str. И так по всему коду.


TeamCity Jarvis Framework :: CI-GitFlow [Build 58](http://build.prxm.it:8811/viewLog.html?buildId=4862&buildTypeId=CqrsFramework_CiGitFlow) is now running


nit: opentstb -> OpenTSDB


опционально. в задании не сказано как, главное чтоб было.


It's ok. But next time I would suggest to keep valgrind log in commit msg, like done on commit 0b345460
It makes it easier for us to understand the problem when reviewing it and for further reference.
On http-server, we used as reference for a discussion I had with ceolin later.


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 119](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=518&buildTypeId=XbimEssentials_XbimEssentials) is now running


Maybe something like "is a shorthand for the old thumb() syntax"?


That was actually my instinct too. And I think that would work, but I ended up moving it here because I think placing it inside `repeat_exec` leads to an extra nested timer we don't need on the repeated calls.

Essentially, I don't think we need to wrap lines 63-67 in a timer, since after the first call, the whole `repeat_exec` call is already in the context of a timer from the interval timer scheduled on line 55. If 63-67 were in a `timer.at(0)` call, then we'd have a nested timer we don't necessarily need on those scheduled calls (anything except the first call). Again, I think that probably would work just fine, but this saves us the nested 0 second timer on the repeat calls (and there is technically a cap on the number of timers allowed in openresty). And I probably could have clarified this further in the comments, but this does then make the calling of `repeat_exec` consistent, since it's always within the context of a timer (the first one just happens to be an immediate one).

Does that make sense? But thanks for taking another look at this!


clean up


Actually ignore that, seems I was wrong and actually it crashed my application instead of hanging the OS!  We have progress!


for you @alexcjohnson


seems ok despite the function name may lead devs to think vector could be freed at some point inside this function (what won't happen)


Thanks, Martin.

At first I didn't set a default, but then in the columnar view, there were
all these '(None)' entries -- I set the default to empty string to clean up
the view, so that when no notes were entered, nothing (not even '(None)')
would be displayed -- how should I do that if I remove the default?

On Tue, Nov 24, 2015 at 3:30 PM, Martin Mahner <notifications@github.com>
wrote:

> If you allow null=True a default empty string is contra-productive.
> Should remove the default.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AASHE/hub/commit/bd629eb1081aa8534218703fed5c28373dfed175#commitcomment-14599798>
> .
>

--
Robert Erb
Web Application Developer
Association for the Advancement of Sustainability in Higher Education
www.aashe.org | bob.erb@aashe.org | (888) 347-9997 ext 35

--

Connect with us:   Website <http://www.aashe.org/> | Facebook
<https://www.facebook.com/aasheorg> | Twitter
<https://twitter.com/AASHENews> | LinkedIn
<http://www.linkedin.com/company/aashe>

<http://www.aashe.org>
------------------------------
Email Confidentiality Notice
<http://www.aashe.org/email_confidentiality_notice>


What exactly was the problem with the empty constructor?


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 119](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=518&buildTypeId=XbimEssentials_XbimEssentials) outcome was **SUCCESS**
Summary: Running Build time: 00:01:17


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


Ok. I'll do it next time


I can't really understand why the original code did it all in small reads, there needs to be a loop that reads in however large size it can still read. It needs to handle signal related errors and partial reads but nothing more than that.


тут согласна


FYI @alexcjohnson


А я понял, что мы сами выбираем как нам писать. Либо * к типу двигаем и потом пробел и так везде. Или пробел и * к имени двигаем и так везде.


Adding underscore in the IDs causes problem with JS because this doesn't follow the same ID naming convention as the usstate and country fields which is generated by JHTML and which doesn't insert any underscore. We can either change this to be consistent with how JHTML generates the ID (without underscore), or change the JS to make an exception for usstate and country fields.


Glad this is gone :) Nice job +1


Me gusta


I don't like this. If I've concsiously chosen to be registered with multiple scopes, I'm also signing up for the burden of the additional bookkeeping. Stifling callbacks seems like it will create even more mystery than the current situtation.

I'd rather see MultiScoped#exitScope include a Scope argument, so that registrants can keep track of where they are.

Although really, I'd rather just not support this use case at all. We haven't made a 1.0 release yet, and have made breaking API changes before. As long as we document it well, I'm inclined to just keep things clean.


..and I am not crazy:  FF adds the extra "/" on paste!


Sweet


Gotcha, it does, thanks. Sorry to have missed this the last time through!


TeamCity Jarvis Framework :: CI-GitFlow [Build 1.1.7](http://build.prxm.it:8811/viewLog.html?buildId=4862&buildTypeId=CqrsFramework_CiGitFlow) outcome was **SUCCESS**
Summary: Tests passed: 132 Build time: 00:04:33


TeamCity Jarvis Framework :: CI-GitFlow [Build 59](http://build.prxm.it:8811/viewLog.html?buildId=4863&buildTypeId=CqrsFramework_CiGitFlow) is now running


@DNx5 Change in behavior – name is no longer always lower-case. Is that still OK for these two methods?


piece of :cake:


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