@tomsmeding currently we aren't setting _workingFor if the bot can't execute the instruction, we just skip the instruction, what do you think about this?


не заметил из-за его фишки, что он обрезается метод и показывает только его тело


ИМХО, `if (way_black != cur_way)`


Let's have a convention when renaming data: note_stage_data_01. Demo will be: note_stage_demo_01.


I don't understand what this should do. In my opinion the clipboard should not be cleared by the browser. My be I copy some text to primary clipboard (selectiong something in terminal) browse a little and press `<Esc>` and my clipboard is empty is no useful thing. I don't think anybody would expect such a behaviour.


#9 の対応


Does this mean the elements are filtered when trying to place it or even beforehand, so the elements are not shown to pick in the page module?


I had actually based my changes yesterday on the parent source methods and hacked in some of our pre-existing checks (things that from what I can tell can't be overridden in the ruleset.xml file).  Excluding constructor/destructor from requiring a `@return` tag is one of those things.


+ 1


fix mistake with copy-paste


I agree that all that should be moved, but if your chainge was complete, you wouldn't need more parameters but less (ie deletedFees shouldn't be used in AcceptToMempool. what I'm trying to do in the commit above is precisely to simplify that movement. Can you take a look at what I do to with GetMinRelayFee there?


hi wes check on this and let me knowon some appropriate names we could name the parameters to be passed to the checkprivilege method


Consider using camelCase for javascript. snake_case, in the company context would be better for ruby / rails


Ok, now is the question: where I can get both asciidoc and source-highlight on Windows? And how to set it up?


Same with this method.  It was based on parent source with our checks added.  In this case, it was to force our parameter alignment rules (PEAR only allows one space after the tag and I think it didn't like aligning params and comments).


Next time consider using separate file for each exercise - the coder review would be easier to do. :)


it might be confusing for the user, but i think it's technically functional---especially, if they want to change the default.


ajouter $config->application->services->controllersDir  dans le loader.php


@stubailo so now `html-scanner` is no longer a separate package.
Isn't it useful?


不用吧 到 dashboard 就看得到啦
> Philip Chou <notifications@github.com> 於 2015年7月17日 下午5:57 寫道：
>
> 呃
> staff 應該要能看到所有玩家的頁面啊
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/sitcon-tw/arcane/commit/28b11f4fd1a0a9100089bac94a25b862d9b625ac#commitcomment-12222433>.
>


Dnes ti to jde


This is broken.

$ grep remmina /usr/share/applications/remmina.desktop
TryExec=/remmina
Exec=/remmina
Icon=/remmina
Exec=/remmina --new
Exec=/remmina --icon

Seen on version 1.1.1-1+766+next+201507170316~ubuntu14.04.1 from ppa:remmina-ppa-team/remmina-next.


@azdkj532  後來想想也是，所以我沒動那邊


Lemonphoto


It's better using triple equals operator `===` over `==` as javascript have some bad parts and using `==` can make your head spin. More:

(http://conceptf1.blogspot.com/2014/01/javascript-triple-equals-vs-double-equals-operators.html)


其實我只是吧所有可用的變數列一列 看前端那邊會不會用到而已


In this git, no single module does not work ... The server does not see them at all ..

(  1) Load fails: Module/Library "engine" required for plugin.  Check modules.ini.
         (  2) Load fails: Module/Library "sockets" required for plugin.  Check modules.ini.
         (  3) Load fails: Module/Library "fakemeta" required for plugin.  Check modules.ini.
         (  4) Load fails: Module/Library "fakemeta" required for plugin.  Check modules.ini.
         (  6) Load fails: Module/Library "fakemeta" required for plugin.  Check modules.ini.
         ( 10) Load fails: Module/Library "regex" required for plugin.  Check modules.ini.
         ( 11) Load fails: Module/Library "regex" required for plugin.  Check modules.ini.
         ( 12) Load fails: Module/Library "fakemeta" required for plugin.  Check modules.ini.

etc ...


Adding a space between keyboards like `for (` would make your code more readable.


E.g. vulcanize has output:

```
 <!-- only allow characters that match [0-9] -->
    <
    input
    is = "iron-input"
    prevent - invaild - input
    allowed - pattern = "[0-9]" >

    @
    hero
    hero.svg
    @
    demo
    demo / index.html
    * /
```
(note space in closing comment, so following js migth get ignored)


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.358](http://teamcity.monogame.net/viewLog.html?buildId=8813&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 516, ignored: 6 Build time: 00:24:40


I'd try MSYS2 and `pacman -S asciidoc` as well as `pacman -Ss highlight` and then installing the right packages. Then (after configuring CMake) a simple `make trosettastone` should suffice.


it's already implemented via tox, just add this repo to coveralls, via it's web interface


Thanks for keeping up the good work on this issue.

As for the commit message, how about bringing it more in line with the rest of Git's commit history? In particular, the Git project frowns upon commit messages that 1) repeat what the diff already says, and 2) leave out important details.

In this case, for example, it is of course correct to say that we verify the memoized files. But that does not tell the reader *why*. It does not give the reader the context of *what* was the problem we wanted to solve to begin with. Also, just mentioning "Fixes #233" will probably elicit not very nice language when encountered on a plane ride without internet access while trying to figure out why some code was introduced that has a nasty side effect.

And of course we can do much better than that. Something like this:

```
git-svn: do not reuse caches memoized for a different architecture

Reusing cached data speeds up git-svn by quite a fair bit. However, if
the YAML module is unavailable, the caches are written to disk in an
architecture-dependent manner. That leads to problems when upgrading,
say, from 32-bit to 64-bit Git for Windows.

Let's just try to read those caches back if we detect the absence of the
YAML module and the presence of the file, and delete the file if it
could not be read back correctly.

Note that the only way to catch the error when the memoized cache could
not be read back is to put the call inside an `eval { ... }` block
because it would die otherwise; the `eval` block should also return `1`
in case of success explicitly since the function reading back the cached
data does not return an appropriate value to test for success.

This fixes https://github.com/git-for-windows/git/issues/233.
```

Notice the explanation of the `; 1` part? It took me 10 minutes to verify that that is correct. An appropriate commit message saves the interested readers that time.

To update, please amend the commit message, sign off on it (as [requested by the Git project](https://github.com/git/git/blob/v2.3.5/Documentation/SubmittingPatches#L234-L286)) and force-push the branch.


Will check that ASAP


added


Warning, the commit of the message contains comments inserted by git that should not appear in the final message


php实现的网络爬虫，外加一个“编程语言薪资排行榜”


About first question, `+?` and `*` aren't same. First of this is reluctant quantifier, but second is greedy.(See http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html)


@azdkj532 怎麼說？


Putting a private function as default value without a string / key method name is not so nice.
Honestly I would suggest to wrap up things and don't make the API and don't get distracted by working on expert options.


It doesn't work, shouts at me about wrong PGP signatures. Where are packages coming from? If it's from SourceForge, that explains everything, whole SF is a disaster now! :rage:


@crami I would absolutely do that, unfortunately I don't know how? Quick pointer in the right direction and I'll surely try my best. :)


Indeed, you're right. My mistake. =)


sad


ok


Typo in Extension.


The prefix "new" conflicts with metrics "new_". I would rename it "added" or "newly"


fuck


Shh... You saw nothing... :ghost:


You rock!


What do you think of moving all the examples to http://codepen.io/
This way I can not only see the code but run it and see if it run as expected - you can modify it applying the feedback and share what've you learnt on the way.
Ex: http://codepen.io/ryrych/pen/WvKjXJ?editors=001
(you can create some collection)

I'm not sure if it is possible, but see if you can get the source from github gists (first you would have to upload each example as a separate gist)


I think better English would be "do_not_create_measures_when_no_values"


Time change was good


We can also easily enough make this broadcast.


I remember needing to install ca-certs first. Then everything went fine. You only have to convince pacman to install it ignoring the certs using --force or something :)


Cool, thx


Windows CYGWIN에서는 절대주소가 제대로 작동이 안되어 수정.


As you have used it in the previous examples, consider extracting it into a function that you could use it like this:
`isDividable(4, 2)`


Am 17.07.2015 um 13:41 schrieb Peter Bjuhr:
> I have doubts about the roadmap section for two reasons:
>
>   *
>
>     The user may not be helped by features planned for the future; a
>     release note seems to be a better forum for this kind of information.

Good point.
I suggest keeping it for now until it has been reviewed by others and
then move it to the ROADMAP.

>
>   *
>
>     Are we ready to announce these plans at this point?

Yes, they belong to the roadmap. Not in release notes, though.


I'd prefer not to require this patch only because a kernel commit which has been sent to linux-stable messed things up. Complexity literally explodes to support this. The PIC/PIE support is already quite complex. This is why it has such a long explanation text in the source. Also other user-space tools could be affected. So the kernel would be the best place to fix this.
But in case we can't reach a consensus on this, we have at least something to fix this for us.


Yes, finally I'll just use the setUp() function.


Increased to give enough time for the log readers to finish delivering messages.
Set to 10s because @lk4d4 said 10.

Before reading was happening directly from the container stdout/stderr (via broadcastwriter) and not from the logger.


```divisor``` is ensured to be non-zero because of the single method call at line 116. It's risky for future changes. I would simply replace this method ```calculateDensity``` by this statement at line 114 :

```java
if (nbLines.isPresent() && nbLines.get() > 0) {
  double density = Math.min(100.0, 100.0 * duplicatedLines / nbLines.get());
  return Optional.of(Measure.newMeasureBuilder().create(density));
}
```


@petrus-v thanks for review


No, it's really SourceForge. I wish it to finally die and wash off from the face of Earth.

` We're sorry -- the Sourceforge site is currently in Disaster Recovery mode, and currently requires
the use of javascript to function.  Please check back later. `

So glad we've migrated to GitHub in time.


если просто View оставить, то получается пусть ../Admin/Delete


Windows ping 옵션에서 linux ping`-c` 옵션에 대응되는 것이 `-n`이므로 이것들을 추가하는 것이 필요함.


谢谢啦 ~
难怪上次在同学的机器上出现了一些问题 -- ，我一直都没发现这个问题。


@Mingun Your comments here were still marked as unresolved in my e-mail, got to them now…

> But the contract also shall include testing of that you don't see variables which aren't declared yet and you don't see variables which part you are.

I consider the behavior in these situations undefined — something you can’t test for really.

Also, form the practical POV, there is usually a ton of possible negative test cases for every possible positive one. So I generally tend to focus on the positive cases and introduce the negative ones only when I think it would be highly valuable or when the test case is required to write some code when practicing TDD. Admittedly, label variables are a boundary case (the negative test cases wouldn’t be completely value-less) but I still think they lie on the “not necessary to test” side.

> ```js
> // Must failed with undefined variable 'b'
> start = a:"a" b:("b" !{return b;});
> ```
> It seems to me that at the moment this test will fail because at first the variable `b` is added to `env`, and only then subexpression `"b" !{return b;}` will be processed (because AST node for label contains AST node for subexpression).

No, a parser generated from that grammar fails with `ReferenceError`. The [relevant code](https://github.com/pegjs/pegjs/blob/122d7b0737f13b4ff8731d86d9c55721e1efb4f5/lib/compiler/passes/generate-bytecode.js#L429-439) handles this situation correctly.

> > Because “describe can access label variables...” sounds wrong but “it can access label variables...” sounds right.
>
> I didn't mean the naming. I mean, that you have a set of `it`, beginning with the same sentence and them it is logical to carry out in separate `describe`.

I agree, as long as the resulting wording sounds natural and descriptive. I wasn’t able to find such wording, therefore the duplication stays.

---

Your comments prompted me to look at this code again and [I ended up simplifying and restructuring it a bit](https://github.com/pegjs/pegjs/compare/122d7b0737f13b4ff8731d86d9c55721e1efb4f5...6f2c75f7d8a2f32aa7ee35a88e0a820b66eca438). Thanks for triggering that.


for the time being, it's not possible to exclude a field, here the db id, so it's not possible to use the json example


The sale.order.line create method already call this function.


Исправил, забыл убрать


Is modulename needed? IIRC, pluginname should be enough. Did you receive some debugging warning if the string was missing?


ок


хорошо


@suryatech Yes, you are right. I just pushed a commit to fix and added some tests: SHA: 5f1487a3ad3527ea3f5a872306bec51f1107397d


:+1:

Às vezes a gente esquece de usar as próprias ferramentas :)


OK I'll do that.


:tada:


@weierophinney Can you apply this fix to version 1.0? Now after update `zf-content-negotiation` to 1.0.8 and above my test fails ;-(


Исправлял, откатывался, а потом забыл(


could we maybe put the `file_lock` method together with `acquire_lock` and `release_lock` from service_object into a more generic place to avoid duplication?


Personally I prefer restricting the number of one-line private methods when possible. Here the shared code is trivial and decreases readability. I would do:

```java
    @Override
    public void aggregate(SumDuplicationCounter counter) {
      value += counter.getValue();
    }

    @Override
    public void aggregate(FileAggregateContext context) {
      Optional<Measure> measureOptional = context.getMeasure(metricKey);
      if (measureOptional.isPresent()) {
        value += measureOptional.get().getIntValue();
      }
    }
```

My 2 cents !


For testing, I just change the lng to 'zh', ( I will be working on the traditional Chinese when I have them, it's zh-TW, for people from Hong Kong and Tai Wan ). We can get the locale from the server or as a user preference on the settings section, just as an option... What do you think?


```sut``` !


> To keep it has be moved to the `transformResponse` method.

I guess you mean it has to be moved onto the promise [returned here](https://github.com/vuejs/vue-resource/blob/master/src/http.js#L65), because moving it into the `transformResponse` method makes no sense.

If I'm understanding you correctly, we still need this here. We don't have access to the `request` there. We'll have to reassign it there. Perhaps something like this:

```js
promise = request(self.$url || Url, options);

function request(url, options) {
    var sender = options.method.toLowerCase() == 'jsonp' ? jsonp : xhr;
    var request = sender(url, options);
    var promise = request.then(transformResponse, transformResponse);

    promise.abort = request.abort;

    return promise;
}
```


Yeah I will remove it..


 >>Are we ready to announce these plans at this point?

>Yes, they belong to the roadmap.

My feeling is that they have not been properly discussed.


If this is going to be one of the final design-level iterations, it would be nice to have some comments/docstrings to specify the design-scope and purpose of the Component. This would be especially helpful to people like me who want to become familiar with the code, but who are unclear how everything fits together.


What if `num1` or `num2` is not a number, but a string like `'10'` or `'thousand'`?.
#


yeah, here we don't need a body id..but this can be helpful when we are using a single JS file for multiple HTML pages.


I'll look upon this :+1:


Loving the copy :)


It's been a while (2 weeks or something) since my last TRCL check but I noticed:

* devastating performance in briefing
* text buffer at start of briefing flooded with Xes
* increased flickering of GUI, especially the text
* don't quote me on this one until I did more testing but it seems there are some rare collisions triggered where absolutely no objects are (AKA thin air). Or there is an object but it's invisible.


well, these will be removed if the property generator is run


なおしました。


There is a bug on this piece of code, variable $error is not defined.
Also this variable is intended to transport the error ( not as Json ) raised from the ```call()``` and ```_call()``` methods:

https://github.com/tilde-nlp/MateCat/blob/baee27b8d48099837f9d640cd89c512793f90446/lib/Utils/Engines/AbstractEngine.php#L163

https://github.com/tilde-nlp/MateCat/blob/baee27b8d48099837f9d640cd89c512793f90446/lib/Utils/Engines/AbstractEngine.php#L118

so it is related to all the calls made inside the AbstractEgine class and should be the default behaviour.


Ups ... I did if for you ... Tried to explain how ... and it was allready done ...

It's very simple yust go on your fork on the right there those icons, second from top ist "pull requests", there you just click on "create pull request" and done.

Regards

  Matthias

On 17/07/15 14:43, Mitch Bumganer wrote:
> @crami <https://github.com/crami> I would absolutely do that, unfortunately I don't know how? Quick pointer in the right direction and I'll surely try my best. :)
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/mitchell486/language-cisco/commit/e09f0443754352c80f2faa1c7a2c852319d32a9f#commitcomment-12224691>.
>

--
Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach
http://www.freestone.net
GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E  3959 B62F DF1C 2D20 8250


Thanks alot
U know what? U r z first contributer 2 zis project. 10x

If u have time nd believe in open source, fork fix nd send me a pull request pls
U r right it sould be is_int


After the ```delete()``` there should be a return error like the other engines call:

https://github.com/tilde-nlp/MateCat/blob/baee27b8d48099837f9d640cd89c512793f90446/lib/Controller/engineController.php#L237

This prevent the javascript to be executed in case of failure.


Does that correctly handle the case where we have feature definitions inside strings in a Scenario?

I tried something similar to this but I couldn't get it to handle with that case.


The problem I see here is that this only runs when there is no `$PGDATA` directory. I assume that most people mount `$PGDATA`, so this would be run only once during the first container startup.

In case the container is stopped and then restarted with different env variables they would never be written to `postgresql.conf`.


就是很單純的把所有可用的變數列出來，沒特別用html tag 把它包得漂亮之類。


It was meant to test invalid(non numeric) data. It is not a signal or magic constant.

I think it should be like "randomString" or "loren ipsum#


Instead of only check
```javascript
Object.keys(d.data.config).length
```
you should create a key holding the MT engine name or type so the method ```renderMTConfig``` could be used for other engines configurations and/or for future purposes.


@azdkj532 後來決定還是弄一弄好了@_@


OK, enabled, see https://coveralls.io/github/yast/yast-installation.


I see, that's a mistake on my part. We should be throwing if we fail to bind a built-in helper.


Could we perhaps get rid of having to define `getLabel()` and `getRelationshipType()` in this interface?


Ok


I think this formatting looks strange whenever intellij decides to do it...


This should be severity 1


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


Good point, maybe the regex should be modified to not allow spaces before.


Eh?
On Jul 17, 2015 3:11 AM, "icyore" <notifications@github.com> wrote:

> p =1/delta(t)?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/diydrones/ardupilot/commit/fc898a00a34697458bd4b81e05a9cb18e7c91990#commitcomment-12222644>
> .
>


+1

btw I've did this to handle abrt-dbus timeouts- https://github.com/abrt/abrt/commit/01e0a3586d2f35d8a73d2fbf213d21a34c16d1c9


i suggest we fix that in different PR, keeping PR with small scope


This is one of many reasons why JavaScript sucks.


This probably needs to be an || - if it's disabled, or it's revoked. I forget when sysStatus is set to disabled.


There should be an error check for the service call here.


Non


No. Entware's uClibc uses kernel 2.6 syscalls.

Alexander, seems to we have to add this question to FAQ.


Good point !


You will want to use a more descriptive error, like "Public key has been disabled/revoked" and in the details include the public key ID and the revocation date. I'd look into the 'disabled' code and see why it might be disabled.


You're absolutely right !


ok. it was stupid...


Why are these unindented now?


Not a typo.

OATH stands for Open AuTHentication.


mdr ...


Indeed, I've created this test before the decision to use sut :)


There may be higher priorities now. But it probably should happen sometime. :)


You are actually setting value on your option above, so just set it to something else, without spaces it won't be translated and check for it here. ei

<option translatable="yes" class="deploy-app-type-text" value="kube-manifest">Kubernetes Manifest</option>


There are error messages like "path_to_file: undefined parse transform". They haven't characters to match `(\\d+):`. There are some problems not only with pattern.  Also number of line  is optional now but we always  show it to user. I going to fix it and add tests.


Codemaid _sigh_


this line isn't useful.


No, once the bug ping pong dies down it won't have to change often, and people will see it when we merge.

Also, we could add the page to another repo and remove it from here if you wanted, but still thinking of options so I think just leave it here for now.


@lly-dev, [done](https://github.com/Entware/entware/wiki/FAQ#q-which-platforms-are-supported).


:P


The JS docs are good, but I don't think it makes sense to put all the docs in a subdirectory. Surely at least installation and development info can be in the main README.md, with links to the design docs or whatever else has more detail.


In that case too, there are ways of structuring JS that don't require a body ID.


 var config = {
-	name: 'Revolution BoTTT',


I don't understand. I don't see what we're looking for in /usr/lib/ at all.

http://packages.ubuntu.com/vivid/amd64/libpcsclite1/filelist

**/lib/x86_64-linux-gnu/libpcsclite.so.1**
**/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0**
/usr/share/doc/libpcsclite1/changelog.Debian.gz
/usr/share/doc/libpcsclite1/copyright

Only the -dev version is going into /usr/lib, and the whole point of this class is to
fix 1) the old bug where the JRE devs are looking for a -dev lib and 2) the slightly newer bug where Oracle JRE don't know about the Debian multi-arch strategy.

http://packages.ubuntu.com/vivid/amd64/libpcsclite-dev/filelist

/usr/bin/pcsc-spy
/usr/include/PCSC/debuglog.h
/usr/include/PCSC/ifdhandler.h
/usr/include/PCSC/pcsclite.h
/usr/include/PCSC/reader.h
/usr/include/PCSC/winscard.h
/usr/include/PCSC/wintypes.h
**/usr/lib/x86_64-linux-gnu/libpcsclite.so**
/usr/lib/x86_64-linux-gnu/libpcscspy.so
/usr/lib/x86_64-linux-gnu/libpcscspy.so.0
/usr/lib/x86_64-linux-gnu/libpcscspy.so.0.0.0
/usr/lib/x86_64-linux-gnu/pkgconfig/libpcsclite.pc
/usr/share/doc/libpcsclite-dev/changelog.Debian.gz
/usr/share/doc/libpcsclite-dev/copyright
/usr/share/doc/libpcsclite-dev/examples/pcsc_demo.c.gz
/usr/share/man/man1/pcsc-spy.1.gz

What am I not getting, here?


Seems fine to me. Cannot be merged without ITK4.8 as 4.6 does not contain the type FixedParametersType.


at the same time, reorder the import at the top. The new one should be in a new section at the top.


Also, fix the tabs.


name: 'Revolution BoTTTt',


Good.

Why don't we leave compiler error reporting aside for now and focus on incremental compilation instead?

You can submit compiler messages handling in a separate pull request after we finish with incremental compilation.


`//TODO: handle EOF errors`


Ah yeah that would probably do it :)


Special Rules typos and clarifications update


I have some identation issues (at least in github). Also template <typename XX> has to be preferred to template <class XXX>. The first part of the two new functions could be factorized... Otherwise OK, but needs itk 4.8.


case 1 and 2 are duplicated here.


`zfs list -r -d1 -t snapshot $dataset` has an off by 1 error that I need to fix inside the kernel. `zfs list -d2 -t snapshot $dataset` does work as expected, but I will attach gdb to see if userland is filtering something that the kernel should not hvae emitted.


The `path` parameter.


Поразмышлял надо коммитом. Понял, что менять 24 недостаточно, надо и 104 тоже подстраивать. Если бы мы знали высоту клиентской области тулбара, то

- берем от неё где-то 2/3 для высоты нашего контрола
- умножаем на ведомый только нам aspect ratio, например, 4.3, чтобы при 24 выйти на теже 104

Это позволит на ретине выводить красивый ползунок. Надо запустить на ней текущее решение и проверить, думаю сделать это на выходных. Но кажется, что имеет смысл или откатить или допилить.


Does it mean we should always trust the sender to behave in this case? Or we are the ones to generate this base64 encoded data?


Текущее решение вод виндой выглядит красиво, а под убунтой кажется слишком высоким.


This has merged now, but we should've at least gone with NonFatal, no?


Excellent. The problem with public fields is that they cannot implement interfaces. Properties so much better.


What is the reasons of moving the method?


@theengineear I changed it because I got this error
```
nosetests plotly/tests/test_core/test_tools/test_file_tools.py
E
======================================================================
ERROR: test_set_config_file_all_entries (plotly.tests.test_core.test_tools.test_file_tools.FileToolsTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/nedaamin/projects/python-api/plotly/tests/utils.py", line 24, in tearDown
    self.restore_file_credentials_and_config()
  File "/Users/nedaamin/projects/python-api/plotly/tests/utils.py", line 40, in restore_file_credentials_and_config
    json.load(self._file_config, f)
  File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 286, in load
    return loads(fp.read(),
AttributeError: 'dict' object has no attribute 'read'

----------------------------------------------------------------------
Ran 1 test in 0.007s

FAILED (errors=1)
```


Once reviewed, I will re-build the documentation (due to doc changes) and attach to this PR.


non_scalars[0].size would be equivalent. No need to change, just for your info.


Thanks for cleaning up on this.

I do find the two-statements-on-one-line a little icky though.  Not that it matters :)


**bug**
![11406716_868664203226888_4612905732441285566_o](https://cloud.githubusercontent.com/assets/13377997/8748200/9c89846e-2ca1-11e5-9b21-f1015f5750aa.jpg)


I think that's not a good change. We still use this log device to test the RIL.


I want to do that but it introduces cyclic definition which is not possible to implement.


I know you didn't accepted it in the previous Pull Request, so I place it here in a different branch. So can we together find a working around for this small issue ?


@theengineear  I locally changed it back to load and now I get this
```
ValueError: No JSON object could be decoded
```
and all of my tests fail.  Is it because of api restriction?


@sahilsarpal frreee


People should apply these settings by themselves. It's not hard to google around.. core.autocrlf


Wow, that's even more messy than I expected! Thanks for the exaplanation. I'm absolutely okay with using the ``mv`` utility then :)


move this to webtip


Up.


I would love to add comments. So, feedback is welcome. I will add comments when I have time.


and in the condition `new_op_input_nb_elements != 1` to lower the number of following opt needed to clean this.


checks*


Ah. The version check seems strange: the error message says 4.8.0 but the test is made against 4.7.2. Also using VERSION_LESS will make the cmake code clearer and will also allow removing _ITKVersionNum.


Cadê meu feedback? :cry:


idem, if new_op_output is 1, don't add it.


Oops, looks like there was an obvious bug there.


Comentário que deletei sem querer:

> As mensagens de commit devem ser claras e dizer o que foi incorporado ao produto, por exemplo: "Possibilita visualizar listas", "Adiciona listagem de 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.

> @jlgm


Okay, I was gonna say... :)

It might also be useful to have a context manager version of this.  Can I port this back into Astropy? It seems to me something that should be in the standard testing tools anyways.


No space before "in" + line is too long


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.359](http://teamcity.monogame.net/viewLog.html?buildId=8817&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 516, ignored: 6 Build time: 00:25:37


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


Thanks :) and it stops people thinking they can modify the order fields to
change stop prices etc. Now it will coax people to use order  tickets
instead..
On Jul 17, 2015 9:33 AM, "dpavlenkov" <notifications@github.com> wrote:

> Excellent. The problem with public fields is that they cannot implement
> interfaces. Properties so much better.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/QuantConnect/Lean/commit/9bc0c8e450d1512eadb55e7b4f378b7775ce4719#commitcomment-12225383>
> .
>


Wouldn't it be easier to just use HTTP? Send a command to the builder client to download from a certain URL and then just serve that with your web app. There are many other file transfer protocols as well. You really should not roll your own for something like this.


Great job with you html and css code. Everything is indented and nested properly. Very clean!


@Mingun It was meant to be `start = . start`. I [fixed it](https://github.com/pegjs/pegjs/commit/373f48c10fb6643dde033a8bb82e99bbc7de5000) together with another similar instance. Thanks for pointing this out.


@lieuwex good. But jezus christ that diff. Why, for gods sake, was it necessary to introduce *another* level of indentation in that huge switch? Can't you negate the if condition and return quickly if so?


Seems like this needs to go in utils or some helper package.


Seems like this belongs in utils or some helper package.


esrvcdrgtdrtv


This should be a constant


hm. it seems the merge algorithm isn't working as well(?) as before. It seems as if  - in this case at least - it created a new duplicate: http://glottolog.org/resource/reference/id/472445 which was merged with http://glottolog.org/resource/reference/id/116817 before?


OK this is transferring from the client to the server. Still just offer an HTTP endpoint and have the client post to that.


Same as others? It's not the only place with `@poperty` annotations...


Lastly please don't spend a bunch of time on something like this if you are having a bunch of issues. You probably could get an HTTP based version going in an hour. How much time did you spend on this?


Yep. I initially thought that would be an easy add-on to the new code, but it turns out it would need its own nontrivial handling. In a non-topology request, the originating stonithd doesn't know what device will be used. So after doing the 'off', the executing stonithd would have to return a new status code for "success but you need to do 'on' now with such-and-such device".


`first()` :)


Fine by me. One thing though: http://www.itk.org/Wiki/ITK/Git/Download refers to git://itk.org/ITK.git. Why use the github mirror which is slightly delayed.... This does not have much impact , but at least put a comment explaining why this choice has been made (so that we avoid going back and forth).


@maxiloc : Wouldn't [this](http://stackoverflow.com/questions/20894705/how-to-check-if-a-class-is-a-doctrine-entity#20907212) be safer ?


`singleOrNull()`


Agreed

ncreep <notifications@github.com> wrote:
>It may not be strictly necessary, but I think that it makes the
>intention of the test more clear and can serve as documentation for the
>user.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/101dev/slick-migration-api-flyway/commit/030837aa63f57cc8c27d26a6a6b10fddfde33549#commitcomment-12218563


`Lists.newArrayList` could be replaced with `arrayListOf` in the file


Revert 돌리면 되잖아요


Great `random/2` change, though it's not just "Update CHANGELOG". :Ь


La razón por la cual preguntaba si el playable estaba en un evento en el EventEngineManager es porque conceptualmente me parece mal que un evento tenga que manejar eso. El EventEngineManager funciona a modo de comunicador entre el Core de L2J y el sistema de eventos. Preguntando si el jugador está registrado o no en el listener del AbstractEvent, te estás salteando una capa (EventEngineManager) de algo de lo cual no debería hacerse cargo.

¿Es lo mismo? Prácticamente sí. ¿Conceptualmente? Prefiero la solución anterior por lo que ya te comenté.


Quickbase API
https://www.quickbase.com/api-guide/index.html


It seems to me that this block is called every time a page is being loaded.


it is not required as it is only for 1 line below it but having it explicitly there makes the code easier to follow, I've updated my fork


1: M111 unrecognized component name: legacy


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


1: D100 Missing docstring in public module
30: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: I100 Imports statements are in the wrong order. import fnmatch should be before import time
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: 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:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_ADDING_RECORDS_STARTED_STR, CFG_BIBINDEX_INDEX_TABLE_TYPE, CFG_BIBINDEX_SPECIAL_TAGS, CFG_BIBINDEX_TOKENIZER_TYPE, CFG_BIBINDEX_UPDATE_MESSAGE, CFG_BIBINDEX_UPDATE_MODE, CFG_BIBINDEX_WASH_INDEX_TERMS, CFG_CHECK_MYSQL_THREADS, CFG_MAX_MYSQL_THREADS, CFG_MYSQL_THREAD_TIMEOUT
39:1: E402 module level import not at top of file
40:6: E126 continuation line over-indented for hanging indent
49:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibauthority.config should be before from invenio.legacy.bibindex.engine_config
49:1: E402 module level import not at top of file
50:6: E126 continuation line over-indented for hanging indent
51:1: I101 Imported names are in the wrong order. Should be get_control_nos_from_recID, get_index_strings_by_control_no
51:1: F401 'get_index_strings_by_control_no' imported but unused
51:1: E402 module level import not at top of file
52:6: E126 continuation line over-indented for hanging indent
53:1: I101 Imported names are in the wrong order. Should be get_synonym_terms, perform_request_search, search_pattern
53:1: E402 module level import not at top of file
54:6: E126 continuation line over-indented for hanging indent
56:1: I100 Imports statements are in the wrong order. from invenio.legacy.dbquery should be before from invenio.legacy.search_engine
56:1: E402 module level import not at top of file
57:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_washer should be before from invenio.legacy.dbquery
57:1: E402 module level import not at top of file
58:1: I101 Imported names are in the wrong order. Should be get_datetime, task_get_option, task_get_task_param, task_init, task_set_option, task_sleep_now_if_required, task_update_progress, write_message
58:1: E402 module level import not at top of file
61:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.legacy.bibsched.bibtask
61:1: E402 module level import not at top of file
62:1: I201 Missing newline before sections or imports.
62:1: E402 module level import not at top of file
63:1: F401 'get_def_name' imported but unused
63:1: E402 module level import not at top of file
64:1: E402 module level import not at top of file
65:1: I101 Imported names are in the wrong order. Should be CFG_JOURNAL_PUBINFO_STANDARD_FORM, CFG_JOURNAL_PUBINFO_STANDARD_FORM_REGEXP_CHECK, CFG_JOURNAL_TAG
65:1: F401 'CFG_JOURNAL_PUBINFO_STANDARD_FORM_REGEXP_CHECK' imported but unused
65:1: F401 'CFG_JOURNAL_PUBINFO_STANDARD_FORM' imported but unused
65:1: F401 'CFG_JOURNAL_TAG' imported but unused
65:1: E402 module level import not at top of file
69:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.termcollectors should be before from invenio.modules.indexer.tokenizers.BibIndexJournalTokenizer
69:1: E402 module level import not at top of file
70:1: I101 Imported names are in the wrong order. Should be filter_for_virtual_indexes, get_all_index_names_and_column_values, get_all_indexes, get_all_synonym_knowledge_bases, get_field_tags, get_index_remove_html_markup, get_index_remove_latex_markup, get_index_remove_stopwords, get_index_tags, get_index_virtual_indexes, get_marc_tag_indexes, get_min_last_updated, get_nonmarc_tag_indexes, get_records_range_for_index, get_virtual_index_building_blocks, list_union, load_tokenizers, make_prefix, recognize_marc_tag, remove_inexistent_indexes, run_sql_drop_silently
70:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_utils should be before from invenio.legacy.bibindex.termcollectors
70:1: F401 'get_field_tags' imported but unused
70:1: F401 'get_all_index_names_and_column_values' imported but unused
70:1: E402 module level import not at top of file
91:1: E402 module level import not at top of file
92:1: F401 'get_record' imported but unused
92:1: E402 module level import not at top of file
93:1: E402 module level import not at top of file
94:1: I101 Imported names are in the wrong order. Should be NonmarcTermCollector, TermCollector
94:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.termcollectors should be before from invenio.utils.memoise
94:1: F999 redefinition of unused 'TermCollector' from line 69
94:1: E402 module level import not at top of file
97:1: I101 Imported names are in the wrong order. Should be deserialize_via_marshal, serialize_via_marshal
97:1: E402 module level import not at top of file
100:1: E402 module level import not at top of file
101:1: I100 Imports statements are in the wrong order. from MySQLdb should be before from sqlalchemy.exc
101:1: I201 Missing newline before sections or imports.
101:1: E402 module level import not at top of file
103:1: E402 module level import not at top of file
118:17: E261 at least two spaces before inline comment
119:25: E261 at least two spaces before inline comment
126: D401 First line should be in imperative mood ('Return', not 'Returns')
135: D400 First line should end with a period (not 'n')
135: D205 1 blank line required between summary line and description (found 0)
135: D208 Docstring is over-indented
150:66: E502 the backslash is redundant between brackets
155: D400 First line should end with a period (not 'd')
155: D205 1 blank line required between summary line and description (found 0)
184: D400 First line should end with a period (not 'e')
184: D205 1 blank line required between summary line and description (found 0)
192: D209 Multi-line docstring closing quotes should be on a separate line
192: D205 1 blank line required between summary line and description (found 0)
195:53: E502 the backslash is redundant between brackets
218:67: E225 missing whitespace around operator
219:30: E124 closing bracket does not match visual indentation
219:31: E261 at least two spaces before inline comment
228:33: E261 at least two spaces before inline comment
240:33: E261 at least two spaces before inline comment
251:33: E261 at least two spaces before inline comment
263:33: E261 at least two spaces before inline comment
274:33: E261 at least two spaces before inline comment
286:33: E261 at least two spaces before inline comment
296: D401 First line should be in imperative mood ('Remove', not 'Removes')
296: D300 Use """triple double quotes""" (found '-quotes)
301: D401 First line should be in imperative mood ('Return', not 'Returns')
301: D400 First line should end with a period (not 'd')
313: D401 First line should be in imperative mood ('Return', not 'Returns')
313: D400 First line should end with a period (not 'e')
313: D205 1 blank line required between summary line and description (found 0)
313: D208 Docstring is over-indented
324:68: E502 the backslash is redundant between brackets
332: D401 First line should be in imperative mood ('Check', not 'Checks')
332: D205 1 blank line required between summary line and description (found 0)
332: D208 Docstring is over-indented
353: D401 First line should be in imperative mood ('Return', not 'Returns')
353: D400 First line should end with a period (not 's')
355:10: E225 missing whitespace around operator
370:56: E261 at least two spaces before inline comment
378: D210 No whitespaces allowed surrounding docstring text
378: D400 First line should end with a period (not 's')
378: D205 1 blank line required between summary line and description (found 0)
389:70: E502 the backslash is redundant between brackets
390:32: E127 continuation line over-indented for visual indent
394: D401 First line should be in imperative mood ('Return', not 'Returns')
394: D400 First line should end with a period (not 'e')
394: D300 Use """triple double quotes""" (found '-quotes)
407: D401 First line should be in imperative mood ('Create', not 'Creates')
407: D209 Multi-line docstring closing quotes should be on a separate line
407: D400 First line should end with a period (not 'd')
407: D205 1 blank line required between summary line and description (found 0)
426: D401 First line should be in imperative mood ('Return', not 'Returns')
426: D400 First line should end with a period (not 't')
448:74: E502 the backslash is redundant between brackets
452:52: E261 at least two spaces before inline comment
453:52: E261 at least two spaces before inline comment
454:54: E261 at least two spaces before inline comment
455:54: E261 at least two spaces before inline comment
458: D205 1 blank line required between summary line and description (found 0)
458: D208 Docstring is over-indented
468:70: E502 the backslash is redundant between brackets
474: D210 No whitespaces allowed surrounding docstring text
474: D400 First line should end with a period (not 'd')
484: D401 First line should be in imperative mood ('find_affected_record', not 'find_affected_records')
484: D205 1 blank line required between summary line and description (found 0)
484: D208 Docstring is over-indented
495: D202 No blank lines allowed after function docstring (found 1)
495: D400 First line should end with a period (not 'd')
495: D205 1 blank line required between summary line and description (found 0)
495: D208 Docstring is over-indented
516:37: E127 continuation line over-indented for visual indent
542:24: E127 continuation line over-indented for visual indent
551:20: E126 continuation line over-indented for hanging indent
589: D401 First line should be in imperative mood ('Split', not 'Splits')
589: D400 First line should end with a period (not 's')
589: D205 1 blank line required between summary line and description (found 0)
589: D208 Docstring is over-indented
610: D203 1 blank line required before class docstring (found 0)
610: D205 1 blank line required between summary line and description (found 0)
610: D208 Docstring is over-indented
629: D102 Missing docstring in public method
634:65: E502 the backslash is redundant between brackets
635:49: E128 continuation line under-indented for visual indent
635:57: E502 the backslash is redundant between brackets
636:49: E128 continuation line under-indented for visual indent
636:62: E502 the backslash is redundant between brackets
637:49: E128 continuation line under-indented for visual indent
640:24: E261 at least two spaces before inline comment
643: D401 First line should be in imperative mood ('Update', not 'Updates')
643: D400 First line should end with a period (not 'B')
643: D205 1 blank line required between summary line and description (found 0)
643: D208 Docstring is over-indented
648:57: E502 the backslash is redundant between brackets
650:64: E502 the backslash is redundant between brackets
652:62: E502 the backslash is redundant between brackets
653:23: E128 continuation line under-indented for visual indent
672:63: E502 the backslash is redundant between brackets
675:73: E502 the backslash is redundant between brackets
680:62: E502 the backslash is redundant between brackets
694:65: E502 the backslash is redundant between brackets
706:75: E502 the backslash is redundant between brackets
712:55: E502 the backslash is redundant between brackets
714:54: E502 the backslash is redundant between brackets
715:23: E128 continuation line under-indented for visual indent
717: D400 First line should end with a period (not 'y')
720:28: E261 at least two spaces before inline comment
724:74: E502 the backslash is redundant between brackets
728:74: E502 the backslash is redundant between brackets
730:134: E261 at least two spaces before inline comment
732:14: E261 at least two spaces before inline comment
733:70: E502 the backslash is redundant between brackets
737:142: E261 at least two spaces before inline comment
739:17: E266 too many leading '#' for block comment
740:17: E266 too many leading '#' for block comment
743:20: E261 at least two spaces before inline comment
744:104: E261 at least two spaces before inline comment
746: D401 First line should be in imperative mood ('Keep', not 'Keeps')
746: D400 First line should end with a period (not 'g')
746: D205 1 blank line required between summary line and description (found 0)
746: D208 Docstring is over-indented
766:29: F841 local variable 'e' is assigned to but never used
767:84: E502 the backslash is redundant between brackets
779: D400 First line should end with a period (not 'y')
779: D205 1 blank line required between summary line and description (found 0)
793: D401 First line should be in imperative mood ('Clean', not 'Cleans')
793: D300 Use """triple double quotes""" (found '-quotes)
798: D203 1 blank line required before class docstring (found 0)
798: D205 1 blank line required between summary line and description (found 0)
798: D208 Docstring is over-indented
814: D401 First line should be in imperative mood ('Create', not 'Creates')
814: D205 1 blank line required between summary line and description (found 0)
814: D208 Docstring is over-indented
823:43: E127 continuation line over-indented for visual indent
824:43: E127 continuation line over-indented for visual indent
825:43: E127 continuation line over-indented for visual indent
829: D401 First line should be in imperative mood ('Set', not 'Sets')
829: D400 First line should end with a period (not 'l')
829: D205 1 blank line required between summary line and description (found 0)
829: D208 Docstring is over-indented
837: D205 1 blank line required between summary line and description (found 0)
837: D208 Docstring is over-indented
856:85: E502 the backslash is redundant between brackets
878:28: E126 continuation line over-indented for hanging indent
881:87: E502 the backslash is redundant between brackets
911: D401 First line should be in imperative mood ('Retrieve', not 'Retrieves')
911: D202 No blank lines allowed after function docstring (found 1)
911: D400 First line should end with a period (not 'x')
911: D205 1 blank line required between summary line and description (found 0)
911: D208 Docstring is over-indented
931: D401 First line should be in imperative mood ('Retrieve', not 'Retrieves')
931: D202 No blank lines allowed after function docstring (found 1)
931: D400 First line should end with a period (not 'x')
931: D205 1 blank line required between summary line and description (found 0)
931: D208 Docstring is over-indented
951: D401 First line should be in imperative mood ('Update', not 'Updates')
951: D400 First line should end with a period (not ':')
951: D205 1 blank line required between summary line and description (found 0)
951: D208 Docstring is over-indented
981:55: E502 the backslash is redundant between brackets
982:24: E127 continuation line over-indented for visual indent
983:24: E127 continuation line over-indented for visual indent
983:69: E261 at least two spaces before inline comment
985:174: E261 at least two spaces before inline comment
990: D401 First line should be in imperative mood ('Insert', not 'Inserts')
990: D400 First line should end with a period (not 'e')
990: D205 1 blank line required between summary line and description (found 0)
990: D208 Docstring is over-indented
1018:179: E261 at least two spaces before inline comment
1020:174: E261 at least two spaces before inline comment
1025: D401 First line should be in imperative mood ('Remove', not 'Removes')
1025: D400 First line should end with a period (not 'd')
1025: D205 1 blank line required between summary line and description (found 0)
1025: D208 Docstring is over-indented
1050:179: E261 at least two spaces before inline comment
1052:174: E261 at least two spaces before inline comment
1057: D401 First line should be in imperative mood ('Update', not 'Updates')
1057: D400 First line should end with a period (not 'o')
1057: D205 1 blank line required between summary line and description (found 0)
1057: D208 Docstring is over-indented
1096: D401 First line should be in imperative mood ('Update', not 'Updates')
1096: D205 1 blank line required between summary line and description (found 0)
1096: D208 Docstring is over-indented
1111: D401 First line should be in imperative mood ('Update', not 'Updates')
1111: D400 First line should end with a period (not 'd')
1111: D205 1 blank line required between summary line and description (found 0)
1111: D208 Docstring is over-indented
1139: D401 First line should be in imperative mood ('Remove', not 'Removes')
1139: D400 First line should end with a period (not 'e')
1146: D401 First line should be in imperative mood ('Clean', not 'Cleans')
1146: D400 First line should end with a period (not ')')
1146: D205 1 blank line required between summary line and description (found 0)
1146: D208 Docstring is over-indented
1153:18: E127 continuation line over-indented for visual indent
1157: D401 First line should be in imperative mood ('Remove', not 'Removes')
1157: D400 First line should end with a period (not ')')
1157: D205 1 blank line required between summary line and description (found 0)
1157: D208 Docstring is over-indented
1174:5: E303 too many blank lines (2)
1174: D401 First line should be in imperative mood ('Remove', not 'Removes')
1174: D205 1 blank line required between summary line and description (found 0)
1174: D208 Docstring is over-indented
1212: D203 1 blank line required before class docstring (found 0)
1212: D400 First line should end with a period (not 'x')
1212: D205 1 blank line required between summary line and description (found 0)
1212: D208 Docstring is over-indented
1223: D401 First line should be in imperative mood ('Create', not 'Creates')
1223: D205 1 blank line required between summary line and description (found 0)
1264: D401 First line should be in imperative mood ('Fill', not 'Fills')
1264: D400 First line should end with a period (not 'h')
1264: D205 1 blank line required between summary line and description (found 0)
1264: D208 Docstring is over-indented
1287: D401 First line should be in imperative mood ('Prevent', not 'Prevents')
1287: D208 Docstring is over-indented
1287: D200 One-line docstring should fit on one line with quotes (found 3)
1293: D401 First line should be in imperative mood ('Turn', not 'Turns')
1293: D208 Docstring is over-indented
1293: D200 One-line docstring should fit on one line with quotes (found 3)
1299: D401 First line should be in imperative mood ('Return', not 'Returns')
1299: D209 Multi-line docstring closing quotes should be on a separate line
1299: D202 No blank lines allowed after function docstring (found 1)
1299: D400 First line should end with a period (not 'e')
1299: D205 1 blank line required between summary line and description (found 0)
1299: D208 Docstring is over-indented
1314: D401 First line should be in imperative mood ('Inform', not 'Informs')
1314: D205 1 blank line required between summary line and description (found 0)
1314: D208 Docstring is over-indented
1334: D401 First line should be in imperative mood ('Display', not 'Displays')
1334: D300 Use """triple double quotes""" (found '-quotes)
1341: D401 First line should be in imperative mood ('Return', not 'Returns')
1341: D300 Use """triple double quotes""" (found '-quotes)
1345: D401 First line should be in imperative mood ('Print', not 'Prints')
1345: D300 Use """triple double quotes""" (found '-quotes)
1349: D202 No blank lines allowed after function docstring (found 1)
1349: D300 Use """triple double quotes""" (found '-quotes)
1362:62: E502 the backslash is redundant between brackets
1363:17: E128 continuation line under-indented for visual indent
1365:75: E502 the backslash is redundant between brackets
1366:31: E127 continuation line over-indented for visual indent
1368: D401 First line should be in imperative mood ('Fetche', not 'Fetches')
1368: D400 First line should end with a period (not 's')
1368: D205 1 blank line required between summary line and description (found 0)
1381:35: E261 at least two spaces before inline comment
1398:73: E502 the backslash is redundant between brackets
1399:25: E128 continuation line under-indented for visual indent
1409:73: E502 the backslash is redundant between brackets
1410:25: E128 continuation line under-indented for visual indent
1466:31: E701 multiple statements on one line (colon)
1487:27: E701 multiple statements on one line (colon)
1490:184: E261 at least two spaces before inline comment
1493:179: E261 at least two spaces before inline comment
1505: D401 First line should be in imperative mood ('Divide', not 'Divides')
1505: D209 Multi-line docstring closing quotes should be on a separate line
1505: D400 First line should end with a period (not ',')
1505: D205 1 blank line required between summary line and description (found 0)
1505: D208 Docstring is over-indented
1527: D209 Multi-line docstring closing quotes should be on a separate line
1527: D205 1 blank line required between summary line and description (found 0)
1538:81: E502 the backslash is redundant between brackets
1539:17: E128 continuation line under-indented for visual indent
1542:63: E502 the backslash is redundant between brackets
1543:21: E128 continuation line under-indented for visual indent
1545: D401 First line should be in imperative mood ('Keep', not 'Keeps')
1545: D400 First line should end with a period (not 'g')
1545: D205 1 blank line required between summary line and description (found 0)
1545: D208 Docstring is over-indented
1565:9: B901 blind except: statement
1569:5: E303 too many blank lines (2)
1569: D401 First line should be in imperative mood ('Fetche', not 'Fetches')
1569: D400 First line should end with a period (not 's')
1569: D205 1 blank line required between summary line and description (found 0)
1585: D401 First line should be in imperative mood ('Delete', not 'Deletes')
1585: D209 Multi-line docstring closing quotes should be on a separate line
1585: D400 First line should end with a period (not 'w')
1585: D205 1 blank line required between summary line and description (found 0)
1585: D208 Docstring is over-indented
1588:82: E502 the backslash is redundant between brackets
1589:17: E128 continuation line under-indented for visual indent
1599:80: E502 the backslash is redundant between brackets
1600:17: E128 continuation line under-indented for visual indent
1602: D401 First line should be in imperative mood ('Find', not 'Finds')
1602: D200 One-line docstring should fit on one line with quotes (found 3)
1611: D400 First line should end with a period (not 'r')
1611: D205 1 blank line required between summary line and description (found 0)
1635: D400 First line should end with a period (not 'e')
1653:35: E261 at least two spaces before inline comment
1684: D400 First line should end with a period (not 'e')
1686:9: E266 too many leading '#' for block comment
1692:19: E261 at least two spaces before inline comment
1694:9: E266 too many leading '#' for block comment
1697:17: E127 continuation line over-indented for visual indent
1702: D202 No blank lines allowed after function docstring (found 1)
1702: D400 First line should end with a period (not 'y')
1702: D205 1 blank line required between summary line and description (found 0)
1726:15: E261 at least two spaces before inline comment
1728:16: E713 test for membership should be 'not in'
1741:49: E713 test for membership should be 'not in'
1761:29: E128 continuation line under-indented for visual indent
1762:33: E128 continuation line under-indented for visual indent
1767:21: E126 continuation line over-indented for hanging indent
1778:13: E128 continuation line under-indented for visual indent
1779:13: E128 continuation line under-indented for visual indent
1802:13: E128 continuation line under-indented for visual indent
1803:13: E128 continuation line under-indented for visual indent
1819:13: E126 continuation line over-indented for hanging indent
1824:1: E302 expected 2 blank lines, found 1
1832:1: E302 expected 2 blank lines, found 1
1832: D210 No whitespaces allowed surrounding docstring text
1832: D400 First line should end with a period (not 'e')
1832: D205 1 blank line required between summary line and description (found 0)
1866:78: E502 the backslash is redundant between brackets
1867:17: E128 continuation line under-indented for visual indent
1880:1: E302 expected 2 blank lines, found 1
1880: D210 No whitespaces allowed surrounding docstring text
1887: D210 No whitespaces allowed surrounding docstring text
1887: D401 First line should be in imperative mood ('Find', not 'Finds')
1887: D400 First line should end with a period (not ']')
1887: D205 1 blank line required between summary line and description (found 0)
1887: D208 Docstring is over-indented
1906:36: E127 continuation line over-indented for visual indent
1912:41: E127 continuation line over-indented for visual indent
1915:36: E127 continuation line over-indented for visual indent
1921:41: E127 continuation line over-indented for visual indent
1926:36: E127 continuation line over-indented for visual indent
1933:41: E127 continuation line over-indented for visual indent
1954: D210 No whitespaces allowed surrounding docstring text
1954: D401 First line should be in imperative mood ('Find', not 'Finds')
1954: D400 First line should end with a period (not ']')
1954: D205 1 blank line required between summary line and description (found 0)
1954: D208 Docstring is over-indented
1994:48: E261 at least two spaces before inline comment
2000: D401 First line should be in imperative mood ('Find', not 'Finds')
2000: D205 1 blank line required between summary line and description (found 0)
2000: D208 Docstring is over-indented
2016: D401 First line should be in imperative mood ('Get', not 'Gets')
2016: D400 First line should end with a period (not 'n')
2016: D205 1 blank line required between summary line and description (found 0)
2016: D208 Docstring is over-indented
2051: D401 First line should be in imperative mood ('Get', not 'Gets')
2051: D400 First line should end with a period (not 'e')
2051: D205 1 blank line required between summary line and description (found 0)
2051: D208 Docstring is over-indented
2069: D401 First line should be in imperative mood ('Remove', not 'Removes')
2069: D205 1 blank line required between summary line and description (found 0)
2069: D208 Docstring is over-indented
2093: D401 First line should be in imperative mood ('Decide', not 'Decides')
2093: D205 1 blank line required between summary line and description (found 0)
2093: D208 Docstring is over-indented
2102: D205 1 blank line required between summary line and description (found 0)
2102: D208 Docstring is over-indented
2135: D401 First line should be in imperative mood ('Run', not 'Runs')
2135: D205 1 blank line required between summary line and description (found 0)
2135: D208 Docstring is over-indented
2191:85: E502 the backslash is redundant between brackets
2192:56: E128 continuation line under-indented for visual indent
2192:86: E502 the backslash is redundant between brackets
2193:56: E128 continuation line under-indented for visual indent
2199:5: E303 too many blank lines (2)
2220:29: E126 continuation line over-indented for hanging indent
2259:29: E126 continuation line over-indented for hanging indent
2271:25: E126 continuation line over-indented for hanging indent
2298:29: E126 continuation line over-indented for hanging indent
2312:25: E126 continuation line over-indented for hanging indent
2337:5: E303 too many blank lines (2)
2341:1: E266 too many leading '#' for block comment


1: D100 Missing docstring in public module
20:1: E402 module level import not at top of file
22:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
34:1: I100 Imports statements are in the wrong order. from intbitset should be before from six
34:1: E402 module level import not at top of file
36:1: E402 module level import not at top of file
37:1: E402 module level import not at top of file
38:1: I101 Imported names are in the wrong order. Should be beautify_range_list, create_range_list, kill_sleepy_mysql_threads
38:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine should be before from invenio.legacy.dbquery
38:1: E402 module level import not at top of file
40:1: E402 module level import not at top of file
41:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be task_get_option, task_sleep_now_if_required, task_update_progress, task_update_status, write_message
42: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
46:1: I101 Imported names are in the wrong order. Should be deserialize_via_marshal, serialize_via_marshal
46:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
50:1: I100 Imports statements are in the wrong order. from MySQLdb should be before from sqlalchemy.exc
50:1: I201 Missing newline before sections or imports.
50:1: E402 module level import not at top of file
53:13: E261 at least two spaces before inline comment
56:28: E261 at least two spaces before inline comment
57:27: E261 at least two spaces before inline comment
58:30: E261 at least two spaces before inline comment
61:1: E302 expected 2 blank lines, found 1
61: D101 Missing docstring in public class
62: D102 Missing docstring in public method
65:5: E301 expected 1 blank line, found 0
65: D102 Missing docstring in public method
67:22: W602 deprecated form of raising exception
74:17: E261 at least two spaces before inline comment
75:25: E261 at least two spaces before inline comment
78:1: E302 expected 2 blank lines, found 1
78: D401 First line should be in imperative mood ('Return', not 'Returns')
78: D300 Use """triple double quotes""" (found '-quotes)
100:1: E302 expected 2 blank lines, found 1
100: D401 First line should be in imperative mood ('Return', not 'Returns')
100: D300 Use """triple double quotes""" (found '-quotes)
127:32: E225 missing whitespace around operator
138:36: E225 missing whitespace around operator
142:42: E231 missing whitespace after ','
146:1: E302 expected 2 blank lines, found 1
146: D203 1 blank line required before class docstring (found 0)
146: D300 Use """triple double quotes""" (found '-quotes)
149: D401 First line should be in imperative mood ('Create', not 'Creates')
149: D300 Use """triple double quotes""" (found '-quotes)
157: D401 First line should be in imperative mood ('Return', not 'Returns')
157: D209 Multi-line docstring closing quotes should be on a separate line
157: D202 No blank lines allowed after function docstring (found 1)
157: D400 First line should end with a period (not 'e')
157: D205 1 blank line required between summary line and description (found 0)
157: D208 Docstring is over-indented
166:75: E703 statement ends with a semicolon
172: D401 First line should be in imperative mood ('Clean', not 'Cleans')
172: D300 Use """triple double quotes""" (found '-quotes)
174:19: E225 missing whitespace around operator
176: D401 First line should be in imperative mood ('Update', not 'Updates')
176: D400 First line should end with a period (not 'B')
176: D205 1 blank line required between summary line and description (found 0)
176: D208 Docstring is over-indented
181:72: E231 missing whitespace after ','
182:65: E502 the backslash is redundant between brackets
183:17: E128 continuation line under-indented for visual indent
192:17: E122 continuation line missing indentation or outdented
202:31: E225 missing whitespace around operator
205:62: E502 the backslash is redundant between brackets
206:17: E128 continuation line under-indented for visual indent
214:17: E122 continuation line missing indentation or outdented
219:17: E122 continuation line missing indentation or outdented
228:17: E122 continuation line missing indentation or outdented
233:17: E122 continuation line missing indentation or outdented
245:29: E231 missing whitespace after ','
254:35: E231 missing whitespace after ','
254:40: E231 missing whitespace after ','
254: D202 No blank lines allowed after function docstring (found 1)
254: D400 First line should end with a period (not '1')
254: D205 1 blank line required between summary line and description (found 0)
263:18: E231 missing whitespace after ','
278: D400 First line should end with a period (not 'y')
282:28: E261 at least two spaces before inline comment
293:14: E261 at least two spaces before inline comment
303:21: E266 too many leading '#' for block comment
305:20: E261 at least two spaces before inline comment
311: D401 First line should be in imperative mood ('Display', not 'Displays')
311: D300 Use """triple double quotes""" (found '-quotes)
318: D401 First line should be in imperative mood ('Return', not 'Returns')
318: D300 Use """triple double quotes""" (found '-quotes)
322: D401 First line should be in imperative mood ('Print', not 'Prints')
322: D300 Use """triple double quotes""" (found '-quotes)
326: D202 No blank lines allowed after function docstring (found 1)
326: D300 Use """triple double quotes""" (found '-quotes)
339:62: E502 the backslash is redundant between brackets
340:17: E128 continuation line under-indented for visual indent
342:75: E502 the backslash is redundant between brackets
343:31: E127 continuation line over-indented for visual indent
345: D209 Multi-line docstring closing quotes should be on a separate line
345: D205 1 blank line required between summary line and description (found 0)
355: D401 First line should be in imperative mood ('Fetche', not 'Fetches')
355: D400 First line should end with a period (not 's')
355: D205 1 blank line required between summary line and description (found 0)
368:35: E261 at least two spaces before inline comment
374:74: E231 missing whitespace after ','
383:69: E502 the backslash is redundant between brackets
384:25: E128 continuation line under-indented for visual indent
393:69: E502 the backslash is redundant between brackets
394:25: E128 continuation line under-indented for visual indent
403:51: E231 missing whitespace after ','
403:64: E231 missing whitespace after ','
408:43: E231 missing whitespace after ','
408:56: E231 missing whitespace after ','
410: D205 1 blank line required between summary line and description (found 0)
410: D208 Docstring is over-indented
424:38: E231 missing whitespace after ','
426:35: E231 missing whitespace after ','
437:27: E201 whitespace after '('
443:5: E303 too many blank lines (2)
446:9: F841 local variable 'normalize' is assigned to but never used
448:42: E231 missing whitespace after ','
462:13: F841 local variable 'nb_total_to_read' is assigned to but never used
463:13: F841 local variable 'verbose_idx' is assigned to but never used
467:42: E701 multiple statements on one line (colon)
468:73: E261 at least two spaces before inline comment
469:56: E231 missing whitespace after ','
472:27: E701 multiple statements on one line (colon)
501: D209 Multi-line docstring closing quotes should be on a separate line
501: D205 1 blank line required between summary line and description (found 0)
512:81: E502 the backslash is redundant between brackets
513:17: E128 continuation line under-indented for visual indent
516:63: E502 the backslash is redundant between brackets
517:21: E128 continuation line under-indented for visual indent
519: D401 First line should be in imperative mood ('Adds/delete', not 'Adds/deletes')
519: D300 Use """triple double quotes""" (found '-quotes)
529:9: B901 blind except: statement
533:5: E303 too many blank lines (2)
533: D401 First line should be in imperative mood ('Fetche', not 'Fetches')
533: D400 First line should end with a period (not 's')
533: D205 1 blank line required between summary line and description (found 0)
540:42: E231 missing whitespace after ','
544: D401 First line should be in imperative mood ('Delete', not 'Deletes')
544: D209 Multi-line docstring closing quotes should be on a separate line
544: D400 First line should end with a period (not 'w')
544: D205 1 blank line required between summary line and description (found 0)
544: D208 Docstring is over-indented
547:82: E502 the backslash is redundant between brackets
548:17: E128 continuation line under-indented for visual indent
549:39: E231 missing whitespace after ','
558:80: E502 the backslash is redundant between brackets
559:17: E128 continuation line under-indented for visual indent
561: D401 First line should be in imperative mood ('Find', not 'Finds')
561: D200 One-line docstring should fit on one line with quotes (found 3)
569: D400 First line should end with a period (not 'r')
569: D205 1 blank line required between summary line and description (found 0)
593: D400 First line should end with a period (not 'e')
611:35: E261 at least two spaces before inline comment
617:74: E231 missing whitespace after ','
637:51: E231 missing whitespace after ','
637:64: E231 missing whitespace after ','
642:43: E231 missing whitespace after ','
642:56: E231 missing whitespace after ','
645: D400 First line should end with a period (not 'e')
647:9: E266 too many leading '#' for block comment
651:21: E225 missing whitespace around operator
652:80: E231 missing whitespace after ','
652:84: E231 missing whitespace after ','
652:64: E228 missing whitespace around modulo operator
653:19: E261 at least two spaces before inline comment
655:9: E266 too many leading '#' for block comment
657:151: E502 the backslash is redundant between brackets
658:13: E128 continuation line under-indented for visual indent
661: D202 No blank lines allowed after function docstring (found 1)
681:30: E225 missing whitespace around operator
684:15: E261 at least two spaces before inline comment
686:16: E713 test for membership should be 'not in'
698:49: E713 test for membership should be 'not in'
699:53: E231 missing whitespace after ','
711:29: F841 local variable 'sign' is assigned to but never used
726:1: E302 expected 2 blank lines, found 1
726: D400 First line should end with a period (not 'k')
726: D205 1 blank line required between summary line and description (found 0)
754:70: E231 missing whitespace after ','
754:82: E231 missing whitespace after ','
755:73: E231 missing whitespace after ','
755:85: E231 missing whitespace after ','
756:32: E261 at least two spaces before inline comment
756:33: E262 inline comment should start with '# '
757:64: E261 at least two spaces before inline comment
757:65: E262 inline comment should start with '# '
758:9: F841 local variable 'function' is assigned to but never used
758:44: E231 missing whitespace after ','
771:51: E231 missing whitespace after ','
787:51: E231 missing whitespace after ','
799:45: E231 missing whitespace after ','
813:71: E502 the backslash is redundant between brackets
814:22: E128 continuation line under-indented for visual indent
827:1: E302 expected 2 blank lines, found 1
827: D400 First line should end with a period (not 'r')
830:40: E231 missing whitespace after ','
836:41: E231 missing whitespace after ','
836:49: E225 missing whitespace around operator
847:69: E231 missing whitespace after ','
857:1: E302 expected 2 blank lines, found 1
857: D401 First line should be in imperative mood ('Return', not 'Returns')
857: D202 No blank lines allowed after function docstring (found 1)
877:1: E302 expected 2 blank lines, found 1
890:29: F841 local variable 'e' is assigned to but never used
894:1: E302 expected 2 blank lines, found 1
894: D401 First line should be in imperative mood ('Check', not 'Checks')
905:36: E225 missing whitespace around operator
924:97: E231 missing whitespace after ','
924:99: E231 missing whitespace after ','
935:1: E302 expected 2 blank lines, found 1
935: D401 First line should be in imperative mood ('Show', not 'Shows')
935: D202 No blank lines allowed after function docstring (found 1)
948:19: E225 missing whitespace around operator
950:22: E225 missing whitespace around operator
954:10: E225 missing whitespace around operator
955:10: E225 missing whitespace around operator
957:7: E225 missing whitespace around operator
960:55: E231 missing whitespace after ','
960:77: E231 missing whitespace after ','
962:1: E302 expected 2 blank lines, found 1
962: D401 First line should be in imperative mood ('Update', not 'Updates')
962: D209 Multi-line docstring closing quotes should be on a separate line
962: D205 1 blank line required between summary line and description (found 0)
983:44: E261 at least two spaces before inline comment
983:45: E262 inline comment should start with '# '
1001:76: E225 missing whitespace around operator
1015:79: E225 missing whitespace around operator
1019:10: E261 at least two spaces before inline comment
1019:11: E262 inline comment should start with '# '
1035:77: E225 missing whitespace around operator
1060:76: E225 missing whitespace around operator
1082:76: E225 missing whitespace around operator
1111:17: E266 too many leading '#' for block comment
1114:74: E225 missing whitespace around operator
1140:72: E225 missing whitespace around operator
1147: D103 Missing docstring in public function
1154:1: E302 expected 2 blank lines, found 1
1154: D103 Missing docstring in public function
1158:1: E302 expected 2 blank lines, found 1
1158: D103 Missing docstring in public function
1169:9: E116 unexpected indentation (comment)
1171:1: E302 expected 2 blank lines, found 1
1171: D401 First line should be in imperative mood ('Return', not 'Returns')
1171: D209 Multi-line docstring closing quotes should be on a separate line
1171: D205 1 blank line required between summary line and description (found 0)
1185:112: E221 multiple spaces before operator
1191:25: F841 local variable 'e' is assigned to but never used
1195:1: E302 expected 2 blank lines, found 1
1195: D400 First line should end with a period (not 'd')


1: D400 First line should end with a period (not 'e')
23:1: I100 Imports statements are in the wrong order. from pprint should be before from string
24:1: I100 Imports statements are in the wrong order. import os should be before from pprint
29:1: I101 Imported names are in the wrong order. Should be task_low_level_submission, task_update_progress, write_message
30:30: E126 continuation line over-indented for hanging indent
34:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from invenio.legacy.bibsched.bibtask
35:1: I101 Imported names are in the wrong order. Should be get_collection_reclist, get_fieldvalues, record_exists, search_pattern
36:36: E126 continuation line over-indented for hanging indent
41:1: I101 Imported names are in the wrong order. Should be assure_quality, encode_video
44:41: E126 continuation line over-indented for hanging indent
47:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.cli should be before from invenio.modules.encoder.profiles
49:1: I100 Imports statements are in the wrong order. from invenio.modules.encoder.metadata should be before from invenio.modules.encoder.utils
50:41: E126 continuation line over-indented for hanging indent
52:1: I101 Imported names are in the wrong order. Should be chose2, generate_timestamp, getval
52:1: F999 redefinition of unused 'chose2' from line 48
53:1: I101 Imported names are in the wrong order. Should be CFG_BIBENCODE_ASPECT_RATIO_MARC_FIELD, CFG_BIBENCODE_DAEMON_DIR_NEWJOBS, CFG_BIBENCODE_PBCORE_MARC_XSLT
53:1: I100 Imports statements are in the wrong order. from invenio.modules.encoder.config should be before from invenio.modules.encoder.utils
54:39: E126 continuation line over-indented for hanging indent
58:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.modules.encoder.config
59:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.ext.email
63:1: I100 Imports statements are in the wrong order. import invenio.config should be before from invenio.utils.json
73:1: E302 expected 2 blank lines, found 1
73: D401 First line should be in imperative mood ('Send', not 'Sends')
73: D400 First line should end with a period (not 'g')
73: D205 1 blank line required between summary line and description (found 0)
84:13: E128 continuation line under-indented for visual indent
85:13: E128 continuation line under-indented for visual indent
86:13: E128 continuation line under-indented for visual indent
87:13: E128 continuation line under-indented for visual indent
88:13: E128 continuation line under-indented for visual indent
90:14: E128 continuation line under-indented for visual indent
98:1: E302 expected 2 blank lines, found 1
98: D401 First line should be in imperative mood ('Send', not 'Sends')
98: D205 1 blank line required between summary line and description (found 0)
116:13: E128 continuation line under-indented for visual indent
117:13: E128 continuation line under-indented for visual indent
126:13: E128 continuation line under-indented for visual indent
127:13: E128 continuation line under-indented for visual indent
129:14: E128 continuation line under-indented for visual indent
130:14: E128 continuation line under-indented for visual indent
131:14: E128 continuation line under-indented for visual indent
134:14: E128 continuation line under-indented for visual indent
135:14: E128 continuation line under-indented for visual indent
136:14: E128 continuation line under-indented for visual indent
144:1: E302 expected 2 blank lines, found 1
144: D401 First line should be in imperative mood ('Send', not 'Sends')
144: D205 1 blank line required between summary line and description (found 0)
160:13: E128 continuation line under-indented for visual indent
161:13: E126 continuation line over-indented for hanging indent
167:13: E128 continuation line under-indented for visual indent
168:13: E128 continuation line under-indented for visual indent
170:14: E128 continuation line under-indented for visual indent
171:14: E128 continuation line under-indented for visual indent
172:14: E128 continuation line under-indented for visual indent
175:14: E128 continuation line under-indented for visual indent
176:14: E128 continuation line under-indented for visual indent
177:14: E128 continuation line under-indented for visual indent
185:1: E302 expected 2 blank lines, found 1
185: D210 No whitespaces allowed surrounding docstring text
185: D401 First line should be in imperative mood ('Generate', not 'Generates')
185: D205 1 blank line required between summary line and description (found 0)
185: D208 Docstring is over-indented
196:1: E302 expected 2 blank lines, found 1
196: D210 No whitespaces allowed surrounding docstring text
196: D401 First line should be in imperative mood ('Store', not 'Stores')
196: D400 First line should end with a period (not 's')
196: D205 1 blank line required between summary line and description (found 0)
196: D208 Docstring is over-indented
205:1: E302 expected 2 blank lines, found 1
205: D401 First line should be in imperative mood ('Remove', not 'Removes')
205: D400 First line should end with a period (not 'r')
205: D205 1 blank line required between summary line and description (found 0)
229:25: E128 continuation line under-indented for visual indent
230:25: E128 continuation line under-indented for visual indent
231:25: E128 continuation line under-indented for visual indent
232:25: E128 continuation line under-indented for visual indent
246:1: E302 expected 2 blank lines, found 1
246: D210 No whitespaces allowed surrounding docstring text
246: D401 First line should be in imperative mood ('Create', not 'Creates')
246: D400 First line should end with a period (not 'n')
246: D205 1 blank line required between summary line and description (found 0)
247:29: E126 continuation line over-indented for hanging indent
262:1: E302 expected 2 blank lines, found 1
262: D210 No whitespaces allowed surrounding docstring text
262: D401 First line should be in imperative mood ('Create', not 'Creates')
262: D400 First line should end with a period (not 'a')
262: D205 1 blank line required between summary line and description (found 0)
279:1: E302 expected 2 blank lines, found 1
279: D210 No whitespaces allowed surrounding docstring text
279: D401 First line should be in imperative mood ('Create', not 'Creates')
279: D400 First line should end with a period (not 's')
279: D205 1 blank line required between summary line and description (found 0)
302:1: E302 expected 2 blank lines, found 1
302: D210 No whitespaces allowed surrounding docstring text
302: D401 First line should be in imperative mood ('Create', not 'Creates')
302: D400 First line should end with a period (not 'y')
302: D205 1 blank line required between summary line and description (found 0)
303:21: E126 continuation line over-indented for hanging indent
325:1: E302 expected 2 blank lines, found 1
325: D210 No whitespaces allowed surrounding docstring text
325: D401 First line should be in imperative mood ('Check', not 'Checks')
325: D400 First line should end with a period (not 'y')
325: D205 1 blank line required between summary line and description (found 0)
331: D210 No whitespaces allowed surrounding docstring text
331: D401 First line should be in imperative mood ('Sanitize', not 'Sanitizes')
331: D400 First line should end with a period (not 's')
331: D200 One-line docstring should fit on one line with quotes (found 2)
360:5: E129 visually indented line with same indent as next logical line
362:21: E128 continuation line under-indented for visual indent
378:1: E302 expected 2 blank lines, found 1
378: D210 No whitespaces allowed surrounding docstring text
378: D401 First line should be in imperative mood ('Processe', not 'Processes')
378: D202 No blank lines allowed after function docstring (found 1)
378: D400 First line should end with a period (not 'y')
387: D210 No whitespaces allowed surrounding docstring text
387: D401 First line should be in imperative mood ('Create', not 'Creates')
387: D400 First line should end with a period (not 'd')
387: D200 One-line docstring should fit on one line with quotes (found 2)
390:36: E225 missing whitespace around operator
404:5: E266 too many leading '#' for block comment
407:5: E266 too many leading '#' for block comment
410:5: E266 too many leading '#' for block comment
420:5: E266 too many leading '#' for block comment
435:21: E129 visually indented line with same indent as next logical line
438:21: E266 too many leading '#' for block comment
440:25: E266 too many leading '#' for block comment
449:27: E128 continuation line under-indented for visual indent
452:13: E266 too many leading '#' for block comment
455:5: E266 too many leading '#' for block comment
462:5: E266 too many leading '#' for block comment
470:5: E266 too many leading '#' for block comment
473:5: E266 too many leading '#' for block comment
477:5: E266 too many leading '#' for block comment
485:13: E266 too many leading '#' for block comment
486:13: E266 too many leading '#' for block comment
487:13: E266 too many leading '#' for block comment
488:13: E266 too many leading '#' for block comment
490:27: E128 continuation line under-indented for visual indent
492:37: E126 continuation line over-indented for hanging indent
495:13: E266 too many leading '#' for block comment
496:13: E266 too many leading '#' for block comment
500:21: E126 continuation line over-indented for hanging indent
517:28: E128 continuation line under-indented for visual indent
519:9: E266 too many leading '#' for block comment
529:13: E266 too many leading '#' for block comment
537:13: E266 too many leading '#' for block comment
542:13: E266 too many leading '#' for block comment
545:13: E266 too many leading '#' for block comment
546:13: E266 too many leading '#' for block comment
548:50: E126 continuation line over-indented for hanging indent
554:13: E266 too many leading '#' for block comment
556:18: E126 continuation line over-indented for hanging indent
570:53: E261 at least two spaces before inline comment
576:13: E266 too many leading '#' for block comment
577:15: E271 multiple spaces after keyword
578:17: E266 too many leading '#' for block comment
593:47: E127 continuation line over-indented for visual indent
619:25: W503 line break before binary operator
620:25: E128 continuation line under-indented for visual indent
622:28: E128 continuation line under-indented for visual indent
623:28: E128 continuation line under-indented for visual indent
624:28: E126 continuation line over-indented for hanging indent
634:13: E266 too many leading '#' for block comment
636:17: E266 too many leading '#' for block comment
637:17: E266 too many leading '#' for block comment
640:21: E266 too many leading '#' for block comment
641:21: E266 too many leading '#' for block comment
644:21: E266 too many leading '#' for block comment
647:21: E266 too many leading '#' for block comment
651:21: E266 too many leading '#' for block comment
655:21: E266 too many leading '#' for block comment
656:21: E266 too many leading '#' for block comment
660:35: E128 continuation line under-indented for visual indent
663:37: E126 continuation line over-indented for hanging indent
668:13: E266 too many leading '#' for block comment
680:5: E266 too many leading '#' for block comment
684:5: E266 too many leading '#' for block comment
689:9: E266 too many leading '#' for block comment
702:44: E251 unexpected spaces around keyword / parameter equals
702:46: E251 unexpected spaces around keyword / parameter equals
703:50: E251 unexpected spaces around keyword / parameter equals
703:52: E251 unexpected spaces around keyword / parameter equals
704:49: E251 unexpected spaces around keyword / parameter equals
704:51: E251 unexpected spaces around keyword / parameter equals
737:5: E266 too many leading '#' for block comment
747:55: E721 do not compare types, use 'isinstance()'
747:69: E202 whitespace before ')'
757:32: E128 continuation line under-indented for visual indent
758:32: E128 continuation line under-indented for visual indent
759:32: E128 continuation line under-indented for visual indent
761:1: W391 blank line at end of file