@novalis @nwin I had thought that dealing with EINTR was a natural side-effect of the "read enough bytes to fill this buffer, and fail if you couldn't read them all" semantics of `read_exact`. Thinking better about it, I now noticed that it's in fact an orthogonal issue: whether or not `read_exact` returns EINTR is orthogonal to its semantics, and I can easily imagine an alternate `read_exact` which returned on EINTR.

What leads `read_exact` to have to deal with EINTR is in fact its non-idempotence. When failing, it might advance the read pointer by an unspecified amount, which means it can't be retried on EINTR. A function should only return EINTR if the read pointer hasn't been advanced at all.

One could argue that this means that `read_exact` can return EINTR if it happens on its *first* read, but that introduces a non-orthogonality in the design, where the same function would return EINTR if it happened at the beginning or retry if it happened in the middle. So the only sane semantics is "never return EINTR (always retry)".

I think I'll add a more precisely specified semantics for `read_exact`, and a section on the EINTR rationale.

@novalis , what should be done about [the current pull request](https://github.com/rust-lang/rfcs/pull/980)? I don't want to needlessly split the discussion by creating a separate pull request for this alternative RFC. Do you want to merge from mine into yours, making the pull request be again about a single method? Or should we do something else?

I think merely saying "read_full is great, but this RFC is about read_exact" would only invite the same discussion which led to read_full being in the same RFC in the first place, which is why I took some time to set them apart.

Unfortunately, I can't add your justifications for the case for read_full being stronger than I think, because I don't believe them (but feel free to add them if you take over this RFC). Being used to implement `read_exact` in the generic case is an implementation detail (and if you compare it with my implementation proposal, you can notice it would use an extra register to keep track of the number of bytes already read, while I used the "length" field of the buffer's slice instead to track the number of bytes left to read). Code duplication is an argument for it being on a reusable crate. And users not knowing `read` can do short reads (or assuming that it won't "just in this case") will happen regardless of how many extra methods are added to `Read`.


@mkortstiege i'll create a PR for it


read commit message


You are making it worse using silly while-loop here. Revert to its original version.


The statement above and this one kind of contradict each other :)


Use 120 characters per line for user readability


変換後の `ja/02_quicktour.md`

https://gist.github.com/xuwei-k/20a4525ec8a488073704


thought we can provide like company_name, website, address1 instead of individual line


damn I don't like that :( my plan was to remove all those no covers...


这就是你说的最难的技能是吧。
好，明天把“蛊惑”这个简单技能给更了。


why the parentheses?


Really? How come?


After some more investigation, I don't think that's true. For normal forms case type will be unique among datums, so a case_id of "case_id_<case_type>" will never need a suffix.


ack


BTW: Before upgrading to 0.8 you need to fix/merge cucumber/cucumber#888 and cucumber/cucumber#890


polling every 30 mins, catches changes during overruns of live events etc, changing to every 4 hrs will not catch these.


reluctant ack. 3.5 is more important than 3.2


We probably don't need to set this option here as ExchangeWebServices have a default


i have added Check box field named Include Holidays in the Leave Type Doctype.


Remove this one


Sound right


The original ExchangeWebServices defaults to 2007, but the simple library is built for 2010. Maybe I should default them both to 2010?


no julia entry?


nice, more hacks to get around badly coded drivers ;)


very good


That makes sense. Thanks.


Исправил


The very fact that a boolean property is even defined for an Image means it is True. This is the most intuitive thing to do, and is  explicitly documented for the two new properties.

Regarding non-uniformity with existing boolean properties, I could only find these other boolean properties in the documentation:
```
$ grep yes docs/interface.rst
 * **DO_SYNC=yes**
 * **IGNORE_UNATTEND=yes**
 * **EXCLUDE_ALL_TASKS=yes**
 * **EXCLUDE_TASK_<task_name>=yes**
```

Except for the obscure DO_SYNC property, the *existing* code considers all the other properties as True as long as they are not empty, and it ignores their contents.

See for example this line from commit 2ee63cce:
+if [ -n "$unattend" -a -z "$SNF_IMAGE_PROPERTY_IGNORE_UNATTEND" ]; then

So, the only incompatibility is the incompatibility between what the documentation says, which is not intuitive anyway, and what the code does. I would propose fixing the documentation instead, so it agrees with the code.

Also, as a sidenote, I propose removing the DO_SYNC property altogether. An untrusted user should *not* have a say on how an Image gets deployed to the disk and should *not* be able to choose between enabling or disabling fsync() or other similar settings during a data copy. This is for the administrator to decide.

If deployment fails without DO_SYNC but works with DO_SYNC, it is a bug of snf-image and it should be fixed. Supporting such option does not serve any purpose, but may cause problems by hiding snf-image bugs instead.

If there must be such option, I would propose including it as a debug setting in /etc/default/snf-image, similarly to the way HELPER_DEBUG works, so the administrator can set it, and no-one else.

Finally, regarding automatically setting the OFFLINE_NTFSRESIZE / OFFLINE_NTFSRESIZE_NOCHECK properties for Windows XP [I assume Windows 2000 is a typo]: Performing an offline resize with ntfsresize is potentially dangerous, and should be requested explicitly. The creator of the Image will notice immediately that resizing does not work without this property anyway, *and* we take care to emit a warning when attempting an online resize with Windows XP / Server 2003, since it will be a no-op.

So, I think this commit can be merged as is. After this patch set has been merged, I can contribute patches to fix the documentation wrt processing boolean Image properties, on a separate Pull Request.


Ок


JITLib https://github.com/supercollider-quarks/JITLibExtensions/blob/master/classes/ProxySubmix.sc


This is to test the github


@gaydenko Thank you, I'll fix now. Don't hesitate on sending a pull request it would be easier - currently working on replacing css with javascript project.


Change method name into user get_website

there is no reason to store 'None selected'.


I saw how unattend.xml works when writing the code, but it does not help to include a specific SYSPREP.INF in snf-image. Since snf-image *requires* the Image to have already been generalized via SYSPREP, we can expect SYSPREP.INF to already exist in the Image.

In fact, it would do more harm than good to overwrite the existing SYSPREP.INF; Its contents are Image-specific policy, hence they belong to the Image. There is no "sane" file that snf-image can inject without imposing specific policy. It is safe to assume that whoever ran SYSPREP in the first place, either a human who built the Image by hand, or an automated program has already included a suitable SYSPREP.INF, otherwise running SYSPREP wouldn't have worked properly.

Finally, bear in mind this commit, in contrast to the existing Windows support for Vista and higher, makes no assumption regarding the contents of SYSPREP.INF and does not need any special sections or commands; it works with the existing SYSPREP.INF and inserts whatever it needs dynamically.

So, I propose we leave this commit as is.
In the future, it would be best to improve the existing support for Windows >= Vista too, so it also makes no assumption for the contents of unattend.xml, but takes care of injecting the specific unattend.xml section(s) that snf-image needs to do its job properly.


Note that the line 113 below for trunk should be updated similarly (I'm not allowed to comment there).


fixed in 5261df2


I think that this solves the saving problem but not the heart of the problem. See my comment in #517.


@johnnykv did you forget to commit a file? Where is the BACNetServer?


move inline styles into class and in separate files under app/assets


@mbernat Why? We don't require trunk to be up to date, that is the point of this change, right?


Clients did not know who to count with


remove and use from layout.html.erb


happens also on other boxes.


It's fine to me. Thanks a lot, Fathi.


your examples didnt quite work, also not sure about shared ptr etc.  Anyway I got something working using unique_ptr on each new TimerType as well as for the contents of the vector.  Let me know how that looks.

Commit here: https://github.com/ryangribble/pvr.wmc/commit/5559d5d9d8b1f9eb3e590ebbcf4f66b9b67989f5


Use a single stats function to create and delete stats


I'm not sure how exactly you handle the Story-Id tag. But hopefully you filter out invalid values before any further processing, so no need to check for it here.


You can `return CFAutorelease(blockPointer)` here.


i see no purpose of polling every 30min - i checked a lot of logs - without any change to timers, just nice spinners every 30min if 50+ autotimers are checked.


reack


Do we need all those constants? Let's just declare the `BLOCK_NEEDS_FREE` case in addition to the one we already have.


@mbernat This is using the key as received from JIRA. I am not pre-processing it in any way...


ack


Looks good to me. Autoreleasing blocks might be unneeded when passing blocks as arguments to a call, but it solves a real issue when we need to return blocks, so it doesn't hurt to be there.


there a reason why pylint doesn't like them?


Completely forgot about that, will add a check


Just saw this - all tests will fail because of this. I'll remove it after the acking round


I am fine with that. But it will take me some time to change it...

BR,
Ck


Consider this include


s/support/understands/


Remove this interval calculation


Итак, объясняю разницу между `async` и `spawn`. У нас в качестве асинхронных функций используются генераторы, но они могут быть и синхронные, т.е. выполниться сразу безо всяких задержек. Отличие `spawn` в том, что он ВСЕГДА возвращает промис, а `async` только в том случае, если функция выполнялась асинхронно. Если функция выполнилась синхронно, то `async` выглядит так, будто мы просто вызвали нормальную функцию без него. Сделано это для увеличения скорости при синхронной инициализации. Промисы ВСЕГДА будут медленнее в синхронном коде по одной простой причине. Возьмём код:

```JS
console.log('A');
new Promise(r => { console.log('B'); r(); }).then(() => console.log('C'));
console.log('D');
```
выполняться он будет таким вот образом:
```JS
console.log('A');
console.log('B');
setTimeout(() => console.log('C'), 0);
console.log('D');
```
Т.е. по спецификации `console.log('C')` всегда будет выполняться с задержкой. Генераторы позволяют избежать этого, выполняя код без подобных задержек.

В данном случае `spawn` возвращает промис `cfgRead`, с помощью которого мы в `initScript` можем дождаться окончательной загрузки конфига при помощи конструкции `yield readCfgPromise`, если конфиг к тому времени не загрузился. Раньше скрипт просто загружал его повторно.


Wouldn't it be better to have such an exit criterion to be set by the user? Don't we have an exit criterion defined in the input file?


Related to #4.


so it doesn't yield any results after all those commits anymore?


98812224-RoomAirTemperaturePattern-5014 (rglazer2) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (652 of 652 tests passed)

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


Consider using rdtscl


Lol, no - it has lots more results - about 150+ I think


If you're checking for `None`, check for `None`. Perhaps it's stylistic, but I think you should be precise. You're not interested here in whether somebody defined `__nonzero__` on the `User` class, you're interested in whether you got `None` back.


I will but it needs casting.


ack


Note: this test is conducted by the equivalent C code output - Erlang rand module output rate is approx 1/100 of that of the C code.


couldn't you use tuples here?


and here


and so on


I would actually like to do the opposite, and it was on my mental list of things that I'd not got around to doing. The only dependency on pombola here is the choice of model. If the wordcloud function took a model as a parameter, for example, then this should immediately work fine for any model for which Elasticsearch is configured.

I would take leave this outside pombola and pass a model in.


unack


temporary fix for #7


Why is there hard-coded label? It should be localized.


I just realised if this is to be merged, you might want to export the SecondScale enum since secondsIn is exported. Whoops!
I don't know if it's worth exporting countLeapYears, countDays, countYears or countYearsAndDays. If you think they'll be used aside from internally in this unit then do annotate them with * to export.


//con


thats why I asked about it yielding results ;)


