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


@TD22057 Please make a new issue.


In case when 'path' not exists method will return whole config which is not expected.


when we didn't have the flag, having all the processes open the file was benign but not now when it tries to wipe it. At least that is the theory!


Closes #20


probably want to use a set rather than a list.


Try `@var` annotation for describing properties


This is a management API change so it would need an alias added.


Fixed.
Ignored Pep8 warning about length.


The code `type.GetProperties()` can be replaced with `TypePropertiesCache(type)` for more speed


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


As soon as this gets committed, "Current" becomes a bit confusing, as it's referring to the behaviour without this patch.


Already Modified.


Word Ladder solution accepted!


I doubt this is tested runtime, typically this is needed when udev is not there... did you check that?


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


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


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


Good point, thanks for the review


Already Modified.

Changed the '+' syntax to '.format()'.


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


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


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


Thanks for pull!


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


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3623](https://teamcity.mesosphere.io/viewLog.html?buildId=68351&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:46


You should use that: https://github.com/tools/godep#using-other-tools


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


Already Modified.

Would you like the ".format("  moved to the next line?


107310700-change-license-text (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1425 of 1425 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.4%25-green.svg)


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3628](https://teamcity.mesosphere.io/viewLog.html?buildId=68358&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:39


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


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


This potentially overwrites the high 16 bits of x87_op_off.


Docker 1.9 has added the ability to define build-time ARGs (along with default values) inside Dockerfiles that can be reset in the build command. We're going to upgrade to Docker 1.9 ASAP, so maybe we should use build-time arguments instead of templatizing the Dockerfiles.

More info available here:

https://docs.docker.com/engine/reference/builder/ (Ctrl-F for ARG)


Without this change, UIforETW (Debug build) crashes on my machine when I click on "Copy startup profiles".


in _initializedFromStoredSettings


Nei ikke på denne siden. Superadmin skal kunne lage stillingene som trengs
for rollene for teamet sitt. Vi trenger ikke lage noe begrensninger på
hvilke stillinger de gir til teammedlemmene, men de burde ikke ha mulighet
til å slette noe. Siden dette fører til at alle radene i workhistories med
den stillings iden blir satt til null.

On 4. november 2015 23.11.27 Kristandre <notifications@github.com> wrote:

> Er det ikke det som er meninga da?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/vektorprogrammet/webpage/commit/2fada3509baa0ef8d66b496a917c2846ab88a68d#commitcomment-14196841


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


changed to showRunTests and showCancel


Without an additional comment it is not clear that for negative numbers (e.g., -1) john will finally abort if the currently processed block of password candidates has been tried for all the hashes.
Also, we should only document that behavior for -1, not for any negative number, e.g. -4 times UINT_MAX...


removed


You don't need to comment each line. In method you will usually put general DocBlock, inline comments for lines with not obvious logic and inline comments to separate sections if method is complex.


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


Should this be `static::create`?


Those come QtWebkit, which probably is used by PhantomJS. I don't know if this will ever make a difference - besides in our unit tests - but I think they won't do any harm either.


Both WPA 8 and WPA 10 look into "Documents/WPA Files" to find regions file.


Fixed. Is this suitable?

```
        logger.info('Spawning {0} years for processing seasonal summaries via'
                    ' {1} processors ....'
                    .format(num_years, self.num_processors))
```


Runner method / statistical feedback for decision making


// Get all hosts at siteId


move to `Set`


ff een testje met eGit (net geinstalleerd in Eclipse) ;-))
deze interface is nog niet af / correct


