TeamCity MahApps :: MahApps.Metro PullRequests [Build 1.2.1.24](http://builds.brendanforster.com/viewLog.html?buildId=398&buildTypeId=MahApps_MahAppsMetroPullRequests) outcome was **SUCCESS**
Summary: Running Build time: 00:00:35


Looks like a difference between 5 & 6. Babel wiped out their issue tracker, but here's another project with same issue: https://github.com/phoenixframework/phoenix/pull/1332


is this something that is broken in dgtoolkit too ? if so pls commit these changes to the dg-toolkit project, then ill merge them. so by doing so we'll create a clean template to start stuff from. tx


P.S. next time just do "commit --amend" and "push --force" :)


Why you are using fork of `https://github.com/fsouza/go-dockerclient` not repo itself ?


Noooooooooo I though it was for real!


Again, for `filter`, it would be good to see more usage of that value to ensure it works as expected.  In this case, I would probably use the examples directly from the documentation:

```js
var fn = mm.filter('*.md');
['a.js', 'b.txt', 'c.md'].filter(fn);

fn = mm.filter('[a-c]');
['a', 'b', 'c', 'd', 'e'].filter(fn);

var arr = [1,2,3,4,5,6,7,8,9,10,11,12,13,14,15];

fn = mm.filter(['{1..10}', '![7-9]', '!{3..4}']);
arr.filter(fn);
```


The best workflow for now (unfortunately) is this:

1. From your PowerShell console in the vscode-powershell directory, type `code --extensionDevelopmentPath="c:\your\path\to\vscode-powershell"`.  A development version of VS Code will appear with your current code loaded.
2. Type `npm run compile`.  This will build the code and wait for any further file saves then it will recompile again.
3. When you make changes to the code you can press the `Ctrl+R` hotkey to have VS Code reload itself and pick up any changes you made to the code after they are recompiled
4. In your code, you can temporarily call `window.showInformationMessage` to make some text appear at the top of the VS Code screen.  This might be helpful for seeing the state of your variables while you're working out the details of the function.

I really need to get some unit tests set up so that we can test functions like this without having to run the extension.  This is the first time I've come across something that would have benefitted from it.


Could you please add a ```typedef struct _PyFrameObject PyFrameObject;``` and keep the ```PyFrame_GetLineNumber``` arg type as ```PyFrameObject```


Do not use  uppercase (floor'T'ype) in package name


Not to my knowledge (and I am using websocket-fork daily). I hope that Moxie requested this only for statistical purposes, but I would be lying if I'd tell you that more evil variants didn't come to my mind ;-)

Open Whisper Systems can eliminate all websocket users from their servers anytime they want with this (but on the other hand, they can do it even without different USER_AGENT, it would just be little more difficult).


That was sloppy. New personal rule: don't push code past my bedtime.


Great. Thanks for pointing that out. I did the first few manually and it
already proved useful! --J

On Thu, Jan 7, 2016 at 9:02 AM, Tony Kelman <notifications@github.com>
wrote:

> Enabled. Did you trigger the first few builds manually? For what I did to
> the webhook, see JuliaOpt/JuMP.jl#362 (comment)
> <https://github.com/JuliaOpt/JuMP.jl/pull/362#issuecomment-70610293>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/JuliaLang/Roots.jl/commit/da017b2cc7b11c493f902d6245de8985b40ca19a#commitcomment-15316331>
> .
>

--
John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
verzani@math.csi.cuny.edu


Rename it as FloorTypeService


@hannesj your observation is totally valid. Let me explain why I put the `stop` as prefix.

I was using pelias to feed the From/To fields on a OTP client (via autocomplete API endpoint) but my pelias has indexed other type of places, which in some cases match with the name of stops.
so, basically the intention of the prefix is that you as a user can get the stops as results if you start typing `stop`.
I understand that you may not need this behaviour so I would propose that the prefix addition be optional and we could make it configurable through a command line argument.


For readability, this would be nice.


If we remove the `readwrite` redeclaration then we'll need to add an explicit `@synthesize`. Otherwise we won't get a backing ivar because we are overriding the getter of a `readonly` property.

