This catches not enough potentials and catches false positives. In it current state it's not useful:

- misses addAttributeToFilter (which delegates to addFieldToFilter, but the offending code will be here
- flags addFieldToFilter('`novariablehere`'), which should continue to work without issues.
- does not catch any multiline variants as scanner is line based.


http://api.themoviedb.org/3/movie/top_rated?api_key=please create ur own api_key


lol; was meant to be


I am under the impression that it should cover all specializations already.


**Code Functionality: Nitpick**

Limit is expected to default to 20 records per page. You could write `limit = request.arg.get('limit') or 20`.


Does it help to fix the bug #15 ?


**Code Quality - Nitpick**

Compare variables as truthy or falsy, not `undefined`.


93653546-FuelGenShowingInABUPSwhenPV (mjwitte) - x86_64-MacOS-10.9-clang: OK (1947 of 1954 tests passed)

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


@nemeth thanks! I was *just* about to comment :+1:


Sample code in scala :

```scala
object App {
  var last_event : Long = -3600000

  var lastMessage : String = _

  def updateStrip(data:String) {
    if(data.length()>0){
      lastMessage = data
      last_event = millis()
    }
  }

  var current: Long = _

  def setup() {
  }

  def loop() {
    current = millis()
    val data = "test"
    if(data.length() > 0) updateStrip(data)
  }
  def millis() : Long = -1

  private def test2args(x:Long,y:Long) = x+y
}
```

will be translated to :

```c++
class App
{
public:
static long $last_event;
static long last_event();
static void last_event_$eq(long $x$1);
static String $lastMessage;
static String lastMessage();
static void lastMessage_$eq(String $x$1);
static void updateStrip(String $data);
static long $current;
static long current();
static void current_$eq(long $x$1);
static void setup();
static void loop();
static long millis();
static long test2args(long $x,long $y);
};
long App::$last_event = -3600000;

long App::last_event() {
return App::$last_event;
}

void App::last_event_$eq(long $x$1) {
App::$last_event = $x$1;
}

String App::$lastMessage = "";

String App::lastMessage() {
return App::$lastMessage;
}

void App::lastMessage_$eq(String $x$1) {
App::$lastMessage = $x$1;
}

void App::updateStrip(String $data) {
if($data.length() > (0)) {App::lastMessage_$eq($data);
App::last_event_$eq(App::millis());};
}

long App::$current = 0;

long App::current() {
return App::$current;
}

void App::current_$eq(long $x$1) {
App::$current = $x$1;
}

void App::setup() {
;
}

void App::loop() {
App::current_$eq(App::millis());
String $data = "test";
if($data.length() > (0)) {App::updateStrip($data);};
}

long App::millis() {
return -1;
}

long App::test2args(long $x,long $y) {
return $x + ($y);
}
```

This code was verified on Build from Particle.IO and compilation worked well ! :)


Okay, I understand :+1:


thanks.


Refer to https://github.com/Andela-thomas/Dms-ODM-database/commit/96c3f87733812abeb1eacd5306774988ca84490e#commitcomment-14065148


We can't just return an image here, cause ImageDecompresser is also responsible for resizing images.


Is now :)


Thanks @namin , I'll consider the first approach. Anyway, as @sstucki mentioned, in the typing rules, we'll definitely allow un-inhabitable types in the typing environment. As this issue only concerns the formulation of effect safety, I want to delay it a while and go back to it after the soundness(progress/preservation) proof.


thanks!


rückgängig mache. das isch notwendig.


here is an example data viz in which we can observe the problem. http://bl.ocks.org/tdhock/raw/e5b881395291477bb1b7/ clicking the interactive legends hides a different set of points in the first and second plots! It is misleading, and occurs just because both interactive legends are assigned to the `show_fill` variable, and the `vs` and `am` variables happen to both have just two values: 0 and 1.


We're avoiding creating the `SparseVector`  and using the slow `find` and `filter` by simply using `nzrange` with another loop. Nice!


A semicolon typo


I plan to eventually replace all the debugging code with the python logging module, which lets you set the levels in a less global way.


This is by far the best update to this project i have seen!


We might not need anything as elaborate as Martin's rules. What if we just had a judgment for "capability producing" types, e.g.

                               Γ ⊢ B caprod
    ------------ (CP-Eff)    ---------------- (CP-Fun)
    Γ ⊢ E caprod             Γ ⊢ A → B caprod

Anyway, I think it's fine focus on something else and to come back to this issue later on.


However, does this take us a step closer to essentializing this entire bfs generation as a series of Sparse Matrix Sparse Vector multiplies?


I would prefer the help to be an empty string. This way it adds no additional value and looks weird in the help output. It can't be left out immediately or it would not show up the help output.

It could be handled in the `set_command` function – if there is no help in `kwargs`, add empty string.


It's ok for me, and sure a better way to manage logging. ;-)


Also, FreqDist doesn't have attribute "iteritems()"  instead items() in NLTK 3.0


**Code Functionality: Critical**

Querying should come before pagination. This is so that I can call the endpoint with a query while also setting a limit for records to be returned per page i.e `/api/bucketlists/?q=x&limit=c`


I really didn't get what you think it's crazy about it. It is absolutely
the same complexity of any vargs usage out there.

On Wed, Oct 28, 2015 at 5:18 PM, Gustavo Lima Chaves <
notifications@github.com> wrote:

> Maybe we should document these crazy out vargs.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mbelluzzo/soletta/commit/54997f7e21dccc3baa804ecaefc8460904237274#commitcomment-14049385>
> .
>


Je vais voir pour les intégré dans le collecte.tar.gz.
Pour le nom du fichier aprés mise à jour il suffit de regarder dans le getfiles.py du collector puis ensuite le files.sql toutefois j'ai encore quelque problème avec strings.exe et au niveau de l'analyse de la collecte.
Mais tout avance bien.

Oui il manquait un ```;``` mais c'est tout bon.
Merci pour t'es remarques.


Probably not!  When I get a chance, I'll take it out ... or I would accept a PR removing it.  :wink:


prefer `color` > `colour` (unless project is handled otherwise)


:+1:

And supersede https://github.com/lloyd/yajl/pull/146


pass until discussed


Looks great and seems to be right. Well done @CodeLionX


* addAttributeToFilter should be safe since that only allows actual
attributes and errs otherwise. (I could be incorrect.)
* Any addFieldToFilter expression including backticks is broken after the
patch, even if it does not include a variable. Try it yourself.
* No, it does not catch multi-line variants, or variants using a variable
or other approaches. If you can come up with a way to do that in any
practical and reliable manner, submit a PR.


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


<!-- PMABOT:SOB -->
This commit is missing Signed-Off-By line to indicate that you agree with phpMyAdmin Developer's Certificate of Origin. Please check [contributing documentation](https://github.com/phpmyadmin/phpmyadmin/blob/master/CONTRIBUTING.md) for more information.


Is 5.2 repo up? I have this error
revision master in arter97/arm-linux-androideabi-5.2 not found


@sstucki -- cool, that could work. it comes as a surprise that you don't need to consider the contra-variant position `A` at all, but why not, since even if it's `E`, we're all good.


I see that in database it is called `colour` - could you change that? Through the whole project it's used sparingly - can lead to some irritating bugs.


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


**Code Quality: Nitpick**

It might be nice if you created a `.extend` method in the `BucketListItem` Model class. This way, the method can simply accept a dictionary and update the object by looping over the keys and updating the attributes individually.


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


You're right, my bad.


You're welcome! Big fan of your work @mjackson :)


i would create a method `maintenance?` and check that.


You're testing with a regular expression if *each* line starts with `connecting at`. It is probably much faster to test with this trick `lines[i].lastIndexOf('connecting at', 0) === 0`


Why did you revert this one?

This way fails for me with:
```
    Module build failed:
    	filter: progid: DXImageTransform.Microsoft.gradient( startColorstr='#ffffff', endColorstr='#037db9e8', GradientType=1);
            ^
          Non-terminal statement or declaration must end with ';'
          in /Users/my/src/node_modules/simplemde/src/css/simplemde.css (line 95, column 10)
     @ ./~/simplemde/src/css/simplemde.css 4:14-105 13:2-17:4 14:20-111
```


I changed all the throws to do pdal_error UNLESS they were being locally
caught, which almost none were.  If you need to filter a particular
exception, then the exception type should be changed.

On Wed, Oct 28, 2015 at 11:32 PM, Howard Butler <notifications@github.com>
wrote:

> Yeah, that's what the trampoline throws. It used to throw a specific
> pdal::gdal_error but that seems to be gone now.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PDAL/PDAL/commit/c4898cab0df4dadd643081cd5052fbba41251cf2#commitcomment-14057982>
> .
>

--
Andrew Bell
andrew.bell.ia@gmail.com


If you look at the generated code - before the pragmas went after the { and before the }, now they go before the function definition and after the }

The second parameter to addQuotedCompound is a string that appears after the closing } - the addQuotedCompound implicitly adds the { and } and causes subsequent stuff to go inside them


