GroundDomainUpdate (sushobhit) - i386-Windows-7-VisualStudio-12: OK (1636 of 1639 tests passed)

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


I did not git tag. I did not forget it, I did not apply it as it's not
finish and I don't want to see any other RC tag that fail.

On Mon, Apr 13, 2015 at 6:16 PM, Sébastien Coavoux <notifications@github.com
> wrote:

> This commit is not consistent with the Changelog. A simple pull request
> could have pointed this actually. Don't forget to edit it when tagging.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/naparuba/shinken/commit/9987361e5191071791e81df90989c4cc1505219d#commitcomment-10695858>
> .
>


I don't understand when you choose the Syntax Error over the Annotation Error.


```Description``` should be a short message about project. In english.


change to private static? or replace to inline invocation


Hi, delays are not a problem, you should enjoy this project as long as you like to work with it :)
Native async usage in this case will be awesome!


Unreleated, but line: https://github.com/MediaBrowser/SocketHttpListener/blob/6fcc5c20df115f5cc8b3c5954b11bf60e5bc6095/SocketHttpListener/Net/HttpConnection.cs#L337

should probably be this.ms


I know that this is a nice entry point for this, but I'm not comfortable mixing protocol operations with code whose sole purpose it was to fire out AODVv2 messages like that.
I fear that with the addition of stuff like

   After the attempted Route Discovery has failed, RREQ_Gen MUST wait at least
   RREQ_HOLDDOWN_TIME before attempting another Route Discovery to the
   same destination.

(http://tools.ietf.org/html/draft-ietf-manet-aodvv2-08#section-8.5) this section is going to grow into one more instance of the monolithic awkward code blobs that populate ``aodv.c`` currently...


With the array it throws

```
Strict (2048): Declaration of App\View\AppView::initialize() should be compatible with Cake\View\View::initialize() [APP/View/AppView.php, line 22]
```


#4090 every time a patch doesnt apply, a poor builder reports a "bug"

no huge patch will stop me from updating kodi, especialy when we dont even do official unofficial nightlies


91958608DOASEffectOnZoneSizing (wfbuhl) - x86_64-MacOS-10.9-clang: Tests Failed

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


quem solicitou essas funcionalidades de renomear avaliações? parecem pouco úteis


Error: you broke the world!


1570-EnergyPlus-8-3 (kbenne) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Mais blague à part, +1 pour le comment de Julien


Should probably check both `getNumberOfParameters` (max amount of params) & `getNumberOfRequiredParameters` (min amount of params)


Good point, added that.


parameterized*


all the question need of answers - all the questions need answers

coloca o texto no word, para aproveitar a correcao


`ReplProps` collects various props that you can never remember the name of. Maybe time for `~/.scalarc`.

Would also be neat if the string property were a dollar quote, naturally with `$intp` in scope. If there are no dollars (a constant), spit it out immediately; otherwise, compile it and echo it in `loopPostInit`. An empty string means no banner. That's just an idea.

https://github.com/scala/scala/blob/2.11.x/src/repl/scala/tools/nsc/interpreter/ReplProps.scala

Also, the surrounding source is not quite so space happy.


Check with anil


focar mais nas principais funcionalidades


As I have recently been reminded, do not use backslash line continuation.


Si je comprend où s'en va @BlackMinou avec son module, cette erreur est temporaire.


Behoben mit f8af2b967ba84f6884bd89082817e0a104ebaade .
Danke :v:  wenn schon kein konsistenenten Drift dann wenigstens hier :grin:


Review if begin and end periods are required.


exato. ou select. o importante é elevar o nível de abstração


These changes should have been released with bf1e5296d6c861a0f576ea022c466eb17f793b41.


We should add that to all the methods though right?


exato, tem que ser uma precisa. mas não pode ser ficticia, melhor concreta. tira a duvida comigo, se noa souber


Delegate to new entity


vago? amarrar mais o comportamento do sistema.


I'm still not seeing a documentation.md written anywhere, even though it's referenced in the !include.  Should that `if (writer!=null){` be there, or is it unnecessary?

Thanks for looking into this!


pode enviar incompleta?


melhor evitar clicks... aumentar o nível. verificar livro.


use JQuery lite notation with xPath selectors


mas como verificar isso se não amarrou antes na precondição?


Check if it should be DomainObject converter.


Z tymi stratami jakosci to mi zabiles cwieka bo szczerze mowiac nie wiem. Ale sie dowiem. :)

Nos jest imho rownie problematyczny niz srodek. A nawet bardziej bo dodatkowa kaskada. Srodek miedzy oczyma juz blizej ale mozna jeszcze prosciej.

—
Wysłano z Mailbox

On Mon, Apr 13, 2015 at 9:11 PM, Filip Kowalski <notifications@github.com>
wrote:

> A nie jes tak, że rotacja -> resize powoduje mniejsze straty jakości niż resize -> rotacja? Sama rotacja troche szumów dodaje, ale one potem fajnie zanikają jak się obraz pomniejszy.
> Ja z rogiem obrazu to mówię o względnych współrzędnych oczu, a nie rotacji (róg obrazu jako oś to chyba najgorsze miejsce). Mam dwa pomysły: nos albo środek pomiędzy oczyma i chyba pójdę póki co za tym drugim, bo
> -nos jest blisko środka twarzy - który jest słabą osią obrotu
> -żeby znaleźć środek między oczyma nie potrzeba kodzić kolejnych kaskad ;)
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/voldi9/FaceRecognition/commit/56fdffd32f96ba2eb3014548bc68cd23764a4164#commitcomment-10699211


One reported build issue is sufficient reason to drop a patch set that is used (without problem) by others? Blimey!

So what are your plans for future RPi support - grab the Pi backport patches just before each new release build and hope they work (then delete them afterwards)? You might as well drop the RPi linux patches too, and apply the same build logic - no reason to keep them up to date between releases.


muitos cenários com funcionalidades que talvez não sejam tao úteis. esta faltando foco nas funcionalidades principais


Why was this btn-block added? This causes weird styling:

![](http://i.nonr.nl/hkxw1.png)


Where is that on the spigot agenda?


no.

On Mon, Apr 13, 2015 at 12:28 PM, Brent Picasso <notifications@github.com>
wrote:

> does this fix the auto-detect problem we saw at the event?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/autosportlabs/RaceCapture-Pro_firmware/commit/fa9bdb818bb49e4fdbfbd9188752075d0ca26481#commitcomment-10697335>
> .
>


No good reason - this just seemed simpler and easier to understand.  I'll re-implement with util.Wait and see whether that's better.


Bug 27 will still be prevalent on the gdc-4.8 branch.  In a way it is not important as this bug-fix relied on gcc backend fixing their side in order to allow us to fix ours.  I didn't expect it to work with anything less than gcc-5.1


I'm front of Hydrolux and Aileron.

The addon don't start. So this fix is not enough.

I think all the strategy based on unitCreated event can't work correctly


Take a look as that pattern would be more idiomatic, if it's not worth the effort lets leave it.


Speaking of gcc 5.1, it's branch time (I'll create a new gcc-5 stable branch)


falta complementar com testes de controlador


erro de ingles. usa o word para verificar as frases.


ya olmuyo napimm :D


has been sent


@RamonGilabert yes :)


muita funcionalidade pouco util e não complementada por cenários de controladores. amarra muito pouco como o sistema deve se comportar.


Verify that student statute creation is prevented with non explicit creation


Would you mind updating this information for the plugin for your contact details (if you want to include them)?


You need to check if the module is loaded. Does it not load Water/Air at all? Or does it not start the encounter when you engage combat? What about when you target the bosses manually (forces a UnitCreated event)?

Do you see the UnitEnteredCombat event being fired and does it reach the event handlers?


Thanks for the explanation and for the link. I see this is a hot topic.


So, this test is pretty beefy.  It takes a long time to run and does a bunch of crazy shite, and it uses a lot of memory.  But I think it's fairly valuable.

Some "travis bisecting" has me convinced that the extra memory overhead of this test is responsible for some OOM errors that are showing up when travis tries to test the latest version of this PR.  This doesn't seem totally shocking since the max heap is set in the project file to 256MB, and we're doing a bunch of crazy flushing shenanigans with 4+ JRubies in this test, and our recommended max heap for 4 JRubies is 2GB.  It's a little weird to me that the OOM is happening on a later test after this one has run and passed, but I don't think it's a leak.  I'll try to kick off a gatling run on my local box tomorrow, using this branch, and let it run for a while with max-requests set to something like 50, and see if it looks like there is a leak.

Assuming there is not, I can see a few possible courses of action here:

1. Change this test so that it just boots up a TK with the jruby-puppet service (and maybe the puppet-admin service?), without the rest of the services.  If I do this, I think I could use the mock jruby fixture ( :no_bicycles: ) for this test, which would drastically reduce the execution time and memory requirements.  This is probably what I'm leaning toward  ( :rage: ), but if I don't include the admin endpoint I'll have to figure out a different way to trigger the flush.  (I can't use the mock jruby fixture if the puppet config service / master service are included, because they try to call puppet ruby code at startup.)
2. Increase the max heap in the project.clj until travis stops failing ( :no_good: )
3. Get rid of this test or try to simplify it a bit somehow ( :confounded: )
4. Make it into a beaker test somehow ( :hankey: )

