Pas de soucis.
De mon côté j'ai pu finalement passé en Python 3 pure! Donc ça va faciliter les choses.

On essaiera de faire le point à l'occasion.


r+


What is the reason to do so?
It's exactly the same functionally.

 From a Syskit point of view the semantic could be separated by using
DataServices, but on Task/Device level for the simulation there are
completly equivalent.

Best,
Matthias

On 05.01.2015 17:39, Jakob Schwendner wrote:
>
> I agree with malte. There should be an additional plugin for ground
> truth pose. And the IMU should be properly handled internally.
>

--
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 1
  28359 Bremen, Germany

  Zentrale: +49 421 178 45-6611

  Besuchsadresse der Nebengeschäftstelle:
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Tel.:    +49 421 178 45-4193
  Empfang: +49 421 178 45-6600
  Fax:     +49 421 178 45-4150
  E-Mail:  matthias.goldhoorn@informatik.uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik


已经添加s.libraries = 'stdc++'依赖并push了


Updated with a link


Thanks


For now, SkypeNet shall watch silently.


I don't see any unit test for this, is there any?

Also, why would you use a pure javascript implementation of Zlib when native implementations are available in both node.js and all supported browsers?


I can move ````bool hardware_flag = false;```` into the big while loop, but ````char* result_path = NULL;``` not.


It is better to use `warn` log level here.


why ? Drag and Drop Between Lists Bug #61 and update card server side.


かんぺきです！


Could you give an example of the contents of the different variables created by pkg_check_modules? I'd like to know if this can somehow be solved without so many conditionals.

Is it necessary to link Sodium and libuecc statically? As you can see, I'm not familiar with the Android NDK...


Hi Marco,

It was my first attempt at contributing, so may not have made optimum use
of FishTest so far. My apologies.

I have two "Yellow" results so far.
Total: 64025 W: 10836 L: 10630 D: 42559 sprt @ 60+0.05 th 1
Total: 103449 W: 20945 L: 20765 D: 61739 sprt @ 15+0.05 th 1

There is more than one parameter to tune in the code and I do not think I
have achieved anywhere near what is possible.

Parameter 1) When a Quick move is made, how to use the saved time? I've
added code to allot time to the next move. Need to identify what is optimum
time to use on next move. (Half the saved time, all the saved time, 3/4th
the saved time?)

Parameter 2) How much time to spend searching for 2nd best move. (To what
depth to search?)

Parameter 3) When to play a Quick Move? When the best move score is 2 pawns
better than 2nd best?

I think with Ponder On, a measurable ELO gain will come from Quick move
code. But, I don't know of a way to test this. Does FishTest support
testing with Ponder On?

What is the optimal way to tune for multiple parameters like this? Should I
use the SPSA feature?

I will limit the test runs to 20,000 games & sprt @ 15+0.05 th 1 and keep
the priority low. (What priority do you suggest -3?)
Please consider letting me pursue this till I am convinced no further gains
are available.

Regards,
Rohan

On Tue, Jan 6, 2015 at 12:14 PM, Marco Costalba <notifications@github.com>
wrote:

> You are now starting to overtune this series: already 5 tests on the same
> topic. Please consider changing topic.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rohanryan/Stockfish/commit/820a793530495825ffd3548a634b3fdb8ac74bd1#commitcomment-9164938>
> .
>


This should fail as soon as an user tries to set `conf.user` or `conf.group`, as it is done for the `pmtu` option on non-Linux systems.


I don't like implicit imports, but typing enum.ScalingEvent.... got a bit much. Thoughts on a better way to organise the enums?


So many apostrophes...


JSHint reports mixed quotes issue here...


Coding style: please don't use C++-style comments


should we make this jump into a filter function instead of using a lamba AND list comprehension? (or is there a better way to do this?)


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


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


Sorry these extra `AddStaticResource` calls should have been removed.


Please put the whole two lines in the condition and duplicate `fastd_peer_reset` in the other branch to make this easier to understand.


Remove `Julia.app`?


Maybe it is better to reject a promise here instead of just throwing. At least one reason is consistancy with line 273...


As `fastd_cpuid` isn't called very often, let's just drop the conditional and the non-PIC version (like it was done in the ticket in the comment as well)


will build and run too. At the moment user manually types input.


I was debating whether to raise an exception or exit_with_error...


can you explain that why static_initializer is not needed any more?


r+


Otherwise LGTM


Hi Jason,

You're right, I had added the SF2 Form component to my composer.json. Let me test this again. I think we should add this component ASAP in preparation for the moving of forms to AbstractType (that I also proposed). Right now the forms are not re-usable and validation is ad-hoc, whereas it could much easier be handled by the SF2 Form + Validation components.


I think this should be called something like `fastd_socket_android_protect` and get a `fastd_socket_t *sock`, so the socket can be properly closed when the protection fails.


pik


Yes, but this is about indentation. Eclipse removes leading spaces from otherwise empty lines.


sincere apologies for this shifting...will take care.


This should be moved to `compat.h`.

Furthermore, there's only one place where stpcpy is used at all, so I guess it would make sense to get rid of it completely... I'll do that if I find time today.


「SITE_SITEURL」のところ「WP_SITEURL」ではないでしょうか？
`$ vagrant up`したら
以下エラーが表示されました。
```
uninitialized constant WP_SITEURL (NameError)
```


@imagescape Thanks. We'll have to adjust the migrations, too, right?


Just change it to `epoll_create(1)` unconditionally


We should not require the removal of the result tables to ensure correctness.  The lifetime of the result tables depends on factors that may be beyond our control (when the user wants to retrieve the results); that lifetime may extend for more than one year.  (In addition, I don't see why multiple queries can't be issued within the same second or even millisecond, potentially leading to collisions.)  I don't see any obvious reason why the resultName and lockName need to be in a sequence.  A unique id per query seems safest.  I assume that unique id is recorded somewhere (other than the log) so that it can be associated with the query.


I need to think about this part a bit longer. This might create a race condition, but I'm not sure at the moment...


Of these, `sys/un.h` is the only one not pulled in by `fastd.h`.


Please don't use variables declared in outer scope of higher order function. In this instance it is even worse because `idx` is hoisted to be global for QueryString.stringify/QueryString.encode. The same might be written as
```js
return obj.map(function(item, idx) {
  var ks = name || idx;
```


やっぱりこれは、git pull --rebaseでいけそうじゃないかな？

fix_gulpfileのPRをmasterにマージしてからだけど。


Please completely duplicate `fastd_tuntap_open`, like it is done for the other supported systems as well.


Nok var det klogt, men det var også testet ;)
Dog forstår jeg ikke helt, hvordan din implementation får `LoadsFromLatePartiallyCachedStream` til gå grøn?


Stimme zu.


Is this TUN-only, or does it also work with TAP? If it doesn't work with TAP, it should fail here if TAP mode is configured.


Because an IMU is different, and Ideally you would simulate additional things like noise etc. The plugin is very simple, so I see no reason to "hide" a ground truth sensor for pose behind an IMU sensor, which you would always believe to be an orientation sensor if you dont know whats inside. IMO there should be a sensor for an IMU, one for GPS, and for a ground truth pose.


enabled console


Obviously, there are lots of coding style issues in the imported code. Besides the indentation and general spacing, all "internal" functions must be declared static.


I thought about this, but since we have no maximum block size at the moment I don't know where to put it.

There is sort of an implicit (albeit fairly loose) one already since we are expecting 2 hunks so it does have to go back to deciding they are the same at some point.


Yes, all changes should go in this file :)

You can read more about what LESS is here: lesscss.org


`idx` is not incremented on each map function call. Is this intended?


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1788](http://teamcity.monogame.net/viewLog.html?buildId=4195&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 289, ignored: 6 Build time: 00:15:49


Har du gjort dig nogen yderligere tanker om hvordan api'et skulle være til #21?


4558_hpwh_coil_removing_heat_from_tank (nmerket) - x86_64-MacOS-10.9-clang: OK (1577 of 1578 tests passed)

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


But inside the simulation there is no difference for IMU and or ground
truth position (aka GPS).
If the 'Pose' sensor (maybe "imu" is misleading) can be configured with
different variances (for position/orientation). This will absolutly do
the job. I see absolutly no reason to double the code for
position/orientation/gps.
In Avalon we have also a 'deph' sensor, which outputs only 'z', whis
could be archived by setting these properties, there is no need to add a
new sensor-implementation.

Maybe a for some setups (as already done in avalon) the complete pose is
requested, (because we don't want to simulate the complete pose-estimator).
The "Semantic", is this sensor is a imu or a gps or a ground-truth
should not enforce a separation from the code.
This abstraction could done in syskit.

On 06.01.2015 08:43, Jakob Schwendner wrote:
>
> Because an IMU is different, and Ideally you would simulate additional
> things like noise etc. The plugin is very simple, so I see no reason
> to "hide" a ground truth sensor for pose behind an IMU sensor, which
> you would always believe to be an orientation sensor if you dont know
> whats inside. IMO there should be a sensor for an IMU, one for GPS,
> and for a ground truth pose.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rock-simulation/simulation-orogen-mars/commit/603b4e239d7e692f2ebd1ca42ae9a317814fd824#commitcomment-9165286>.
>

--
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 1
  28359 Bremen, Germany

  Zentrale: +49 421 178 45-6611

  Besuchsadresse der Nebengeschäftstelle:
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Tel.:    +49 421 178 45-4193
  Empfang: +49 421 178 45-6600
  Fax:     +49 421 178 45-4150
  E-Mail:  matthias.goldhoorn@informatik.uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik


The test case is wine's d3d9_test.exe visual, function update_surface_test().
on wine it fails here: http://source.winehq.org/source/dlls/wined3d/surface.c#1583
and prints "Destination rectangle not block-aligned".
It looks like this is a limitation of the used texture DXT1, which has to be multiple of 4.
see here: http://msdn.microsoft.com/en-us/library/windows/desktop/bb173059%28v=vs.85%29.aspx
I'm going to do more tests.


###### Crop
```
var img = C4Image("img")
img.crop(C4Rect(10,10,img.width-10,10))
view.add(img)
```


Hi Sol,

On Mon, Jan 5, 2015 at 5:49 PM, Sol Simpson <notifications@github.com>
wrote:

> This is expected actually. ;) Events are sent from iohub to psychopy as a
> list of lists, where each list element is the list of attribute values for
> that event. Then on the psychopy side, getEvents() turns each event list
> into one of 3 types:
>

thanks for the clarification!

> Is the 'NT' part a big issue for you?
>

Not really, I just never happened to notice it before, and I thought
something is wrong.
Glad it's not! ;)

Take care,

    Richard


crashing because respondsToSelector is missing...

fixed with:
if ([self.delegate respondsToSelector:@selector(keyboardControllerKeyboardDidHide:)]) {
            [self.delegate keyboardControllerKeyboardDidHide:self];
}
please add this to the latest version ;)


Accessing your views directly in the browser perhaps? Or wrong extension (should be `yourfilename.blade.php`? Also: ask in the forums.


Hey Ben, what do you think of this?


FixPGOLinkingOfSQLite (lefticus) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Everything appears to be working as expected with this code, yay :)


I'll setup a email account (Nothing Special only a consumer email from hotmail or something)


Thanks.

This is the type of code that is likely not to be changed once fixed, so it's important to get exactly the right checks.


'We have two template event callbacks:' Nous avons donc deux rappels émanant d'évènements du template: ou qqchose comme ça?
J'avoue que je ne me souviens plus si l'on utilise callback ou rappel dans le reste du livre...


@httpete
You were right about getting undefined, it was a tiny teeny bug in the code which is now addressed in #56. Just pull latest sources and re-test your code, above.


Probably not anymore. There was a time when patch level upgrades to nokogiri would break this gem, hence the specific version numbering.


We can make it disable by default and enabled via an option.
So instead of removing the code with unmodifiable lists, you can simply add a nested if via:
```
<if(options.("java_unmodifiable_list"))>
```
Sames goes for the finally block below.


"des événements classiques dû à un clic" - des évènements par défaut?


@henryju FYI, you can use isEmpty() instead of isEqualTo(""), I thought it nicer but it's only my point of view !


récupérer -> récupéré


あざます。修正しました。


This was out of range.


Nice merge!, did you handle all rejects by hand or did you use some nice tool i didnt hear of?


lasjf;lasjfdl


It sounds logical to me that the string for "one" should not be "all 1 cache" but e.g. "this cache".


"qui met à jour les champs spécifiés" -> qui remplace un ensemble de champs
(which replaces a set of specified fields while leaving the others untouched)


any particular reason you added this? it looks unused. Assuming no, I'm deleting it in my merge for https://github.com/TelescopeJS/Telescope/pull/672


"Rajouter" -> "Ajouter"?


No, like I've said: In some images /tmp is persistent.
E.g. on the Fedora image /tmp is part of the / filesystem.
After a reboot the $TEMP_KERNEL_DIR did still exist.


Why not just store `highScore` in the local variable before you re-initialize the state?


I tried a few combinations of internal resolution and window size and none of them failed for me on Windows 7.

-[Unknown]


Hi,

Can you please share source of this commit?


It would actually be better if it was flipped around. In particular it would allow me to call it like:

`tst_timeout 3 sleep 1`


@cprice404 it looks like it was originally added in bd8d09747fd6c0dce89c17da41eb67ad92823cf7, and the error message has been moved around to https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/indirection.rb#L297. Does it mean the authorization message, where we interpolate the `"... on #{request}"`, will be less meaningful now?


@mcculls Thanks!


@mgholam   It is good to throw an exception to notice user that recursion has reached the limit.
however, if the user knows exactly what he/she want and the exception will bring a null result.
How about this ?
If the user set the value of Parameters.SerializerMaxDepth = MAX_DEPTH, that means he/she knows the fact. And fastJSON try to solve it.
otherwise, fastJSON show give him/her an exception when _current_deption > (default)_MAX_DEPTH.
:-)


1. This works too (and catches valid cases, i.e. not timeout == 0, etc):
<pre>
case "$1" in
^[1-9]([0-9]*)?$)
    timeout=$1
    ;;
*)
    echo "timeout must be a non-zero integral value"
    ;;
esac
</pre>
2. Although opengroup.org says sleep must accept an integral value, many implementations actually support floating point values.


Merge from main


<!-- PMABOT:TAB -->
This commit is using tab character for indentation instead of spaces, what is mandated by phpMyAdmin. Please check our [Developer guidelines](http://wiki.phpmyadmin.net/pma/Developer_guidelines#Indentation) for more information.

Offending files: libraries/sql-formatter/README.md


<!-- PMABOT:SPACE -->
This commit contains trailing whitespace, what is prohibited in phpMyAdmin. Please check our [Developer guidelines](http://wiki.phpmyadmin.net/pma/Developer_guidelines#Indentation) for more information.

Offending files: libraries/sql-formatter/README.md, libraries/sql-formatter/lib/SqlFormatter.php


"pourtant vous ne pourrez pas les modifier" -> "pourtant vous ne pourrez pas les modifier tout de suite"
(you won't be able to actually edit anything right now)


Merge branch 'readme-enhance' into dev


HVACSizingSim_CoincidentPlant (EnergyArchmage) - i386-Windows-7-VisualStudio-12: Build Failed

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


But why you need to have version within the PHP file?


"refusées"


"chargées"


You should have `$ git submodule update` instead of checking in the old revision of the project again :/ Effectively this reverts 12e062a, which is not good.


bac1d80ab730b8a05839b6eada92f73d73349ea3 1 parent f723707
 toverscriptercybergodscripter authored an hour ago
![sunflower](https://cloud.githubusercontent.com/assets/8031438/5625936/7ed2bb48-9584-11e4-8c2e-6809b5061580.gif)++000


I suggest to run a LTC test with SPRT(0, 4)


*server-side* peut être traduit par "côté serveur" je pense vu que l'on utilise "client'"un peu plus haut?


Yay!


Hrmf!


Putting it in auto0.g is a nice solution. Unfortunately, I'd have to modify my workflow because I currently do all of my printing from auto0.g, switching out that file with copy of whatever gcode file I want to run so that I can print without using USB or an LCD. Putting setup stuff like that in auto0.g and my print in auto1.g should work, but I haven't tried it.

I really prefer to stay in millimeter mode through most of my start code and switch back to it in my end code so that host controls work as intended. I also do a good long retraction at the beginning of prints and re-priming at the beginning that should logically be in millimeters, since the point is to pull the filament completely out of the hot zone before it cools to make filament changes easy.

When I use Cura, I use volumetric mode and have the following lines near the end of my start code:

M200 D{filament_diameter} T0
M200 D{filament_diameter2} T1

and these ones near the beginning of my end code:

M200 D0 T0
M200 D0 T1

But I'll take your point that there are a variety of places where it might make sense to put it, so it probably shouldn't be put in the start code automatically, though I would like the tooltip for the volumetric mode checkbox to explain how to add a line like the above to the start code if you don't have something else to set it.


looks good to me


Je pense que l'original est plus dans le sens "limiter les éditions" que de parler des limites de l'édition?
(Limiting edits)


The case was wrong, however the grep above should be "echo $1 | grep -o '^[1-9][0-9]*$', e.g.

<pre>
fuji:~ ngie$ ./natural_num.sh 3
3
fuji:~ ngie$ ./natural_num.sh 300
300
fuji:~ ngie$ ./natural_num.sh 300.0
fuji:~ ngie$ ./natural_num.sh 0
fuji:~ ngie$ ./natural_num.sh 1
1
fuji:~ ngie$ ./natural_num.sh 100000
100000
</pre>


some tests failed:
exception: http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/2687
exception: http://buildbot.rust-lang.org/builders/auto-win-64-nopt-t/builds/1515


Right. Will fix it.


Uhm, yes it is? When I run `make install` (with --prefix=/usr), I get
```
/usr/lib/libuv.a
/usr/lib/libuv.la
/usr/lib/libuv.so -> libuv.so.1.0.0
/usr/lib/libuv.so.1 -> libuv.so.1.0.0
/usr/lib/libuv.so.1.0.0
```


@bors: retry


thank you sir :+1:


OK :-)


+ }		 }
+ @@ -15,26 +15,29 @@ h1 {
+ h3 {		 h3 {
+   font-size: 1.5em;		   font-size: 1.5em;
+ }		 }
++#top-title, .graph-title {
++  font-weight: normal;
++  padding-left: 30px;
++}
++#loading, #errormessage {
++  font-weight: normal;
++  text-align: center;
++}
+ .graph-section {		 .graph-section {
+   float: left;		   float: left;
+   margin: 20px 0px;		   margin: 20px 0px;
+ }		 }
+ .graph-container .y-axis {		 .graph-container .y-axis {
+-  width: 50px;
+   float: left;		   float: left;
++  height: 300px;
++  width: 50px;
+ }		 }
+ .graph-container .graph {		 .graph-container .graph {
+   float: left;		   float: left;
++  height: 300px;
+ }		 }
+-#top-title,.graph-title {		+.legend {
+-  font-weight: normal;
+-  padding-left: 30px;
+-}++++


* 这个会影响调用mob的用户，如果他们不想用 box-sizing,而是想用默认的，就被坑了。能否只对form组件添加box-sizing 属性


saw approval from alexcrichton
at https://github.com/alexcrichton/rust/commit/4b359e3aeeaf97a190c5a7ecff8815b7b5734ece


merging alexcrichton/rust/rollup = 4b359e3a into auto


status: {"merge_sha": "340ac040f7603e169a3739c65956ed2213622be5"}


alexcrichton/rust/rollup = 4b359e3a merged ok, testing candidate = 340ac040


bac1d80 5 minutes ago+++++///++00


The patch has been on the mailing list for review for quite some time, you should have commented it there...

The thing is that there are follow up patches that fixes testcases using this function. So changing it now would mean fixing them as well.


Isn't there another option?
5. Switch to Consul, which already implements ACLs.


For the floating point values. Been there, done that in the review on mailing list. There are implementations in use that does not support it. For example busybox.


KRO view id 1311 is conflicted with JRO view id,
i will use JRO for now, and let see will KRO or JRO change it


TeamCity ChameleonForms :: Continuous Integration [Build 217](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3486&buildTypeId=bt20) is now running


This install should be `npm install -g bower`.


Again, we want to do `npm install -g gulp`.


TeamCity ChameleonForms :: Continuous Integration [Build 2.0.0-PullRequest113+009](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3486&buildTypeId=bt20) outcome was **FAILURE**
Summary: Tests passed: 2339; compilation error: ChameleonForms.Tests\ChameleonForms.Tests.csproj (new) Build time: 0:0:0


I am a nice comment


@pepol "a" shouldnt be there.


This counter will be incresed twice per tick. This TickEvent is a pre tick and a post tick.


Create ...idcraraanjobruntoverallonaantorunnerrun	 b4dd35b
 	Create plusdotbot0dotplusbotaan …	 cf787dd
 	fn007 …	 006fa98
 	8ballpluss++innn …	 e3f6281


Create ...idcraraanjobruntoverallonaantorunnerrun	 b4dd35b
 	Create plusdotbot0dotplusbotaan …	 cf787dd
 	fn007 …	 006fa98
 	8ballpluss++innn …	 e3f6281+


We should follow kRO, jRO won't follow kRO, and neither change, since jRO holds major share.


please consider using the newly added Haddock syntax for collapsible examples which `base-4.8.0.0` makes extensive use of; see e.g.

 http://hackage.haskell.org/package/base-4.8.0.0/candidate/docs/Data-Maybe.html


Create ...idcraraanjobruntoverallonaantorunnerrun	 b4dd35b
 	Create plusdotbot0dotplusbotaan …	 cf787dd
 	fn007 …	 006fa98
 	8ballpluss++innn …	 e3f6281+++


Seriously? Try to learn a standard or two.


committing for Jan Monthly EDA Course


This doesn't check that the secretAccountID is one of the SigningAccount's currently allowed keys?


The next commits resolve bld\aui and bld\wv, I see nothing that would
fix guistat.c in bld\setupgui. I am updated to the latest commit.

Jiří Malák wrote:
> I am sorry. It was temporary problem.
> It was fixed by next commit.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/open-watcom/open-watcom-v2/commit/ed991f848eaa87f4a74c502a0432b4a619d43693#commitcomment-9164956>.
>


Oops, thanks for noticing :-)


Why to use numbers instead of constants? Constants are easier to read and less prone to change, if people behind of PHP for some reason decides to change the numbers from those constants (which I doubt, though).

Good coding practice is always to use constants if they are defined -- basically they are just aliases for the numbers in this case, to make the code more readable.


LOL


The fault was mine, I was setting height with a string pixel value (e.g. "600px") instead of as an integer (e.g. 600).  We should probably document that it is supposed to be an integer corresponding to the number of pixels.


@shiftkey for my curiosity: which tags have we not kept in sync?


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1789](http://teamcity.monogame.net/viewLog.html?buildId=4197&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **FAILURE**
Summary: Snapshot dependency failed: MonoGame :: Develop (Mac) Build time: 00:00:00


Nice....


1: M100 needs more reviewers
1: M101 signature is missing


4: I102 copyright year is outdated, expected 2015 but got 2014
62: D202 No blank lines allowed *after* function docstring, found 1
62: D400 First line should end with '.', not 's'
62: D205 Blank line missing between one-line summary and description
90: D200 One-line docstring should not occupy 3 lines


I've found a couple more with a proposed fix in https://github.com/w3c/mediacapture-main/pull/110


4: I102 copyright year is outdated, expected 2015 but got 2014


4: I102 copyright year is outdated, expected 2015 but got 2014
262: D401 First line should be imperative: 'Searche', not 'Searches'
262: D209 Put multi-line docstring closing quotes on separate line
262: D400 First line should end with '.', not 'd'
262: D205 Blank line missing between one-line summary and description


The alert box doesn't say `HAI`, it says `Hi from Scala-js-dom`


Thank you!


i Have used same type tools like ghostphiser pwnstar, karma (bt i have not tried it yet) it would be more sophisticated tool if it also redirect  the  traffic of opera mini (on android) or Facebook app(since it web app )........................i am going try and get back....good work :D


but I want da fancy java


Thanks for the pull request.

Container based builds and fast finish are great ideas. I'm not sure of the value of testing in pypy since the script can only run in WeeChat and that only supports regular cpython.


Trailing whitespace? What do you mean?

I may just convert it to a table of functions. I don't like having holes in
the array. Kind of messy, I guess.
On Jan 5, 2015 10:57 PM, "Robert Cochran" <notifications@github.com> wrote:

> Nothing looks obviously wrong here. You did manage to add 'trailing
> whitespace' (src/main.c:31) though. Check to make you don't leave that in
> your
> source ('git diff' helpfully highlights trailing whitespace in red) Also,
> if we know that strings will be measured via strlen(), then I think there
> isn't a need to have a slot for it in typeSizes. (src/vars.c:14-15)
> Otherwise this patch looks good to me.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/TheUnderscores/protolang/commit/cefe42c2ab91bdc03176a42a7afc1119b579df33#commitcomment-9165026>
> .
>


@pepol the comma is redundant.


The authors file is generated, so duplicates can occur dependent on the used ids of the git commits.


hey man just a quick question, how do you know where and how to fix stuff like this?
I mean debugging must be pretty hard as you have to build the whole rom source again and again isnt it so? Im just wondering. thanks for that fix


Спасибо, исправил. :)


enumerate iterable objeyi numaralandırma yapan fonk
desc nerde kullandızınız hocam?


see pr #110


oh you're right, I ended up not using it.


It never ends. :(

I'll look into the problem. The workarounds are documented in the source code. I think that is good enough. Building external documentation and keeping it in sync would be more trouble than it is worth.


Removed pypy & pypy3


@pepol please adress my comments, otherwise LGTM!


Huh, this issue still returns. I've come up with an idea to disable the gpu process to solve this issue. Try passing the --disable-gpu and --disable-gpu-sandbox flags. You can do this programmatically in the OnBeforeCommandLineProcessing callback. When passing flags in this callback it should be without the "--" prefix. It should also be possible to pass these flags from command line when launching executable.


I would personally prefer if we use the correct quotes (“”) in text, and the other in code (where they’re required); I can make a PR either way, but the editors need to chime in on their preference (since they’ll have to maintain the document one way or another in the long run)


Hi,
I'm working on this on my (rare) spare time. I thought about caching, your approach sounds interesting but bears complexity due to its asynchronous nature. What do you mean with "reorganzing boards"?

I'm working on fixing the incomplete title problem. I intend to wrap the title to the subtitle if the string is too long.


Oui, contrib ou unmaintained en indiquant dans le README du repo que ces
projets cherchent un mainteneur et sont à adopter ;)

Et… Bonne année !

2014-12-22 20:44 GMT+01:00 Laurent Destailleur <notifications@github.com>:

> Le terme obsolete n'est pas le bon. C'est le projet qui accueil tous les
> trucs qui sont pas maintenues directement par l'équipe.
> On pourrait renommer en "contrib" ?
>
>
> 2014-12-22 14:54 GMT+01:00 Raphaël Doursenaud <notifications@github.com>:
>
> > It's a bit sad you moved it under the obsolete repo.
> > I was under the impression you would create a dedicated repo for this
> > subproject so it can foster contributions from the community. Putting it
> > there is like putting a death sentence over it.
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/Dolibarr/obsolete/commit/6a9a171845a6ad03fb4f05db81d28712988d5be8#commitcomment-9064057>
>
> > .
> >
>
>
>
> --
> Laurent Destailleur (alias Eldy)
> ------------------------------------------------------------------------------------
>
> Social networks of my OpenSource projects:
> Dolibarr Google+: https://plus.google.com/+DolibarrOrg/
> Dolibarr Facebook: https://www.facebook.com/dolibarr
> Dolibarr Twitter: http://www.twitter.com/dolibarr
> AWStats Google+: https://plus.google.com/+AWStatsOrgPoject/
> AWStats Facebook: https://www.facebook.com/awstats.org
> AWStats Twitter: http://www.twitter.com/awstats_project
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Dolibarr/obsolete/commit/6a9a171845a6ad03fb4f05db81d28712988d5be8#commitcomment-9068174>
> .
>

--
*Raphaël Doursenaud*
Directeur technique (CTO)
Expert certifié en déploiement Google Apps
<https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist>
+33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10

--
 <http://gpcsolutions.fr>
http://gpcsolutions.fr
Technopole Hélioparc
2 avenue du Président Pierre Angot
64053 PAU CEDEX 9
SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921
<http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>


Build is still broken. Please see http://ci.cgeo.org/job/c-geo/3218/console
Build was first broken at http://ci.cgeo.org/job/c-geo/3129/


4558_hpwh_coil_removing_heat_from_tank (nmerket) - x86_64-MacOS-10.9-clang-Debug: OK (1577 of 1578 tests passed)

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


Maybe update {create,new}_vm in app/models/compute_resource.rb too?


sorry


You're right that's a better way. See 308d529.


@elemoine any suggestion?


Booted fine but one build booted with low storage issues. Atm idk why so I'm stopping for the day.


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


parse_args also calls symbolize_keys, that should probably be changed to deep too, as it's used via the clone_vm method.


Right, the commit message should have listed the at least some of the tags by example.


clean.bat deletes *.pdb but clean.cmd doesn't.
Any reason not to use switches for rmdir?
The following clean.bat works successfully, I believe should also work for the OS2 clean.cmd file.

@echo off
if not exist %OWBINDIR%\builder.exe goto no_builder
REM delete the builder and wmake build directories
if exist %OWSRCDIR%\builder\%OWOBJDIR% rmdir /S /Q %OWSRCDIR%\builder\%OWOBJDIR%
if exist %OWSRCDIR%\wmake\%OWOBJDIR% rmdir /S /Q %OWSRCDIR%\wmake\%OWOBJDIR%
REM clean all projects
cd %OWSRCDIR%
builder -i clean
builder -i bootclean
REM Finally delete the builder and wmake executables
if exist %OWBINDIR%\builder.exe del %OWBINDIR%\builder.exe
goto wmake_del
:no_builder
echo Cannot find builder - have you run your setvars.bat and build.bat?
:wmake_del
if exist %OWBINDIR%\wmake.exe del %OWBINDIR%\wmake.exe
cd %OWROOT%


A recursive descent parser might be more readable; I've just written a toy (and obviously incomplete and not that efficient) implementation [here](https://github.com/jonasmalacofilho/csv-rdp). The gist? Keep things simple, with (mostly) one function per production rule.

@aszasz, (since you've taken on this project) see which approch you think is best...


@nick4me this is how to install the package.


Awesome :D!! :cake:


Alles klar, ich schau noch mal drüber, damit kürzere Sätze bei rauskommen.

Bei den Passwörtern kannst du mich gerne eines besseren überzeugen, so ganz zufrieden bin ich auch nicht, jedoch wollte ich dies von dem Hinterlegen der Keys beim Kompilieren von Gluon abgrenzen.

Schönen Gruß an @tcatm :smiley_cat:


Pas IP , ID


@dscho at the time `1.9.5.msysgit.0` wasn't pushed for the `git` submodule, which meant building msysgit would autogenerate the version. This was just our workaround so our users could see they weren't behind, so i tagged it to indicate it was different.


HVACSizingSim_CoincidentPlant (EnergyArchmage) - Win64-Windows-7-VisualStudio-12: Build Failed

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


Need to clear this flag after the checksum is added? (otherwise I think that successive calls to `want_modify()` will recalculate and screw up the checksum.)


These last two blocks of deletions seem to be an error.


These last blocks of deletions seem to be an error.


What did I miss?


add commit 2


Ah yes, I had exactly same issue, but I can compile with normaly ART without any patches.


sdfsdfsdfsdfsdf


@petergoldstein I've renamed supervisor_class to server_class as this makes more sense IMHO.


Thank you for the fix. :-)


you might want to use circleCI or some other CI to run the tests. this would eliminate need for a dedicated DB with hardcoded credentials.


format (space after commas)


not C# naming convention for consts.


Yes, I guess it should also should set 'the other' flag `PACKET_CSUM_VALID`, but I think that one is only used on the receive path.   This is almost untested, since right now the NFV test script fails to connect with the VMs for some reason.


typo here, should be "create"


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


It seems these changes (apart from the version change) should be cherry-picked to 6.2.x, is that right?


Actually, the first test you asked for is already there - https://github.com/Arnavion/TypeScript/blob/2aa5e91a/tests/baselines/reference/templateStringWithEmptyLiteralPortions.js#L12


2: I102 copyright year is outdated, expected 2015 but got 2011
27:6: E126 continuation line over-indented for hanging indent
30:37: E126 continuation line over-indented for hanging indent
34:9: E126 continuation line over-indented for hanging indent
45:31: E126 continuation line over-indented for hanging indent
52:1: E302 expected 2 blank lines, found 1
52: D200 One-line docstring should not occupy 2 lines
55:11: E221 multiple spaces before operator
76:1: E302 expected 2 blank lines, found 1
76: D290 White spaces around docstring should be trimmed.
76: D301 Use r""" if any backslashes in a docstring
81:75: E502 the backslash is redundant between brackets
82:12: E128 continuation line under-indented for visual indent
85:64: E502 the backslash is redundant between brackets
86:12: E128 continuation line under-indented for visual indent
86:80: E502 the backslash is redundant between brackets
87:12: E128 continuation line under-indented for visual indent
90:79: E502 the backslash is redundant between brackets
91:12: E128 continuation line under-indented for visual indent
98:17: E201 whitespace after '{'
98:64: E202 whitespace before '}'
100:1: E302 expected 2 blank lines, found 1
100: D200 One-line docstring should not occupy 2 lines
110:41: E201 whitespace after '('
110:57: E202 whitespace before ')'
114:25: E201 whitespace after '['
114:63: E202 whitespace before ']'
115:35: E201 whitespace after '['
115:93: E202 whitespace before ']'
118:45: E201 whitespace after '('
118:60: E202 whitespace before ')'
119:21: E201 whitespace after '['
119:70: E202 whitespace before ']'
122:17: E712 comparison to True should be 'if cond is True:' or 'if cond:'
131:1: E302 expected 2 blank lines, found 1
131: D400 First line should end with '.', not 'd'
131: D205 Blank line missing between one-line summary and description
141:1: E302 expected 2 blank lines, found 1
141: D205 Blank line missing between one-line summary and description
152:34: E261 at least two spaces before inline comment
152:35: E262 inline comment should start with '# '
156:16: W601 .has_key() is deprecated, use 'in'
159:42: E261 at least two spaces before inline comment
159:43: E262 inline comment should start with '# '
163:97: W601 .has_key() is deprecated, use 'in'
223:34: E261 at least two spaces before inline comment
223:35: E262 inline comment should start with '# '
250:1: E302 expected 2 blank lines, found 1
250: D205 Blank line missing between one-line summary and description
261:5: F841 local variable 'cache_dirty' is assigned to but never used
274:34: E261 at least two spaces before inline comment
274:35: E262 inline comment should start with '# '
295:31: E201 whitespace after '('
295:50: E202 whitespace before ')'
296:31: E201 whitespace after '('
296:50: E202 whitespace before ')'
297:20: E711 comparison to None should be 'if cond is None:'
303:14: E261 at least two spaces before inline comment
309:31: E201 whitespace after '('
309:50: E202 whitespace before ')'
310:20: E711 comparison to None should be 'if cond is None:'
318:31: E201 whitespace after '('
318:50: E202 whitespace before ')'
319:31: E201 whitespace after '('
319:50: E202 whitespace before ')'
320:20: E711 comparison to None should be 'if cond is None:'
335:1: E302 expected 2 blank lines, found 1
335: D205 Blank line missing between one-line summary and description
346:52: E261 at least two spaces before inline comment
346:53: E262 inline comment should start with '# '
347:5: F841 local variable 'cache_dirty' is assigned to but never used
355:34: E261 at least two spaces before inline comment
355:35: E262 inline comment should start with '# '
380:1: E302 expected 2 blank lines, found 1
380: D200 One-line docstring should not occupy 2 lines
395:9: E125 continuation line with same indent as next logical line
418:1: E302 expected 2 blank lines, found 1
418: D209 Put multi-line docstring closing quotes on separate line
418: D205 Blank line missing between one-line summary and description
418: D208 Docstring is over-indented
435:36: E201 whitespace after '('
435:62: E202 whitespace before ')'
439:40: E127 continuation line over-indented for visual indent
440:42: E261 at least two spaces before inline comment
440:43: E262 inline comment should start with '# '
442:14: E261 at least two spaces before inline comment
442:15: E262 inline comment should start with '# '
444:36: E201 whitespace after '('
444:51: E202 whitespace before ')'
465:1: E302 expected 2 blank lines, found 1
465: D401 First line should be imperative: 'Return', not 'Returns'
465: D209 Put multi-line docstring closing quotes on separate line
465: D400 First line should end with '.', not ')'
465: D205 Blank line missing between one-line summary and description
465: D208 Docstring is over-indented
473:18: E201 whitespace after '('
473:27: E202 whitespace before ')'
475:1: E302 expected 2 blank lines, found 1
475: D209 Put multi-line docstring closing quotes on separate line
475: D400 First line should end with '.', not 'o'
475: D205 Blank line missing between one-line summary and description
485:1: E302 expected 2 blank lines, found 1
485: D400 First line should end with '.', not '}'
485: D205 Blank line missing between one-line summary and description
498:59: E502 the backslash is redundant between brackets
501:1: E302 expected 2 blank lines, found 1
501: D400 First line should end with '.', not 'd'
501: D205 Blank line missing between one-line summary and description
529:74: E502 the backslash is redundant between brackets
530:32: E713 test for membership should be 'not in'
537:9: F841 local variable 'new_record2_managed_dois' is assigned to but never used
541:78: E502 the backslash is redundant between brackets
542:40: E713 test for membership should be 'not in'
542:37: E127 continuation line over-indented for visual indent
547:60: E502 the backslash is redundant between brackets
549:9: E125 continuation line with same indent as next logical line
552:16: E126 continuation line over-indented for hanging indent
574:27: E127 continuation line over-indented for visual indent


1: M111 unrecognized component name: BibKnowledge


2: I102 copyright year is outdated, expected 2015 but got 2011
26:1: E302 expected 2 blank lines, found 1
26: D290 White spaces around docstring should be trimmed.
26: D203 Expected 1 blank line *before* class docstring, found 0
26: D204 Expected 1 blank line *after* class docstring, found 0
34: D401 First line should be imperative: 'Thi', not 'This'
39:5: E303 too many blank lines (2)
43:56: E261 at least two spaces before inline comment
43:57: E262 inline comment should start with '# '
44:63: E261 at least two spaces before inline comment
44:64: E262 inline comment should start with '# '
45:58: E262 inline comment should start with '# '
46:65: E262 inline comment should start with '# '
47:58: E262 inline comment should start with '# '
48:58: E262 inline comment should start with '# '
49:54: E261 at least two spaces before inline comment
49:55: E262 inline comment should start with '# '
50:61: E261 at least two spaces before inline comment
50:62: E262 inline comment should start with '# '
51:77: E261 at least two spaces before inline comment
51:78: E262 inline comment should start with '# '
52:59: E261 at least two spaces before inline comment
52:60: E262 inline comment should start with '# '
53:63: E261 at least two spaces before inline comment
53:64: E262 inline comment should start with '# '
54:63: E261 at least two spaces before inline comment
54:64: E262 inline comment should start with '# '
55:65: E261 at least two spaces before inline comment
55:66: E262 inline comment should start with '# '
56:56: E261 at least two spaces before inline comment
56:57: E262 inline comment should start with '# '
57:61: E261 at least two spaces before inline comment
57:62: E262 inline comment should start with '# '
58:61: E261 at least two spaces before inline comment
58:62: E262 inline comment should start with '# '
59:57: E261 at least two spaces before inline comment
59:58: E262 inline comment should start with '# '
61:57: E261 at least two spaces before inline comment
61:58: E262 inline comment should start with '# '
62:54: E261 at least two spaces before inline comment
62:55: E262 inline comment should start with '# '
63:59: E261 at least two spaces before inline comment
63:60: E262 inline comment should start with '# '
93:24: E261 at least two spaces before inline comment
93:25: E262 inline comment should start with '# '
124:1: W391 blank line at end of file


1: M111 unrecognized component name: plotextractor


1: D100 Docstring missing
4: I102 copyright year is outdated, expected 2015 but got 2011
20:12: E401 multiple imports on one line
22:28: E126 continuation line over-indented for hanging indent
27:42: E126 continuation line over-indented for hanging indent
30:31: E126 continuation line over-indented for hanging indent
40:53: E261 at least two spaces before inline comment
43:56: E261 at least two spaces before inline comment
44:53: E261 at least two spaces before inline comment
45:53: E261 at least two spaces before inline comment
58:66: E502 the backslash is redundant between brackets
59:9: E128 continuation line under-indented for visual indent
83:1: E302 expected 2 blank lines, found 1
83: D401 First line should be imperative: 'Call', not 'Calls'
83: D202 No blank lines allowed *after* function docstring, found 1
83: D400 First line should end with '.', not 'b'
83: D205 Blank line missing between one-line summary and description
83: D208 Docstring is over-indented
154: D401 First line should be imperative: 'Make', not 'Makes'
154: D400 First line should end with '.', not 'd'
154: D205 Blank line missing between one-line summary and description
154: D208 Docstring is over-indented
177:1: E302 expected 2 blank lines, found 1
177: D401 First line should be imperative: 'Build', not 'Builds'
177: D400 First line should end with '.', not 's'
177: D205 Blank line missing between one-line summary and description
177: D208 Docstring is over-indented
206:1: E302 expected 2 blank lines, found 1
206: D401 First line should be imperative: 'Thi', not 'This'
206: D202 No blank lines allowed *after* function docstring, found 1
206: D400 First line should end with '.', not 'l'
206: D205 Blank line missing between one-line summary and description
233:1: E302 expected 2 blank lines, found 1
233: D400 First line should end with '.', not 'd'
233: D205 Blank line missing between one-line summary and description
299:1: E302 expected 2 blank lines, found 1
299: D401 First line should be imperative: 'Take', not 'Takes'
299: D400 First line should end with '.', not 's'
299: D205 Blank line missing between one-line summary and description
316:20: E711 comparison to None should be 'if cond is not None:'
322:1: E302 expected 2 blank lines, found 1
322: D202 No blank lines allowed *after* function docstring, found 1
322: D400 First line should end with '.', not 'g'
322: D205 Blank line missing between one-line summary and description
357:59: E261 at least two spaces before inline comment
363:1: E302 expected 2 blank lines, found 1
363: D202 No blank lines allowed *after* function docstring, found 1
384:24: E127 continuation line over-indented for visual indent
385:24: E127 continuation line over-indented for visual indent
387:23: E127 continuation line over-indented for visual indent
388:23: E127 continuation line over-indented for visual indent
388:38: E261 at least two spaces before inline comment
419:94: E502 the backslash is redundant between brackets
420:25: E128 continuation line under-indented for visual indent
450:88: E502 the backslash is redundant between brackets
451:19: E128 continuation line under-indented for visual indent
451:66: E502 the backslash is redundant between brackets
452:19: E128 continuation line under-indented for visual indent
469:24: E127 continuation line over-indented for visual indent
483:1: E302 expected 2 blank lines, found 1
483: D202 No blank lines allowed *after* function docstring, found 1
483: D400 First line should end with '.', not 'd'
483: D205 Blank line missing between one-line summary and description
508:23: E711 comparison to None should be 'if cond is not None:'
514:23: E711 comparison to None should be 'if cond is not None:'
522: D202 No blank lines allowed *after* function docstring, found 1
522: D205 Blank line missing between one-line summary and description
536:48: E711 comparison to None should be 'if cond is None:'
545:1: E302 expected 2 blank lines, found 1
545: D202 No blank lines allowed *after* function docstring, found 1
545: D400 First line should end with '.', not ','
545: D205 Blank line missing between one-line summary and description
545: D208 Docstring is over-indented
584:24: E127 continuation line over-indented for visual indent
591:28: E127 continuation line over-indented for visual indent
598:12: E111 indentation is not a multiple of four
602:1: E302 expected 2 blank lines, found 1
602: D202 No blank lines allowed *after* function docstring, found 1
602: D400 First line should end with '.', not ','
602: D205 Blank line missing between one-line summary and description
602: D208 Docstring is over-indented
641:24: E127 continuation line over-indented for visual indent
649:28: E127 continuation line over-indented for visual indent
654:59: E261 at least two spaces before inline comment


1: M111 unrecognized component name: BibConvert


4: I102 copyright year is outdated, expected 2015 but got 2012
49:6: E126 continuation line over-indented for hanging indent
94:60: E502 the backslash is redundant between brackets
99:1: E302 expected 2 blank lines, found 1
99: D400 First line should end with '.', not ':'
99: D205 Blank line missing between one-line summary and description
132:76: E502 the backslash is redundant between brackets
133:37: E502 the backslash is redundant between brackets
138:1: E302 expected 2 blank lines, found 1
138: D200 One-line docstring should not occupy 3 lines
161:76: E502 the backslash is redundant between brackets
162:37: E502 the backslash is redundant between brackets
167:1: E302 expected 2 blank lines, found 1
167: D400 First line should end with '.', not ':'
167: D205 Blank line missing between one-line summary and description
192:76: E502 the backslash is redundant between brackets
193:37: E502 the backslash is redundant between brackets
198:1: E302 expected 2 blank lines, found 1
198: D200 One-line docstring should not occupy 3 lines
213:76: E502 the backslash is redundant between brackets
214:37: E502 the backslash is redundant between brackets
219:1: E302 expected 2 blank lines, found 1
219: D400 First line should end with '.', not ':'
219: D205 Blank line missing between one-line summary and description
244:76: E502 the backslash is redundant between brackets
245:37: E502 the backslash is redundant between brackets
250:1: E302 expected 2 blank lines, found 1
250: D200 One-line docstring should not occupy 3 lines
258:1: E302 expected 2 blank lines, found 1
258: D401 First line should be imperative: 'Processe', not 'Processes'
293:53: E225 missing whitespace around operator
296:49: E225 missing whitespace around operator
299:45: E225 missing whitespace around operator
368:66: E502 the backslash is redundant between brackets
375:64: E502 the backslash is redundant between brackets
399:43: E128 continuation line under-indented for visual indent
400:43: E128 continuation line under-indented for visual indent


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
5: I102 copyright year is outdated, expected 2015 but got 2013
33:28: E126 continuation line over-indented for hanging indent
55:1: E302 expected 2 blank lines, found 1
55: D203 Expected 1 blank line *before* class docstring, found 0
55: D400 First line should end with '.', not 'l'
58: D202 No blank lines allowed *after* method docstring, found 1
58: D400 First line should end with '.', not 'd'
58: D205 Blank line missing between one-line summary and description
91:13: F841 local variable 'last_comment_round_name' is assigned to but never used
97:139: E221 multiple spaces before operator
100:85: E231 missing whitespace after ','
100:87: E221 multiple spaces before operator
129:34: E127 continuation line over-indented for visual indent
141:13: E128 continuation line under-indented for visual indent
143:33: E203 whitespace before ':'
148:36: E225 missing whitespace around operator
149:168: E502 the backslash is redundant between brackets
149:57: E225 missing whitespace around operator
150:67: E127 continuation line over-indented for visual indent
153:13: E124 closing bracket does not match visual indentation
167:14: E127 continuation line over-indented for visual indent
169:14: E124 closing bracket does not match visual indentation
173: D401 First line should be imperative: 'Display', not 'Displays'
173: D205 Blank line missing between one-line summary and description
198: D400 First line should end with '.', not 'd'
198: D205 Blank line missing between one-line summary and description
231:26: E201 whitespace after '{'
231:45: E203 whitespace before ':'
231:22: E222 multiple spaces after operator
232:46: E203 whitespace before ':'
233:44: E203 whitespace before ':'
234:44: E203 whitespace before ':'
235:44: E203 whitespace before ':'
235:62: E261 at least two spaces before inline comment
235:63: E262 inline comment should start with '# '
236:44: E203 whitespace before ':'
236:62: E261 at least two spaces before inline comment
236:63: E262 inline comment should start with '# '
237:25: E124 closing bracket does not match visual indentation
247:13: F841 local variable 'last_comment_round_name' is assigned to but never used
274:106: E231 missing whitespace after ':'
274:143: E231 missing whitespace after ':'
275:32: E222 multiple spaces after operator
297:37: E225 missing whitespace around operator
317:13: E122 continuation line missing indentation or outdented
317:14: E201 whitespace after '{'
317:40: E203 whitespace before ':'
318:40: E203 whitespace before ':'
319:40: E203 whitespace before ':'
320:40: E203 whitespace before ':'
321:40: E203 whitespace before ':'
322:40: E203 whitespace before ':'
323:40: E203 whitespace before ':'
324:40: E203 whitespace before ':'
325:41: E203 whitespace before ':'
326:60: E225 missing whitespace around operator
327:40: E203 whitespace before ':'
328:13: E124 closing bracket does not match visual indentation
340:28: E128 continuation line under-indented for visual indent
341:28: E128 continuation line under-indented for visual indent
344: D400 First line should end with '.', not 'n'
344: D205 Blank line missing between one-line summary and description
383:35: E128 continuation line under-indented for visual indent
384:35: E126 continuation line over-indented for hanging indent
389:81: E225 missing whitespace around operator
389:100: E225 missing whitespace around operator
391:83: E225 missing whitespace around operator
414:105: E225 missing whitespace around operator
416:106: E225 missing whitespace around operator
422:110: E225 missing whitespace around operator
433:111: E271 multiple spaces after keyword
442:37: E126 continuation line over-indented for hanging indent
469:17: E127 continuation line over-indented for visual indent
469:33: E203 whitespace before ':'
470:33: E203 whitespace before ':'
471:33: E203 whitespace before ':'
481: D400 First line should end with '.', not 'n'
481: D205 Blank line missing between one-line summary and description
514:107: E231 missing whitespace after ':'
549:94: E225 missing whitespace around operator
555:99: E225 missing whitespace around operator
570:31: E203 whitespace before ':'
571:16: E128 continuation line under-indented for visual indent
572:16: E128 continuation line under-indented for visual indent
572:31: E203 whitespace before ':'
573:16: E128 continuation line under-indented for visual indent
573:31: E203 whitespace before ':'
574:16: E128 continuation line under-indented for visual indent
575:16: E128 continuation line under-indented for visual indent
575:31: E203 whitespace before ':'
576:16: E128 continuation line under-indented for visual indent
576:31: E203 whitespace before ':'
577:16: E128 continuation line under-indented for visual indent
577:31: E203 whitespace before ':'
578:16: E124 closing bracket does not match visual indentation
581: D400 First line should end with '.', not 's'
581: D205 Blank line missing between one-line summary and description
590:55: E231 missing whitespace after ','
673:13: F841 local variable 'c_round_name' is assigned to but never used
674:13: F841 local variable 'c_restriction' is assigned to but never used
683:26: E201 whitespace after '{'
683:45: E203 whitespace before ':'
683:22: E222 multiple spaces after operator
684:46: E203 whitespace before ':'
685:44: E203 whitespace before ':'
686:44: E203 whitespace before ':'
687:44: E203 whitespace before ':'
688:44: E203 whitespace before ':'
689:44: E203 whitespace before ':'
690:44: E203 whitespace before ':'
691:44: E203 whitespace before ':'
692:44: E203 whitespace before ':'
693:25: E124 closing bracket does not match visual indentation
700:22: E201 whitespace after '{'
700:37: E203 whitespace before ':'
700:19: E222 multiple spaces after operator
701:42: E203 whitespace before ':'
702:36: E203 whitespace before ':'
703:36: E203 whitespace before ':'
705:36: E203 whitespace before ':'
706:36: E203 whitespace before ':'
707:36: E203 whitespace before ':'
708:36: E203 whitespace before ':'
717:13: F841 local variable 'last_comment_round_name' is assigned to but never used
728:20: E127 continuation line over-indented for visual indent
735:35: E127 continuation line over-indented for visual indent
735:73: E221 multiple spaces before operator
744:132: E202 whitespace before ')'
745:33: E127 continuation line over-indented for visual indent
745:71: E221 multiple spaces before operator
746:140: E225 missing whitespace around operator
819:66: E261 at least two spaces before inline comment
827:275: E231 missing whitespace after ':'
828:163: E231 missing whitespace after ':'
861:38: E203 whitespace before ':'
861:62: E231 missing whitespace after ':'
863:38: E203 whitespace before ':'
863:61: E231 missing whitespace after ':'
864:38: E203 whitespace before ':'
864:63: E231 missing whitespace after ':'
866:35: E203 whitespace before ':'
1066:9: E122 continuation line missing indentation or outdented
1067:47: E203 whitespace before ','
1069:43: E225 missing whitespace around operator
1085: D401 First line should be imperative: 'print', not 'prints'
1085: D400 First line should end with '.', not 'm'
1093: D202 No blank lines allowed *after* method docstring, found 1
1093: D400 First line should end with '.', not 'n'
1093: D205 Blank line missing between one-line summary and description
1105:15: E221 multiple spaces before operator
1138: D400 First line should end with '.', not 'n'
1138: D205 Blank line missing between one-line summary and description
1156:15: E221 multiple spaces before operator
1158:9: E122 continuation line missing indentation or outdented
1159:9: E128 continuation line under-indented for visual indent
1160:9: E128 continuation line under-indented for visual indent
1177: D400 First line should end with '.', not 's'
1177: D205 Blank line missing between one-line summary and description
1197:22: E201 whitespace after '{'
1197:40: E203 whitespace before ':'
1198:40: E203 whitespace before ':'
1198:65: E202 whitespace before '}'
1203: D400 First line should end with '.', not 'r'
1203: D205 Blank line missing between one-line summary and description
1210:9: F841 local variable '_' is assigned to but never used
1219: D400 First line should end with '.', not 's'
1219: D205 Blank line missing between one-line summary and description
1238:22: E201 whitespace after '{'
1238:37: E203 whitespace before ':'
1238:19: E222 multiple spaces after operator
1239:42: E203 whitespace before ':'
1240:36: E203 whitespace before ':'
1241:36: E203 whitespace before ':'
1242:36: E203 whitespace before ':'
1243:36: E203 whitespace before ':'
1261:20: E222 multiple spaces after operator
1286:13: E122 continuation line missing indentation or outdented
1287:121: E502 the backslash is redundant between brackets
1288:28: E127 continuation line over-indented for visual indent
1289:100: E502 the backslash is redundant between brackets
1290:31: E127 continuation line over-indented for visual indent
1291:238: E271 multiple spaces after keyword
1300:50: E251 unexpected spaces around keyword / parameter equals
1300:52: E251 unexpected spaces around keyword / parameter equals
1335: D400 First line should end with '.', not 's'
1335: D205 Blank line missing between one-line summary and description
1353:22: E201 whitespace after '{'
1353:37: E203 whitespace before ':'
1353:19: E222 multiple spaces after operator
1354:42: E203 whitespace before ':'
1355:36: E203 whitespace before ':'
1356:36: E203 whitespace before ':'
1357:36: E203 whitespace before ':'
1358:36: E203 whitespace before ':'
1407:1: E128 continuation line under-indented for visual indent
1408:50: E251 unexpected spaces around keyword / parameter equals
1408:52: E251 unexpected spaces around keyword / parameter equals
1449:35: E203 whitespace before ':'
1449:42: E225 missing whitespace around operator
1450:35: E203 whitespace before ':'
1450:41: E225 missing whitespace around operator
1465: D400 First line should end with '.', not 'd'
1465: D205 Blank line missing between one-line summary and description
1472:22: E201 whitespace after '{'
1472:37: E203 whitespace before ':'
1472:19: E222 multiple spaces after operator
1473:42: E203 whitespace before ':'
1474:36: E203 whitespace before ':'
1475:36: E203 whitespace before ':'
1476:36: E203 whitespace before ':'
1477:36: E203 whitespace before ':'
1481:51: E221 multiple spaces before operator
1492:101: E222 multiple spaces after operator
1496: D401 First line should be imperative: 'Create', not 'Creates'
1496: D290 White spaces around docstring should be trimmed.
1496: D205 Blank line missing between one-line summary and description
1519:15: E221 multiple spaces before operator
1559: D400 First line should end with '.', not 'e'
1559: D200 One-line docstring should not occupy 3 lines
1585:19: E225 missing whitespace around operator
1589:36: E203 whitespace before ':'
1592:35: E203 whitespace before ':'
1593:35: E203 whitespace before ':'
1598:39: E225 missing whitespace around operator
1600: D400 First line should end with '.', not 'e'
1615:18: E225 missing whitespace around operator
1646: D400 First line should end with '.', not ')'
1646: D205 Blank line missing between one-line summary and description
1670:27: E127 continuation line over-indented for visual indent
1673:27: E127 continuation line over-indented for visual indent
1696:13: E201 whitespace after '{'
1696:25: E203 whitespace before ':'
1697:25: E203 whitespace before ':'
1698:25: E203 whitespace before ':'
1699:25: E203 whitespace before ':'
1701:26: E203 whitespace before ':'
1702:25: E203 whitespace before ':'
1703:25: E203 whitespace before ':'
1704:25: E203 whitespace before ':'
1734: D401 First line should be imperative: 'output', not 'outputs'
1734: D290 White spaces around docstring should be trimmed.
1734: D400 First line should end with '.', not 'd'
1738: D401 First line should be imperative: 'prepare', not 'prepares'
1738: D290 White spaces around docstring should be trimmed.
1738: D400 First line should end with '.', not 'r'
1753: D401 First line should be imperative: 'output', not 'outputs'
1753: D290 White spaces around docstring should be trimmed.
1753: D400 First line should end with '.', not 'w'
1768:34: E203 whitespace before ':'
1776: D400 First line should end with '.', not 't'
1776: D205 Blank line missing between one-line summary and description
1783:9: F841 local variable '_' is assigned to but never used
1822:17: E128 continuation line under-indented for visual indent
1822:50: E225 missing whitespace around operator
1822:69: E225 missing whitespace around operator
1823:17: E128 continuation line under-indented for visual indent
1823:36: E203 whitespace before ','
1823:23: E231 missing whitespace after ':'
1824:17: E128 continuation line under-indented for visual indent
1824:49: E203 whitespace before ','
1825:17: E128 continuation line under-indented for visual indent
1826:17: E128 continuation line under-indented for visual indent
1832:17: E128 continuation line under-indented for visual indent
1832:50: E225 missing whitespace around operator
1832:69: E225 missing whitespace around operator
1833:17: E128 continuation line under-indented for visual indent
1833:36: E203 whitespace before ','
1833:23: E231 missing whitespace after ':'
1834:17: E128 continuation line under-indented for visual indent
1835:17: E128 continuation line under-indented for visual indent
1840: D400 First line should end with '.', not 't'
1840: D205 Blank line missing between one-line summary and description
1846:9: F841 local variable '_' is assigned to but never used
1880:49: E225 missing whitespace around operator
1880:68: E225 missing whitespace around operator
1881:54: E272 multiple spaces before keyword
1883:49: E225 missing whitespace around operator
1883:68: E225 missing whitespace around operator
1884:54: E272 multiple spaces before keyword
1890:13: E128 continuation line under-indented for visual indent
1890:39: E203 whitespace before ','
1891:13: E128 continuation line under-indented for visual indent
1892:13: E128 continuation line under-indented for visual indent
1893:13: E128 continuation line under-indented for visual indent
1894:13: E128 continuation line under-indented for visual indent
1895:13: E128 continuation line under-indented for visual indent
1900: D400 First line should end with '.', not 't'
1900: D205 Blank line missing between one-line summary and description
1950:73: E261 at least two spaces before inline comment
1950:73: E262 inline comment should start with '# '
1952:81: E261 at least two spaces before inline comment
1952:81: E262 inline comment should start with '# '
1953:81: E261 at least two spaces before inline comment
1953:81: E262 inline comment should start with '# '
1954:81: E261 at least two spaces before inline comment
1954:81: E262 inline comment should start with '# '
1955:81: E261 at least two spaces before inline comment
1955:81: E262 inline comment should start with '# '
1956:81: E261 at least two spaces before inline comment
1956:81: E262 inline comment should start with '# '
1958:81: E261 at least two spaces before inline comment
1958:81: E262 inline comment should start with '# '
1959:81: E261 at least two spaces before inline comment
1959:81: E262 inline comment should start with '# '
1960:81: E261 at least two spaces before inline comment
1960:81: E262 inline comment should start with '# '
1961:82: E261 at least two spaces before inline comment
1961:82: E262 inline comment should start with '# '
1963:76: E261 at least two spaces before inline comment
1963:76: E262 inline comment should start with '# '
1965:84: E261 at least two spaces before inline comment
1965:84: E262 inline comment should start with '# '
1966:84: E261 at least two spaces before inline comment
1966:84: E262 inline comment should start with '# '
1967:84: E261 at least two spaces before inline comment
1967:84: E262 inline comment should start with '# '
1968:84: E261 at least two spaces before inline comment
1968:84: E262 inline comment should start with '# '
1969:84: E261 at least two spaces before inline comment
1969:84: E262 inline comment should start with '# '
1971:84: E262 inline comment should start with '# '
1972:84: E262 inline comment should start with '# '
1973:84: E262 inline comment should start with '# '
1974:84: E262 inline comment should start with '# '
1975:84: E262 inline comment should start with '# '
1977:83: E261 at least two spaces before inline comment
1980:65: E261 at least two spaces before inline comment
1980:66: E262 inline comment should start with '# '
1981:65: E261 at least two spaces before inline comment
1981:66: E262 inline comment should start with '# '
1982:66: E261 at least two spaces before inline comment
1982:66: E262 inline comment should start with '# '
1989:75: E261 at least two spaces before inline comment
1990:75: E261 at least two spaces before inline comment
1991:75: E261 at least two spaces before inline comment
1992:70: E261 at least two spaces before inline comment
2007:15: E128 continuation line under-indented for visual indent
2008:15: E128 continuation line under-indented for visual indent
2009:15: E128 continuation line under-indented for visual indent
2010:23: E211 whitespace before '('
2023:13: E122 continuation line missing indentation or outdented
2024:13: E122 continuation line missing indentation or outdented
2025:13: E122 continuation line missing indentation or outdented
2029:13: E122 continuation line missing indentation or outdented
2030:13: E122 continuation line missing indentation or outdented
2031:13: E122 continuation line missing indentation or outdented
2045:74: E222 multiple spaces after operator
2047:75: E222 multiple spaces after operator
2051:36: E225 missing whitespace around operator
2051:58: E225 missing whitespace around operator
2053:36: E225 missing whitespace around operator
2053:59: E225 missing whitespace around operator
2080: D400 First line should end with '.', not ','
2080: D205 Blank line missing between one-line summary and description
2092:37: E225 missing whitespace around operator
2092:86: E225 missing whitespace around operator
2104: D400 First line should end with '.', not ','
2104: D205 Blank line missing between one-line summary and description
2116:37: E225 missing whitespace around operator
2116:86: E225 missing whitespace around operator
2130:5: E303 too many blank lines (3)
2130: D400 First line should end with '.', not ','
2130: D205 Blank line missing between one-line summary and description
2142:37: E225 missing whitespace around operator
2142:86: E225 missing whitespace around operator
2154: D202 No blank lines allowed *after* method docstring, found 1
2154: D400 First line should end with '.', not ')'
2164:21: E126 continuation line over-indented for hanging indent
2167:26: E225 missing whitespace around operator
2203:9: E122 continuation line missing indentation or outdented
2204:9: E122 continuation line missing indentation or outdented
2205:9: E122 continuation line missing indentation or outdented
2206:9: E122 continuation line missing indentation or outdented
2207:9: E122 continuation line missing indentation or outdented
2208:9: E122 continuation line missing indentation or outdented
2209:9: E122 continuation line missing indentation or outdented
2210:9: E124 closing bracket does not match visual indentation
2213: D401 First line should be imperative: 'Print', not 'Prints'
2213: D400 First line should end with '.', not 'w'
2213: D205 Blank line missing between one-line summary and description
2235:15: E127 continuation line over-indented for visual indent
2235:109: E502 the backslash is redundant between brackets
2237:16: E127 continuation line over-indented for visual indent
2239:48: E225 missing whitespace around operator
2239:67: E225 missing whitespace around operator
2243: D401 First line should be imperative: 'Print', not 'Prints'
2243: D400 First line should end with '.', not 'w'
2243: D205 Blank line missing between one-line summary and description
2265:72: E221 multiple spaces before operator
2266:16: E127 continuation line over-indented for visual indent
2266:82: E502 the backslash is redundant between brackets
2266:44: E225 missing whitespace around operator
2266:63: E225 missing whitespace around operator
2270:81: E221 multiple spaces before operator
2271:20: E126 continuation line over-indented for hanging indent
2271:86: E502 the backslash is redundant between brackets
2271:48: E225 missing whitespace around operator
2271:67: E225 missing whitespace around operator
2275:79: E221 multiple spaces before operator
2276:20: E126 continuation line over-indented for hanging indent
2276:86: E502 the backslash is redundant between brackets
2276:48: E225 missing whitespace around operator
2276:67: E225 missing whitespace around operator
2280:16: E127 continuation line over-indented for visual indent
2284: D401 First line should be imperative: 'Print', not 'Prints'
2284: D400 First line should end with '.', not 'e'
2284: D205 Blank line missing between one-line summary and description
2311:15: E271 multiple spaces after keyword
2313: D202 No blank lines allowed *after* method docstring, found 1
2313: D400 First line should end with '.', not 'e'
2313: D205 Blank line missing between one-line summary and description
2351: D400 First line should end with '.', not 'r'
2396:55: E231 missing whitespace after ','
2404:22: E222 multiple spaces after operator
2439:9: E303 too many blank lines (3)
2502:34: E126 continuation line over-indented for hanging indent
2505:102: E502 the backslash is redundant between brackets
2505:77: E225 missing whitespace around operator
2505:96: E225 missing whitespace around operator
2510:98: E502 the backslash is redundant between brackets
2510:73: E225 missing whitespace around operator
2510:92: E225 missing whitespace around operator
2534:25: E127 continuation line over-indented for visual indent
2534:37: E203 whitespace before ':'
2535:37: E203 whitespace before ':'
2536:37: E203 whitespace before ':'
2537:37: E203 whitespace before ':'
2538:37: E203 whitespace before ':'
2539:37: E203 whitespace before ':'
2544:24: E261 at least two spaces before inline comment
2549:16: E127 continuation line over-indented for visual indent
2576:52: E126 continuation line over-indented for hanging indent


1: D290 White spaces around docstring should be trimmed.
2: I102 copyright year is outdated, expected 2015 but got 2014
27:6: E126 continuation line over-indented for hanging indent
32:1: E302 expected 2 blank lines, found 1
32: D203 Expected 1 blank line *before* class docstring, found 0
32: D204 Expected 1 blank line *after* class docstring, found 0
32: D400 First line should end with '.', not 'm'
103:36: E203 whitespace before ':'
110:5: E122 continuation line missing indentation or outdented
111:5: E122 continuation line missing indentation or outdented
119:5: E122 continuation line missing indentation or outdented
120:5: E122 continuation line missing indentation or outdented
121:5: E122 continuation line missing indentation or outdented
128:5: E122 continuation line missing indentation or outdented
129:5: E122 continuation line missing indentation or outdented
130:5: E122 continuation line missing indentation or outdented
280:23: E203 whitespace before ':'
281:26: E203 whitespace before ':'
282:28: E203 whitespace before ':'
283:27: E203 whitespace before ':'
284:24: E203 whitespace before ':'
289:23: E203 whitespace before ':'
290:26: E203 whitespace before ':'
291:28: E203 whitespace before ':'
292:27: E203 whitespace before ':'
293:24: E203 whitespace before ':'
301:23: E203 whitespace before ':'
302:26: E203 whitespace before ':'
303:28: E203 whitespace before ':'
304:27: E203 whitespace before ':'
305:24: E203 whitespace before ':'
350:28: E222 multiple spaces after operator
359:22: E203 whitespace before ':'
371:48: E203 whitespace before ','
371:49: E231 missing whitespace after ','
379:16: E231 missing whitespace after ':'
392:16: E231 missing whitespace after ':'
531:16: E126 continuation line over-indented for hanging indent
537:58: E203 whitespace before ','
597:15: E126 continuation line over-indented for hanging indent
622:14: E126 continuation line over-indented for hanging indent
647:13: E126 continuation line over-indented for hanging indent
653:17: E203 whitespace before ':'
654:22: E203 whitespace before ':'
655:20: E203 whitespace before ':'
656:18: E203 whitespace before ':'
657:24: E203 whitespace before ':'
658:22: E203 whitespace before ':'
659:19: E203 whitespace before ':'
660:20: E203 whitespace before ':'
661:23: E203 whitespace before ':'
662:18: E203 whitespace before ':'
663:17: E203 whitespace before ':'
664:19: E203 whitespace before ':'
665:20: E203 whitespace before ':'
666:21: E203 whitespace before ':'
667:19: E203 whitespace before ':'
668:19: E203 whitespace before ':'
669:20: E203 whitespace before ':'
670:17: E203 whitespace before ':'
671:24: E203 whitespace before ':'
672:23: E203 whitespace before ':'
673:21: E203 whitespace before ':'
674:37: E203 whitespace before ':'
678:33: E126 continuation line over-indented for hanging indent
688:32: E131 continuation line unaligned for hanging indent
689:9: E126 continuation line over-indented for hanging indent
692:33: E126 continuation line over-indented for hanging indent
702:32: E131 continuation line unaligned for hanging indent
703:32: E131 continuation line unaligned for hanging indent
704:32: E131 continuation line unaligned for hanging indent
705:32: E131 continuation line unaligned for hanging indent
706:32: E131 continuation line unaligned for hanging indent
707:32: E131 continuation line unaligned for hanging indent
708:32: E131 continuation line unaligned for hanging indent
709:32: E131 continuation line unaligned for hanging indent
710:32: E131 continuation line unaligned for hanging indent
711:32: E131 continuation line unaligned for hanging indent
712:32: E131 continuation line unaligned for hanging indent
713:32: E131 continuation line unaligned for hanging indent
714:32: E131 continuation line unaligned for hanging indent
715:32: E131 continuation line unaligned for hanging indent
716:9: E126 continuation line over-indented for hanging indent
721:23: E126 continuation line over-indented for hanging indent
721:27: E231 missing whitespace after ':'
722:32: E231 missing whitespace after ':'
723:32: E231 missing whitespace after ':'
724:32: E231 missing whitespace after ':'


4: I102 copyright year is outdated, expected 2015 but got 2014
81:1: E302 expected 2 blank lines, found 1
81: D203 Expected 1 blank line *before* class docstring, found 0
81: D204 Expected 1 blank line *after* class docstring, found 2
81: D400 First line should end with '.', not 'd'
81: D205 Blank line missing between one-line summary and description
88:5: E303 too many blank lines (2)
88: D400 First line should end with '.', not 'e'
94:5: E303 too many blank lines (2)
94: D400 First line should end with '.', not 'r'
94: D205 Blank line missing between one-line summary and description
99:34: W601 .has_key() is deprecated, use 'in'
101: D205 Blank line missing between one-line summary and description
118:34: W601 .has_key() is deprecated, use 'in'
127:17: E113 unexpected indentation
131:5: E303 too many blank lines (2)
131: D205 Blank line missing between one-line summary and description
139: D400 First line should end with '.', not 'e'
139: D205 Blank line missing between one-line summary and description
172:18: E261 at least two spaces before inline comment
172:19: E262 inline comment should start with '# '
176:34: W601 .has_key() is deprecated, use 'in'
184:95: E502 the backslash is redundant between brackets
185:33: E128 continuation line under-indented for visual indent
190:5: E303 too many blank lines (2)
190: D401 First line should be imperative: 'Thi', not 'This'
190: D400 First line should end with '.', not 'e'
190: D205 Blank line missing between one-line summary and description
197:34: W601 .has_key() is deprecated, use 'in'
200:34: W601 .has_key() is deprecated, use 'in'
201:15: E127 continuation line over-indented for visual indent
207:5: E303 too many blank lines (2)
207: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 's'
2: I102 copyright year is outdated, expected 2015 but got 2011
35:6: E126 continuation line over-indented for hanging indent
71:25: E203 whitespace before ':'
72:25: E203 whitespace before ':'
73:25: E203 whitespace before ':'
78:25: E203 whitespace before ':'
82:25: E203 whitespace before ':'
96:1: E302 expected 2 blank lines, found 1
96: D400 First line should end with '.', not 'r'
96: D200 One-line docstring should not occupy 3 lines
124:1: E302 expected 2 blank lines, found 1
124: D202 No blank lines allowed *after* function docstring, found 1
124: D400 First line should end with '.', not 'r'
124: D200 One-line docstring should not occupy 3 lines
144:1: E302 expected 2 blank lines, found 1
144: D200 One-line docstring should not occupy 3 lines
154:1: E302 expected 2 blank lines, found 1
154: D401 First line should be imperative: 'Get', not 'Gets'
154: D202 No blank lines allowed *after* function docstring, found 1
154: D200 One-line docstring should not occupy 3 lines
162:9: E221 multiple spaces before operator
167:1: E302 expected 2 blank lines, found 1
167: D401 First line should be imperative: 'Return', not 'Returns'
167: D205 Blank line missing between one-line summary and description
177:1: E302 expected 2 blank lines, found 1
177: D400 First line should end with '.', not 'e'
177: D205 Blank line missing between one-line summary and description
187:1: E302 expected 2 blank lines, found 1
187: D400 First line should end with '.', not 'e'
187: D205 Blank line missing between one-line summary and description
197:1: E302 expected 2 blank lines, found 1
197: D209 Put multi-line docstring closing quotes on separate line
197: D202 No blank lines allowed *after* function docstring, found 1
197: D400 First line should end with '.', not 'r'
197: D205 Blank line missing between one-line summary and description
206:1: E302 expected 2 blank lines, found 1
206: D400 First line should end with '.', not 'e'
206: D205 Blank line missing between one-line summary and description
222:1: E302 expected 2 blank lines, found 1
222: D400 First line should end with '.', not 't'
222: D205 Blank line missing between one-line summary and description
254:85: E261 at least two spaces before inline comment
254:86: E262 inline comment should start with '# '
259:1: E302 expected 2 blank lines, found 1
259: D200 One-line docstring should not occupy 3 lines
272:9: E113 unexpected indentation
273:13: E113 unexpected indentation
274:17: E113 unexpected indentation
275:13: E113 unexpected indentation
276:17: E113 unexpected indentation
277:13: E113 unexpected indentation
278:17: E113 unexpected indentation
279:13: E113 unexpected indentation
280:17: E113 unexpected indentation
281:13: E113 unexpected indentation
282:17: E113 unexpected indentation
284:9: E113 unexpected indentation
285:13: E113 unexpected indentation
286:17: E113 unexpected indentation
287:13: E113 unexpected indentation
288:17: E113 unexpected indentation
289:13: E113 unexpected indentation
290:17: E113 unexpected indentation
292:1: E302 expected 2 blank lines, found 1
292: D401 First line should be imperative: 'Print', not 'Prints'
292: D202 No blank lines allowed *after* function docstring, found 1
309:37: E713 test for membership should be 'not in'
372:1: E302 expected 2 blank lines, found 1
372: D401 First line should be imperative: 'Generate', not 'Generates'
372: D202 No blank lines allowed *after* function docstring, found 1
391:1: E302 expected 2 blank lines, found 1
391: D401 First line should be imperative: 'Generate', not 'Generates'
391: D202 No blank lines allowed *after* function docstring, found 1
416:30: E261 at least two spaces before inline comment
449:1: E302 expected 2 blank lines, found 1
449: D401 First line should be imperative: 'List', not 'Lists'
449: D202 No blank lines allowed *after* function docstring, found 1
449: D200 One-line docstring should not occupy 3 lines
470: D401 First line should be imperative: 'Return', not 'Returns'
470: D202 No blank lines allowed *after* function docstring, found 1
486:12: E127 continuation line over-indented for visual indent
495:1: E303 too many blank lines (3)
495: D401 First line should be imperative: 'Generate', not 'Generates'
495: D202 No blank lines allowed *after* function docstring, found 1
495: D208 Docstring is over-indented
519:17: E128 continuation line under-indented for visual indent
520:17: E128 continuation line under-indented for visual indent
521:17: E128 continuation line under-indented for visual indent
522:17: E128 continuation line under-indented for visual indent
523:17: E128 continuation line under-indented for visual indent
539:1: E302 expected 2 blank lines, found 1
539: D200 One-line docstring should not occupy 3 lines
545:1: E302 expected 2 blank lines, found 1
545: D200 One-line docstring should not occupy 3 lines
553:1: E302 expected 2 blank lines, found 1
553: D401 First line should be imperative: 'Generate', not 'Generates'
558:1: E302 expected 2 blank lines, found 1
558: D401 First line should be imperative: 'Generate', not 'Generates'
562:1: E302 expected 2 blank lines, found 1
562: D401 First line should be imperative: 'Return', not 'Returns'
562: D209 Put multi-line docstring closing quotes on separate line
562: D400 First line should end with '.', not 'd'
562: D205 Blank line missing between one-line summary and description
578: D401 First line should be imperative: 'Return', not 'Returns'
578: D400 First line should end with '.', not 'C'
578: D200 One-line docstring should not occupy 3 lines
592: D290 White spaces around docstring should be trimmed.
606:29: E261 at least two spaces before inline comment
606:30: E262 inline comment should start with '# '
613:31: E261 at least two spaces before inline comment
613:32: E262 inline comment should start with '# '
623:1: E302 expected 2 blank lines, found 1
623: D401 First line should be imperative: 'Return', not 'Returns'
623: D200 One-line docstring should not occupy 3 lines
644:1: E302 expected 2 blank lines, found 1
644: D401 First line should be imperative: 'Generate', not 'Generates'
650:1: E302 expected 2 blank lines, found 1
650: D400 First line should end with '.', not 'e'
650: D205 Blank line missing between one-line summary and description
663:1: E302 expected 2 blank lines, found 1
663: D200 One-line docstring should not occupy 3 lines
669:1: E302 expected 2 blank lines, found 1
669: D401 First line should be imperative: 'Restore', not 'Restores'
669: D200 One-line docstring should not occupy 3 lines
678:1: E302 expected 2 blank lines, found 1
678: D200 One-line docstring should not occupy 3 lines
688:29: F841 local variable 'e' is assigned to but never used
692:1: E302 expected 2 blank lines, found 1
692: D200 One-line docstring should not occupy 3 lines
726:1: E302 expected 2 blank lines, found 1
726: D400 First line should end with '.', not 's'
726: D205 Blank line missing between one-line summary and description
738:39: E261 at least two spaces before inline comment
738:40: E262 inline comment should start with '# '
750:12: E713 test for membership should be 'not in'
751:16: E126 continuation line over-indented for hanging indent
754:18: E261 at least two spaces before inline comment
758:12: E127 continuation line over-indented for visual indent
766:12: W601 .has_key() is deprecated, use 'in'
767:12: E127 continuation line over-indented for visual indent
774:12: W601 .has_key() is deprecated, use 'in'
775:12: E127 continuation line over-indented for visual indent
787:12: W601 .has_key() is deprecated, use 'in'
788:12: E127 continuation line over-indented for visual indent
789:12: E127 continuation line over-indented for visual indent
795:12: E127 continuation line over-indented for visual indent
796:36: E261 at least two spaces before inline comment
802:12: E127 continuation line over-indented for visual indent
802:20: W601 .has_key() is deprecated, use 'in'
806:12: E127 continuation line over-indented for visual indent
806:20: W601 .has_key() is deprecated, use 'in'
811:12: E127 continuation line over-indented for visual indent
811:21: W601 .has_key() is deprecated, use 'in'
815:12: W601 .has_key() is deprecated, use 'in'
816:12: E127 continuation line over-indented for visual indent
821:1: E302 expected 2 blank lines, found 1
821: D401 First line should be imperative: 'Run', not 'Runs'
821: D400 First line should end with '.', not 'k'
821: D200 One-line docstring should not occupy 3 lines
827:90: E203 whitespace before ':'
827:91: E231 missing whitespace after ':'


16: M102 unrecognized bullet/signature
17: M102 unrecognized bullet/signature
18: M102 unrecognized bullet/signature
19: M102 unrecognized bullet/signature
20: M102 unrecognized bullet/signature
21: M102 unrecognized bullet/signature
22: M102 unrecognized bullet/signature
23: M102 unrecognized bullet/signature
24: M102 unrecognized bullet/signature
25: M102 unrecognized bullet/signature
26: M102 unrecognized bullet/signature
27: M102 unrecognized bullet/signature
28: M102 unrecognized bullet/signature
29: M102 unrecognized bullet/signature
30: M102 unrecognized bullet/signature
31: M102 unrecognized bullet/signature
32: M102 unrecognized bullet/signature
1: M110 missing component name


27:6: E126 continuation line over-indented for hanging indent
30:37: E126 continuation line over-indented for hanging indent
34:9: E126 continuation line over-indented for hanging indent
45:31: E126 continuation line over-indented for hanging indent
53:1: E302 expected 2 blank lines, found 1
53: D200 One-line docstring should not occupy 2 lines
56:11: E221 multiple spaces before operator
77:1: E302 expected 2 blank lines, found 1
77: D290 White spaces around docstring should be trimmed.
77: D301 Use r""" if any backslashes in a docstring
82:75: E502 the backslash is redundant between brackets
83:12: E128 continuation line under-indented for visual indent
86:64: E502 the backslash is redundant between brackets
87:12: E128 continuation line under-indented for visual indent
87:80: E502 the backslash is redundant between brackets
88:12: E128 continuation line under-indented for visual indent
91:79: E502 the backslash is redundant between brackets
92:12: E128 continuation line under-indented for visual indent
99:17: E201 whitespace after '{'
99:64: E202 whitespace before '}'
101:1: E302 expected 2 blank lines, found 1
101: D200 One-line docstring should not occupy 2 lines
111:41: E201 whitespace after '('
111:57: E202 whitespace before ')'
115:25: E201 whitespace after '['
115:63: E202 whitespace before ']'
116:35: E201 whitespace after '['
116:93: E202 whitespace before ']'
119:45: E201 whitespace after '('
119:60: E202 whitespace before ')'
120:21: E201 whitespace after '['
120:70: E202 whitespace before ']'
123:17: E712 comparison to True should be 'if cond is True:' or 'if cond:'
132:1: E302 expected 2 blank lines, found 1
132: D400 First line should end with '.', not 'd'
132: D205 Blank line missing between one-line summary and description
142:1: E302 expected 2 blank lines, found 1
142: D205 Blank line missing between one-line summary and description
153:34: E261 at least two spaces before inline comment
153:35: E262 inline comment should start with '# '
160:42: E261 at least two spaces before inline comment
160:43: E262 inline comment should start with '# '
164:97: W601 .has_key() is deprecated, use 'in'
224:34: E261 at least two spaces before inline comment
224:35: E262 inline comment should start with '# '
251:1: E302 expected 2 blank lines, found 1
251: D205 Blank line missing between one-line summary and description
262:5: F841 local variable 'cache_dirty' is assigned to but never used
275:34: E261 at least two spaces before inline comment
275:35: E262 inline comment should start with '# '
296:31: E201 whitespace after '('
296:50: E202 whitespace before ')'
297:31: E201 whitespace after '('
297:50: E202 whitespace before ')'
298:20: E711 comparison to None should be 'if cond is None:'
304:14: E261 at least two spaces before inline comment
310:31: E201 whitespace after '('
310:50: E202 whitespace before ')'
311:20: E711 comparison to None should be 'if cond is None:'
319:31: E201 whitespace after '('
319:50: E202 whitespace before ')'
320:31: E201 whitespace after '('
320:50: E202 whitespace before ')'
321:20: E711 comparison to None should be 'if cond is None:'
336:1: E302 expected 2 blank lines, found 1
336: D205 Blank line missing between one-line summary and description
347:52: E261 at least two spaces before inline comment
347:53: E262 inline comment should start with '# '
348:5: F841 local variable 'cache_dirty' is assigned to but never used
356:34: E261 at least two spaces before inline comment
356:35: E262 inline comment should start with '# '
381:1: E302 expected 2 blank lines, found 1
381: D200 One-line docstring should not occupy 2 lines
396:9: E125 continuation line with same indent as next logical line
419:1: E302 expected 2 blank lines, found 1
419: D209 Put multi-line docstring closing quotes on separate line
419: D205 Blank line missing between one-line summary and description
419: D208 Docstring is over-indented
436:36: E201 whitespace after '('
436:62: E202 whitespace before ')'
440:40: E127 continuation line over-indented for visual indent
441:42: E261 at least two spaces before inline comment
441:43: E262 inline comment should start with '# '
443:14: E261 at least two spaces before inline comment
443:15: E262 inline comment should start with '# '
445:36: E201 whitespace after '('
445:51: E202 whitespace before ')'
466:1: E302 expected 2 blank lines, found 1
466: D401 First line should be imperative: 'Return', not 'Returns'
466: D209 Put multi-line docstring closing quotes on separate line
466: D400 First line should end with '.', not ')'
466: D205 Blank line missing between one-line summary and description
466: D208 Docstring is over-indented
474:18: E201 whitespace after '('
474:27: E202 whitespace before ')'
476:1: E302 expected 2 blank lines, found 1
476: D209 Put multi-line docstring closing quotes on separate line
476: D400 First line should end with '.', not 'o'
476: D205 Blank line missing between one-line summary and description
486:1: E302 expected 2 blank lines, found 1
486: D400 First line should end with '.', not '}'
486: D205 Blank line missing between one-line summary and description
499:59: E502 the backslash is redundant between brackets
502:1: E302 expected 2 blank lines, found 1
502: D400 First line should end with '.', not 'd'
502: D205 Blank line missing between one-line summary and description
530:74: E502 the backslash is redundant between brackets
531:32: E713 test for membership should be 'not in'
538:9: F841 local variable 'new_record2_managed_dois' is assigned to but never used
542:78: E502 the backslash is redundant between brackets
543:40: E713 test for membership should be 'not in'
543:37: E127 continuation line over-indented for visual indent
548:60: E502 the backslash is redundant between brackets
550:9: E125 continuation line with same indent as next logical line
553:16: E126 continuation line over-indented for hanging indent
575:27: E127 continuation line over-indented for visual indent


4: I102 copyright year is outdated, expected 2015 but got 2014
81:1: E302 expected 2 blank lines, found 1
81: D203 Expected 1 blank line *before* class docstring, found 0
81: D204 Expected 1 blank line *after* class docstring, found 2
81: D400 First line should end with '.', not 'd'
81: D205 Blank line missing between one-line summary and description
88:5: E303 too many blank lines (2)
88: D400 First line should end with '.', not 'e'
94:5: E303 too many blank lines (2)
94: D400 First line should end with '.', not 'r'
94: D205 Blank line missing between one-line summary and description
101: D205 Blank line missing between one-line summary and description
127:17: E113 unexpected indentation
131:5: E303 too many blank lines (2)
131: D205 Blank line missing between one-line summary and description
139: D400 First line should end with '.', not 'e'
139: D205 Blank line missing between one-line summary and description
172:18: E261 at least two spaces before inline comment
172:19: E262 inline comment should start with '# '
184:95: E502 the backslash is redundant between brackets
185:33: E128 continuation line under-indented for visual indent
190:5: E303 too many blank lines (2)
190: D401 First line should be imperative: 'Thi', not 'This'
190: D400 First line should end with '.', not 'e'
190: D205 Blank line missing between one-line summary and description
201:15: E127 continuation line over-indented for visual indent
207:5: E303 too many blank lines (2)
207: D205 Blank line missing between one-line summary and description