This is crach log. rev.20b4e6f03adc29e486e20866222a42e8935704b4
OS: Win10 x64
build in DEBUG by VS2013 Update5
part1: http://pastebin.com/fm7htrjM
part2: http://pastebin.com/smkG2qV5


> very performant.

thanks! this code is very close to what I had on earlier versions. I just wanted to simplify since we use this so much!

> you can still do the array notation

great point! I'll have to make a note of that on the readme! (unless you want to do a pr?)


Hmm.
https://github.com/arter97/arm-linux-androideabi-5.2


It seems to me "capability producing" types are those together with `B` we can prove `E`.

If I were right, the formula `B -> (E -> E) -> E` can't be proved, thus `E -> E` is not a `capacity producing` type.


Ceci est un commentaire réalisé sur Github jeudi après-midi.


here you could also check that with `f.object.maintenance?` - would look a little better.
Also it would be nice to introduce view object here which you would use like:
`class: projects_view_object.hide_maintenance!` (naming is just a proposal)


I'm a bit confused about the role of this method, as the term children refers to the direct children in the docs of the other Inventory methods, while this methods seems to return the leaf nodes.


`num::Finite`? Ah, no. The linter told me it was an uneeded import.


Typo - should be 'processing'.


I think it would be better to actually create canary template - simply copy the last one to canary-template.txt and apply the changes there. We're not going to alter already published canaries...


IS BUG


no pr for me. trying to be anonymous as much as possible. plus it would take me too long to get the shit together. I am not to organized in this area yet.


Any reason why? The same doesn't happen on Laravel (https://github.com/laravel/laravel/blob/master/.gitignore).


no, not really. I can keep looking at it, but I have to prepare a talk for tomorrow and have several hours of phone calls on friday.


Hi,

When do you expect to release Atlas for Android please?

Thanks,
Manar


93653546-FuelGenShowingInABUPSwhenPV (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1953 of 1960 tests passed)

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


Tested?


ローカルコストマップに初期値として50のコストを与え， /filtered_cloudを受け取った時，そのグリッドのコストをフリーにするようにした


Lol, English is my first language after all :) ... oh :0 Not sure about the is/are change, though. I think this should be 'are' as 'images' is plural.


@karthilxg Perfect! Thanks!


Thanks.. my bad.


wieso machsch du das gnau? es gaht meh um es einheitlichs naming:
``add-expense-items`` → ``expense-items``
``edit-expense-items`` → ``expense-items``
``globalMessage`` → ``globalMessages``
``adminPoolGraphs`` → ``administration.graphs.``

usw. hald so dasses sinn macht. das ganze isch über dziit gwachse und het drum inkonsistenze dinne.


Hi,
I don't understand these changes (with lines 4745).
Leftover from a test or a bad patch ?

Regards
Didier


Edit name: navigationbar centered


I don't understand why you try a value of 100 if `_max_value_warning` is not `None`. Perhaps what you meant to try was something like `100 * _max_value_warning` or `100 + _max_value_warning`?


Is OCTTransform() throwing or just returning an error?  This is the bit
that I don't understand.

On Thu, Oct 29, 2015 at 7:32 AM, Andrew Bell <andrew.bell.ia@gmail.com>
wrote:

> I changed all the throws to do pdal_error UNLESS they were being locally
> caught, which almost none were.  If you need to filter a particular
> exception, then the exception type should be changed.
>
> On Wed, Oct 28, 2015 at 11:32 PM, Howard Butler <notifications@github.com>
> wrote:
>
>> Yeah, that's what the trampoline throws. It used to throw a specific
>> pdal::gdal_error but that seems to be gone now.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/PDAL/PDAL/commit/c4898cab0df4dadd643081cd5052fbba41251cf2#commitcomment-14057982>
>> .
>>
>
>
>
> --
> Andrew Bell
> andrew.bell.ia@gmail.com
>

--
Andrew Bell
andrew.bell.ia@gmail.com


Just realised I'm using 'I' here - happy to change this to "Gian started off .." and "Mohamed ..." to personalise, or we could change to 'we' if you would prefer?


I did test it manually both with and without encryption with about a gigabyte of generated data and with a real use case while working on a streaming xlsx writer. Still an automated test would be preferable.


why like that?
this should work `'click .js-remove-team': 'removeTeam'`


Additionally to the inline comments, some more issues regarding the whole commit.

- `js/vendor/.DS_Store` shouldn't have been committed to the repo (please remove it and from cache too!)
- The commit message could have been more descriptive (or even better, commits be split logically so if one would want to revert one change it would be easy)
- Work shouldn't get pushed directly on the development branch, but on a feature branch and then make a PR (pull request) to the development branch.
- Commented out code shouldn't exist in the commit (I've mentioned it in a comment but there are more examples of it).


we discussed to do this in 1.2.6


If you want, just use the syntax [Mohamed](https://twitter.com/mzaatar) and your name will just link to your twitter account. Also, I used Mohamed as that is the most common for me (to use first names), but if you prefer Moh, Zaatar etc then please change as you like!


**Test Coverage - Critical**

Your `searchIndex` function should provide a consistent output.
As we discussed, the result should always be an Array that contains the index of the strings/words searched for.
Hence, this expectation should be `[0]` not `0`, so it matches the result of line _122_.

This inconsistency is found in lines _123_, _124_ etc.


demo说明

前面input里面的name是一样的时候，获取到的东西就是一个数组
```
<QueryDict: {u'a': [u'1', u'2'], u'csrfmiddlewaretoken': [u'ZWOI2eAhzuIQiRn1lgTcxZ4Lg7AcpYjw'], u'b': [u'3']}>
```

这个demo获取到的东西是这样的


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


Didier...

Looks like a bit of leftover cruft from a manual merge.
I'll kill it.

Thanks
Dave


hehehe


Good one! Perhaps this is also a good change to make to the initial value of `min` in the function `getRandomValue()`?


pass until discussed


3DURGの向きをぎりぎりまで変えても直近1mほどの地面の点群が取得できず，回避する直前でコストが消えてしまうため3DURGからの障害物情報を使うことを断念


**Code Quality: Nitpick**

You should add comments as much as possible. Always ensure the comments for your methods are descriptive of what it seek to achieve. Javadoc style is recommended.


It's wrong, ignore it. These changes were since reverted.


Thank you for putting up with all the questions. dvm is my first go app! :-) I need a Christmas ornament for it...


dá pra trocar esse foreach e esse if por um lambda.


AstroMenace still saying 'no' :

````
Program received signal SIGSEGV, Segmentation fault.
0xb6e2ad8a in gl_pointer_index (p=p@entry=0xb6e5f9ac <state+188>, index=index@entry=0) at /home/odroid/temp/glshim/src/gl/array.c:206
206         GL_TYPE_SWITCH(src, ptr, p->type,
#0  0xb6e2ad8a in gl_pointer_index (p=p@entry=0xb6e5f9ac <state+188>, index=index@entry=0) at /home/odroid/temp/glshim/src/gl/array.c:206
#1  0xb6e3eee2 in glArrayElement (i=0) at /home/odroid/temp/glshim/src/gl/gl.c:1244
#2  0xb6e3f4b2 in glDrawElements (mode=7, count=1868, type=<optimized out>, indices=<optimized out>) at /home/odroid/temp/glshim/src/gl/gl.c:648
#3  0x00022ccc in vw_SendVertices(int, int, int, void*, int, unsigned int*, unsigned int, unsigned int*, unsigned int*, unsigned int*) ()
#4  0x00030fcc in eParticleSystem::Draw(eTexture**) ()
#5  0x0002f7a8 in vw_DrawAllParticleSystems() ()
#6  0x000708ce in DrawAllObject3D(int) ()
#7  0x0004dfb0 in DrawMenu() ()
#8  0x00020fec in Loop_Proc() ()
#9  0x0001e64c in main ()
````


daria pra colocar essa parte aqui que converte dentro do lambda.


Whenever you get the time, thanks.


Tja, und gerade heute kommt alpha-45 raus! ;-)


Can you add a parameter for this directory too?

Awesome work!


no text!


Unnecessary spacing detected.


Две навигации? Стоит ли распиливать?) Лого можно тоже считать частью навигации.. + вопрос: логотип — это декоративное или контентное изображение?)


Thanks for the good suggestions!
Only “Link-Layers” smells German to me. :) I’m sure the hyphen is not needed in English.
I’ll merge and change it back to “Link Layers”.


Fair enough.  Lesson learned.  Sorry about that.


Remove `test` from the class name name.


@2betop 改了模块的依赖版本就解决了么？这么吊


лишний элемент, на мой взгляд)


Remove `test` from the class name.


I surely plan to add more configuration parameters, but I'd rather postpone them to different PRs. I like to keep my PRs as small and easy to accept as possible.


They can, through the dedicated port to that. The main use of this family of nodes regarding initial values is to get them dinamically, so I did not bother replicating this via options.


viewに入れちゃってます。


the method name isn't formatted well


Ooops, true. Thanks.


// Sent not "Sended"


Divide by 0 error could be thrown here


