BTW, the step were you run the "old" version of the avocado-server tests should be removed:

```
diff --git a/examples/testplans/release.json b/examples/testplans/release.json
index 899f213..04be1c9 100644
--- a/examples/testplans/release.json
+++ b/examples/testplans/release.json
@@ -30,9 +30,6 @@
 	{"name": "Avocado Server Run",
 	 "description": "On the same machine used during 'Avocado Server Source Checkout and Unittests', run the quick and dirty script to get it running `$ ./reset-and-run.sh`. Set admin password to `123`. Expected result: `Starting development server at http://0.0.0.0:9405`"},

-	{"name": "Avocado Server Functional Test",
-	 "description": "On the same machine used during 'Avocado Server Run', on another console, run `$ avocado run selftests/all/functional/avocadoserver/api.py`. Expected result: `PASS`"},
-
 	{"name": "Avocado Virt and VT Source Checkout",
 	 "description": "On a virtualization capable machine, checkout a copy of the avocado-vt, avocado-virt, avocado-virt-tests repositories with `$ git clone git://github.com/avocado-framework/avocado-vt.git`, `$ git clone git://github.com/avocado-framework/avocado-virt.git` and `$ git clone git://github.com/avocado-framework/avocado-virt-tests.git`. On the Avocado (non-virt) repo, run `make link`. Now run `$ avocado plugins`. Expected result: `virt_bootstrap`, `virt`, `virt_test_compat_runner` and `virt_test_compat_lister` plugins enabled."},

```


Could you tell that here? https://github.com/libass/libass/issues/188

This branch with Dwrite by default will get merged soonish and Fontconfig will only be used if compiled and if dwrite isn't available on the system (XP, etc.) They could add some way of loading fonts in the directory of the .ass or the program or inside a "fonts" dir.

For now, I've un-disabled fontconfig if --enable-fontconfig is in ffmpeg_options.txt (which it is by default) but Dwrite will still be used. Embedded fonts in Matroska files should still work. If you really need only Fontconfig you can delete "fonts" from line 1349 and it will go back to master branch.


Yep, that's also true.


Check https://github.com/jb-alvarado/media-autobuild_suite/commit/83ef41df3a9be711af82dda4368a6288610cbd3b#commitcomment-12465082 though


한줄에 하나씩, 주석 달기.


@AlexFdv interesting. Haven't observed that yet. What display size did you connect with?


Lots of strange indendation changes here, that doesn't seem correct.


Is `Pillow` a direct dependency of any part of the `make check` utilities? If not, shouldn't it be pulled by the component that depends on it? From a quick look at this list, I'd guess `pygraphviz` depends on it.


Looks good, above you could pre-allocate the String[] array with childen().size() so there is no need for an ArrayList at all. Also conditions of the 2 if could be merged I think.


줄바꿈


Thanks, actually I included all the stuff in eclipse project
- this file javacpp/open_face.java  as well as the org.bytedeco.javacpp.presets.opencv_face.java
- with the remaining javacv1.0 jars: ffmpeg, javacv,javacpp opencv,
- classpath reference to org for classes (so it could find both classes in org.bytedeco.javacpp)
- with flag JVM -Djava.library.path="C:\Program Files\opencv\build\lib\Release" where I have built opencv_face300 (as per cmake/etc instructions at OpenCV)

however I still got an error when building the new OpenCVFaceRecognizer.java as a project:
 Exception in thread "main" java.lang.UnsatisfiedLinkError: no jniopencv_face in java.library.path


I'm sorry but I did not understand what you mean by "sys messages".


string-format here


string-format


some masterdata information in kio are wrong for this application


You should be aware that this will break big-endian, since the data will loaded in a different order in that case. If you don't support BE anyway, then this is fine of course.


@dpoe I know it's quite some time but do you by accident remember what the problem was that this commit fixed and maybe also who it can be reproduced?
I've picked this commit to master back then and it seems there is still a problem somehow.


Instead of going through the environment you could also `awk -v e="$(echo "$1" | array_element_encode)" ...`.


... or just remove the CPU_LE() around the rev32 instructions.


5058-fix-readvars-cli (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (0 of 0 tests passed)

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


added


@AlexFdv also did you find another way to reproduce this except with notepad? - I tried with different programs but without success.
It also seems that this always happens at the same spot regardless of the display size.


initial step


Awsome, nice job. Looks different in php I havent learned it yet. And sorry for the week you had to wait.... I been on GitHub just did not see your message.


Reverted. How did I miss it


Looks like this is not needed anymore? (moved to kie-bom)


5058-fix-readvars-cli (mbadams5) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


I'm wondering about this whole approach.  The software underlying pander and pandoc is quite limited in its table formatting and you are having to modify a lot of code from the rms package that will break if I modify rms.  If you are able to install the TeX4ht software package on your system you can use rms package latex methods to create advanced LaTeX code then convert it to self-contained html.  I am working with the creator of knitr to get this implemented with the Hmisc html method.  Then no new programming would be required to use html(latex(fit object)) in knitr with Rmarkdown in RStudio.


> if you have any ideas

So what about:
* add new function which will return list of libraries and other files: `glob_root_dir(${root_dir} library_files all_except_library_files)`
* loop through all roots. first root just copy all files, next roots `lipo` files from `library_files` list, others check the difference of `all_except_library_files`
* there is undocumented `DIFFERENT` command in CMake ([sources](https://github.com/Kitware/CMake/blob/1687060b587ded9e65153280c8ab364b05614b64/Source/cmFileCommand.cxx#L1115)) to check if files have the same content:
```cmake
file(DIFFERENT result FILES "${a}" "${b}")
if(result EQUAL 0)
  # same files
else()
  # files not the same => hunter_fatal_error
endif()
```


OK.


Embedded Fonts only work if the splitter do that. in case for ffmpeg it does not do that :/


Right sorry, I only wanted to simplify the first line but then the second half looked wrong; "[...]otherwise
it assumes ``x`` is a real number and returns[...]" would definitely be better.


I wouldn't imagine the order would make a difference here (thought that dependencies would be reliable), but since it's based on your experience, I believe it! :smile:


gitignore 부분과, CMake옵션부분 분리.


After this commit I've got a bus error (Mac OS X 10.10, go 1.4.2). Maybe we should check golang version for enabling/disabling those flags?


ログイン後のヘッダーのボタンを押した時のリンク先URLが誤っているので、修正しておきます


Thanks!


True


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


This is a "cure" for having the packages installed on a development machine, right? I can't find any reason to object it, so ACK.


To properly respect DRY principle a library for interactive repl-like interfaces is need. I failed to find an existing one (inquirer(https://www.npmjs.com/package/inquirer) is somewhat near, and it even quotes Citizen Kane, but it does not support the loop part).

I guess at the moment it is better to focus on web interface rather then implement repl library.


pessimi :-P


#include \<iterator\> worked


Nice catch!


Ok


GetDB, not GetRedis


Just a test


There are multiple flavours so we have to be sure they're identical, as the crc16 the client calculates, must match the one the server would calculate for a given key.


Still didn't answer my first question...

`CMD_DOWNLOADED_RAW_ADC_SAMPLES_125K` is handled in `UsbCommandReceived()`.

The nominal port baud rate doesn't have an impact. Even your transfer speed is higher than 115kbaud.

What I still don't understand: you get both the message which is printed after 2 seconds `Waiting for a response from the proxmark...
Don't forget to cancel its operation first by pressing on the button` AND the timeout message which is printed after 1.5 seconds. First, they appear in the wrong order and second, only one of them should appear.


OK!


OK.


5058-fix-readvars-cli (mbadams5) - x86_64-MacOS-10.9-clang: OK (1772 of 1772 tests passed)

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


This shows
how dangerous it is to use :
```Ceylon
value v = javaMethod();
```
if it's not fully proved that `javaMethod()` will *never* return `null`
in all the possible use-cases.

if `javaMethod()` might return `null` in any unknown or unmanaged case,
the line should be :
```Ceylon
ReturnType? v = javaMethod();
```


You're not *sending* the seed into the port; you're overwriting the port object.
```elm
    game.ports.initialSeed.send = Date.now();  // "send"
```

Maybe initialize it with that value instead:
```elm
var game = Elm.embed(Elm.App, gameContainer, {initialSeed: Date.now()});
```