Right, I agree.


Ok, still the following two:
    BLOCK_DEALLOCATING = (0x0001), // runtime
    BLOCK_REFCOUNT_MASK = (0xfffe), // runtime
Help a lot figuring out the ref-count magic.


Would be nice if this was annotated. Did this code change at all (and if so, how much) or is it just copy&paste of the above? From a quick glance the latter, so I'll just ignore this code but if you changed something and made a mistake, it will go unnoticed because of this.


Could you use \todo instead? Then it'll show up in doxygen...


Про структуру не могу согласиться с тобой. Возможно, названия разделов не очень удачно подобраны, но сама структура такая, чтобы дать человеку некоторое понимае, что вообще делает этот пакет технологий.

В самом начале перечислены технологии и сказано одной строкой, для чего он используется. Дальше перечислены технологии ссылками.
Но чтобы человеку начать ими пользоваться одной из технологий, ему надо знать, что делать каждая из них. Поэтому сразу идет объяснение, как и для чего каждую технологию можно применить. Про результат работы технологии также рассказано в самом начале, потому что человеку важно знать, сможет он все это применить себе или нет (именно поэтому сразу же и идут очень коротки варианты использования). Потому что, если у человека в проекте нет модульной системы, то он должен знать, что он все равно сможет использовать данный пакет для сборки (это как пример), а заодно, где он сможет это использовать на клиенте или на сервере.

А в принципах (над названием действительно можно подумать) рассказаны самы важные пункты работы.


Т.е. со `spawn` мы просто можем написать `spawn(func).then(...);` и всё будет работать. Но если функция может быть синхронной и нам важна скорость, лучше написать
```JS
var res = async(func)();
if(res instanceof Promise) { // асинхроннове выполнение
    res.then(...);
} else { // синхронное выполнение
    ...
}
```


Returns None if the data is not geometric?


Yep, should we ever decide to split the logic in two:
 - marshall for a call
 - marshall on return
we will resolve this.


```
format specifies type 'char *' but the argument has type 'int'.
```
please change it to `%i`


зачем этот их? если нет текста для поиска, то это уже на серверной стороне обрабатывается


Another hard-coded label that should be localised.


same here
```
format specifies type 'char *' but the argument has type 'int'.
```
please change it to `%i`


Can we make this \todo for doxygen as well please?


Если правки повышают совместимость с ГОСТ и не ломают функциональность, то такие правки следует принять.

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


это технологии этого пакета


I think it's conventional to put generated files in MEDIA_ROOT (see http://stackoverflow.com/questions/7456817/django-when-should-i-use-media-root-or-static-root say) and Pombola already does it with thumbnails, via sorl-thumbnail. User-uploaded files should only be under `MEDIA_ROOT/file_archive` (so long as the underlying storage mechanism is written safely, which we'd hope) and only admin users can upload files. Also, it would seem strange to me to have to set up Apache to server files from a subdirectory of the backend cache, whereas we already serve files statically from `MEDIA_ROOT`.


My code snippet was actually not supposed to compile. Just scribbeled it down to give you the basic idea. Latest commit is looking good to me. unique_ptr should work fine.


 there we can change the 4 last lines (884 to 888 ) by :
if( this.m_contactListener.BeginContact( new B2Contact(fix1,fix2,touching) ) )
this.m_current_contacts.push( new B2Contact(fix1,fix2,touching)  );


Thanks! There's unfortunately some more style issues introduced with this update - the pep8 checks fail as a result:

```
$ pep8 sos
sos/plugins/ovirt.py:193:25: E201 whitespace after '['
sos/plugins/ovirt.py:194:13: E128 continuation line under-indented for visual indent
sos/plugins/ovirt.py:194:51: E202 whitespace before ']'
sos/plugins/ovirt.py:198:13: E128 continuation line under-indented for visual indent
```

If you look at the other plugins using the `protect_keys` pattern (or other multi-line lists used in sos code) they should look something like:

```python
        protect_keys = [
            "vars.password",
            "pool.default.auth.simple.password",
            "pool.default.ssl.truststore.password"
        ]
```

And the method call needs to have its continuation line indented to the opening `(`, although personally I would also break the line earlier as it means less searching around for the non-string args:

```python
            self.do_path_regex_sub("/etc/ovirt-engine/aaa/.*\.properties",
                                                    regexp, r"\1*********")
```

For really long calls you can also place the `)` on its own line (like a `[]` list) but in this case I don't think that's necessary.

You can save yourself some time by setting up git hooks that automatically run pep8 to check commits - take a look in the wiki, there are a couple of pages describing how to do it.


already part of https://github.com/xbmc/xbmc/pull/7497


I'm going to add it to the script


thanks for the help :)


Is this in the official Modtweaker @jaredlll08


что за а? куда оно?


wtf is this...


Мне кажется, что слово "требования" здесь лишнее -- достаточно "зависимость(и)".


deleting this commit for the time being - converting to tuples will kill some stuff due to asserts in which lists are checked and no time to hunt them all down right now


Не очень понимаю, что значит "пакет [..] поддерживает версию.." Здесь, видимо, надо более развернуто написать.


ok, file a bug?

2015-07-14 13:12 GMT+02:00 AbdealiJK <notifications@github.com>:

> deleting this commit for the time being - converting to tuples will kill
> some stuff due to asserts in which lists are checked and no time to hunt
> them all down right now
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/120c2364bea75eb8516e4782927a647e6c32239e#commitcomment-12153303>
> .
>


Opinion-based: I'm not sure about generic `toString`, `equals` and `toHashCode` methods. On the one hand, you build 'em, you've got to test them, on the other hand: If you don't care too much about equality/hashing, why not using some commons (ToStringBuilder, EqualsBuilder, HashCodeBuilder) and extending an abstract model? I'm running in the same dilemma, the only way out is deciding for yourself how to deal with these particular issues. See https://github.com/mp911de/CleanArchitecture for my code


reack


ตรงนี้ไม่เข้าใจความหมายของมันอ่ะ


Needs to the be plememted in offocial Modtweaker @jaredllll08


1. если метод стал приватным, то его экшен-атрибуты можно удалять
2. зачем этот метод? у тебя доступ в админку должен быть где-то типа конфига ограничен только администраторами


interesting approach, but this definitely belongs into the orchestration layer. a use case must not know about threads.


Its already part of the "use pylint bear" bug

On Tue, Jul 14, 2015 at 4:43 PM, Lasse Schuirmann <notifications@github.com>
wrote:

> ok, file a bug?
>
> 2015-07-14 13:12 GMT+02:00 AbdealiJK <notifications@github.com>:
>
> > deleting this commit for the time being - converting to tuples will kill
> > some stuff due to asserts in which lists are checked and no time to hunt
> > them all down right now
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/coala-analyzer/coala/commit/120c2364bea75eb8516e4782927a647e6c32239e#commitcomment-12153303
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/120c2364bea75eb8516e4782927a647e6c32239e#commitcomment-12153317>
> .
>


Looks correct


Related task #1694


Should be done one month ago


Why suffixing it with `UseCase`? `GetUserDetails` is the best name to describe what you're doing


"в отдельных файлах [..] в директориях блоков"
Такие конструкции тяжело воспринимаются из-за двойной вложенности. В итоге не понимаешь: в директориях блоков хранятся шаблоны, отдельные файлы или и то и другое.


yes you're right, I forgot MIPS is three operands instead of x86 so yes you may need to do the else part too. Let me fix it.


sa pete srx


You are assuming the application program will always be using the CCM RAM for the initial stack. This may not be the case. I'd prefer to see:

uint32_t value = block[0] & 0xFFFC0000 ;
if ( (value != 0x10000000) && ( value != 0x20000000) )
{
  return 0;
}
to allow for both possibilities.

