there is a `stub_current_user(your_user_here)` test helper that makes all controllers respond to `current_user` with your user


@lpinca thank you!
I agree with you, I think it can be released as 3.2.
Yes the event list needs to be updated, I will try to get to it tomorrow however, I always think it would be awesome to be able to reuse an existing Primus spark and make it a multiplex spark but I haven't had the time to investigate further on this.


finish readme.md


ResultsSchema (sanyalj) - i386-Windows-7-VisualStudio-12: OK (1675 of 1676 tests passed)

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


90946736_WSHP_#4567 (Nigusse) - x86_64-MacOS-10.9-clang: OK (1660 of 1671 tests passed)

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


Is there any screen that shows the username of the logged in user? I don't know of one but maybe there is


Fill In Blanks in purpose, add user instructions.


I forgot the markdown linter in the gemfile


it's not related? I cannot reproduce your issue, tested with Chrome and Firefox...


Memo: Check all places where  rateMedia is called. Pretty sure I forgot to update the manual call


Can you change this to inLinks and outLinks?  And change the counters back to numInLinks/numOutLinks or something.

The reason is that inLinks/outLinks will be storing multiple links and I was a little confused when I was accessing the variable elsewhere.


:sparkles: :+1:


Excellent


@gabbiano %appdata%/PokuBot/config.properties


Sending a message should be a single command, args could be:
* int devFile (our device file for the I2C bus)
* uint8_t sensorAddress
* uint8_t regToWrite
* uint8_t messageToSend
* uint8_t returnData


esto esta fulero


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


Is there any way to break up this visit method? Maybe a bunch of protected methods such as visitExpression(), visitOperation(), etc etc. It would vastly improve readability here.


The commit is a lie!


Not seeing the ability category file changed to match. Added to the type Maneuver Selection. Looking at my copy I have a disconnect between Maneuver in one and Maneuvers in the other.


Successfully works with moving the defines to the headers. Work on making these into function calls is next


comment for a recent add


@bjornnborg implementado um Proxy simples para entender melhor o funcionamento usando a lib disponiveis no JDK.


Thanks for the suggestion, done in 756f024a26708fad03856212b714ac990c84ce95


相对而言的...... 你不看看之前的 printf 用法

-----原始邮件-----
发件人: "Mingye Wang" <notifications@github.com>
发送时间: 2015/3/30 18:33
收件人: "AOSC-Dev/cliinst" <cliinst@noreply.github.com>
抄送: "Jeff Bai" <jeffbaichina@members.fsf.org>
主题: Re: [cliinst] learn more, code clean up, ui improv. (bed62b3)

你说这叫 Clean up？
我以为是写一个 learn_more 然后 learn_more $more_de 呢。
—
Reply to this email directly or view it on GitHub.


ResultsSchema (sanyalj) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1674 of 1676 tests passed)

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


Some of the patches were mangled and would not apply with git am. I will manually rebase the tree to preserve authorship.


@bjornnborg implementado proxy usando CGLib, versao mais aprimorada que a anterior simulando um List com Generics.


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


No because the hash here is not tied.


I added the options hash here to use the regular shell instead of the silent shell, but to no avail.


This change has broken recursive folder content copying on windows 8 when using symlinks. Instead of copying the symlink, it instead creates a junction link which tries to link to the original file as if it was a directory


The hashtags ???


$self->_getVersion() return a string ;) It's ok ;)


ResultsSchema (sanyalj) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


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


Ok, I will review the commit tonight.


meant "forgot to uncomment the lines"


Change from using file to devFile for easier understanding


This does leave less details about why an error state was entered. Does an errorString()-type construct make sense?


So...no more traction?


You can check this post, because already in the database and correct the error.


TEST:
error occured because O_RDWR undeclared


@Olion17 - Fantastic job, well done


This commit was done by me.


I can't edit the code right now which makes me sad.
Pete:
Sudo check your email so you can edit it for me!!!


@leahpadgett done with my reivew. checkpoint complete.


This will be very very slow, since `String#+` expands string in memory every character.

Use:

```ruby
name.each_char.inject([]) do |ary, ch|
  ary << @korean_name_convert[ch]
end.compact.join(' ')
```


this can be reduced to about 50ms.


@leahpadgett even then they might not be!!


@leahpadgett done with my review. checkpoint complete.


Limace.


This is the only thing that caught my eye in this code.  Do we really need to wrap every request in a transaction?  If so, what changed in Django 1.6 that would require this?  There could be a performance impact.  (Were there any specific views or tests that had problems?)


Instead of manually counting `i`, there's `each_with_index`


[![Build Status](https://travis-ci.org/Aravindpogu/Test1.svg?branch=master)](https://travis-ci.org/Aravindpogu/Test1)


It compiles but isn't tested. I just copy & paste from my private 335 repo. May have more errors.


This unsup penalty was introduced 1 year ago by snicolet
It passed STC and LTC fairly easily.

One indirect benefactor was the backward pawns, which received that S(20,10) bonus.
The isolated case was explicitly excluded

There was an attempt to remove it in summer 2014.
Also to remove it only in the RANK_2 case.
The attempts worked at STC but not at LTC.

Since then, the Connected array had gained some complexity,

Last week, this Unsup penalty had been incorporated into the backward array,
so now it is a completely separated case when it kicks in.

I tried to fine tune this "new" unsup with a recent test, without any real benefit.
So maybe it is just noise. ?

In fact, if we have some bonus for supported pawns, (via the connected array)
why should we have also penalties also for the unconnected pawns ?

Finally, since the introduction of unsup 1 year ago, the backward and the isolated arrays had not been tuned at all. That will be the next duty on my list..


Double colon ;)


I think no, unless it's actually needed and used. We can always add something.


you are quick ;)


I think the recents events are already being displayed on the home screen. I did that about a month ago. you just need to add pagination to it.


*grins*


Perhaps related to [changes to the default transaction handling in 1.6](https://docs.djangoproject.com/en/1.7/topics/db/transactions/#transactions-upgrading-from-1-5)?  I am curious as to whether this will improve, worsen, or not change the issues we've occasionally been having with deadlocking in accounting and schedule generation.


These textures look pretty awesome. What's the license of them?


Part of #62


What is the effect when this occurs?


Thanks.


Ah, so should we remove TransactionMiddleware?  I had forgotten about that.


I found a trick for importing colors. Instead of importing all of them on different lines, you can do this:

import static android.graphics.Color.*;


MarkdownDocs (kbenne) - i386-Windows-7-VisualStudio-12: OK (1675 of 1676 tests passed)

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


hrm... ok. no thanks.


hello .Could you assist me on which option to turn this available? Thanks


he was trying to trigger the travis CI test.


Well, node callback functions are defined to be called with the error in first argument, right? Yes, we could throw, but that bypasses the node callback convention.


@Nxt3 Yes,you are right.I thought it could be smaller so the bundle size would be smaller. I'll fix it next update.


Good question. Yes, they do each run in their own process. `npm test` runs the testRunner.js script, which launches a child process for each file in the testAsyncOptions directory.


Should be CC-BY-SA 4.0 like his models. I'll double check and upload a
small readme this evening.


same problem here


oops.  will remove.


Hey Tristan,

I notice that with this commit you reverted this patch:
https://github.com/erlware/relx/commit/18a192ef884535ceb67dffedc8caf77fe4e39b2b
and once again, files generated from bin.dtl fail to run in my local environment.

Your reversion doesn't seem related to the others in this commit: was it accidental?

Thanks,
Jay


@Xfurry, please take a look. So, as FollowerAI we do not have, besides StartFollow and MoveFollow you know is not the same)


Thanks :)


whith your methode! keep calme and see!


It conflicted with something else but I added your name.


Just of interest, is this the preferred style?


@DanielMcInnes max_legs should be 4, since we can make up to 3 transfers. i.e. 4 legs


Thanks James

Date: Mon, 30 Mar 2015 18:17:49 -0700
From: notifications@github.com
To: csse7032-a1@noreply.github.com
CC: d_h_mcinnes@hotmail.com
Subject: Re: [csse7032-a1] Interim checkin - added explanatory text for defintions, axiomatic definitions, and schema. CHanged MAX_LEGS from 4 to 3 (b8d4c3f)

@DanielMcInnes max_legs should be 4, since we can make up to 3 transfers. i.e. 4 legs

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


Hang on, I have go the right idea here, right? :S


喔喔喔！這個好！


Yep, my bad :)

Date: Mon, 30 Mar 2015 18:19:24 -0700
From: notifications@github.com
To: csse7032-a1@noreply.github.com
CC: d_h_mcinnes@hotmail.com
Subject: Re: [csse7032-a1] Interim checkin - added explanatory text for defintions, axiomatic definitions, and schema. CHanged MAX_LEGS from 4 to 3 (b8d4c3f)

Hang on, I have go the right idea here, right? :S

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


metaに下記を追記します。
When using replication slot sets a value for replication_slot_name.


:| That really shouldn't happen... I'll look into it.


Maybe a bug seen in old NVIDIA drivers (?). If you have the latest one, you can test it (and compare to what happens in super).


Will this one work ok? I haven't looked at the EasyBuildError interface yet, but it is perhaps a bit unusual (I assume makefiles is a list?)


Please refer to https://phpunit.de/getting-started.html if you need help with making unit tests in php.


is err missing here as a parameter?


In multiple events there is now methods named getBlock() but return a Location. I feel it would be more appropriate for these methods to be changed to getLocation() since the methods return the location of where the block is.