I'm inclined to keep the `readwrite` override because it expresses the semantics I want: that this property is okay to set internally.


I was thinking more along the lines of leaving it be a dictionary, keeping this code the same, but generating the dictionary with a function like this:
```python
def make_module_dict(modules: list) -> dict:
  ret = dict()
  for m in modules:
    name = '!' + m.__name__[len(m.__package__)+1:]  # I'm gonna trust you on this one,
    ret[name] = m                                   #I don't know what __name__ returns exactly
  return ret
```

The sole purpose of this function being having the ugly hack that is necessary to do this out of sight, and having the main file be less imposing to read. Yes/no?


@dillaman If the async read returns an error,  "r" will be set but "err" may not be set if none of the BufferHeader in this range(start, length) was previously marked as error, and thus the callbacks(contexts) may be executed with the result code "err" which may not actually reflect the real async read result.


See note on line 11 about assigning the result to a `boolean` variable to ensure return types don't get changed in the future.


close #6


Sry, I fear I don't understand that last comment.

The only thing the compile check does is that it provides an additional mandatory check that should pass in order to set SHAIRPLAY_FOUND, right?
Then can't we just remove lines 24-26 and add HAVE_SHAIRPLAY_CALLBACK_CLS to the required vars of FPHSA? Then if the code does not compile, FPHSA would set SHAIRPLAY_FOUND to false and tell us that HAVE_SHAIRPLAY_CALLBACK_CLS is missing.


For some reason it wasn't working for me. I just found out it is a Python 2/3 thing. In 3, range is equivalent to python 2's xrange. Whereas there's no xrange in Py3.

Hmm, I'm sorry about that. I didn't know about the change. Should I simply revert it? Or could I add something like this below?
```python
try:
    xrange
except NameError:
    xrange = range
```


Looks good to me (the king of typos).


there are 3 cases

1) shairplay not found
2) shairplay found, no HAVE_SHAIRPLAY_CALLBACK_CLS
3) shairplay found, HAVE_SHARIPLAY_CALLBACK_CLS

both case 2 and 3 shall pass.

On Thu, Jan 7, 2016 at 3:41 PM, Christian Fetzer <notifications@github.com>
wrote:

> Sry, I fear I don't understand that last comment.
>
> The only thing the compile check does is that it provides an additional
> mandatory check that should pass in order to set SHAIRPLAY_FOUND, right?
> Then can't we just remove lines 24-26 and add HAVE_SHAIRPLAY_CALLBACK_CLS
> to the required vars of FPHSA? Then if the code does not compile, FPHSA
> would set SHAIRPLAY_FOUND to false and tell us that
> HAVE_SHAIRPLAY_CALLBACK_CLS is missing.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/fetzerch/xbmc/commit/c40707e14d3eaa2bdd65aae3c5a88d57dea1317a#commitcomment-15317143>
> .
>


done


Yeah, I wasn't thinking.


Thanks for the changes. I think these will work.


this is only the html file for the client login page


```host_calls[__lkl__NR_##name]``` sometimes NULL when host system call is called in other constructor.

how about the followings ?

```c
if (!is_lklfd(p1))	 {
  if (!host_calls[__lkl__NR_##name])
     host_calls[__lkl__NR_##name] = resolve_sym(#name);
  return host_calls[__lkl__NR_##name](p1, p2, p3, p4, p5, p6);
}

```


Can we also disable `<select>` boxes until they have data to choose from?


are you about id or about position in the list?
i changed the position in the list to be the last one

if this is about id, are you sure that application id should be plain autoincrement number?


Please add a more descriptive commit message in future


It comes directly from Predict, and is this value:

https://github.com/la1k/flyby/blob/master/flyby.c#L5116

In Predict, it is given a different sign depending on the context (whether uplink or downlink frequency should be calculated). Either sign is "correct" since it is just a relative/meaningless factor later given meaning by either subtracting or adding to the actual downlink/uplink frequency, and depends on whether we see it from the point of view of the satellite or the observer. In my opinion, I think we should correct the conversion/interpretation of the factor in the testcase code, not adjust the raw data. :^)


Why do you need that?  Artemis is JMS 2.0


