OK, the original emails I send were not the correct ones.  I found and sent the correct ones now, also to Tanner this time.


Sure can do - it's not that important to use a raw pointer, but using a shared_ptr is unnecessary and slightly wasteful - the lifetime of the object is controlled by the shared_ptr in the outter scope so it should never be null


It works fine now


Best site


Bloqueio falhou =(


The removal of  the `if (!isScan())` branching code results in an `appInfo` object that is never null. Due to this, the following code (beginning at line 196 after the changes in this file) does not behave properly:

`        BeanConfig beanConfig = appInfo == null
                ? new BeanConfig()
                : new ApplicationBeanConfig(appInfo.getProvider());`

The consequence of the change is that the check always returns an `ApplicationBeanConfig` object rather than a `BeanConfig` object, which causes the call to  the `classes()` method on line 240 of `BeanConfig.java` to never call its own `classes()` method since it calls `ApplicationBeanConfig`'s `classes()` method, which is responsible for populating the list of any listeners annotated with `@SwaggerDefinition`.

Is this a bug, or is there  a workaround? This change breaks our current implementation.


TeamCity Code :: 1. Development :: DDK :: Feature [Build 465](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=33060&buildTypeId=Code_Development_Ddk_Feature) is now running


On Oct 7, 2017 12:40 AM, "AIKKYU" <notifications@github.com> wrote:

xpub2

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/blockchain/My-Wallet-V3/commit/ecf020cc1202b1489e45ed8921fd49088ee2ba75#commitcomment-24813401>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVac3wdG_ZA40PWNTmn4JzciBk3wSh2uks5spnQDgaJpZM4Pv_26>
.


В общем, я вижу, что знания у тебя есть совсем начальные, но если ты хочешь учиться, то я могу бесконечно ревьюировать твой код, пока он не станет идеальным.
Мне это интересно, потому что хочу чтобы все разработчики умели хорошо верстать, мне больно видеть чужой кривой код.
Если тебе это как-то замотивирует, то ни одного фронтендера не возьмут в Яндекс если он плохо верстает, но хорошо пишет скрипты.
Поэтому для начала можешь просто прошерстить методичку на предмет незнакомых тебе тем, там просто кладезь знаний. Учебники никакие советовать не буду, они бесполезны. Потому что пока их переведут на русский, то всё устареет, а на русском никто учебников не пишет.
А так не бойся меня и спрашивай, если есть что-то непонятное. Надеюсь, ты не сильно пугаешься от моих замечаний :)


suggestions?

there was already a "solve_dense" function - so to keep consistency in moving the functionality to other functions which can be called synchronously or asynchronously, I added a "_f" to the to denote "function" as it's kind of the functions function ;)


can do - I think the original version was too


true


oh yeah, feel free to give me the right file!


But the cache was created while constructing shard consumer, I don't think it can get the name of ProcessTask inside there.


TeamCity Code :: 1. Development :: DDK :: Feature [Build 465](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=33060&buildTypeId=Code_Development_Ddk_Feature) outcome was **SUCCESS**
Summary: Tests passed: 64 Build time: 00:03:06


copy pasta


Гут


Метры в секунду (оптимальный рандом)


What's the difference between hardcode processTask here and hardcode it inside startScope?


Да нет вроде


Это просто для теста, потом это планировалось заменить на "разум" машин


Все норм)


@madbuda @radix42 I tried to write down what our process is evolving to be, let me know if these changes sound about right


Test


Изначально тестировал, потом сделал нормально :upside_down_face:


Por que no habria una lista, si las inicializaron en el crear?


No destruyen el iterador, pierde memoria.
BTW, esta logica de iterar la lista la tienen en todas las primitivas


I'll leave it like that then 😇


@Hypnosphi not sure about this change, I guess something more should be done to make it work.


@Natali2411 Можно было и и не задавать start и end. По умолчанию они вся вся строка. Т.е. можно было просто `s.count(' ')`


This patch is not needed anymore since it is relevant only for r7p0 version.


Should we change URL to point to official ARM website?


@Natali2411 Хорошо, что попробовала пользоваться библиотекой math. Но все таки как это сделать без нее?


import React, { Component } from 'react';
import PropTypes from 'prop-types';
//  PropTypes via the main React package is now deprecated.


[Table] Always disable batch-rendering in headers (#1679)

Preview: documentation
Coverage: core | datetime


@Natali2411 Это не следующее четное число. И эту задачу можно сделать без конструкции if в одну строчку :)