Can't we simply use:
#ifndef  glVertexAttribDivisor
#   define glVertexAttribDivisor glVertexAttribDivisorARB
#endif
That would make sure that if the 'standard' (not extension) version is there, it will be used (it probably doesn't matter much, it just feels better).


I think returning a double is reasonable, because it just means the count of dots. I don't think there is any unit information about dots...


LOL


curiosity: what is the advantage of doing it this way?


Is the src,target path in err typically or should it also be included?


changing name to test editing


/cc @ryanbrainard FYI, wip.


ResultsSchema (sanyalj) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (657 of 658 tests passed)

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


nice job.


Why did you changed that ?, now you can only define one ip address for the dns server.
It mean that if pfdns crach then the reg/isol network will not work anymore because the device will not be able the resolv anything.
The goal of that was a way to define multiples dns server for the device and if one failled then the device will try the other one.
BTW the ability to set more than one ip for the dns server is usefull for inline network.


Release build also passes.
![hrtest](https://cloud.githubusercontent.com/assets/5778156/6910650/df597f3e-d723-11e4-9d9b-9602d6d9e2f7.jpg)


-> Packages provided from ...


我的手機


Here, too.


this will just break sites other than mangahere.


Also, here.


Good stuff, moving this kind of UI generation out of openlayers


(y)


同名のスロットが既に存在している場合は存在するものを使います。(作成をスキップします)
この場合も返り値は0なので、メッセージを修正します。
PostgreSQL creates or already has the replication_slot($replication_slot_name)


I'm not trying to insult anyone, but with full respect, some "magic commits" from well-known builders are pure placebo that nobody even tested, that doesn't change anything, or that causes more bad than good. Everybody has his own choice, and can commit/use anything he wants, but if you're looking for placebo commits, you won't find them here.

I keep an eye on all projects I'm interested in, to see if I can improve my own flags with additional ones, but if I decided to NOT do so, I had strong reasons.


Here.


動作仕様はコメントで書きます。


AMD has too much to do to improve its compiler. For example, just for fun, I commented the line above and this silly change:
- Halve the "Effective concurrency constrain (Max waves per SIMD)".


names! haha! Always check those cases


For example the reason of not implementing graphite flags is very simple - because they don't work, they cause compiler internal errors, and if something doesn't work, or causes side effects, it shouldn't be commited. Of course you can workaround the issue and apply that flag selectively to some projects, or selectively NOT apply them on some projects, the question is, what is the point of using that flag if it works with like 50% code? Are we playing cat and mouse here, or improving speed for no cost? Because I'm not interested in flags that cause more harm than good, and this is the perfect example.

(Which doesn't mean that I'm not trying to implement them in my own, better way)


To use `for of` syntax, babel requires `babel/polyfill`, so I dropped it and use `Array.prototype.forEach`.


Use bit would be better, we don't need to care about the sign.
https://github.com/ejoy/ejoy2d/commit/16220857a9eb69359f00a795faee4c402057b673


@ceineke Ok, thanks.  I think I'd prefer to add them only when we discover that we need them.  Sound ok?


and start it ... started. ->
and enable automatic start up on the machine boot.


following ->
the following


All what?


Should this have OSError, err ?


Why would a JNDI exception happen here?


:bomb:


Doing that doesn't mean that mysql is running well, it's just mean that you are able to connect.
The old way was a way to test the connection with the username and password defined in pf.conf and a test to see if we are able to do a sql request.
BTW you probably have to grant privileges for a haproxy user.


user name ->
the user name

password ->
the password


Closes #27


@carlosantoniodasilva Haven't had a detailed look. But seems that @matthewd did a merge https://github.com/rails/docrails/commit/ffd2f085a5a55b5db70637c33a5fb14d83571893 - this is enough right?


I think returning a double is reasonable, because it is only the count of the dots, there is no unit information about dots.


I have raised a new issue (#7852) so that this can be discussed in more detail.


It's wrong to throw an exception with the wrong meaning just because it has a nice name. `NamingException` is not about a bad "name" in general, but about JNDI problems. Read the JavaDoc of that exception and you'll see what it's actually supposed to do.


We could try just listing the words and having the picture enlarge on click. The tutorial has a row click handler so we could try to modify that. When we populate the quizzes, I'd like to get each item as an custom object for sure. That might make a lot of things easier such as setting the correct answer, and generating choices.

The tutorial is also right [here](https://www.caveofprogramming.com/guest-posts/custom-listview-with-imageview-and-textview-in-android.html). I modified certain things such as the Adapter's parameters.


Duplicate.  This can be closed.


Hello

Any particular reason why we need this? Indeed, we could log all the outgoing uploader messages, but it would get very wordy, even for debug mode.

Perhaps we need a higher level of debugging, one that allows super verbose logging?


Is that a valid concatenation for the strings?


嗯嗯 …… 我知道你说什么


処理の背景(なぜノードリストの数で処理を分けるのか)が複雑なため、条件を明示しました。
特に不要ということであればelseに変更します。


also updated all dependencies to latest versions


You ->
you

We should describe what lines are added/fixed in the hatohol.conf.


the default player profile is random decks since the runner doesn't load all cards, it blocks on random deck generation. the initialize call can be removed since what is does it setup the player and decks which is done manually here in the subsequent calls.


This should be use syscon.
In fact, the patch send in maillist has already change to
compatible = "hisilicon,aoctrl", "syscon";


De hecho aquí hay que usar el log en ves del print, lo dejamos anotado para la siguiente revisión...


after hatohol database created ->
after hatohol database is created ?

And the above sentence uses DB, but here 'database'.


this killed double tap right?


Does not work as intended. Better use the synchronize method.


r+


missing some variables?


90946736_WSHP_#4567 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1666 of 1677 tests passed)

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


saw approval from jdm
at https://github.com/Adenilson/servo/commit/07915739cbee285f99cea3c88fad73d0def9267a


merging Adenilson/servo/panicOnBorkedURL01 = 07915739 into auto


Adenilson/servo/panicOnBorkedURL01 = 07915739 merged ok, testing candidate = 63346f97


That line was already present:
https://github.com/juliankrispel/autosize/blob/03cb2d0e5ee162bb5b73251e4ef181de0726dce3/package.json#L15


missing a %s


qqqqqqqqqqqqqqqqqqqqqqqqqqqqqq


No


The first case is in-place (`-=`), so there could be some casting going on, but everything should be `float`, so I'm not sure. I don't really know what's up in the second case.


No Magic numbers plz.


Align with existing data plz.


Oh thanks baris, I forgot there were two sets of submit/discard :pensive:


OSError?


Carnicoro Gato tierno


Leave cosmetic changes for another pr plz.


> ${prefix}/etc/hatohol/hatohol.conf.

It is sometimes wrong. In the RPM, ${prefix} is /usr, however, the path is not /usr/etc/hatohol/....


Addition 2


Is there much difference between grabbing Exception vs OSError?


Now I'm just using themes instead of colors; nothing has to be imported.

On Mon, Mar 30, 2015 at 6:05 PM, squidplayer123 <notifications@github.com>
wrote:

> I found a trick for importing colors. Instead of importing all of them on
> different lines, you can do this:
>
> import static android.graphics.Color.*;
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mydogisjibe/SuggestApp/commit/e156bf98a15b08f5bc216570060c78997d8ae316#commitcomment-10479909>
> .
>


move this into db plz.


90946736_WSHP_#4567 (Nigusse) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Client....
Recently we call it web UI or something.


following ->
the following


Well the location and block are really the same thing for these cases, but getBlock is more precise since a Location can also represent something other than a block. I think this is better actually.


same concat issue as further up


in MySQL
in the MySQL command line tool


init script ->
the init script

following ->
the following


> 「PostgreSQLのレプリケーションスロットを利用可能とする」といった内容ではないでしょうか。
Medium: pgsql: Support replication slot.
に変更します

> Pacemakerとしてどのような使い方が新しくできるようになるのか、もしくはどう変わるのか、という観点での内容を書いて欲しいです
下記でいかがでしょうか。
It is enable to use the Replication slot which is the new feature of PostgreSQL 9.4
By using Replication slot, It is not necessary to synchronize to recover slave node in advance.
For the more information of replication slot is following
http://www.postgresql.org/docs/9.4/static/warm-standby.html#STREAMING-REPLICATION-SLOTS


Instead of the number "2", can we have a constant?


Looks good


As being relatively new to apt programming and English not my native language, I often thought about the structure of apt and the names of functions and variables.

Difficult to see through is the length of code, so I would suggest to split it in functional or logical parts. I saw this in different github projects, that multiple python files exist, but only one complete file was the output for installing - never tried out, if a ide/tool supports such things? On the other hand, importing them as modules shouldn't be a problem either.

I really don't like all the globals, because one can never be sure if and where they are initialized, even you don't see they are global.  And I like to have a main(argv) function and a short global section.

One way out of this is using classes, as they have separated name spaces and we could name similar variables equally - same with separated modules.

My proposal:
"apt" is the name of the program, handling the commands, checking options, environment: it's our User Interface.
"setup" describes the superior thing of apt. It is the connection between server and local stuff. As a command ('setup') it initialises the installation. It knows, which setup files will be stored and where to find them ('setup_rc: rc=resources: wrong word right action?').

"installation" describes the output of apt well, as the local part of setup, it deals with the local install (as a command) of packages, does the post_install, reports errors and success of installed packages

"repository" is often used for what osgeo4w download server is, it is the availability of "ressources", it has mirrors, several trees ("architectures") and holds downloadable setup files and packages

"packages", I liked to encapsulate them, containing the metadata and information about the 'content'. They could have a server and a local "status", mainly a version and a installed flag.

It's not mandatory to realize a class structure, but, as you said, words should be clear and intuitiv. As I wrote, its a proposal, hoping to give some impulse.


Does it? I'm not familiar with the code - but I guess the check itself makes sense.
If someone edits the config files and removes all `Listener = ...` lines - then this error message should be triggered.
Or do you mean rephrasing it to say "... at least one Listener in your config."?


@andyjmaclean: I've tidied this up a bit, moving the tests into spec/features per the RSpec 3 convention, and merged into develop.


This should send 'goodbye' for all names, shared and unique (10.1 <https://tools.ietf.org/html/rfc6762#section-10.1>).


`origin.url` from git is now mixed with `remove_url` from database... I am not sure about that.


Great work here. An alternative is also possible using `create_list`:

```ruby
  post = create(:post, user: user)
  create_list(:comment, evaluator.num_comments, user: user, post: post)
```


@gogeta95, what language you used earlier? lol :v


Would it be better for you if I have separate branches for unrelated fixes? I'm thinking that might make PR's more self contained and easier for you to merge.

Sorry if this a stupid/obvious question, let's just say I'm still getting the grips with Github PRs


Do note that React's link state mixin doesn't do a binding rather a re-render.


Good work


może warto zmienić nazwę cuton na reconnect?
Nie ma wyrazu cuton, ani cut on w języku angielskim...


I like more informative variable names, and seen the previous one ... something like couchdDocumentSize? .


Hi,

Take last version ?

https://github.com/PrestaShop/PrestaShop/blob/1.6/controllers/front/OrderDetailController.php#L189

Regards


Under the compiler the test of U+017F and U+0053 folding fails. This is because the following issue discussed on Trello has yet to be resolved:

```
The "^(0073)" "^(017F)" case is a little tricky.

In terms of case folding 0053, 0073 and 017F are equal.

The uppercase of 0073 is 0053
The lowercase of 0053 is 0073
The uppercase of 017F is also 0053

I wouldn't expect 017F to be used much, well not until we get a mass of Greek speaking users.

The options we have are:

1. Ignore 017F (but address in the full unicode support module)
   0053 <> 017F
   0073 <> 017F
   Document this in the Unicode proposal
2, Have a special case for equals
 0053 = 0073 = 017F
3. Have a special case for uppercase
uppercase 017F -> 0053
(lowercase 0053 still -> 0073)
4. Have both 2 & 3

I would vote for option 1 but it would be worth checking with Nenad.

I will change the tests to reflect the option chosen.
```


no i %NOW% nie jest funkcją sql, tylko symbolem specjalnym definiowanym przez daemona, dlatego operator() nie jest za nim potrzebny.


啊 删去哪里……

On Tue, Mar 31, 2015 at 11:46 AM CHEN LIYANG <notifications@github.com>
wrote:

> 准备把整个删掉了…
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ojny/oj_judge_x/commit/c559e6a0f6cb526c084d15898f37dff4d6f149da#commitcomment-10481171>
> .
>


I was using the `stub_current_user` method in my test, but when I signed in as another user I could still access the admin page, it's because the code is trying to change the current_user which is getting stubbed.  So I decided to not use `stub_current_user`.


91051416_RadianceParameters (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2170 of 2197 tests passed)

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


I couldn't find one.  I can add something like "Sign in as XXX" next to the "Sign out!" link?


请问在使用myChart.compoent.yAxis.getAxis(0)这个的时候，总是报getAxis()未定义的错误，请问我需要加载component的组件么，config的path和require里面怎么写呢？麻烦了！！！


Thanks, it's fixed.


Oh I see, thanks.  I'll fix it.


The case-folding tests generate a script error under the interpreter. The reason is not obvious. The message is:

```
signify failure
~~~started test~~~ run-all-interp
*** Script error: do-fold has no value
*** Where: do
*** Stack: do
```
do-fold is a function defined in case-folding-test.red.


Its conventional to have a leading space before the closing `%>`


It's from accounts ;)


added Tasks from Challenge 1


In english no problem but in french see attached...logo bottom and links wrong (no activated)
![bug mail ps 1 6 0 14](https://cloud.githubusercontent.com/assets/11722854/6916698/b3a4cf94-d79e-11e4-94da-d10e9102c39a.jpg)
We do not find the origin of the bug ...
Best regards.


Is this OK?


@miq @tfarago @TimoDritschler: this is a pretty deep change but became necessary to make the whole trigger mess more consistent and allow for things like trigger type. I haven't yet updated the Dexela (I don't know when this stuff should be changed) and Concert (I don't know if we should stick with `trigger_mode` there or change to `trigger_source` too).


perche' li togli?


cool


This will cause issues with puppet-server.
It was removed in https://github.com/electrical/puppet-lib-file_concat/pull/8


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


This indentation still doesn't look right


@ultrabug here it is :) removing gpl.


J'ai dû mal rédiger mon message.
Nous avons des postes qui tournent sous Edubuntu 12.04 et pour lesquels
nous n'avons aucun problème de connexion, ni pour les élèves, ni pour
les adultes.
Nous avons voulu tester des postes sous Mint pour différentes raisons.
Ces postes fonctionnent au problème près des connexions adultes. C'est
la raison pour laquelle je pensais que la difficulté pouvait provenir du
script spécifique de cette distribution.

Cordialement

D. Benveniste

Le 31/03/2015 11:05, dane-lyon a écrit :
> Bonjour,
>
> Les comptes utilisateurs "élèves" et "profs" fonctionnent sous Linux
> Mint si la case "client shell linux" est coché dans l'EAD, j'ai même
> testé en vitesse ce matin.
>
> cordialement;
>
>
> Le 31/03/2015 10:40, David Benveniste a écrit :
> > Bonjour,
> >
> > après enquête et divers essais, il apparait que le problème réside dans
> > la connexion des utilisateurs adultes. Les élèves peuvent se connecter
> > sans aucun problème. En revanche, les adultes ne peuvent se logger, le
> > message leur indique que leur compte a été désactivé. Seul les comptes
> > administrateur réseau et administrateur local sont effectifs.
> > Le script client est bien activé par défaut pour les sessions.
> > Il y aurait peut-être un conflit entre le script et l'architecture des
> > comptes sur le serveur mais cela dépasse mes capacités.
> >
> > Cordialement
> > D. Benveniste
> >
> >
> > Le 31/03/2015 09:16, dane-lyon a écrit :
> > > Bonjour,
> > >
> > > Sous Linux Mint, il vaut mieux cocher la case "activer les clients
> shell
> > > linux" dans l'EAD pour les utilisateurs sinon il peux y avoir des
> > > problèmes de connexion, j'ai pu faire le test en créant un utilisateur
> > > sans cette case coché et alors ça indiquait le message que
> > > l'administrateur a désactivé le compte et en la cochant puis en
> > > redémarrant le scribe/client, alors il pouvait se connecter
> normalement.
> > >
> > > En faite si vous voulez déployer du Linux, je vous conseille de mettre
> > > plutôt "Xubuntu" (voir Lubuntu pour les très anciens pc) car c'est
> plus
> > > léger et rapide et il n'y a pas besoin d'avoir la case des clients
> shell
> > > linux coché, de plus Linux Mint est plutôt orienté pour une
> utilisation
> > > familiale/perso/multimedia et non professionnelle et consomme quasi
> > > autant de ressource que Ubuntu/Unity.
> > >
> > >
> > > cordialement;
> > >
> > >
> > > Le 30/03/2015 17:39, David Benveniste a écrit :
> > > > Bonjour,
> > > >
> > > > J'ai installé deux postes sous Mint avec le script téléchargé sur le
> > > > site. La connexion fonctionne avec le compte administrateur mais
> si on
> > > > essaye de se logger avec un compte utilisateur, un message
> indique que
> > > > l'administrateur a désactivé le compte.
> > > > Vérification faite, le compte existe bien dans scribe et reste
> > > > fonctionnel sur des postes sous windows ou Edubuntu 12.04.
> > > > De plus sur un des deux postes (le plus récent), une fois la
> > fenêtre du
> > > > message validée, l'écran devient noir et il n'est plus possible de
> > faire
> > > > quoi que ce soit. Redémarrage brutal du poste obligatoire.
> > > >
> > > >
> > > > Cordialement
> > > >
> > > > D. Benveniste
> > > >
> > > > Le 27/03/2015 15:47, dane-lyon a écrit :
> > > > > Bonjour,
> > > > >
> > > > > Il faut désactiver l'userlist avec le compte local (vous pouvez le
> > > faire
> > > > > avant de lancer le script) et ensuite vous pourrez vous
> connecter en
> > > > > tapant le login et le mdp comme sous Windows, vous pourrez vous
> > > > > connecter a la fois avec un compte du domaine (compte admin du
> > > domaine,
> > > > > compte prof, compte élève) mais aussi avec le compte locale.
> > > > >
> > > > > A noté que Mint est assez exigeant en ressource, si le pc n'est
> > > pas très
> > > > > performant, il vaut mieux utiliser Xubuntu voir Lubuntu.
> > > > >
> > > > > cordialement;
> > > > >
> > > > > Le 27/03/2015 15:32, David Benveniste a écrit :
> > > > > > Le document que j'ai téléchargé ne correspond pas à celui qui
> > > apparait
> > > > > > quand on active le lien de votre message. En faisant un copié
> > > collé de
> > > > > > la page web, j'ai reconstitué un fichier qui a installé le
> > > client sur
> > > > > > scribe.
> > > > > > En revanche, je ne parviens pas à me connecter. Je vois une
> liste
> > > > > > d'utilisateurs (tous ceux du collège) et quand je saisis le
> mot de
> > > > > > passe, la machine tourne dans le vide.
> > > > > > Je ne suis donc pas en mesure de paramétrer la machine en
> > > suivant les
> > > > > > commentaires du script et je ne parviens pas à me connecter
> sur le
> > > > poste
> > > > > > en local.
> > > > > >
> > > > > > Cordialement
> > > > > >
> > > > > > D. Benveniste
> > > > > >
> > > > > > Le 27/03/2015 13:04, dane-lyon a écrit :
> > > > > > > Bonjour,
> > > > > > >
> > > > > > > Nous avons un script d'intégration pour le client Linux Mint
> > > > > 17/17.1 et
> > > > > > > il fonctionne (
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://raw.githubusercontent.com/dane-lyon/clients-linux-scribe/master/client_scribe_linuxmint_17.X.sh
>
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > ) mais il faut bien lire ce qui est en commentaire dans le
> > > script au
> > > > > > > début.
> > > > > > >
> > > > > > > En faite, toutes les dérivés d'Ubuntu fonctionnent avec le
> > script
> > > > > de la
> > > > > > > 14.04 sauf la dérivé avec KDE (Kubuntu) qui n'est pas
> > compatible.
> > > > > > >
> > > > > > > Voici ce qui fonctionne :
> > > > > > >
> > > > > > > - Ubuntu 14.04
> > > > > > > - Xubuntu 14.04
> > > > > > > - Lubuntu 14.04
> > > > > > > - Ubuntu Gnome 14.04
> > > > > > > - Ubuntu Mate 14.04
> > > > > > > - Linux Mint 17 Cinnamon/Mate
> > > > > > > - Linux Mint 17.1 Cinnamon/Mate
> > > > > > >
> > > > > > > A noté que Debian n'est pas compatible a notre script mais il
> > > y a le
> > > > > > > script crée par quelqu'un d'autre pour ça.
> > > > > > >
> > > > > > >
> > > > > > > Cordialement;
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Le 27/03/2015 12:14, David Benveniste a écrit :
> > > > > > > >
> > > > > > > > Bonjour,
> > > > > > > >
> > > > > > > > j'ai testé avec succès le script sur une distribution
> Edubuntu
> > > > > 12.04.
> > > > > > > > En revanche, je ne parviens pas à cloner le poste avec
> Oscar.
> > > > > > > > Je viens d'essayer d'utiliser le script client avec une
> > > > distribution
> > > > > > > > Mint 17.1 et la console me retourne le message suivant :
> > Syntax
> > > > > error
> > > > > > > > : newline unexpected
> > > > > > > >
> > > > > > > > —
> > > > > > > > Reply to this email directly or view it on GitHub
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10429363>.
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Simon Bernard
> > > > > > > académie de Lyon - Délégation Académique au Numérique Éducatif
> > > > > > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/> *Simon
> > > Bernard
> > > > > > > Rectorat de Lyon
> > > > > > > DANE - Délégation Académique au Numérique Éducatif
> > > > > > > Assistance de niveau 2 aux utilisateurs du réseau pédagogique
> > > > > > > * Téléphone : 04 72 80 64 88
> > > > > > >
> > > > > > > Adresse postale : 92 rue de Marseille - BP 7227 - 69354 Lyon
> > > > Cedex 07
> > > > > > > Locaux site Croix-Rousse (47 rue Philippe de Lassalle 69004
> > Lyon)
> > > > > > > *http://www.ac-lyon.fr*
> > > > > > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/>
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly or view it on GitHub
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10430053>.
> > > > > > >
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly or view it on GitHub
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10432751>.
> > > > > >
> > > > >
> > > > > --
> > > > > Simon Bernard
> > > > > académie de Lyon - Délégation Académique au Numérique Éducatif
> > > > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/> *Simon
> Bernard
> > > > > Rectorat de Lyon
> > > > > DANE - Délégation Académique au Numérique Éducatif
> > > > > Assistance de niveau 2 aux utilisateurs du réseau pédagogique
> > > > > * Téléphone : 04 72 80 64 88
> > > > >
> > > > > Adresse postale : 92 rue de Marseille - BP 7227 - 69354 Lyon
> > Cedex 07
> > > > > Locaux site Croix-Rousse (47 rue Philippe de Lassalle 69004 Lyon)
> > > > > *http://www.ac-lyon.fr*
> > > > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/>
> > > > >
> > > > > —
> > > > > Reply to this email directly or view it on GitHub
> > > > >
> > > >
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10432996>.
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > >
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10470632>.
> > > >
> > >
> > > --
> > > Simon Bernard
> > > académie de Lyon - Délégation Académique au Numérique Éducatif
> > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/> *Simon Bernard
> > > Rectorat de Lyon
> > > DANE - Délégation Académique au Numérique Éducatif
> > > Assistance de niveau 2 aux utilisateurs du réseau pédagogique
> > > * Téléphone : 04 72 80 64 88
> > >
> > > Adresse postale : 92 rue de Marseille - BP 7227 - 69354 Lyon Cedex 07
> > > Locaux site Croix-Rousse (47 rue Philippe de Lassalle 69004 Lyon)
> > > *http://www.ac-lyon.fr*
> > > <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/>
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > >
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10483837>.
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> >
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10486144>.
> >
>
> --
> Simon Bernard
> académie de Lyon - Délégation Académique au Numérique Éducatif
> <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/> *Simon Bernard
> Rectorat de Lyon
> DANE - Délégation Académique au Numérique Éducatif
> Assistance de niveau 2 aux utilisateurs du réseau pédagogique
> * Téléphone : 04 72 80 64 88
>
> Adresse postale : 92 rue de Marseille - BP 7227 - 69354 Lyon Cedex 07
> Locaux site Croix-Rousse (47 rue Philippe de Lassalle 69004 Lyon)
> *http://www.ac-lyon.fr*
> <http://www2.ac-lyon.fr/serv_ress/mission_tice/wiki/>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dane-lyon/clients-linux-scribe/commit/b547803a04abbbe6be07813ba9933f0bb9f425c3#commitcomment-10486570>.
>


I would suggest to put the taalicoon description in a variable, defined in the EventFormatter. You could use an array of descriptions, and pass on the one corresponding to the taalicoon count.

Example from the top of my head:
```php
$languageDescriptions = array(
    'Je spreekt nog geen of niet zo veel Nederlands.',
    'Je begrijpt al een beetje Nederlands, maar je durft nog niet zo goed praten.',
    ...
);
$languageDescription = $languageDescriptions[$taalIcoonCount];
```


Remove the unnecessary `='There was an error.'` from line 5. Then change `flash[:error]` to `flash.discard(:error)`:

```html
$("#comment-" + <%= @comment.id %>).prepend("<div class='alert alert-danger'><%= flash.discard(:error) %></div>");
```

When **outputting** a message in a template, aim to use `flash.discard(:thing)` instead of `flash[:thing]`.

By using `flash.discard`, we ensure that the flash message is not shown in the **following** response. It ensures a given flash message is only displayed once.


Hey again! Sorry for taking a while to respond, I see the issue. I'll take a look into how this can be fixed.


Resolves Issue #5


test 4


what exactly is wrong with unsigned char? can index be > 255 ? there is no usage of 'signed' AFAICT?


We can remove the following .gitkeep files:

*  tests/unit/.gitkeep
*  app/templates/components/.gitkeep
* app/routes/.gitkeep
* app/components/.gitkeep
* app/models/.gitkeep


I think this should be `true` - the commit is now included. `false` suggests you should retry.


:-1:

Solution for this problem shouldn't touch `_reset_counter`.


At a glance, it looks OK, but I'll leave it to @AccaliaDeElementia to review and maybe merge.

I'm assuming it's likes received, with /t/1000 split out from the rest?


Is there a specific reason why this removed Node support on purpose and kept only in-browser support?


ping @asarenski :wink:


pressure or humidity??


It is not time delay. It uses clever [alghorithm](http://wiki.ros.org/message_filters/ApproximateTime). PLease see relevant docs for message_filters::sync_policies::ApproximateTime.


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


I'm also wondering if we should use Dutch words in the source code, ie. "Taalicoon".
Words like UiTPAS, Vlieg, etc are actual brands so we shouldn't translate those, but I'm not sure if taalicoon is something we can not translate in the source code. Is "taalicoon" a word they actively communicate to the end-user (like "Vlieg"), or is it just a name for the CSS class that was delivered to us like that?


Disregard that, found #18.


I'm aware of the issue.  This is not ready for public release.


Test


agree add Student


@bertramakers it's really called "taaliconen", an initative of Huis van Het Nederlands: http://www.taalboulevard.be/content/taaliconen. So better to use the name as is.


After our discussion our discussion I agree that the registry is not the best place, but that we could rather achieve that using signals...


28:1: I100 Imports statements are in the wrong order. from invenio.utils.shell should be before from invenio.version


4: L102 copyright year is outdated, expected 2015 but got 2014
29:1: I100 Imports statements are in the wrong order. from invenio.ext.legacy.handler should be before from invenio.ext.logging
31:1: I101 Imported names are in the wrong order. Should be CFG_ACCESS_CONTROL_LEVEL_SITE, CFG_DEVEL_SITE
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils
32:1: F401 'webinterface_proxy' imported but unused
47:13: E731 do not assign a lambda expression, use a def
59:9: B901 blind except: statement
69: D209 Multi-line docstring closing quotes should be on a separate line
69: D203 1 blank line required before class docstring (found 0)
69: D204 1 blank line required after class docstring (found 0)
69: D400 First line should end with a period (not 'e')
69: D205 1 blank line required between summary line and description (found 0)
73:5: E301 expected 1 blank line, found 0
73: D102 Missing docstring in public method
78:13: E731 do not assign a lambda expression, use a def
85:23: E127 continuation line over-indented for visual indent
92:9: B901 blind except: statement
100: D209 Multi-line docstring closing quotes should be on a separate line
100: D203 1 blank line required before class docstring (found 0)
100: D204 1 blank line required after class docstring (found 0)
100: D400 First line should end with a period (not 'f')
100: D205 1 blank line required between summary line and description (found 0)
104:5: E301 expected 1 blank line, found 0
104: D102 Missing docstring in public method
108:13: E731 do not assign a lambda expression, use a def
116:23: E127 continuation line over-indented for visual indent
123:9: B901 blind except: statement
132:1: B901 blind except: statement
138:1: B901 blind except: statement
144:10: E126 continuation line over-indented for hanging indent
145:1: B901 blind except: statement
151:10: E126 continuation line over-indented for hanging indent
152:1: B901 blind except: statement
162:1: E302 expected 2 blank lines, found 1
162: D203 1 blank line required before class docstring (found 0)
162: D204 1 blank line required after class docstring (found 0)
165:5: E301 expected 1 blank line, found 0
165: D102 Missing docstring in public method
171:1: E302 expected 2 blank lines, found 1
171: D210 No whitespaces allowed surrounding docstring text
171: None: None
171: D209 Multi-line docstring closing quotes should be on a separate line
171: D203 1 blank line required before class docstring (found 0)
171: D400 First line should end with a period (not 'l')
171: D205 1 blank line required between summary line and description (found 0)
176:16: E127 continuation line over-indented for visual indent
208: D102 Missing docstring in public method
245: D102 Missing docstring in public method


1: D100 Missing docstring in public module
83:1: E402 module level import not at top of file
84:1: I101 Imported names are in the wrong order. Should be IndentedHelpFormatter, Option, OptionError, OptionGroup, OptionParser
84:1: E402 module level import not at top of file
86:1: I100 Imports statements are in the wrong order. import os should be before from optparse
86:1: E402 module level import not at top of file
87:1: I201 Missing newline before sections or imports.
87:1: E402 module level import not at top of file
88:1: I100 Imports statements are in the wrong order. import random should be before import pkg_resources
88:1: I201 Missing newline before sections or imports.
88:1: F401 'random' imported but unused
88:1: E402 module level import not at top of file
89:1: E402 module level import not at top of file
90:1: E402 module level import not at top of file
91:1: E402 module level import not at top of file
92:1: F401 'string' 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: E402 module level import not at top of file
95:1: I201 Missing newline before sections or imports.
95:1: E402 module level import not at top of file
96:1: I100 Imports statements are in the wrong order. from warnings should be before from six
96:1: I201 Missing newline before sections or imports.
96:1: E402 module level import not at top of file
97:1: I201 Missing newline before sections or imports.
97:1: F401 'exc' imported but unused
97:1: E402 module level import not at top of file
105: D210 No whitespaces allowed surrounding docstring text
105: None: None
105: D400 First line should end with a period (not 'o')
116: D202 No blank lines allowed after function docstring (found 1)
116: D400 First line should end with a period (not 'g')
116: D205 1 blank line required between summary line and description (found 0)
122:5: E266 too many leading '#' for block comment
125:5: E266 too many leading '#' for block comment
137:5: E266 too many leading '#' for block comment
153:5: E266 too many leading '#' for block comment
158:5: E266 too many leading '#' for block comment
164:5: E266 too many leading '#' for block comment
168:5: E266 too many leading '#' for block comment
219:5: E266 too many leading '#' for block comment
226:5: E266 too many leading '#' for block comment
267:5: E266 too many leading '#' for block comment
272:5: E266 too many leading '#' for block comment
277:5: E266 too many leading '#' for block comment
285:5: E266 too many leading '#' for block comment
289:5: E266 too many leading '#' for block comment
311:5: E266 too many leading '#' for block comment
315: D103 Missing docstring in public function
321: D400 First line should end with a period (not 's')
321: D205 1 blank line required between summary line and description (found 0)
337: D205 1 blank line required between summary line and description (found 0)
344:5: E266 too many leading '#' for block comment
346:21: E127 continuation line over-indented for visual indent
347:5: E266 too many leading '#' for block comment
351:50: E502 the backslash is redundant between brackets
352:25: E127 continuation line over-indented for visual indent
352:66: E502 the backslash is redundant between brackets
353:25: E127 continuation line over-indented for visual indent
364: D205 1 blank line required between summary line and description (found 0)
371:5: E266 too many leading '#' for block comment
373:21: E127 continuation line over-indented for visual indent
374:5: E266 too many leading '#' for block comment
377:5: E266 too many leading '#' for block comment
393: D400 First line should end with a period (not '6')
393: D205 1 blank line required between summary line and description (found 0)
410: D400 First line should end with a period (not 'r')
410: D205 1 blank line required between summary line and description (found 0)
418:5: E266 too many leading '#' for block comment
420:14: E127 continuation line over-indented for visual indent
421:5: E266 too many leading '#' for block comment
424:16: E126 continuation line over-indented for hanging indent
425:13: E266 too many leading '#' for block comment
439:45: E128 continuation line under-indented for visual indent
440:45: E128 continuation line under-indented for visual indent
449: D400 First line should end with a period (not 'd')
449: D205 1 blank line required between summary line and description (found 0)
477: D209 Multi-line docstring closing quotes should be on a separate line
477: D400 First line should end with a period (not 'n')
477: D205 1 blank line required between summary line and description (found 0)
503:32: F841 local variable 'err' is assigned to but never used
523: D209 Multi-line docstring closing quotes should be on a separate line
523: D400 First line should end with a period (not 'n')
523: D205 1 blank line required between summary line and description (found 0)
537: D200 One-line docstring should fit on one line with quotes (found 3)
552: D400 First line should end with a period (not 'N')
552: D205 1 blank line required between summary line and description (found 0)
562:5: E266 too many leading '#' for block comment
564:5: E266 too many leading '#' for block comment
566:5: E266 too many leading '#' for block comment
569:9: E266 too many leading '#' for block comment
570:9: E266 too many leading '#' for block comment
586:9: E266 too many leading '#' for block comment
592:49: E128 continuation line under-indented for visual indent
597:9: E266 too many leading '#' for block comment
603:82: E231 missing whitespace after ','
618: D400 First line should end with a period (not 's')
618: D205 1 blank line required between summary line and description (found 0)
637: D209 Multi-line docstring closing quotes should be on a separate line
637: D205 1 blank line required between summary line and description (found 0)
662: D103 Missing docstring in public function
672: D103 Missing docstring in public function
707:72: E502 the backslash is redundant between brackets
708:20: E127 continuation line over-indented for visual indent
708:44: E231 missing whitespace after ','
712:35: E261 at least two spaces before inline comment
731:21: E128 continuation line under-indented for visual indent
731:93: E231 missing whitespace after ','
749:50: E231 missing whitespace after ','
769:48: E231 missing whitespace after ','
822: D400 First line should end with a period (not 'e')
822: D205 1 blank line required between summary line and description (found 0)
844: D400 First line should end with a period (not 's')
844: D205 1 blank line required between summary line and description (found 0)
859: D400 First line should end with a period (not 'r')
859: D205 1 blank line required between summary line and description (found 0)
869:10: E122 continuation line missing indentation or outdented
882: D200 One-line docstring should fit on one line with quotes (found 3)
897: D400 First line should end with a period (not 'y')
897: D205 1 blank line required between summary line and description (found 0)
916: D400 First line should end with a period (not 'L')
916: D205 1 blank line required between summary line and description (found 0)
931: D400 First line should end with a period (not 's')
931: D200 One-line docstring should fit on one line with quotes (found 3)
945: D400 First line should end with a period (not 's')
945: D200 One-line docstring should fit on one line with quotes (found 3)
959: D400 First line should end with a period (not 'd')
959: D200 One-line docstring should fit on one line with quotes (found 3)
973: D200 One-line docstring should fit on one line with quotes (found 3)
987: D202 No blank lines allowed after function docstring (found 1)
990: D203 1 blank line required before class docstring (found 0)
990: D204 1 blank line required after class docstring (found 0)
990: D400 First line should end with a period (not 'l')
1106: D210 No whitespaces allowed surrounding docstring text
1106: None: None
1106: D400 First line should end with a period (not 's')
1145:9: E266 too many leading '#' for block comment
1201:21: B901 blind except: statement


22:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
30:1: E302 expected 2 blank lines, found 1
30: D202 No blank lines allowed after function docstring (found 1)
36: D202 No blank lines allowed after function docstring (found 1)
41:1: E302 expected 2 blank lines, found 1
41: D210 No whitespaces allowed surrounding docstring text
41: None: None
41: D202 No blank lines allowed after function docstring (found 1)
47:1: E302 expected 2 blank lines, found 1
47: D103 Missing docstring in public function
50:1: E302 expected 2 blank lines, found 1
50: D202 No blank lines allowed after function docstring (found 1)
56: D210 No whitespaces allowed surrounding docstring text
56: None: None
56: D202 No blank lines allowed after function docstring (found 1)
64: D210 No whitespaces allowed surrounding docstring text
64: None: None
64: D202 No blank lines allowed after function docstring (found 1)
72: D202 No blank lines allowed after function docstring (found 1)
72: D400 First line should end with a period (not 's')
77:1: E302 expected 2 blank lines, found 1
77: D202 No blank lines allowed after function docstring (found 1)
77: D400 First line should end with a period (not 't')
82:1: E302 expected 2 blank lines, found 1
82: D202 No blank lines allowed after function docstring (found 1)
82: D400 First line should end with a period (not 't')
87:1: E302 expected 2 blank lines, found 1
87: D202 No blank lines allowed after function docstring (found 1)
87: D400 First line should end with a period (not 'y')
92:1: E302 expected 2 blank lines, found 1
92: D202 No blank lines allowed after function docstring (found 1)
92: D400 First line should end with a period (not 't')
97:1: E302 expected 2 blank lines, found 1
97: D202 No blank lines allowed after function docstring (found 1)
102:1: E302 expected 2 blank lines, found 1
102: D202 No blank lines allowed after function docstring (found 1)
102: D400 First line should end with a period (not 't')
107:1: E302 expected 2 blank lines, found 1
107: D202 No blank lines allowed after function docstring (found 1)
107: D400 First line should end with a period (not 't')
112:1: E302 expected 2 blank lines, found 1
112: D210 No whitespaces allowed surrounding docstring text
112: None: None
112: D202 No blank lines allowed after function docstring (found 1)
117:1: E302 expected 2 blank lines, found 1
117: D210 No whitespaces allowed surrounding docstring text
117: None: None
121:1: E302 expected 2 blank lines, found 1
121: D210 No whitespaces allowed surrounding docstring text
121: None: None
121: D202 No blank lines allowed after function docstring (found 1)
124:151: E231 missing whitespace after ','
126:1: E302 expected 2 blank lines, found 1
126: D202 No blank lines allowed after function docstring (found 1)
126: D400 First line should end with a period (not 'e')
132: D202 No blank lines allowed after function docstring (found 1)
132: D400 First line should end with a period (not 'e')
141: D202 No blank lines allowed after function docstring (found 1)
141: D400 First line should end with a period (not 'e')
151: D202 No blank lines allowed after function docstring (found 1)
151: D400 First line should end with a period (not 'e')
160: D202 No blank lines allowed after function docstring (found 1)
160: D400 First line should end with a period (not ':')
177: D202 No blank lines allowed after function docstring (found 1)
177: D400 First line should end with a period (not ':')
188:32: E128 continuation line under-indented for visual indent
189:32: E128 continuation line under-indented for visual indent
190:32: E128 continuation line under-indented for visual indent
191:32: E128 continuation line under-indented for visual indent
192:32: E128 continuation line under-indented for visual indent
193:32: E128 continuation line under-indented for visual indent
196: D209 Multi-line docstring closing quotes should be on a separate line
196: D202 No blank lines allowed after function docstring (found 1)
196: D400 First line should end with a period (not ',')
196: D208 Docstring is over-indented
208: D202 No blank lines allowed after function docstring (found 1)
215: D210 No whitespaces allowed surrounding docstring text
215: None: None
215: D202 No blank lines allowed after function docstring (found 1)
222: D210 No whitespaces allowed surrounding docstring text
222: None: None
222: D202 No blank lines allowed after function docstring (found 1)
229: D209 Multi-line docstring closing quotes should be on a separate line
229: D202 No blank lines allowed after function docstring (found 1)
229: D208 Docstring is over-indented
245: D209 Multi-line docstring closing quotes should be on a separate line
245: D202 No blank lines allowed after function docstring (found 1)
245: D208 Docstring is over-indented
261: D209 Multi-line docstring closing quotes should be on a separate line
261: D202 No blank lines allowed after function docstring (found 1)
275: D210 No whitespaces allowed surrounding docstring text
275: None: None
275: D209 Multi-line docstring closing quotes should be on a separate line
275: D202 No blank lines allowed after function docstring (found 1)
275: D400 First line should end with a period (not ':')
275: D208 Docstring is over-indented
292: D209 Multi-line docstring closing quotes should be on a separate line
292: D202 No blank lines allowed after function docstring (found 1)
292: D208 Docstring is over-indented
303:37: E128 continuation line under-indented for visual indent
304:37: E128 continuation line under-indented for visual indent
305:37: E128 continuation line under-indented for visual indent
306:37: E128 continuation line under-indented for visual indent
309: D209 Multi-line docstring closing quotes should be on a separate line
309: D202 No blank lines allowed after function docstring (found 1)
309: D400 First line should end with a period (not 's')
309: D205 1 blank line required between summary line and description (found 0)
309: D208 Docstring is over-indented
335: D209 Multi-line docstring closing quotes should be on a separate line
335: D202 No blank lines allowed after function docstring (found 1)
335: D400 First line should end with a period (not 'a')
335: D205 1 blank line required between summary line and description (found 0)
344: D210 No whitespaces allowed surrounding docstring text
344: None: None
344: D202 No blank lines allowed after function docstring (found 1)
349:1: W391 blank line at end of file


22:1: E402 module level import not at top of file
23:1: F401 'os' imported but unused
23:1: E402 module level import not at top of file
24:1: I100 Imports statements are in the wrong order. import datetime should be before import os
24:1: F401 'datetime' imported but unused
24:1: E402 module level import not at top of file
25:1: F401 'time' imported but unused
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import sys should be before import time
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. import threading should be before from invenio.utils
29:1: I201 Missing newline before sections or imports.
29:1: F401 'threading' imported but unused
29:1: E402 module level import not at top of file
30:1: I201 Missing newline before sections or imports.
30:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be CFG_BIBRANK_SHOW_DOWNLOAD_STATS, CFG_CACHEDIR, CFG_INSPIRE_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_URL, CFG_WEBDIR, CFG_WEBSEARCH_DEFAULT_SEARCH_INTERFACE, CFG_WEBSEARCH_ENABLED_SEARCH_INTERFACES, CFG_WEBSEARCH_INSTANT_BROWSE_RSS, CFG_WEBSEARCH_MAX_RECORDS_IN_GROUPS, CFG_WEBSEARCH_RSS_I18N_COLLECTIONS, CFG_WEBSEARCH_RSS_MAX_CACHED_REQUESTS, CFG_WEBSEARCH_RSS_TTL, CFG_WEBSEARCH_USE_MATHJAX_FOR_FORMATS, CFG_WEBSEARCH_WILDCARD_LIMIT
42:1: I100 Imports statements are in the wrong order. from invenio.config should be before from werkzeug.local
42:1: F401 'CFG_WEBSEARCH_USE_MATHJAX_FOR_FORMATS' imported but unused
42:1: F401 'CFG_WEBSEARCH_RSS_TTL' imported but unused
42:1: F401 'CFG_WEBSEARCH_RSS_MAX_CACHED_REQUESTS' imported but unused
42:1: F401 'CFG_WEBSEARCH_RSS_I18N_COLLECTIONS' imported but unused
42:1: F401 'CFG_WEBDIR' imported but unused
42:1: F401 'CFG_INSPIRE_SITE' imported but unused
42:1: F401 'CFG_BIBRANK_SHOW_DOWNLOAD_STATS' imported but unused
42:1: F401 'CFG_CACHEDIR' imported but unused
42:1: F401 'CFG_WEBSEARCH_INSTANT_BROWSE_RSS' imported but unused
42:1: E402 module level import not at top of file
61:1: E402 module level import not at top of file
62:1: I101 Imported names are in the wrong order. Should be WebInterfaceDirectory, wash_urlargd
62:1: I100 Imports statements are in the wrong order. from invenio.ext.legacy.handler should be before from invenio.legacy.dbquery
62:1: E402 module level import not at top of file
63:1: I101 Imported names are in the wrong order. Should be drop_default_urlargd, make_canonical_urlargd, redirect_to_url
63:1: E402 module level import not at top of file
64:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.url
64:1: F401 'get_mathjax_header' imported but unused
64:1: E402 module level import not at top of file
65:1: F401 'nmtoken_from_string' imported but unused
65:1: E402 module level import not at top of file
66:1: I101 Imported names are in the wrong order. Should be collect_user_info, getUid, get_user_preferences, isUserSuperAdmin, page_not_authorized
66:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.html
66:1: E402 module level import not at top of file
68:1: I100 Imports statements are in the wrong order. from invenio.legacy.webcomment.webinterface should be before from invenio.legacy.webuser
68:1: E402 module level import not at top of file
69:1: E402 module level import not at top of file
70:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcirculation.webinterface should be before from invenio.legacy.weblinkback.webinterface
70:1: E402 module level import not at top of file
71:1: I101 Imported names are in the wrong order. Should be create_error_box, page, pageheaderonly
71:1: F401 'pageheaderonly' imported but unused
71:1: E402 module level import not at top of file
72:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.legacy.webpage
72:1: E402 module level import not at top of file
73:1: I101 Imported names are in the wrong order. Should be EM_REPOSITORY, check_user_can_view_record, collection_reclist_cache, collection_restricted_p, get_coll_i18nname, get_most_popular_field_values, guess_primary_collection_of_a_record, perform_request_search, restricted_collection_cache
73:1: F401 'collection_reclist_cache' imported but unused
73:1: F401 'get_most_popular_field_values' imported but unused
73:1: F401 'EM_REPOSITORY' imported but unused
73:1: E402 module level import not at top of file
82:1: E402 module level import not at top of file
83:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.collections.models
83:1: F401 'get_fieldvalues' imported but unused
83:1: F401 'get_fieldvalues_alephseq_like' imported but unused
83:1: E402 module level import not at top of file
84:6: E126 continuation line over-indented for hanging indent
85:1: E402 module level import not at top of file
86:1: E402 module level import not at top of file
87:1: E402 module level import not at top of file
88:1: E402 module level import not at top of file
89:1: E402 module level import not at top of file
90:1: E402 module level import not at top of file
91:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.modules.formatter.engine
91:1: I201 Missing newline before sections or imports.
91:1: E402 module level import not at top of file
92:1: I201 Missing newline before sections or imports.
92:1: E402 module level import not at top of file
93:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrank.citation_searcher should be before from invenio.legacy.bibupload.engine
93:1: F401 'get_cited_by_list' imported but unused
93:1: E402 module level import not at top of file
94:1: F401 'get_download_weight_total' imported but unused
94:1: E402 module level import not at top of file
95:1: F401 'summarize_records' imported but unused
95:1: E402 module level import not at top of file
96:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.search_engine.summarizer
96:1: E402 module level import not at top of file
97:1: E402 module level import not at top of file
98:1: E402 module level import not at top of file
99:1: I101 Imported names are in the wrong order. Should be WebInterfaceFilesPages, WebInterfaceManageDocFilesPages
99:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.webinterface should be before from invenio.legacy.bibmerge.webinterface
99:1: E402 module level import not at top of file
100:1: E402 module level import not at top of file
101:1: F401 'mymkdir' imported but unused
101:1: E402 module level import not at top of file
103:1: I100 Imports statements are in the wrong order. import invenio.legacy.template should be before from invenio.utils.shell
103:1: E402 module level import not at top of file
112: D202 No blank lines allowed after function docstring (found 1)
112: D200 One-line docstring should fit on one line with quotes (found 3)
151: D210 No whitespaces allowed surrounding docstring text
151: None: None
151: D203 1 blank line required before class docstring (found 0)
151: D204 1 blank line required after class docstring (found 0)
155: D102 Missing docstring in public method
157:17: E203 whitespace before ':'
158:21: E203 whitespace before ':'
168:13: E266 too many leading '#' for block comment
170:22: E203 whitespace before ':'
171:26: E203 whitespace before ':'
172:21: E203 whitespace before ':'
173:26: E203 whitespace before ':'
174:23: E203 whitespace before ':'
188: D210 No whitespaces allowed surrounding docstring text
188: None: None
188: D203 1 blank line required before class docstring (found 0)
188: D400 First line should end with a period (not 't')
197: D102 Missing docstring in public method
218: D102 Missing docstring in public method
233:17: E128 continuation line under-indented for visual indent
261:86: E203 whitespace before ':'
263:21: E127 continuation line over-indented for visual indent
263:67: E203 whitespace before ':'
263:91: E203 whitespace before ':'
266:52: E502 the backslash is redundant between brackets
267:17: E128 continuation line under-indented for visual indent
267:32: E502 the backslash is redundant between brackets
268:17: E128 continuation line under-indented for visual indent
281:42: E261 at least two spaces before inline comment
281:43: E262 inline comment should start with '# '
296: D210 No whitespaces allowed surrounding docstring text
296: None: None
296: D203 1 blank line required before class docstring (found 0)
296: D400 First line should end with a period (not 't')
305: D102 Missing docstring in public method
324: D102 Missing docstring in public method
336:17: E128 continuation line under-indented for visual indent
366:21: E128 continuation line under-indented for visual indent
367:21: E128 continuation line under-indented for visual indent
386: D210 No whitespaces allowed surrounding docstring text
386: None: None
386: D203 1 blank line required before class docstring (found 0)
391: D210 No whitespaces allowed surrounding docstring text
391: None: None
404:17: E128 continuation line under-indented for visual indent
405:40: E126 continuation line over-indented for hanging indent
448:102: E203 whitespace before ':'
450:37: E127 continuation line over-indented for visual indent
450:83: E203 whitespace before ':'
450:107: E203 whitespace before ':'
453:64: E502 the backslash is redundant between brackets
454:29: E128 continuation line under-indented for visual indent
454:44: E502 the backslash is redundant between brackets
455:29: E128 continuation line under-indented for visual indent
465:94: E203 whitespace before ':'
467:29: E127 continuation line over-indented for visual indent
467:75: E203 whitespace before ':'
467:99: E203 whitespace before ':'
470:60: E502 the backslash is redundant between brackets
471:25: E128 continuation line under-indented for visual indent
471:40: E502 the backslash is redundant between brackets
472:25: E128 continuation line under-indented for visual indent
498: D202 No blank lines allowed after function docstring (found 1)
508:94: E203 whitespace before ':'
510:29: E127 continuation line over-indented for visual indent
510:75: E203 whitespace before ':'
510:99: E203 whitespace before ':'
513:60: E502 the backslash is redundant between brackets
514:25: E128 continuation line under-indented for visual indent
514:40: E502 the backslash is redundant between brackets
515:25: E128 continuation line under-indented for visual indent
543:9: E303 too many blank lines (2)
555: D210 No whitespaces allowed surrounding docstring text
555: None: None
555: D203 1 blank line required before class docstring (found 0)
560: D210 No whitespaces allowed surrounding docstring text
560: None: None
560: D202 No blank lines allowed after function docstring (found 1)
587:1: E302 expected 2 blank lines, found 1
587: D210 No whitespaces allowed surrounding docstring text
587: None: None
600: D210 No whitespaces allowed surrounding docstring text
600: D401 First line should be in imperative mood ('Thi', not 'This')
600: None: None
600: D209 Multi-line docstring closing quotes should be on a separate line
600: D202 No blank lines allowed after function docstring (found 1)
600: D400 First line should end with a period (not 'r')
600: D205 1 blank line required between summary line and description (found 0)
691:13: E266 too many leading '#' for block comment
692:13: E266 too many leading '#' for block comment
700: D400 First line should end with a period (not 'I')
702:63: E231 missing whitespace after ','
709: D210 No whitespaces allowed surrounding docstring text
709: None: None
718: D400 First line should end with a period (not 'e')
723:55: E202 whitespace before '}'
765: D209 Multi-line docstring closing quotes should be on a separate line
765: D400 First line should end with a period (not 'g')
765: D205 1 blank line required between summary line and description (found 0)
770:84: E203 whitespace before ':'
781:17: E128 continuation line under-indented for visual indent
784:13: F841 local variable 'user_preferences' is assigned to but never used
798:5: F841 local variable 'normalised_name' is assigned to but never used
817: D400 First line should end with a period (not 'e')
817: D205 1 blank line required between summary line and description (found 0)
837:59: E502 the backslash is redundant between brackets
838:32: F812 list comprehension redefines 'doi' from line 817
861:27: F841 local variable 'e' is assigned to but never used
875: D203 1 blank line required before class docstring (found 0)
887: D210 No whitespaces allowed surrounding docstring text
887: None: None
887: D203 1 blank line required before class docstring (found 0)
887: D400 First line should end with a period (not 't')
892: D102 Missing docstring in public method
901: D102 Missing docstring in public method
911:17: E128 continuation line under-indented for visual indent
941:86: E203 whitespace before ':'
943:21: E127 continuation line over-indented for visual indent
943:67: E203 whitespace before ':'
943:91: E203 whitespace before ':'
946:52: E502 the backslash is redundant between brackets
947:17: E128 continuation line under-indented for visual indent
947:32: E502 the backslash is redundant between brackets
948:17: E128 continuation line under-indented for visual indent


1: D100 Missing docstring in public module
20:1: E402 module level import not at top of file
21:1: I100 Imports statements are in the wrong order. import cgi should be before import urllib
21:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: I101 Imported names are in the wrong order. Should be CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBSEARCH_MAX_RECORDS_IN_GROUPS, CFG_WEBSESSION_ADDRESS_ACTIVATION_EXPIRE_IN_DAYS, CFG_WEBSESSION_RESET_PASSWORD_EXPIRE_IN_DAYS
24:1: F401 'CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS' imported but unused
24:1: E402 module level import not at top of file
25:6: E126 continuation line over-indented for hanging indent
40:1: I101 Imported names are in the wrong order. Should be create_html_link, create_url, make_canonical_urlargd
40:1: E402 module level import not at top of file
41:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.url
41:1: F401 'nmtoken_from_string' imported but unused
41:1: E402 module level import not at top of file
42:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
42:1: E402 module level import not at top of file
43:1: E402 module level import not at top of file
44:1: I100 Imports statements are in the wrong order. from invenio.legacy.websession.websession_config should be before from invenio.modules.apikeys.models
44:1: E402 module level import not at top of file
47: D101 Missing docstring in public class
69:17: E225 missing whitespace around operator
70:16: E126 continuation line over-indented for hanging indent
70:25: E203 whitespace before ':'
71:25: E203 whitespace before ':'
72:25: E203 whitespace before ':'
73:25: E203 whitespace before ':'
74:14: E126 continuation line over-indented for hanging indent
78: D102 Missing docstring in public method
79:9: F841 local variable '_' is assigned to but never used
87: D102 Missing docstring in public method
97:37: E203 whitespace before ':'
98:28: E203 whitespace before ':'
99:38: E203 whitespace before ':'
100:29: E203 whitespace before ':'
101:30: E203 whitespace before ':'
103:35: E203 whitespace before ':'
108:5: E303 too many blank lines (2)
108: D401 First line should be in imperative mood ('Display', not 'Displays')
108: D202 No blank lines allowed after function docstring (found 1)
108: D400 First line should end with a period (not 'r')
134:22: E126 continuation line over-indented for hanging indent
134:36: E203 whitespace before ':'
163:31: E126 continuation line over-indented for hanging indent
168:43: E203 whitespace before ':'
196:32: E203 whitespace before ':'
197:43: E203 whitespace before ':'
198:27: E203 whitespace before ':'
199:22: E203 whitespace before ':'
201:39: E203 whitespace before ':'
204:16: E126 continuation line over-indented for hanging indent
208: D401 First line should be in imperative mood ('Display', not 'Displays')
208: D202 No blank lines allowed after function docstring (found 1)
263:17: E126 continuation line over-indented for hanging indent
263:30: E203 whitespace before ':'
264:30: E203 whitespace before ':'
265:33: E203 whitespace before ':'
266:27: E203 whitespace before ':'
268:34: E203 whitespace before ':'
268:45: E225 missing whitespace around operator
269:34: E203 whitespace before ':'
269:45: E225 missing whitespace around operator
270:28: E203 whitespace before ':'
271:28: E203 whitespace before ':'
272:26: E203 whitespace before ':'
273:23: E203 whitespace before ':'
274:29: E203 whitespace before ':'
275:24: E203 whitespace before ':'
276:33: E203 whitespace before ':'
278:38: E203 whitespace before ':'
279:13: E121 continuation line under-indented for hanging indent
318:21: E126 continuation line over-indented for hanging indent
318:34: E203 whitespace before ':'
319:32: E203 whitespace before ':'
320:35: E203 whitespace before ':'
321:35: E203 whitespace before ':'
323:31: E203 whitespace before ':'
324:27: E203 whitespace before ':'
325:36: E203 whitespace before ':'
326:40: E203 whitespace before ':'
327:38: E203 whitespace before ':'
328:33: E203 whitespace before ':'
329:40: E203 whitespace before ':'
331:17: E121 continuation line under-indented for hanging indent
334:21: E128 continuation line under-indented for visual indent
334:34: E203 whitespace before ':'
336:139: E203 whitespace before ':'
337:35: E203 whitespace before ':'
340:30: E203 whitespace before ':'
340:96: E203 whitespace before ':'
344:5: E303 too many blank lines (2)
344: D400 First line should end with a period (not 'd')
362:11: E121 continuation line under-indented for hanging indent
362:26: E203 whitespace before ':'
363:32: E203 whitespace before ':'
364:32: E203 whitespace before ':'
365:37: E203 whitespace before ':'
366:21: E203 whitespace before ':'
367:21: E203 whitespace before ':'
368:28: E203 whitespace before ':'
374:5: E303 too many blank lines (2)
374: D102 Missing docstring in public method
382:11: E121 continuation line under-indented for hanging indent
382:26: E203 whitespace before ':'
383:31: E203 whitespace before ':'
387:27: E203 whitespace before ':'
388:27: E203 whitespace before ':'
389:26: E203 whitespace before ':'
394:26: E203 whitespace before ':'
395:30: E203 whitespace before ':'
401:5: E303 too many blank lines (2)
401: D102 Missing docstring in public method
409:11: E121 continuation line under-indented for hanging indent
409:26: E203 whitespace before ':'
410:26: E203 whitespace before ':'
413:23: E203 whitespace before ':'
414:19: E203 whitespace before ':'
417:23: E203 whitespace before ':'
418:19: E203 whitespace before ':'
423:30: E203 whitespace before ':'
429:5: E303 too many blank lines (2)
429:51: E251 unexpected spaces around keyword / parameter equals
429:53: E251 unexpected spaces around keyword / parameter equals
429:72: E251 unexpected spaces around keyword / parameter equals
429:74: E251 unexpected spaces around keyword / parameter equals
429:93: E251 unexpected spaces around keyword / parameter equals
429:95: E251 unexpected spaces around keyword / parameter equals
429: D102 Missing docstring in public method
441:11: E121 continuation line under-indented for hanging indent
441:26: E203 whitespace before ':'
442:36: E203 whitespace before ':'
443:27: E203 whitespace before ':'
444:30: E203 whitespace before ':'
445:25: E203 whitespace before ':'
446:28: E203 whitespace before ':'
452:25: E126 continuation line over-indented for hanging indent
452:35: E203 whitespace before ':'
453:28: E203 whitespace before ':'
454:21: E121 continuation line under-indented for hanging indent
460:17: E126 continuation line over-indented for hanging indent
460:34: E203 whitespace before ':'
461:39: E203 whitespace before ':'
463:13: E121 continuation line under-indented for hanging indent
466: D401 First line should be in imperative mood ('Display', not 'Displays')
466: D202 No blank lines allowed after function docstring (found 1)
479:256: E203 whitespace before ':'
479:280: E203 whitespace before ':'
479:302: E203 whitespace before ':'
501:20: E203 whitespace before ':'
502:19: E203 whitespace before ':'
503:11: E121 continuation line under-indented for hanging indent
507:45: E203 whitespace before ':'
508:46: E203 whitespace before ':'
509:45: E203 whitespace before ':'
511:46: E203 whitespace before ':'
515:15: E128 continuation line under-indented for visual indent
515:73: E201 whitespace after '{'
515:81: E203 whitespace before ':'
515:106: E202 whitespace before '}'
518:9: E303 too many blank lines (2)
520: D401 First line should be in imperative mood ('Display', not 'Displays')
520: D202 No blank lines allowed after function docstring (found 1)
520: D400 First line should end with a period (not 'n')
542:17: E126 continuation line over-indented for hanging indent
542:32: E203 whitespace before ':'
543:25: E128 continuation line under-indented for visual indent
544:15: E126 continuation line over-indented for hanging indent
552:22: E126 continuation line over-indented for hanging indent
552:26: E203 whitespace before ':'
553:37: E203 whitespace before ':'
554:38: E203 whitespace before ':'
555:20: E126 continuation line over-indented for hanging indent
560:11: E121 continuation line under-indented for hanging indent
560:15: E203 whitespace before ':'
561:26: E203 whitespace before ':'
562:27: E203 whitespace before ':'
568:9: E122 continuation line missing indentation or outdented
568:13: E203 whitespace before ':'
569:9: E122 continuation line missing indentation or outdented
569:23: E203 whitespace before ':'
570:9: E122 continuation line missing indentation or outdented
570:25: E203 whitespace before ':'
576:13: E122 continuation line missing indentation or outdented
576:17: E203 whitespace before ':'
577:13: E122 continuation line missing indentation or outdented
577:28: E203 whitespace before ':'
578:13: E122 continuation line missing indentation or outdented
578:31: E203 whitespace before ':'
583:11: E121 continuation line under-indented for hanging indent
583:15: E203 whitespace before ':'
584:24: E203 whitespace before ':'
585:27: E203 whitespace before ':'
592:15: E121 continuation line under-indented for hanging indent
592:27: E203 whitespace before ':'
593:30: E203 whitespace before ':'
594:13: E122 continuation line missing indentation or outdented
595:13: E122 continuation line missing indentation or outdented
604: D401 First line should be in imperative mood ('Display', not 'Displays')
604: D202 No blank lines allowed after function docstring (found 1)
604: D400 First line should end with a period (not 'e')
617:17: E225 missing whitespace around operator
619:19: E225 missing whitespace around operator
629: D401 First line should be in imperative mood ('Display', not 'Displays')
629: D202 No blank lines allowed after function docstring (found 1)
629: D400 First line should end with a period (not 'r')
652: D401 First line should be in imperative mood ('Display', not 'Displays')
652: D202 No blank lines allowed after function docstring (found 1)
652: D400 First line should end with a period (not 'e')
667:14: E225 missing whitespace around operator
678: D401 First line should be in imperative mood ('Display', not 'Displays')
678: D202 No blank lines allowed after function docstring (found 1)
678: D400 First line should end with a period (not 'e')
740:32: E128 continuation line under-indented for visual indent
746:36: E128 continuation line under-indented for visual indent
750:35: E222 multiple spaces after operator
751:36: E222 multiple spaces after operator
752:35: E128 continuation line under-indented for visual indent
757:33: E222 multiple spaces after operator
758:34: E222 multiple spaces after operator
765: D401 First line should be in imperative mood ('Display', not 'Displays')
765: D202 No blank lines allowed after function docstring (found 1)
765: D400 First line should end with a period (not 'd')
779:14: E225 missing whitespace around operator
780:15: E225 missing whitespace around operator
787:17: E203 whitespace before ':'
788:18: E203 whitespace before ':'
789:24: E203 whitespace before ':'
790:11: E121 continuation line under-indented for hanging indent
793: D202 No blank lines allowed after function docstring (found 1)
793: D400 First line should end with a period (not 't')
793: D205 1 blank line required between summary line and description (found 0)
812:17: E128 continuation line under-indented for visual indent
813:17: E128 continuation line under-indented for visual indent
814:33: E203 whitespace before ':'
814:34: E231 missing whitespace after ':'
815:30: E203 whitespace before ':'
816:35: E203 whitespace before ':'
819:21: E203 whitespace before ':'
820:19: E203 whitespace before ':'
821:17: E131 continuation line unaligned for hanging indent
822:25: E203 whitespace before ':'
823:24: E203 whitespace before ':'
825:20: E203 whitespace before ':'
826:21: E203 whitespace before ':'
830: D202 No blank lines allowed after function docstring (found 1)
830: D400 First line should end with a period (not 'e')
830: D205 1 blank line required between summary line and description (found 0)
849:17: E128 continuation line under-indented for visual indent
850:17: E128 continuation line under-indented for visual indent
851:33: E203 whitespace before ':'
851:34: E231 missing whitespace after ':'
852:30: E203 whitespace before ':'
853:35: E203 whitespace before ':'
856:21: E203 whitespace before ':'
857:19: E203 whitespace before ':'
858:17: E131 continuation line unaligned for hanging indent
859:25: E203 whitespace before ':'
860:33: E203 whitespace before ':'
862:20: E203 whitespace before ':'
863:21: E203 whitespace before ':'
867: D401 First line should be in imperative mood ('Display', not 'Displays')
867: D202 No blank lines allowed after function docstring (found 1)
867: D400 First line should end with a period (not 't')
881:14: E225 missing whitespace around operator
885: D401 First line should be in imperative mood ('Display', not 'Displays')
885: D202 No blank lines allowed after function docstring (found 1)
885: D400 First line should end with a period (not 't')
900: D401 First line should be in imperative mood ('Display', not 'Displays')
900: D202 No blank lines allowed after function docstring (found 1)
900: D400 First line should end with a period (not 't')
900: D205 1 blank line required between summary line and description (found 0)
905:9: F841 local variable '_' is assigned to but never used
909:22: E126 continuation line over-indented for hanging indent
909:26: E203 whitespace before ':'
914: D401 First line should be in imperative mood ('Display', not 'Displays')
914: D202 No blank lines allowed after function docstring (found 1)
914: D400 First line should end with a period (not 'r')
1006: D401 First line should be in imperative mood ('Display', not 'Displays')
1006: D202 No blank lines allowed after function docstring (found 1)
1006: D400 First line should end with a period (not 'k')
1052:22: E126 continuation line over-indented for hanging indent
1053:26: E203 whitespace before ':'
1054:33: E203 whitespace before ':'
1055:31: E203 whitespace before ':'
1056:29: E203 whitespace before ':'
1057:20: E126 continuation line over-indented for hanging indent
1061:21: E126 continuation line over-indented for hanging indent
1061:36: E203 whitespace before ':'
1062:25: E203 whitespace before ':'
1063:31: E203 whitespace before ':'
1064:16: E121 continuation line under-indented for hanging indent
1066:21: E126 continuation line over-indented for hanging indent
1066:36: E203 whitespace before ':'
1067:25: E203 whitespace before ':'
1068:29: E203 whitespace before ':'
1069:17: E121 continuation line under-indented for hanging indent
1072: D400 First line should end with a period (not 's')
1072: D205 1 blank line required between summary line and description (found 0)
1093: D400 First line should end with a period (not 'r')
1093: D205 1 blank line required between summary line and description (found 0)
1100:9: F841 local variable '_' is assigned to but never used
1109: D401 First line should be in imperative mood ('Display', not 'Displays')
1109: D202 No blank lines allowed after function docstring (found 1)
1109: D400 First line should end with a period (not 'l')
1113:52: E251 unexpected spaces around keyword / parameter equals
1113:54: E251 unexpected spaces around keyword / parameter equals
1134:9: F841 local variable '_' is assigned to but never used
1149:14: E225 missing whitespace around operator
1159:14: E225 missing whitespace around operator
1163:5: E303 too many blank lines (2)
1163: D202 No blank lines allowed after function docstring (found 1)
1182:9: E303 too many blank lines (2)
1183:102: E202 whitespace before ')'
1203:35: E225 missing whitespace around operator
1210:15: E225 missing whitespace around operator
1213:46: E203 whitespace before ':'
1214:44: E203 whitespace before ':'
1216:42: E231 missing whitespace after ':'
1217:43: E231 missing whitespace after ':'
1218:45: E231 missing whitespace after ':'
1220:49: E203 whitespace before ':'
1221:47: E203 whitespace before ':'
1223:45: E231 missing whitespace after ':'
1224:46: E231 missing whitespace after ':'
1225:48: E231 missing whitespace after ':'
1284:15: E225 missing whitespace around operator
1308:16: E127 continuation line over-indented for visual indent
1309:29: E231 missing whitespace after ':'
1310:16: E124 closing bracket does not match visual indentation
1314:5: E303 too many blank lines (2)
1347:15: E225 missing whitespace around operator
1361: D400 First line should end with a period (not ':')
1361: D205 1 blank line required between summary line and description (found 0)
1384:20: E225 missing whitespace around operator
1399:46: E231 missing whitespace after ','
1468:25: E203 whitespace before ':'
1471:28: E203 whitespace before ':'
1479:30: E231 missing whitespace after ':'
1480:31: E231 missing whitespace after ':'
1481:28: E231 missing whitespace after ':'
1483:30: E203 whitespace before ':'
1483:31: E231 missing whitespace after ':'
1486:16: E124 closing bracket does not match visual indentation
1489: D201 No blank lines allowed before function docstring (found 1)
1489: D205 1 blank line required between summary line and description (found 0)
1580:25: E203 whitespace before ':'
1584:25: E231 missing whitespace after ':'
1585:29: E231 missing whitespace after ':'
1588:31: E231 missing whitespace after ':'
1589:29: E203 whitespace before ':'
1589:30: E231 missing whitespace after ':'
1589:64: E231 missing whitespace after ','
1590:33: E203 whitespace before ':'
1591:16: E124 closing bracket does not match visual indentation
1594: D202 No blank lines allowed after function docstring (found 1)
1729:19: E203 whitespace before ':'
1730:26: E222 multiple spaces after operator
1735:37: E231 missing whitespace after ','
1735:23: E222 multiple spaces after operator
1736:13: E203 whitespace before ':'
1738:27: E203 whitespace before ':'
1739:27: E222 multiple spaces after operator
1747:38: E231 missing whitespace after ','
1747:23: E222 multiple spaces after operator
1748:13: E203 whitespace before ':'
1757:21: E203 whitespace before ':'
1758:30: E203 whitespace before ':'
1759:27: E203 whitespace before ':'
1767:9: E122 continuation line missing indentation or outdented
1767:73: E201 whitespace after '{'
1767:81: E203 whitespace before ':'
1768:65: E128 continuation line under-indented for visual indent
1768:78: E203 whitespace before ':'
1769:65: E124 closing bracket does not match visual indentation
1770:26: E128 continuation line under-indented for visual indent
1774:13: E128 continuation line under-indented for visual indent
1776:24: E231 missing whitespace after ':'
1777:30: E203 whitespace before ':'
1778:31: E203 whitespace before ':'
1778:32: E231 missing whitespace after ':'
1779:25: E231 missing whitespace after ':'
1780:24: E231 missing whitespace after ':'
1789:31: E231 missing whitespace after ':'
1790:21: E231 missing whitespace after ':'
1858:21: E222 multiple spaces after operator
1861:13: E203 whitespace before ':'
1867:25: E203 whitespace before ':'
1868:29: E203 whitespace before ':'
1869:25: E231 missing whitespace after ':'
1871:24: E203 whitespace before ':'
1872:31: E231 missing whitespace after ':'
1873:21: E203 whitespace before ':'
1873:22: E231 missing whitespace after ':'
1874:25: E203 whitespace before ':'
1879:5: E303 too many blank lines (2)
1879: D400 First line should end with a period (not 'p')
1879: D205 1 blank line required between summary line and description (found 0)
1910:11: E225 missing whitespace around operator
1911:19: E231 missing whitespace after ':'
1914:22: E231 missing whitespace after ':'
1916:15: E124 closing bracket does not match visual indentation
1919: D400 First line should end with a period (not 'e')
1919: D205 1 blank line required between summary line and description (found 0)
1950:11: E225 missing whitespace around operator
1951:19: E231 missing whitespace after ':'
1954:22: E231 missing whitespace after ':'
1956:15: E124 closing bracket does not match visual indentation
1959: D400 First line should end with a period (not 'y')
1959: D205 1 blank line required between summary line and description (found 0)
1973: D210 No whitespaces allowed surrounding docstring text
1973: None: None
1973: D400 First line should end with a period (not 'u')
1973: D205 1 blank line required between summary line and description (found 0)
1978:20: E203 whitespace before ':'
1980:62: E225 missing whitespace around operator
1981:13: E203 whitespace before ':'
1988:54: E225 missing whitespace around operator
1993:5: E303 too many blank lines (2)
1993: D400 First line should end with a period (not 's')
1993: D205 1 blank line required between summary line and description (found 0)
1999:9: F841 local variable '_' is assigned to but never used
2011: D400 First line should end with a period (not ':')
2011: D205 1 blank line required between summary line and description (found 0)
2026:15: E271 multiple spaces after keyword
2028: D400 First line should end with a period (not ':')
2028: D205 1 blank line required between summary line and description (found 0)
2045: D400 First line should end with a period (not 'p')
2045: D205 1 blank line required between summary line and description (found 0)
2064: D400 First line should end with a period (not 'd')
2064: D205 1 blank line required between summary line and description (found 0)
2089: D400 First line should end with a period (not 'd')
2089: D205 1 blank line required between summary line and description (found 0)
2107: D400 First line should end with a period (not ')')
2107: D205 1 blank line required between summary line and description (found 0)
2125: D400 First line should end with a period (not 'e')
2125: D205 1 blank line required between summary line and description (found 0)
2173:19: E128 continuation line under-indented for visual indent