In passing, I did recommend the bootloader should be compiled from its own (private) source files to ensure there was no possibility of linking with the main application code, or the bootloader unexpectedly changing as a result of a change to the main application.


Similar point as the generic `toString` etc. You're using DI at use case level. While this may work good, it's a mix of concerns and belongs into the orchestration level


c'est très emacs~


oops, sorry - no reack. needs to be reviewed


`exit 0` will **quit** the current shell. and `return $?` is the default behaviour of `function()`, which is the case of `rm -f`. it always returns 0.


reack


Concatenating strings to translate makes it sometimes hard for translators, consider using format string instead.


Good, more functional = a better world ;-) (if these changes pass tests)


Так все же: это прямо пакет что-то собирает или сборку обеспечивают технологии, которые пакетом распространяются?
Выше "bh.js" выделен


Can you please use relative paths and the certificates that are in https://github.com/PritamUpadhyay/mosca/tree/patch-1/test/secure?

So that this works out of the box.


:P

Dat Ene Programmer


return Index()


       创建一个新窗口，用于计算次级线圈的相关参数-->
               寄生电容
               次级 箍数


Зачем это предложение? Если прямо хочется подчеркнуть, что разные технологии делают одно и то же, но разными способами, то это можно написать во вводной.


You need to fork the repository, update the buildpack.txt and build your own docker image afterwards.


Oh, apparently it's even [in PEP8](https://www.python.org/dev/peps/pep-0008/#programming-recommendations):

> Comparisons to singletons like None should always be done with is or is not , never the equality operators.
>
> Also, beware of writing if x when you really mean if x is not None -- e.g. when testing whether a variable or argument that defaults to None was set to some other value. The other value might have a type (such as a container) that could be false in a boolean context!


Oh. In that case it's really unnecessary, isn't it? JIRA keys are always XXX-123.


a lower value isn't possible?


but does C++ will display this expression: if (x < 0) x = -x else **x = x**?

or it is smart enough to display: if (x < 0) x = -x? That is, smart enough to nullify an identity expression?


```sh
ceph-monstore-tool $store_path get osdmap -- \
                        $epoch -o $osdmap > /dev/null || exit
```
would suffice. but i think you meant `return` but not `exit`, right ?


Maybe this should be changed


@hvelarde I thought I took out this id and added the slideshow-container class instead to share the same styles and javascript with the tile.. I don't understand why this test is passing now..


Зачем здесь перечислять эти технологии? А если завтра их станет три?
Знак вопроса, если мы говорим о расширении, -- лишний.  Если хочется показать, что перед этим может быть "любое название" -- я бы рекомендовал звездочку поставить. Но мне кажется и это избыточным. Здесь и далее по тексту я бы писал "bh.js-файл" и т.п.


Oh, I see. I thought that the `CheckOrCreateTrackingBranch`, which is used both times, tries to update the repo.


Я просто перенёс установки конфига из `readCfg` в `aib.init`. И там есть такое ветвление:
`if(aib.tiny && !aib._8ch) {`
Вот этотт `null` и реализует подобное ветвление не позволяя выполниться `init` функции тинибоарда.


`reportLoopCount` records the number of dynamic loops within a methods like it does the number of times the method is called, in order to decide when to compile.

`reportLoopCount` is out-dated though - we should really be using a `LoopNode` to allow for OSR.

A pack expression is a linear sequence of nodes, like a sequence node in Ruby. In Ruby we always explode the loop over this sequence, in order to get linear code, rather than a loop. However, unlike most Ruby code, pack expressions can be very large, so we can't explode all of them. This code explodes small loops, but not big ones.

I should pull that constant `4` into an option.


если правильно понимаю - это экшен для реализации поиска. почему у него сигнатура иная, чем у [Get]Index?


is it this necessary to specify naked in the declaration? (instead of at the definition)


The block of code for looping through sections, checking if section enabled and calling `execute_section()` which is there in coala_ci, coala and DbusDocument has about 15 lines


В `npm` начиная с версии `3.0.0` такие зависимости не будут ставиться автоматически, их надо будет прописать руками. Поэтому слово «Требования» подходит лучше.


база внутри вью-модели - фу. потом преобразуем


Thats no false positive :)

2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:

> The block of code for looping through sections, checking if section
> enabled and calling execute_section() which is there in coala_ci, coala
> and DbusDocument has about 15 lines
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553>
> .
>


- could also bail out if `local last_osdmap_epoch=$(osdmap_get $store_path "/osdmap/epoch")` fails, instead have a dedicated line for detecting a running monitor ?
- could move `echo "error accessing mon store at '$store_path'"` as part of error handling?


Sorry I don't get it. Also I don't understand the comment here.
If I look the term up in the ontology:
```
[Term]
id: MS:1001494
name: no threshold
def: "In case no threshold was used." [PSI:PI]
is_a: MS:1002482 ! statistical threshold
```
The comment should at least say something like: // check if no threshold (MS:1001494) was used


надо запомнить в переменную запрос вплоть до Order и использовать для TotalSpare


Let's implement the method.

And.. controller specs are all green:

To the top of the pyramid! The only failing spec is the first one, the feature spec:

It's funny how high-level spec guides us through all the development process and serves like a final quality control. It's important that it encourages us to write tests on each level of the pyramid.

Let's make it [all green finally](https://github.com/liptonshmidt/alchemy/commit/ce8bd7c4605d0769cc5accb5af1a52b30fbe66e0)


Also Changes to site look and feel


seems to be tabs instead of spaces.


tell me a number to put.

On Tue, Jul 14, 2015 at 4:55 PM, Lasse Schuirmann <notifications@github.com>
wrote:

> Thats no false positive :)
>
> 2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:
>
> > The block of code for looping through sections, checking if section
> > enabled and calling execute_section() which is there in coala_ci, coala
> > and DbusDocument has about 15 lines
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153586>
> .
>


Will this require answering yes or no? Or does the script just run?


I'm not sure we should specify the clobbered registers here, we don't want the compiler to add any stacking operations before our code, it might be enough to only use the basic inline asm syntax (without any `: : :`)


I don't get the comment here. It should at least state what MS:1002482 means
e.g.
```
MS:1002482 ! statistical threshold
```


is there a reason for specifying the fields? leaving out completely will make it default to all fields.


Zusätzlich:
Neue Funktion GetDefaultPrinter() - gibt Standarddrucker aus
Neue Funktion NavUCCall() - NavigateUC Anruf Initialisierung aus Navision heraus
Verbesserungen am PDFCreator Verhalten
Verbesserungen an der Funktion SearchFolderBuildtoOrder()


looks like ```backgroundservice``` was not camelcased?


the lowest one thats no false positive, does 5 work?

2015-07-14 13:26 GMT+02:00 AbdealiJK <notifications@github.com>:

> tell me a number to put.
>
> On Tue, Jul 14, 2015 at 4:55 PM, Lasse Schuirmann <
> notifications@github.com>
> wrote:
>
> > Thats no false positive :)
> >
> > 2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:
> >
> > > The block of code for looping through sections, checking if section
> > > enabled and calling execute_section() which is there in coala_ci, coala
> > > and DbusDocument has about 15 lines
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153586
> >
>
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153601>
> .
>


or even 4?

2015-07-14 13:27 GMT+02:00 Lasse Schuirmann <lasse.schuirmann@gmail.com>:

> the lowest one thats no false positive, does 5 work?
>
> 2015-07-14 13:26 GMT+02:00 AbdealiJK <notifications@github.com>:
>
>> tell me a number to put.
>>
>> On Tue, Jul 14, 2015 at 4:55 PM, Lasse Schuirmann <
>> notifications@github.com>
>> wrote:
>>
>> > Thats no false positive :)
>> >
>> > 2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:
>> >
>> > > The block of code for looping through sections, checking if section
>> > > enabled and calling execute_section() which is there in coala_ci,
>> coala
>> > > and DbusDocument has about 15 lines
>> > >
>> > > —
>> > > Reply to this email directly or view it on GitHub
>> > > <
>> >
>> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553
>> > >
>> > > .
>> > >
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153586
>> >
>>
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153601>
>> .
>>
>
>


Very nice. Just a small detail. It should handle the case when update was never run and the file isn't created. An example:
```bash
stat -c %y /var/lib/apt/periodic/update-success-stampede | cut -d" " -f1
stat: cannot stat ‘/var/lib/apt/periodic/update-success-stampede’: No such file or directory
```
In that case there should be a check if the file exists
```bash
if locate /var/lib/apt/periodic/update-success-stamp &>/dev/null; then
     echo "gets info about the last update"
else
     echo "never updated before"
fi
```
That was a "small" typo I made lol
Thanks for fixing


And the lines after that in the for loop are different for each (the
handling of result) ... so, I dont see how that's going to be solved.

I think I'll leave the default value for now ?

On Tue, Jul 14, 2015 at 4:56 PM, Abdeali Kothari <abdealikothari@gmail.com>
wrote:

> tell me a number to put.
>
> On Tue, Jul 14, 2015 at 4:55 PM, Lasse Schuirmann <
> notifications@github.com> wrote:
>
>> Thats no false positive :)
>>
>> 2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:
>>
>> > The block of code for looping through sections, checking if section
>> > enabled and calling execute_section() which is there in coala_ci, coala
>> > and DbusDocument has about 15 lines
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153586>
>> .
>>
>
>


This message makes it sound like the server rejected you. Can you reword it?


return View("Edit", new SparePart()) <-> return Edit(new SparePart())


Do you guys think we need to do email twice too? People are less likely to make mistakes there - it's a visual field where you can just look to see if it's correct