Octree (DeadParrot) - i386-Windows-7-VisualStudio-12: OK (1901 of 2009 tests passed)

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


Thanks for the notification!
I've just merged master with my branch. Indeed there were conflicts, but now it seems to work fine. I've added a new (abstract) RenderTarget class to manage rendering to a texture in order to avoid the "if(CVS->isGLSL()" conditions outside of the engine. So both m_new_rtt and oldRttProvider are replaced by m_render_target in my branch.


Yep... I was doing that... but it will be a nightmare with conflicts and to have both SPIDriver and SPIDevice to use the table. I'll take the other aproach: SPIDriver will later have its methods removed and then it will be turned into SPIDeviceProperties.


edek was here;


Uh oh...


Ah, it's the net35 build of the Ugly library.  Previously that one was built only for PCL profiles, but now there's a new net35 build as well, which, yes, should not have the PCL project type guid.  Fixing that.  Thanks.


Let's slow down with the javascript and finish the CSS portion first for now.

Okay, so we know that each of these `<td>` have a width of 90px. In order to do this in CSS, we can just do

```css
td {
  width: 90px
}
```


duplicated ?


I noticed you gave the table an ID! Perfect! We can scope this so it doesn't change the width for every table data cell, but just for the table with an ID of gameBoard.

```css
table#gameBoard td {
  width: 90px;
}
```


Was this change intentional?  It doesn't seem related to the bug fix and is a breaking change.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.1136](http://teamcity.monogame.net/viewLog.html?buildId=13439&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 560, ignored: 6 Build time: 00:27:54


I think I have the same feeling as you about this. I've always tried to declare variables before the statement, due to old MS VC doesn't support declaration-after-statement. Sorry that I broke it.

I didn't turn on as many warnings as you is that I need to build view, which has some warnings that I haven't got rid of, and so it could just issue too many warnings, if I use the same compiler switches as you do.

When I find time, I will try to clean up VIEW, and start turning on all of the warning switches.


issue #6 closed, but some more testing needs to be done


Good!


Alright, I'll have a look. (Although I think this case might be handled by the line above already.) Thanks!


Now what I want to do is move the background color logic into css since I notice a lot of repeats.

What we can do is

```css
.yellow {
  background-color: #ffff00;
}
```

Now we can call

```html
<td class="yellow">9</td>
```

It's basically the same as `<td bgcolor="#ffff00">9</td>`, but a lot easier to read.


Let's make the CSS changes first, before we move onto javascript!


> Use ロード instead of 再更新

Hmm, I really want to avoid having katakana all over the place... I did use セーブする though, so I guess ロードする works as well.

> Maybe 回転させる should be something like 回転中? Isn't this part to describe what the ride is currently doing?

That works for me, too.

> Use テーマ instead of スタイル?