@camlow325 would be interested to hear your take.


Jedno z oczu.
Kurde, ja mam laptopa w rogu pokoju podłączonego prawie 24/7 pod monitor i zew. klawiature i myszke, on jest tak przyciśniety do rogu, że nie da się odchylić ekranu do tyłu prawie, leży na wysokości moich kolan i jest przy nim tyle okablowania, że ciężko go nawet obrócic. Dlatego właśnie, żeby moja twarz była blisko dolnego rogu ekranu to muszę klęczeć :laughing: dlatego mi ta usterka umknęła przez tyle czasu... No ale już naprawione.


When you switch of target, that will do an event "UnitCreated"

So I you have reload for any reason, and you don't select any boss. The addon can't start.


+1 he's back!!!! :)


Nit: No need for `readwrite` here as it's implicitly inferred here.


necessário?


`success(())` might be cleaner.


All boss should trig on UnitEnteringCombat with unit = PlayerUnit. at least.

The boss identification must be based on UnitEnteringCombat.


Another good way to fix it.


deveria amarrar melhor, com pré-condições, senão fica difícil testar


`strong` instead of `retain`


I think this uses more space then needed....
say you start on kola base version X. You then upgrade all of the services to docker container version X+1.
The data containers will still live on, pointing at kola base version X, pinning it on disk and wasting space.

Therefore, should the data containers be based on busybox or something smaller?


r+


i see ... then please forget about this ... seems that this patch wasn't in 1.57


amarrar melhor o comportamento, sendo mais concreto


```ruby
record.errors.each do |key,value|
  @todo.errors[key] << value
end
```


Nit: `instancetype`


usa exemplos concretos, nao ficticios


problemas similares aos anteriores


Like than, you have no problem with reloadui.

But the task is big. I will to it for next month. For this delivery, it's too late.


saw approval from graydon
at https://github.com/gmarceau/stellar-core/commit/b3c1401a6af6643d0dac11f7c222b4f96bba8dce


merging gmarceau/stellar-core/faster-event-cancel = b3c1401a into auto


gmarceau/stellar-core/faster-event-cancel = b3c1401a merged ok, testing candidate = 2f88bce6


As this is a public header - please use `#import <Bolts/BFCancellationToken.h>`


Fine for me :+1: One thought, maybe download badge could link to our download page?


mais de controlador, tem a ver com comportamento interno.

tem que decidir se o cenário é de guia ou de controlador


Since this is a new API - I think we might want to drop extra `with` from the second parameter.
This would look like `taskWithDelay:cancellationToken:`


`continueWithBlock:cancellationToken:`


@gouessej There is no PR for updating the build system to use Maven instead of Ant, no. My question is: does upstream want a change like this? Or is too big/disruptive a change? (Personally I think it would make things very much easier for developers, but I am obviously heavily biased towards Maven.)

> Supporting both Maven and Gradle for the most popular engines based on JogAmp is one of my objectives.

So it sounds like you do want this change, then! How about you, @hharrison?


`continueWithExecutor:block:cancellationToken:`


Sure thing, I'll have a look tomorrow.
On Apr 13, 2015 10:35 PM, "Kacper Michajłow" <notifications@github.com>
wrote:

> Fine for me [image: :+1:] One thought, maybe download badge could link to
> our download page?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/XhmikosR/mpc-hc/commit/5cf0a9cc0ba7bc6767f4991b1f0e82b832eb50a4#commitcomment-10699611>
> .
>


Will do


Yep. Jedno z oczu. Tak jest moim zdaniem najprosciej.

—
Wysłano z Mailbox

On Mon, Apr 13, 2015 at 9:31 PM, Filip Kowalski <notifications@github.com>
wrote:

> Jedno z oczu.
> Kurde, ja mam laptopa w rogu pokoju podłączonego prawie 24/7 pod monitor i zew. klawiature i myszke, on jest tak przyciśniety do rogu, że nie da się odchylić ekranu do tyłu prawie, leży na wysokości moich kolan i jest przy nim tyle okablowania, że ciężko go nawet obrócic. Dlatego właśnie, żeby moja twarz była blisko dolnego rogu ekranu to muszę klęczeć :laughing: dlatego mi ta usterka umknęła przez tyle czasu... No ale już naprawione.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/voldi9/FaceRecognition/commit/56fdffd32f96ba2eb3014548bc68cd23764a4164#commitcomment-10699534


So where is that even be used? Or how would it be used by a client?


91958608DOASEffectOnZoneSizing (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed

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


Sure


So if you just enter the room normally it works correctly, without reloadui?

It's an issue with reloadui because that doesn't trigger the UnitCreated event, so you have to target the boss manually or leave it's range/room and re-enter it which triggers the UnitCreated event again.

This is why we have RegisterEnableZone and RegisterEnableEvent handlers for some bosses. However elemental pairs are not possible to do that way as far as I know.

Do you have idea on how to trigger it via UnitEnteringCombat? Since there are elemental pairs, we still need to know which module to activate. For other bosses it's easier since boss names are unique to an encounter, but not elemental pairs... That's why I added RegisterEnablePairs, because before that it also loaded the wrong elemental pair modules.


Oops


Looks good. Well formatted readable code. Does what it's supposed to.


No need to check if `token` is `nil`, since second call is going to check for that anyways and return `NO` if `token` is `nil`.


No one cares :)


1. I have included the collision part
2. Student Pickup
3 Score changes on students pickup
4. Some clean up
5. Integration error resolved


Same as in `taskWithDelay:cancellationToken:` method.


@tarelli I removed that _stopVisiting variable since it's no longer needed.


Instead of calling ```getSettings``` you can call ```getSettingsKV``` and it will return the plugin settings a hash of key/value pairs.  no performance gain, it does the same thing but it will save you a few lines.


It looks like the differences won't cleanly apply, and I couldn't figure out how to make a pull request based on that. Not even sure that's what you would want?

https://github.com/dblock/gem-licenses/compare/master...newrelic:master

How would I go about making a pull request with those changes?


Contact information is updated now.


Nit: Move `BFC*` above `BFExecutor` to sort all of these alphabetically.


For anyone else who stumbles across this discussion: the tutorial to which @gouessej refers is [this one](https://gouessej.wordpress.com/2012/08/01/java-3d-est-de-retour-java-3d-is-back/).


@westonruter Since this was merged I'm [receiving errors in Travis builds](https://travis-ci.org/wp-stream/stream/jobs/57595240):

```
dev-lib/travis.before_script.sh: line 21: upsearch: command not found
```


**SUCCESS** - TeamCity Quickstarts :: Pull requests monitor [Build 57](http://ci.infinispan.org/viewLog.html?buildId=25163&buildTypeId=quickstarts_PullRequestsMonitor&guest=1) for 366053e12f5a8edb9649c4690af20b9aee25af9d
Tests: 4, 0 failed (0 new), 0 ignored. Build time: 00:01:27


I just had a warning on this during compilation, so i initialized the `struct` directly.
Honestly I never saw an initialization the way you did it before :)


Awesome, thanks you! The plug in has been approved.
On Apr 13, 2015 3:38 PM, "Mark Baird" <notifications@github.com> wrote:

> Contact information is updated now.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/markbaird/blogger2pb/commit/f824f2c107766b117aa11b5cce95c349881b7572#commitcomment-10699678>
> .
>


@yehudasa Thanks for the review, haven't given a thought of the latter version you were referring above, but yes, should be more involved.


voila


+1 for changing `getWorkDelegate` to `acceptIndexWorkVisitor`


it would be nice to change indents from tabs to spaces


About what ! Ssw nothing


Nit: Use `XCTFail`


Supposedly by 1.9 actually


watch that equal sign in the loop. 0 to 11 is 12 iterations.


Same here. Typically when you use .length to get the max on a zero indexed array, you use less than (not less than or equal).


Since this function unconditionally consumes `task`, you could use `glnx_unref_object` on the task declaration instead.


91958608DOASEffectOnZoneSizing (wfbuhl) - 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)


It renders properly. Code is quite readable.


Si tenes razón lo de la marca , seria mejor ponerla en el constructor y lo de los test los cambie por que si no iban a romper , pero igual creo que no nos pedían los test.
Ahora me estoy por ir hasta lugano lo cambio después o si alguno puede cámbielo.


I can't answer to the first question, my game was in french at the beginning.

The workaround .. could be fixed. Not now, I agree.

RegisterEnableZone for me... it's useless.

Yes, I have a good idea. It's what I code in DruseraBossMod. ^^ So that works ^^


> One reported build issue is sufficient reason to drop a patch set that is used (without problem) by others? Blimey!

dude. those fail to apply. I test before dropping. please dont get on my nerves. I'd prefer having a master branch that people can build. self builders like you, who know what they are doing, can always add whatever they want, on top.

if our master branch cant be compiled, it's useless.

I have no time and will to rebase every time I need to update kodi for some reason. I've had very bad experience with fernetmenta's x11 stuff in the past. if you want the patches in, feel free to rebase and PR. I promise to hit the green button immediately. thanks in advance.

> So what are your plans for future RPi support - grab the Pi backport patches just before each new release build and hope they work (then delete them afterwards)? You might as well drop the RPi linux patches too, and apply the same build logic - no reason to keep them up to date between releases