"then the next NDIRECT distance symbols"


You're right, defining arguments for those events is redundant. Cleaned in 8ad20704269188faa34a8fc6514504461aeaeab9


длинные тире (—) можно ставить так: `—`, а ещё лучше перед ними ставить неразрывный пробел: ` `


initialize integers to 0


@dragonjet theres no great success image for exped tab :sweat_smile:
![error](https://cloud.githubusercontent.com/assets/13024936/10818859/45d7ecbe-7e77-11e5-91fd-a48d5146cc48.png)


Afaik this would work better:

    de method_missing(method_name, *args)
      return self[method_name] if key?(method_name) && args.empty?
      super
    end

because if you have extra args something is wrong, and the key compliance is handled by methods you delegate to.

Also, you want `respond_to_missing?` in companion to this.


This is the sum, not the average!


average is not initialized with a value


Style convention not followed for method name


why are you returning 0?


This is the average, not the sum!


average += x[i] / x.length


Yes!! I use MYSQL_PWD instead of -p option!!
If you use any other variable name, you have to be set -p option at line 149 and 153 and 160!!


could you also change "distance special symbols" to "special distance symbols" to be consistent with other usages?


This should be the total sum?


average is not initialized


@andela-gukpere Fixing this right now.


should be args not argv


clearfix'ов то сколько) точно всё осознанно расставлено?)


Possible deadlock? `lazy` vs storage manager


Improper function name


In the future, can you put new news items at the top? I think that's less likely to cause merge conflicts


Should be every first letter in capital letter


average and sum variable names should be switched


Value returned is not average.


initiallize sum


Undo commit 2312a93, because it is obsolete


initialize average


@andela-gukpere I have updated the repo with the correct tests for search results.


The correct param should be args not argv


the method should be void possibly.


bad variable name
Consider switching average and sum


I mean it's eventually initialized so don't see too much of a problem with that


average=sum/number of elements, but you should introduce an if statement to avoid division by zero


    wrapper.nonexistent_key # nil. Don't think you would want this
    wrapper.do_something_from_activesupport_that_is_not_supported(x, y, ...) # nil?


sum and average are mixed up


average = sum/length


method name convention not followed


Average not sum.


Wrong identifier used
should use "sum"


@2betop  感觉现在的js模块化的构建打包，还是不够傻瓜，太麻烦了，一堆配置~哎，能不能再傻瓜一点。之前看FIS3，好像也没有很好的解决此问题。


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


check if x.length > 0 first


names are flipped


вроде ссылкой должно быть) ну и не похоже на блочный элемент...


why 0?


camel case please!


в текст ссылок можно добавить `Twitter`, `Facebook`,...


method itself doesn't need to return anything if you're trying to print out inside the method.


^ important as if the for loop doesn't run for some reason (i.e. length=0) then the var is never initialized


no need for return statement since you are already printing out the sum and average


Mr McIntosh, you've coded for how long? Surely you know not to use capitalization in this manner. The first letter of each word suffices.


deal.


method name convention did not followed, should be printSumAndAverage


Wrong Identifier used again.
Average = sum/x.length


You can actually name this whatever you want.


:cool:


inside the loop should be sum instead of average, and average = sum/x.length


Should be static method


зачем лишний див?


Wrong prints


should be String []args


this is the sum of the array not average


это ссылки должны быть


the average should be double to support the use of decimals. (e.g array has 1,0,1; needs to print out 2/3).


Don't need to create an object since it is in the same class


^except the first one


лучше использовать data-pause=paused  или вообще ставить атрибут и удалять его, т.к. из-за приведений типов в js может быть гемор


integer division will lead to errors. Change sum and average to floats.


The file `tests/runtest.py` was reviewed by me up until this commit.


why is there an object initialization here


wrong type


вот, намного лучше)


Should not return 0


X is not an array.


можно ещё перелинковать страницы между собой


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


I didn't experience no crash issues when I coded it. There are possible KeyErrors I suppose might occur under weird circumstances if in a dict. To fix an error like that with sourcecoder would mean the dev/user would have to delete or reinitialize the default variables... which means if the saved app launchers paths are are deeply rooted in a saved dict/pickle then the user might have to delete the pickle(Py2 and Py3 pickle are not compatible by default vise-versa(2 to 3, but not 3 to 2)). If it is an ini or simple readable text file, then the user can just edit the path hopefully.
I would assume the code takes care of themost of the  ``if not os.path.exists`` issues already.

krita 16,24,32.png yes, are the sizes(squared).
Ex: 32x32 pixel png for krita32.png


йой. зачем же его числовым делать, если у нас есть как раз для таких целей прекрасные true/false?


Method name


@daywbdb

第14行左右的内容是否需要做一些code clean up?

https://github.com/DennyZhang/devops-knowledgebase/commit/84f6bbb494ff1033a1b3333a4d2b34a72463c2c1#diff-a4b986e7476f06ec6f7401238c38b2e5R14

==================
第47行左右

max_connect_number建议重命名为max_retries_count

https://github.com/DennyZhang/devops-knowledgebase/commit/84f6bbb494ff1033a1b3333a4d2b34a72463c2c1#diff-a4b986e7476f06ec6f7401238c38b2e5R47


@wiliam29 Valeu pelo commit irei aceitar


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


Average and sum should switch positions here. "average" switches place with "sum" earlier on.


`img/rate-stars-3.png` — я бы из одно


I would vote for not casting it into being a toolbar button.
To me, the "tiddler toolbar" is a well defined spot and that toggle is not part of it.

Perhaps the "Toolbars" tab could be called "Controls" instead.

Then there could be a "Tiddler Controls" subtab... with a group heading called "Toolbar Buttons" listing all buttons and at the bottom a section perhaps called "Additional Controls" allowing to toggle tiddler folding.


`fn_item` (same as `impl_method`) should implement `RustNamedElement`, not just `NavigatablePsiElement`


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1028.b9357da0c3b4e6d41f3d39bb18014bd1162fe76e](http://build.palaso.org/viewLog.html?buildId=65078&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 694, ignored: 6 Build time: 00:15:12


Отлично!)


object initialization is there because printSumAndAverage method is not static
but printSumAndAverage could/should be made static


Круто!


@daywbdb 建议不要做sleep 5，这个magic number。将它定义为一个变量。

L65: 一般是这样for (i=0; i < $max_connect_number; i++), 这样你也可以去除L73

L68: 可以用简化为： curl -I -s --connect-timeout $timeout -m $maxtime $website -w %{http_code}  | grep '200 OK'

https://github.com/DennyZhang/devops-knowledgebase/commit/84f6bbb494ff1033a1b3333a4d2b34a72463c2c1#diff-a4b986e7476f06ec6f7401238c38b2e5R65


Why not remove the default bucket entirely, and generate this UUID on the client-side?


Только наоборот: `PTSans, Arial, sans-serif;`


Just a suggestion which doesn't have anything todo with this commit: It looks like @Raureif is the account of your company and you're using @frankrausch as a personal account.

Why don't you convert @Raureif to a organization then? If you ask me, that would make much more sense. And of course: No, you won't loose your repositories.

Team members should respectively use separate accounts.

Here's a doc on how to convert it: https://help.github.com/articles/converting-a-user-into-an-organization/


```
DEBUG: Better Fig. PATH: /home/xenith/git/opsech.io/content
DEBUG: Better Fig. img.src: {filename}/images/dnf_changelog.png
DEBUG: Better Fig. img_path: {filename}/images
DEBUG: Better Fig. img_fname: dnf_changelog.png
ERROR: Better Fig. Error: image not found: /images/dnf_changelog.png
DEBUG: Better Fig. Skip src: /images/dnf_changelog.png
```

Getting this error following your instructions on duncanlock.net, the path of the article is

`content/articles/2015/dnf_changelog.md`

and the path of the image is:

`content/images/dnf_changelog.png`

the image is sourced via markdown in the above-mentioned article as such:

`![dnf_changelog.sh]({filename}/images/dnf_changelog.png)`


Good PR though, `NavigatablePsiElement` is a 'dilluted' interface -- every PSI element in our hierarchy is `N avigatablePsiElement`, so i believe `RustNamedElement` would be a better shot.


Ok, after a quick search, there's no silver bullet for doxygen + variadic functions, other than mentioning something like "the rest of the arguments make up for the <whatever semantics>".


Good idea, merging.


зачем эта строка? по-умолчанию и так авто)


5255-EMS-dual-Temp-Node-Setpoints (EnergyArchmage) - x86_64-MacOS-10.9-clang: OK (1954 of 1954 tests passed)

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


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


`self.app.stop()` should work


It is because the default bucket feature is not the name of the bucket but the implicit collections creations in it, which let developer use it without having to make sure at each application starts that the collection already exists.


Please format the comment according to README.Coding:

/*
 * foo foo
 * bar bar ...
 */


Про колонки — напомни, расскажу подробнее


C'est moi qui ai utilisé magic car ça permet de détécter le type de fichier facilement pour un binaire, même si le nom de fichier n'a pas d'extension.