I'm a bit surprised to see Mozilla using テーマ there, but I'll admit it is [more common](http://windows.microsoft.com/ja-jp/windows/themes) than I thought. Thing is, テーマ is also used to refer to *topics* in other contexts, so that's why I prefer to use the more unambiguous スタイル.

> 名前を保存 should be 名前を付けて保存

You're absolutely right, I'm not sure how 付けて got left out there.

@nickhall If you have time, please feel free to submit a PR with more translations. I don't have much time at the moment, myself, but the sooner we've established the basic translation, the better, I think.


This is in place so that the watch task only rebuilds the style files that have changed rather than rebuilding everything. I therefore don't want to remove this line.

What file is being missed out? I assume the script building works fine? I think more investigation is required as to why you are having the problem with Bootstrap style files missing rather than removing this line altogether.


"purposely" is the correct word for "done on purpose"
"Purposefully" describes the action or demeanor of a person who is determined or resolute.
Anyway, I think you can omit the word without a loss of meaning.


I'd chop "getter"


add newline above


the documentation shows an example that helps us know what the valid `options` are:

`options: { track: false, dot: undefined, makeRe: true, negated: false }`

More options can be gleaned from the code.

So perhaps:
```js
interface GlobOptions {
  track?: boolean;
  dot?: boolean;
  makeRe?: boolean;
  negated?: boolean;
  nobraces?: boolean;
  nobrace?: boolean;
  nobrackets: boolean;
  noextglob?: boolean;
  braces?: boolean;
  dotfiles?: boolean;
  dotdirs?: boolean;
  negated?: boolean;
  globstar?: boolean;
}
```


Nice :+1:

Does this always have to be "RefugeeTech" here -> Get another RefugeeTech developer to review your pull request before merging


@KimDahye  constant는 development.json에 뺄 수 있어. 해당 파일이랑 app.js 등 기타 파일 보는 게 좋겠다.


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 115](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=640&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **SUCCESS**
Summary: Running Build time: 00:36:42


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


Message is never echoed since script is run in -e mode.


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 116](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=642&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **UNKNOWN**
Summary: Canceled Build time: 00:00:16


Should we add a `FMSG` in this case?


Should we replace `0` by `TEE_SCN_RETURN`?


public function getDrops(Item $item){
return [
[$this->id, $this->meta, 1],
];
Really easy.


What does this first block have to do with VCL_DISAPPEARING_TYPENAME?


Danke für den Hinweis! Ich habe den Fehler gefunden und beseitigt.


Ah, understood the issue. Thanks.


formが大量にできてしまう事案が発生したので、第二引数でインスタンスを指定したら収まりました


That's one small **diff** for Android...


Awesome. I'll look into it.  I think the answer is a [haskell pandoc script](http://pandoc.org/scripting.html#include-files).  I'll also look into pandoc's syntax highlighting.


I agree, that G_LIKELY/UNLIKELY should be used with care. The patch should
be dropped, and I'll in the next iteration.

--
Bazsi

On Thu, Jan 7, 2016 at 11:52 AM, Tamas Nagy <notifications@github.com>
wrote:

> I'm not sure whether the compiler could really alter the instructions in
> this case, though I didn't give it much thought this time. You did note in
> person that the effects might have been small for this specific commit
> anyway.
>
> Actually my bigger problem with these in general is that if we compiled
> with profile guided optimization and ran through a dedicated quick test
> suite mimicking real world usage, the computer would deduce the exact same
> information. Maybe the existing stress/stability suites are good enough for
> this purpose, but I haven't looked into those yet.
>
> If you give it second thought, giving an executable specification in the
> form of real world tests is a higher level abstraction to this aspect of
> the code than micro managing the compiler. A higher level, cleaner, less
> complicated and less error prone abstraction to a problem is always the
> correct solution in my opinion.
>
> Of course, in this simple case, your assumptions look sane and reasonable.
> However, in general, you could just as well mispredict real world behavior,
> and usually only get too small of a penalty to notice and have little
> opportunity to fix. In that case, the G_LIKELY constructs are an eye sore
> and candidates for rotting in the future.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/balabit/syslog-ng/commit/a3798f9af3b855a723bc0cabfc87b585c6b813a8#commitcomment-15312936>
> .
>


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


I made several minor mistakes in the commits and you're totally right that I should have taken the time to fix them before I shared with everyone.  If I do it now though I'll need to rebase and force push pretty much the entire history, which is going to muck with all the comments we have been making.  My bad, and I'll try to do better in the future.


@Rush Don't use `^` in package.json.


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1462 of 1462 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)


Yes, will do.


Type of `options` return type should be `MicromatchOptions`.
Also, it would be better to create an interface for the second return type.  It would make this definition easier to read, and autocompletion documentation would appear nicer in the code editor.


Remove the first sentence about GQSS-3235.


for (FieldCell fieldCell : DBManager.getAllFieldsCells.values()) {

}


ACK.


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


No worries.  We all have silly habits, me especially.


`ispath(S.type, F.build_type) || ispath(S.build_type, F.build_type)`


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


the convention is to add a letter to the file name, e.g. patch_83_84_a.sql. The "a" patch is usually the schema version update, so you should be using "b" for this one. And also, tables.sql has to be updated too and the GeneTreeAdaptor must return the name of the table for the API to use this


How to build for android one mt6580 sir?? Please source for me
Pada tanggal 7 Jan 2016 10.00 PM, "Shimz0rd" <notifications@github.com>
menulis:

> That's one small *diff* for Android...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/CyanogenMod/android/commit/50be19e243383a442e90c7f7bed5a3842c66957b#commitcomment-15317639>
> .
>


Adding a `var` and type annotation here would be good.


No, because it can actually be negative (but there is a check a few lines above for that).


This is not necessary. Please see the previous commit f45f284 which removed this dependency as it was not used.


GHT_Bugs (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (2001 of 2001 tests passed)

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


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 186](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=643&buildTypeId=XbimEssentials_XbimEssentials) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:35


Oops...


@tych0 You are correct, fixing...


You've basically answered your own question, but to spell it out - this whole thing works because the joins are treated as a stack, and different layers of the stack don't interfere with each other. If your base entity is `Email` and you want to filter on or return the contact's emplyer's custom field, then you'd write

    'return' => 'contact_id.employer_id.custom_5'

and by the time this function is called we'd be 2 layers down in the stack and the `$baseTable` param would represent the 2nd time we've joined onto `civicrm_contact` but that's just a coincidence - the `getFkField` function doesn't care what's in the stack.


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 127](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=644&buildTypeId=Xbim_XbimExchange_XbimExchange) is now running