No, I think they just made the change so that the tool is version agnostic, i.e. they always append the version number to the directory. Sneaky... I wonder how many travis builds will fail because of this change. I did notice in [their .travis.yml](http://conda.pydata.org/docs/travis.html) that they explicitly set the folder name.


Hvis vi bruker
```
 { path: ^/teamadmin/stilling/slett/, roles: ROLE_HIGHEST_ADMIN }
```
så kan de fortsatt gjøre alt det, da begrenser vi kun sletting


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


I like in this way, then if it will blocks again will dig into it and find another solution


@monishdeb this does not merge cleanly into the master branch - can you assist?


Thanks for the reply.  I'll give it a try and will let you know.


Fixed. Is this suitable?
```
                    logger.error('Error processing seasonal summaries for year'
                                 ' {0} and season {1}'
                                 .format(start_year + i, season))
```


hmm, GtkTable is pretty deprecated with gtk3, can this be improved?


should be shutdown(). will fix after comments and before potential merge


Same with the other commit, I think this should be `static::create`


Should we create a zk folder for site to reduce the number of keys we need to look at?


@babadi this might be the issue. `-name` should be outdented at the same level as the others


You can use 2.6.0-SNAPSHOT for now either from Sonatype's snapshot repo, or
by downloading the latest jar from there.

On Wed, Nov 4, 2015 at 11:10 PM Robert Fink <notifications@github.com>
wrote:

> Uh, this is pretty exciting. Any idea when this make it into a release?
> Until then, is there a workaround for overriding name resolution?
> Cheers!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/square/okhttp/commit/38c6e610f13033bc40d0307c0a2f2e86a49564b9#commitcomment-14196828>
> .
>


This doesn't escape table names with quote chars in the name correctly. I.e:
CREATE TABLE "evil""table" (id int4)


@hschilling, 100% agree that only the rank0 proc should make the file. That sounds like the correct fix.


:smile:


Careful changing these if you're doing this automatically


Ah thank you sir, I will give that a try.


Hi Ben,

Yes, the API is correct - but the events sent to the app will be the _intersection_ of the signals, rather than their union (not sure this is what you're looking for here).

If there's anything I can help with along these lines let me know. Thanks for checking this out!


Eric could you please look at the GraphNodeDao class? I got really confused with the neighbour nodes


nits:
"the default"
Comments are full sentences. Please finish them with a period.

I suggest a different comment:
Note: If multiple ACL plugins are registered, a default ACL factory has to be set with tableacl.SetDefault().


Are we sure we're fine with this?

That means one can set enforce-table-config but forget to give a table-acl-config on the command line. I would rather fail here and tell the user that they forgot something to configure.

nits:
- "ACL definitions" sounds better
- missing period


And finally, same thing, `static::create`


nits:
"Failed"
Probably better to say "the Table ACL module" ?


nit: I suggest: "Exiting because the Table ACL module was not successfully initialized but enforce-tableacl-config is set."


I see. I assume the SNAPSHOT is subject to change as new commits go on develop? Do you publish stable semver-named artifacts in addition?


Please change this as follows:

``` go
if configFile == "" {
  return nil
}
actual code
```
This way, the function returns early and it's clearer to read why it does that. This is also the preferred way to indent (error) flows in Go.


Fixed.
```
        logger.info('    Generating {0} {1} good looks using {2}'
                    ' files ...'.format(year, season, n_files))
```


I would prefer if we don't log this when the JSON unmarshalling below succeeds.

Otherwise, it would only confuse the user.


Please add here the bit from my other pull request:

``` go
if len(acls) == 0 {
  return nil, errors.New("no AclFactory registered")
}
```


nit: "there is"


nit: "AclFactory" to be consistent with the other error messages


Internal guidelines say "Don't name result parameters just to avoid declaring a var inside the function".

Therefore, please remove the naming.


@alecthomas Could you have a look at this commit? Seems bit hacky to test the interface inside ``get_binding`` and let it save the binding to ``self._bindings`` despite ``auto_bind`` disabled but it works rather well and the changes are minimal.

If it looks good - would you mind releasing a new version when you have a moment?


Please rewrite this as follows:

``` go
f, err := GetCurrentAclFactory()
if err != nil {
  return nil, err
}
return f.New(entries), nil
```

This is the expected way to indent error flows in Go. See the internal Google guidelines.


I'm going to write a VS extension to auto-sort all dependencies in a solution.

But it will only sort by version, not by name. :stuck_out_tongue:


nit: Please write in the test error message what you were expecting. This way the code itself is also better documented.

e.g.

``` go
t.Errorf("GetCurrentAclFactory() should return the registered ACL factory, but did not: %v", err)
```


nit: Please write in the test error message what you were expecting. This way the code itself is also better documented.

e.g.

``` go
t.Errorf("GetCurrentAclFactory() should fail if multiple ACL factories are registered and no default is set. But it did not: %v", err)
```


Configuration values is better to keep in separate file.
p.s. from php 5.4 you may use short array syntax `$veryArray = ['suchKey' => 'Wow']`


```C#
if error or response.statusCode isnt 204
```


nit: Please write in the test error message what you were expecting. This way the code itself is also better documented.

e.g.

``` go
t.Errorf("GetCurrentAclFactory() should fail because the set default ACL factory is not registered. But it did not: %v", err)
```


The internal guidelines for error flow indenting in Go require the following structure:

``` go
x, err := f()
if err != nil {
  // error handling
  return
}
// use x
```

Please change the code to this structure.


Thanks for the info!


I suggest to be more explicit here:

```
log.Infof("Table ACL checks will be exempted for all members of the group '%v'.", config.TableAclExemptACL)
```


nit: "table ACL module" ?


Could you try to revert this manually?


Can you please copy this check into table.Init() as well and fail there if no ACL factory is found?

I would prefer if we fail already at startup on this (in addition to at runtime).


We don't need separate definitions for this struct; it's the same across architectures so we can just define it once in `BaseArch`.


Possibly use named flags instead of bool


Yes

On Wed, Nov 4, 2015 at 11:28 PM Robert Fink <notifications@github.com>
wrote:

> I see. I assume the SNAPSHOT is subject to change as new commits go on
> develop? Do you publish stable semver-named artifacts in addition?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/square/okhttp/commit/38c6e610f13033bc40d0307c0a2f2e86a49564b9#commitcomment-14197238>
> .
>


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

```


Yeah, thought about that too but was to lazy in the end. Can change tomorrow.


We don't need `record_page_below_stack_ptr` since from my reading of the kernel source, `compat_alloc_user_space` is not used for this ioctl.


ok


Este label "US-sprint6" no se corresponde con la referencia que se hace a la misma previamente en el texto, \textbf{Tabla \ref{USrelacionados-Sprint6}}


@CPDigitalDarkroom There are some dodgy ones where I would need more context, also the Capital on every word looks weird in Dutch, should I get rid of those?


Fixed.


When you mention that it needs to build from scratch on macosx. What happen on other platform ? How is the extension build ?


bug, should be catching a `NodeExistsException` which means this hostId already registered by another instance.


Nope, it's done by `php-cs-fixer` (in particular the `pre_increment` fixer that's ebabled by default).
Since the value of $i is not used in the same statement of this post/pre-incrementor there's no problem here.


Either here or in `uninstall()`, we're going to need to unload any modules loaded by the Add-On. Since references will continue to work after modules are unloaded, we should tear down any active calls as well.

See https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Language_Bindings/Components.utils.unload


Thanks. I'm glad they are relatively harmless in python. Its hard to transition between C and python in that regard.


bug, I get a: `AmqpArgumentError: must provide argument containerId`


Cool, that's what I thought just wanted to mention it :+1:


дякую


Awesome, thanks!


Yes, probably it's better in the case when some old code uses the old method for sub-classes of this class that use the new method (it's the only reason that I see to use static instead of self).


Вася(


Why has values-en-rGB/strings.xml less strings to translate.
eg general_pro_msg is missing?


@chrishaid do you like this logic for adding `CGP: ` to the first non-NA occurrence in the data?


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


> it is not clear that for negative numbers (e.g., -1) john will finally abort if the currently processed block of password candidates has been tried for all the hashes.

The fact it will do that is obvious - what would be the alternative?

I think it's perfectly clear: The grace time becomes unlimited so we will never *hard* abort. The concept of waiting for an optimal resume point is mentioned. Anyone not understanding that won't need the option anyway :wink:

Feel free to commit a change though!


Oh, ok, I get why. Users never actually call `new OpenFrame`, so it's not a bug. Sorry about that.


обновление


GG scrub (actually cool though)


Already modified.
All instances of "log_handler" have been removed from the entire project.


Thanks! that's a great resource. can you please add that resource to 1) the full lecture notes in this unit, and 2) the Resources.md file in the root dir?

Thanks!


досить лише
if (email != null ? !email.equals(that.email) : that.email != null) return false;
if (password != null ? !password.equals(that.password) : that.password != null) return false;

Тоді ж доведеться виправляти)


Already modified.
logger.warn was used.


Lets first see if it compiles again with gcc 5.2, which is in jethro. And fixing compilers is out of (my) scope.


If you will revert to the version prior to your reversion and add in the mouseup change, I'll tackle cleaning up the code manually.


the site ids don't match the ones below. typo?


а чому статично?
чому не бін?


I wonder if this path should be a const so you don't have to keep repeating it


Oh, that's way better. I'd definitely prefer to do it that way as soon as we have docker 1.9 on the build machines. Do we have any sort of precise timeline on that?


Alright


а може має бути окрема табличка?


Nice catch.  Thanks.  Merged into my fork, as I don't want to wait around to see what happens with your PR.  You may want to check out my PR/fork which has a new option to prevent bound pickers from closing automatically after a date is selected.


I added the empty testcases on purpose.  They are there to be filled in


Yes, you can create an issue with this


#4399-ZoneSum-vs-VentilationRateProcedure-when-one-zone-has-zero-oa-requirement (rraustad) - 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)


不要ignore .swp啊


107310700-change-license-text (jasondegraw) - Win64-Windows-7-VisualStudio-12: OK (1961 of 1961 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)


That's a good idea!  So you get the context but needn't repeat it *ad nauseum*


You could also write this as:

```ruby
unless allowed_classes.include?(klass)
```

This works because `Array#include?` iterates over the elements and calls `#==` on each, and `Class#==` is the same as `Class#equal?`.


Fixed.


please change
my $authorized_keys_file = = $conf->{basic}{authorized_keys_file};
to
my $authorized_keys_file = $conf->{basic}{authorized_keys_file};


What was the motivation for making this non-anonymous? That broke the linking to the clustering docs and was really hard to find :-/


I didn't even know this was a thing!


uuu!! si, ya lo cambio!


r+


well appreciated  ;)


saw approval from jedmccaleb
at https://github.com/MonsieurNicolas/stellar-core/commit/0af1ebaff6ffe01eacc521c2a7e2dc25abacbc1f


merging MonsieurNicolas/stellar-core/matchShortIDfromSCP = 0af1ebaf into auto


MonsieurNicolas/stellar-core/matchShortIDfromSCP = 0af1ebaf merged ok, testing candidate = fa6f3251


I think this and the zkreg class should be in container.
I don't see this as being part of the core. do you agree?


Что-то странно отобразилось - как будто все перезатёрлось, точнее форма как будто новая добавлена


I'd suggest documenting `classes` as `Enumerable<Class>` and then coercing it to a `Set` when passing it to `TypeCheck.new` (or coercing it inside `TypeCheck#initialize).

Alternatively you could use `Set[...]` in the callsite for `attribute`, changing the docs to `Set<Class>`. This is better since it happens earlier.

The list of classes doesn't need to contain any duplicate entries so a `Set` is probably more appropriate than an `Array`.


Done!


Maybe done


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


Сложные моменты по страничке catalog:
1. Карточки с товаром располагаются по две в ряду, хотя они макетной ширины в 220px.
2. Не получается разместить заголовок "Группы товаров" на одну строку. Не реагирует на маргины или паддинги.
3. Блоки с ценой и кнопкой купить при display: inline-block не становятся на одну строку.
4. Пагинатор не смещается  вправо под карточки ни через паддинги, ни через маргины.
И по странице catalog-item: три маленькие фотографии слиплись.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3633](https://teamcity.mesosphere.io/viewLog.html?buildId=68383&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:58


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3632](https://teamcity.mesosphere.io/viewLog.html?buildId=68382&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:59


Should this be renamed to something like `context` or `routingContext`?


What are the circumstances in which two versions of jQuery were loaded? I've never encountered that. I'm actually looking at it right now and am not seeing this issue. The stock version of jQuery is actually dequeued to avoid that issue.

About the supported version of jQuery, you can actually use whatever version your theme wants to use, WordPress doesn't care. WordPress needs a specific version for _admin_, but this piece only changes the version for the theme, which can be anything.


I think Jesse was saying before the end of the year, but hopefully (maybe)
in November.

On Wed, Nov 4, 2015 at 11:34 PM Robert Fink <notifications@github.com>
wrote:

> Awesome, thanks!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/square/okhttp/commit/38c6e610f13033bc40d0307c0a2f2e86a49564b9#commitcomment-14197404>
> .
>


var fs = require('fs');


May not help. Write is much slower than read. (write need consensus but read can be read locally)
Having additional folder like site -> hosts. we need to update two records when the there is a successful register.


Oh I am sorry, the double underscore __ was not a typo, I just understand now.
Sorry about that, you can of course reverse that change. My bad.


This can stay as it was originally when requiring fs-extra: fs.mkdirsSync(destination);


To support any `ColumnAttribute` even from `System.ComponentModel.DataAnnotations.Schema`, this should work:

`            var columnNames = TypePropertiesCache(type).Where(p => p.GetCustomAttributes(false).Any(attr => attr.GetType().Name == "ColumnAttribute"))
                .ToDictionary(p => p.Name, p => (p.GetCustomAttributes(false).First() as dynamic).Name as string);`


cbecc-reintegrate (kbenne) - i386-Windows-7-VisualStudio-12: OK (2332 of 2368 tests passed)

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


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


enforce-table-config is for enforcing inital configuration, it only make sense for file based, static-only use cases. Internally, we have dynamic TableACL support which doesn't rely on a file at all


Nitpick: please include spaces between strings, methods and the plus sign


@patriciogonzalezvivo Here's the changes I made to account for the behavior you talked about in your sandbox styles - initialization of global variables happens at the very beginning of `main()` now.


Hi @satnam6502, appveyor CI build start to failed after this change:
https://ci.appveyor.com/project/Facebook/rocksdb/build/1.0.75
I believe it's related to your "Add RocksDb/GeoDb Iterator interface" commit.
Could you please take a look at this? Thank you :)


I've literally renamed this from `RoutingContext` to `routingContext` and then back again per @timdorr and @ryanflorence.