Tell me if I'm following here: In this method, a range is generated based on fuzziness to determine the target color and the +- color range for replacement. If the pixel falls within the range then the color bytes are modified based on how far off the target color they currently are;

Pre-edit: From an outside perspective, I think some confusion due to variable naming is occurring: originalR/G/B led me to believe we were talking about the original color of the current pixel, not the 'original color R/G/B that you targeted for replacement'.

eg: We are replacing RBG 200,200,200 with 200,0,0 and a fuzz of 10.
     Pixel 1,1 is RGB 200,200,200
          Replace original R 200 with replacement R 200 (200 - 200 + 200).
          Replace original G 200 with replacement G 0 (200 - 200 + 0).
          Replace original B 200 with replacement B 0 (200 - 200 + 0).
     Pixel 2 1 is RGB 195, 195, 195
          Replace original R 195 with replacement R 205 (200 - 195 + 200).
          Replace original G 195 with replacement G 5 (200 - 195 + 0).
          Replace original B 195 with replacement B 5 (200 - 195 + 0).
     Pixel 3 1 is RGB 189, 195, 195
          Replacement does not occur because the diff of origin R and target R is > fuzz 10

If I am accurate, than consider this change double checked!


TeamCity pull requests :: netty [Build 496](https://garage.netty.io/teamcity/viewLog.html?buildId=2754&buildTypeId=pulls_netty&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:50


Sorry, didn't see you opened this pull request. I'll close mine :)