I, personaly, have no plans, and I dont know (nor I do care) what plans @sraue have for rpi/2. I guess most of @popcornmix work should go upstream at some point, and/or when we start building official OE+kodi betas, someone should take care for those patches (not me, you can be a volunteer if you want). if I have to rebase a 90+ patches every 3 days, I am out off this business.


ahh, that's a pity, I just forgot about that (you told me about it earlier :blush:)
So, I guess a separate FIB handling thread is increasingly likely now :(


I dont want to update Forge to because GT5. Is there a reason for using newer Forge Version ?


@fjarrett Oops. Right, this function is only defined in the `pre-commit` hook. Could you try just

```bash
if [ -e .jscsrc ]; then
    export JSCS_CONFIG=.jscsrc
elif [ -e .jscs.json ]; then
    export JSCS_CONFIG=.jscs.json
fi
```

And open a PR to fix if it works for you?


Updated FocalOperationPrimitives.py


Just curious, do you plan on merging this work back into a release, and/or getting it integrated into the `metrics-influxdb` module? I realize this probably adds a dependency that folks wouldn't want, but the syntax is nice and convenient :+1:


what?


I fear so too :/


should log at info level and check the stream to see if its active (to avoid composing the string needlessly)


The release here should not have been checked in!


you mean like this?
![image](https://cloud.githubusercontent.com/assets/6933240/7124039/57728b9e-e27a-11e4-8b1a-caf94e06c1ae.png)


This call to pack doesn't seem to do much...


An indentation error sneaked into this commit while moving code from rows() to get_rows(). The final loop, "for attrib in attribs.values()" should be at the same level as "for field_group in field_groups". The incorrect indentation creates incomplete duplicate entries.

emergence/python-sharepoint/@c7b4f8049ce5b4c21abcce9ddda5cc32eaf76554 fixes the error.


Okay…revert my changes when you merge with yours.

From: Craig [mailto:notifications@github.com]
Sent: Monday, April 13, 2015 12:46 PM
To: GridOPTICS/GOSS
Subject: Re: [GOSS] changed publishString method to work properly. (537ccc1)

The release here should not have been checked in!

—
Reply to this email directly or view it on GitHub<https://github.com/GridOPTICS/GOSS/commit/537ccc15ea2f1b8b890a55634d8c13021d7b1696#commitcomment-10699820>.


nope, like this :smile:
![image](https://cloud.githubusercontent.com/assets/111710/7124076/b357ecb4-e226-11e4-974d-0ae7b862065f.png)


I hope you are referring to replace 'Mutex handle_lock' with that of a RWLock. Currently any writer into the map, meaning a thread that doesn't have a RADOS handle associated, would take the mutex and update the map. This operation is idempotent of any consumers of the map, as the lookups for the respective threads are unique on the map.

Not sure if am missing anything here, can you please explain a bit further as to why this recommendation.


again, this call to `pack` doesn't seem to do much


Ahh. Magic! :wink:


Out of interest, what would be the use case for `setPeaks=false`?


Bad casing. Probably a bug in the IDE.


These three lines are great for generalizing the hours, should that ever be needed.


Works fine. OS X 10.10, Vim 7.4.622


great looking code.


My fault, that was leftover from the previous code. It is not used, I was using the OMP_NUM_THREADS environment variable to control the maximum available threads.


тут можно QStringList::join()


Nice work! Just a small optimization: take `temp` out of the loop and compute it one time only
```
let temp = split(searchdir, "/")
while 1
    " all the code


xq agregaste eso?


this made my evening :D


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


14.1.X would be awesome. Thank you.


Have retained the legacy implementation here, would remove if it is offending.


It looks like that you fixed a bug here, because ETH_HLEN is 14, not 16.


After, with a target, that seem to work a minimum.


The readme change looks good.


Also, upgraded to Jupiter:
<pre>
Server Information:

You are using IPython notebook.

The version of the notebook server is 3.1.0-cbccb68 and is running on:

Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2]

Current Kernel Information:

Python 2.7.6 (default, Mar 22 2014, 22:59:56)
Type "copyright", "credits" or "license" for more information.

IPython 3.1.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.
%guiref   -> A brief reference about the graphical user interface.
</pre>


1570-EnergyPlus-8-3 (kbenne) - x86_64-MacOS-10.9-clang: Build Failed

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


para que no cambie taaaanto, propongo hacer un chequeo respecto de null a marca y si esta seteada con algo que aplique ese, asi no cambia nada los tests viejos y agregamos tests nuevos para mostrar las nuevas funcionalidades. Y si, tests SI o si, sino es programar al pedo XD


Yeah, that usually did the trick in my experience... The first pull after a reloadui doesn't work unless you manually target, but pulls after that do work... because when you wipe the bosses respawn so you get a new UnitCreated event.


тысячи копипаста с подсчётом матожидания и дисперсии?


No, you shouldn't have to rebase 90+ patches every few days, agreed. But this is a change to an existing "process" (for want of a better word) that has been in place for 2+ years without any notice or public discussion, and to be honest it seems to be something of a knee-jerk reaction.

I don't personally have a problem with the patches being dropped if they're a problem but understanding in advance what the plans are now they have been dropped would have been nice.


update


Binding pry left in. otherwise :shipit:


The standard practice through the Scala libraries is to call this Foo.Builder rather than Foo.FooBuilder.


@jeanlf you are on git now :). You can commit 2 ideas separately :).


Since we're redoing this anyway, I think this code should be factored out into a separate file in the `code` dir.


git rebase -i HEAD~2
Then change "pick" to "r" to reword the commit message.

On Mon, Apr 13, 2015 at 9:59 AM, Zifei Tong <notifications@github.com>
wrote:

> Is there any chances we can fix this commit message? Looks funny with git
> log...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/taskgraph/taskgraph/commit/1ebbef5931cddd330a9a42ed7653eb3652784ada#commitcomment-10685364>
> .
>


This `begin` statement should move down below the method definitions.


Where do you place the php on the server? I could really use the Verotel gateway.  But does this entail al of the code needed and does wit work with the latest WooCommerce update?


var index = -1;

... for loop

if (index != -1) {
  // delete the found tweet
}

your code does

if (index) {
// ...
}

But if the tweet is at index = 0 that if condition will not be true so you won't delete the tweet at index 0.


develop (lefticus) - Win64-Windows-8.1-VisualStudio-14: OK (336 of 337 tests passed)

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


Truth


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


I think it's better to leave the main() function in main().


Regarding this commit... I had these lines in my old setup (borrowed from @ppold )

```elisp
  ;; UTF-8 please
   (setq locale-coding-system 'utf-8) ; pretty
   (set-terminal-coding-system 'utf-8) ; pretty
   (set-keyboard-coding-system 'utf-8) ; pretty
   (set-selection-coding-system 'utf-8) ; please
   (prefer-coding-system 'utf-8) ; with sugar on top
   (set-language-environment 'utf-8)
```


Would you (or anyone with write permissions) please do a force push? Hopefully it won't affect many users.


I think you meant `setHighlight(buffer, 2);` here. Highlights on regular channels (not queries) are showing as normal messages.


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-AddressSanitizer: OK (337 of 337 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)


Lol, i just mentioned them cause i have seen this customizations or like this one before... Ill amend the commit later


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.194](http://teamcity.monogame.net/viewLog.html?buildId=6128&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 481, ignored: 6 Build time: 00:15:02


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.195](http://teamcity.monogame.net/viewLog.html?buildId=6130&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


Going to check this out.


When we discussed it, I told you `Gtk::Application` and `Application` are not interchangeable and to not attempt to replace Application with `Gtk::Application` but to rename `Application` to something else if it bothered you so.

Gtk::Application is already used. See: https://github.com/gtorrent/gtorrent-gtk/blob/master/src/gtk/Gtk.cpp


all tests pass:
success: http://buildbot.bos1/builders/test-riak_cs/builds/1053


idl member ready


2 situation should be handled for machine:
1)If no job is getting processed and user clicks on machine failed, we should pop up some error like: 'corrective maint can be reported only when machine is operating'
2)if job is under process, u cannot do prev maintenance.


What about on line 49? I'm looking at it using github's interface and I can find instances of it.


Not all faces have the same dimensions. So it will have disproportional textures when pasting to all faces.


We don't usually rewrite merged commits.
Just write good commits next time when submitting a PR.


list, add, result need to be inside a Builder class. This is a global list. That means only one thread at a time can be building a notification, and that's not realistic.


Your `application.yml` should be added to `.gitignore`! Otherwise everyone can know your API keys or password!


This can become Notification.empty, which could be a convenient method that creates NoErrors.


This can become `val errors = Notification.newBuilder` which is a convenient method for `new Notification.Builder`.


错字


The binding.pry can be removed.


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-ThreadSanitizer: OK (337 of 337 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)


@5kg @fengjingchao Hrm........ I have no idea on this. Yea... Usually we should not do force-push on master or stable.


All the ScalaTest asserts are `assert (expected) (actual)`. This def needs to match the ScalaTest ones, otherwise it's frustrating when similar APIs reorder arguments.


你去看看 PEP8... 装个插件来 lint 一下


I agreed with Xiang.
Let's be more cautious next time.


Gtk::Application is not being used the same way I'm currently using it.
GTorrentApp intends to replace Application - wait for the next commit


Hope this resolution of the cake-recipe conflict is good, and let's test the comment feature while we're at it.


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


There is an easy way to style the error messages about charging credit card. Use jQuery `wrap()` function to wrap a <div> with class 'alert alert-danger'. Moreover, put a condition to check the <span> has already been wrapped or not. Otherwise, if the user enter wrong credit card information, the error messages will be wrapped by several <div>s.

```
    if ($('.payment-errors').closest('div.alert-danger').length == 0) {
      $form.find('.payment-errors').wrap("<div class='alert alert-danger' role='alert'></div>");
    }
```


Add to #92 and #109


Yes.  I think there are implicit conversions that make the code still work, not sure though.


Fair enough. Let's be cautious while pushing the merge button, which I agree with linus (torvalds/linux#17) is evil.

Thanks.


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-gcc-4.6: OK (337 of 337 tests passed)

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


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.195](http://teamcity.monogame.net/viewLog.html?buildId=6130&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 483, ignored: 6 Build time: 00:15:16


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.67: OK (0 of 0 tests passed)

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


Muidugi, ma seda ei pannud tähele. Oma forkis nüüd parandasin, sa pead
vist uuesti merge'ima.

On 13/04/15 00:10, edmundlaugasson wrote:
> kas võiks olla:
> id="rumma-ko"
> vms
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/lsaffre/alvatal.github.io/commit/bc5d8c8636bdd0bf9de863c34031a5e8582a899c#commitcomment-10684287>.
>


@5kg Well... I have tried another workflow within a team. But it does not work well on github. So you have to live with the merge button and the ugly history that contains a lot of `Merge...` .


Hi Alex,
You're getting a bit too far ahead; I may not be able to merge this in cleanly.  We'll need to do some testing of the integration first.  For example, what range in Teff will we integrate over to make the dense table?  What if the Teff range doesn't cover the desired range in Tb?  Do we even need a dense table—we made this to match the interface with pcy97, but it may make more sense to make the interface more flexible.


God fucking damn it benwaffle, how many times do I I have to repeat myself.

I know you're trying to replace Application with this "GTorrentApp". But Application is not written to do what Gtk::Application does. If you want to replace or rewrite Application, go ahead, just don't do it with an instance of Gtk::Application.

There's an instance of Gtk::Application already, if you want to use the features of Gtk::Application do it with m_app.


Very nice! Note that at some point, we'll convert to one-more-minute's `ObjectiveC.jl` for all of this-- should make life much, much easier.


Ah, but I forgot that there's one testing issue to fix.  I'll take care of it now...


@5kg
This is a top priority PR. It's already much appreciated that Gang has implemented the code. And we don't wanna bother him with minor nits.
Any good contribution will be accepted.


If we're going to use the same Style Guide for products and docs, then "startup" should be written as one word as a noun or adjective. The verb form is "start".


Very nice.


vcbgf


I'll take care of this, but just note you can't remove the generic stuff, people may be using it.  Just going to add the new field


no.


ありがとうございます！


Besides, Ubuntu like having `-D_FORTIFY_SOURCE=1` when `-O` is specified with their `gcc`. Dunno why. Had to compile with `clang` whenever I worked on my Ubuntu laptop.


@kevinpschaaf I was frozen on the `0.8.0` tag on GH but after updating to `0.8-preview` I wasn't able to repro. Looks like it's been fixed somewhere along the way!


@Unia can you please make the modification on Transifex and we'll pull it in.


Confirmation: comparators attached to tanks will now change signal when tanks are filled with a bucket.

BREAKING NEWS: Filling with a faucet will give all redstone power values from 0-15.

I'd say our work here is done, but I did nothing other than comment, so /your/ work here is done. :smiley:


Dann Kompliment für die konsistente Arbeitsweise. ;)


Not sure - that looks correct. To make sure everything built correctly, you can:

  * Shut down all instances of Robomongo
  * Remove both new entries from `~/.config/robomongo/robomongo.json`
  * Restart Robomongo and open a query of some kind (even if you just double-click on a collection)

Then you should be able to check `~/.config/robomongo/robomongo.json` and see default/blank entries. If you don't see empty/default entries for the two new textFont* entries, something is wrong with the build or you're not running the version you built.

If you DO see the blank entries, I'm not sure what's going on. This patch has worked for me and at least one person, but I'm happy to try and fix anything broken if we can figure out what's going on. Qt will use a font matching algorithm if it can't figure out the font matching for the string given. You might want to try a different font and a ridiculous point size (like maybe "Liberation Mono" and 24) to see if you notice any change at all.


This should be made into a partial later on


Yep - thats fair


And to call this Foo.newBuilder rather than Foo.builder. Here at least, we should follow the established practice to avoid cognitive overload in the poor programmer who has to use this.


Probably one of the most amazing commit message I've ever seen... ;)


auditd does in fact still support restart, only through the old school sysv init script though.

See https://bugzilla.redhat.com/show_bug.cgi?id=1026648


I think a more proper way to do this would be a `get_lengths(font_name)` that would return a dictionary with the lengths (all lower-case)


 no_work_pending：
 	BNE fast_work_pending
+＃如果定義（CONFIG_IRQSOFF_TRACER）
+ asm_trace_hardirqs_on
+ #ENDIF
+ ＃如果定義（CONFIG_IRQSOFF_TRACER）
+ asm_trace_hardirqs_on
+


and then all functions using the width should have a `font_width` argument passed to them


Why is this change required?


isn't there a scope ambiguity here? I think you should set temp_width to 0 outside of an `if` block so that you're sure it will be available in the whole function


Please add a space before and after !=.


@maurya am assuming you just forgot to change this too. Correct? https://github.com/openmrs/openmrs-module-referenceapplication/commit/df9340ff1efbcf6bf51ced219b52b5185ffa5458
It was leading to AJAX errors on devtest01 during patient name searches.


There is 1 boss which is not destroyed and recreated between 2 try.

It's the spider in Earth Wing.


Please try to revert all unrelated changes in this file. E.g. separator lines are probably broken after this change.


thank you @rstoyanchev


Entire switch uses a 4 space indent instead of 2.


Meh, silly carbine... Would be so much easier with a GameLib.GetUnits() to return units in range :P


@whyrusleeping yeah it's true that people might want to put multiple versions because they might want hash links to old versions to continue working. But in this case a better strategy might be to use the fact that pack files that have a name that ends with ".keep" can be left as is by git when it repacks objects. See the --honor-pack-keep flag in [git pack-objects](http://git-scm.com/docs/git-pack-objects).

This way you can have for example V1 using pack-XXX.pack.keep, and V2 using both pack-XXX.pack.keep and pack-YYY.pack.keep, and V3 using pack-XXX.pack.keep, pack-YYY.pack.keep and pack-ZZZ.pack.keep, and so on.


moves files. Helpful to rename too.


"Clone URL:"


Like this maybe?
```viml
+++ b/autoload/ag.vim
@@ -201,21 +201,22 @@ function! ag#guessProjectRoot()
   let projroot = ''
   for marker in ['.git', '.hg', '.svn', 'bzr', '_darcs', 'build.xml']
     let searchdir = getcwd()
+    let splitsearchdir = split(searchdir, "/")
     while 1
       if filereadable('/'.searchdir.'/'.marker) || isdirectory('/'.searchdir.'/'.marker)
         let projroot = searchdir
         break
       endif
-      let temp = split(searchdir, "/")
-      if len(temp) < 3  " If size is that small we assume we won't find it anymore
+      if len(splitsearchdir) < 3  " If size is that small we assume we won't find it anymore
         break
       endif
-      let searchdir = join(temp[0:-2], "/") " Splice the list to get rid of tail directory
+      let splitsearchdir = splitsearchdir[0:-2] " Splice the list to get rid of the tail directory
+      let searchdir = join(splitsearchdir, "/")
     endwhile
   endfor
   if len(projroot) " Any result means good to go
     return "/".projroot
   endif
-  " Not found, returning parent directory of current file / file itself.
+  " Not found, returning parent directory of current file itself.
   return getcwd()
 endfunction
```


Shouldn't this also set `config_module.homedir`?

This something I noticed in the current master, so I blamed it back to the originating commit and commented there :-)


Please revert this whitespace change.


@AndrewGrachov fixed, thanks ;)


Again uses 4 spaces for indentation instead of 2.


@robertmesserle - this was the issue. LOL


What do you think about this?

![screenshot from 2015-04-13 22 08 05](https://cloud.githubusercontent.com/assets/5604686/7124491/91fbc588-e229-11e4-8d33-4c07c9fa7fc9.png)


Hi @evanphx,
Maybe I'm wrong but `start_with?` look faster even with a typecasting.

~~~ ruby
require 'benchmark'
Benchmark.realtime { 1.upto(10000000) { :binding.to_s.start_with?("bind") }} # => 4.654047345
Benchmark.realtime { 1.upto(10000000) { :binding.to_s[0, 4] == "bind" }} # => 5.624575477
~~~

I'm running `ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]`


Use 2 spaces for indentation.


If `erode` removes peaks, shouldn't `dilate` add them?


2 space indent.


I think ``AND requestname NOT IN ('Random top hit','radio wizi', 'Ultra Wizi TOP 10')`` might be a cleaner solution.


Thank you for this PR. If you could cherry-pick this change into master after fixing up these minor things, it would be great. If cherry-picking does not work, I will try to do it. You do not need to try against master (which is IntelliJ 12) - I will do it before merging (which will not before this weekend).

If you do not know: you can update a PR at GitHub by force-push an amended commit into the same branch.


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


Meant to move this block below, but apparently forgot to remove the original.  Thanks.


You could declare `a` `b` where they are initialised.


no, Entering combat is mandatory in an encounter. At least the player itself :)


Previously, some feed readers would fail to parse this feed because it did not contain links: https://www.reddit.com/r/changelog/comments/321quy/reddit_change_a_live_thread_for_smaller_and/cq729v9

That's not to the RSS spec, but since we have permalinks now, we might as well link to 'em. This will make it so each entry has a permalink to the update in question.


By the way, do we actually use `NUL` in new code or do we use `'\0'` or `0`? What's normally used in modern C for NUL?


Instead of returning the float you could pass it by reference like so:
float damage = damageNotModified;
ent->DoDamageModifier(foo... damage);
damage has been modified


This line would disappear ofc.


don't worry, I have already start this task. I immediately identify this weakness.


related #1986


The interesting part about having it being a message is that you could combine several types of components tinkering with the damage value.
On of them could be a locationalDamagecomponent


fast-forwarding master to auto = 2f88bce6


Also, what's the difference between "homedir" and "dotdir"? Neither seems to be documented?


PlayerPhysicsComponent would have a HandleDamage() and do the knockback


Fixed in https://github.com/google/fonts/commit/b36f05fc35d60c62bee38d9b0ff424d244d980ba


This is the cause of the failing knitr test (with python 2 at least, I've not tried python 3 yet).


This would be in armor component no?


@chriscool okay, well in that case, ill remove the unpack line


It would have been cleaner to separate the software updates for the affected issues, wouldn't it?


Hopefully it doesn't have to load the graphical user interface, making it faster


Maybe this would be easier to read without the looping and conditionals? Right now this would just be three variants.
```
GOOS=windows GOARCH=386 go install -ldflags "%{ldflags}" %{import_path}/cmd/${cmd}
GOOS=darwin GOARCH=amd64 go install -ldflags "%{ldflags}" %{import_path}/cmd/${cmd}
GOOS=linux GOARCH=amd64 go install -ldflags "%{ldflags}" %{import_path}/cmd/${cmd}
```


@vitaly-krugl, I think that should restore the BlockingConnection timeout 'logic' WDYT?


@troydai sp should this be `GetApplicationBasePath`?


Best to let the owner decide what the version will be


updated


Looks good for the events assignmnet.


I haven't seen this message in either.
In fact, lately, I haven't seen any messages at all.  I recapped a couple of docs this morning and didn't get a popup.  The docs and docket recapped successfully though.


Should use latest minor version (2.3.11 in this case)


@lazel about that ad hoc marker, i've seen some projects use an empty file .rootdir to mark project repositories so maybe I'll put that in the markers list. That way people won't need several different markers.


91958608DOASEffectOnZoneSizing (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (617 of 617 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-5.02%25-green.svg)


Chrome or Firefox?

On Mon, Apr 13, 2015 at 1:20 PM simality <notifications@github.com> wrote:

> I haven't seen this message in either.
> In fact, lately, I haven't seen any messages at all. I recapped a couple
> of docs this morning and didn't get a popup. The docs and docket recapped
> successfully though.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/freelawproject/recap/commit/3e3261ca4af56c056d7f059acb9091e03c3ba55d#commitcomment-10700405>
> .
>


Quite involved with two generic parameters. Why are they needed anyways? AFAICT in most case `P` is `Void` anyways. The only case where `P` is not `Void` is `FlushStrategySelector` in which case a `NRTWorkspaceImpl` is passed. Why is `FlushStrategySelector` not just returning a `FlushStrategyNeed` and at the caller site `FlushStrategyNeed.apply` is called. At least this makes all the `IndexWorkVisitor` subclasses consistent and I think we can get rid of `P` altogether.

That is beside the fact that we actually never 'visit' a `LuceneWork` instance.


O ho


If grails.project.work.dir is set there's no reason to specify grails.project.class.dir, grails.project.test.class.dir, or grails.project.test.reports.dir unless you have an unusual use case for non-default folders


Sorry about that. I didn't catch that use of a number with the choices function because the slots variable is untyped. And I always save to file, so I didn't notice this in testing the changes.


This is complicated the first time!!!


The spelling mistakes in the plugin names are the authors.


Resolves #6.


Fixes #61


Always include the rest-client-builder plugin and use export=false - some versions of Grails fail to exclude transitive plugin dependencies and leak them into the containing app


(But I don't really care -- this is a fine place too.)


Ibid ;)


D'oh


                                                                                I think these could all be code comments, instead of (or as well as) GitHub comments.                                                                                From: Shaun CramptonSent: Friday, 10 April 2015 21:19To: Metaswitch/calicoReply To: Metaswitch/calicoSubject: Re: [calico] Initial thoughts on UpdateSplitter (fa1b616)As mentioned above, this is only trying to delete left-over state form a previous run of felix.  Using async=False blocks this greenlet until that iptables updater actually finishes its cleanup and returns.

We allow blocking calls to iptables updater because it's at the lowest level of the tree and it makes the rest of the code simpler on balance.

Each actor has its own greenlet so, even if it spins the scheduler, it still can't process another message off the queue in parallel.  The cleanup blocks anything else until it's done.

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


Fixes #62


Minor/Nonstructural changes. Will ensure readability next time, as wanted


Hi Ralf. I have checked this new code today and it looks like the 'I' response doesn't wait for RX transmission ends and it use only time limit to transmit the response.
And second, if i try to be fast to receive the 'I' response, it seems to be overwritten by regular ACK. I don't see any other message or is it too fast. Hope it helps.
Need some testing, let me know :)


:+1: That flag really should be set to true by default!


develop (DavidGoldwasser) - Win64-Windows-7-VisualStudio-12: OK (2172 of 2197 tests passed)

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


If we stay with this method, we need to make sure there is always at least one type or keyword set


Whoops, No idea why that pushed to here.. Was trying to update my fork of it..


Good catch @dkayiwa.

@maurya, @dkayiwa, since we changed the algorithm, we need to do some quick
testing to make sure that similar patient matching still works acceptably.

@maurya: please make sure we mention (as a one-liner) in the documentation
that you can add the namephonetics module for a more sophisticated patient
matching algorithm.

-Darius

On Mon, Apr 13, 2015 at 4:05 PM, dkayiwa <notifications@github.com> wrote:

> @maurya <https://github.com/maurya> am assuming you just forgot to change
> this too. Correct? openmrs/openmrs-module-referenceapplication@df9340f
> <https://github.com/openmrs/openmrs-module-referenceapplication/commit/df9340ff1efbcf6bf51ced219b52b5185ffa5458>
> It was leading to AJAX errors on devtest01 during patient name searches.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openmrs/openmrs-distro-referenceapplication/commit/14c1b496ab40aedcd2f073113d22e4870e3fb6b1#commitcomment-10700139>
> .
>


Good code but make sure to fix up the block indenting to the standard so I can read it easier.


I think that's ok :) Maybe add also `.agroot` as a marker for someone who doesn't use any of the programs already considered :P

Oh! Just noticed, you should also invert the two loops: first the while and then the for, so you split the dirs only once, plus some other small optimizations:
```vim
function! ag#guessProjectRoot()
  let searchdir = ''
  let splitsearchdir = split(getcwd(), '/')

  while 1
    let searchdir = '/' . join(splitsearchdir, '/') .'/'
    " prefer the general marker?
    for marker in ['.rootdir', '.git', '.hg', '.svn', 'bzr', '_darcs', 'build.xml']
      " found it! Return the dir
      if filereadable(searchdir . marker) || isdirectory(searchdir.marker)
        return searchdir
      endif

      let splitsearchdir = splitsearchdir[0:-2]
      " If size is that small we assume we won't find it anymore
      " and return the current working dir
      if len(temp) < 3
        return getcwd()
      endif
    endfor
  endwhile
endfunction
```

I've also included your suggested marker `.rootdir`, standard is better ;)


"Lead developer" means they're swaggier than us. :P


Zrobione:)


Lets us create packet directly in enqueue method in read


Good to know.


Not sure whose CSS this is, but it's not me


In combination with CSS, the button should be full width of the loginblock


Non !!! On ne commite pas les fichiers générés (et le PDF en fait partie)...
Commitez le source latex ou markdown, s'il vous plaît !


Nice


I think this is a better solution:

```diff
diff --git a/notedown/notedown.py b/notedown/notedown.py
index 06826bb..a8f03cb 100644
--- a/notedown/notedown.py
+++ b/notedown/notedown.py
@@ -534,8 +534,8 @@ class Knitr(object):
         into markdown, returning a file object.
         """
         # use temporary files at both ends to allow stdin / stdout
-        tmp_in = tempfile.NamedTemporaryFile()
-        tmp_out = tempfile.NamedTemporaryFile()
+        tmp_in = tempfile.NamedTemporaryFile(mode='w+')
+        tmp_out = tempfile.NamedTemporaryFile(mode='w+')

         tmp_in.file.write(input_file.read())
         tmp_in.file.flush()
```

Fully passing tests on both python 2 and 3 for me.


You can edit if you want to, but I'm not sure what else there is to put in right now.


I don't think this usage is particularly useful.  Folks interested in creating one-off issues from the command line can always use cURL, with something like:

    $ curl -XPOST -u username -H "Content-Type: application/json; charset=UTF-8" -d '{"title": "Your issue title"}' https://api.github.com/repos/your/repo/issues


Everything looks fine. Could you please add the notice back ```<aside class="notice">
-  If you haven't requested any short_term_loans yet, or requested one but not activated it yet.
-</aside>``` somewhere around line 183 https://github.com/alfuken/api-docs/commit/0be14f283b31727b924688662fb22c5a89bb787a#diff-fe6637aaccba320d8eb8beacb8afca1bR183


`NUL`


can probably fix it in: https://github.com/whyrusleeping/git-ipfs-rehost


v1.4.2: 400992 frames, with seed 1428898417

Please save this seed number to share, if you would like proof of your run!

A screenshot has been saved to the Gameboy\Screenshots folder in BizHawk.

beat the game in 1:51:23 !

But with "." (dot) name of nidoran.


Looks good.


@ibuildthecloud  do we want to say that users can directly edit the file?

Is this phrasing better `RancherOS should be configured by using the rancherctl command. The configuration file is stored at /var/lib/rancher/conf/rancher.yml, we do not recommend directly editing the file`


But I need to be the swaggiest!

I'll have to live with osdev admin


This `zil_commit()` must be kept because in the common case the `zil_commit()` in zfs_putpage() will not be run.  This is done explicitly to ensure that `zil_commit()` isn't called per-page but instead runs once per-writepages call.


There are some minor typos on your translation:

aikau/src/main/resources/alfresco/dnd/i18n/DroppedItemWrapper_pt_BR.properties
+droppedItemWrapper.up.alt.text=Mover o item para cima um local
Correct: Mover o item para um nível acima
+droppedItemWrapper.down.alt.text=Mover o item para baixo um local
Correct: Mover o item para um nível abaixo


91958608DOASEffectOnZoneSizing (wfbuhl) - i386-Windows-7-VisualStudio-12: Tests Failed

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


Been a long time since I wrote this, but I guess: homedir is the name that makes sense, dotdir is for backwards compatibility, or something.

Also, since I'm no longer a contributor to this project I'd prefer not to get this kind of notifications to my email box, so please keep discussion like this in issues and not in comments on years-old commits


Yes, this can almost certainly be safely dropped since they're already redundant.  See my commit in #3281.


Actually we use POST for some things that should be GET because suhosin puts an unreasonably strict limit on the length of GET parameters; ergo we can't pass signatures or identity information that has crypto in it.

We probably should convert stuff to more of a REST model where possible.  I haven't worried too much about it traditionally because of the suhosin issue, and the fact that php doesn't really support anything but GET and POST, so you can't easily implement PUT and DELE; so you can't really implement a full REST model anyway. Many folks see this as a flaw so it's probably a good idea to move in that direction.

Likewise post tokens have been implemented but I neglected to use them as the initial phases of red involved lots of long days and nights (marathon coding sessions lasting a year or more) trying to achieve basic function. I figured these could be added later, but as with many things you decide to do later, sometimes you need a kick in the pants or help getting it done. The only form that we can't easily use a CSRF token is posting at item since this could come from a number of places (like the API). Adding the tokens is a couple of lines of code so if you see a place that could use one, feel free to drop it in. Since development isn't quite as fast and furious these days I'll try and get to some of these as well.


LGTM!


`Enable`, not `Enabled`


/*
Задачи Урока 3
Задача 1  - Сортировка чисел в массиве
1. Задать массив целых чисел длинной 10 эл.
2. Отсортировать числа в массиве
3. Вывести на экран результат.
4. Сделать возможность наполнения массива с клавиатуры*.
Задача 2 - Замена первого и последного элементов массива
1. Задать массив целых чисел длинной N эл.
2. Поменять 1-й и последний элемент местами.
3. Вывести массив на экран.
Задача 3 - Разбиение массива на 2 равной длинны, сортировка каждой из половинок и вывод на экран
1. Ввести с клавиатуры массив из 10 чисел.
2. Разбить его на 2 массива равной длинны.
3. Отсортировать каждую из половинок и вывести их содержимое на экран.
Задача 4 - Среднее арифметическое элемнтов массива
1. Среднее арифметическое элементов массива.
Задача 5 - Зеркальный переворот массива
1. Написать код для зеркального переворота массива (1,2,3,4) -> (4,3,2,1).
Задача 6 - Вывод элементов массива по его индексу на консоль.
1. Написать программу, которая позволит задать длину массива с клавиатуры, наполнить его
элементами, а затем выводить нужный элемент по его индексу на консоль.
*/

package com.company;

import java.util.Arrays;
import java.util.HashMap;
import java.util.Map;
import java.util.Random;
import java.util.Scanner;

public class Main {

    public static void main(String[] args) {

        int num = 10;                   // Количество элементов массива
        boolean flagRnd = false;        // Способ формирования массива (либо вручную, либо случайные числа)
        byte option;                    // Флаг выбора задачи
        int[] myArray;

        // String[] menuArray = {"inputText"};
        // Предполагалось собрать тексты для меню, чтобы использовать их повторно. Варинат с массивом выглядел не удобно
        // Наиболее полно задаче создания меню соответствовал словарь или map в Java

        Map<String, String> dic = new HashMap<String, String>();
        dic.put("Welcome text", "Выберите задачу:");
        dic.put("Task №1", "(1) Задача 1 - Сортировка чисел в массиве ");
        dic.put("Task №2", "(2) Задача 2 - Замена первого и последнего элемента ");
        dic.put("Task №3", "(3) Задача 3 - Разбиение массива пополам и сортировка этих половинок ");
        dic.put("Task №4", "(4) Задача 4 - Среднее арифметическое элементов массива ");
        dic.put("Task №5", "(5) Задача 5 - Зеркальный переворот массива ");
        dic.put("Task №6", "(6) Задача 6 - Вывод элементов массива по его индексу ");
        dic.put("Choose Task Number", "Для выбора задачи - введите соответствующий номер задачи (от 1 до 6)");
        dic.put("Number of Elements", "(8) Выбор количества элементов массива (по умолчанию 10) (8)");
        dic.put("Enter Array Option", "(9) Выбор случайного варианта заполнения элементов массива - нажмите (9)");
        dic.put("Exit text", "(0) Для завершения работы введите ноль (0)");
        dic.put("Exit text-1", "(-1) Для завершения работы введите минус 1 (-1)");
        dic.put("Enter number of elements", "Введите количество элементов массива");
        dic.put("Actual flag", "Текущий выбор  ");
        dic.put("Attention!", "С этим выбором вам придется вручную вводить массив элементов в количестве ");
        dic.put("Wrong Num", "Количество элементов следует выбрать больше одного");
        dic.put("Random or not", "Для выбора ввода вручную нажмите 1, для случайного выбора - 2");
        dic.put("Input element", "Введите значение элемента массива");
        dic.put("First state", "Первоначальная форма массива");
        dic.put("Last state", "Форма массива после обработки");
        dic.put("Wrong Array", "В данной задаче массив должен состоять из четного количества элементов");

        Scanner sc = new Scanner(System.in);
        Random rnd = new Random();

        do {
            //Окно приглашения:
            System.out.println(dic.get("Welcome text") + "\n" + dic.get("Task №1") + "\n" + dic.get("Task №2") + "\n" + dic.get("Task №3") + "\n" + dic.get("Task №4") + "\n" + dic.get("Task №5") + "\n" + dic.get("Task №6"));
            System.out.println(dic.get("Choose Task Number") + "\n" + dic.get("Number of Elements") + "\n" + dic.get("Actual flag") + num + "\n" + dic.get("Enter Array Option") + dic.get("Actual flag") + flagRnd + "\n" + dic.get("Exit text") + "\n");

            //Считывание ввода варианта от пользователя:
            option = sc.nextByte();

            myArray = new int[num];

            if(flagRnd == true){
                    for(int i = 0; i < num; i++){
                    myArray[i] = rnd.nextInt();
                }
            }

            switch (option){
                case 8:{ //Выбор количества элементов массива (по умолчанию - 10)
                    System.out.println(dic.get("Enter number of elements"));
                    int var;
                    var = sc.nextInt();
                    if (var <= 1) {
                        System.out.println(dic.get("Wrong Num"));
                        break;
                    }
                    num = var;
                    if (num > 99 && flagRnd == false) System.out.println(dic.get("Attention!") + num);
                    break;
                }

                case 9:{
                    System.out.println(dic.get("Random or not"));
                    int var;
                    var = sc.nextInt();
                    //if(var != 1 || var != 2) {System.out.println(dic.get("Random or not")); break;}
                    if (var == 2){flagRnd = true;} else {flagRnd = false;}
                    if (num > 99 && flagRnd == false) System.out.println(dic.get("Attention!") + num + "\n");
                    System.out.println(flagRnd);
                    break;
                }

                case 1:{
                    System.out.println("\n" + dic.get("Task №1") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true){
                        for(int i=0; i<myArray.length; i++){
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    System.out.println(dic.get("First state") +"\n" + Arrays.toString(myArray));
                    Arrays.sort(myArray);
                    System.out.println(dic.get("Last state") +"\n" + Arrays.toString(myArray));
                    break;
                }

                case 2:{
                    System.out.println("\n" + dic.get("Task №2") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true){
                        for(int i=0; i<myArray.length; i++){
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    System.out.println(dic.get("First state") +"\n" + Arrays.toString(myArray));
                    int temp;
                    temp = myArray[0];
                    myArray[0] = myArray[myArray.length];
                    myArray[myArray.length] = temp;
                    System.out.println(dic.get("Last state") +"\n" + Arrays.toString(myArray));
                    break;
                }

                case 3: {
                    System.out.println("\n" + dic.get("Task №3") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true){
                        for(int i=0; i<myArray.length; i++){
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    System.out.println(dic.get("First state") +"\n" + Arrays.toString(myArray));
                    if (myArray.length%2 != 0) {System.out.println(dic.get("Wrong Array")); break;}
                    int[] halfArray1 = new int[(myArray.length / 2)];
                    int[] halfArray2 = new int[(myArray.length / 2)];
                    for (int i=0; i <(myArray.length / 2); i++){
                        halfArray1[i] = myArray[i];
                        halfArray2[i] = myArray[i+(myArray.length / 2)];
                    }
                    Arrays.sort(halfArray1);
                    Arrays.sort(halfArray2);
                    System.out.println(dic.get("Last state") +"\n" + Arrays.toString(halfArray1)+"\n"+Arrays.toString(halfArray2));
                    break;
                }

                case 4: {
                    System.out.println("\n" + dic.get("Task №4") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true){
                        for(int i=0; i<myArray.length; i++){
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    int average = 0;
                    // Возможно использовать float если нужна большая точность.
                    for (int i=0; i < num; i++){
                        average = average + myArray[i];
                    }
                    System.out.println(dic.get("First state") +"\n" + Arrays.toString(myArray));
                    average = average / num;
                    System.out.println(dic.get("Task №4") + " = " + average);
                }

                case 5: {
                    System.out.println("\n" + dic.get("Task №5") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true){
                        for(int i=0; i<myArray.length; i++){
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    int temp;
                    System.out.println(dic.get("First state") +"\n" + Arrays.toString(myArray));
                    for (int i = 0; i < myArray.length/2; i++){
                        temp = myArray[i];
                        myArray[i] = myArray[num -1 - i];
                        myArray[num -1 - i] = temp;
                    }
                    System.out.println(dic.get("Last state") +"\n" + Arrays.toString(myArray));
                    break;
                }

                case 6: {
                    System.out.println("\n" + dic.get("Task №6") + dic.get("Actual flag") + num  + " " + flagRnd);
                    if(flagRnd != true) {
                        for (int i = 0; i < myArray.length; i++) {
                            System.out.println(dic.get("Input element") + "[" + i + "]");
                            myArray[i] = sc.nextInt();
                        }
                    }
                    int temp = 0;
                    while (true){
                        System.out.println(dic.get("Input element"));
                        System.out.println(dic.get("Exit text-1"));
                        temp = sc.nextInt();
                        if (temp == -1) break;
                        System.out.println(dic.get("Actual flag") + "[" + temp + "] = " + Integer.toString(myArray[temp]));
                    }
                    break;
                }
            }
        }
        while (option != 0);
        sc.close();
    }
}


why move this call to random here? step is called for every step (move, drop, whatever) and so is the call to random here. it is only needed when you need a new piece, in new game and add function. this change means a lot of calls to random which are not needed.


Can I be first mate? :P
/offtopic for the 1337th time


Not sure how your secret keys have been committed for 2 years with no issues! If you want to remove them: https://help.github.com/articles/remove-sensitive-data/


Hi,

On Sat, 2015-04-11 at 20:47 -0700, Michael Marineau wrote:
> Just added qemu 2.2.0 and enabled the aarch64-softmmu target in the
> SDK, is that generally new enough or is there something in the current
> 2.3 development that you recommend having?

2.2.0 is what I use, so it should be enough.

More recent QEMU should have support for the ARM PSCI (Power State
Control Interface).  I use the Foundation or Base models when I need to
work with PSCI (for my arm64 kexec work).

https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/psci.txt

-Geoff


OK


Ah, sorry. I considered doing this but assumed backwards compatibility wasn't a priority and that semver was going to be enough.


Right, good point


that's a superb idea! I think, I'll adopt that pattern soon


This script is badly broken with this commit. I intentionally checkout a clean copy of the code whenever releasing new versions to ensure that local uncommitted changes are not accidentally included. Also, maven-install is not a "release" command - it just copies the files to your local .m2 cache. The release plugin is supposed to release the plugin - i.e. to the plugin repo.


Sure


please reconsider this decision


простите за любопытство, но что это?


Dont just want left click window to appear on markers with street view available, so i took out no street view avail window and replaced it with universal info window.


I died laughing for some reason at "pilppe is a potato. ".


call createInfoWindw() which takes menuContent, map, and marker as arguments. Functionally it goes through the same check if info window is null to make sure we don't have multiple info windows up at the same time as fixed by @natyconnor


Fair enough


Thanks, forgot about that. Yeah we get a webidl compile error without that.

Cool, that solves my concern in #34 :)


I would switch the order here... "Like all code under [Basho Labs](https://github.com/basho-labs/), the below tools are "best effort" and have no dedicated Basho support.


are changes to `/home` and `/opt` persisted on reboots?


我想是因为函数没有被调用。this.init仅仅是被声明出来指向一个表达式，但是由于声明外部函数（类）不需要调用内部函数所以是不会主动执行的。
换言之，这里也只有在类实例化的时候才会执行~


Brawo Jasiu!


Sure, I agree with the reasoning exposed here.


lol :P


@Iazel Yes that's much much more elegant, there's 1 little logic error in there but much much cleaner syntax. This is how I will rewrite it.

```viml
function! ag#guessProjectRoot()
    let searchdir = ''
    let splitsearchdir = split(getcwd(), "/")
    while 1
      let searchdir = '/'.join(splitsearchdir, '/').'/'
      for marker in ['.rootdir', '.git', '.hg', '.svn', 'bzr', '_darcs', 'build.xml']
      if filereadable(searchdir.marker) || isdirectory(searchdir.marker)
          return searchdir
      endif
    endfor
    let splitsearchdir = splitsearchdir[0:-2] " Splice the list to get rid of the tail directory
    if len(splitsearchdir) < 3  " If size is that small we assume we won't find it anymore
      return getcwd()
    endif
  endwhile
endfunction

```


Just noticed a typo here: "and emtpty..."


Moved bytes in transit to only be associated with in_transit packet not in QueuedPacket class


GroundDomainUpdate (sushobhit) - Win64-Windows-7-VisualStudio-12: OK (1636 of 1639 tests passed)

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


Пожелания:
* функция должна заниматься только одним делом — если это `bubble_sort`, то она должна выполнять только сортировку пузырьком, но не формировать массив чисел с нечетными индексами и не выводить информацию на экран;
* собственно, выборку нечетных элементов можно было вынести в отдельную функцию;
* вывод (помимо функции `super_printf`) тоже можно оформить отдельной функцией, т.к. там происходит по сути одно и то же, только название алгоритма меняется — его можно передавать в выводящую функцию.


The ammunition_exclusions_multiplication section is currently not used as the same function is controlled in the ammunition_materials by the <multiply> line.


Ok, I was worried it would cause an error but it sounds like it won't, just duplicate effort


GroundDomainUpdate (mmatts) - x86_64-MacOS-10.9-clang: OK (1630 of 1633 tests passed)

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


Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

C:\Users\GODI\Documents\GitHub> - - qcom,noise-rjct-scl : Number of low samples
on clock line to consider it low.+ - qcom,i2c-src-freq : Frequency of the source
 clocking this bus in Hz.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,noise-rjct-scl : Number of low samples on clock line to consid
er it low.+ - qcom,i2c-src-freq : Frequency of the source clocking this bus in
Hz.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       Range of values is 0-3. When missing def
ault to 0.+      Divider value is set based on soruce-frequency and
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        Range of values is 0-3. When missing default to 0.+      Divide
r value is set based on soruce-frequency and
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,noise-rjct-sda : Number of low samples
on data  line to consider it low.+      desired I2C bus frequency. If this value
 is not
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,noise-rjct-sda : Number of low samples on data  line to consid
er it low.+      desired I2C bus frequency. If this value is not
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       Range of values is 0-3. When missing def
ault to 0.+      provided, the source clock is assumed to be running
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        Range of values is 0-3. When missing default to 0.+      provid
ed, the source clock is assumed to be running
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,i2c-src-freq   : Frequency of the sourc
e clocking this bus in Hz.+      at 19.2 MHz.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,i2c-src-freq   : Frequency of the source clocking this bus in
Hz.+      at 19.2 MHz.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       Divider value is set based on soruce-fre
quency and+ - qcom,scl-gpio     : I2C clock GPIO number. Required for execution
of bus
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        Divider value is set based on soruce-frequency and+ - qcom,scl-
gpio     : I2C clock GPIO number. Required for execution of bus
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       desired I2C bus frequency. If this value
 is not+      recovery procedure.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        desired I2C bus frequency. If this value is not+      recovery
procedure.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       provided, the source clock is assumed to
 be running+ - qcom,sda-gpio     : I2C data  GPIO number. Required for execution
 of bus
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        provided, the source clock is assumed to be running+ - qcom,sda
-gpio     : I2C data  GPIO number. Required for execution of bus
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       at 19.2 MHz.+      recovery procedure.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        at 19.2 MHz.+      recovery procedure.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,scl-gpio       : I2C clock GPIO number.
 Required for execution of bus+ - qcom,active-only  : Vote for core clock when t
he application processor goes
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,scl-gpio       : I2C clock GPIO number. Required for execution
 of bus+ - qcom,active-only  : Vote for core clock when the application process
or goes
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       recovery procedure.+      to active stat
e and remove that vote when it goes to idle
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        recovery procedure.+      to active state and remove that vote
when it goes to idle
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,sda-gpio       : I2C data  GPIO number.
 Required for execution of bus+      state. This flag may improve service time o
f first i2c
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,sda-gpio       : I2C data  GPIO number. Required for execution
 of bus+      state. This flag may improve service time of first i2c
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       recovery procedure.+      request at the
 expense of power consumption. When this
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        recovery procedure.+      request at the expense of power consu
mption. When this
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,active-only    : Vote for core clock wh
en the application processor goes+      entry is not present, voting is done by
the runtime-pm
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,active-only    : Vote for core clock when the application proc
essor goes+      entry is not present, voting is done by the runtime-pm
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       to active state and remove that vote whe
n it goes to idle+      callbacks.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        to active state and remove that vote when it goes to idle+
 callbacks.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       state. This flag may improve service tim
e of first i2c+ - qcom,master-id    : Master endpoint number used for voting on
clocks using
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        state. This flag may improve service time of first i2c+ - qcom,
master-id    : Master endpoint number used for voting on clocks using
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       request at the expense of power consumpt
ion. When this+      bus-scaling driver.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        request at the expense of power consumption. When this+      bu
s-scaling driver.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       entry is not present, voting is done by
the runtime-pm+ - qcom,clk-ctl-xfer : When present, the clocks's state (prepare_
enable/
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        entry is not present, voting is done by the runtime-pm+ - qcom,
clk-ctl-xfer : When present, the clocks's state (prepare_enable/
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       callbacks.+      unprepare_disable) is c
ontrolled by i2c-transaction's
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        callbacks.+      unprepare_disable) is controlled by i2c-transa
ction's
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,master-id      : Master endpoint number
 used for voting on clocks using+      begining and ending. When missing, the cl
ock's state
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,master-id      : Master endpoint number used for voting on clo
cks using+      begining and ending. When missing, the clock's state
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       bus-scaling driver.+      is controlled
by runtime-pm events.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        bus-scaling driver.+      is controlled by runtime-pm events.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> - - qcom,clk-ctl-xfer   : When present, the cloc
ks's state (prepare_enable/
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:4
+ - - <<<<  qcom,clk-ctl-xfer   : When present, the clocks's state (prepare_ena
ble/
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       unprepare_disable) is controlled by i2c-
transaction's
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        unprepare_disable) is controlled by i2c-transaction's
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       begining and ending. When missing, the c
lock's state
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        begining and ending. When missing, the clock's state
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub> -       is controlled by runtime-pm events.
'-' 一元運算子後面遺失運算式。
位於 行:1 字元:2
+ - <<<<        is controlled by runtime-pm events.
    + CategoryInfo          : ParserError: (-:String) [], ParentContainsErrorR
   ecordException
    + FullyQualifiedErrorId : MissingExpressionAfterOperator

C:\Users\GODI\Documents\GitHub>


Yeah, you're right. I looked again at the coercion code, and it figures the type out pre-autoref, but then adjusts it (by wrapping it back in the pointer) before adding it to the adjustment. I had missed that second step before.


You spelled "restaurants" wrong.


Do I really do that much PHP? Not really much to do without access to the forums. I'll stick with front-end, I guess.


@whyrusleeping it also depends on how often people might want to upload a new version. If they want to upload a new version every day and there are only a few new objects each day, then always unpacking the pack files makes sense.


Не могу понять, для чего нужен "Массив, хранящий выбор сортировки". Можно считать строку, и в зависимости от её значения присвоить переменной, например `int sorting_algorithm`, соответствующее значение (`INSERTION` или `BUBBLE`).


dosc


Looks good.


MarkdownDocs (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1129 of 1129 tests passed)

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


@andrewjcole  I didn't be knowin' we were runnin' a scurvy pirate ship, though we be keepin' thin's ship shape fer all ye pirates to heartly enjoy! Ye can add first matey to ye jobs list if ye want. :P


Looks like this commit broke build.
Please see http://ci.cgeo.org/job/c-geo/3644/console to remedy the problem.


This check doesn't work because IID_ID3D11ShaderReflection isn't a macro, so it's never defined. Thus this will break anyone who has the real correct headers.


*oh, hi*


also added jquery libs in ui for datepicker (for action steps), slider and mouse (req'd for slider)


drop these two lines.


есть логика автоудаления логинов которые были зарегистрированны, но так и небыли активированы в течении недели. Она ломалась, если кто-то ставил remark на неактивированный ник. Этот коммит исправляет данную проблему.


I'll make this change and squash it in as part of my history re-write.


+ - qcom,i2c-src-freq : Frequency of the source clocking this bus in Hz.
-		       Range of values is 0-3. When missing default to 0.		+		      Divider value is set based on soruce-frequency and
- - qcom,noise-rjct-sda : Number of low samples on data  line to consider it low.		+		      desired I2C bus frequency. If this value is not
-		       Range of values is 0-3. When missing default to 0.		+		      provided, the source clock is assumed to be running
- - qcom,i2c-src-freq   : Frequency of the source clocking this bus in Hz.		+		      at 19.2 MHz.
-		       Divider value is set based on soruce-frequency and		+ - qcom,scl-gpio     : I2C clock GPIO number. Required for execution of bus
-		       desired I2C bus frequency. If this value is not		+		      recovery procedure.
-		       provided, the source clock is assumed to be running		+ - qcom,sda-gpio     : I2C data  GPIO number. Required for execution of bus
-		       at 19.2 MHz.		+		      recovery procedure.
- - qcom,scl-gpio       : I2C clock GPIO number. Required for execution of bus		+ - qcom,active-only  : Vote for core clock when the application processor goes
-		       recovery procedure.		+		      to active state and remove that vote when it goes to idle
- - qcom,sda-gpio       : I2C data  GPIO number. Required for execution of bus		+		      state. This flag may improve service time of first i2c
-		       recovery procedure.		+		      request at the expense of power consumption. When this


where do you need this?


What is this 'x' for?


Sorry, I've done a little more refactoring, take a look at the previous post :P

For the logic error, you mean the leading slash? If it is that, I don't think its worth to fix it because `:lcd` will understand it correctly


Extra semicolon?


:pig: <-- What happened when I tried to get a pirate emoji. :P


This should be in Utils somewhere.  It's valuable.


I think that is the case when checking for coercions during type checking, but not in trans (in both cases, logically and actually). I.e., you are right from the perspective of the code which is generated, but not from the perspective of how the adjustment itself is created. I tend to think of these adjustments from the latter perspective, but perhaps that is not so helpful.


This is actually the same thing I made at ORCHARD the year we had the
python class.

    ____       __
   / __ \___  / /____  _____
  / /_/ / _ \/ __/ _ \/ ___/
 / ____/  __/ /_/  __/ /
/_/    \___/\__/\___/_/

Not sent from my iPhone because I don't have one

On Mon, Apr 13, 2015 at 11:51 AM, ParkerMc <notifications@github.com> wrote:

> cool pie
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PieCrafter314/python-browser-bar/commit/205dba1a7a3e7e8d2a89ce40a028690a68e0cadd#commitcomment-10696665>
> .
>


test


Good


Splitting the array must be outside of the for, otherwise it splits the array way too soon.


I copied this from the previous documentation. @ibuildthecloud would need to answer the question.


Is the idea that `icon` is a favicon?  I think we should say as much if that's the case.  But I'm not convinced the `RemoteTab` model should know that -- it's strictly a presentation concern at this time.


masih ada bugnya


This will not work. It also does the exact same thing I'm doing in the other test.

Deproxy doesn't give out the exact data for the request, and so this test will never indicate failure. Or am I wrong?


Ok. I've found some different opinions here http://stackoverflow.com/q/1296843. Apparently `NUL` is not in the standard.

But this is off-topic and I don't want to distract anybody so I'll drop it.


docs


This is definitely not the cleanest way to do this. I figured you would have better view on how to best parse and pass arguments, so I just wrote something that works for now.


add a variable in for too - even though it will be empty as a default. But, any template that pulls it in can give the for attribute some content


Then don't update Forestry.

Forge made breaking changes to Fluids. All other mods have been updating. We aren't going to not update just because of Greg. Greg seems to be the only one rooting himself into an older Forge version.


lol :P I guess GitHub is in need of a pirate emoji!


Also, `asURL` should be a computed value rather than a method.


92380320_RadianceGTest (evanweaver) - x86_64-MacOS-10.9-clang: Tests Failed

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


Ops, you're right, that's slipped!


Sure. As discussed during the Monday meeting, we could temporarily change the current avocado config to point to mocked sysinfo commands/config files. I'm happy with the compromise made here.