I'm totally okay with whichever, but I'd like to stop changing it back and forth.

We can do either `RoutingContext` because this is a component class, and that's the standard naming convention adopted by e.g. `Relay.RootContainer`, or we can call it `routingContext` to be consistent with `component` on `<Route>` and otherwise. I'm really, really okay with going either way.

Just someone tell me which!


I'd leave out this comma after 'dependencies' personally.


lol, good commit message.


Just leave it. I don't really care that much. This is a relatively small edge case API anyways.


why go away from bytebuf bytesinput


Interesting step for an introductory tutorial since this is kinda something you well ever do in real rust development.


I pervasively over-comma, so yeah, seems good :embarassed:


I added the .env parameter: INCLUDE_SHIBBOLETH_AUTHENTICATION=true. But, the generate_history_text method still fails for us after logging in with Shibboleth:
ActionController::RoutingError (No route matches "https://idp-test.uiowa.edu/idp/profile/SAML2/Redirect/SSO"):
  app/helpers/application_helper.rb:3:in `generate_history_text'
  app/views/application/_nav.html.haml:28:in `_app_views_application__nav_html_haml___583485331303763218_70113240'
  app/views/layouts/application.html.haml:15:in `_app_views_layouts_application_html_haml___103948154994869432_56373060'
  app/controllers/protocols_controller.rb:10:in `block (2 levels) in index'
  app/controllers/protocols_controller.rb:9:in `index'
  app/controllers/application_controller.rb:12:in `set_time_zone'

I'm not sure what the fix is but did find this...read Caveats: http://cookieshq.co.uk/posts/a-menu-system-with-pundit/


Dette gjør vel det samme rollesjekken i controlleren? Altså at når en
trykker knappen, så vil ikke funksjonen kjøre.

Vi burde ha sjekk i både front og backend. Men er det noe forskjell på
security.yml og sjekk i controlleren?

On 4. november 2015 23.23.19 Kristandre <notifications@github.com> wrote:

> Hvis vi bruker
> ```
>  { path: ^/teamadmin/stilling/slett/, roles: ROLE_HIGHEST_ADMIN }
> ```
> så kan de fortsatt gjøre alt det, da begrenser vi kun sletting
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/vektorprogrammet/webpage/commit/2fada3509baa0ef8d66b496a917c2846ab88a68d#commitcomment-14197117


Maybe `numDirLights` and `NUM_DIR_LIGHTS` would be clearer? Just a thought...


See https://sft.its.cern.ch/jira/browse/CVM-931


Why is one `N` capital here?


How about marking this request as bogus then instead of just ignoring it?


Too long. Previous is better.


Merged


There's value in teaching the layout of a Cargo project, but I'm a bit worried that this sequence makes it seem like Cargo is strangely difficult, when the real way you start a cargo project is a single command. I do see there's an 'easy way' section later...


Did you find something interesting :-)?


index


@Meijuh tells me that the reason for VSet update is parallel enumeration.
I'll remove this commit.


And finally, the location of `/usr/share/locale` is only configurable in NixOS because we patch glibc, and that option is not available on Darwin.


#define NUM_ENTRY_CHARS 4