PS: c'est plus simple de faire les remarques directement sur le pull request plutôt que sur un commit (quand tu vas dans l'onglet "Files changed"): comme ça tu vois tous les changements (plutôt qu'un seul commit), et si je corrige ça efface le commentaire du pull request.


For now in Blocks we have two places, in Fuel there is one. I will do the same refactoring for Blocks as I did for Fuel in https://github.com/mila-udem/fuel/pull/254 just as soon as we are done with all this release hassle. The reason I decided to do it after release is that we have to get rid of namespace packages to implement the same trick as I used in Fuel. Even though I got Bart's okay for renaming `blocks.extras` into `blocks_extras`, I think it is important to have a working release with namespace packages first.


je te laisserai l'enlever si tu juges inutile... puisque je ne connais pas trop ce que tu as fait, je préfère laisser comme c'était.


Tous les noms de champs sont automatiquement traduisibles, il n'est pas nécessaire de les mettre dans la fonction de traduction.


Tak jak zawsze jest mowa - dla takich stringów używamy ``'str'`` a nie ``"str"``


@drod4 DWMR (done with my review). This is good. Press ahead!


改完一整個升級了!!!
感謝~~


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


Valid point. 100+ sounds like what I wanted. But how about warning_value + 100 and warning_value * 10

The idea is not to test a insane value like 10000 when there is a warning value which is much smaller.


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


Wow, nice. Didn’t know that they had introduced this helpful feature. Thanks.

(Can we delete these comments because it’s off-topic for the commit?)


@tobibeer
IMO it may be a new issue, since my "make it translatable" ticket and the PR are merged and closed already.

I think your concerns are valid. +1 for renaming "Toolbars" tab to "Controls" and creating a new tab with "Global Settings" or "Tiddler Controls" ...


93653546-FuelGenShowingInABUPSwhenPV (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1424 of 1424 tests passed)

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


Yes, this is a debug bus and its removal is not harmful, code still compiles correctly and kernel works.


We typically put `@extends` at the top of the property list. Would you mind moving this to the top?


Refs #13


```
DEBUG: Better Fig. PATH: /home/xenith/git/opsech.io/content
DEBUG: Better Fig. img.src: {filename}/images/dnf_changelog.png
DEBUG: Better Fig. img_path: {filename}/images
DEBUG: Better Fig. img_fname: dnf_changelog.png
ERROR: Better Fig. Error: image not found: /images/dnf_changelog.png
DEBUG: Better Fig. Skip src: /images/dnf_changelog.png
```

Getting this error following your instructions on duncanlock.net, the path of the article is

`content/articles/2015/dnf_changelog.md`

and the path of the image is:

`content/images/dnf_changelog.png`

the image is sourced via markdown in the above-mentioned article as such:

`![dnf_changelog.sh]({filename}/images/dnf_changelog.png)`

Edit: The image is however present in the output and visible on the page itself (pre-publish and post-publish), It's just not being processed by the plugin for some reason. Help?


Yes, of course.


Ээээ. Использовать булеву переменную в if-e путём прямого сравнения со значением true/false?
![не надо так](http://images.vfl.ru/ii/1402882405/b473b96a/5438988_m.png)

(И, кстати, мелочь, но — правильное название для переменной-опции не должно бы быть глаголом; кому-то же потом читать этот код! `recommend(watch = true)` — читается как «порекомендуй фильмы! ну и посмотри их заодно уж»)


Sure!


Damn, ok, still working on it...


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


O que o Template faz é basicamente gerenciar o fluxo de exibição dos objetos na tela. Então pense no template como um desenhador.
Você poderia criar uma interface para isso, ficaria algo assim:

```java
interface IDrawer {
   void setName(string name);
   void draw(int quantity);
}
```

Basicamente o que qualquer classe que implementar essa vai fazer, é desenhar na tela (se vai fazer efeitos de fade_in, fade_out, etc, ai fica com cada classe que implementar.


Why do you call this "patch ..."? Just write something like "refbox: don't link against mongodb". In the commit body you can mention the shared object (other distributions) vs. static library (Ubuntu) issue which we identified as the source of the problem.


Because of the GDAL trampoline stuff, OCTTransform or any other GDAL function will throw an error if GDAL deems it an error. GDAL's debugging mechanism works the same way, but in that case, there is simply output to `log()` instead.


If a user has a classmap definition for a `vendor/$vendor/$package` then this will result in a runtime exception as it might not be installed yet at this point. Either we should try/catch those and output them to the console (but still proceed) or otherwise consider reverting this change.


Please avoid using this syntax. Use `map { case (name, index) => index }` instead.


See below.


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


aha ... i see now. there is GUI extra in [setup.py](https://github.com/neovim/python-client/blob/master/setup.py#L32) only working with python 2 and requires ``click`` and ``pygobject``.

let me finish work today and i'll package the GUI part.


RadianceMeasureMessaging (rpg777) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


remove kebab


isso tá buildando?


Also prevents from multiple notifications appearing for the same error.


one should probably increase version here too


n'y aurait-il pas le suffix ezproxy en trop à cet endroit ?
.faraway.u-paris10.fr


deve ser feito apenas um único linq/lambda para resolver o exercício.


suggest to insert:
else
  compression_type.clear();


Potentially give committee members a veto on sections of the minutes at discretion of president?


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


This can be written a bit more nicely with `using flixel.util.FlxArrayUtil` and [`last()`](https://github.com/HaxeFlixel/flixel/blob/dev/flixel/util/FlxArrayUtil.hx#L159).


John Winters: ·         Clause 35 is too long and has two clauses in it.

·         The changes are misleading, unhelpful and adds no value.

·         The “exceptions made below” allow any member to observe a committee meeting, but this point implies that is not the case and that the default is they are barred.

·         It is also now not clear that invited guests cannot vote. “Only voting officers of the Committee may vote and attend… exceptions... The Committee may invite other Members… as Guests of the Committee” Could be interpreted that guests could vote. This should be very clear that they cannot.


I don't think it is necessary to mention transform id 73 explicitly. Since you mention the terminating zero byte, I think it would be a little better to include that in the maximum buffer size (one byte more or less does not matter much and it can lead to less surprises in implementations).

So all in all, it could read:

"The maximum number of additional bytes that a transform may add to a base word
is 13. Since the largest base word is 24 bytes long, a buffer of 38 bytes is sufficient
to store any transformed words (counting a terminating zero byte)."

Also, this would be more useful as the last paragraph of section 8, not hidden at the very end in the appendix. The appendix is supposed to contain only the raw data + checksum.


Switching from PlayerViewOperationMode.Presentation to a different view mode does not recover the visibility correcty, for example the centerplayhead will remain visible if you switch from Presentation to any other value.
With 4 view modes it makes it a bit more dificult to configure with simple switches,  a different approach is to use per-element visibility configuration. For example, intead of using a switch/case and setting ShowControls = bool you can do:
controlsbox.Visible = value != PlayerViewOperationMode.Presentation;
ratescale.Visible = value != PlayerViewOperationMode.Presentation;


I am pretty sure that you cannot create a `std::vector<QOpenGLVertexArrayObject>`, because `QOpenGLVertexArrayObject` is not copiable. But I do not understand why a vector of pointers cannot be used!


Thank you soooo much for the updates.


K I'll +1 on gerrit


Hey @rvansa, I could give you my specific use case, but this is really related to how the `groups` parameter for a stage is handled. If my benchmark includes a `service-start` stage with a single group, then I expect the `expect-num-slaves` property to be set equal to the size of the specified group. If the `service-start` stage specifies multiple groups, then I expect the `expect-num-slaves` property to be set equal to the sum of the sizes of all of the specified groups. Your change will not achieve that, and the developer of the stage should not have to do any extra work to support this. There should be an easy way to accomplish this, or the ability to specify multiple groups on a stage should be removed.


No need to put a -j# on repo sync


Fixes #821.


yes i added the commits to build repo to make dirty when we started


5255-EMS-dual-Temp-Node-Setpoints (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.726](http://teamcity.monogame.net/viewLog.html?buildId=11001&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 551, ignored: 6 Build time: 00:18:56


let's move compression type to the end of the list...


I think it's better we don't copy textures from other texture packs.

![](http://i.imgur.com/bZYPnvN.png)
And I don't think that this texture is so much better.


 #[zstack Test Bot Report] P A S S
 Integration Test Result:
Test Summary:

 TestSuite|TestCase | Pass | Fail | Timeout | Skip
 ---------|---------| ---- | ---- | ------- | ----
 basic_test|__suite_setup__|0|1|0|0
basic_test|_basic/test_create_vm_|0|0|0|1
basic_test|_basic/test_stop_vm_|0|0|0|1
basic_test|_basic/test_start_vm_|0|0|0|1
basic_test|_basic/test_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_volume_|0|0|0|1
basic_test|_basic/test_add_vol_to_stopvm_|0|0|0|1
basic_test|_basic/test_add_volume_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_multi_volumes_|0|0|0|1
basic_test|_basic/test_add_volume_negative_|0|0|0|1
basic_test|_basic/test_crt_temp_from_volume_|0|0|0|1
basic_test|_basic/test_crt_vm_with_volume_|0|0|0|1
basic_test|_basic/test_vm_securitygroup_|0|0|0|1
basic_test|_basic/test_create_iso_vm_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account2_|0|0|0|1
basic_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
basic_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
basic_test|_suite_teardown_|0|0|0|1
virtual_router_test|__suite_setup__|0|1|0|0
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
virtual_router_test|_novlan/test_create_vm_|0|0|0|1
virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_vlan/test_create_vm_|0|0|0|1
virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_snat_create_|0|0|0|1
virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
virtual_router_test|_vlan/test_start_vm_|0|0|0|1
virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
virtual_router_test|_volume/test_add_volume_|0|0|0|1
virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
virtual_router_test|_sg/test_ingress_|0|0|0|1
virtual_router_test|_sg/test_egress_|0|0|0|1
virtual_router_test|_sg/test_icmp_|0|0|0|1
virtual_router_test|_sg/test_udp_|0|0|0|1
virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
virtual_router_test|_sg/test_vm_ops_|0|0|0|1
virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
virtual_router_test|_sg/test_detach_l3_|0|0|0|1
virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
virtual_router_test|_pf/test_attach_pf_|0|0|0|1
virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_multi_rules_|0|0|0|1
virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
virtual_router_test|_pf/test_tcp_|0|0|0|1
virtual_router_test|_pf/test_udp_|0|0|0|1
virtual_router_test|_pf/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_2_eips_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
virtual_router_test|_eip/test_attach_eip_|0|0|0|1
virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
virtual_router_test|_eip/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
virtual_router_test|_lb/test_create_lb_|0|0|0|1
virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_suite_teardown_|0|0|0|1
local_ps_virtual_router_test|__suite_setup__|0|1|0|0
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_ps_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_ps_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_udp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_ps_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_ps_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_ps_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_ps_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_ps_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_udp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_ps_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_ps_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_ps_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_ps_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_ps_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_suite_teardown_|0|0|0|1
local_nfs_virtual_router_test|__suite_setup__|0|1|0|0
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_nfs_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_nfs_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_nfs_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_nfs_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_suite_teardown_|0|0|0|1
Total|304|0|4|0|300


merci pour l'oeil de lynx. c'est corrigé.


In questo progetto si eseguono sperimentazioni!


First I used ```pwd -P``` here. Later I decided not to resolve symlinks, so I removed the -P and added this comment for the case that I or someone else wants to change this behavior. I felt this info seems to be worth saving. ;-)


Did not think about it when i was writing it but yeah good point! Thanks :)


good!


@briancantrell I've added `Activities#get_activities`, which loops through the pages correctly! And by _correctly_ I mean of course that the spec works. We've got to try it out and see if it works


Authority is delegated to the PM by the committee, but they're not necessarily selected by the committee - don't know if it's worth clarifying.


你现在写的，我都有点看不懂了~~~~~~~


Nice, next commit will be with `FlxArrayUtil.last(_recentPositions)`.


93653546-FuelGenShowingInABUPSwhenPV (mjwitte) - i386-Windows-7-VisualStudio-12: OK (1953 of 1960 tests passed)

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


When I tried this code it gave me the error, but it still put the item in the pot and worked fine, I'm gonna test it more but it might work even when it gives the error, we'll see


good project, learning


Can you then rephrase the comment, to not be confusing? :-)


These are used in production, so they're deps rather than devDeps. main-bower-files would need an [extra includeDev option](https://github.com/ck86/main-bower-files#includedev) provided otherwise


In our error handler do we need to throw?  Can we just eat the error
(perhaps logging) and let the return code (false) bubble up?

On Thu, Oct 29, 2015 at 8:23 AM, Howard Butler <notifications@github.com>
wrote:

> Because of the GDAL trampoline stuff, OCTTransform or any other GDAL
> function will throw an error if GDAL deems it an error. GDAL's debugging
> mechanism works the same way, but in that case, there is simply output to
> log() instead.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/PDAL/PDAL/commit/c4898cab0df4dadd643081cd5052fbba41251cf2#commitcomment-14066765>
> .
>

--
Andrew Bell
andrew.bell.ia@gmail.com


Branch alias was changed but I don't see a 0.7 tag, should it exist?


“更多信息 (MORE INFO) ” 与  “无论如何都运行 (RUN ANYWAY)  ” 保留原文即可，因为这个是软件的实际提示英文，描述时保留英文为宜。

与先前所校正的不同，那些诸如 “Menu” 等，实际在软件上是只有图标，无英文，因此描述是以中文为主。

此二处有劳再次修订。


Fixed, thanks


Part of https://github.com/mattbk/changeblindnesstest/issues/2.


I were backporting tab fix to v0.12 and find there a problem.
This extra condition saves some computations on repeated tab strokes but will break tabbing in cases when first/last element is disabled during first tab stroke.


small_func with generators only :rocket:
- [ ] @BardyshBorys


I'm pretty sure that the markdown files aren't templated, so you need to change this to `/developers/docs/code/libraries/`.


Just to avoid too much code repetition in JS streams


thx!


This sentence feels a bit weird in a sense that it starts with some detail, i.e. from where do we count the bits.

If your goal is to use the same notation, it could be:

"The copy length code within its range is determined by bits 0-2, and the insert length code within its range is determined by bits 3-5 of the insert-and-copy length code (counted from the LSB)."

Or, if we don't mind some repetition:

"The copy length code within its range is determined by bits 0-2 (counted from the LSB) of the insert-and-copy length code, and the insert length code within its range is determined by bits 3-5 (counted from the LSB) of the insert-and-copy length code."


OK


I had it throw for convenience so I wouldn't have to put the C-style call/check/printerr dance around/near every GDAL and OGR call. If GDAL is returning an error, it isn't going to be recoverable most times. In this particular case, where the point doesn't project correctly, it is recoverable.


We can also override the files that MBF grabs for for specific packages, or when they haven't specified a 'main' property in their bower.json. Letting it grab the defaults for now.

e.g.

```
$.mainBowerFiles({
    'overrides': {
        'html5shiv': {
            'main': [
            'dist/html5shiv.min.js',
            'dist/html5shiv-printshiv.min.js'
            ]
        },
        'jquery': {
            'main': 'dist/jquery.min.js'
        }
    },
});
```

This can also be done within the project's bower.json itself, but personally I prefer to do it in the Gulpfile along with all the other project-specific config.


this fixes as bug where if you do the OF path wrong, the addons array = null, so we can't really call filter on it.
now, we check if it's null, then check if it has length, then filter....


Just for quick future use


hjjk


@un1versal please look into your database, and tell  look how the values totalCount and watchedCount are set.


ij


@christianstahl,
this commit breaks compilation:
![bug1](https://cloud.githubusercontent.com/assets/10432699/10820066/c041d3ce-7e4b-11e5-938b-7b4321d0654c.PNG)


I would say the overhead of calling a function is negligible. The rest of the inner loop of an alignment should dominate the runtime. Yes, the char should be u8.


![screen shot 2015-10-29 at 12 04 25 pm](https://cloud.githubusercontent.com/assets/15378190/10820077/8992731c-7e71-11e5-89be-deb1ef0aeb1b.png)


sp


year 2, semester 1


But that means you won't update any of the boot.blk disk parameters and so the boot.blk geometry will have to match exactly the fatfs generated geometry. This seems a little limiting, don't you think?


kk


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1029.542e86bedf9b0bbc3dcbc34f09f7c63c8adb840f](http://build.palaso.org/viewLog.html?buildId=65089&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 703, ignored: 6 Build time: 00:10:16


Nope I just do a 1.0 release if all milestone issues are resolved


Why do I see is this?

    /**
     * Returns product option
     *
     * @return \Magento\Catalog\Api\Data\ProductOptionInterface|null
     */
    public function getProductOption();


5255-EMS-dual-Temp-Node-Setpoints (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1960 of 1960 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)


Wow. I can even use ewa_lanczossharp with this, while it was giving me around 0.5 fps before.

Amazing, huge thanks for developing mpv!


Not sure about mounting without the nosuid flag?  Is this happening because there is an image mounted without this flag?

```
+        while not Mount._is_device_active(os.path.join("/dev/mapper", name)):
+            sleep(.5)
```
If you are going to do this, you should have some kind of counter where it breaks out after 10 seconds or something with a failure.


Just the readme.


fdgdgd


elif [ "$role" == "CP1" ] ...

So, if this function is called with two params,  **CP1 t1**, for example, will it work?
It seems to me that we will enter here, as role is $1, which is CP1, and then we will use ${CP1_DB_NAME}, ignoring the second parameter **t1** ...    I might be wrong


unused


Thanks!


TL;DR: Faltou fechar o `</div>` do `.comments`.

Cara, acho que está errado isso aqui. Você abriu na linha 34 o div `.comments` que vai agrupar dois comentários, que serão os divs `.comment`. Logo, antes desse `<h2>3D Renders</h2>` tem que fechar o `</div>` do `.comments`, certo?


Fixed in next commit.

https://github.com/minetro/ntdb/commit/0b21a4bbed6f7c55004439ed26bbd4987d48f4ae


SwitchPage should be private and CurrentPage's setter public (calling SwitchPage internally) to mimic the GtkNoteBook API.

You should use the SwitchPage event instead of ChangeCurrentPage.  change-current-page is an Action signal see https://developer.gnome.org/gtk2/stable/GtkNotebook.html#GtkNotebook-change-current-page and https://developer.gnome.org/gobject/unstable/gobject-Signals.html#G-SIGNAL-ACTION:CAPS
"They can also be thought of as object methods which can be called generically by third-party code."


TODO


When I write VFS plugins I usually almost start writting a close method after open, because that seems a more natural pattern then storing a back reference for the handle destructor if I need to do a resource cleanup in the file system. So yes, I would prefer handing an allocator to the file system, and using a guard for closing the handle in the same way that it is done for the file_system.


só uma observação, você poderia criar listas inline:

```
listaDeJogos = new List<Jogo>
{
  jogo
};
```


Eu não gosto e nem é recomendado, usar nomes para estrutura como `right-side` ou `left-side`... E se você quiser mudar essas colunas de lado, colocando `float: right` no div que está na esquerda (`left-side`)? Aí ele vai ficar na direita, mas vai ter **left** no nome... :-)


What effect does adding a "Noncommercia"l license have on the book being sold with funds (I presume) going to the Pharo Association?


Eu faria com lista... mas parágrafo não está errado.


@arr2036 btw, it's related with F5/LTM?


Also, in case of naming the event differently, it's better using PageSwitchedEvent than SwithPageEvent which is imperative and can be considered as an action to perform instead of an event that has ocurred


This was actually intentional, it's an MMO joke :stuck_out_tongue: .


Yeah it sticks the service name at the end of the packet, after the RADIUS data


I also have the feeling these functions could be MUCH simpler. Something like:

    function dbInit()
    {
        role=$(roleTranslate $1) # roleTranslate translates CB to ftest, CP1 to ftest_cp1 etc
        tenant=$2            # perhaps a test with $# before

        db=$host:$port/$role$tenant

        echo 'db.dropDatabase()' | mongo $db --quiet
    }

roleTranslate would be used in dbDrop as well (and perhaps more places)


Because it was a patch previously available and referenced by the FAQ


also changed 'short' field to 'description' to match data team datapackages


@gaganawhad @joeosburn can you explain this more? What do you mean by "works better"? What do you mean by "not secure"?


`<br>` isn't a valid child in `<dl>`. We could use pure CSS, though:

```css
.tribe-help-plugin-info dt {
    clear: both;
    display: inline;
    font-weight: bold;
}

.tribe-help-plugin-info dd {
    display: inline;
    -webkit-margin-start: 0;
    -moz-margin-start: 0;
    margin-start: 0;
}

.tribe-help-plugin-info dd:after {
    content: '';
    display: block;
}
```


Para que la Galería no tenga comportamientos erráticos las imagenes deben estar optimizadas en el tamaño del div contenedor.


added the correct extension dir name


@cioan  I *think* the right thing to do here would be to move the allergies stuff below out of this controller and into the currentAllergies directive (which I think is currently unused, and is in allergies.js).  Then the current Allergies directive template would be changed from allergiesList to reviewAllergies (and allergiesList could be removed, I believe). A new gsp page would need to be created to include the currentAllergies directive.


a duplicação de `DateTime.Now` pode ser problemática. Ex:

**Entre o momento** da primeira vez que é chamado e a segunda pode trocar o ano, e aí afetaria a query.

Sugestão: quando for repetir `DateTime.Now`, guardar em uma variável antes. Ex:

```
var agora = DateTime.Now;
var query = from func in Funcionarios
  where agora.Year - func.DataNascimento.Year <= idade - 5 &&
  agora.Year - func.DataNascimento.Year >= idade + 5
  select func;
```


Other than broadcasting updates of Master to backup/slave controllers, I still think we should keep a local log on trace tree in the hard-drive of Master controller. In addition, should we keep the uncompressed trace tree as local log/broadcast to slave controller, or we use compressed trace tree to save communication and I/O overhead?


this causes issues


@johanneskoester alright, sir


This may cause problems during delivery of packets? e.g: Be the reason of delay during answer?

```
Wed Oct 28 19:58:22 2015 : ERROR: (13245) ERROR: Failing proxied request for user "14:1a:a3:2c:c1:28", due to lack of any response from home server 10.1.1.10 port 1812
```


:+1: Great arguments.


Methods should be internal static after the changes in master


No, it's only in packet captures


Какая от них польза?


Hi @venturia, why if you consider the vector empty, you still want to add a pixeldet or a stripdet? (last else of this line)


Scripts task now only works on the app's ``main.js``, as we now no longer need to concatenate it with jQuery, etc.


oh! phew! :+1:


Awesome!

Thanks :)


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


Hay @macumber, this is working, on 64bit Windows as well. Could we maybe review this crap this morning? In addition to a lot of messaging cleanup, the Radiance measure now renders simple views of all your daylighting control points, and glare sensors:

<img width="1512" alt="screen shot 2015-10-29 at 7 47 58 am" src="https://cloud.githubusercontent.com/assets/3161332/10820267/ef7ff7cc-7e11-11e5-9c21-92fcc8f874bf.png">

![space_1 cvf](https://cloud.githubusercontent.com/assets/3161332/10820405/afac4794-7e12-11e5-9e58-0a35b67c5da8.png)

![space_1_glare_sensor_1 pvf](https://cloud.githubusercontent.com/assets/3161332/10820416/b979341c-7e12-11e5-8c1c-dae19177cb5f.png)

...would be great to pick all these up and place them in a simple report along with the daylight metrics!


public class HomeWork1 {

	 public static void main(String[] args) {
	        // ошибка: Pet zorka = new Pet();
	        Drink cola = new Drink();
	        Snack mars = new Snack();

	         cola.addItem();
	         mars.addItem();
	    }

}


@arturoc @thomasgeissl  does this look right?


abstract class Item {
	int product;

	public void addItem() {
		product +=1;

		System.out.println("One item added");

	}
    public void sellItem() {
    	product -=1;
    	System.out.println("One item sold");

    }
    public void getItemsCount() {
    	System.out.println("Items left - "+ product);

    }
    public void loadItems(int x){
    	if (x < 0)
        {
            System.out.println("not able to load"+ x + "items");
        } else if (x==1)
        {
            addItem();
        } else {
        	product = x;
        	System.out.println(x + "items added");
        }
    }

}


Not sure about placing these imports
here   vs.   at the file beginning

Comments are welcome :-)


Extra line breaks in all methods


**README: Nitpick**

Markdown syntax should be used properly. For multiline code style, put the `pip install -r requirements.txt` on a new line. The 3 back ticks at the end should also be on a new line of its own.


5255-EMS-dual-Temp-Node-Setpoints (EnergyArchmage) - i386-Windows-7-VisualStudio-12: OK (1960 of 1960 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)


Methods, even "getter" methods, should have verb names.  You don't need to be super-creative about this `GetSpaceAt(int position)` is fine and while I respect that this gets blurred by c#'s "property" construct (which we name with nouns) the addition of an argument changes this somewhat.

Alternatively, nisce the Board's primary responsibility seems to be to index spaces, you could implement IDictionary<int, IBoardSpace> and do your "getting" via that convention.


True. Intended to be a quick fix.


主要是 images 这个 npm 包里面的 windows 64 的二进制包不对，重新编译了一次。


**Code Quality: Nitpick**

Don't leave commented out code within your file. It makes your program less easy to read. Ensure to clean up after you always.


gcm_sender_id was purged.


Setting a line-height of `1.9em` would make for some ugly blocks of text:

![screen shot 2015-10-29 at 10 04 16 am](https://cloud.githubusercontent.com/assets/430385/10820600/70df7cf4-7e24-11e5-99b2-628cf378666b.png)


**Code Quality: Nitpick**

It might have been better if you named this class `Room` since it represents a general room object.


@ankurankan I had thought about that too.
Since, the ``events`` are [sets](https://github.com/pgmpy/pgmpy/blob/dev/pgmpy/independencies/Independencies.py#L177-L179), I think the equality will hold independent of the order of input.
I had read about this [here](http://stackoverflow.com/a/15181907/4927751), and thought it would be good to use the ``__str__`` to compare the objects.
But if you think this is not the most optimum solution then I can try to improve upon it.


I suggest you just call this "Var", because that is what it is.


added comments to override base on header/query parameter


Mixed up some refactoring on the FakeForm test fixture with this commit, I'll need to be more careful in the future.


Mais faux..: https://github.com/patacrep/patacrep/commit/e91a52604c7344c25c120546f988981dff034f9f


Yikes!  This class/interface is becoming a feature magnet.  I think you've got two or three other classes hiding in here.


Wait for my next push, I have this fixed :)


5255-EMS-dual-Temp-Node-Setpoints (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (886 of 886 tests passed)

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


The crash on Windows 7 was caused by the fact that engine_pkcs11.dll compiled by mingw used another memory allocator (from msvcrt.dll) than libcurl.dll with statically linked openssl (from MSVCR100.DLL or MSVCR110.DLL). On Windows XP these heap implementations were compatible.
http://blogs.msdn.com/b/oldnewthing/archive/2006/09/15/755966.aspx

Confirmed above theory using pkcs11 card communicating with protected server.
OpenSSL (compiled with mingw/gcc) and libcurl.dll v.7.45.0 (compiled with VS2012) dynamically linked with it do not crash on Windows 7 when deallocating private key allocated by engine_pkcs11.dll (compiled with mingw/gcc).

@badger Please remove this patch from the git. It causes memory leak in the engine_pkcs11.dll.
To correctly deallocate keys allocated by the engine_pkcs11.dll using different heap implementation you may need private key deallocating callback to the engine module from the OpenSSL.
Only developers of OpenSSL (and engine_pkcs11) can do that.


**Code Quality: Nitpick**

It's very good that you're using the `is_` format for your boolean methods. However, naming your method `is_available` for a method that tells you whether a room is filled or not might not be very intuitive. It might be better if this method was named something like `is_filled` or `is_occupied`. Makes more contextual sense.


No problem, I was just doing the code review portion, and it was something I noticed. :)


ah, you're right.


How about replace AsyncTask by Rx?


Minor typo, I guess you meant "on the coverage **or** feature collection


Set `target="_blank"` on the redcloth url so it opens in a new tab.  I'll merge after.


**Code Quality: Nitpick**

`Spaces` might not be an ideal name for this class. Use something else, maybe `Building` or `Amity`.


Yes. I know, they look weird. NuGet handles them specially. They aren't well documented, but there's a little more info at https://github.com/aspnet/Home/issues/744#issuecomment-123411563


Yes, you are right, thanks.
Is it better now?


This "player loses" logic is getting duplicated a lot.  Maybe you can fold it into the debiting logic?


How does that happen. If we are trying to remove an active device, something is wrong? Atleast we need to document those conditions well.


I forget how much :dollar: you start Monopoly with but I'm sure it's not $400


**Code Quality: Nitpick**

Use meaningful variable names. `livings` does not make grammatical sense and although the program works, let's always try to make our program reasonably readable. Use `living_spaces` or something similar to depict this.


Thorsten you were too fast. Integration was not yet finished. Is now done

> On 29.10.2015, at 14:46, Thorsten Schulz <notifications@github.com> wrote:
>
> @christianstahl,
> this commit breaks compilation:
>
>
> —
> Reply to this email directly or view it on GitHub.
>


Nope, it shouldn't be there!


You can definitely use str to compare but in that case also you will have
to come up with a way to sort the values.
On Oct 29, 2015 7:34 PM, "Kshitij Saraogi" <notifications@github.com> wrote:

> @ankurankan <https://github.com/ankurankan> I had thought about that too.
> Since, the events are sets
> <https://github.com/pgmpy/pgmpy/blob/dev/pgmpy/independencies/Independencies.py#L177-L179>,
> I think the equality will hold independent of the order of input.
> I had read about this here <http://stackoverflow.com/a/15181907/4927751>,
> and thought it would be good to use the __str__ to compare the objects.
> But if you think this is not the most optimum solution then I can try to
> improve upon it.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kshitij10496/pgmpy/commit/2466142cff7328c18779419460a6a4b9fd3f3524#commitcomment-14067765>
> .
>


Huh?


I will check that and the comments you made on the code. I’ll find you during lab and we can go over it. Interestingly, I started with the isNaN command but Sam switched it to NaN. Not sure why exactly. Thanks for all the help! See you soon.

> On Oct 28, 2015, at 22:41, Jonathan Stallings <notifications@github.com> wrote:
>
> What happens if the user passes an empty string to the prompt (by just pressing enter)? What is value of years after parseInt, and how does that affect the control flow in your following while loop?
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/jaredscarr/guessing-game/commit/13d1c983151807a02a8560ed70a52f9e576a472c#commitcomment-14058462>.
>


We don't seem to be waiting in docker after device activation. So I am curious when do you see this. If device activation command returned success, then device should be active and we should not have to wait.


Build Failure fix


I choose $400 because when only playing 20 rounds it was a reasonable number to have a player lose.  If I had the "correct" $1500, after 20 rounds it was uncommon for a player to lose already.


The commit message doesn't say `why` it must be triggered with a change of the `company_id`.

Besides that, it's correct :).


You did something wrong then. You have to be at a clean repo


I can work on a better name, but a property group is one where it shares the same colors.  A group would be all the oranges, or the green properties.


Typo: `Plaiy` should be `Plait` /cc @adambullmer


:+1: These fixups are fine with me, the throw was more to make sure I noticed any leaks, but thats not appropriate for staging and master.


This should not have been set, and is the reason why the RHEL6 build is failing.


@rahulait Thanks for pointing out, this check actually should be disable. It was used to tested the if clients can ping ip of server. But we found it doesn't make sense, since if the ip is not available, the result will not be acknowledged. I will remove this. By the way, only the checks regarding with openstack are with controller, however openstack are not fully functional now, so I disabled them already.


**Code Quality: Nitpick**

Leave a space between these two parameters. See [PEP-8 Standard](https://www.python.org/dev/peps/pep-0008/#pet-peeves).


This is great. thanks.


Unused import.


ouch, right, I approved it after the rename branch. And my tests passed because I have the old path downloaded. Thanks for catching this.


It will be better "Node.js® è un runtime JavaScript "


Hey @LookLittleJohn, I just found out about TylerWebDev. It's great that you folks are getting so much traction and energy, and nurturing the community!

I am a little confused by the reference to Hack Tyler's "gray area" ethics. Can you unpack that? I don't recall there being an ethically-relevant component to any of Hack Tyler's projects or meetups. We were just nerds who liked to hang out and occasionally build stuff together. Also happy to clarify any history, though as the Hack Tyler founder, @onyxfish is the canonical resource.

Cheers!


**Code Quality: Nitpick**

Use context-specific naming for variables used within a loop. Each object that you're iterating through represents a line and hence should be named as such. i.e
```python
for line in file_contents
    # do something
```


Segnala un problema di Node.js


Minute Incontri TSC Node.js


The waypoints for Twilight Lord Everun's third path are still missing.


wie stellt sich eine invertierte toolbar dar?


Are you planning on upstreaming this? I'd rather not have to use custom uploaders when my distribution ships the sunxi-tools.


why not make this case insensitive ? (because symfony2 use `{@inheritDoc}`


Right. Well, testing both +100 and *10 sounds good to me.


I went through the Chanllenge exercises once more @ScottDalessandro


Did you do some local testing to get an impression?


hi shantur may ı ask is this method working good? because you are hacking (for example libcamera) libs to load this lib instead of libbinder but i think it can cause various crashes because ı mean you are providing ONLY pmem instructions in this libold.so (and some others such as vectorimpl) but your libcamera.so may need to call other instructions from libbinder.so as well (because you can look libbinder makefile https://github.com/CyanogenMod/android_frameworks_native/blob/cm-13.0/libs/binder/Android.mk ) there are much more includes in libbinder... ım just curious....
thanx & regards


`history_file.readlines()` seems to be malloc much memory and inefficient if the history command file is huge, But it should be okay because the log files has size limit or rows limit.


Direzione (or just leave it untraduced as governace)


Leave it as "knowledge"


Direzione tecnica


Marchio registrato


@h4 калории считают :) Лучше спроси у @lautsevich


Ок. Там более полезные PR от меня есть ;)


Hab die Version aktualisiert.
Breaking Changes betreffen uns nicht. :+1:


xform .. ich muss dort auslesen welche klassen vorhanden sind und diese entsprechend abfragen..


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


Can't this be inside the `inputWrapper`? A label is part of the input, right?


> wie stellt sich eine invertierte toolbar dar?

nur andere Farben also andere Look

vergleiche
http://getbootstrap.com/components/#navbar-default
http://getbootstrap.com/components/#navbar-inverted


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


Great change! Keep up the good work!!


hüstel … yform meint er ;)


@santimarrone Paloma no vuela :cry: jajaj. Dale, de todas maneras hacelo tranqui igual, la idea de como `orquestre` el test era para que podemos apretar el boton eliminar en `TestMain.java` y listo jaja :grin:
Despues voy a hacer un metodo `manejarCollection` o algo parecido que administre la paloma, ladrillos etc, pero eso no te afecta en nada, hace lo que tenias pensado en paloma, si necesito modificar algo va a ser muy especifico asique no te hagas drama. :+1:


what's the reason for moving the '-x's from inside the scripts to outside?


Couldn't you do something like `check_func_headers "windows.h Security.h" InitializeSecurityContext -DSECURIT
Y_WIN32 -lSecur32` here?


@Kimmax Cloned your repro and working from your console frontend not sure whats going on there are no packages on my side can i upgrade or reinstall them?


"and" is a good indication that you're testing two or more things.  These are integration tests (which is fine, but that's what they are) but they're fast ones; you could probably set this up so that you have distinct tests determining if the property changes hands and if the balance decreases.

Check out the `Returns` (`Return`?  I may have the name wrong) property on the `TestCase` object; it lets the test return a value and checks for equality.  It's not useful 100% of the time but if you use it where you can it'll get you into a good habit of having each test assess one and only one thing.


`tail -f ` may be is the easiest way to implement the feature, but not pythonic.


@darrell-rg sorry I didn't respond about this earlier, it's being addressed properly now in #1360


Yes, it seems to be working for me. I think because libold loads libbinder libgui so libcamera can access these methods. Check http://review.cyanogenmod.org/#/c/114345/ or search libdmitry


Actually the correct notation would be ``{@inheritDoc}``, according to phpdoc http://www.phpdoc.org/docs/latest/guides/inheritance.html

But I get your point. Would you be so kind and open a pull request?


DRY applies to tests too.  You shouldn't be afraid to have short tests with well-named private functions that do a lot of the work.  This is doubly true for set-up work in integration tests as we're looking at high-level function of the system.


You'd need to call `tls_close` here to free what `ff_tls_open_underlying` allocated.


ok i'll do it


@bencoman Hmm I think this is an error on my part -- I copied the wrong license link. It should be [Creative Commons Attribution-ShareAlike](http://creativecommons.org/licenses/by-sa/3.0/), without the Non-Commercial. I'll fix.


nit: space


See https://github.com/c2corg/v6_api/issues/54#issuecomment-152197280


You're not really testing "landing" here as such -- your player's movement isn't triggering the buy/don't buy decision.  Consider broadening your integration test to include a mocked dice roll and letting the `PurchaseCurrentSpace` function fire of its own accord.


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


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


the simple definition of @sstucki is an _over-approximation_, and this is good enough for effect safety, since it at least excludes all "capability producing" types, even though it excludes some more which would safe to include, like `E -> E`. later, we can work on refining the criteria for `caprod` to be a better over-approximation. as you pointed out, we probably cannot do better than an over-approximation (b/c of Curry-Howard), but an under-approximation is not effect safe.

this is why i suggest starting with sandro's def.


Another indication that your tests may be doing too much is the presence of more than one `Assert`.  In this case you could check to see that rent is being charged in one test and that it's being credited to the owner in another.


Why did you use this foreign lanuage?


nit: brace placement


Itsent ruby foreign too?


I love the "User Story" descriptions in the tests.  They really help make sense of what you're testing.


Checking every 100 ms seems excessive


This fix was already done in newer version https://github.com/phpmd/phpmd/commit/9271fc6153db0a3e67ce57f706a1e2bcc2828b7c#diff-6ac2ca51ccf7d60ae29873447c6b87bcL123


To close the bugzilla ticket you should use `fix Issue 14327`, then it will also show up in the changelog.


Huge props for this! :+1:


You could stick the RRs in a list and reference them by index; that would let you DRY up your RR Rent tests into a series of test cases rather than having to have a full-fledged test for each one.


No spaces after commas (here, and on line 295). Please fix. :)


nit: space


You can easily make a cookie-fallback of there is no localstorage. See https://gist.github.com/Fluidbyte/4718380


Two things:
1. The images should be uniformly named, e.g. `button_play` and `button_pause`.
2. The pause image is not transparent (yet).


Agreed, but there is no way around without any more elements, Inline elements doesn't allow me to do Padding or Margin.


extra line


damn, this should have not be committed here

sorry


This generally is kinda risky when it leaves c->enc_buf_size set to a nonzero value while c->enc_buf is NULL, but here you check c->enc_buf == NULL first and override the size in those cases, so I think it's ok.


With this version, or the old one?


bad indent (extra space before """)


This test is fragile.  You supply Boardwalk's rent in your factory but you're testing against it here.  Try to link these values somehow so that either the test doesn't care what value you set for Boardwalk's rent in the factory or so that the factory and the test pull Boardwalk's rent value from the same place.


no need for \ in docstrings (or any triple quoted string)


Actually nothing statistically sound, I had a rapid look at its play from the initial position and maybe search is more unstable... With 128 instead of 256 it's more fun but that looked quite weak at bullet TC...


The volume should be set correctly before playing. My ears were blown out when clicking preview XD

<review, user-interface, logic


What would you suggest?


commit标题以后能不能严肃点


Add a describer test for route for display.


Vorschlag: ...Ausschlussentscheid mit Mehrheitsbeschluss;


Thanks @namin it makes sense to me now, it's really a clever idea. I'll use the definition of @sstucki to reformulate the effect safety.


wooww... ı understand now...ı love the new approach... because now we can use our hack in our device trees without bloating common repos(cm team usually was blocking us) so ı think we can see more new devices in cm... :)
and thank you man for your explanation..


dcbw had added an optimization at one point of doing "yum install -y deltarpm" before doing the yum update, to ensure that it can pull down package deltas rather than whole packages to save time. It would be nice to add that back.


I think that this is how the code was originally. Can you check both in 620_SLHC or in 73x? But I don't know if it is like that for a good reason or simply to accept a case which should never happen. I do not remember


See test fragility comment [above](https://github.com/fgs-dbudwin/DBudwin-Monopoly/commit/cf2a6209090f39108ea72a94df202986527dba13#commitcomment-14068648).


huff


alright. looks good. merge conflics solved.


The issue was outdated fa-css-utilities files, solved by running `npm update fa-css-utilities`. It'd be helpful if we mentioned this in the Origin readme, and also flagged relevant updates to fa-css-utilities in Origin's release notes.


It's probably interesting to know what went wrong here :)


You probably want to add a rule for universal types as well.


Why not write the code like this?
```python
while os.getppid() == parent:
    time.sleep(0.1)

proc.kill()  # Is this necessary if we just exit the with block?
```


C'est noté...


:+1: I forgot about this one until you brought it up.


Trop bien, me réjouis de voir ça


You could add a height to the `dd:after` and then set the last dd:after to have a height of 0:

```css
.tribe-help-plugin-info dd::after {
  content: '';
  display: block;
  height: .9em;
}

.tribe-help-plugin-info dd:last-child::after {
  height: 0;
}
```


typo


Does that just mean "you have to use --no-parallel" or is there something ensuring that that I'm just not seeing?


Is there a reason why you placed two line breaks here?

<review, layout


Can't you drop Arrays.asList and use ImmutableList.of ?


Fixes #122


you should not store the result of the last line in a variable and try to describe the result in comments, but rather show the result you actually get from doing that in a console. For example, in this case, that would be:
```
>>> from larray import *
>>> xnat = Axis('nat', ['BE', 'FO'])
>>> xsex = Axis('sex', ['H', 'F'])
>>> zeros([xnat, xsex])
nat\sex |   H |   F
     BE | 0.0 | 0.0
     FO | 0.0 | 0.0
```


With a MS-DOS 3.3 boot.blk, MS-DOS 3.3 boots fine.
Without a boot.blk MS-DOS 3.3, now generates a new message 'error on reading bootsector, Leaving DOS..'. I haven't seen that before, so as yes I'm unsure if that's an improvement or not. I'll investigate.


bad indent (extra space)


That's true... haha I was playing around and found something like that...


This is whole another story actually... I added that as a pending to remember.... but it requires a lot of new changes to implement it.


please leave all booleans lowercase


same as the other one, please leave all bools lowercase


could it move to backend cassandra module ?


general comments, each type you mention LArray, you should use precisely that case (capital A)