@spastorino, @jmbejar we already guard the insertion of web-console on non HTML compatible responses, so we can't show it on a JSON page unless the content type allows it.


@jluis Surely you meant irEland :)


This should actually have a non-existing place id as a query param.


```
==coalib.coala:67
==coalib.coala_ci:54
    except SystemExit as exception:
        exitcode = exception.code
    except Exception as exception:  # pylint: disable=broad-except
        log_printer.log_exception(_("An unknown error occurred.") + " " +
                                  StringConstants.THIS_IS_A_BUG + " " +
                                  _("During execution of coala an exception
"
                                  "was raised. This should never happen.
When "
                                  "asked for, the following information may
"
                                  "help investigating:"),
                                  exception)
        exitcode = 255

    return exitcode (duplicate-code)
R:  1, 0: Similar lines in 2 files
==coalib.coala:41
==coalib.coala_ci:33
        for section_name in sections:
            section = sections[section_name]
            if not section.is_enabled(targets):
                continue

            interactor.begin_section(section)
            results = execute_section(
                section=section,
                global_bear_list=global_bears[section_name],
                local_bear_list=local_bears[section_name],
                print_results=interactor.print_results,
                log_printer=log_printer)
            yielded_results = yielded_results or results[0] (duplicate-code)
R:  1, 0: Similar lines in 2 files
==coalib.coala:28
==coalib.coala_ci:26
        yielded_results = False
        (sections,
         local_bears,
         global_bears,
         targets) = gather_configuration(interactor.acquire_settings,
                                         log_printer)
 (duplicate-code)
R:  1, 0: Similar lines in 3 files
==coalib.coala:47
==coalib.coala_ci:39
==coalib.output.dbus.DbusDocument:115
            results = execute_section(
                section=section,
                global_bear_list=global_bears[section_name],
                local_bear_list=local_bears[section_name],
                print_results=interactor.print_results,
                log_printer=log_printer) (duplicate-code)
```

Are the similarities for 4

On Tue, Jul 14, 2015 at 4:57 PM, Abdeali Kothari <abdealikothari@gmail.com>
wrote:

> And the lines after that in the for loop are different for each (the
> handling of result) ... so, I dont see how that's going to be solved.
>
> I think I'll leave the default value for now ?
>
>
> On Tue, Jul 14, 2015 at 4:56 PM, Abdeali Kothari <abdealikothari@gmail.com
> > wrote:
>
>> tell me a number to put.
>>
>> On Tue, Jul 14, 2015 at 4:55 PM, Lasse Schuirmann <
>> notifications@github.com> wrote:
>>
>>> Thats no false positive :)
>>>
>>> 2015-07-14 13:24 GMT+02:00 AbdealiJK <notifications@github.com>:
>>>
>>> > The block of code for looping through sections, checking if section
>>> > enabled and calling execute_section() which is there in coala_ci, coala
>>> > and DbusDocument has about 15 lines
>>> >
>>> > —
>>> > Reply to this email directly or view it on GitHub
>>> > <
>>> https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153553
>>> >
>>> > .
>>> >
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/coala-analyzer/coala/commit/bb43ea421868c2e44180321a9def626f05c2a8ea#commitcomment-12153586>
>>> .
>>>
>>
>>
>


it should probably return a 400 Bad Request


Ah thanks, `reportLoopCount` is different than I thought, It's not connected with the `@ExplodeLoop` optimisation.


It's pretty good now :)


is it possible to do the same as for ```MainActivity``` here?

Means to make it

```Java
 if (display.getRotation() == Surface.ROTATION_0 || display.getRotation() == Surface.ROTATION_90)
```


Seems this concept is missing in OpenMS. If we filter an entry it get's removed from the structure.
What I could imagine is to use a meta value that encodes if an existing entry will be reported (e.g. in mzTab).
But then I would not call it pass_threshold (see below). Any thoughts?


still lack of spaces here


Из контекста непонятно идет ли речь о вариантах использованиях технологий или результатов работы технологий.


I don't think the `humanize` is needed here. I think `service_status.name` returns a value provided by the user. Doesn't it?


Good question... I didn't realise that one could optimize it that way. Give it a try. :-)
I implemented it purely with Sweetman's definition of the corresponding C-code.

Btw did you check 'redir'?