if (s_selection_index < NUM_ENTRY_CHARS) {
...


This commit is essentially reverting 8a871f7bac6b3ed9ae99400c1e01fb7064e0d847. The tests were [failing all over the place](https://circleci.com/gh/18F/C2/2759) with the module definition being in its own file under `app/models/`, and putting it back seems to fix the problem. Played around with explicit `require`s etc., but probably not worth worrying about it for now, especially since we only have one `Ncr` model.


LGTM


Does the fact that 'we chose it' matter? Sounds defensive.


To be clear, this is mostly just a move of what exists today, we already do this: teach a hello world with `rustc` and then move it into cargo. See https://doc.rust-lang.org/book/hello-cargo.html#converting-to-cargo

(not that that makes it right, just that this PR doesn't _introduce_ it.)


I was struggling between providing a justification and just being like "hey, toml, whatever". Maybe I should go for one or the other.


Rejection in Chromium happens only for TLS 1.0, not 1.1.


> update というひとつのアクションに、 「移動」と「変更（名前など）」 の２つのアクションが入っていると危うい感じ

確かにそうですね！
モーダル画面の出し分け時に処理が別れるよりも、「移動」「変更」の処理前後に処理が別れる場合の方が起こりえそうですしね。。
「移動」「変更」はユーザーから見たら結構違う処理なので、更新側を別々にしておいた方がわかりやすいですね！
修正しておきます！

> 今の move に相当する処理は js ( coffee ) だけでやってしまい

Railsでjsの処理する時のイメージがまだイマイチわかってないところがあるかもなのですが、

- jsで画面の一部を表示更新したいアクション起動
- Rails側で待ち受けてる、更新部分だけをjsonで返すURLにアクセス
- jsで画面書き換え

な流れになるかと思うのですが、
結局今のmoveに相当するRails側の待受け口が必要になりますよね・・？
（今はformを表示するパーシャルを呼び出すjsを返してるところが、jsonになって、coffee側で受け取ったjsonを埋め込む感じになりますかね・・？？）
画面のレイアウト的なところはなるべくhamlでやっちゃって、成形後のものをRails controllerが返してくるjsで処理（html埋め込むだけ）の方がRailsっぽいかな？と。。
・・結局どっちも手数的には同じ、なのかな。。


Too long. Should stick with the first.


The API currently 500s countries besides the US and Canada (where these tests expect a 400).  Even if we 400 them, it's probably still worth testing that Beehive knows them because we use the same country list for product origins (although it may make more sense to move this test to the product API if/when we gain a writable API there).  Anyhow, if I test my local database against this (using 500 instead of 400), I get the following errors:

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [BONAIRE, SINT EUSTATIUS AND SABA (BQ)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [CURAÇAO (CW)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [LIBYA (LY)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 242, in test_country_iso_list
        name, alternate_names.get(country_code, [country]))
    AssertionError: 'LIBYAN ARAB JAMAHIRIYA' not found in ['LIBYA']

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [PALESTINE, STATE OF (PS)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 242, in test_country_iso_list
        name, alternate_names.get(country_code, [country]))
    AssertionError: 'PALESTINIAN TERRITORY, OCCUPIED' not found in ['PALESTINE, STATE OF']

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [SAINT BARTHÉLEMY (BL)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [SAINT MARTIN (FRENCH PART) (MF)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [SINT MAARTEN (DUTCH PART) (SX)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ======================================================================
    FAIL: test_country_iso_list (test.address.TestAddress) [SOUTH SUDAN (SS)]
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/wking/Private/azure/api-spec/test/address.py", line 230, in test_country_iso_list
        self.assertEqual(cm.exception.code, 500)
    AssertionError: 400 != 500

    ----------------------------------------------------------------------
    Ran 1 test in 178.553s

    FAILED (failures=8)

The `400 != 500` errors are for new entries that I don't have in my test database.  For example:

    {"message": "country-name not found: u'SS'", "code": 400}

Palestine and Libya are probably just official name changes (and I'd suggest we migrate to “Libya”, matching the ISO, and “Palestine”, to stay out of that debate).


 -  Is the project relevant to what we’re doing in class?
Yes, definitely! It will be a challenging task but several of the models we learned are equipped for the challenge.

 -  Is there something that’s not obvious or not understood about their project?
No. It is clearly laid out.

 -  Are you working on similar problem and perhaps could share your thoughts?
No. I think I will steer clear of NLP and instead focus on financial data.

 -  What do you like or find interesting?
Twitter is an interesting beast. It is psuedo-anonymous. Most accounts / tweets are from "real" people like Facebook. But there are definitely a significant number of accounts that are fake or purely set up to troll. These accounts may trigger your mental health detection algorithms, even if they don't truly convey mental disturbances.

I would also advise you to separate groups of twitter users based on how many followers they have. If they have say, >150 followers, it is very likely they are "real" and should be asssessed as such. I bet you will see even fewer deranged / mental health triggering tweets at the "Verified Twitter User" level, as most of those are celebrities with carefully curated tweet content.

Also, please parse Donald Trump's tweets and let us know how sane they are! :+1:

 -  How are results validated / what could be improved?
Good luck with the NLP processing. Some of the sentiment algorithms may need to be tweaked given how people often shorten words or phrases on twitter.


Looks like there is some code repetitions in places where columns are concatinated, perhaps possible to make it DRY-er?


Also, does the book use 'we' a lot? Is it a conscious decision to present the book from the perspective of the rust developers?


changed to Unenhanceable. let me know if this is ok. 'ca' usually makes a 'ka' sound in english, ot it needs to have the e.


Caracteristicas:Soporte No SQL.
1. Acceso, exploración y organización de fuentes de datos.
2. Capacidades de Normalización.
3. Conectividad a cualquier tipo de datos.
4.Arrastrar y soltar diseño sin generación de código.
5.Arquitectura moderna.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3639](https://teamcity.mesosphere.io/viewLog.html?buildId=68396&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:01:05


g_free (priv->origin_name);
priv->origin_name = NULL;


BTW, per @ryanflorence this is intended as a private/experimental API. I'm going to use it in `react-router-relay` but you really shouldn't use it elsewhere. That means there's not necessarily a guarantee of semver compliance. So... don't use it without some thought.


g_free (priv->media_baseurl);
priv->media_baseurl = NULL;


Looking forward to it, thanks.


Solves #14


"Cargo figured out *that the hasn't changed*".


I security har vi oversikt over alle sider som krever spesielle rettigheter. Jeg synes at det å slette semester/stilling også burde stå der. Det skal holde å gjøre sjekk i kontrolleren, men det blir veldig uoversiktelig og tungvindt å sjekke alle funksjoner i kontrollere for å lete etter adgangsbegrensninger ved et senere tidspunkt. Faktisk så tror jeg vi burde fjerne sjekken i kontrolleren og kun bruke security.yml. Hvis vi har lyst til å endre rettigheter senere, så trenger vi kun å endre en linje i security, da trenger vi ikke huske hvilke begrensninger vi har gjort i kontrolleren


107310700-change-license-text (jasondegraw) - i386-Windows-7-VisualStudio-12: OK (1961 of 1961 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)


Sorry about the confusion. I overlooked the check above which checks: if enforce && config == "" then exit.


Amie,

According to the documentation, if ```pileup.is_del``` is ```True```, then ```pileupread.query_position``` will be ```None```.
I believe you need to address that scenario at this point.

I fixed it by adding
```
    if pileupread.is_refskip:
        return True
```
in this area. Before the patch, I was getting an error pointing me to that location and saying the list index had to be int and not NoneType

Arjun


"modified your program" -> "modified your source code" / "built the file" -> "built the program" ?


yep :nail_care:


Good :+1:


I suggest to put this check into its own block:

``` go
if *enforceTableACLConfig && *tableAclConfig == "" {
  log.Error("table acl config has to be specified with table-acl-config flag because enforce-tableacl-config is set.")
  exit.Return(1)
```

This way it's easier to see the specific case it's guarding against.


@AmiraSh There was a mistake. It is your zone of responsibility, so deal with it=)


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1059.98d7412fe9f7331540c727670601a34fd37aac81](http://build.palaso.org/viewLog.html?buildId=65585&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 724, ignored: 6 Build time: 00:10:21


I  don't have any preferences on abbreviating the missing-entirely entries.  I'd probably avoid messing with the ISO names until (if) we ever source a product from one of them.


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/89331497


this reminds me of BASIC... you need to leave enough space between the labels so you can goto 10, goto 30, etc...


Rerolled as 765342885ece4a4c90a2886a03ddc706780680b7.


I think we could use this decorator https://docs.djangoproject.com/en/1.8/topics/auth/default/#django.contrib.auth.decorators.user_passes_test


Haha, I know right :P


Хорошо бы не удалять лишнего :)


flag CONCURRENT_MODE required for support under Android 4.x and Android 5.x


Any chance this could get pushed out to CocoaPods?


Generally, it uses "we", but to mean "the author and the reader," as in "Let's do this together", not "I command you to do a thing."

You are right that this makes "we" ambiguous here :/


it will anyway fail inside the `negotiateCrypto()` routine.


ok, no worries :) Sphinx is tricky sometimes.


Думаю, что надо комментарий какой-нибудь добавить. Потому что вот так вот совсем неясно откуда это 7 взялось. Предлагаю как-нибудь так: `To fit the longest name of HTTP method ("OPTIONS")`


Because I want to skip 4 bytes. small n is 16 bit big endian, big N 32 bit.


Neat. I didn't know you could do this!


fast-forwarding master to auto = fa6f3251


Interesting.  I'll have to check that my fix made it out.  I may have to add some additional protections.  The back button stuff was tricky.

Andrew

On Nov 4, 2015, at 5:56 PM, robertjamesmiller <notifications@github.com<mailto:notifications@github.com>> wrote:

I added the .env parameter: INCLUDE_SHIBBOLETH_AUTHENTICATION=true. But, the generate_history_text method still fails for us after logging in with Shibboleth:
ActionController::RoutingError (No route matches "https://idp-test.uiowa.edu/idp/profile/SAML2/Redirect/SSO"):
app/helpers/application_helper.rb:3:in generate_history_text'
app/views/application/_nav.html.haml:28:in_app_views_application__nav_html_haml___583485331303763218_70113240'
app/views/layouts/application.html.haml:15:in _app_views_layouts_application_html_haml___103948154994869432_56373060'
app/controllers/protocols_controller.rb:10:inblock (2 levels) in index'
app/controllers/protocols_controller.rb:9:in index'
app/controllers/application_controller.rb:12:inset_time_zone'

I'm not sure what the fix is but did find this...read Caveats: http://cookieshq.co.uk/posts/a-menu-system-with-pundit/

—
Reply to this email directly or view it on GitHub<https://github.com/sparc-request/sparc-fulfillment/commit/0268e44828d1b31a063e50cf0c558b817bafdd2d#commitcomment-14197955>.


I restored the mouseout changes. Cleanup is next.


yeah, but implementations are free to reject for 1.1 too as per the RFC. Hence I'm going to be safe and upgrade to 1.2 if possible.


This is still swallowing SnappydbExceptions. The options are:
- In a comment, explain why this exception can **never** happen
- Throw the exception up
- Do something that handles the exception.

The issue we ran into production is that creating the SnappyDB failed (likely a snappy db exception). The db variable was thus null, but the class was created with no communication that something bad happened.

I see this fix makes the class safe again, by checking the status of the db variable. However, when the class is in this state, it is more or less useless, and when I use the library I would like that. So I would lean towards option 1.


Would love to see a mailbox-like snooze plugin!


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3643](https://teamcity.mesosphere.io/viewLog.html?buildId=68406&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:02:20


More discussion in https://18f.slack.com/archives/ruby/p1446676427000009.


'@context' should not be needed here, as hit comes back from es, it won't have an attr called @context.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3641](https://teamcity.mesosphere.io/viewLog.html?buildId=68404&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:21


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3642](https://teamcity.mesosphere.io/viewLog.html?buildId=68405&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:21


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3645](https://teamcity.mesosphere.io/viewLog.html?buildId=68408&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:21


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3644](https://teamcity.mesosphere.io/viewLog.html?buildId=68407&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:23


Nice, thanks! :D


#4399-ZoneSum-vs-VentilationRateProcedure-when-one-zone-has-zero-oa-requirement (rraustad) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1948 of 1962 tests passed)

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


Hi - this bug is still showing when downloading sendgrid-django using from https://pypi.python.org/pypi (v1.3.0). Manually editing to include the missing **smtpapi.** resolves the bug.


:smile: :+1: you're welcome! Maybe tomorrow or Friday v1.1.1 will be released


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


I like this addition. Cleanly separates extensions from the standard.


saw approval from jedmccaleb
at https://github.com/MonsieurNicolas/stellar-core/commit/1c239a703cc0213de9bfa24ee1f80a5ea28b74ee


merging MonsieurNicolas/stellar-core/handleHello2Fix = 1c239a70 into auto


MonsieurNicolas/stellar-core/handleHello2Fix = 1c239a70 merged ok, testing candidate = 924ad4bb


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


This looks great! Is it ready to pull request, or are you still working?


scopeまだあまり慣れてない感じで、良さがあんまり分かってないですが・・

（今返事を書こうとしてて一旦調べなおしてみて↓がちょっと納得感・・必ずメソッドチェーン出来る、は他から使う時の安心感ですね！）
http://qiita.com/m_nakamura145/items/39820db683255cdc9ea3

何度かscopeについてのご指摘を頂いて自分の傾向に気づいたのですが、
私、モデルに自分を起点として条件を絞り込もうとする、インスタンスメソッドを書きがちである・・という傾向があるみたいです。

コレって、あんまり良くないんですかね・・？
モデルで条件を指定して値を返す場合、基本的にはscopeを使うべき、と思ってる方が良いのかな・・
インスタンスメソッドの方がしっくりくる、ってパターンは少ないんでしょうか・・？


Sorry for the merge commit.


somehow it looks similar to the $.map()


@dgilperez En unos días la libero, disculpa que no te contestara antes!


This should be in the normal `engi` package.


Don't forget to `npm publish`! :shipit: :wink:


cant see your changes bro, you just pushed the professors file.
try:
git add Path/to/GraphNodeDao.java
git commit -m "GraphNodeDao"
git push


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


Yup I know, I mean compiling a binary.


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


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


remove


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


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3647](https://teamcity.mesosphere.io/viewLog.html?buildId=68412&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:01:47


@matiwinnetou SGTM


factorize


This should be `GO15VENDOREXPERIMENT`. Maybe this should be a constant somewhere?


@taion Fair enough, sorry I wasn't aware of the other conversations I was just throwing in 2c. Nice addition BTW.


>That's a HUGE amount of damage, You sure?

Oops, typo. Sorry, haha.

Change it to: [Poison Effect] 2% chance to inflict a total of 6165 damage to an enemy over 10 seconds


Rerolled in 3b11d86094f56d7bd3afefcceeff5ebe18d39a18 with better `alternate_names` handling (the stuff here doesn't add the current ISO name to the list of alternate names before comparing with the API's name).


@nathansh  I think the issue was that it is pulling 1.8.2 from wp as a fallback and 1.11.1 from the CDN.  Although maybe it is just a mis-labeling of `$ver`.


test: can we include the field delimiter `|` here to show that it is replaced too?  And similarly above that it is dropped? It could be separate tests, but as part of the existing tests would be fine too.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3652](https://teamcity.mesosphere.io/viewLog.html?buildId=68418&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:46


The path is:
/usr/sbin/fsck


I think the same - model form would be good idea.


Reviewed by Yanny


Exceptions thrown by hugsql are not handled or returned on the channel.

To be absolutely sure that you catch all exceptions, you would have to do something like the following:

```clj
(go
  (try
    (let [res (<! (some-db-fn db))]
      (if (instance? Exception res)
        (throw res)
        (println "Succeded: " res)))
    (catch Exception e
      (println "Failed: " e))))
```


@davidjbradshaw Yeah, it's ugly but it did fix the error.  I tried your suggested fix but I still intermittently hit the error.  Also, I applied the script to another iframed site (within the same host site) and saw the same issue, so I'm wondering if it might be a global issue and not specific to something weird we're doing in these sites.


It's useful for the Relay integration. I'd be a little bit wary and consider reaching out to us before using this API integration point, though. If nothing else I'd like to get a better understanding of whether there's a different abstraction possible for the functionality here. I added this more or less because I need it for the Relay integration - if there's some other general principle available, let's see if we can satisfy that rather than just my own requirements.


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


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


@reubenmoes yeah, looks like just a mislabelling.


I'm really looking forward to it!
It's cool to see how this stuff works, too, although I deal mainly with Python.


Godt poeng. Tror det høres ut som en god praksis å fokusere på å holde den
fila oppdatert og slutte å ta rollesjekk i controlleren.

On 5. november 2015 00.02.32 Kristandre <notifications@github.com> wrote:

> I security har vi oversikt over alle sider som krever spesielle
> rettigheter. Jeg synes at det å slette semester/stilling også burde stå
> der. Det skal holde å gjøre sjekk i kontrolleren, men det blir veldig
> uoversiktelig og tungvindt å sjekke alle funksjoner i kontrollere for å
> lete etter adgangsbegrensninger ved et senere tidspunkt. Faktisk så tror
> jeg vi burde fjerne sjekken i kontrolleren og kun bruke security.yml. Hvis
> vi har lyst til å endre rettigheter senere, så trenger vi kun å endre en
> linje i security, da trenger vi ikke huske hvilke begrensninger vi har
> gjort i kontrolleren
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/vektorprogrammet/webpage/commit/2fada3509baa0ef8d66b496a917c2846ab88a68d#commitcomment-14198145


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/89337003


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3656](https://teamcity.mesosphere.io/viewLog.html?buildId=68427&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:33


string.gubs! replaces the orginal variable as opposed to making a copy


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3658](https://teamcity.mesosphere.io/viewLog.html?buildId=68431&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Failed to create a directory Build time: 00:00:00


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3657](https://teamcity.mesosphere.io/viewLog.html?buildId=68430&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:37


#4399-ZoneSum-vs-VentilationRateProcedure-when-one-zone-has-zero-oa-requirement (rraustad) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (886 of 888 tests passed)

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


 -  Is the project relevant to what we’re doing in class?
Yes, it certainly is. I am curious myself what findings you come up with.

 -  Is there something that’s not obvious or not understood about their project?
No. Your code is very well commented and you do an extensive EDA process, so I think it is quite clear what you are investigating.

 -  Are you working on similar problem and perhaps could share your thoughts?
No, I am working on qualitative metrics myself.

 -  What do you like or find interesting?
I really like all of the plots / charts. The extensive EDA phase will prove worthwhile when you dive into a more model-driven approach.

 -  How are results validated / what could be improved?
It would be interesting to see a predictive model applied. I think logistic regression or KNN could be useful for this one. I also wonder if combining news data about the financial markets and using NLP to measure sentiment could be a useful driving force.

Also, I see you mentioned this in your code, but layering in other bits of world economic news could be to understanding the "why" around currency movements. Things to consider include Twitter data, stock prices, and oil / commodities prices.


*gsub!


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3659](https://teamcity.mesosphere.io/viewLog.html?buildId=68432&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Failed to create a directory Build time: 00:00:00


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3660](https://teamcity.mesosphere.io/viewLog.html?buildId=68433&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Failed to create a directory Build time: 00:00:00


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 3648](https://teamcity.mesosphere.io/viewLog.html?buildId=68413&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:01:08


cool

On Wed, Nov 4, 2015 at 3:15 PM, Ben Delaney <notifications@github.com>
wrote:

> This looks great! Is it ready to pull request, or are you still working?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GFUCABAM/statler/commit/9450a0394c3724db7edee040d5cfd0a74ed3c655#commitcomment-14198412>
> .
>


@joergoster I already tried th->completedDepth >= bestThread->completedDepth but aborted test early since it didn't meet the idea logic of selecting the deepest thread first and then best score. http://tests.stockfishchess.org/tests/view/563780b00ebc59227df16ddc


Amazing job on this assignment! :+1:

#FEWD Week #5 Project: More JavaScript

---

###Description

JavaScript is powerful: we're able to take user interaction and information and use it to update the page without requiring a refresh. This week, a new startup in your city, CitiPix, is looking to create a personalized picture app that allows users to store pictures they've taken around the world and quickly access them by typing in keywords or tags associated with each photo; they have asked for your help to start building the front-end prototype. You will begin by building a web-app that will take a user's input and update the background image of the page based on that input. Once again, you have been given the starter code that includes the HTML and the CSS. Use the images in the image folder and write JavaScript to make the background image reflect user input based on the Technical Requirements  below.

|                                                                                |                                |                        |                          |
|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------|--------------------------|
| Technical Requirements                                                                                | Does Not Meet Expectations (0) | Meets Expectations (1) | Exceeds Expectations (2) |
| Call ```$.val()``` on inputs to get the string value of your user's input                                                     |                                |                        |                   x       |
| Store user input in ```var city```                                                                                |                                |                        |                x          |
| Use $.on(submit) or ```$.click``` to figure out when the user clicks the "submit" button                                      |                                |                        |         x                 |
| Create ```if / else if / else``` conditionals to control the flow of your application                                         |                                |                        |              x            |
| Write at least six different lines of pseudocode and display them inline as JavaScript comments                               |                                |                        |                  x        |
| Prevent a form submission using the ```event.preventDefault()``` function                                                     |                                |                        |            x              |
| Use the ```$.ready()``` handler to delay your code from executing until all DOM assets have been loaded                       |                                |            x            |                          |
| Use the ```||``` operator in your conditionals to allow for multiple string values to execute ```if/else if``` statement code |                                |                        |           x               |
| If a user submits "New York" or "New York City" or "NYC" make the background of the page nyc.jpg                              |                                |                        |             x             |
| If a user submits "San Francisco" or "SF" or "Bay Area" make the background of the page sf.jpg                                |                                |                        |             x             |
| If a user submits "Los Angeles" or "LA" or "LAX" make the background of the page la.jpg                                       |                                |                        |           x               |
| If a user submits "Austin" or "ATX" make the background of the page austin.jpg                                                |                                |                        |        x                  |
| If a user submits "Sydney" or "SYD" make the background of the page sydney.jpg                                                |                                |                        |       x                   |
| TOTAL: 26/26                                                                                |                                |                        |                          |


Will do...I will re-submit after


Published!


This commit is a great patch to have in the official MacPorts port. Although this may not be the right place to ask, I'd really appreciate if this commit is patched into the port so that I can debug without seeing tons of 'alloc_size' warnings. I have already filed a [trac ticket](https://trac.macports.org/ticket/49590). Thank you for reading this.


I don't agree with the "synchronised". I would have said HeartbeatGracePeriod should be greater than the interval.


No real reason...I had read somewhere that using em is better than using px but not sure if that's true. And as you can see, I use a mix of both! As for the %, I probably should have just used a px or em value.


fast-forwarding master to auto = 924ad4bb


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


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


Well, this explains the phantom build failures in the original XD


Still not aligned.


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


Sorry, I fixed it.


inlet seems to need some more attention in the patcher code which made me see the outlet could be done better as well. investigating.


Fixed. Thank you.


I think these are dead now.


"Package quad provides numeric integration of single variable functions by quadrature."


Nice.


This function could use map instead of forEach since that looks to be the intention:

    function createStudentRecords(records) {
      return records.map(function(record) {
        return {
          studentId: record.id,
          lastName: record.last,
          firstName: record.first,
          active: true
          // get school attr here
        };
      });
    }

The other option would be to create a function that returns a single record and use that for a callback:

    function createStudentRecord(record) {
      return {
        studentId: record.id,
        lastName: record.last,
        firstName: record.first,
        active: true
        // get school attr here
      };
    }

then use it like:

    records.map(createStudentRecord);


format: include `import` in the name of `hiveDelimsReplacement`, like above.


Missing `;`


Can I put "(numeric integration)" after that?


Same as above using map instead of forEach.


At some point I'll also reference the bot.config to ignore any bot names rather than hardcoding them here.


It's in the first five words. I think this wording is way simpler, but I'll leave it up to you.


Sorry. I'm an idiot.

Done.


My pyeq2 library is more properly listed under the "Numerical Analysis" section than the "Math" section.


Looks good, go on and add it.


I'll even fix the spelling of Tolerances.


What is this for


Windows 8 64 bit,
OBS v0.656b - 64bit

sad but i try to install your fork but it is still just freezes on StopRecord when i am not streaming and just recording video into file.


Fixes issue #169


document: `witha` -> `with a`  and  `/n, /r and /001` -> `\n, \r and \01`


Vou mostrar o @Url.Action amanhã, mas se quiser já pode arrumar aí pra location.href='@Url.Action("Relatorio", "JogosDisponiveis")'


unifique el repo base que se habia creado automaticamente con el de la catedra


@Isabelle1512, @nicoleslaw, @meiqimichelle I didn't make the final content changes for the involved section because it meant adding a footnotes section, which seemed like it was pushing the scope of that set of changes. I'm sorry for the confusion. As Michelle said, I am tracking my changes to that particular area in #703, so changes to that section will likely be overwritten when I do add content.


Yeah, I think it looks good. Best we do a pull request have everyone code review to make sure before merging


By convention the name of the services are capitalized. See `User` and `Auth` services.


This was done by me before the accounts were created


Can I suggest replacing
```
        path_str0 = displayable_path(task.paths, u'\n')
```
with
```
        path_str0 = os.path.basename(normpath(displayable_path(task.paths, u'\n')))
```
to make the import task path only display the last part of the path?


hi - nice to see this getting used!
one thought; the tint colour can be done without needing to change the pod. You just use the appearance proxy, e.g.

    //selected text
    [[UISegmentedControl appearance] setTitleTextAttributes:@{NSForegroundColorAttributeName : [UIColor redColor]} forState:UIControlStateSelected];
    //not selected text
    [[UISegmentedControl appearance] setTitleTextAttributes:@{NSForegroundColorAttributeName : [UIColor greenColor]} forState:UIControlStateNormal];
    //background
    [[UIImageView appearanceWhenContainedIn:[UISegmentedControl class],nil] setTintColor:[UIColor blueColor]];


this was done by cwm262 (Cody) before the accounts were created


This comment makes it seem like it applies to `this.list = function() { ... }`. Let's remove it.


This is very much a work in progress. The UI works but the BE is not refactored and there's no communication yet. If you want to build to see where the UI is at, don't forget to run bower as there are some new dependencies (angular-xeditable and ng-tags-input).


Vou mostrar o @Url.Action amanhã, mas se quiser já pode arrumar aí pra $(location).attr('href', '@Url.Action("Relatorio", "JogosDisponiveis")');
Isso vai prevenir que teu link quebre caso haja alguma mudança de rota.


@pivotal-plech I think it's funny that this was committed on master


I couldn't seem to get this to work for some reason(+Pic.Draw (mo,0,0,picCopy)) .


Aqui é melhor usar @jogo.Preco.ToString("c")
Ele vai botar a moeda da cultura da tua aplicação, no caso de pt-BR vai botar 'R$', além de formatar as casas decimais


@tarcieri @digitalextremist Is this `@sync_proxy` just a remnant of a previous implementation? Can this be safely removed?


you need to have the logo saved on your harddrive in the same file as cyoae. i will update it in a moment :octopus:


Vou mostrar o @Url.Action amanhã, mas se quiser já pode arrumar aí pra href="@Url.Action("Relatorio", "JogosDisponiveis")"

Isso vai prevenir que teu link quebre caso haja alguma mudança de rota.


Not sure why we're using release tars here instead of the API_VERSION.


ToString("c") vai ficar melhor :)


No idea yet about other platforms - for now I'm just trying to implement the dicom plugin support.  Once I configure I can build and test the modules in the build directory.


since SV is now an interface, can we rewrite the fakes to not require an external script?


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


Since F21 is the N-1 release that currently has a box we should keep it as well


fixes #304 #271


test js push and commit


Não é que esteja errado, mas aqui eu não usaria o string.Format. Prefiro deixar minhas views mais "HTML" possível. Ou seja:

Quantidade total de jogos: @Model.NumeroDeJogos


At the time I switched from chef-ha to chefdk this was not available for all tested platforms.  have you confirmed it with a kitchen test of all platforms?


Saw the later commit.  Ignore this one


Bala, vlw :) Só tive que inverter ali, ficout tipo @Url.Action("action","controller")


#Contato
tiago.miserani@gmail.com


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


谢谢关心啦～看完这几个GitHub通知就去睡啦～


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


This will construct a cons list of Python strings, not Racket Path objects.


Hi Matthias,
   Thanks for looking at this.  This pull will certainly fix the pom issue, but I would imagine that GraphicsExportPanel.java (which specifically imports lowagie) will break.  In order to move from lowagie/itext to itextpdf, I think we'll need to update that module also.  Want to tackle that?

-- scooter


[![Illustration for Canto XI of the 'RubÃ¡iyaÃ¡t of Omar KhayyÃ¡m'](http://api.artsmia.org/images/2536/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=2536)


[![Shepherdess and Sheep, Fontainebleau](http://api.artsmia.org/images/5925/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=5925)


[![Still Life with Pascalâs "PensÃ©es"](http://api.artsmia.org/images/6359/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=6359)


Usa aqui o ToString("c") pra exibir no formato currency


should be different from NONE


Oi,

Se um método ainda deve ser implementado o mais correto a fazer é:

```
throw new NotImplementedException();
```

Aí não corremos o risco do código chamar este método e seguir silenciosamente sem erros.


Wow, no kidding, that is old. OK, I'll see about getting this updated.

I think part of my problem is sleep deficiency, it's archery deer season and since the time change here in the states I have to get up at 4:30am and never seem to get to bed much before midnight.


essa lógica não faz sentido.

Vale mais a pena vc deixar o if logo abaixo mais simples e colocar um comentário ```// TODO: verificar quando iniciou eleições``` do que já deixá-lo confuso desde então...


Line `<!--Search Page Msg-->` went from `<p>` to `<h1>` so this was needed.


This database provides statistics for words and nonwords of Mandarin, Chinese. Lexical statistics include subtitle corpus frequency, phonological neighborhood density, neighborhood frequency, and homophone density. The accompanying word descriptors include pinyin, ascii phonetic transcription, tone, syllable structure, dominant PoS, and syllable, segment and pinyin lengths for each word. It is designed for researchers particularly concerned with language processing of isolated words. The database is divided into multiple files according to the desired search criteria: 1) the syllable segmentation schema used to calculate density measures, and 2) whether the search is for words or nonwords.

The database is made of 28 files, organized according to words with tone, words without tone,
nonwords with tone, and nonwords without tone.
Words with tone files: C_V_C_T, C_V_V_X_T, C_V_VX_T, C_VVX_T, CV_V_X_T, CV_VX_T, CVVX_T
Words without tone files: C_V_C, C_V_V_X, C_V_VX, C_VVX, CV_V_X, CV_VX, CVVX
Nonwords with tone files: The same as words with tone plus "nonword_"
Nonwords without tone files: The same as words without tone plus "nonword_"

Key: The database was made according to phonological words. Therefore, in each file the "Key"
column features the phonological words from which all phonologically related manipulations
were made. The phonological words are in sampa. See the Dictionary.txt for help in
translating Sampa-IPA-Pinyin.

PY+T: pinyin plus tone

Pho+T: phonological word plus tone

PY-T: pinyin minus tone

Pho-T: phonological word minus tone

Tone: tone number

SyStruct: syllable structure according to the CVVX system

SyLen: syllable length

OrthLen: orthographic length here refers to the number of pinyin characters per each word

PhoLen: phonological length

FreqPM: frequency per million adapted from Cai & Brysbaert (2010)

Words: words in simplified Chinese character form that correspond to the phonological word
presented in "Key"

HomoDensity: homophone density

Dominate-POS: dominant part of speech

Freq-Dominate-POS: frequency of the dominant part of speech

Percent-Dominate-POS: the percent for which a words is a assigned a given part of speech
in comparison to to multiple part of speech assignments

Other-POSes: the other parts of speech assignments that were not of the highest percentage

Num-Neighbors: the total number of phonological neighbors after calculating the
replacement, addition, and substitution of a single phonological unit

R-Neighbors: number of replacement neighbors

A-Neighbors: number of addition neighbors

S-Neighbors: number of substitution neighbors

Neighbors: all phonological neighbors presented in sampa

Freq-Neighbors: the summed raw frequency of all of the phonological neighbors


You're ambushing deers in your ghillie suit at 4:30 in the morning? :open_mouth:


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


Paragraph spacing. Dunno why I waited so long to do this.


:warning: :warning: :warning:

Eu e o Ben Hur estávamos olhando teu código e ele fez uma observação pertinente: este WHERE concatenado sem espaço não vai funcionar.

mais atenção @dodireis !

:coffee: :coffee: :coffee:


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


ce n'est pas*

wow, my french is really rusty.


Moved MaxPressure into EasyTabContext because Pressure ranges from 0.0f to 1.0f
It is useful only in the context of handling events when it does the divide.


Cara isso tá ruim.

Essa query tá 98% igual à query no método de cima.

Duplicação de código não @ericgottschalk !


Yeah, I'm trying to conserve antibiotics by only eating free range meat., ha!


The sample code in the comments already does this, but having the EasyTab structure right at the top, instead of after pktdef and wintab, makes things more readable.


:+1: :cake:


OK, so include what can be included, then exclude the locations that match the ignore checks.


cara esse lance de chamar `ToList` antes de fazer a cláusula de busca vai te trazer problemas no futuro.

Faz primeiro o predicado da busca, e por último chama `ToList`, ok?

```
return this.Get().Where(_ => _.Name.Upper().StartsWith(name.ToUpper()));
```


어메이징 어메이징 :dragon_face:


OK, basic `os.walk` implementation.


Renamed because EasyTabContext->WintabContext is less confusing than EasyTabContext->Context


Arrrg,
503 trying to pull from GitHub.


There's a minor outage: https://status.github.com/messages

Can you see the homepage of this project? I can only open issue pages currently.


thanks


卧槽之前没注意。。大哥你怎么把 PDF提交上来了。。这是要被举报的。。


this is its own command to avoid a cyclic import, do we want a new sub group for it?


要全部改回去 希奧利艾 (遠目


Nice slogan! heuaheauiheiaha


Considering this is only to locate tests and not inspect the test contents in any way, looks OK to me. My worry is about files without extensions (I guess they would be executed as `SimpleTests` anyway.


Put in the wrong comment, User can now have a balance.


>21:00 CSTMinor service outage.

I'm not sure what qualifies as minor when your trying to get updated.


Same here.


mesma coisa de cima:

```
return this.Get().FirstOrDefault(_ => _.Id == id);
```


Thanks @frankdiox ! Forgot about this :)


Comentario. Prueba para ver la integración con Telegram.


Huh, I guess this is a pythonic replacement for `touch file`. Nice, a new trick to put on my sleeve (my first instinct would to open a file and then close it).


pq buscar por vazio?

se realmente quiser isso, prefira o uso de `String.Empty`.

Motivos: legibilidade e semântica.


But for the "https://www.khronos.org/registry/cl/api/1.2/cl.hpp" ?


TeamCity libpalaso :: palaso-precise64-master Continuous [Build 3.0.535.1fa18c831f6f962bcf7e4dafc04153d152799d36](http://build.palaso.org/viewLog.html?buildId=65489&buildTypeId=bt322) outcome was **SUCCESS**
Summary: Tests passed: 3286, ignored: 106 Build time: 00:28:12


咦....没注意呢....然后要怎么办?


鸟哥威武


#missing code
puts @address_book.entries[selection]


Actually, it should be *radar_client* and later, when *radar* is ready, we can add that also.

Yes, consumers of APIs should update to newer API libs when they are available, and bump the consumer's version once the update is done.  We do this already with *radar* and *zendesk_radar*, *radar_client* and *zendesk_radar_client*.


Oi, essa variável `listaDeJogos` é inútil.

Faça o simples:

```
return ConsultarJogos().Where(j => j.Disponibilidade == "SIM").ToList();
```


As Models não devem ter referência para outras camadas, elas devem estar "blindadas" de que possíveis alterações em projetos externos (domo o Locadora.Dominio) afetem a view.


Btw, in your `master` branch, you have that 1 commit "Add tiedown support" at the top?


Nice


Ter a busca de dados aqui dentro também nao ficou legal (idem acima). Move essa responsabilidade pra Controller por enquanto. Essa view tem que ficar "purinha" sem referencia pra nada de fora.


Tá quase lá, continua assim!


Please check `carousel.js` against semi-standard linter and correct any problems. Specifically:

 - To avoid leaking globals please define `var yt_players` and `function setup_youtube_api` inside the containing [IIFE](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression).
 - Please use [camelCase for variable and function names](http://stackoverflow.com/posts/5640564/revisions).
 - Be expicit when declaring, defining or accessing `window`-level globals, so instead of `function onYouTubeIframeAPIReady () {` use `window.onYouTubeIframeAPIReady = function () {`, and instead of `new YT.Player(...)` use `new window.YT.Player(...)`. (Also - this event handler should be defined inside the IIFE.)


@Unknwon 不对啊..我记得我fork下来的时候 .就有那个原版的pdf了....不然我从哪里翻译的....


:+1: :+1: :+1:


:warning: :warning: :warning:

variáveis em C# são pascalCase.


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


s/OpenShift//


本软件主要应用于东华大学思政课题库复习。


@taylori Ian Stewart asked me to work up a data plot that has circles representative of the uncertainty of the data. I've created this branch to house this code thinking that it might be worth integrating in at some point.

Since this is my first commit can you have a look and see if this is a good approach? The code produces and plots a second data plot (data_plot2.png) by default, in addition to the original which is unchanged. This can be turned off by setting `datasize=FALSE` in `SSplotBiology`. I checked and the new file get's parsed correctly into the HTML page. Attached below are the two plots for a halibut model.

In particular I'm not sure if I should turn on reporting inside this function so the user can toggle between the graphical output by default.

![data_plot](https://cloud.githubusercontent.com/assets/4804974/10928736/420b607e-8260-11e5-960a-a2040be92c6d.png)
![data_plot2](https://cloud.githubusercontent.com/assets/4804974/10928735/420b1772-8260-11e5-83ff-1574c0041c18.png)


:warning: :warning: :warning:

Duplamente errado!!

1. Campos de objeto públicos? Nunca! Utilize propriedades com modificadores de acesso adequados para garantir o encapsulamento.
2. `new BaseDeDados().ConsultarDisponiveis()` está sendo chamado duas vezes para gerar o mesmo relatório (vide controller acima). Isso é **muito ruim**. Imagina se fossem milhões de registros que viessem do banco de dados?


83811630_ReheatCoilSizingImprove (rongpengzhang) - 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)


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


I should've known that one...fixed


@hasufell, sounds fine.  Shoot it over to tianon since he's the actual maintainer.


Um dia tu vai descobrir que `ToUpper` é mais custoso :stuck_out_tongue:


Yeah, I suppose it should be (sd > 2) in case someone passes /proc/self/fd/0... looking again, this coverity warning seems like a false positive in this case.


。。。。。提交记录显示你添加的。。我已经先删了。。


Olha que coisa bizarra:

1. Dentro do método `Get` você declara a variável de retorno como `new List<Game>` (veja aqui: https://github.com/ericgottschalk/crescer-2015-2/commit/db4bd9d3fb2a8a1f0c88ae46388fa58ef8ce4157#diff-981385a0d758845bb0f0e74280ecd2ebR25).
2. Fora do método `Get` você tem que converter uma variável que você sabe que é List<Game> com `ToList` :stuck_out_tongue:

Sugestão: altera a assinatura deste método `ObterJogos` para `IList<Game>`


ok.....下次提交 ..我会注意的......


o `Max` é bacana, mas você poderia matar tudo em um lambda só:

```
return lista.OrderByDescending(_ => _.Preco).ElementAt(0).Nome;
```


A model não pode ter referência para o teu dominio. O ideal (pro ponto em que estamos) é fazer essa busca na controller e popular a model. Os campos da model devem ser um espelho dos dados que tu quer exibir na tua View. Ex: se na tua view tu quer exibir um "Total de jogos disponiveis", tu vai ter um campo int na tua model chamado TotalJogosDisponiveis.


Hey, this commit breaks a few things.

By forcing everything to have quotes, you're assigning values where they shouldn't be. You can generally get a good feel for what's working/broken by running your changes through `widget_demo.py`.

Things to note:

1. The Required Arguments check no longer works since everything receives an implicit quote `'""'` and thus has a "value" of sorts.
2. Choosers in the `optional` section now break for the same reason. Because they have a value, they pass the `self.option_string and value` test and end up generating a command line arg like `--flag ""`.

>MultiDirChooser and other similar Payloads store not a part of a command but a list of paths separated by a os dependend path separator.

All of the Choosers can be used as Optional values. So, they _do_ function as a command in that sense. They also need to honor things like `nargs` and what not, so we shouldn't over-specify their behavior.

Finally, I really like the introduction of a command field that doesn't apply quoting! However, I'm not sure what the rest of the quoting changes are solving. Could you elaborate?


:trollface:


mixing --confirm, --additive, --definitions, and --overwrite-priorities is confusing. As much as I'd love symmetry with the other commands, would these be clearer:
```
--confirm (defaults to false)
--reset-definitions (defaults to true, sort of the point)
--reset-priorities (defaults to false, leaving set priorities alone while setting any unset ones)
--reset-subjects (defaults to false, leaving existing users and groups while adding new ones)
```


bugfix :/


No, any suggestions. I think it might be best if I just re-clone the repo.


@Unknwon  我找到记录了... @leisore 同学...


Ok, maybe better to do that.


pq não fazer mais simples?

```
return lista.Average(_ => _.Preco);
```


of course a macro is also acceptable

- 发送自我的Sony Xperia™智能手机

---- Mingye Wang编写 ----

bugfix :/

---
Reply to this email directly or view it on GitHub:
https://github.com/AOSC-Dev/autobuild3/commit/00d092165283813841aed239df62d007266637ea#commitcomment-14172972


nah, I agree with you.  This shouldn't reference OpenShift for AEP reasons


Can you see my commit in https://github.com/Juanvvc/c172p-detailed/issues/499 ?


For bash, no. If you want macros, use aliases.


Sua lai sql cua Rule


Fiquei curioso com o que esse relatorio.GerarRelatorio() ta retornando.


# Related Posts
I'll keep saying this as it comes up but the related posts widget I was using died. And the other related posts widgets out there are riddled with spam and advertising. It's not worth it to me when I have no control over what's displayed on my own site.
# Share Buttons
For as long as I've had integrated share counters and whatever they've seemed to do more harm than good. All the counters do is show how *LITTLE* visitors re-share my content. And for the privilege of this public shame I slow the site down with unnecessary JavaScript calls.

I don't even use the share buttons on *other* people's websites! Why should I expect any different from *my* visitors? When I want to share something I just copy the link from my address bar. I mean, that's how I've been doing it since the 90s, why change now? And when I'm on mobile I share from the universal share function in Android. I imagine IOS also has an OS-level share feature. So why are we putting these beacons and trinkets on our sites that do NOTHING for us except give free analytics to random social networks?

It turns out there's been some research done on all this. See also this great post by @dkutcher that collects several articles on the topic.
* [No hyperbole - this article might change ALL of your assumptions about how social sharing relates to your SEO and content strategy](https://plus.google.com/+DavidKutcher/posts/PWhVjBV422Z)


Note to all actively participating members: please come Thursday as we have a competition coming soon!


哈哈！好吧。。罪魁祸首。。莫非是间谍？


I scratched my head as to why this is a good default.  I couldn't figure it out from reading the help.  I then came here to see the commit message, slightly more enlightening, but only barely.  I feel like reasons for picking these defaults should be commented in the file.


Interesting. I think that when an independent reader sees something like `` `Python_daemon`` it would just raise lots of questions that we're not prepared to answer. But you do make a good point. Any thoughts @ihodes ?


+1 for cleaner language.


I'm with @smondet here; Python is (fortunately) everywhere, so this works no matter what. I agree the name is confusing, though; can we change it (or at least have an alternative, e.g. `\`Daemon`.)?


I followed the EzeeGit tutorial this time elie !
( ok , the autosave was added , but it could have been worse , remember .... eh eh )
^^


![untitled](https://cloud.githubusercontent.com/assets/14340184/10928961/a809a3d2-82be-11e5-8853-6068b284ea0c.png)

Please change the code to change the image


@liushuyu Refer to https://github.com/AOSC-Dev/aosc-os-abbs/issues/114


`--infrastructure-namespace`


Unsupported pawns (including isolated, backward, some doubled pawns, some passed pawns, all second rank pawns, some pawns in a phalanx...) are statically evaluated in pawn.cpp and have at least a S(20, 20) penalty, and some adjustments.

Some pawns can simply not be attacked, due to blockage, or shielded by pieces,
or absence of Rooks, etc.
In this case, they would not be that weak...

Many subtle things could be tried.
Here, as a first attempt, I try a crude compensation:  if not attacked in current position, adjust by S(10, 0).


@MingcongBai The actual problem here is I (as the seem-to-be most active libarch editor) still can't find out an elegant way of doing so, and if I keep this I am almost fscking myself…


Good talk.


>Pedals is showing as changed on a fresh pull.

That one?

No but I don't think I have pulled since you did that.


entries = @address_book.entries
#entries == [entry1, entry2, entry3]
#entry1 == {name: 'Adam', email: '...', phone: '...'}
entries.each do |entry|
  if entry.name == zebra
      return entry
  end
end


Fixes #114 #114 #114 #114 #114 #12580 #12306 #116114 #chinatelecom


I meant a comment in an issue. But never mind.


Consider what "count" means: It counts! So, if you "count" the stooges, you should get "Three". Rather, what you actually want to do is add (or "sum") the percentages. I hope this helps! @KariWomack


This is very nice !:)


I saw the one in #498


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


CXX. C Preprocessor optimization levels doesn't matter that much…


Excellent, thanks for checking. I'll use that.


Have you looked at VectorTools::integrate_difference? Maybe you could use it to make your error calculation much shorter...


it is not good


Move to deal.ii (see Wolfgang's comment in the .cc file)


@JeromSar it won't compile. I'm getting errors with banning


View, edit, create, delete all work through API, but the short url has to be manually entered currently. The only part of normal mode for urly-bird-api that's not here is the user's overall stats page which I don't remember doing on the original urly-bird project.


Split into several functions?
Discuss if this should be moved to deal.ii when finished.


There should be a function in deal.II's GridTools namespace (see Wolfgang's comment in the .cc file)


看一下 nginx.conf 辣
```
server
    {
      listen 80;
      listen [::]:80 ssl ipv6only=on;
      server_name example.com;
      return 301 https://$host$request_uri;
    }
```
并没有在nginx.conf引用这个文件的说，所有80的请求都被301到443了，这个文件只是给那些有80需要的人喵~


I think I'd rather make the infra ns be input to `bootstrappolicy.GetBootstrapSCCAccess(ns)` and let it add the build controller... I'm not sure we'll ever make all those individual service account names configurable... if we do, we'll have more work to come back and do here and in reconcile, so let's not overcomplicate it now


Same as for get_patch_around_cell.


You can try to pull again. Strange pieces of wood:

![fgfs-screen-288](https://cloud.githubusercontent.com/assets/3361585/10929131/021b14f0-82b0-11e5-838c-20041111681a.png)


Durrr, related posts.


Move to deal.ii (Wolfgang's comment)


rather than jump through hoops to make this shared, I'd rather just add a comment here that if we make these individually configurable, we also need to update the reconcile command and the `GetBootstrapSCCAccess` function... I'm not sure we ever will


Vishi. Como assim? Vou renomear o método.


lol


chane password


I really want it under policy... if it doesn't have to pull in master config and can just reference bootstrappolicy, is it still cyclical?


This status message is now the headline on search pages. It just makes semantic sense.


So i was on master , done a checkout to accessibility again , worked on it , then .add , commit , checkout
master , merge accessibility , push

your method rocks elie !


This map is not changed in this function, I think it can be marked as const.


One thing I forgot yesterday: `cabal-rpm install <package name>` installs packaged Haskell dependencies automatically.


83811630_ReheatCoilSizingImprove (rongpengzhang) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (887 of 887 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-24.58%25-green.svg)


Discuss whether this could be moved to hp::DoFHandler or Triangulation


Ok, cool.  If I can rely on the constants I can eliminate a lot of the refactorings.


Yeah, I think it was a problem with some script, not the CSS :P


kljlkjkl


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


Is this function only here to check your patch routines? Or is there any reason to output single patches later on?


Cloud


鸟哥威武


For a longest time I've been trying to figure out the right combination of [escape codes](http://www.theukwebdesigncompany.com/articles/entity-escape-characters.php) to make this work. It was only after stepping away—*for several years!*—then coming back that I figured it out. Coding is funny like that. And while I'm aware of `numPosts`, I feel like this is the best way to determine a failed search. Also for the amount of work I had to do you bet your ass it's staying!


test from javascript


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


Is this comment still necessary? It sounds like it is written for a very particular case.


But I can also add a separate PR for mentioning `cabal-rpm`.


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


Talked myself out of it in the following order:
1. We can't easily reason about these if we don't reset definitions (I don't want to implement covers() on these tonight)... adding users we care about to SCCs we think grant certain permissions without ensuring that is silly.
2. If the only things we'd let them preserve were custom priorities and custom users/groups, that falls more easily under an `--additive-only` flag


103643052-FiniteDifferenceFluxOutput (mjwitte) - Win64-Windows-7-VisualStudio-12: OK (1952 of 1961 tests passed)

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


Super good work. That was sorely needed.


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


鸟哥V5


please don't spam commits,  too many users watch this repo, thanks


This was only supposed to trigger on failed/no result searches. But it didn't really work out that way. `<b:if cond='data:olderPageUrl == data:newerPageUrl'>` means it basically triggers for *any* search with one page of results. I needed to fix that. Also maybe the text was a tad negative so I wanted to change that too. I'm not trying to throw shade at Google like that. I'm happy with Blogger, for the most part.

But what I said about the search *is* true. The caching is limited and unpredictable, ESPECIALLY if you use the scheduling feature. I wouldn't use it if I were you. Be warned!


In principle this functionality should be moved to deal.ii. Discuss how the function should look like and which arguments it should have!


这个提交之后，ProgressBar就几乎看不到了


Nice


I left it like that, @gilbertohasnofb is going to do the select animation coding. I just selected it so I could see it when I was working on it. We made those for the 26" and 36" wheels.


I pulled and all is well, thanks.


This routine is now an `<b:includable>`. I'm turning `Blog1` into a more modular system. Should make this section easier to read as well.


@pmorie, are SupplementalGroups and FSGroup something we expect will be customized from the default SCCs we provide?


I appreciate the motivation here, but I hesitate to create some dependencies on `Data.ByteString.Internal` functions. Perhaps there is a way to get the performance benefit just utilizing the `Data.Text.Lazy.Builder` API?


You should use script.getColor cause sys.getColor makes some colors appear as black :D


I might add it back later but I don't see `~expired_event` getting used any time soon.