No capital e please.


@williewillus  WAIT there's a problem. Line 85 should be motionZ!


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 127](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=644&buildTypeId=Xbim_XbimExchange_XbimExchange) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:51


I went looking but I couldn't find anything on the machine. I know it nags the user before it quits.


There's something weird with the last sentence.


Introducing a variable with a type annotation would be good here for verifying the return type.  You can reassign it on line 7 as well.


What happens when I click on the notification sooner than this timeout launches?


are you kidding? that was a pretty egregious violation. Nice catch.


See note on line 139.


Do you have a reason to prefer the former?  My reasoning is given in [this commit](https://github.com/NoRedInk/ruby-style-guide/commit/16537adb474f459e8c3e63917137ab27a4e6c932).  I'm open to other points of view though.

To clarify, my reference to "our style" in this commit message meant _this style guide_, not _our application_.


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


What happens when I get more notifications while on background? Does the app with com.oney.gcm.GCMReceiveNotification intent got run more times? Does it combine well with the timeout below (what if I get another notification in less than a second, before `stopService` does its work)?


Pretty neutral about the opinion; I just didn't want to alter existing behaviour so took a monkey-patching route.


Correct. Thats what Block.php has by default. So theres no need to implement that to the flowers

> Am 07.01.2016 um 15:58 schrieb BlackShadow1 <notifications@github.com>:
>
> public function getDrops(Item $item){
> return [
> [$this->id, $this->meta, 1],
> ];
> Really easy.
>
> —
> Reply to this email directly or view it on GitHub.
>


reject if以下の記述を削除しました。
文章で説明するのが難しいのですが、edit機能のviewを作成する時に
thumbnailのsubが空のカラムで保存されていると都合が良いのでこうしました。

例えばcreate時
thumbnail_main 画像有
thumbnail_sub1 画像有
thumbnail_sub2 画像無
の場合、
sub2も空のカラムとして保存しておきます。
update時にsub2を投稿する場合、そのカラムにmain sub1と同様の処理をかけるだけで済むので
こうしました。


@nhpatt This is important: if all objects live in the same database, then one user can get objects of other user


Ok. Thx for the tips by the way. I've been in Java land way too long :)


done


According to https://www.openhub.net/p/firedrakeproject, this commit removed ~95 % of the source code :scream:


Yes and it's also going to need to do

3. Check api permissions on the foreign entity before performing the join.


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 128](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=645&buildTypeId=Xbim_XbimExchange_XbimExchange) is now running


1，加入组织
2，fork代码
3，提pr到主干

pls review & LGTM
@Uturboo/develops


@nhpatt Finally I tend to prefer this approach. It's simpler, faster and requires less code


TeamCity DNN JavaScript Libraries :: CI [Build 130](http://teamcity.engagesoftware.com/viewLog.html?buildId=408&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 130](http://teamcity.engagesoftware.com/viewLog.html?buildId=408&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:7


TeamCity Xbim :: Xbim Exchange :: XbimExchange [Build 128](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=645&buildTypeId=Xbim_XbimExchange_XbimExchange) outcome was **SUCCESS**
Summary: Running Build time: 00:00:51


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


But the Server crashes for Error: Undefined class constant 'id' xD


Also removed the "PartnerAccountId", etc. fields because these are not guaranteed to be present --- they only exist if you've got Partner Portal setup in an org.


we can delete this line?


Hi @lennerd, question, why removing PHP 5.3 is the plugin doesn't use PHP 5.5 specific code ? I am using PHP 5.4.45 now, so that means that composer will stick to the 1.1.5 tag now and I won't get updates.


thumbnails_attributes にid を追加しました。
idがないことが原因でprototype更新時に関連thumbnailが更新ではなく新規作成されてしまっていたため
それへの対応です。


That sounds good. We have a quite similar use case, but instead of prefixing we show the user an icon depending on the type. Also, we want to discourage the user to write a stop as from/to and encourage the users to write an address/poi, since the users very seldom arrive/depart exactly from a stop.


You know, I think this is the most commented commit in GitHub...


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

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


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


Thank you!


s/group/user/


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


Migrated model fields :

```python
>>> heroku run bash
>>> python manage.py migrate vav
Running bash on nameless-tor-3513... up, run.4663
~ $ ./manage.py migrate vav
Operations to perform:
  Apply all migrations: vav
Running migrations:
  Rendering model states... DONE
  Applying vav.0011_auto_20160107_1604... OK
~ $ exit
```


Pruebas


TeamCity libpalaso :: palaso-win32-master Continuous [Build 3.0.626.6590ff158b36054665d29e1055ada989026fb501](http://build.palaso.org/viewLog.html?buildId=67602&buildTypeId=bt223) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 3323, ignored: 125 Build time: 00:09:22
### Failed tests
```
SIL.DictionaryServices.Tests.dll: SIL.DictionaryServices.Tests.Processors.MergeHomographsTests.Run_ComplicatedSense_FullSensesPreserved: <no details avaliable>

```


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


I think this would look a little more intuitive if you default to UNDEFINED and only use EXACTLY is the dimension is actually defined.


I just had a situation where the old one didn't work for me either. It didn't work with a multi-word search on youtube (but it works on google and other sites), if one of the words contains the letter ø.

I'm testing out the new one you found in my own script now. I will give it a few days and see if I run into anything weird with it, but it seems better I agree.


TeamCity libpalaso :: palaso-precise64-master Continuous [Build 3.0.639.6590ff158b36054665d29e1055ada989026fb501](http://build.palaso.org/viewLog.html?buildId=67603&buildTypeId=bt322) outcome was **SUCCESS**
Summary: Tests passed: 3303, ignored: 106 Build time: 00:10:11


So we can easily add things like `enum Type { MUST_MATCH = 1; MUST_NOT_MATCH = 2; }` or other additional properties.


C'est comme ca qu'on utilise cloudinary dans les templates, il y a plein de settings possibles (cf la doc cloudinary ..)


I assume this is consistent with the C# coding style? i.e. Undefined instead of UNDEFINED.


Unrelated?


Ditto.


I agree, good call!

On Wed, Jan 6, 2016 at 7:06 PM, Aaron Lahey <notifications@github.com>
wrote:

> +1 Except I would probably use a StringBuilder instead of a StringBuffer.
> I'm not sure you would need the StringBuffer synchronization here.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/nystromb/java-httpserver/commit/f28c69bf368e7c67011fee76840ee7d26a8d49a6#commitcomment-15306014>
> .
>


Thanks, @artur79 !

Wow, that's a terrible API design by Adobe! It looks like they're depending on the *order* of the query string parameters.

Before this gets merged, I'd like to see a test that demonstrates the use case of having to repeat query string parameters. That would explain to future developers why we can't just use the params hash.


GHT_Bugs (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1465 of 1465 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.62%25-green.svg)


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


Looks good overall ;-) I'd like to see tests for cases where each measure mode ends up being used.


Could lines 89-92 be replaced by `extra_query_string = params.delete(:extra_query_string)`.


I think this line will fail with an undefined variable exception if `params[:extra_query_string]` is not present.


Please don't bump the version number in your PR. We'll do that when we release a new version.


:fries:


@albill I guess the announced date needs to be updated.


> No actual save support yet (it will come step by step).

Does this mean we'll be able to load saves as plugins, and, for example, turn player-made settlements into mods?


AbstractComponent.get_child seems to be what you want here, if I understand what you want


I'll do this one :)


human.name = xxx was used to tested #558. By removing them, you inhibit partially the goal of this test. Please keep them, for at least two humans.


boost ratio: 1.3 on my PC.


The change from rawurlencode to urlencode changes the semantics of routing significantly when spaces are involved, as they are now encoded as '+', and not automatically decoded back into spaces.


Yes we can.
https://github.com/aries-auto/ariesautomotive/commit/2839ffff0f9fdf2355f4d49f8896a4876af4a936
https://github.com/aries-auto/ariesautomotive/commit/05329652c2c8710b2fc41cd548eecc1416e24353


@jwittenbach That looks awesome! Very clean and intuitive and informative. Great work!


MiB instead of megabits?


maximum


This is not a good code


node's


this


Change this


no name on the manifest?


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


the -help says: per kB


asd


the one for arm still isnt working
path must be given in .bashrc


`ppc64le`, despite its name, is actually an ABI variant (ppc ABIv2, only so far implemented on little endian), not a CPU property. Renaming this field 'abi' might make most sense. Endianness is sometimes a CPU property (eg x86), but more often an ABI property, eg most arms can run arm or armeb binaries if they have the right libraries and kernel support. Sigh.


@hlee why?


@mourner that's the previous global eslint setup. It's fixed with the local eslint config in https://github.com/Turfjs/turf-deviation/pull/2


prototype作成userでないとeditボタンが表示されない設定です


If you want to expose interfaces outside this file (to consumers of this definition), it would be better to rename the namespace to 'micromatch' and move it inside the `declare module 'micromatch'` block.  The `namespace` and the `const`, both named `micromatch`, would be merged, and you could access interfaces like the options:

```ts
declare module 'micromatch' {
    namespace micromatch {
        type Pattern = ...
        interface Options {
            ...
        }
    }

    interface Micromatch {
        ...
    }

    const micromatch: Micromatch;
    export = micromatch;
}
```
then in the tests (or wherever):
```ts
//this also makes the ES6 import syntax work
import * as mm from 'micromatch';

//use interfaces
let options: mm.Options;
//use object
mm.expand('*.js', options);
```


好唷！不過以下可以修改：
網絡 >> 網路
信號 >> 訊號
通信 >> 通訊
带宽 >> 頻寬


Should this be "Unipycation" (not all capitalised)?


I'm sorry to dig in an old PR, but why is it impossible to print the files if the sample is not in the DB ? I'm not sure I understand this bit


One thing at a time. It's on my list. :smile:

We can probably store OCSP bytes to the .caddy folder.


s/project the contains/project that contains


The feature to temporarily show the dock when switching workspaces has been added to the master branch. This is the feature enhancement from issue #24.


@herby
The problem I want to solve is when the app is closed/killed, there is no alive React Native Activity to handle received notification in Javascript code.
The solution now is [launch](https://github.com/oney/react-native-gcm-android/blob/master/android/src/main/java/com/oney/gcm/BackgroundService.java#L37) a `Service`(that is `com/oney/gcm/BackgroundService.java`) in the background to create a `ReactInstanceManager` and patch the notification info to `GcmAndroid.launchNotification`.
Then, in Javascript, there is no need register component(`AppRegistry.registerComponent('YourApp', () => YourApp)`), and we handle the GCM notification(e.g. create a notification).
After finishing handling, we should call `GcmAndroid.stopService()` to destroy the `BackgroundService.java` and this `ReactInstanceManager`.

In my test, we can create many `BackgroundService` without disturbing each other.
The reason I delay 1 second to [`stopService`](https://github.com/oney/react-native-gcm-android/blob/master/android/src/main/java/com/oney/gcm/GcmModule.java#L155) is it is too fast to destroy `ReactInstanceManager`, creating notification won't work.


I'm experimenting with a new sauce feature.