1) There should be no spinners during polling (and I never noticed that on any of my boxes)
2) See your logs when an event EPG-time has actually changed. Of course this is very much related to the EPG-source you use (e.g. OpenTV is actually very accurate, and a daily XMLTV import of course isn't).


为什么这样改？大致测试了一下
```clojure
user> (= (list (inc 1)) [(inc 1)])
;; true
```


please, do not start method names from capital later, it's for class names


ack


spaces stuff turns to be completely wrong here


This might get too expensive, with too many DOM reads and writes, specially for devs who are always resizing browsers. If it really is necessary, I suggest throttling could be applied "using requestAnimationFrame, setTimeout or customEvent", see: https://developer.mozilla.org/en-US/docs/Web/Events/resize


Мы еще не рассказали пользователю, как компилить этот файл, а уже рассказываем, как его подключать. Здесь. во вводной (которая называется сейчас "Использование") можно (и нужно) оставить ссылки на варианты использования, но сам текст перенести в конец.


again, wrong spacing


It's because of the Place and User seriealizers, when I left it empty, it serialized the foreign key (encapsulated objects) as single digit ids for some reason. So I had to explicitly define "place" and "user" to serialize them properly which made it work but obviously had to also list the rest of the fields as well.


Should work- there's no chance of that result being undefined

On July 14, 2015 4:52:01 AM EDT, sebworks <notifications@github.com> wrote:
>Will `{{ (classes or '') }}` work?
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/rosskarchner/cfgov-refresh/commit/eef7d121f9f25d45f0ffd921fae4519f72340642#commitcomment-12150781

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


@DidUknowiPwn you need to hook!


Add custom fonts for OSX and Linux, also added entry in `face-font-rescale-alist`.
modified kbd shortcut and rewrite in a more graceful way.


还是有问题，不过问题少了，这样子可以不用把 react-router 放到库 demo.js 里去，加快构建


is "1" correct? or should it be "true"?


Was released to npm but not tagged here.


в том и дело, что bh.js  — это исходные файлы, а не результат. Знак вопроса использую, потому что он используется в коде.

Не поняла твой комментарий "Про модульную систему дальше что-то пишется, но здесь вообще не понять, к чему она относится."


Some useful relevant links:

* [JSON Schema](http://json-schema.org/)
* [CCAV API](http://ccav.terranova.org.au/apidocs/#http://ccav.terranova.org.au/api/) An API I constructed a couple of years ago!


another uninformed comment from my side ;)
the uids are pretty large - are these are compatible to 32bit systems?


Added input files and the corresponding output


@mbernat No, it just returns `ErrRefNotInSync` when the branch is not up to date...


@novalis @nwin Just posted a new version with my explanations about EINTR (and more), could you take a look?


I am not sure to understand.
The `Thread#run` should wake up the thread as soon as it can take the lock, right?
Then if `Thread#run` is called between the `unlock` and `sleep` lines it is not a problem, we'll just do with the check before the sleep (in the fixed version on master).


no .. different orientation have different camera angle ...


Added set of new input files


@mbernat As mentioned somewhere above, I just moved it here under `issueTracker` so that I don't need to handle API client instantiation all the time... So no, no need to check deeply really...


If you `return false` from `cancelDrag` (or do `e.stopPropagation()` and add `e` as the first argument) does it remove the need for these functions?


I can see your point. On the other hand our [style guide](https://google-styleguide.googlecode.com/svn/trunk/pyguide.html?showone=True/False_evaluations#True/False_evaluations) says _Use the "implicit" false if at all possible_, and being aware of other values I don't expect that `user` can be set to any falsy value besides `None`. Also if someone did change `get_by_username()` to return, say, `False` or an empty list when no user(s) were found this code would actually continue working as desired (whereas `is None` would crash).


By specifying the function as naked, the compiler already doesn't produce any entry/exit code, so why would specifying clobber registers change that?
I'd say that they don't hurt and eanble the compiler to (maybe) do better optimization.


Отрефакторь на использование объектов


You should really test before commiting :)


Evita adicionar ao controle de versão estes arquivos em branco.


The query params are made further down in the tests:
```response = self.client.get(self.valid_url, {'place': self.valid_place.uuid})```

didn't know how to add it in the reverse api and couldn't find a way with my limited internet at the moment :S


Como isto é algo que aparece em **qualquer** página do sistema, o ideal é tu colocar no `layout`.


great ;)


詳細よりは内容というイメージなので
detailよりcontentの方が良いかもです


I can't test cookies locally :c


but isn't ```Surface.ROTATION_0``` actually equals to 0? ROTATION_180 to 180 and so on?


Anyway, doesn't matter. I was just wondering why it's there.


全体的に外部キー制約は使用しない方針でしょうか？


Found the problem - another rogue version of functions.php sitting in the /var/www/ directory so all the function calls were being made to there apparently.
Thanks for your help.
Dave


Por que tu deletou esta migração?

Sem isso, a tua funcionalidade não ter a tabela necessária criada em produção quando o deploy for feito, por exemplo. Nós só deletamos as migrações depois de muito tempo que ela foi criada, quando deletamos.


sa pete srx


@enumag you're probably right, this was more of a hotfix.


ta bien fet denleve le *
mdrrrrrr


OK, is this something you can fix, Nick, or do I need to do a different commit?

Timothy Lang
Research AST, Atmospheric Measurements
NASA Marshall Space Flight Center (ZP11)
Huntsville, AL 35812
(256) 961-7861
timothy.j.lang@nasa.gov

From: Anderson <notifications@github.com<mailto:notifications@github.com>>
Reply-To: nguy/artview <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Monday, July 13, 2015 at 5:31 PM
To: nguy/artview <artview@noreply.github.com<mailto:artview@noreply.github.com>>
Cc: Timothy Lang <timothy.j.lang@nasa.gov<mailto:timothy.j.lang@nasa.gov>>
Subject: Re: [artview] pep8 compliance (e54b540)

artview must be imported after this 3 lines (not before), otherwise it will fail if using in-place (not install). This lines are actually adding the folder to the import path

—
Reply to this email directly or view it on GitHub<https://github.com/nguy/artview/commit/e54b54010e83434451257b985a1f2aac0be7bcf8#commitcomment-12144301>.


https://github.com/oe-alliance/enigma2-plugins/commit/f22c474d6c5c59dc22cca6a278a68ad00d383c4e

only changed for openmips and openatv. vix stays as is.


sa pete


Да, неочевидно, однако. А я плевался и голову ломал.
Ну это хорошо, пока в init тиниборда нет ничего, кроме Cfg.fileThumb = 0. А если там появится нужный для всех доменов код, придется что-то менять.


я выше пишу (предыдущее предложение) "Способы его (результата) использования зависят от наличия модульной системы и ее типа."
ниже идет список возможных вариантов использования. Мне кажется, что это логично: такие-то технологии используются для получения вот такого файла. Как применять файл, зависит от наличия в проекте модульной системы. А вот варианты применения этого файла (с разными кейсами с/без модульной системой).
Это все в пределах одного раздела. Если бы это был новый раздел, то, наверное, можно было бы подумать, что речь о вариантах использования технологий.


ui


посмотрел пример в конце, теперь понял. Вывод: ясности в изложении не хватает.
выше есть вот такое предложение:
"Пакет `enb-bh` собирает отдельные файлы с шаблонами (bh.js) в один общий файл с помощью одной из следующих технологий:"
Ровно здесь (после словосочетания "в один общий файл") нужно в скобках указать (?.bh.js). Тогда это противопоставление (что было -- что стало) будет сразу видно и понятно.


ce write et impresionan


nn


jcapt kedal srx


woaw


https://github.com/oe-alliance/enigma2-plugins/commit/e67bb44af7d66c12a0124f91a5c50cd951441a8c

only openatv and openmips., vix stays as is.


ta rien ecri srx


Test json/xml


(mentioning https://github.com/rust-lang/rfcs/pull/980 here so this commit shows in the timeline there)


Why not? Use this to add them https://chrome.google.com/webstore/detail/editthiscookie/fngmhnnpilhplaeedifhccceomclgfbg?hl=en


Our task is to make feature spec green as soon as possible.

Let's do it and run our specs:
<img width="626" alt="14" src="https://cloud.githubusercontent.com/assets/5196926/8672218/f89d322e-2a34-11e5-8c40-2bf6da465acb.png">
Cool! All tests are green.

However, it seems that we violated one of Sandi Metz' rules here: "Controllers can instantiate only one object". So, we're are ready for the last but not least step of feature development: [Refactoring](https://github.com/liptonshmidt/alchemy/commit/57aa493e67eb7fda5fae69a3e43f53af0775f414).


There is a great java library for this type of logic http://modelmapper.org/


ses mieu


Yes, it's really only for edge cases. Rarely do people resize their browser window a lot. I'll use the setTimeout/clearTimeout method to throttle it though.


If I want Transmission downloads created with a umask of 022 how do I do this?


My bad, you are right, get parameters are not defined in reverse, only if the url would contain variables.
This case the `self.non_existent_url` variable is not needed and `self.valid_url` should be renamed to `self.url`. It is not the url that will be invalid but the GET parameter.

Line 28 should look like:
`response = self.client.get(self.url, {'place': 'invalid place uuid'})`.


Maybe I misunderstand the code. I just want to make sure again that |sizeof(rec->name)| at line 313 is correct when calling |strncpy|. The length should be equal to return value of |lookup_service_name_by_uuid16|, at the time, rec->name = '\0' by default.


コメントも削除フラグがあっても良いのでは？


Hi Bernd,
Now it compiles, but I got a Segmentation fault (core dumped)...
I don't really know how to debug : I will search, but any help would be appreciated !


As mensagens de commit devem ser claras e dizer o que foi incorporado ao produto, por exemplo: "Possibilita visualizar listas".

Outro ponto é que a mensagem do teu commit fala que foi uma modificação relacionada a login/signin ("making some changes into login/signin features"), mas na verdade as modificações manipulam recursos relacionados à lista.


Had a few users reg to my site with the wrong mail. It means they can't get the confirmation token.


MIPS load/store:  offset(base) --> *(base + offset)

it gave : offset(base + reg) --> *(base + reg + offset) <---- but what 'reg' is !?

if you look at *operand.mem* and *operand.reg*, they are member in a *union* so they share the same placeholder:
```
// Instruction operand
typedef struct cs_mips_op {
	mips_op_type type;	// operand type
	union {
		unsigned int reg;	// register value for REG operand
		int64_t imm;		// immediate value for IMM operand
		mips_op_mem mem;	// base/index/scale/disp value for MEM operand
	};
} cs_mips_op;
```
so *mem* and *reg* are mutually exclusive.


Спасибо. Если честно, я до сих пор не понимаю многих es6 вещей, которые ты делаешь.


Well done. I wonder how significant the movecount is?


Выше пишем "В Node.js скомпилированный `?.bh.js`-файл подключается как модуль в формате [CommonJS](http://www.commonjs.org/)." -- фразы нужно привести к одному знаменателю (формулировка, приведенная здесь, лаконичнее, за основу лучше взять ее).


Это обсуждалось с заказчиком, что использование пишем до описания технологий. Мы даем общее представление о работе пакета. Детали реализации каждой технологии описаны в соответствующем разделе. Пользователь работает только с конечным файлом.
cc @blond


I think what we want is the sleep call to release the lock and put the thread to sleep atomically so it should not allow `run` to be called in between which would result in run call to be lost and the thread would remain sleeping. I am not sure what you mean by "we'll just do with the check before the sleep (in the fixed version on master)."


serial型じゃなくて良い？


Да я сам в эти асинхронные дела не сразу впёр.


please tell me the line number


同上でserial型じゃなくて良い？


I googled a bit and it seems like it is.

1. `Function attributes are introduced by the __attribute__ keyword on a declaration, followed by [...]`
2. `Note that __attribute__ applies to function declarations, not definitions, and we're not sure why this is.`

[1] https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html
[2] http://www.unixwiz.net/techtips/gnu-c-attributes.html


自分はtextとvarcharの使い分けとして
文字数が多いものはtext
文字数の上限が想定されるものはvarcharだと考えているのですがいかがでしょう？


This doesn't seem right. Since `data.teachers` is an array, why don't you use just map?


Usa as variáveis em inglês. :v:


63: ```c= getApplicationContext();```


Esta modificação deve vir sempre junto com o migrate que gerou ela. :wink:

Neste aqui: https://github.com/jlgm/Rails-todo-list/commit/a94c43dd9ac2761ee8df97fdb6ac26b58d04267d


Yes, I did : same issue


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


Something weird with indent here (tabs?) -- I fixed it after the merge though.


@adamcooke I've done this as service statuses can be added by the user in the admin? I'm a freak when it comes to keeping things neat and consistent.


It didn't worked?


優先度的なカラムでしょうか？
そうだとしたらorder byで並び替える可能性があると思うのでInteger型ではいかがでしょう？


O banco não deve ser adicionado ao controle de versão. :)

`db/development.sqlite3`


これでどう　[Dealing with line endings](https://help.github.com/articles/dealing-with-line-endings/)

    # Declare files that will always have CRLF line endings on checkout.
    *.sln text eol=crlf


ah, hmm... I stole that from the X86 analyzer actually :-/


message


added a file?!? really?


Получается глубокий уровень вложенности заголовков, теряется зависимость от заголовка предыдущего уровня.
Я бы попробовал привести это, например, в таблицах. Возможно, какие-то еще варианты. Заголовки здесь -- очень "жирно" для такого объема текста.


Звязок між Тютором та Екшином - один до багатьох, тобто в моделі Екшин має бути поле ФоренКі тютор


Imports in settings should be reduced to minimum, so I changed this to rather use ancestor(2) then import 2 new modules. To be honest, considering we added booktype as Django app this might not even be needed for booktype but I would rather leave it.


Nice, thank you. I knew there must have been a better way to deal with that.


Slightly queasy about moving UI-like code into BrowserProfile. Otherwise good.


Это инициализация поиска, там руками вбивается строка поиска, и предается индексу.


Я не понимаю сочетание "шаблон как этап".


My concern is that with humanize, it uppercases the first letter and lower cases everything else. So if you had a status called "All OK" it would be changed to "All ok".


Нет, я конечно в общих чертах ориентируюсь в нашем поделии. И все процессы, основанные на ванильном js я знаю прекрасно. Но вот таких "черных асинхронных ящиков" становится слишком много, и это делает меня очень нервничать, так как теряю контроль над происходящим.


Incorrect view of TableView on some devices. Does not support iOS 6. Please make corrections.


Можно добавить функцию `aib.fixCfg` и использовать её вместо `init`.


Собирает сам ENB, но с помощью технологий, которые распространяются этим пакетом.


we should not add returned text directly from method to temperatureLabel. Felt that its better if we first get a string variable then show it as text. Added an extra line so that it makes code more readable.


yup that's a fair point, will clean that up


Зато это удобно. Всегда есть возможность сослаться именно на этот вариант использования и дать на него прямую ссылку — это причина использования заголовков даже для мелких размеров


`<th>` é usado para o header da tabela, o conteúdo deve ser colocado no `<td>`. :+1:

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/table


Hmm, no this should be okay because legacy.topic_tools_settings is a part of the settings themselves so it can't load from django.conf.settings


98812224-RoomAirTemperaturePattern-5014 (rglazer2) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1169 of 1169 tests passed)

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


Ooops, It keeps happening on my computer. Am I becoming unstable?

Starting
/home/graeme/git/mandelbulber2/mandelbulber2/build-mandelbulber-Desktop-Debug/mandelbulber2...

Log file name: /home/graeme/.mandelbulber_log.txt

Detected 8 CPUs

Default data directory: /home/graeme/.mandelbulber/

/home/graeme/git/mandelbulber2/mandelbulber2/build-mandelbulber-Desktop-Debug/mandelbulber2
exited with code 0

Starting
/home/graeme/git/mandelbulber2/mandelbulber2/build-mandelbulber-Desktop-Debug/mandelbulber2...

Log file name: /home/graeme/.mandelbulber_log.txt

Detected 8 CPUs

Default data directory: /home/graeme/.mandelbulber/

Warning: slotLogLineEditChanged() error: value from "logedit_DE_factor" is
not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from "logedit_DE_factor" is
not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from
"logedit_camera_distance_to_target" is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

/home/graeme/git/mandelbulber2/mandelbulber2/build-mandelbulber-Desktop-Debug/mandelbulber2
exited with code 0

Starting
/home/graeme/git/mandelbulber2/mandelbulber2/build-mandelbulber-Desktop-Debug/mandelbulber2...

Log file name: /home/graeme/.mandelbulber_log.txt

Detected 8 CPUs

Default data directory: /home/graeme/.mandelbulber/

Warning: slotLogLineEditChanged() error: value from "logedit_flight_speed"
is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from
"logedit_formula_scale_1" is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from
"logedit_formula_scale_2" is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from
"logedit_formula_scale_3" is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

Warning: slotLogLineEditChanged() error: value from
"logedit_formula_scale_4" is not greater zero

(../src/render_window.cpp:144, void
RenderWindow::slotLogLineEditChanged(const QString&))

On Tue, Jul 14, 2015 at 8:42 PM, carbuncle grim <mclarekin@gmail.com> wrote:

> Closed QT Creator, reloaded and now the problems gone away. So will alert
> you if it happens again.
>
> Cheers, G
>
> On Tue, Jul 14, 2015 at 6:33 PM, carbuncle grim <mclarekin@gmail.com>
> wrote:
>
>> None in my ubuntu set up, probably some in my windows drives. If that
>> makes any sense. I only run Mandelbulber2 in QT Creator.
>>
>> On Tue, Jul 14, 2015 at 5:40 PM, Sebastian Jennen <
>> notifications@github.com> wrote:
>>
>>> Can you attach your mandelbulber.INI and auto.fract (if present)?
>>> These ones are under ...username/.mandelbulber
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/buddhi1980/mandelbulber2/commit/9620b313cfc8011a7f9d5620dcc5e9f395c9bbca#commitcomment-12148284>
>>> .
>>>
>>
>>
>


But there's another "derived setting" happening below.


I think this doesn't need type-param `P`, I think it can be `<T as AuthorizeSession>::Permissions`?


have a lot of:
```
[Warning] class nc::core::ir::MemoryLocation __cdecl nc::core::ir::dflow::DataflowAnalyzer::computeMemoryLocation::<lambda_453acc5f7895062e6691988f88cde051>::operator ()(void) const: Term kind 0 cannot have a memory location.
```

and a popup dialog due to a "abort() has been called".


Doh...


This is still dynamic?


Что такое "финальный ?.html файл"? Выше все эти разделы были объединены под заголовком, суть которого сводится к "как использовать итоговый файл ?.bh.js". Здесь с места в карьер начинаем про "сборку финального ?.html-файла".


Closed Visual Studio Online Task [vso#4345](https://azurecom.visualstudio.com/DefaultCollection/ACOM/_workitems#_a=edit&id=4345): 'This is a test usersnap task submission'

VSO State: Done


After discussing with @lewistaylor, he thought that we should just return an empty list. That ended up being an easier implementation and the default behaviour.

I can look at returning a bad request if we think that's better ? But I guess if my thinking is that if you search for queues for a place that doesn't exist, I'd expect just an empty list normally. What are your thoughts as to why it should return a bad request?


Event Deligation 기법을 활용하여 개선하였습니다(http://git.io/vmY9k)

이 기능의 요구사항은 "하나의 li element를 삭제한다" 인데
제가 생각할때는 요구사항이 간단하므로
removeTodo 함수 하나의 실행이 종료되었을때
하나의 작업이 완료되었으면 하는 바람이 있었습니다.

웬지 Event delegation을 이용하면 하나의 작업이 여러곳으로 분산되는것 같다는 느낌이 들어
이 경우에는 event delegation을 사용하고 싶지 않았었는데
교수님께서 유사한 상황을 여러개 설명해 주셔서 잘 이해하였습니다~


dive into them? (the neighborhood methods?)


Кажется, что это важная информация, поэтому вынесла ее отдельным предложением, чтобы обратить внимание.


I think `Option<MyUser>` would allow coherence to work for the above without wrapping a newtype?


we can add a link to the wikipedia article of LCC


Will fix the indentation


There's a typo in the commit name.


This is cancer.


leave it as is for now can change later.


highlight the method method names, i.e. `reduceOnEdges`


Ah yes. I can remove humanize if you wish. I guess in the context of where it is shown, the text could in fact all be lowercase too.


No, seriously. Why are you specifying a type in the first place? It's already going to be a string in the first place.


Might be good to have the example show something *slightly* more complicated that boolean just so users can understand the potential? E.g. if we just have `enum Permissions { Admin, User, None }`


不用更新的。。。
小版本自动更新


здесь нужно привести примеры библиотек и то, как это может отразиться на работе (что у нас при это расширится, какие возможности появятся). Буквально на одно-два предложения.


As you remember, we've decided to get rid of multiple instance variables in the controller.

It seems that Facade pattern here will give us exactly what we want: we'll get single complex object that will handle all the logic for serving materials: both completed and active.

Implementing facade leads to new tests; however, we feel secure while making those changes because we already have solid test coverage.

When refactoring is completed and all specs are green we are ready to squash all the commits in one, write meaningful commit message and open a pull request.

That's it! Our TDD/BDD tour is now finished. Thanks for watching!
![409bd928-d3c2-11e4-9dc3-113d2bbcab8b](https://cloud.githubusercontent.com/assets/5196926/8672694/81d55c0c-2a39-11e5-8fb9-2ce75b426d4f.png)

You can find more Ruby/Rails/Testing stuff in my [blog](https://medium.com/@liptonrb),
follow me on [Twitter](https://twitter.com/liptonrb),
or drop me a line on liptonshmidt@gmail.com

See you!

[to the first step](https://github.com/liptonshmidt/alchemy/commit/fdc58de19e8bbfaebc4c130f348fd9bef5034706)


Пользователю очень важно понимать что можно получить в результате и где это можно использовать.

Вначале нужно узнать о том какие фичи предоставляет этот пакет, и только потом как это собрать.


maybe we can add a simple figure to show the edge direction options


ok, i must disable 'Decompile automatically' and 'Decompile' on an instruction.

Good, I can test this way


Also, why are you specifying a default value?


*versions


*node's neighbors


The reason for checking for `None` is that is valid to have an empty expected output (in that case any stuff outputted is an error). `None` was used to specify that we don't expect anything, just warn if there's crap going on.


使用小版本，

第二位用于新增功能，和 antd 一起发布


Why not use multi-catch here?  These catch blocks could be reduced to the following:

``} catch (BadServerResponse | XenAPIException | XMLRpcException e) {
     logger.warn("Failed to attach config drive ISO to VM " + vmName + " in host " + ipAddr + " due to the following error: " + e);
     return false;
}```

Also, why is that logger level ``WARN`` and not ``ERROR``?


You welcome. Using it myself for my own access Point.


Se tem uma regra específica para o action `show`,  o ideal é que este `before_action` não se aplique ao action `show` e que a regra específica fique dentro da definição do próprio action `show`.


@gildegoma so I've started to be able to reproduce this fairly consistently in a CI environment where we've applied this patch to vagrant 1.7.2 and running the latest vagrant-libvirt plugin. Since this was done using debug mode I'm seeing a little more information and unfortunately it does indeed look like there is still a race in there.

    ERROR warden: Error occurred: An action 'read_ssh_info' was attempted on the machine 'group1-0001',
    but another process is already executing an action on the machine.
    Vagrant locks each machine for access by only one process at a time.
    Please wait until the other Vagrant process finishes modifying this
    machine, then try again.

The problem was that group1-001 was running the ansible provisioner while another machine was running the inventory gathering and called this line which in turn for the vagrant-libvirt plugin will call the action read_ssh_info. I believe it's down to how the fact that vagrant by default locks machines when running actions on them to prevent update by multiple processes running in parallel.

In this case however, since it's a read only action, the plugin should disable the lock when calling that action so that ssh_info may be attempted to be retrieved no matter what action is currently running. Looks like support for this was added for 1.7.0.

I believe the problem is at https://github.com/pradels/vagrant-libvirt/blob/57c860e884e242a62d70fa4c5a137e138aa92c7d/lib/vagrant-libvirt/provider.rb#L48

I'll look to follow up with the plugin author and reference them to this issue so they can see how they are being called and the potential issue.


highlight the `HashMap<String,HashSet<Long>>` and the other types


alternate names bikeshed: Permissions, Authorize, Verify, Approve, Authority


1: M111 unrecognized component name: docker


1: M110 missing component name


1: M111 unrecognized component name: docs


4: L102 copyright year is outdated, expected 2015 but got 2013
22:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite


22:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite
23:1: I101 Imported names are in the wrong order. Should be AndOp, DoubleQuotedValue, EmptyQuery, GreaterEqualOp, GreaterOp, Keyword, KeywordOp, LowerEqualOp, LowerOp, NotOp, OrOp, RangeOp, RegexValue, SingleQuotedValue, Value, ValueQuery
23:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. from invenio.modules.search.walkers.elasticsearch should be before from invenio_query_parser.ast
205:17: E126 continuation line over-indented for hanging indent
209:14: E126 continuation line over-indented for hanging indent
211:17: E126 continuation line over-indented for hanging indent
227:14: E126 continuation line over-indented for hanging indent
229:17: E126 continuation line over-indented for hanging indent
239:14: E126 continuation line over-indented for hanging indent
241:17: E126 continuation line over-indented for hanging indent
244:13: E121 continuation line under-indented for hanging indent
246:17: E126 continuation line over-indented for hanging indent
249:13: E121 continuation line under-indented for hanging indent


22:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite
25:1: I101 Imported names are in the wrong order. Should be clean_field_model_definitions, field_definitions, model_definitions


1: M111 unrecognized component name: legacy


22:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite


25:1: E402 module level import not at top of file
26:1: I101 Imported names are in the wrong order. Should be ImportPathRegistry, PkgResourcesDirDiscoveryRegistry, RegistryProxy
26:1: I100 Imports statements are in the wrong order. from flask_registry should be before from invenio.base.wrappers
26:1: I201 Missing newline before sections or imports.
26:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite
29:1: E402 module level import not at top of file
44:1: E731 do not assign a lambda expression, use a def
46:1: E731 do not assign a lambda expression, use a def
48:1: E731 do not assign a lambda expression, use a def


1: D400 First line should end with a period (not 'n')
1: D205 1 blank line required between summary line and description (found 0)
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
34:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: E402 module level import not at top of file
37:1: I101 Imported names are in the wrong order. Should be EmailMessage, EmailMultiAlternatives
37:1: I201 Missing newline before sections or imports.
37:1: E402 module level import not at top of file
38:1: I101 Imported names are in the wrong order. Should be AbstractFormatter, DumbWriter
38:1: I100 Imports statements are in the wrong order. from formatter should be before from flask_email.message
38:1: I201 Missing newline before sections or imports.
38:1: E402 module level import not at top of file
39:1: I101 Imported names are in the wrong order. Should be StringIO, iteritems
39:1: I201 Missing newline before sections or imports.
39:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. from time should be before from six
40:1: I201 Missing newline before sections or imports.
40:1: E402 module level import not at top of file
42:1: E402 module level import not at top of file
43:1: E402 module level import not at top of file
44:1: E402 module level import not at top of file
45:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
49:1: E731 do not assign a lambda expression, use a def
84: D400 First line should end with a period (not 'd')
84: D205 1 blank line required between summary line and description (found 0)
97:25: E124 closing bracket does not match visual indentation
138:8: E714 test for object identity should be 'is not'
140:8: E714 test for object identity should be 'is not'
156: D301 Use r""" if any backslashes in a docstring
156: D400 First line should end with a period (not 'y')
156: D205 1 blank line required between summary line and description (found 0)
239:24: E127 continuation line over-indented for visual indent
240:24: E127 continuation line over-indented for visual indent
241:24: E127 continuation line over-indented for visual indent
265:53: E502 the backslash is redundant between brackets
266:25: E128 continuation line under-indented for visual indent
266:50: E502 the backslash is redundant between brackets
266:28: E251 unexpected spaces around keyword / parameter equals
266:30: E251 unexpected spaces around keyword / parameter equals
267:25: E128 continuation line under-indented for visual indent
267:50: E502 the backslash is redundant between brackets
267:28: E251 unexpected spaces around keyword / parameter equals
267:30: E251 unexpected spaces around keyword / parameter equals
268:25: E128 continuation line under-indented for visual indent
268:44: E502 the backslash is redundant between brackets
268:31: E251 unexpected spaces around keyword / parameter equals
268:33: E251 unexpected spaces around keyword / parameter equals
269:25: E128 continuation line under-indented for visual indent
269:46: E502 the backslash is redundant between brackets
269:35: E251 unexpected spaces around keyword / parameter equals
269:37: E251 unexpected spaces around keyword / parameter equals
270:25: E128 continuation line under-indented for visual indent
270:35: E251 unexpected spaces around keyword / parameter equals
270:37: E251 unexpected spaces around keyword / parameter equals
286:40: E127 continuation line over-indented for visual indent
312: D200 One-line docstring should fit on one line with quotes (found 3)
323: D209 Multi-line docstring closing quotes should be on a separate line
323: D205 1 blank line required between summary line and description (found 0)
426:21: E266 too many leading '#' for block comment
438:13: B901 blind except: statement
463: D401 First line should be in imperative mood ('Remove', not 'Removes')
463: D400 First line should end with a period (not 'n')
463: D205 1 blank line required between summary line and description (found 0)
485: D400 First line should end with a period (not 's')
485: D205 1 blank line required between summary line and description (found 0)


4: L102 copyright year is outdated, expected 2015 but got 2014
22:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite


1: D100 Missing docstring in public module
4: L102 copyright year is outdated, expected 2015 but got 2014
21:1: I201 Missing newline before sections or imports.
22:1: I100 Imports statements are in the wrong order. from flask should be before from invenio.testsuite
22:1: I201 Missing newline before sections or imports.
25: D203 1 blank line required before class docstring (found 0)
25: D204 1 blank line required after class docstring (found 0)
25: D200 One-line docstring should fit on one line with quotes (found 3)
29: D210 No whitespaces allowed surrounding docstring text
29: D400 First line should end with a period (not 'e')
38: D210 No whitespaces allowed surrounding docstring text
38: D400 First line should end with a period (not 'e')
47: D400 First line should end with a period (not 'e')
47: D200 One-line docstring should fit on one line with quotes (found 3)
91: D210 No whitespaces allowed surrounding docstring text
91: D202 No blank lines allowed after function docstring (found 1)
91: D400 First line should end with a period (not 'k')
105: D400 First line should end with a period (not 's')
105: D200 One-line docstring should fit on one line with quotes (found 3)
118: D400 First line should end with a period (not 'n')
118: D205 1 blank line required between summary line and description (found 0)
139: D210 No whitespaces allowed surrounding docstring text
139: D400 First line should end with a period (not 'd')


4: L102 copyright year is outdated, expected 2015 but got 2014
23:1: I201 Missing newline before sections or imports.
24:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, nottest, run_test_suite
24:1: I100 Imports statements are in the wrong order. from invenio.testsuite should be before from mock
24:1: I201 Missing newline before sections or imports.


1: D100 Missing docstring in public module
4: L102 copyright year is outdated, expected 2015 but got 2013


2: L102 copyright year is outdated, expected 2015 but got 2014
27:1: I101 Imported names are in the wrong order. Should be CFG_SITE_SECURE_URL, CFG_SITE_URL
29:1: I100 Imports statements are in the wrong order. from invenio.ext.legacy.handler should be before from invenio.modules.access.engine
31:1: I101 Imported names are in the wrong order. Should be get_bibsched_mode, get_bibsched_tasks, get_css, get_javascript, get_motd_msg
31:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.webapi should be before from invenio.legacy.webpage
37: D203 1 blank line required before class docstring (found 0)
42: D210 No whitespaces allowed surrounding docstring text
42: D400 First line should end with a period (not 'e')
42: D200 One-line docstring should fit on one line with quotes (found 2)
54:9: F841 local variable 'header' is assigned to but never used
82:17: E127 continuation line over-indented for visual indent


1: M111 unrecognized component name: script


1: D400 First line should end with a period (not 's')
22:1: E402 module level import not at top of file
23:1: I100 Imports statements are in the wrong order. import os should be before from six.moves
23:1: I201 Missing newline before sections or imports.
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import tempfile should be before import time
26:1: E402 module level import not at top of file
27:1: I100 Imports statements are in the wrong order. import sys should be before import tempfile
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. import datetime should be before import sys
28:1: E402 module level import not at top of file
33:1: I101 Imported names are in the wrong order. Should be abort, url_for
33:1: E402 module level import not at top of file
34:1: I201 Missing newline before sections or imports.
34:1: E402 module level import not at top of file
35:1: I201 Missing newline before sections or imports.
35:1: E402 module level import not at top of file
36:1: I201 Missing newline before sections or imports.
36:1: E402 module level import not at top of file
38:1: I100 Imports statements are in the wrong order. from invenio.config should be before from six
38:1: E402 module level import not at top of file
39:6: E126 continuation line over-indented for hanging indent
64:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.config
64:1: F401 'cfg' imported but unused
64:1: E402 module level import not at top of file
65:1: E402 module level import not at top of file
66:1: E402 module level import not at top of file
67:1: I101 Imported names are in the wrong order. Should be datetime_format, run_sql, wash_table_column_name
67:1: E402 module level import not at top of file
69:1: E402 module level import not at top of file
70:1: I101 Imported names are in the wrong order. Should be get_record, record_exists, search_unit_in_bibxxx
70:1: E402 module level import not at top of file
72:1: E402 module level import not at top of file
73:1: E402 module level import not at top of file
74:1: E402 module level import not at top of file
75:1: I101 Imported names are in the wrong order. Should be EscapedXMLString, X
75:1: E402 module level import not at top of file
78:25: E203 whitespace before ':'
79:25: E203 whitespace before ':'
80:25: E203 whitespace before ':'
85:25: E203 whitespace before ':'
89:25: E203 whitespace before ':'
107: D205 1 blank line required between summary line and description (found 0)
119: D400 First line should end with a period (not 'r')
119: D200 One-line docstring should fit on one line with quotes (found 3)
135:9: E266 too many leading '#' for block comment
136:9: E266 too many leading '#' for block comment
147:1: E302 expected 2 blank lines, found 1
147: D202 No blank lines allowed after function docstring (found 1)
147: D400 First line should end with a period (not 'r')
147: D200 One-line docstring should fit on one line with quotes (found 3)
169:1: E302 expected 2 blank lines, found 1
169: D200 One-line docstring should fit on one line with quotes (found 3)
179:1: E302 expected 2 blank lines, found 1
179: D401 First line should be in imperative mood ('Get', not 'Gets')
179: D202 No blank lines allowed after function docstring (found 1)
179: D200 One-line docstring should fit on one line with quotes (found 3)
187:9: E221 multiple spaces before operator
192:1: E302 expected 2 blank lines, found 1
192: D401 First line should be in imperative mood ('Return', not 'Returns')
192: D205 1 blank line required between summary line and description (found 0)
202:1: E302 expected 2 blank lines, found 1
202: D400 First line should end with a period (not 'e')
202: D205 1 blank line required between summary line and description (found 0)
212:1: E302 expected 2 blank lines, found 1
212: D400 First line should end with a period (not 'e')
212: D205 1 blank line required between summary line and description (found 0)
222:1: E302 expected 2 blank lines, found 1
222: D209 Multi-line docstring closing quotes should be on a separate line
222: D202 No blank lines allowed after function docstring (found 1)
222: D400 First line should end with a period (not 'r')
222: D205 1 blank line required between summary line and description (found 0)
231:1: E302 expected 2 blank lines, found 1
231: D400 First line should end with a period (not 'e')
231: D205 1 blank line required between summary line and description (found 0)
247:1: E302 expected 2 blank lines, found 1
247: D400 First line should end with a period (not 't')
247: D205 1 blank line required between summary line and description (found 0)
279:85: E261 at least two spaces before inline comment
279:86: E262 inline comment should start with '# '
284:1: E302 expected 2 blank lines, found 1
284: D200 One-line docstring should fit on one line with quotes (found 3)
289:5: E266 too many leading '#' for block comment
290:5: E266 too many leading '#' for block comment
297:9: E116 unexpected indentation (comment)
298:13: E116 unexpected indentation (comment)
299:17: E116 unexpected indentation (comment)
300:13: E116 unexpected indentation (comment)
301:17: E116 unexpected indentation (comment)
302:13: E116 unexpected indentation (comment)
303:17: E116 unexpected indentation (comment)
304:13: E116 unexpected indentation (comment)
305:17: E116 unexpected indentation (comment)
306:13: E116 unexpected indentation (comment)
307:17: E116 unexpected indentation (comment)
309:9: E116 unexpected indentation (comment)
310:13: E116 unexpected indentation (comment)
311:17: E116 unexpected indentation (comment)
312:13: E116 unexpected indentation (comment)
313:17: E116 unexpected indentation (comment)
314:13: E116 unexpected indentation (comment)
315:17: E116 unexpected indentation (comment)
317:1: E302 expected 2 blank lines, found 1
317: D401 First line should be in imperative mood ('Print', not 'Prints')
317: D202 No blank lines allowed after function docstring (found 1)
334:37: E713 test for membership should be 'not in'
335:13: E266 too many leading '#' for block comment
336:13: E266 too many leading '#' for block comment
350:5: E266 too many leading '#' for block comment
397:1: E302 expected 2 blank lines, found 1
397: D401 First line should be in imperative mood ('Generate', not 'Generates')
397: D202 No blank lines allowed after function docstring (found 1)
416:1: E302 expected 2 blank lines, found 1
416: D401 First line should be in imperative mood ('Generate', not 'Generates')
416: D202 No blank lines allowed after function docstring (found 1)
441:30: E261 at least two spaces before inline comment
447:9: E266 too many leading '#' for block comment
448:9: E266 too many leading '#' for block comment
471:9: E266 too many leading '#' for block comment
476:1: E302 expected 2 blank lines, found 1
476: D401 First line should be in imperative mood ('List', not 'Lists')
476: D202 No blank lines allowed after function docstring (found 1)
476: D200 One-line docstring should fit on one line with quotes (found 3)
497: D401 First line should be in imperative mood ('Return', not 'Returns')
497: D202 No blank lines allowed after function docstring (found 1)
513:12: E127 continuation line over-indented for visual indent
522:1: E303 too many blank lines (3)
522: D401 First line should be in imperative mood ('Generate', not 'Generates')
522: D202 No blank lines allowed after function docstring (found 1)
522: D208 Docstring is over-indented
546:17: E128 continuation line under-indented for visual indent
547:17: E128 continuation line under-indented for visual indent
548:17: E128 continuation line under-indented for visual indent
549:17: E128 continuation line under-indented for visual indent
550:17: E128 continuation line under-indented for visual indent
566:1: E302 expected 2 blank lines, found 1
566: D200 One-line docstring should fit on one line with quotes (found 3)
572:1: E302 expected 2 blank lines, found 1
572: D200 One-line docstring should fit on one line with quotes (found 3)
580:1: E302 expected 2 blank lines, found 1
580: D401 First line should be in imperative mood ('Generate', not 'Generates')
585:1: E302 expected 2 blank lines, found 1
585: D401 First line should be in imperative mood ('Generate', not 'Generates')
589:1: E302 expected 2 blank lines, found 1
589: D401 First line should be in imperative mood ('Return', not 'Returns')
589: D209 Multi-line docstring closing quotes should be on a separate line
589: D400 First line should end with a period (not 'd')
589: D205 1 blank line required between summary line and description (found 0)
604: D401 First line should be in imperative mood ('Return', not 'Returns')
604: D400 First line should end with a period (not 'C')
604: D200 One-line docstring should fit on one line with quotes (found 3)
618: D210 No whitespaces allowed surrounding docstring text
632:29: E261 at least two spaces before inline comment
632:30: E262 inline comment should start with '# '
639:31: E261 at least two spaces before inline comment
639:32: E262 inline comment should start with '# '
650:1: E302 expected 2 blank lines, found 1
650: D401 First line should be in imperative mood ('Return', not 'Returns')
650: D200 One-line docstring should fit on one line with quotes (found 3)
671:1: E302 expected 2 blank lines, found 1
671: D401 First line should be in imperative mood ('Generate', not 'Generates')
677:1: E302 expected 2 blank lines, found 1
677: D400 First line should end with a period (not 'e')
677: D205 1 blank line required between summary line and description (found 0)
690:1: E302 expected 2 blank lines, found 1
690: D200 One-line docstring should fit on one line with quotes (found 3)
710: D200 One-line docstring should fit on one line with quotes (found 3)
725:31: F841 local variable 'e' is assigned to but never used
729:1: E302 expected 2 blank lines, found 1
729: D200 One-line docstring should fit on one line with quotes (found 3)
739:5: E266 too many leading '#' for block comment
744:5: E266 too many leading '#' for block comment
755:9: E266 too many leading '#' for block comment
759:9: E266 too many leading '#' for block comment
764:1: E302 expected 2 blank lines, found 1
764: D400 First line should end with a period (not 's')
764: D205 1 blank line required between summary line and description (found 0)
771:5: E266 too many leading '#' for block comment
776:39: E261 at least two spaces before inline comment
776:40: E262 inline comment should start with '# '
782:5: E266 too many leading '#' for block comment
786:5: E266 too many leading '#' for block comment
788:12: E713 test for membership should be 'not in'
789:16: E126 continuation line over-indented for hanging indent
792:18: E261 at least two spaces before inline comment
794:5: E266 too many leading '#' for block comment
796:12: E127 continuation line over-indented for visual indent
803:5: E266 too many leading '#' for block comment
805:12: E127 continuation line over-indented for visual indent
813:12: E127 continuation line over-indented for visual indent
826:12: E127 continuation line over-indented for visual indent
827:12: E127 continuation line over-indented for visual indent
831:5: E266 too many leading '#' for block comment
833:12: E127 continuation line over-indented for visual indent
834:36: E261 at least two spaces before inline comment
838:5: E266 too many leading '#' for block comment
840:12: E127 continuation line over-indented for visual indent
844:12: E127 continuation line over-indented for visual indent
847:5: E266 too many leading '#' for block comment
849:12: E127 continuation line over-indented for visual indent
852:5: E266 too many leading '#' for block comment
854:12: E127 continuation line over-indented for visual indent
859:1: E302 expected 2 blank lines, found 1
859: D401 First line should be in imperative mood ('Run', not 'Runs')
859: D400 First line should end with a period (not 'k')
859: D200 One-line docstring should fit on one line with quotes (found 3)
865:90: E203 whitespace before ':'
865:91: E231 missing whitespace after ':'


32:1: I100 Imports statements are in the wrong order. from itertools should be before import pkg_resources
32:1: F401 'count' imported but unused
36:1: F401 'SchTASK' imported but unused