wow can this solve [this](https://github.com/magnars/expand-region.el/issues/172) ?


fixed https://github.com/JetBrains/imperative-nodejs/commit/a4d91275f174a817db438925ee520fd8820446b6


done sometweking to your site by changing backround(renderd wierd on my phone)


Now that is a lot faster! :+1:


This list of files would eventually disappear, since we only use sexp for pretty-printing.


Thanks, I'm still trying to learn my way around all the Git stuff, it's all
new to me.  It's easy to use, but sometimes hard to figure out the
best/correct way to do things.

I'll take all your remarks into account on future updates.  I'll start a
new branch in the main repository and try to keep it to one commit per
feature.  (haha stupid Windows and it's Thumbs.db files :D  That's what I
get for moving to the Desktop version of Github).

Try to test linux/ipfs functionality on my branch, since I can't test that
myself (it should run the same as before when "use IPFS" is selected).

Phil

On Thu, Jul 30, 2015 at 11:03 PM, void4 <notifications@github.com> wrote:

> Nice stuff, thanks! [image: :+1:]
> Some remarks, because I can't include your changes directly:
>
>    - I gave you direct access to the repository, so you don't have to use
>    a fork (a branch would be better, due to our codebase differences).
>    - Please distribute your changes over several commits (e.g. one per
>    feature), as I try to test every change before I push it to master, it's
>    also more readable that way
>    - You accidentally added and committed a Thumbs.db file
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/MrM0bius/FireVR/commit/f2e1f4bd995e372da2e86295f4a3fd7750c8ffba#commitcomment-12459147>
> .
>


haha good catch


1: M111 unrecognized component name: dojson
1: M190 line is too long (64 > 50)


There is a way easier and cleaner way of doing this: https://github.com/Tommy-Geenexus/android_kernel_sony_msm8974_togari_5.0.2/commit/92b0cc31d8df484ff8444b589936eb27d62678f1
This retains ric on all partitions except /system.


I guess we are using fieldslib to generate getters and setters, so this would remain indefinitely.


Should this be `es-ES` to match the extends at  the bottom?


This would have to remain forever.


Should this be `es-ES` to match the extends at the bottom?


How about to make here:
if (self.defaults.init === true) {
                if (typeof self.init === 'function') {
                    self.init();
                }
}


Apparently someone is trying to build a PPX version of cstruct. But, this would have to remain for the foreseeable future.


А после того, как он достигнет FF, как будет меняться его значение?


broken alignment


Here too


Теперь надо сделать, чтобы это регистр работал по назначению.


Should be with the commit adding the pod file


This should state the language you are translating to (not English Translation)


broken alignment here too


@craig-riecke @jnfoster

This is the cleanest hack I can think of and it's not pretty. I suggest we avoid it for now.


We need to add a check for a recent version of Python, or raise a warning. See the discussion between Guido and Daniel


So I call this from a workflow now with 'sudo -u seqware ../path to vcf scripts and wrappers'  ?

I don't know the background on adding samtools/tabix, but if I'm reviewing this change I need to ask why we need them in container for managing GNOS interactions?  I'm sure you put them here for a reason...


:+1: Looks like I'm going back onto `develop` for a while


@shomahirata リーダー！
こちらを見てイシュー番号をコミットメッセージに必ず記載してください。
https://teachme.jp/contents/379800


you guys should remove the private[evaluation] as well, otherwise we can't use that :(


Названия коммитов должны отражать суть изменений.


This whole commit should be split into all other commits: introducing the script should introduce the corresponding bits to build and install it


Не хватает пробелов между параметрами.


Hi,

I came across this string while translating this file to french and found it difficult to understand.
I think it may be wise to make it simpler.

Unfortunately, I'm not sure to understand the role of this code, so I'm not able to give you a better explanation.


You need to have the makefile rules to build it in this commit


@samnazarko wrong indentation in 211-214 ?


Выравнивание пляшет.


This should work yes

Thanks


No worries.


We have a huge bonus for attacking non-pawn protected pieces/pawns with our King,
but nothing for "walking our pawns".

This should help the King to go in front of the pawns when it can help..
In the following position, b5 (with the plan Kb4 and Ka5) is found very easily
8/1k6/2p1n3/2Pp1p2/PP3P2/2KN4/8/8 w - - 0 61

The bonus are S(0,10) (one pawn) and S(0.25) bonus (if many
and is given for a King on rank 4 and above.


Fixed.


only catch the exact error you're trying to catch, this swallows every single possible exception and never handles them leading to impossible to debug situations.


Должны быть фигурные скобки у пары if-else.


try it.


The use case on my servers are for YouTubers who don't want people to know that they're being ignored. We'd need to introduce another toggle command for the notification, which is a UX decision that needs to be worked out.


This has been fixed already

Sam


fixed: c2af6f8d91ec8be80d7ba6795c9fb9ff3c1f1a3f


В одну строчку это писать не нужно.


teď ještě jak vynechat tu mezeru, a každé cassette dát zvlášť do pole

jestli chceš, tak to klidně udělej, mně se nad tím nechce přemýšlet


Always limit the commits by date.


Maybe we should also set the last error in error case.


Exit statuses are non-negative; `exit(-1)` is never right.  Ideally EXIT_FAILURE.


5058-fix-readvars-cli (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: Tests Failed

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


delete


Yeah, I was suggesting inline styles, I'd be surprised if the load time was in any way noticeable, so I'm not sure we get a ton out of being async here. But if you think it's important, I'm fine with the current approach. Just wanted to minimize any sources of bugs.


Excellent work.


Maybe? Can you describe the intended behavior more precisely, as well as
the impact on the existing (even if rather new) behavior?

2015-07-31 14:34 GMT+02:00 Andrea Richiardi <notifications@github.com>:

> wow can this solve this
> <https://github.com/magnars/expand-region.el/issues/172> ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/laurentpetit/ccw/commit/5b0af570e7f164af75c1368bcf4ac6a42524467a#commitcomment-12465462>
> .
>

--
Laurent Petit


It is almost something we should have a warning for.


@miltontony please comment on this, you had a better solution.


yeah I should have used a less generic name -- probably stepped on something.

I'll check it out in MSVC later and get that renamed to patch it up; no need for an issue.


Markdown can format code https://help.github.com/articles/markdown-basics/#code-formatting


Please follow the build instructions in the README.md file.


This 'tc' stuff always makes my head hurt :-)

OK, since each SHAPER_IF interface creates a new "root" tc entry, and shares the same mangle SHAPER_CHAIN, each SHAPER_IF interface should work independently.

The confusion may come with dial WAN external interfaces, shaping may not work as expected and I recall I added this single interface check because Philip P said we needed it.

So, you may be correct and the single interface restriction may be too restrictive.

BTW, are you sure your CFQ implementation is complete ?

Quite old, but still useful info...

Linux Advanced Routing & Traffic Control HOWTO
http://www.tldp.org/HOWTO/pdf/Adv-Routing-HOWTO.pdf

Chapter 9. Queueing Disciplines for Bandwidth Management


Is it legally?


test


Jason,
may I remove parameters $db and $table which are no longer used in the latest master?


Awesome! I'll get this merged to our fork ASAP. Thanks for being awesome.


I assume this is still needed because of PatchExecutable which needs other commands. You'd probably have to delete it


My mistake, the rest of the guide does not use '...' for continuing sentences, so it may be better to not use them.

Hopefully final suggestions:

- HABTM (has_and_belongs_to_many) => either (has and belongs to many) or (`has_and_belongs_to_many`)

- "creates the columns product_id and category_id with the :null option as true" => "which creates `product_id` and `category_id` columns with the :null option set to `true`", or juste add "which" to the beginning (only for this sentence, not the next one which continues after "For example:"

Hope this makes sense ;)


same as above?


That's exactly what we were discussing with @bjansen right now.


delete


I just tried to get it usable as part of mame and sent the relevant changes here. No further changes were needed there.


https://gist.github.com/Rushor/e6069c800b5b070b965c - See you on 6.x :)
![Bild](http://i.imgur.com/qnSyYtH.jpg)


Since we have tests that are separate for centos and ubuntu, and/or yum/apt-get, please rename any tests that you have reworked to work on both platforms/package managers accordingly. If it work on both give it a generic name, if it doesn't create 2 different tests.


Shouldn't this be xfail instead of skip for most of these?

For my understanding xfails says: "I know this currently fails and we need to fix it", while skip means "This test is not meant to work here"


remove this


Because Point with `int` coordinate_type is passed here. Those `double` values must be casted somehow. This is why on some compilers a warning was generated here. I picked `rounding_cast` for this. It rounds FP to INT if needed so does exactly what is desired here but of course we could use `static_cast` to suppress those warnings.


Using the function from utils that patches executables with scripts that throw errors please tests the logic from installing mongod on centos. Make sure all cases are covered


@NicholasBuse He is just trying to win the competition and earn that postcard ;-)


NO.

Inspections can be run in multiple threads, hence they should be stateless.


I should have changed my code style and formatting to match the rest of the project.

Thank you for fixing the errors.


I've ortek/hama remote and could test dev. build!


@davidfestal we specifically designed that use-case so that when *you* know it will never return `null` you say `Foo f = javaMethod()` of you are not sure or you know it can return `null` you use `Foo? f`.
It's very useful to avoid having to put `assert (exists f)` everywhere.
Byt like @gavinking suggests maybe we should at least generate a warning.


I think you want to do `s = s.to_s[0, chars].gsub(/ [^ ]*\z/, "")` to only match end of string - otherwise, if you have multiple newlines within the 500 count things get _really_ odd.

> UPDATE: Found a great Reddit thread explaining how to turn off a lot of **the After waiting** for Windows 10 to finishing installing you get presented with a (...)

> Sit back and grab a drink: it’s time for the story of one of **my favorite ‘Twas my** very first IT job, a software developer summer internship at a manufacturer of (...)

> This page introduces the daily usage of Hyper for Mac. If you meet any problem not described here, see **the trouble shooting Mac OS** X has been introduced **in Hyper To **install Hyper on Mac OS X, you need first to install VirtualBox 5.0, then download and **Install the Command Hyper** for Mac supports the following subcommands **in current attach** Attach to the tty of a specified container in a build Build an

Right now it's truncating the last word before every newline.


A warning emitted when the value returned by a Java-implemented method is assigned to a non-optional type.
And similarly when an optional value is passed as argument to a Java-implemented method.

This way cases when it happens can simply be annotated with the right `disableWarning` annotation and a comment explaining why this is possible.

wdyt ?


I think it's the 3rd time now that I see these arguments. Can you add them to a variable inside the suite itself or to a variable inside the file?


Or just a permission check? essentials.tptoggle.nomessage or something along those lines, doing a check if the messaged player has that permission. Adding another command would probably introduce some code duplication.


I'll fight him if he suggests that we support ice cream sandwich :wink:


check if it needs to be a break statement?


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


4: L102 copyright year is outdated, expected 2015 but got 2013
21:1: I100 Imports statements are in the wrong order. from invenio.ext.login should be before from invenio.ext.sqlalchemy
22:1: I101 Imported names are in the wrong order. Should be FlaskSQLAlchemyTest, InvenioFixture, make_flask_test_suite, run_test_suite
24:1: I100 Imports statements are in the wrong order. from fixture should be before from invenio.testsuite
25:1: I101 Imported names are in the wrong order. Should be UserData, UserUsergroupData, UsergroupData
25:1: I201 Missing newline before sections or imports.


4: L102 copyright year is outdated, expected 2015 but got 2013
22:1: I101 Imported names are in the wrong order. Should be FlaskSQLAlchemyTest, InvenioFixture, make_flask_test_suite, run_test_suite
25:1: I100 Imports statements are in the wrong order. from fixture should be before from invenio.testsuite
26:1: I201 Missing newline before sections or imports.
55:9: B901 blind except: statement
62:9: B901 blind except: statement
134:24: E225 missing whitespace around operator
134:33: E261 at least two spaces before inline comment
134:33: E262 inline comment should start with '# '
189:1: W391 blank line at end of file


4: L102 copyright year is outdated, expected 2015 but got 2013
21:1: I201 Missing newline before sections or imports.
22:1: I101 Imported names are in the wrong order. Should be FlaskSQLAlchemyTest, InvenioFixture, make_flask_test_suite, run_test_suite
24:1: I101 Imported names are in the wrong order. Should be CollectionCollectionData, CollectionData, ExternalcollectionData


4: L102 copyright year is outdated, expected 2015 but got 2013
23:1: I100 Imports statements are in the wrong order. import hmac should be before import re
25:1: I100 Imports statements are in the wrong order. import time should be before import urllib
28:1: I100 Imports statements are in the wrong order. from invenio.testsuite should be before from invenio.utils.hash


4: L102 copyright year is outdated, expected 2015 but got 2013
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be cgi, urlparse
28:16: E401 multiple imports on one line
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. import sys should be before import urlparse, cgi
29:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. import cStringIO should be before import sys
30:1: E402 module level import not at top of file
37:1: E402 module level import not at top of file
38:1: I101 Imported names are in the wrong order. Should be Browser, HTTPError, LinkNotFoundError
38:1: I201 Missing newline before sections or imports.
38:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from mechanize
40:1: E402 module level import not at top of file
41:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, get_authenticated_mechanize_browser, make_surl, make_test_suite, make_url, merge_error_messages, nottest, run_test_suite, test_web_page_content
42:1: E402 module level import not at top of file
43:31: E126 continuation line over-indented for hanging indent
48:1: E402 module level import not at top of file
55:10: E261 at least two spaces before inline comment
55:11: E262 inline comment should start with '# '
67:1: E302 expected 2 blank lines, found 1
89:1: E302 expected 2 blank lines, found 1
110:1: E302 expected 2 blank lines, found 1
144:44: E225 missing whitespace around operator
144:70: E225 missing whitespace around operator
208:1: E302 expected 2 blank lines, found 1
232:9: E266 too many leading '#' for block comment
249:5: E303 too many blank lines (2)
300:1: E302 expected 2 blank lines, found 1
352:105: E502 the backslash is redundant between brackets
361:26: E128 continuation line under-indented for visual indent
367:26: E128 continuation line under-indented for visual indent
377:5: E301 expected 1 blank line, found 0
468:21: B901 blind except: statement
473:17: E303 too many blank lines (2)
474:54: E713 test for membership should be 'not in'
526:44: E128 continuation line under-indented for visual indent
527:44: E128 continuation line under-indented for visual indent
530:1: E302 expected 2 blank lines, found 1
565:56: E251 unexpected spaces around keyword / parameter equals
565:58: E251 unexpected spaces around keyword / parameter equals
566:61: E251 unexpected spaces around keyword / parameter equals
566:63: E251 unexpected spaces around keyword / parameter equals
567:63: E251 unexpected spaces around keyword / parameter equals
567:65: E251 unexpected spaces around keyword / parameter equals
575:62: E251 unexpected spaces around keyword / parameter equals
576:64: E251 unexpected spaces around keyword / parameter equals
585:62: E251 unexpected spaces around keyword / parameter equals
586:63: E251 unexpected spaces around keyword / parameter equals
586:65: E251 unexpected spaces around keyword / parameter equals
595:62: E251 unexpected spaces around keyword / parameter equals
601:56: E251 unexpected spaces around keyword / parameter equals
601:58: E251 unexpected spaces around keyword / parameter equals
602:61: E251 unexpected spaces around keyword / parameter equals
602:63: E251 unexpected spaces around keyword / parameter equals
606:56: E251 unexpected spaces around keyword / parameter equals
606:58: E251 unexpected spaces around keyword / parameter equals
607:61: E251 unexpected spaces around keyword / parameter equals
607:63: E251 unexpected spaces around keyword / parameter equals
611:56: E251 unexpected spaces around keyword / parameter equals
611:58: E251 unexpected spaces around keyword / parameter equals
612:61: E251 unexpected spaces around keyword / parameter equals
612:63: E251 unexpected spaces around keyword / parameter equals
630:17: E203 whitespace before ':'
631:16: E203 whitespace before ':'
632:17: E203 whitespace before ':'
646:17: E203 whitespace before ':'
647:16: E203 whitespace before ':'
648:17: E203 whitespace before ':'
662:17: E203 whitespace before ':'
663:16: E203 whitespace before ':'
664:17: E203 whitespace before ':'
778:38: E203 whitespace before ':'
854:44: E128 continuation line under-indented for visual indent
855:44: E128 continuation line under-indented for visual indent
873:65: E128 continuation line under-indented for visual indent
873:70: E231 missing whitespace after ','
874:71: E126 continuation line over-indented for hanging indent
875:41: E131 continuation line unaligned for hanging indent
875:53: E231 missing whitespace after ':'
876:42: E122 continuation line missing indentation or outdented
876:56: E231 missing whitespace after ':'
885:22: E231 missing whitespace after ','
887:29: E231 missing whitespace after ':'
888:32: E231 missing whitespace after ':'
891:5: E303 too many blank lines (2)
915:13: E128 continuation line under-indented for visual indent
931:62: E261 at least two spaces before inline comment
965:1: E302 expected 2 blank lines, found 1
1005:5: E303 too many blank lines (2)
1161:1: E302 expected 2 blank lines, found 1
1247:17: E128 continuation line under-indented for visual indent
1373:8: E122 continuation line missing indentation or outdented
1374:8: E122 continuation line missing indentation or outdented
1375:8: E122 continuation line missing indentation or outdented
1397:81: E231 missing whitespace after ','
1406:81: E231 missing whitespace after ','
1934:5: E303 too many blank lines (2)
1936:9: E122 continuation line missing indentation or outdented
1940:1: E302 expected 2 blank lines, found 1
2163:8: E122 continuation line missing indentation or outdented
2164:8: E122 continuation line missing indentation or outdented
2165:8: E122 continuation line missing indentation or outdented
2650:21: E122 continuation line missing indentation or outdented
2651:21: E122 continuation line missing indentation or outdented
2652:21: E122 continuation line missing indentation or outdented
2771:1: E303 too many blank lines (3)
2835:8: E122 continuation line missing indentation or outdented
3083:21: E122 continuation line missing indentation or outdented
3276:13: E128 continuation line under-indented for visual indent
3367:5: E303 too many blank lines (2)
3406:5: E303 too many blank lines (2)
3541:84: E231 missing whitespace after ','
3669:1: E302 expected 2 blank lines, found 1
3711:49: E127 continuation line over-indented for visual indent
3732:51: E127 continuation line over-indented for visual indent
3736:1: E302 expected 2 blank lines, found 1
3745:1: E302 expected 2 blank lines, found 1
3785:1: E302 expected 2 blank lines, found 1
3833:1: E302 expected 2 blank lines, found 1
3860:1: E302 expected 2 blank lines, found 1
3888:5: E303 too many blank lines (2)
3936:5: E303 too many blank lines (2)
3959:1: E302 expected 2 blank lines, found 1
3995:1: E302 expected 2 blank lines, found 1
4022:1: E302 expected 2 blank lines, found 1
4049:1: E302 expected 2 blank lines, found 1
4067:1: E302 expected 2 blank lines, found 1
4121:1: E302 expected 2 blank lines, found 1
4141:1: E302 expected 2 blank lines, found 1
4150:63: E231 missing whitespace after ','
4157:63: E231 missing whitespace after ','
4221:1: E302 expected 2 blank lines, found 1
4241:70: E231 missing whitespace after ','
4262:1: E302 expected 2 blank lines, found 1
4301:1: E302 expected 2 blank lines, found 1
4445:14: E261 at least two spaces before inline comment
4445:15: E262 inline comment should start with '# '
4449:73: E225 missing whitespace around operator
4458:73: E225 missing whitespace around operator
4459:51: E128 continuation line under-indented for visual indent
4631:19: E128 continuation line under-indented for visual indent
4662:9: E303 too many blank lines (2)
4666:5: E303 too many blank lines (3)
4758:66: E251 unexpected spaces around keyword / parameter equals
4758:68: E251 unexpected spaces around keyword / parameter equals
4766:66: E251 unexpected spaces around keyword / parameter equals
4766:68: E251 unexpected spaces around keyword / parameter equals
4774:66: E251 unexpected spaces around keyword / parameter equals
4774:68: E251 unexpected spaces around keyword / parameter equals
4782:66: E251 unexpected spaces around keyword / parameter equals
4782:68: E251 unexpected spaces around keyword / parameter equals


This ID should be namespaced


I am sorry, did miss that line in my diff.

I fixed it with #228

I didn't recive any notification about these comments otherwise I had noticed it the night already.


> And similarly when an optional value is passed as argument to a Java-implemented method.

I don't see the use-case for this one? It would be the exact same situation as in Java.


OK, thanks. I think this test should maybe not be run with int then...


@quintesse : yes, I *like* that both be possible. but in this case it was written `value f=javaMethod()`. The fact that `value` was used made it difficult, even when reading the code, to detect that something should have be made explicit.
Maybe we should forbid the use of the `value` keyword with Java-implemented methods.


Here's what happened: once upon a time, we had an ooc package manager, and it was used for installing dependencies (kinda like sam — but different, it had a backend and everything).

Back then the `Requirements` directive was used only to specify dependencies for the package installer. Then somehow support was added into rock (should run git blame to find out where/when) but `UseDef parse` silently returns null when it can't find a file.

`nagaqueen` used to have `greg` in its requirements because, well, even though greg is not an ooc library, it's required to build a set of C sources from nagaqueen's grammar. I had it on my computer, of course, but didn't bother cloning it on Travis, because the .c files for the parser is committed into the git repo so greg isn't actually needed anywhere.

So that's the story of how Travis crashed. I'm sorry I was mean to you Travis! It wasn't your fault.


This revision is clean.


This diverges from rock's implementation — rock's implementation "applies" UseDef's properties to the whole BuildParams. So you can have module A imports module B imports module C, which uses some lib, then module A can import anything from module C - which is confusing, because module A could be totally unrelated!

cork is a bit stricter about it, you can only import a module from another project if you 1) explicitly have an `use` directive in the .ooc file 2) have it listed as `Requirements` in the project.