The following doc(s) have been deployed to the [dgortonpat](https://dgortonpat-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/guides/frontend-performance](https://dgortonpat-static-docs.pantheonsite.io/docs/guides/frontend-performance)


@Natali2411 Хорошо. Но как эту задачу решить с числом, а не со строкой


Done in new version


hello


@programble I've been going through and overwriting history on various repos of mine to update my name in commits whenever I encounter ones with my old name, and sometimes there are commits that include @-mentions of you. So they're technically new commits, but still have the old commit dates, and GitHub sends a notification. Sorry about that.


I'm going to make this one an else statement


Join work if you fix packets.


Should fix issue #870


That's my dump : https://github.com/gameofbombs/pixi-heaven . It will have many things inside, because its really bad for me to maintain THAT many plugin. Better if i do one, then try to split it later.


This is great. Plus, once we build in support for custom schedule, then we can manually change the values.


@Natali2411 К сожалению это не правильно. У тебя на 7, 1, 1 выдаст, что это треугольник, но с такими сторонами треугольник не получится


@Stefano80 I think there is no doubt this will pass. This has been tested at least once.
https://github.com/lucasart/Stockfish/compare/18b0809...51c448b


this patch is not needed


is it decompile Agile .Net Pro assembly file ?


This line has not been modified since its first introduction in tulip-control/tulip-control@85a9ef325b7391198c1201b2aefd9e7db59ca50b (<https://github.com/tulip-control/tulip-control/blob/85a9ef325b7391198c1201b2aefd9e7db59ca50b/tulip/polytope/polytope.py#L883>). It is clear that `Y` is not used and that this assignment has no side-effects, so it can be deleted.


@Natali2411 Представляешь, в Python можно написать это условие и так `if a<= b <= c:`


This patch is not needed.


Puzzle `297-ce241c0d` disappeared from [`test2o/magma/BlkEncryptedTest.cpp`](https://github.com/DronMDF/goost/blob/master/test2o/magma/BlkEncryptedTest.cpp), that's why I closed #299.


These mutable configuration items should not be global, generally speaking.  Probably per-instance would be appropriate.


@Natali2411 Ну, ты уже знаешь, что принтить можно было и без преобразования в str. Точно знаешь?


This seems to have reverted the change from https://github.com/schemaorg/schemaorg/commit/470cb213f27eb6443a71aa172fed41357773a533#diff-200232fafee461b4217385c536cb093e


Created multidev environment [maripiermorin-ca#dev](https://dashboard.pantheon.io/sites/4a2bbb04-36b6-4c99-8632-8ec18ebc92f3#dev).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://dev-maripiermorin-ca.pantheonsite.io/)


@Natali2411 Тут можно было уже и просто `else:`


I guess we don't need anything relating to overlays, at least not yet.


(This part is a note to myself)  The registry here doesn't represent a registry for all transactions, but a registry of all the peers within a single transaction. (End note)


The following doc(s) have been deployed to the [adamedgmond](https://adamedgmond-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/quicksilver](https://adamedgmond-static-docs.pantheonsite.io/docs/quicksilver)


what does this commit do? the message isn't very helpful


lol now we can finally have weekends thanks alex :D


Are convoy ambushes only going to be done by the Guerillas (when unfriendly) or will OPFOR do convoy ambushes as well?


All cubieboard/cubietrack patches are not needed.


Sorry, but I will not do it: `guix-devel-mode` is just a small minor
mode that **adds** some functionality, but it **does not** change the
existing functionality, so it will not rebind `C-c C-z`.

I really don't think this should be mentioned or handled by Emacs-Guix:
if a user edits Guile files with Geiser, it's up to the user to decide
if (s)he wants to disable auto-compilation or not.

In my opinion, if this should be mentioned anywhere, it's either in
Geiser (like: "...if you work with big Guile files, you better use
--no-auto-compile to avoid slowness...") or in Guix (maybe in [this
page](https://www.gnu.org/software/guix/manual/html_node/The-Perfect-Setup.html)).


Guess, we need changes in den too.


au contraire: it is _transition excellence par excellence_

it is used by the browser when it creates a new BAT wallet and transitions the funds/data from an old BTC proof-of-concept wallet. the specific changes are some information hiding (`getPaymentId`, the callback result return on line 576, and `transitioned`). the other change is to add a codepoint on line 549 for future use in case we find situations in which we want to postpone the transition.


I have issues with the multiply timing, works with timing ignore but not multiply:
drool -vv -c 'text:timing multiply 0.5; client_pool target "0.0.0.0" "53"; client_pool skip_reply; client_pool sendas udp; context client_pools 3;' -r pcap.file
2017-09-06 19:11:50 drool.c:0303 core info: runtime 33.455755187 seconds
2017-09-06 19:11:50 drool.c:0309 core info: saw 2 packets, 0/pps
2017-09-06 19:11:50 drool.c:0313 core info: sent 0 packets
2017-09-06 19:11:50 drool.c:0314 core info: dropped 0 packets
2017-09-06 19:11:50 drool.c:0315 core info: ignored 1 packets


The counter here cannot reasonably be atomic with respect to the items in the registry file.  The easiest safe way to do this would be to synchronize and use a plain counter.


No. It's not my idea... I 've got several git hub accounts and they fails at this moment.
If i am done - i will do a PR as usually.


sorry about that!  Thanks @Klumbumbus


not needed.


У тебя пропускаются первые элементы последовательности 0,1,1...
А здесь получается сразу 1,2,3...


good


why


Aaaand.... you commited console.log again ._.


What's the same output if you use "timing keep" and "timing ignore"?


Still pondering this. I’ll leave it open for now


@uncle-tee
Thanks for checking it.
Kindly help point out the bug.
Also, I am interested in learning more about 'code testing'. What learning resources do you think could be of help?
Thanks and regards.


[Core/Tabs2] Write tests for Tabs2 fix in #1492 (#1683)

Preview: documentation
Coverage: core | datetime


@mvmlisb Хорошо, мне нравится, что ты нашел функцию в библиотеке math. А как без нее это сделать?


Тут тоже надо убрать теги


Created multidev environment [maripiermorin-ca#dev](https://dashboard.pantheon.io/sites/4a2bbb04-36b6-4c99-8632-8ec18ebc92f3#dev).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://dev-maripiermorin-ca.pantheonsite.io/)


There is (I think) a race here between closing and deleting the file, and creating a new file if a new resource came in on another thread at the same time the given one was removed.  It's probably OK to just retain the file until the transaction is completed (even if it means extra resources are logged).


Чтобы не считать сумму последних элементов в условии и в теле цикла, можно в условии проверять значение последнего элемента массива (метод last)


@mvmlisb Теперь ты знаешь, как это одним принтом сделать. Да?)


Тут достаточно указывать только -1 и -2 в индексе, не вычитая из arr.size, потому что в руби могут быть отрицательные индексы, будет то же самое, но короче.


drool -vv -c 'text:timing ignore; client_pool target "0.0.0.0" "53"; client_pool skip_reply; client_pool sendas udp; context client_pools 3;’ -r pcap.file
2017-09-06 19:23:14 client_pool.c:0500 network error: client send failed
2017-09-06 19:23:15 drool.c:0274 core info: end
2017-09-06 19:23:15 drool.c:0303 core info: runtime 1.204749090 seconds
2017-09-06 19:23:15 drool.c:0309 core info: saw 1388903 packets, 1152857/pps
2017-09-06 19:23:15 drool.c:0311 core info: sent 893654 packets, 741776/pps 98/abpp
2017-09-06 19:23:15 drool.c:0314 core info: dropped 16026 packets
2017-09-06 19:23:15 drool.c:0315 core info: ignored 479223 packets


@mvmlisb Хорошо! Но это задание можно решить и без if конструкции одной формулой ))


Используй << для добавления в массив, так принято по стилю


@mvmlisb Ты сразу здесь мог писать `t1 + t2 > t3`


When you references files for <img>, <embed>, etc., you need to link to another web site or add them into your site's repo.

To link to an external site, your `src` needs to begin with `http://` or `https://`. Otherwise it does not know to load the file from an external site.


@streeter
Shouldn't this fall back to `raise`?
Currently it will proceed, whereas previously it would have aborted.


These lines cause a NPE for a lot of models. For connections the go from a subcomponent to a system level feature (or visa versa) the destination (source) node will be null.


timing keep freezes just like multiply


Я знаю, поэтому и сообщаю ))


The previous code failed to correctly sort by rating on Firefox.
No idea why this works but whatever...


Added a ground connection to pin 1 of rightmost buffer chip, fixed LED correspondence, fixed a resistor placement.


The recovery registry should not be a part of this API, it should be a part of the JBoss provider only.  Some local transaction managers may not need it because they log the transaction actively instead of only logging on completion like ours does.  Also, making it a part of this API makes it more difficult to configure.

With that in mind, I would think that it would be better to have a class that represents the entire transaction registry, with operations such as "add destination X to Xid yyyy" and "list all in-doubt Xids" that open and close the file(s) within a single operation, and skip having long-lived file channels which can lead to starvation issues and also provide ample opportunity to introduce resource leaks.  It also means that the code which accesses the registry is very near to the code which registers the recovery helper into Narayana, which should allow for some other simplifications.


DisplaySendCommand( ( dfStatus.flipped ) ? 0x12 : 0x10 );
100088 bytes

DisplaySendCommand ( 0x12 );
else
DisplaySendCommand ( 0x10 );
100108 bytes

думаю, ето зависит от оптимизации компилятора.
Логично предположить, что меньше должен бьіть первьій код, так как в нем те же два сравнения, но всего один вьізов функции.
Также не стоит забьівать о так назьіваемом Align - вьіравнивании размера файла до размера "блока" памяти


Хм, по заданию требуется сформировать хэш, а не вывести гласные и индексы.


The min and max key are the start and end of a range. So your current min key starts at the inode you want to inspect, but then at the EXTENT_DATA key value. Your max key is halfway the data of the next inode, because you end at EXTENT_DATA inside there again. Individual fields of a search key don't work like a filter. It's a start and an end, nothing more. Also see 1a63143 in the kernel.

So if you want to get all EXTENT_DATA items from an inode, your min and max would be...
`min_key = btrfs.ctree.Key(inode, btrfs.ctree.EXTENT_DATA_KEY, 0)`
`max_key = btrfs.ctree.Key(inode, btrfs.ctree.EXTENT_DATA_KEY + 1, 0) - 1`
...instead. The -1 is of course a nice convenience thingie, it causes it to be the same as this in my example:
`min_key = btrfs.ctree.Key(inode, btrfs.ctree.EXTENT_DATA_KEY, 0)`
`max_key = btrfs.ctree.Key(inode, btrfs.ctree.EXTENT_DATA_KEY, 18446744073709551615)`


Because ``com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple`` and ``com.arjuna.ats.internal.jta.transaction.jts.TransactionImple`` are different classes, and the type hierarchy in Narayana is a bit muddled in this regard.


@RomaWest Ты что программируешь в Word???? Как же ты запускал? Перенеси код в обычный текстовый формат и поменяй разрешение на .py


[inst/examples/Wolf-Sheep-Predation/Wolf-Sheep-Predation.R:249:8:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/Wolf-Sheep-Predation.R#L249) *style:* **Place a space before left parenthesis, except in a function call.**
```r
while ((NLany(sheep) | NLany(wolves)) & time < maxTime) {
       ^
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:64:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L64) *style:* **Variable or function name should be lowerCamelCase.**
```r
doEvent.WolfSheepPredation <- function(sim, eventTime, eventType, debug = FALSE) {
^~~~~~~~~~~~~~~~~~~~~~~~~~
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:113:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L113) *style:* **Variable or function name should be lowerCamelCase.**
```r
WolfSheepPredationInit <- function(sim) {
^~~~~~~~~~~~~~~~~~~~~~
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:185:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L185) *style:* **Variable or function name should be lowerCamelCase.**
```r
WolfSheepPredationSave <- function(sim) {
^~~~~~~~~~~~~~~~~~~~~~
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:200:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L200) *style:* **Variable or function name should be lowerCamelCase.**
```r
WolfSheepPredationPosition <- function(sim) {
^~~~~~~~~~~~~~~~~~~~~~~~~~
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:220:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L220) *style:* **Variable or function name should be lowerCamelCase.**
```r
WolfSheepPredationPopSize <- function(sim) {
^~~~~~~~~~~~~~~~~~~~~~~~~
```
[inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R:243:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/inst/examples/Wolf-Sheep-Predation/WolfSheepPredation/WolfSheepPredation.R#L243) *style:* **Variable or function name should be lowerCamelCase.**
```r
WolfSheepPredationEvent <- function(sim){
^~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:15:12:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L15) *style:* **Variable or function name should be lowerCamelCase.**
```r
  function(.Object="agentMatrix", coords, ..., levelsAM) {
           ^~~~~~~
```
[R/agentMatrix-Class-methods.R:16:5:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L16) *style:* **Variable or function name should be lowerCamelCase.**
```r
    Coords <- TRUE
    ^~~~~~
```
[R/agentMatrix-Class-methods.R:29:7:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L29) *style:* **Variable or function name should be lowerCamelCase.**
```r
      Coords <- FALSE
      ^~~~~~
```
[R/agentMatrix-Class-methods.R:99:11:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L99) *style:* **Place a space before left parenthesis, except in a function call.**
```r
      if ((is.matrix(dotCols[[1]]) & is.numeric(dotCols[[1]])) | is(dotCols[[1]], "agentMatrix"))
          ^
```
[R/agentMatrix-Class-methods.R:395:6:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L395) *style:* **Commented code should be removed.**
```r
    #charCols <- match(j, nam)
     ^~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:396:6:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L396) *style:* **Commented code should be removed.**
```r
    #charCols <- match(nam, j)
     ^~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:397:34:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L397) *style:* **Commented code should be removed.**
```r
    numCols <- which(!charCols) #colNums[!(colNums %in% charCols)]
                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:404:8:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L404) *style:* **Commented code should be removed.**
```r
      #numColsJ <- which(colNums %in% numCols)
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:409:8:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L409) *style:* **Commented code should be removed.**
```r
      #charColsJ <- which(colNums %in% charCols)
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:609:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L609) *style:* **Variable or function name should be lowerCamelCase.**
```r
head.agentMatrix <- function(x, n = 6L, ...) {
^~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:617:1:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L617) *style:* **Variable or function name should be lowerCamelCase.**
```r
tail.agentMatrix <- function(x, n = 6L, ...) {
^~~~~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:638:36:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L638) *style:* **Variable or function name should be lowerCamelCase.**
```r
cbind.agentMatrix <- function(..., deparse.level) {
                                   ^~~~~~~~~~~~~
```
[R/agentMatrix-Class-methods.R:662:36:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/agentMatrix-Class-methods.R#L662) *style:* **Variable or function name should be lowerCamelCase.**
```r
rbind.agentMatrix <- function(..., deparse.level = 1) {
                                   ^~~~~~~~~~~~~
```
[R/plot.R:37:3:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/plot.R#L37) *style:* **Variable or function name should be lowerCamelCase.**
```r
  Ras <- world2raster(x)
  ^~~
```
[R/plot.R:53:3:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/plot.R#L53) *style:* **Variable or function name should be lowerCamelCase.**
```r
  Ras <- world2raster(x)
  ^~~
```
[R/quickPlot.R:179:39:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/quickPlot.R#L179) *style:* **Commas should always have a space after.**
```r
    grobToPlot@.Data <- toPlot@.Data[,,sGrob@layerName];
                                      ^
```
[R/turtle-functions.R:92:32:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L92) *style:* **Place a space before left parenthesis, except in a function call.**
```r
    coords <- cbind(xcor = rep(((maxPxcor(world) - minPxcor(world)) / 2) + minPxcor(world), n),
                               ^
```
[R/turtle-functions.R:92:33:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L92) *style:* **Place a space before left parenthesis, except in a function call.**
```r
    coords <- cbind(xcor = rep(((maxPxcor(world) - minPxcor(world)) / 2) + minPxcor(world), n),
                                ^
```
[R/turtle-functions.R:93:32:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L93) *style:* **Place a space before left parenthesis, except in a function call.**
```r
                    ycor = rep(((maxPycor(world) - minPycor(world)) / 2) + minPycor(world), n))
                               ^
```
[R/turtle-functions.R:93:33:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L93) *style:* **Place a space before left parenthesis, except in a function call.**
```r
                    ycor = rep(((maxPycor(world) - minPycor(world)) / 2) + minPycor(world), n))
                                ^
```
[R/turtle-functions.R:449:35:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L449) *style:* **Place a space before left parenthesis, except in a function call.**
```r
                          xcor = ((world@extent@xmax - world@extent@xmin) / 2) +
                                  ^
```
[R/turtle-functions.R:451:35:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/turtle-functions.R#L451) *style:* **Place a space before left parenthesis, except in a function call.**
```r
                          ycor = ((world@extent@ymax - world@extent@ymin) / 2) +
                                  ^
```
[R/world-functions.R:517:25:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/world-functions.R#L517) *style:* **Put spaces around all infix operators.**
```r
          mid <- floor(n/2)
                       ~^~
```
[R/world-functions.R:534:9:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/world-functions.R#L534) *style:* **Commented code should be removed.**
```r
    #   cat("names       :", paste(ln, collapse=", "), "\n")
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/world-functions.R:538:28:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/world-functions.R#L538) *style:* **Commas should always have a space after.**
```r
    print(object@.Data[1:4,1:4,])
                           ^
```
[R/world-functions.R:538:32:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/world-functions.R#L538) *style:* **Commas should always have a space after.**
```r
    print(object@.Data[1:4,1:4,])
                               ^
```
[R/worldNLR-classes-methods.R:340:5:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/worldNLR-classes-methods.R#L340) *style:* **Variable or function name should be lowerCamelCase.**
```r
    NLwMs <- list(...)
    ^~~~~
```
[R/worldNLR-classes-methods.R:502:11:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/R/worldNLR-classes-methods.R#L502) *style:* **Place a space before left parenthesis, except in a function call.**
```r
    floor((cellNum - 1) / b[2]) + seq.int(from = 1, to = prod(b),
          ^
```
[tests/testthat/test-plotting.R:6:3:](https://github.com/PredictiveEcology/NetLogoR/blob/d663a662e8b29c4f3e06cb63483e53f503101cb4/tests/testthat/test-plotting.R#L6) *style:* **Variable or function name should be lowerCamelCase.**
```r
  t1_0 <- createTurtles(n = 10, coords = cbind(rep(0, 10), rep(0, 10)))
  ^~~~
```


@rynowak Great, so meet you on the other side :wink:


should be plural for easier understanding


Does the updateOne method no longer support passing in a document as `update`? That won't have a "$" and implicitly and "atomic" operator?


Hm. The context for this is super old, seeing as it's been over a year since I made this PR.

However, I believe the issue was that the response coming back from Stipe was a 404, and contained the message `a similar object exists in test mode`. [I asked](https://github.com/pinax/pinax-stripe/pull/252#issue-146645738) if we should check that as well, but never got an answer back.

But I'm having a hard time remembering why this was needed now.


replace with assertFalse


@JulianeAlbuquerque this commit is ref to #2


@Natali2411 Этот метод сделает только у первого метода большую букву, а не у всех слов в строке


Hi! I was wondering if this issue:
[FIX] mrp: Product Cost Structure decimal precisions
http://gitlab.opengest.fr/opengest/odoo/commit/df91cb5a9a64bb2c2c7ce379de7591c36c99bc02

Is it already fixed on this commit?, since I'm on v10 CE, and even when decimals for price is set to 3 the report only uses 2 digits on the BOM Cost report
Both structures are quite different, but i guess we're talking about this file to need fixing.
addons/mrp/report/mrp_bom_cost_report.py

Thanks for the attention so far.


After call to stack.pop() - the first item should be removed.
So, second call to stack.pop() should return "item 2".
Might yuo be so kind to fix it?


r+


Are you sure it's actually freezing and not just replaying the traffic with
the same delays that are in the PCAP?


Yeah, I think it was to help distinguish them from validator keys. At first, I was going to use `TOKEN_ACCOUNT_PUBLIC` but Vinnie hates base58.


saw approval from vogel
at https://github.com/MonsieurNicolas/stellar-core/commit/0333d65b6ba3f55d8cf09811ac72f08fad6c0503


merging MonsieurNicolas/stellar-core/ledgerDeltaAsserts = 0333d65b into auto


MonsieurNicolas/stellar-core/ledgerDeltaAsserts = 0333d65b merged ok, testing candidate = 918874cc


What I mean is that the `except` swallows all of stripe's `InvalidRequestError`s now.

I think it's fine to react on 404 like that, but if it does not continue, it should raise probably?!


I would also like to know how to substitute different gutter widths per breakpoint now that this gutter map is no longer available...


Ah, yeah, that's probably a fine call


well the pcap data is for a 10 minute interval, and if running in timing keep is taking longer then that about 20 minutes now. Does this seem like its freezing or am I missing something.


Took away previous hurricanes and added Nate


sir how should i implement a project where i want a object to travel over a 2d vector space and avoiding the collision between them.


[Jenkins vg tests](http://jenkins.cgcloud.info/job/vg/750/) complete for merge to master.  View the [full report here](http://cgl-pipeline-inputs.s3.amazonaws.com/vg_cgl/vg_ci/jenkins_reports/branch/master/index.html).

10 tests passed, 0 tests failed and 11 tests skipped in 10543 seconds

Tests produced 1974 warnings. 1974 were for lower-than-expected alignment scores


Please add the license comment at the top of all files


Created multidev environment [maripiermorin-ca#dev](https://dashboard.pantheon.io/sites/4a2bbb04-36b6-4c99-8632-8ec18ebc92f3#dev).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://dev-maripiermorin-ca.pantheonsite.io/)


Ah, yes. That should indeed be removed. Lol.


I'm sorry, I meant to say 'params.properties' or 'config.properties'.


If it doesn't matter what the values are, because each is as good as another, don't bother with Random, just use a hard coded value as it's less code. I think that's the case in these tests --- if 57 doesn't find a bug, 657 won't either.


Similar comment for Guid. If you don't need uniqueness, just use a hard coded value as it's less code.
If you do need uniqueness, of course Guid is necessary. It's also sometimes a convenient way to get "randomness" in the form of a hex string. If you need randomness.


Values of other following constants are influenced after removing otherTrans.
This causes that projects depending on liblouis must either re-compile their binaries or update their (Python) scripts to upgrade liblouis version.
Is this a backward incompatible change? However, I think constants should remain their original values for better compatibility.


Actually an empty chat.ts file already exist at this point and should be picked up by `tsc`.


When one has linkAssets set to false on production and then switches to linkAssets true, it will create new dir automatically and use symlinks instead of requiring you to delete your asset dir contents. No cast is necessary for the purpose.


a for loop is not needed. this can be written as
`byte[] myRawData = new byte[4] {  0, 1, 2, 3 };`  ("array initializer")


if not можно заменить на unless, немного синтаксического сахара)


It has a typo. "selection" should be "section". Then it pass judge.
Anyway, with <!-- .... --> after closing tags, it is unnecessary complicated.
It should work properly for same problem without <!-- ... -->, while the shorter solution can not.


are casts needed here?


are casts needed here? and same comment above, etc.


This was unnecessary since Object.assign will ignore falsy values


Вообще, считается хорошим тоном при наличии else ветки писать через if, перевернув условную проверку. Но в конкретном случае unless выглядит неплохо.


Can you please raise an issue for major version to expand the scopes?


I didn't look, but make sure that the tests in each class can safely run concurrently with the tests in any other class. Eg., they don't both register an event source with the same name. Sometimes people use the class name as a prefix to the ID.


Ok, thanks for the quick feedback.  https://github.com/pinax/pinax-stripe/pull/387.


@mvmlisb На всякий случай: в сообщениях к коммитам можно использовать пробелы :)


We need some kind of description about what this is.


Changed return type to return JSON object


@lecaillon - I'm happy to announce that the real work will be beginning soon https://github.com/aspnet/HttpClientFactory/projects/1


TeamCity Glyssen :: Glyssen pull requests [Build *.*.652.66caadf9cf49beee03c662d040edeccf6b066879](http://build.palaso.org/viewLog.html?buildId=99036&buildTypeId=Glyssen_GlyssenPullRequests) outcome was **SUCCESS**
Summary: Tests passed: 1777, ignored: 18 Build time: 00:10:12


what？？？？？？？


thanks for the update


thanks for the rearrangement


u made a mistake by moving div


This commit does not appear in the npm version of this library.


new updates


test by github


ddd


@zachariasmaladroit this breaks mobile data connection, the rmnet0 interface disappears!


@jawshy the space and the BIS je only for look ? Because with or without space the script Working fine no ?


It occurs to me that this should probably be class=inactive.  I don't think I entirely got what he class names meant when I set that.


ok no problem


thx


```c16849715.lua
--雷の天気模様
function c16849715.initial_effect(c)
	c:SetUniqueOnField(1,0,16849715)
	--Activate
	local e1=Effect.CreateEffect(c)
	e1:SetType(EFFECT_TYPE_ACTIVATE)
	e1:SetCode(EVENT_FREE_CHAIN)
	c:RegisterEffect(e1)
	--effect gain
	local e2=Effect.CreateEffect(c)
	e2:SetDescription(aux.Stringid(16849715,0))
	e2:SetCategory(CATEGORY_TOHAND)
	e2:SetType(EFFECT_TYPE_QUICK_O)
	e2:SetCode(EVENT_BATTLE_START)
	e2:SetRange(LOCATION_MZONE)
	e2:SetCondition(c16849715.retcon)
	e2:SetCost(aux.bfgcost)
	e2:SetTarget(c16849715.rettg)
	e2:SetOperation(c16849715.retop)
	local e3=Effect.CreateEffect(c)
	e3:SetType(EFFECT_TYPE_FIELD+EFFECT_TYPE_GRANT)
	e3:SetRange(LOCATION_SZONE)
	e3:SetTargetRange(LOCATION_MZONE,0)
	e3:SetTarget(c16849715.eftg)
	e3:SetLabelObject(e2)
	c:RegisterEffect(e3)
end
function c16849715.eftg(e,c)
	local seq=e:GetHandler():GetSequence()
	local cseq=c:GetSequence()
	return c:IsType(TYPE_EFFECT) and c:IsSetCard(****) and cseq<5 and math.abs(seq-cseq)<2
end
function c16849715.retcon(e,tp,eg,ep,ev,re,r,rp)
	local c=e:GetHandler()
	local bc=c:GetBattleTarget()
	return bc and c:IsRelateToBattle() and bc:IsRelateToBattle()
end
function c16849715.rettg(e,tp,eg,ep,ev,re,r,rp,chk)
	if chk==0 then return true end
	Duel.SetOperationInfo(0,CATEGORY_TOHAND,e:GetHandler():GetBattleTarget(),1,0,0)
end
function c16849715.retop(e,tp,eg,ep,ev,re,r,rp)
	local bc=e:GetHandler():GetBattleTarget()
	if bc:IsRelateToBattle() then
		Duel.SendtoHand(bc,nil,REASON_EFFECT)
	end
end
```


changes from github


Okej


Class


# Good job!

*You deserved it*


敏感时期……等十一月吧


Спасибо, конечно, но это пока самый удобный способ узнать из какого лифта вышел пассажир. Не стоит это отрубать :)


bootstrap


Can you push the latest when you have a moment? Thanks !


@nobu

Thank you.  I was the partial author...

What is easiest for you, a PR here, or a patch file in an issue at https://bugs.ruby-lang.org/ ?


This commit has been mentioned on **Discourse Meta**. There might be relevant details there:

https://meta.discourse.org/t/members-of-groups-staff/71437/5


deleting


子曰：扯


Had some weird behaviour `deoplete` and `auto-pairs` inserting new lines when picking an auto complete option.

Works fine with `autoclose`.


同意修改


This wasn't a bug... I didn't have the latest version of wednesday-bot on AWS...


Oh I see. Thanks for the pointer.


You’re receiving this email because you recently created a new GitHub account or added a new email address. If this wasn’t you, please ignore this email.


나는 신이오. 으흠


Nice, @chantal66!


WARNING: [UnusedResources] The resource `R.color.grayLight` appears to be unused
 Unused resources make applications larger and slow down builds.


WARNING: [UnusedResources] The resource `R.layout.activity_register` appears to be unused
 Unused resources make applications larger and slow down builds.


@harlanbruno @leoadb fyi.


I think there have overflow problem
maybe change to:
return new Ip(Long.parseLong(evaluate(m, e)));


No objection. Something like... https://www.npmjs.com/package/url-regex


@fogfish I tested on ios11 on a real iphone7 and polylines work great! Thanks so much for forking to this branch, I will be using yours for some production code.


Thanks for updating the release notes, would you mind deleting all the other lines and keep only headings?


Can you please explain why `moment.relativeTime` not needed in case of `moment.localeData`?


You're repeating a lot of code in these tests. You could consider extracting a method that does all the work, and the test could collapse down to almost nothing.
Even better, consider doing a [Theory] instead of a fact, and add the variations as attributes, like this example from another test:
```c#
        [Theory]
        [InlineData(16, 20, -5, -1)]
        [InlineData(16, 21, -4, 1)]
        [InlineData(16, 20, 0, 0)]
        [InlineData(16, 20, 0, 4)]
        [InlineData(16, 24, 0, 4)]
        public void CopyTo(
            int size,
            int arraySize,
            int arrayLowerBound,
            int copyToIndex)
        {
```


I recommend describing these in English without just referring to the variable names.


Stop preventDefault'ing on wheel (#1674)

Preview: documentation
Coverage: core | datetime


This commit caused a regression:
https://repology.org/metapackage/xorg-server/versions
xorg-dmx is grouped with xorg-server, which is not correct.
Is this commit okay or do I need to open an issue?


Is `Clear()` necessary? You're about to dispose of the event log, is that enough?


Thank you for this fix


try instructions here:
https://github.com/dotnet/corefx/blob/master/Documentation/building/code-coverage.md
to get code coverage information, so you can see what parts of event log needs coverage from tests.

It should work -- there is a bug https://github.com/dotnet/corefx/issues/23588 but I think it is not relevant to you if you run only on this library.


Can you fill these in?


Используй постфиксную форму записи, если в if всего одна строка:
puts "#{month}: #{days}" if days == 30


GLHE_Enhancements (mitchute) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


it is not good to initialise a function, which is not anonymous to a variable with the same name.


@tecpromotion Zur Kenntnis für die Zukunft (siehe Commit-Message)


3) is not the case: `degree_C` is accepted, but as opposed to `set_units` not replaced by its symbol.
2) I don't know, and I'm not sure if it is worth the effort (and code mess)
1) maybe yes.

Frankly, I'm quite unhappy with the way things are now -- `make_unit` and `set_units` are nearly identical, yet have their differences. `make_unit` now suddenly needs an argument to specify user-defined units. Calls like `make_unit(paste("m", "/", "s"))` no longer work. I'm thinking about going back to have `set_units` accept expressions, `make_unit` only accept non-udunit units (user-defined), and `parse_unit` parse only the `km s-1` form. Three different functions for three different purposes.


Используй << для добавления в массив, так принято по стилю


Intriguing. What is FaCT?


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-3668-15t4eve: pid 3755 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171006-3668-15t4eve ...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-3668-15t4eve: pid 3755 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171006-3668-15t4eve

ERROR: /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master/quiz_spec.rb; @todo found, but puzzle can't be parsed in line #10, most probably because TODO is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/app/objects/exec.rb:41:in `block in run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/app/objects/exec.rb:39:in `run'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:37:in `deploy'
/app/objects/job.rb:40:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:49:in `block in exclusive'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/app/objects/job_detached.rb:47:in `exclusive'
/app/objects/job_detached.rb:37:in `block in proceed'
/app/objects/job_detached.rb:37:in `fork'
/app/objects/job_detached.rb:37:in `proceed'
/app/0pdd.rb:336:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


I recommend separating out the creation of the dictionary in one line and then the return of the json.dumps on the next line. I also recommend indenting the dictionary to show hierarchy.


Should this perhaps be `weak_connect_signal`?


Where is this signal connected? And why would it be needed?


@swankjesse I want to link to KDoc like you do. Do you host this GitHub page with a custom domain? I am not sure how to find out where you host the documentation. Thank you.


Thanks! For information I improved the --check-library today. When using `--check-library --enable=information` on cppcheck lib I saw there are a few more methods we haven't configured.


Agile protector itself is slightly modified so it does not work

However any assembly protected by it seems to be fine


Я надеюсь, ты понимаешь, что это не очень красиво? )
Тебе достаточно одномероного массива для хранения кол-ва дней в месяце, без указания самого месяца.
Массивы в Ruby упорядоченные. Достаточно будет просуммировать необходимые месяцы. А так получается, что даже если пользователь указал январскую дату, то у тебя будут проводиться все вот эти вычисления.


Should this be `beautiful.notification_font or beautiful.font`?


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-3914-hbc5mz: pid 4001 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171006-3914-hbc5mz  ERROR:...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-3914-hbc5mz: pid 4001 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171006-3914-hbc5mz

ERROR: /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master/quiz_spec.rb; @todo found, but puzzle can't be parsed in line #10, most probably because TODO is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/app/objects/exec.rb:41:in `block in run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/app/objects/exec.rb:39:in `run'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:37:in `deploy'
/app/objects/job.rb:40:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:49:in `block in exclusive'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/app/objects/job_detached.rb:47:in `exclusive'
/app/objects/job_detached.rb:37:in `block in proceed'
/app/objects/job_detached.rb:37:in `fork'
/app/objects/job_detached.rb:37:in `proceed'
/app/0pdd.rb:336:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


Can a notification even change its icon? I would have expected it to be quite constant.


Согласись, не очень красиво и принцип dry не соблюдается.
Если много повторяющегося, однообразного кода, то что-то не так.


is it possible to add support for Agile .Net pro ?


Thanks for making me aware of this issue @toddocon 👍


Объявляй пустые хеши так: hash = {}


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/284365814?utm_source=github_status&utm_medium=notification


If the color picker is displayed outside of the viewport, it is moved backwards.
This, obviously, only if there is enough space!


vk


Thank you!


Minor points. I recommend putting the ) on the next line so that in the future, it's easier to change parameters. With the ) on the next line, you can just delete this line if you don't want it in the future. I recommend an indentation of only 4 spaces rather than 8 spaces, as well.


Great job in the documentation!


если открываешь блок на несколько строк, то приняnо использовать
```
do |..|
  ...
end
```


Please fill these in.


@Rahul151995 this comments are about the commit, you should create a new issue with your question.


GitGolf Champion - Hole In One


И здесь используй постфиксную форму записи, так как в if одна строка.


Can you add description of what this value is?


[R/AddinServer.R:15:26:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/AddinServer.R#L15) *warning:* **no visible global function definition for ‘.get_title_and_message’**
```r
    title_and_message <- .get_title_and_message(response = response)
                         ^~~~~~~~~~~~~~~~~~~~~~
```
[R/AddinServer.R:40:7:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/AddinServer.R#L40) *warning:* **no visible global function definition for ‘.create_test_result_element’**
```r
      .create_test_result_element(i = i, test_results = test_results)
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/AddinUI.R:65:1:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/AddinUI.R#L65) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/AddinUI.R:66:1:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/AddinUI.R#L66) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/Authentication.R:45:5:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/Authentication.R#L45) *style:* **Commented code should be removed.**
```r
  # url <- "https://tmc.mooc.fi/api/v8/core/org/hy/courses"
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/TMC_plugin.R:8:9:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/TMC_plugin.R#L8) *warning:* **no visible binding for global variable ‘.ui’, Did you mean 'ui'?**
```r
  ui <- .ui
        ^~~
```
[R/TMC_plugin.R:10:13:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/R/TMC_plugin.R#L10) *warning:* **no visible binding for global variable ‘.server’, Did you mean 'server'?**
```r
  server <- .server
            ^~~~~~~
```
[tests/testthat/testLintr.R:2:5:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/tests/testthat/testLintr.R#L2) *style:* **Commented code should be removed.**
```r
#   context("lints")
    ^~~~~~~~~~~~~~~~
```
[tests/testthat/testLintr.R:4:7:](https://github.com/RTMC/tmc-rstudio/blob/46d4430e0e5cd200d987d41c78026a1e46950925/tests/testthat/testLintr.R#L4) *style:* **Commented code should be removed.**
```r
#     lintr::expect_lint_free()
      ^~~~~~~~~~~~~~~~~~~~~~~~~
```


Please fill all these in. You can just copy and paste from other functions.


Используй << для добавления в массив, так принято по стилю


These functions are typically used to compare secrets or authentication tags with expected values. We try to achieve a couple things here:
- make the execution time independent of the values being compared
- minimize the time secrets will be kept in registers
- avoid LTO if comparisons are made against hard-coded secrets.
- still keep these functions fairly fast, since they can be called very frequently.
Unlike general purpose registers, SIMD registers tend to not be quickly reused. Since they are also wider, they also hold bigger chunks of these secrets. Making them volatile has a small cost (compare the generated code with/without), but is necessary to prevent the final zeroing from being optimized.


I recommend changing this to the simpler ```SSE/dof```.


drool -vv -c 'text:timing keep; client_pool target "0.0.0.0" "53"; client_pool skip_reply; client_pool sendas udp; context client_pools 3;' -r pcap.file
2017-09-06 19:27:56 drool.c:0611 core info: setup signal handling
2017-09-06 19:27:56 drool.c:0640 core info: initialize pcap-thread
2017-09-06 19:27:56 drool.c:0229 core info: start
^C2017-09-06 20:18:24 drool.c:0274 core info: end
2017-09-06 20:18:24 drool.c:0303 core info: runtime 3027.925578577 seconds
2017-09-06 20:18:24 drool.c:0309 core info: saw 2 packets, 0/pps
2017-09-06 20:18:24 drool.c:0313 core info: sent 0 packets
2017-09-06 20:18:24 drool.c:0314 core info: dropped 0 packets
2017-09-06 20:18:24 drool.c:0315 core info: ignored 1 packets


Тебе не нужно здесь исползовать лишние переменны и обменивать их значения. Сделай массив с 2-мы первыми элементами (единицы) и используй элементы массива для вычисления суммы и в условиях. Не забывай, что индекс может быть отрицательным, это нужно чтобы получить последний и предпоследний элементы.


fast-forwarding master to auto = 918874cc


вот ещё очень крутое пособие для начинающих https://melnik909.gitbooks.io/tutorial-for-beginner-front-end-developer/content/html.html


I like the additional of the equations here!


Well spotted. But I guess it's too late now @egli?


#3 This is the problematic line


This is an example of the result!

![dynamic-position](https://user-images.githubusercontent.com/32025549/31296929-6de3b562-aae4-11e7-95c1-a841e44b45b6.png)


I recommend just combining these two lines at the end, as we already know what's being returned from the comments and name of the function.


I recommend filling these in from other functions by just copying and pasting.


Hi Alain,
yes that was my original idea, I don't know what I was thinking while changing the values in psqt :D


GLHE_Enhancements (mitchute) - i386-Windows-7-VisualStudio-14: OK (2782 of 2785 tests passed, 0 test warnings)

Failures:

EnergyPlusFixture Test Summary
 * Passed: 546
 * Failed: 2

integration Test Summary
 * Passed: 610
 * Failed: 1

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


I recommend combining these last two lines as you know what is being returned from the function name and documentation.


with a 300ms I can see up to just 3 blocking calls to `refreshCurrentTime()`


You can do

```java
if (List.class.isAssignableFrom(valueClass)) { /* ... */ }
```
so it works with any `List` subclass. Same for `Map`. As for `Arrays` it just contains utility methods, you'll never find an instance of that. You might as well remove that case.

(Just investigating why my app crashed while receiving a document with an array field and found this fix.)


I recommend separating this expression out into its own function.

```2*stats.t.sf(np.abs(t), dof)```


I recommend combining the last two lines.


Please remember to fill in all the documentation of variables.


Делай отступы в 2 пробела внутри циклов, условий, блоков и т.п.


Настрой редактор на отступ ровно в 2 проблела, именно так принято в ruby. Причем, именно пробела, а не таба.


GLHE_Enhancements (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: Tests Failed (765 of 1565 tests passed, 0 test warnings)

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


This is a generic, unoptimized function, that accepts any length.

`crypto_verify_n()` is an internal, static function.

It's always inlined to create functions specialized for common sizes (16, 32, 64 bytes -- `crypto_verify_16`, `crypto_verify_32`, `crypto_verify_64`).


I recommend describing what's going on without just referring to variable names.


Truth be told,I also write my test case manually. And am sure you must have done that. Most likely by testing different case scenarios. A good way you have done is by asking a third party to perform code review there is no better software.

Here is the bug.
Imagine if a user input is "5.55".That is a floating number. So is_numeric will not be best as you have only checked if it's a number and not an interget . You had better use is_int or is_float. I hope it helps. I am always avail to help with code reviews. Cheers.


It was used by FFI. I have changed before all the uses to use Smalltalk anonymousClassInstaller. That was something that I hadn't updated correctly. It should not affect FFI at all.


@samdark OK, thanx.


i already have stars!! this is going to be huge


What does the OOS version of the takePicture function do that the default AOSP sources don't? In other terms, why was it necessary to call it like this?


I don't think there's any need to break this into two lines.


Is this fix in version 0.58.4?


@FazeelUsmani delete any other Google Camera version you have already installed


Can you please specify the parameters in the function call? Something like

```python
... np.average(mean_y_local, weights=count_y_local)
```


I don't think there's a need to split this into two lines. It's readable enough on just one line.


Do you know what exactly was the ANR in `refreshCurrentTime`, pure refreshing of UI components shouldn't be an issue since they are not computed until next refresh by the framework, which should happens surely at more than 3fps


Здесь нужен вызов func с аргуметами


Thanks, will make the changes you suggested. I'll be deploying a new version to npm with this in - in a couple hours, just sorting a few other things first :)


I recommend combining these two lines.


Sorry for the typos here, good catch!


I don't think there's a need to separate this out onto two lines, as it's readable on one.


I recommend removing the parentheses, as they are not necessary.


O que é isso?


Does response.StatusCode not work to return the status code, to pass into the exception?


I recommend combining these two lines. Also, I recommend putting the opening { on a separate line to make it more maintainable in the future. Easier to just delete whole lines when that is separate.


GLHE_Enhancements (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed (1393 of 2825 tests passed, 0 test warnings)

Failures:

integration Test Summary
 * Passed: 1
 * Failed: 613

regression Test Summary
 * Passed: 627
 * Failed: 2

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


แกแแปแป


GLHE_Enhancements (mitchute) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


А можно более чётко? Пример работы от Василия выполняется...


does this work with nested containers? i mean where id = "container.attribute" in an option?


Need to figure out error handling.


Now with this kind of UI (unfinished) <img width="874" alt="screen shot 2017-10-06 at 22 37 18" src="https://user-images.githubusercontent.com/5412095/31297614-06c27910-aae7-11e7-9971-74dd7c89ece4.png">


GLHE_Enhancements (mitchute) - x86_64-MacOS-10.9-clang: OK (2764 of 2785 tests passed, 590 test warnings)

Messages:

 * 608 tests had: AUD diffs.
 * 17 tests had: BND diffs.
 * 16 tests had: ESO big diffs.
 * 17 tests had: Table big diffs.
 * 13 tests had: EIO diffs.
 * 2 tests had: ESO small diffs.
 * 10 tests had: ERR diffs.
 * 9 tests had: MTR big diffs.

Failures:

EnergyPlusFixture Test Summary
 * Passed: 546
 * Failed: 2

integration Test Summary
 * Passed: 610
 * Failed: 1

regression Test Summary
 * Passed: 591
 * Failed: 18

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


-Removed Google+ for iOS
-Added maxSDK version for GET_ACCOUNTS permission


Updated xml version to 1.4.8


Updated package version to 1.4.8


@graysky2

If you want the non origin PR build in the testing repo(s), you need to rebase and merge. ;)


¿Desde cuándo "alulab14" es colaborador del proyecto? :v


What's this?


Is this packet loss or something different?


PRESS


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/649e4a90-d2fc-41da-a849-1ab703f1e3a9 "deployToDedicatedChanges"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/bd40176e-127a-47d8-912c-b6f0ed382103 "catalog-api-deployToDedicatedChanges") deployed [catalog-api-deployToDedicatedChanges](https://github.com/jparra5/catalog-api-deployToDedicatedChanges/releases/tag/deploy-ibm-ys1-us-south-jparra-us.ibm.com-dev-20171006-204323 "deploy-ibm-ys1-us-south-jparra-us.ibm.com-dev-20171006-204323") to [dev](https://console.stage1.bluemix.net/apps/4dc03be1-7d5f-42c3-963f-c1cbac3fc73c?env_id=ibm:ys1:us-south "ibm:ys1:us-south:jparra@us.ibm.com:dev"), including this commit


Could you clarify what you mean by that ? I added one line (similar to Don's last commit to the release notes), I don't understand why I would "delete all the other lines"


at first run command: nmp install sqlite3 (there is sistem error in module sqlite3)


Yes. But note that some old clang versions emit incorrect code when using 128 bit types on a 32 bit platform. `HAVE_TI_MODE` is not defined in this special case.


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/649e4a90-d2fc-41da-a849-1ab703f1e3a9 "deployToDedicatedChanges"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/bd40176e-127a-47d8-912c-b6f0ed382103 "catalog-api-deployToDedicatedChanges") deployed [catalog-api-deployToDedicatedChanges](https://github.com/jparra5/catalog-api-deployToDedicatedChanges/releases/tag/deploy-ibm-ys1-us-south-jparra-us.ibm.com-qa-20171006-204622 "deploy-ibm-ys1-us-south-jparra-us.ibm.com-qa-20171006-204622") to [qa](https://console.stage1.bluemix.net/apps/436bcf5f-e620-4500-bd09-a75d8571bdac?env_id=ibm:ys1:us-south "ibm:ys1:us-south:jparra@us.ibm.com:qa"), including this commit


Definitely a big improvement on documentation! Good job. There are a few minor things that I noted, but overall, looks good. Next up is just to add some tests and error handling.


Dear Poggit user,

This is an automatic message from Poggit-CI. Poggit-CI was triggered by this commit, but failed to create builds due to the following error:

```
Resend this delivery later. This commit is triggered by user #25635727, who
has created 60 Poggit-CI builds in the past 168 hours.
```

As a result, no builds could be created from this commit. More details might be available for repo admins at [the webhook delivery response log](https://github.com/ZPlayzMCPE/Slapper/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `71cc4728-aad7-11e7-8301-80e8e4451c51`.

Shall you need any assistance, you may contact us on [on Gitter](https://gitter.im/poggit/Lobby), or more publicly, [on GitHub](https://github.com/poggit/support/issues). Commenting on this commit directly will **not** notify any Poggit staff.

Regards,
Poggit Bot (@poggit-bot)
The official Poggit automation account


Even better, you could use `instanceof`:
```java
      if (value instanceof Boolean) {
        // ...
      } else if (value instanceof Integer) {
        // ...
      } else if (value instanceof List) {
        // ...
      }
```
Great to hear you'll make a new release soon.


lol


GLHE_Enhancements (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Tests Failed (766 of 2179 tests passed, 0 test warnings)

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


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/649e4a90-d2fc-41da-a849-1ab703f1e3a9 "deployToDedicatedChanges"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/bd40176e-127a-47d8-912c-b6f0ed382103 "catalog-api-deployToDedicatedChanges") deployed [catalog-api-deployToDedicatedChanges](https://github.com/jparra5/catalog-api-deployToDedicatedChanges/releases/tag/deploy-ibm-ys1-us-south-jparra-us.ibm.com-prod-20171006-204906 "deploy-ibm-ys1-us-south-jparra-us.ibm.com-prod-20171006-204906") to [prod](https://console.stage1.bluemix.net/apps/be23cee4-91d8-4baa-ac2f-a1d2ad9d27e5?env_id=ibm:ys1:us-south "ibm:ys1:us-south:jparra@us.ibm.com:prod"), including this commit


 In case of high latency (network link latency - deployment accross WAN) between clients and servers I suspect this to be too short. But since I just gone through the file I may missunderstand this.
Shouldn't we increase this or maybe make it tunable ?


First, start by updating to the last revision of version 10.0
If problem persist, [open an issue](https://github.com/odoo/odoo/issues/new) or [submit a support ticket](https://www.odoo.com/help)  if you have a subscription


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-4812-d1oxjj: pid 4899 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171006-4812-d1oxjj  ERROR:...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-4812-d1oxjj: pid 4899 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171006-4812-d1oxjj

ERROR: /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master/quiz_spec.rb; @todo found, but puzzle can't be parsed in line #11, most probably because TODO is not followed by a puzzle marker, as this page explains: https://github.com/yegor256/pdd#how-to-format
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/app/objects/exec.rb:41:in `block in run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/app/objects/exec.rb:39:in `run'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:37:in `deploy'
/app/objects/job.rb:40:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:49:in `block in exclusive'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/app/objects/job_detached.rb:47:in `exclusive'
/app/objects/job_detached.rb:37:in `block in proceed'
/app/objects/job_detached.rb:37:in `fork'
/app/objects/job_detached.rb:37:in `proceed'
/app/0pdd.rb:336:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


HI, @Nikerabbit. Yes, it is packet loss.


No, this is correct. xorg-dmx is part of the server

www.freshports.org/x11-servers/xorg-dmx


Puzzle `234-6f82e2e2` discovered in [`quiz_spec.rb`](https://github.com/irbuch/codequiz-master/blob/master/quiz_spec.rb) and submitted as #4.


duplicate specs.  just a minor thing i spotted.


Oh, how I loathe you sometimes, Coda


It actually is not correct.
They are separate software.
http://ravenports.ironwolf.systems/catalog/bucket_F2/xorg-dmx/standard (version 1.19.3)
http://ravenports.ironwolf.systems/catalog/bucket_E7/xorg-server/dmx (version 1.1.3)
On freebsd, you call it http://www.freshports.org/x11/libdmx/

I believe there is an existing rule for it, but this commit is masking it.
Can you review it again, please?


The first test you made was nevertheless interesting. It shows some sensitivity, so there is hope for some progress here.


readme_V88 (mitchute) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


@mirkonasato I think @chrisbianca has rewritten most of the value/type stuff on his local repo and is and is pending testing before he pushes up - so I wont change too much. You're welcome  to review after it's landed, extra pair of eyes is always welcome :)


Footer widgets needed to look right on small screens, too


each of these should be it's own file.


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-5109-5xqbxq: pid 5196 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171006-5109-5xqbxq  ERROR:...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-5109-5xqbxq: pid 5196 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171006-5109-5xqbxq

ERROR: there are 2 duplicate(s) of the same puzzle: quiz_spec.rb:12-14, quiz_spec.rb:35-37, while maximum 1 duplicate is allowed
ERROR: 1 errors, see log above
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/app/objects/exec.rb:41:in `block in run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/app/objects/exec.rb:39:in `run'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:37:in `deploy'
/app/objects/job.rb:40:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:49:in `block in exclusive'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/app/objects/job_detached.rb:47:in `exclusive'
/app/objects/job_detached.rb:37:in `block in proceed'
/app/objects/job_detached.rb:37:in `fork'
/app/objects/job_detached.rb:37:in `proceed'
/app/0pdd.rb:336:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


`* 0.5f`


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on your our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues)):

> set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-5233-1ogxf7u: pid 5320 exit 255 (not zero): + set -e + set -o pipefail + cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master + pdd -q -f /tmp/pdd.xml20171006-5233-1ogxf7u ...

Please, copy and paste this stack trace to GitHub:

```
set -x;set -e;set -o pipefail;cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master && pdd -q -f /tmp/pdd.xml20171006-5233-1ogxf7u: pid 5320 exit 255 (not zero):
+ set -e
+ set -o pipefail
+ cd /tmp/0pdd20171006-4-145ifpi/irbuch/codequiz-master
+ pdd -q -f /tmp/pdd.xml20171006-5233-1ogxf7u

ERROR: there are 2 duplicate(s) of the same puzzle: quiz_spec.rb:12-14, quiz_spec.rb:35-37, while maximum 1 duplicate is allowed
ERROR: 1 errors, see log above
If you can't understand the cause of this issue or you don't know how to fix it, please submit a GitHub issue, we will try to help you: https://github.com/yegor256/pdd/issues. This tool is still in its beta version and we will appreciate your feedback. Here is where you can find more documentation: https://github.com/yegor256/pdd/blob/master/README.md.

/app/objects/exec.rb:41:in `block in run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:205:in `popen_run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/app/objects/exec.rb:39:in `run'
/app/objects/git_repo.rb:62:in `xml'
/app/objects/puzzles.rb:37:in `deploy'
/app/objects/job.rb:40:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:49:in `block in exclusive'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/app/objects/job_detached.rb:47:in `exclusive'
/app/objects/job_detached.rb:37:in `block in proceed'
/app/objects/job_detached.rb:37:in `fork'
/app/objects/job_detached.rb:37:in `proceed'
/app/0pdd.rb:336:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1091:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:923:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1955:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1726:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1499:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.3/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


ali burayı böyle yapma


awesome! thank you!

On Fri, Oct 6, 2017 at 11:12 AM, J <notifications@github.com> wrote:

> hi! i cant try it tonight. it shouldn't be that much work
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/Javier-Rotelli/typeahead.js-browserify/commit/906f3747d5783039a2387a7120ee1557fd0810ca#commitcomment-24809036>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABfJ0HlOP8yaJAF8-Qxpue0uozhekqMks5spkNdgaJpZM4PuUv9>
> .
>