A test class should have the name of the class it tests + `Test`, so this should be `PatientOnCancelDeleterTest`.


ack


Yes, please have a look at the [fix implemented here - issue#10](https://github.com/praekelt/molo-ndoh-yep/pull/10/files)


O yes, I do use my own fork.

And for the output above I increased the timeout to 2500ms.  That could explain wrong order.


> I don't see the use-case for this one? It would be the exact same situation as in Java.

The thing is that all the parameters of Java methods as seen by the model loader as `optional`. So from the Ceylon code, we might think that we can safely pass a `null` value though a function parameter might not support a `null` argument.
It's also a source of error at runtime, of the same nature IMO.


Ale ale, jen premyslej
Nemam adresu toho produktu s vice cassettama


It'll have no effect for the command attribute.  `imports` is only used with the code attribute.


@jpfr Hey, what was the reason to change that (some subscrption problems or something?)? I have a user who suspects a performance degradation with the new dataStore infrastructure about 15-20%...


Let give the current implementation a shot. Inline styles just don't seem right, having a separate CSS file seems to be more manageable for further changes.


You can use a condition with xfail:

`@pytest.mark.xfail(is_py2, reason="Fails on python 2 due to embedded 'six' module")`


Cassette s velkym C, aby to naslo a prazdne polozky unset


Some sensei should be respected.


please revert this line to: else if (strncmp(buf+0x71, "Europe", 6) == 0)


First mobile app example: Hello World


Does "does not work with pywin32" mean that pkgutil does not work for the module "pywin32", or does it mean, it doe not work for any module as soon as pywin32 is used?


Hey Akash this is a good start toward correctness testing your code.

I would recommend testing the number of rows and the column names of the data frames that are returned by the time and memory testing functions.


Sorry, I did take the license key out of the source code. Will look to add that in later as a setting, but for now you'll need to add that into geoq/static/leaflet/Leaflet.MediaQ.js


Initialize global variable MININS_IPS in setClusterInfo function.
MINION_IPS is defined as a global variable, and is concatenated with other nodeIP.
When setClusterInfo is called for many times, this could cause potential problems.
Such as, you will have MINION_IPS=192.168.0.2,192.168.0.3,192.168.0.2,192.168.0.3 which is obviously wrong.


Yes, the `gendata` test used in `selftests` requires it (including support for zlib-devel, which needs to be installed before running `pip install`, otherwise you have to remove and reinstall it afterwards...)


system messages (`/var/log/messages` or alternative).


NSString *z = @"6";


Just reading a bit:
Is it even possible that this line ever not runs ?
Seems to be testing the same, in fact i tried removing the unless, no effect.


"deprecated":true,


@bmiklautz  I was testing on resolution 1200x800 or higher.
It also reproduces on Microsoft Word application.
Try to type the chars on small window, then maximize it and change font size to **smaller** (or change up and down).

Sometimes the bug is not stable, but try.
P.S. **Font smoothing should = fase.**


deprecated


This revision is clean.


if I created this constructor fileTracker file always will be in project directory, but I want save fileTracker file in another directory, for I was using constructor without parameters


componentSerializer is part of componentMonitor


chová se to úplně stejně


The new rule should enforce the same ordering as the settings for Eclipse and IntelliJ https://github.com/hawkular/hawkular-build-tools/blob/master/ide-configs/eclipse/hawkular-eclipse-preferences-java-codestyle-organizeimports.importorder

To validate this change, I built Hawkular and Inventory with this change and I can say that every import order problem reported by Checkstyle was reliably fixed by Eclipse's Source > Organize Import action.

@jpkrohling could you please ack this?


Yes we only support LE at the moment. I'll just drop the CPU_LE().


Indeed, this particular change probably is not necessary, AFAIU there can be a problem if there is no namespace specified at all. The rest of them, it depends, recently a user provided such workaround (https://github.com/boostorg/geometry/commit/8be10f33a39e79ff10a5ed1654edc22ca3e66a59) for `distance()` which was problematic for him. If this can happen for him then other algorithm can also fail to compile properly for other users. Furthermore we know how annoying MSVC2008 can be but this is a compiler supported by us. And I've done it for other algorithms too: https://github.com/boostorg/geometry/commit/1500dc364452c4219e00b6d241cfe71362b88b33

I believe there is no Boost policy for this. The library is allowed to not support some platforms/compilers, not provide workarounds for broken features, etc. it's author's decision. E.g. MultiPrecision doesn't support MSVC2008, I guess that it's because of exactly this namespaces problem.


@pfpmeijers this is the patch


5058-fix-readvars-cli (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Tests Failed

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


I did not know about that one. Is this only true for `.cc` files or should we always include local headers before system/external ones. I should probably document that somewhere then, related to #13.


AOSParadox qcom/common provide overlay. CM doesn't :p


Hello,

I've integrated a new realpath / readlink emulation from https://github.com/mkropat/sh-realpath (he just added a readlink emulation).
Could you please test this on Busybox ?


Now if someone wants to build this then they will get an error. No reason to delete this Pat.


??? what's wrong with go fmt ?


:DDD


Yes, that's the reason.  Bikeshed provides a bunch of easy, short attributes you can use in your source, which it translates into data-* attributes for you (sometimes in non-obvious ways).  You can always use the data-* attributes directly if you, for some reason, felt like it, tho.


not using go extension for whatever editor you're using ?


@agustinf acá menciono lo de activar Push en el Identifier, lo hago en este punto porque necesitas el CSR para poder dejarlo 100% activo y que no quede "pending"


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


bmake?


comments


It just means that pkgutil doesn't work on certain modules in pywin32: pythoncom, pywintypes, because they import a .dll file using `imp.load_dynamic` and replace all module attributes with those of the .dll, also changing the module's `__file__`.  The pywin32 hooks use get_pywin32_module_file_attribute to get the path to the .dll.

See also b8f86b6992b46c0cdfd9eab473dd4037aa53461f


In pull request #155 I "solved" the missing error message in another way:
Because the error message on unknown words was missing due to an "internal error" (the bug in tokenize.c regarding applying regex to LPUNC), I just ensured printing "Internal error" message in any case. This causes a duplicate message in such a case, which hopefully is rare.

However, your fix is maybe better: if we leave it in, we can simplify `sentence_split()` by removing the invocation of   `sentence_in_dictionary()` and just return -2 if `fw_failed` (and also remove `sentence_in_dictionary() ` altogether because it is not needed any more).


@vzvenyach You... you wrote *tests for bash*!!!  You're my hero, in so many ways.  :+1:  Mad props.


to jest komentarz o specjalnym przeznaczeniu tgz: conditional comments
https://msdn.microsoft.com/en-us/library/ms537512(v=vs.85).aspx


Because I can, that's why!


It seems that it works with Font smoothing = true as well. Sorry, I am not very familiar in glyphs implementation details. :)


yes, thats what pkgsrc for Linux calls the NetBSD make, as make is GNU make.


This patch, unfortunately, breaks other stuff.


Why not improve your style!


@mrsum looks like the duplication


Please change the task name to fit the names I wrote you: clean, load, reload, update.


Actually `pip` doesn't sort dependencies and it compiles all packages before installing them:

http://stackoverflow.com/questions/5394356/how-to-specify-install-order-for-python-pip


Why does dividing daterange.yl / 10 vs subtracting 0.1 fix this? What does these numbers represent?


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


this is wrong

```javascript
_vehicleType = if (count _this > 2) then {_this select 2} else {"LandVehicle"};
```


Certo


@Cybran111
![logo_main-trans](http://i.ytimg.com/vi/dCEgIG9_Bec/hqdefault.jpg)


The effect is only really present for ``.cc``, yes. The other matter of ordering in headers themselves is imo just a matter of consistent style. I think we're pretty good consistency wise with include ``stl -> non-dune -> dune -> stuff`` atm, but yeah, that should prolly go into #13 too.


nice feature indeed; @rodfersou take a look on it.


Yep, we already use this on some places... I guess we should create a function to make this the right way instead custom switch everywhere... :smile:


The error is in this last line. Should be:

    assert len(G.nodes()) == 3


:+1: (provided it compiles and passes unit tests now)


Most Sensei's should be respected.


trim($one_track === '')


In all descriptions please write '(...) Quickspin games (...)'
It will be descriptive, that this is about single provider.


simple JavaEE project


This excludes deleted editions.

It's rare but I'm pretty sure some of the detailed guides I looked at had only ever had one edition, and that edition had been published, then withdrawn, then deleted.


great change benny


It's appear to crash when there is no order_line when creating new SO. I gonna add a unit test and fix it.

```
  File "/srv/openerp/instances/openerp-oca-runbot/parts/odoo-extra/runbot/static/build/3111999-188-25e8fc/openerp/addons/sale_product_bundle/wizard/sale_order_bundle.py", line 26, in add_bundle
    max_sequence = max([line.sequence for line in so.order_line])
ValueError: max() arg is an empty sequence
```


Have you tested this?  Doesn't seem reliable at all without a minimum of 16 point font.  For instance, output on a simple malicious Word doc with macro-enabling text, very large (I assume) 18 point font headers:
![75e0544d1379b7205b3685a0c3fc5c7e9833c1658a9c8723d29802d00b311c58](https://cloud.githubusercontent.com/assets/8310366/9008339/a5a6dfe4-3767-11e5-8a0b-fa1755f642c3.jpg)

Tesseract outputs:

x E a v u \: payeneekyzmm [compammy Moot] r Mkmmﬂwnm :- [5' m

 1     W m an

‘A 1, (ambna ~15

J  a I u...” ,.  mm , IA a
r 7 x A mma a an :3 m , Change Edmng
' V E'A'Ar AA ‘ "N ‘ "N59 H dg) Vim” v

Pan:
(Hpbnam r.‘ Pant Sty‘u m \

libel

PROTECTED DOCUMENT

ms me Is pvotedea m Microsoftoffloe
please enzme Editingznd Conlenuo see thisdocument.

T VIEW THE DOCUMENT" F LO ’V THE STEPS BELO

apemheducumem m Mlcmsuft ofﬁce. premewmgunxme daesmwmuar pmlecled
ducumenls.

2. llyuu duwnluadedlhvsducumentfmmyouremall, please click "Enable Edmng’ frumme yenaw
barabuve.

” \ uu
Wm H by ‘

.Starl @meheeuzazsm 3 mm


Are these tests not ignored under some special circumstances? The message sound to me like they might be - do we have some details here?


This was not reverted accurately.  Notice that the original line was `set :bundle_path, -> { shared_path.join('bundle') }`


Is it possible to delete the sole draft edition of a document, so it would never have been published? I'm concerned about adding routes for documents that never existed.


what's the status and location for here?


talk with front end, they might want the modified user sent back to them.


OK, I will replace that

2015-07-31 13:41 GMT+08:00 Bo Li <notifications@github.com>:

> there is a matMulDeriv in calib3d. maybe you can replace?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jiuerbujie/omnidirectional_calibration/commit/f82220db96e0f42be0ebd2eba2f19d4a1b702bfa#commitcomment-12460081>
> .
>


C'est ça qui sert à détecter si un restaurant a été retiré de la DB master.


probably don't want people updating their auth tokens, especially since they should be in their own table


It is part of https://github.com/openspim/SPIMAcquisition/pull/24. I tried to contribute by mentioning how I would like to see that PR improved, but I have no strong opinion. @hkmoon if you like the code as-is, please feel free to merge.


The timeout of 2500ms explains it. Thanks.

I will push a fix when I am back home today. This won't make your USB port faster though. :grin:

And please forgive me for insisting on my first question. Meanwhile your fork is VERY different from master. Any plans for closing the gap?


See https://github.com/shinken-monitoring/mod-webui/issues/284


@frispete this was deliberate due to problems reported with 0.0.4 on PyPI, see issue #8. The (open) pull request #9 ought to fix this, but at the time I wasn't able to look at this, so pulling 0.0.4 from PyPI was the quickest solution.


Thanks!


same thing, I don't think you want status or location here.


Closes #284 with the previous commits.


Yep, that's how I've done it for other tasks.

Note, this sequence automatically does plan & execute, the prompt here is just a safety in case the execution status flag is buggy and does not safely indicate when execution is complete (and the robot has reached zero velocity).  We had to have this safety prompt on Atlas, too, for the valve task, for reasons that we never fully debugged.  It appeared our matlab plan status was sending mismatched utimes, but it could have been something different.


`Faker::Internet.password` is handy.


Less code to do the same thing. If you think it's not a good idea, I can just remove the reload JavaScript in favour of the jQuery function it used to run.


You're too quick, I did not removed it, only changed the step to use `curl`. I think it's useful to keep this step as it's closer to functional test than the django unittests...


I don't think this should be changed until Origin changes, otherwise it'll be wrong.  Current git head of origin still appears to use OPENSHIFT_NUM_MINIONS


Cool, cheers @LimeBlast


Then I merged because your proposal (in code) is fine too! :smile:


Redirect wrong?
https://gratipay.com/about/me/subscriptions/ now goes to
https://gratipay.com../giving/, which does not exist.


Absolutely. I can simulate dragging to a breakpoint.


Al compilar iconos, la tarea agrega el código unicode a cada archivo svg. Al tener una lista muy larga de iconos, uno puede accidentalmente  llamar dos iconos con el mismo nombre que a simple vista no se puede ver.
Ejm:
u2730-delete.svg
...
...
...
delete.svg

Con este cambio evito que la tarea agregue el código unicode y así evitar conflictos.


Please no. We don't do this anywhere else, and it doesn't help with readability.


Done.


If these aren't tied to the command line interface, I would make them constants inside of the printer. This would retain the same functionality, but it would also mean you aren't passing 6 arguments into the Printer. The difficulty then is that the user cannot change these, but until you create the interface for that functionality, I don't think it should be prioritized.


please, add to .gitignore or --assume-unchanged all IDE settings


more information: https://docs.djangoproject.com/en/1.8/intro/tutorial02/#customize-the-admin-look-and-feel


test


Thanks @NITEMAN for pointing out this flaw.


aaaaaaa


aaaaa


damn, forgot about this, sorry.


How about (something like...)

```
Edition.unscoped.where(type: "DetailedGuide").group(:document_id)
```


I'm guessing it was because of time constraints, but was there a marked decision to keep this one monolithic file? My first thought was that each class and the REPL could go into their own file for an easier read.


@ty-a LGTM, you can send the pull :smile:


this also would exclude the scenario of having only had one published edition which is now deleted.


The repo name is wallabag-**fxos** :grinning:


5058-fix-readvars-cli (mbadams5) - i386-Windows-7-VisualStudio-12: OK (1681 of 1778 tests passed)

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


This seems unrelated to the actual issue. Are you sure this does what you think it does? ;) IIRC The parent pdns process forks, so I don't think that works correctly with Type=simple.


Ah. To be clear. I still meant the separate file, but loaded programmatically into the HTML head.


Okay, I'll update the comment.


`selectedShortcut = LIBRARY.selectShortcut(custom = True, currentAction = listitem.getProperty("path"))`

should work, and be more readable ;)


oops, you committed a secret to a public repo


@nealkruis We had a CI issue where the Linux box ran out of space.  (@lefticus)  It was pumping along fine and usually cleans up after itself, but didn't this morning.  Probably went CI-partying last night.  Anyway, I deleted the 2 red entries above so you'll probably see some new results coming in later this morning.


I'm not sure how that helps. It looks like a document could go straight from `draft` to `deleted`, but would still have a `Document` associated. Is that possible?


The tabs are extra big in this file


Occurred  error here!


where do i sign up for creatures docking station


It really seems to address the issue. The changes LGTM too.


committed a secret!


víš nebo ne?


Just a hint here, shell_exec is considered a forbidden function because of security. This is also achievable with Zend_Pdf and would be best practise.


```ruby
Edition.unscoped.where(type: "DetailedGuide").where("first_published_at IS NOT NULL").group(:document_id)`
```
maybe?


Occurred Error this line


I don't think you want a redirect here, probably a `render json: @tweet`


  if (this.routeData.Values["controller"] != null)
+            {
+                this.dictionary.Add("controller", this.routeData.Values["controller"].ToString());
+                return this.dictionary.ContainsKey(prefix.ToUpper());
+            }


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (744 of 744 tests passed)

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


You want to show them the errors on the tweet model in this case.


Is stderr guaranteed to be flushed on abort?


co vim?


No space


@flaviocopes any reason to have the `$session_timeout` and `$session_path` outside the if?  Seems like it could be right inside that if statement?

I know this is pretty trivial, but these kinds of optimizations build up :)


Add `.idea` to your global `.gitignore` —
http://technicalpickles.com/posts/configure-git-to-globally-ignore-some-files/


jak to spravit.


AddCalcCoilSurfTempSource (kbenne) - x86_64-MacOS-10.9-clang: Tests Failed

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


Wow, thanks!


co spravit, prazdne radky uz tam nejsou


@ldoktor I can drop it, no problem


Good catch! :+1:


Looks great!

On 31 July 2015 at 14:51, Andrew Mundy <notifications@github.com> wrote:
> FIXUP Suggestions by @neworderofjamie
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/project-rig/nengo_spinnaker/commit/844aceb509d604d7a92e3d4ea79488f7b26e7ad8


I think `builtins.hasAttr "homepage" args.src.meta` would be clearer here.


ale takhle se to nemá vypisovat, proč je tam bez cassette, proc je tu jenom jedna a ne čtyři, a proč se do jednoho vypíše první cassette třikrát


This is clever code, but do you think you'll be able to explain this in two months?


Won't we have upgrade problems if we change service arguments and the .sysconfig file?  Doing this (without having some backwards compat) would mean that users that upgrade would have to convert some configuration.  Maybe that's not a problem?  But we do have existing users of openshift-sdn.


If we keep OPENSHIFT_NUM_MINIONS then we'll have to revert this hunk too of course.


@smn Thanks, Now the exception catch only the exact error.


This one actually seems a bit more active than `vanackere.ldap`, so I'm going to add it back. A recent change I made to Hologram seems to mind about the difference.


Better than `Date.now()` would be `Math.floor(Math.rand() * 10000000)`. That's not quite a mathematically uniform choice of seed (I'm not sure what the highest allowed value is) but it's good enough for a game.


@clebergnu Yep, order matters for pip


IIRC, this isn't necessary anymore because of improvements to the default Emacs profile.


@lmr I've been lucky then!


I haven't even booted up with those changes.
It needs more tuning.. :)


No reason, perfectly right. I'll post another PR


Done.


Would be nice to have more descriptive variable names here. You could write, for example,

```
for (funcm, func) in ((:expm, :exp), (:logm,:log), (:sqrtm,:sqrt))
...
function ($funcm)...

    ...  Symmetric(F.vectors * Diagonal(($func)(F.values)) * F.vectors')
```


For consistency, can we have the db files named after the db tables, api collections and go files, so:
 - db_certificates.go
 - db_containers.go
 - db_images.go
 - db_profiles.go

It's currently a bit inconsistent with some being plural (as I'd prefer) and some being singular (so not in line with the rest of our stuff).


5058-fix-readvars-cli (mbadams5) - Win64-Windows-7-VisualStudio-12: OK (1778 of 1778 tests passed)

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


Hey @vermiculus! Long time no chat. How is `sx.el` going? What else are you working on now? :)

As for the faster way of doing this, I am not familiar with Big-O notation and am happy to hear what you have to say, because I cannot find it. Help me out here please?


The text field and begin button should be higher on the page because it looks weird when you toggle the keyboard


Okay, then do you agree with the change in #466 which tells ReSpec to
prefer data-lt so that people can still validate their input form of ReSpec?

On Fri, Jul 31, 2015 at 8:27 AM, Tab Atkins Jr. <notifications@github.com>
wrote:

> Yes, that's the reason. Bikeshed provides a bunch of easy, short
> attributes you can use in your source, which it translates into data-*
> attributes for you (sometimes in non-obvious ways). You can always use the
> data-* attributes directly if you, for some reason, felt like it, tho.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/respec/commit/85e2f950d69028a7300033fa05aee3281a64c0db#commitcomment-12466231>
> .
>

--
Shane McCarron
halindrome@gmail.com


Hmm.. When I added better-npm-run it worked fine on windows just using the name, but on my macbook not so much.


Hi Patrik,

I have commited new versions of Rational.lidr, NonNegRational.lidr and
SimpleProb.lidr. They do not look terribly bad but I have pushed quite a
number of requitements into Rational. These will have to be implemented
at a certain point.

I am going to be away until Aug. 5 but I should be able to check my mail
account.

Ciao,
Nicola

Patrik Jansson <notifications@github.com> wrote:

> I get an error on this import - where can the NatPredicates module be found?
>
> —
> Reply to this email directly or view it on GitHub.*
>


I fixed this specific issue by creating a post_save signal handler on the User model.
This error will only be raised for users that were created before we had that signal handlers.
Adding this UserProfile for the user in question via `./manage.py shell` solves this and eliminates the need for this code.


1: M111 unrecognized component name: login


29:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
34:1: E402 module level import not at top of file
43:1: E402 module level import not at top of file
44:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
48:1: E402 module level import not at top of file
51:1: E402 module level import not at top of file
52:1: E402 module level import not at top of file
53:1: E402 module level import not at top of file
54:1: E402 module level import not at top of file
55:1: E402 module level import not at top of file
59:1: E402 module level import not at top of file
61:1: E402 module level import not at top of file
146: D210 No whitespaces allowed surrounding docstring text
398: D210 No whitespaces allowed surrounding docstring text


40:1: I100 Imports statements are in the wrong order. from zlib should be before from six.moves


1: D400 First line should end with a period (not 'e')
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be datetime_format, rlike, run_sql
25:1: I201 Missing newline before sections or imports.
25:1: E402 module level import not at top of file
26:1: I101 Imported names are in the wrong order. Should be CFG_WEBMESSAGE_DAYS_BEFORE_DELETE_ORPHANS, CFG_WEBMESSAGE_MAX_NB_OF_MESSAGES, CFG_WEBMESSAGE_ROLES_WITHOUT_QUOTA, CFG_WEBMESSAGE_STATUS_CODE
26:1: E402 module level import not at top of file
31:1: I101 Imported names are in the wrong order. Should be convert_datestruct_to_datetext, datetext_default
31:1: E402 module level import not at top of file
32:31: E126 continuation line over-indented for hanging indent
34:1: E402 module level import not at top of file
37: D401 First line should be in imperative mood ('Check', not 'Checks')
37: D400 First line should end with a period (not 'e')
37: D205 1 blank line required between summary line and description (found 0)
44:10: E221 multiple spaces before operator
52:1: E302 expected 2 blank lines, found 1
52: D400 First line should end with a period (not 's')
52: D205 1 blank line required between summary line and description (found 0)
77:21: E127 continuation line over-indented for visual indent
78:21: E127 continuation line over-indented for visual indent
79:20: E127 continuation line over-indented for visual indent
95:1: E302 expected 2 blank lines, found 1
95: D202 No blank lines allowed after function docstring (found 1)
95: D205 1 blank line required between summary line and description (found 0)
116:1: E302 expected 2 blank lines, found 1
116: D210 No whitespaces allowed surrounding docstring text
116: D400 First line should end with a period (not 'r')
116: D205 1 blank line required between summary line and description (found 0)
132:1: E302 expected 2 blank lines, found 1
132: D210 No whitespaces allowed surrounding docstring text
132: D400 First line should end with a period (not 'd')
132: D205 1 blank line required between summary line and description (found 0)
149: D400 First line should end with a period (not 'l')
149: D205 1 blank line required between summary line and description (found 0)
168:26: E502 the backslash is redundant between brackets
169:21: E127 continuation line over-indented for visual indent
169:61: E502 the backslash is redundant between brackets
182:1: E302 expected 2 blank lines, found 1
182: D400 First line should end with a period (not 'd')
182: D205 1 blank line required between summary line and description (found 0)
198:1: E302 expected 2 blank lines, found 1
198: D400 First line should end with a period (not 'x')
198: D205 1 blank line required between summary line and description (found 0)
215:1: E302 expected 2 blank lines, found 1
215: D401 First line should be in imperative mood ('Check', not 'Checks')
215: D400 First line should end with a period (not ',')
215: D205 1 blank line required between summary line and description (found 0)
246:1: E302 expected 2 blank lines, found 1
246: D400 First line should end with a period (not ')')
246: D205 1 blank line required between summary line and description (found 0)
267:1: E302 expected 2 blank lines, found 1
267: D400 First line should end with a period (not 's')
267: D205 1 blank line required between summary line and description (found 0)
279:18: E225 missing whitespace around operator
289:9: E301 expected 1 blank line, found 0
289: D210 No whitespaces allowed surrounding docstring text
289: D401 First line should be in imperative mood ('take', not 'takes')
289: D400 First line should end with a period (not 's')
295:1: E302 expected 2 blank lines, found 1
295: D400 First line should end with a period (not 's')
295: D205 1 blank line required between summary line and description (found 0)
319:1: E302 expected 2 blank lines, found 1
319: D400 First line should end with a period (not 's')
319: D205 1 blank line required between summary line and description (found 0)
331:19: E225 missing whitespace around operator
341:9: E301 expected 1 blank line, found 0
341: D210 No whitespaces allowed surrounding docstring text
341: D401 First line should be in imperative mood ('take', not 'takes')
341: D400 First line should end with a period (not 's')
348: D400 First line should end with a period (not 's')
348: D205 1 blank line required between summary line and description (found 0)
370:9: E301 expected 1 blank line, found 0
370: D210 No whitespaces allowed surrounding docstring text
370: D400 First line should end with a period (not 's')
376:1: E302 expected 2 blank lines, found 1
376: D205 1 blank line required between summary line and description (found 0)
398:1: E302 expected 2 blank lines, found 1
398: D210 No whitespaces allowed surrounding docstring text
398: D401 First line should be in imperative mood ('check', not 'checks')
398: D400 First line should end with a period (not '1')
406:1: E302 expected 2 blank lines, found 1
406: D401 First line should be in imperative mood ('Create', not 'Creates')
406: D205 1 blank line required between summary line and description (found 0)
442:1: E302 expected 2 blank lines, found 1
442: D400 First line should end with a period (not 's')
442: D205 1 blank line required between summary line and description (found 0)
459:9: E301 expected 1 blank line, found 0
459: D210 No whitespaces allowed surrounding docstring text
459: D401 First line should be in imperative mood ('not(i', not 'not(is')
459: D400 First line should end with a period (not ')')
474: D400 First line should end with a period (not 'e')
474: D205 1 blank line required between summary line and description (found 0)
492:1: E302 expected 2 blank lines, found 1
492: D401 First line should be in imperative mood ('Update', not 'Updates')
492: D400 First line should end with a period (not 'd')
492: D205 1 blank line required between summary line and description (found 0)
498:10: E222 multiple spaces after operator
512:12: E225 missing whitespace around operator
525:1: E302 expected 2 blank lines, found 1
525: D400 First line should end with a period (not 'n')
531:37: E222 multiple spaces after operator
537:1: E302 expected 2 blank lines, found 1
537: D400 First line should end with a period (not 'e')
537: D200 One-line docstring should fit on one line with quotes (found 2)
544:71: E222 multiple spaces after operator
562:1: E302 expected 2 blank lines, found 1
562: D400 First line should end with a period (not 't')
562: D205 1 blank line required between summary line and description (found 0)
569:1: E302 expected 2 blank lines, found 1
569: D210 No whitespaces allowed surrounding docstring text
569: D401 First line should be in imperative mood ('Clean', not 'Cleans')
569: D400 First line should end with a period (not 'e')
594:5: E301 expected 1 blank line, found 0
625:1: W391 blank line at end of file


37:1: I100 Imports statements are in the wrong order. from invenio_groups.models should be before from wtforms


1: D200 One-line docstring should fit on one line with quotes (found 3)
4: L102 copyright year is outdated, expected 2015 but got 2012
29:1: I100 Imports statements are in the wrong order. from string should be before from invenio.ext.sqlalchemy
30:1: I201 Missing newline before sections or imports.
31:1: I201 Missing newline before sections or imports.
33:1: I100 Imports statements are in the wrong order. from invenio_groups.models should be before from sqlalchemy.ext.associationproxy
36: D203 1 blank line required before class docstring (found 0)
36: D204 1 blank line required after class docstring (found 0)
38: D102 Missing docstring in public method
40:41: F821 undefined name '_'
41:37: F821 undefined name '_'
41:13: E128 continuation line under-indented for visual indent
42:13: E128 continuation line under-indented for visual indent
45:17: E128 continuation line under-indented for visual indent
46:17: E128 continuation line under-indented for visual indent
48:17: E128 continuation line under-indented for visual indent
49:17: E128 continuation line under-indented for visual indent
51:17: E128 continuation line under-indented for visual indent
53:17: E128 continuation line under-indented for visual indent
57:9: E128 continuation line under-indented for visual indent
57:46: E261 at least two spaces before inline comment
59:9: E128 continuation line under-indented for visual indent
66:13: E128 continuation line under-indented for visual indent
66:29: E231 missing whitespace after ':'
69: D210 No whitespaces allowed surrounding docstring text
69: D401 First line should be in imperative mood ('Alia', not 'Alias')
74: D210 No whitespaces allowed surrounding docstring text
74: D401 First line should be in imperative mood ('Alia', not 'Alias')
79: D102 Missing docstring in public method
81:13: E128 continuation line under-indented for visual indent
89: D102 Missing docstring in public method
91:13: E128 continuation line under-indented for visual indent
99:5: E303 too many blank lines (2)
100: D102 Missing docstring in public method
106:65: E502 the backslash is redundant between brackets
107:17: E128 continuation line under-indented for visual indent
108:17: E122 continuation line missing indentation or outdented
108:51: E502 the backslash is redundant between brackets
111:13: E731 do not assign a lambda expression, use a def
116:54: E502 the backslash is redundant between brackets
117:17: E128 continuation line under-indented for visual indent
117:5: E129 visually indented line with same indent as next logical line
122: D102 Missing docstring in public method
128:58: E502 the backslash is redundant between brackets
129:17: E128 continuation line under-indented for visual indent
130:17: E122 continuation line missing indentation or outdented
130:48: E502 the backslash is redundant between brackets
132:13: E731 do not assign a lambda expression, use a def
139:5: E129 visually indented line with same indent as next logical line
144: D102 Missing docstring in public method
148:13: E128 continuation line under-indented for visual indent
151: D102 Missing docstring in public method
155:13: E128 continuation line under-indented for visual indent
160:1: I100 Imports statements are in the wrong order. from invenio.modules.messages.config should be before from invenio_groups.models
160:1: F401 'CFG_WEBMESSAGE_EMAIL_ALERT' imported but unused
160:1: E402 module level import not at top of file
161:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.messages.config
161:1: F401 'CFG_WEBCOMMENT_ALERT_ENGINE_EMAIL' imported but unused
161:1: E402 module level import not at top of file
162:1: E402 module level import not at top of file
163:1: I100 Imports statements are in the wrong order. from datetime should be before from invenio.utils.date
163:1: I201 Missing newline before sections or imports.
163:1: E402 module level import not at top of file
165:1: E302 expected 2 blank lines, found 1
165: D210 No whitespaces allowed surrounding docstring text
165: D401 First line should be in imperative mood ('Send', not 'Sends')
170:18: E222 multiple spaces after operator
171:20: E127 continuation line over-indented for visual indent
175:9: E731 do not assign a lambda expression, use a def
176:21: E128 continuation line under-indented for visual indent
178:21: E126 continuation line over-indented for hanging indent
182:5: E125 continuation line with same indent as next logical line
187:28: E251 unexpected spaces around keyword / parameter equals
187:30: E251 unexpected spaces around keyword / parameter equals
188:28: E251 unexpected spaces around keyword / parameter equals
188:30: E251 unexpected spaces around keyword / parameter equals
189:29: E126 continuation line over-indented for hanging indent
191:13: B901 blind except: statement
207: D203 1 blank line required before class docstring (found 0)
207: D204 1 blank line required after class docstring (found 0)
211:17: E128 continuation line under-indented for visual indent
212:17: E128 continuation line under-indented for visual indent
214:17: E128 continuation line under-indented for visual indent
215:17: E128 continuation line under-indented for visual indent
216:17: E128 continuation line under-indented for visual indent
218:17: E128 continuation line under-indented for visual indent


32:1: I100 Imports statements are in the wrong order. from time should be before from invenio.utils.date
37: D205 1 blank line required between summary line and description (found 0)
47:1: E302 expected 2 blank lines, found 1
47: D205 1 blank line required between summary line and description (found 0)
55:12: E127 continuation line over-indented for visual indent
60: D205 1 blank line required between summary line and description (found 0)
69:42: E225 missing whitespace around operator
71:5: B901 blind except: statement
72:42: E225 missing whitespace around operator
73:45: E225 missing whitespace around operator
75:1: E302 expected 2 blank lines, found 1
75: D401 First line should be in imperative mood ('Check', not 'Checks')
75: D400 First line should end with a period (not 'e')
75: D205 1 blank line required between summary line and description (found 0)
83:12: E127 continuation line over-indented for visual indent
84:12: E127 continuation line over-indented for visual indent
86:1: E302 expected 2 blank lines, found 1
86: D205 1 blank line required between summary line and description (found 0)
93:42: E502 the backslash is redundant between brackets
93:11: E271 multiple spaces after keyword
94:13: E126 continuation line over-indented for hanging indent
95:13: E127 continuation line over-indented for visual indent
96:13: E127 continuation line over-indented for visual indent
98:1: E302 expected 2 blank lines, found 1
98: D205 1 blank line required between summary line and description (found 0)
113:12: E127 continuation line over-indented for visual indent
114:12: E127 continuation line over-indented for visual indent
116:1: E302 expected 2 blank lines, found 1
116: D210 No whitespaces allowed surrounding docstring text
116: D400 First line should end with a period (not 'r')
116: D205 1 blank line required between summary line and description (found 0)
124:12: E127 continuation line over-indented for visual indent
125:12: E127 continuation line over-indented for visual indent
126:12: E127 continuation line over-indented for visual indent
128:1: E302 expected 2 blank lines, found 1
128: D210 No whitespaces allowed surrounding docstring text
128: D400 First line should end with a period (not 'd')
128: D205 1 blank line required between summary line and description (found 0)
134:12: E127 continuation line over-indented for visual indent
135:12: E127 continuation line over-indented for visual indent
136:12: E127 continuation line over-indented for visual indent
138:1: E302 expected 2 blank lines, found 1
138: D400 First line should end with a period (not 'l')
138: D205 1 blank line required between summary line and description (found 0)
153:12: E127 continuation line over-indented for visual indent
154:12: E127 continuation line over-indented for visual indent
155:12: E127 continuation line over-indented for visual indent
157:1: E302 expected 2 blank lines, found 1
157: D400 First line should end with a period (not 'd')
157: D205 1 blank line required between summary line and description (found 0)
164:12: E127 continuation line over-indented for visual indent
165:12: E127 continuation line over-indented for visual indent
165:44: E225 missing whitespace around operator
166:12: E127 continuation line over-indented for visual indent
168:1: E302 expected 2 blank lines, found 1
168: D400 First line should end with a period (not 'x')
168: D205 1 blank line required between summary line and description (found 0)
178:20: E127 continuation line over-indented for visual indent
182:1: E302 expected 2 blank lines, found 1
182: D401 First line should be in imperative mood ('Check', not 'Checks')
182: D400 First line should end with a period (not ',')
182: D205 1 blank line required between summary line and description (found 0)
193:16: E127 continuation line over-indented for visual indent
194:16: E127 continuation line over-indented for visual indent
195:16: E127 continuation line over-indented for visual indent
195:63: E225 missing whitespace around operator
196:16: E127 continuation line over-indented for visual indent
198:65: E502 the backslash is redundant between brackets
199:12: E128 continuation line under-indented for visual indent
200:12: E127 continuation line over-indented for visual indent
202:1: E302 expected 2 blank lines, found 1
202: D400 First line should end with a period (not ')')
202: D205 1 blank line required between summary line and description (found 0)
210:15: E128 continuation line under-indented for visual indent
210:62: E502 the backslash is redundant between brackets
211:15: E128 continuation line under-indented for visual indent
211:55: E225 missing whitespace around operator
212:51: E225 missing whitespace around operator
214:19: E127 continuation line over-indented for visual indent
214:59: E225 missing whitespace around operator
215:55: E225 missing whitespace around operator
216:19: E127 continuation line over-indented for visual indent
221:1: E302 expected 2 blank lines, found 1
221: D400 First line should end with a period (not 's')
221: D205 1 blank line required between summary line and description (found 0)
233:18: E225 missing whitespace around operator
243:9: E301 expected 1 blank line, found 0
243: D210 No whitespaces allowed surrounding docstring text
243: D401 First line should be in imperative mood ('take', not 'takes')
243: D400 First line should end with a period (not 's')
249:1: E302 expected 2 blank lines, found 1
249: D400 First line should end with a period (not 's')
249: D205 1 blank line required between summary line and description (found 0)
273:1: E302 expected 2 blank lines, found 1
273: D400 First line should end with a period (not 's')
273: D205 1 blank line required between summary line and description (found 0)
285:19: E225 missing whitespace around operator
295:9: E301 expected 1 blank line, found 0
295: D210 No whitespaces allowed surrounding docstring text
295: D401 First line should be in imperative mood ('take', not 'takes')
295: D400 First line should end with a period (not 's')
302: D400 First line should end with a period (not 's')
302: D205 1 blank line required between summary line and description (found 0)
324:9: E301 expected 1 blank line, found 0
324: D210 No whitespaces allowed surrounding docstring text
324: D400 First line should end with a period (not 's')
330:1: E302 expected 2 blank lines, found 1
330: D205 1 blank line required between summary line and description (found 0)
352:1: E302 expected 2 blank lines, found 1
352: D210 No whitespaces allowed surrounding docstring text
352: D401 First line should be in imperative mood ('check', not 'checks')
352: D400 First line should end with a period (not '1')
360:1: E302 expected 2 blank lines, found 1
360: D401 First line should be in imperative mood ('Create', not 'Creates')
360: D205 1 blank line required between summary line and description (found 0)
396:1: E302 expected 2 blank lines, found 1
396: D400 First line should end with a period (not 's')
396: D205 1 blank line required between summary line and description (found 0)
413:9: E301 expected 1 blank line, found 0
413: D210 No whitespaces allowed surrounding docstring text
413: D401 First line should be in imperative mood ('not(i', not 'not(is')
413: D400 First line should end with a period (not ')')
428: D400 First line should end with a period (not 'e')
428: D205 1 blank line required between summary line and description (found 0)
447: D401 First line should be in imperative mood ('Update', not 'Updates')
447: D400 First line should end with a period (not 'd')
447: D205 1 blank line required between summary line and description (found 0)
453:5: F841 local variable 'now' is assigned to but never used
453:10: E222 multiple spaces after operator
459:9: E122 continuation line missing indentation or outdented
459:34: E225 missing whitespace around operator
460:9: E122 continuation line missing indentation or outdented
461:9: E122 continuation line missing indentation or outdented
461:33: E225 missing whitespace around operator
462:9: E122 continuation line missing indentation or outdented
467:38: E225 missing whitespace around operator
476: D400 First line should end with a period (not 'n')
487:1: E302 expected 2 blank lines, found 1
487: D400 First line should end with a period (not 'e')
487: D200 One-line docstring should fit on one line with quotes (found 2)
512:1: E302 expected 2 blank lines, found 1
512: D400 First line should end with a period (not 't')
512: D205 1 blank line required between summary line and description (found 0)
519:1: E302 expected 2 blank lines, found 1
519: D210 No whitespaces allowed surrounding docstring text
519: D401 First line should be in imperative mood ('Clean', not 'Cleans')
519: D400 First line should end with a period (not 'e')
544:5: E301 expected 1 blank line, found 0
575:1: W391 blank line at end of file


25:1: I201 Missing newline before sections or imports.
95:36: W503 line break before binary operator
131:9: B901 blind except: statement


1: D205 1 blank line required between summary line and description (found 0)
28:1: I201 Missing newline before sections or imports.
29:1: F401 'escape_shell_arg' imported but unused
30:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.system should be before from invenio.utils.shell
31:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.legacy.bibcatalog.system
35:1: I100 Imports statements are in the wrong order. import invenio.config should be before from invenio.ext.logging
35:1: E402 module level import not at top of file
43: D101 Missing docstring in public class
46: D202 No blank lines allowed after function docstring (found 1)
46: D400 First line should end with a period (not 's')
51:16: E221 multiple spaces before operator
54:90: E502 the backslash is redundant between brackets
54: D202 No blank lines allowed after function docstring (found 1)
60: D401 First line should be in imperative mood ('create', not 'creates')
60: D202 No blank lines allowed after function docstring (found 1)
60: D400 First line should end with a period (not 'e')
102: D210 No whitespaces allowed surrounding docstring text
102: D202 No blank lines allowed after function docstring (found 1)
102: D400 First line should end with a period (not 'd')
106:16: E221 multiple spaces before operator
113:5: E303 too many blank lines (2)
113: D210 No whitespaces allowed surrounding docstring text
113: D202 No blank lines allowed after function docstring (found 1)
113: D400 First line should end with a period (not 'r')
117:16: E221 multiple spaces before operator
123: D210 No whitespaces allowed surrounding docstring text
123: D202 No blank lines allowed after function docstring (found 1)
123: D400 First line should end with a period (not 'd')
127:16: E221 multiple spaces before operator
133: D202 No blank lines allowed after function docstring (found 1)
138:56: E251 unexpected spaces around keyword / parameter equals
138:58: E251 unexpected spaces around keyword / parameter equals
138: D202 No blank lines allowed after function docstring (found 1)
143:44: E251 unexpected spaces around keyword / parameter equals
143:46: E251 unexpected spaces around keyword / parameter equals
143: D210 No whitespaces allowed surrounding docstring text
143: D202 No blank lines allowed after function docstring (found 1)
143: D400 First line should end with a period (not ')')
166:5: E303 too many blank lines (2)
166: D210 No whitespaces allowed surrounding docstring text
166: D202 No blank lines allowed after function docstring (found 1)
166: D400 First line should end with a period (not '6')
169:14: E222 multiple spaces after operator


1: D100 Missing docstring in public module
55:1: I100 Imports statements are in the wrong order. import datetime should be before import time
57:1: I100 Imports statements are in the wrong order. import logging should be before import traceback
62:1: I201 Missing newline before sections or imports.
63:1: I100 Imports statements are in the wrong order. from socket should be before from intbitset
63:1: I201 Missing newline before sections or imports.
65:1: I101 Imported names are in the wrong order. Should be _db_login, run_sql
66:1: I201 Missing newline before sections or imports.
67:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio_accounts.models
67:1: I201 Missing newline before sections or imports.
68:1: I101 Imported names are in the wrong order. Should be CFG_BIBSCHED_FLUSH_LOGS, CFG_BIBSCHED_PROCESS_USER, CFG_SITE_NAME, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_TMPDIR, CFG_VERSION
68:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.access.engine
79:1: I101 Imported names are in the wrong order. Should be CFG_EXTERNAL_AUTHENTICATION, CFG_EXTERNAL_AUTH_USING_SSO
80:49: E126 continuation line over-indented for hanging indent
81:1: I101 Imported names are in the wrong order. Should be get_email, get_email_from_username, get_user_preferences
81:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.modules.access.local_config
82:1: I101 Imported names are in the wrong order. Should be CFG_BIBSCHED_LOGDIR, CFG_BIBTASK_DEFAULT_GLOBAL_TASK_SETTINGS, CFG_BIBTASK_DEFAULT_TASK_SETTINGS, CFG_BIBTASK_FIXEDTIMETASKS, CFG_BIBTASK_LOG_FORMAT, CFG_BIBTASK_VALID_TASKS
82:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask_config should be before from invenio.legacy.webuser
92:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.utils.shell
93:1: I101 Imported names are in the wrong order. Should be bibsched_get_host, bibsched_set_host
94:41: E126 continuation line over-indented for hanging indent
108: D101 Missing docstring in public class
111:1: E302 expected 2 blank lines, found 1
111: D101 Missing docstring in public class
112: D102 Missing docstring in public method
116:1: E302 expected 2 blank lines, found 1
116: D400 First line should end with a period (not 't')
116: D205 1 blank line required between summary line and description (found 0)
139:13: E266 too many leading '#' for block comment
155: D205 1 blank line required between summary line and description (found 0)
181:17: E266 too many leading '#' for block comment
204:17: E266 too many leading '#' for block comment
224:17: E266 too many leading '#' for block comment
247:17: E266 too many leading '#' for block comment
270:17: E266 too many leading '#' for block comment
287:12: E713 test for membership should be 'not in'
310:9: E266 too many leading '#' for block comment
326: D401 First line should be in imperative mood ('Return', not 'Returns')
352: D401 First line should be in imperative mood ('Return', not 'Returns')
352: D400 First line should end with a period (not 'k')
365: D401 First line should be in imperative mood ('Return', not 'Returns')
365: D400 First line should end with a period (not 'k')
384: D400 First line should end with a period (not 's')
409: D400 First line should end with a period (not 'r')
429: D401 First line should be in imperative mood ('Set', not 'Sets')
457: D210 No whitespaces allowed surrounding docstring text
457: D205 1 blank line required between summary line and description (found 0)
487:18: E203 whitespace before ':'
488:31: E203 whitespace before ':'
489:20: E203 whitespace before ':'
490:29: E203 whitespace before ':'
491:15: E203 whitespace before ':'
492:18: E203 whitespace before ':'
493:20: E203 whitespace before ':'
494:18: E203 whitespace before ':'
495:19: E203 whitespace before ':'
496:24: E203 whitespace before ':'
497:18: E203 whitespace before ':'
533:33: E128 continuation line under-indented for visual indent
534:33: E128 continuation line under-indented for visual indent
535:33: E128 continuation line under-indented for visual indent
566:5: E303 too many blank lines (2)
642:1: E302 expected 2 blank lines, found 1
642: D210 No whitespaces allowed surrounding docstring text
642: D205 1 blank line required between summary line and description (found 0)
664:13: E128 continuation line under-indented for visual indent
700:41: E261 at least two spaces before inline comment
743:1: E302 expected 2 blank lines, found 1
743: D400 First line should end with a period (not 'k')
749:24: E203 whitespace before ':'
751:1: E302 expected 2 blank lines, found 1
751: D401 First line should be in imperative mood ('Return', not 'Returns')
751: D400 First line should end with a period (not 'k')
761:1: E302 expected 2 blank lines, found 1
761: D400 First line should end with a period (not 'S')
768:1: E302 expected 2 blank lines, found 1
768: D401 First line should be in imperative mood ('Return', not 'Returns')
768: D400 First line should end with a period (not 'm')
778:1: E302 expected 2 blank lines, found 1
778: D400 First line should end with a period (not 'm')
784:28: E203 whitespace before ':'
786:1: E302 expected 2 blank lines, found 1
786: D401 First line should be in imperative mood ('Update', not 'Updates')
791:13: E128 continuation line under-indented for visual indent
793:1: E302 expected 2 blank lines, found 1
793: D401 First line should be in imperative mood ('Update', not 'Updates')
798:13: E128 continuation line under-indented for visual indent
800:1: E302 expected 2 blank lines, found 1
803:9: E128 continuation line under-indented for visual indent
810:1: E302 expected 2 blank lines, found 1
810: D400 First line should end with a period (not 'e')
817:1: E302 expected 2 blank lines, found 1
817: D205 1 blank line required between summary line and description (found 0)
843:1: E302 expected 2 blank lines, found 0
843: D401 First line should be in imperative mood ('Return', not 'Returns')
843: D209 Multi-line docstring closing quotes should be on a separate line
843: D205 1 blank line required between summary line and description (found 0)
843: D208 Docstring is over-indented
865: D401 First line should be in imperative mood ('Thi', not 'This')
865: D400 First line should end with a period (not ',')
865: D205 1 blank line required between summary line and description (found 0)
903:1: E302 expected 2 blank lines, found 1
903: D400 First line should end with a period (not 'n')
903: D205 1 blank line required between summary line and description (found 0)
914:1: E302 expected 2 blank lines, found 1
914: D202 No blank lines allowed after function docstring (found 1)
914: D205 1 blank line required between summary line and description (found 0)
943:5: E266 too many leading '#' for block comment
985:13: E266 too many leading '#' for block comment
992:1: E302 expected 2 blank lines, found 1
992: D401 First line should be in imperative mood ('Submit', not 'Submits')
992: D209 Multi-line docstring closing quotes should be on a separate line
992: D202 No blank lines allowed after function docstring (found 1)
992: D400 First line should end with a period (not 'l')
992: D205 1 blank line required between summary line and description (found 0)
992: D208 Docstring is over-indented
996:5: E266 too many leading '#' for block comment
999:5: E266 too many leading '#' for block comment
1001:5: E266 too many leading '#' for block comment
1004:5: E266 too many leading '#' for block comment
1014:9: E128 continuation line under-indented for visual indent
1019:5: E266 too many leading '#' for block comment
1024: D401 First line should be in imperative mood ('Return', not 'Returns')
1024: D209 Multi-line docstring closing quotes should be on a separate line
1024: D400 First line should end with a period (not 'k')
1024: D205 1 blank line required between summary line and description (found 0)
1029:9: E128 continuation line under-indented for visual indent
1034:13: E128 continuation line under-indented for visual indent
1088: D400 First line should end with a period (not 'n')
1094:25: E127 continuation line over-indented for visual indent
1102: D400 First line should end with a period (not 'n')
1108: D401 First line should be in imperative mood ('Run', not 'Runs')
1108: D209 Multi-line docstring closing quotes should be on a separate line
1108: D202 No blank lines allowed after function docstring (found 1)
1108: D205 1 blank line required between summary line and description (found 0)
1118:5: E266 too many leading '#' for block comment
1125:13: E128 continuation line under-indented for visual indent
1134:5: E266 too many leading '#' for block comment
1138:13: E128 continuation line under-indented for visual indent
1161:17: E266 too many leading '#' for block comment
1162:211: E261 at least two spaces before inline comment
1163:199: E261 at least two spaces before inline comment
1173:13: E128 continuation line under-indented for visual indent
1178:5: E266 too many leading '#' for block comment
1185:5: E266 too many leading '#' for block comment
1188:5: E266 too many leading '#' for block comment
1210:13: E266 too many leading '#' for block comment
1212:17: E266 too many leading '#' for block comment
1219:17: E266 too many leading '#' for block comment
1229:13: E266 too many leading '#' for block comment
1231:9: E266 too many leading '#' for block comment
1252: D401 First line should be in imperative mood ('Print', not 'Prints')
1262:9: E128 continuation line under-indented for visual indent
1264:9: E128 continuation line under-indented for visual indent
1266:9: E128 continuation line under-indented for visual indent
1267:9: E128 continuation line under-indented for visual indent
1271:9: E128 continuation line under-indented for visual indent
1272:9: E128 continuation line under-indented for visual indent
1273:9: E128 continuation line under-indented for visual indent
1280:9: E128 continuation line under-indented for visual indent
1293:1: E302 expected 2 blank lines, found 1
1297:13: E128 continuation line under-indented for visual indent
1302:1: E302 expected 2 blank lines, found 1
1305:13: E128 continuation line under-indented for visual indent
1307:25: E261 at least two spaces before inline comment
1310:1: E302 expected 2 blank lines, found 1
1313:13: E128 continuation line under-indented for visual indent
1321:1: E302 expected 2 blank lines, found 1
1321: D209 Multi-line docstring closing quotes should be on a separate line
1327:13: E128 continuation line under-indented for visual indent
1331:1: E302 expected 2 blank lines, found 1
1336:1: E302 expected 2 blank lines, found 0
1353:1: E302 expected 2 blank lines, found 1
1353: D205 1 blank line required between summary line and description (found 0)
1368:1: E302 expected 2 blank lines, found 1
1368: D400 First line should end with a period (not 'r')
1368: D205 1 blank line required between summary line and description (found 0)
1385:63: E502 the backslash is redundant between brackets
1386:13: E128 continuation line under-indented for visual indent
1388:57: E261 at least two spaces before inline comment
1395:63: E502 the backslash is redundant between brackets
1396:9: E128 continuation line under-indented for visual indent