Yes that's why I implemented this (which was removed in this commit) at the beggining of the summer. The comment tell you why this solution was used.
 /*
- * Since QPlainTextEdit::appendPlainText() add newLines without asking us and
- * QPlainTextEdit::insertPlainText() insert text by default at the cursor pos,
- * which can be modified by the user, this function assures the text is
- * inserted at the end without new line by default.
- */
-
 void MainWindow::appendLog(const QString& text)
 {
-    QTextCursor prev_cursor = m_ui->plainTextEdit_JohnOut->textCursor();
-    m_ui->plainTextEdit_JohnOut->moveCursor(QTextCursor::End);
-    m_ui->plainTextEdit_JohnOut->insertPlainText(text);
-    m_ui->plainTextEdit_JohnOut->setTextCursor(prev_cursor);

 }


알고 있는지 모르겠는데.
ready도 많이 쓰지만 아래처럼도 많이 쓴다.
```
$(function(){
});
```


Yeah, that is true. I removed this and wrote a test to ensure that the error bubbles up.


I just followed the nomenclature depot_tools chose :)


clone을 사용했구나 잘했다.
실제로도 이렇게 많이 쓴다.^^


이 부분을  handlebar로 바꿔서 해봐.


mobile....


It seems that @Eldy took some part of lead module code to introduce it (at least table name). the project Lead is now hosted here https://github.com/FHenry/lead
In my opinion, we should not merge Project and Lead. It two feature not for the same purpose. Lead do not need task, project need millestones...  I wish to introduce this module into next release (3.9, because I don't have time to merge it in dev branch before freeze), but if some code part are already introduce, I don't know what to do. I take a look at 3.8 to see how it works.


closest 잘 썼다.
closest, parents, parent의 차이점을 알고 있니?


please get rid of the _ in perFrame_


this->perFrame = perFrame;


여긴 parent을 썼네?
왜 closest을 안쓰고 parent을 썼지?


This is the expected semantics when there's only one block and no padding is necessary, isn't it? Or should we call `reader.readWithPadding` one more time to know it has ended?


`type_data` can be used for other things and is not strictly being used for what the comment says.


왜, li가 div인지 한번 고민해보고 잘 모르겠으면 수업시간에 물어보렴.


Correct me if I'm wrong, but it's not being set to null inside the function, so won't it be null as the file is initially parsed? By the time the function itself is called, `user_callback` will have already been set to null when the file was read in?


@xynnn, I really don't like injecting the Service Container here but I can't seem to get tests passing when I try injecting just the `@twig` service.


It is the module https://www.dolistore.com/fr/crm-gestion-relation-client/308-PDF-de-proposition-commerciale-avec-fiche-produit-service.html push into core version during devcamp.
If you activate the option, in product document card, you can check a PDF document, and Invoice and proposal, when the product in in it, the PDF seleted will be outputed in propal/invoice/propal. Can be usefull to add commercial presentation with your proposal for some product


I was just expanding on the pattern from L:180 so I don't know. In fact, I meant to remove it from there. I'll add it to the issue tracker.


IIRC My fork is just a bunch of other peoples patches.


what do you think to move buttons creation to separate method or even file?


Does the `radio_type` spelling actually help? We want `radio` at the very end. If the custom code has to take radio and radioType or radio and radio_type into account isn't really different.


I looked into this and didn't really know where the best place to put extracted constant is right now. I'd prefer to leave this cleanup for another PR and just focus on getting this fix in.


Hello @sunheehnus, yep but I modified it (in the previous commit) to have a return value to signal it, this is why there is:

    if (jobReplicationAchieved(j) == DISQUE_ERR) { .... return back to the caller ... }


No, this means 0.23 will be the last published version in games-overlay :-(

I doubt to get ever any feedback on NetMauMau and the happening with my sis is
enough just to publish any new version on GH, SF, LP and OBS.

I want to keep that code separated just to have the next project to work on.
NMM will only get bugfixes if I discover one or (unlikely) if some feedback
comes.

Am Dienstag, 30. Juni 2015 schrieb Julian Ospald:
> Well, I don't want to add libraries to this repository (although I have
> already violated this once and I want to keep it that way). So it seems you
> have to *optionally* bundle it.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/velnias75/games-overlay/commit/8ecf7f25ad1a9a381433a6c3f
>70d6d4192b3d9f7#commitcomment-11929990


The change is in d173877


If there is one block exactly and no padding necessary I would definitely expect only one call to readWithPadding to be necessary.


Sure, didn't know if there was pre-existing pattern. My preference would simply be a "ConfigurationKeys" class with interfaces inside of it for grouping and in each interface public static final strings representing the keys. That would make reference searching for where config items are used much more elegant in the IDE as well.


Now that we have data associated with the type, it's useful to pass the type to other callbacks that are not getting it (either explicitly or implicitly via `sol_flow_node *`).


Wait, I see what I've done - the _unauthorized_ tests should use `self.user_refused` and the _authorized_ test (as above) should use `self.user`. Good catch, thanks @mhl


Isn't this missing a `internal_name='snr'`?


Right, was not enough. In the usuall case, the code refreshes the page and the `currentUserChanged` isn't propagated.


C'était trop dur de dire :
> Formatting
?
è_é


can't comment on the `signalToNoiseRatio =` line, slightly below, but I think that should again map to `snr`, at least LocateV1Transform did that so far.


reack


404
Here's the proper link : https://github.com/savoirfairelinux/monitoring-tools


Looks fine


Fixed.


@Agontuk which other .so files should I remove from vendor to avoid bugs?


This command is not required. The environment variable automatically routes the main to run cluster_insight.py. I use it in debug mode to explicitly start it in debug mode.


In everything I have looked it it is, it probably could be removed from public, but if Storage is ever used, it needs to be 777.


this is temporary goat image logic using a set of fixed goat image assets in an array. this can be replaced with @RHTurnerNOLA 's API image source logic.


OK, I will change that en will let you know in this thread.


to remove


If `setFullSize` uses `!!fit`, it seems like `setHalfSize` should too.


I have added a license file in the root of the project.  We do need to add the notice to any documentation that we produce though.


いいね！


Yes I would like to know why, the one I put was perfectly fine and actually how the controller itself renders
 except the glow in the dark.


As discussed in person, don't store the builder on the options structure. You can grab it and any other relevant information from the type->data. Pass the type as a first parameter for child_opts_set callback.


Yes you better should be, add the moment the copy function with ctrl+c is broken inside the editor and also attachment uploads are fixed now.


If you want the program to run in debug mode, the command option needs to be included.
It looks the same as in the file: install/cluster-insight-master-controller-debug.yaml

          command:
            - "python"
            - "./cluster_insight.py"
            - "--debug"


I fired up a Travis CI account of my own so I can run tests on my own fork without opening bogus PR requests. My command history for today now includes `git commit -m "the Travis shell syntax parser is dumber than a bag of rocks"` Meh.


@jackparmer sounds good!


The only thing is that I might call it `org.hibernate.search.fulltext_query` to leave room for the other queries?


done, see commit https://github.com/opengapps/opengapps/commit/5fb32f988cf31950d4c3288544a6a885ef8c3b23


Fixes #57


Looks like this commit didn't get ported back to the 14.07 branch.  Trying to specify the PingCmd option for olsrd on that branch fails with "daemon.info olsrd: /etc/init.d/olsrd: warning_invalid_value() in option 'olsrd.cfg064e54.PingCmd', skipped".


Shouldn't the last "Arger" be "Ärger"? (With Umlaut)


Do you mean it creates a PDF of a product card ?!?
or it just adds the option to choose to merge with propal, a pdf which is already uploaded in the linked documents of the product ?


いいね！！


WTF


HEY


Ce sont des tests. Ils ont tous une erreur qui ne leur permettent plus ni de pull, ni de commit.


Grand fan du nom du commit.


やったぜー


LA PUTAIN DE FAUTE LAAAAAAA !


Have a look at the ioloops!


This should actually use simplejson. We don't want our special non-JSON compliant data structures like custom hash or datetime values to be returned to an outside party. The error payloads and other responses are all going to outside parties.


Minor: would `SOL_FLOW_BUILDER_OPTIONS_API_VERSION` be more precise?

Actually, we don't even need this particular versioning here because the user can't create the struct on their own (it can't allocate it on the stack for example), but might be helpful as a safety net to catch mistakes.


Oh, good catch. We should probably include more of N+1s in `pages_controller#show`, no?


Есть причина, по которой здесь кортеж а тут https://github.com/MarinaPeresypkina/w_catalog/commit/02d937da4621f015db34b13f0cd7201b5cef323d#diff-9a1dce4f3fc427a5efcc4eec9c9328d7R16 лист?


Would it be possible to add the "Eclipse Plug-In Development Environment" feature as a dependency?


Ah, will fix that, thanks


No problem, saw it while translating.


Está re bueno Stefy! -> De mis favoritos hasta ahora.

Mi feedback va más sobre Jekyll:

- Borrar el que file que no termina en .md (porque está 2 veces el post si entiendo bien).
- No es necesario meterlo en el folder de tumblr. Con que esté adentro de _posts funciona.

Con eso y las sugerencias de Isa, :shipit: !


I got this wrong myself here, for the error constant we should use standard simplejson instead of our customjson.


I think this is not used anymore.


Sure, my thought was that `setFullSize` is the only one that is getting called without arguments, but it doesn't hurt to enforce the type for both, just in case.


The actual call to has_access is made within verify_error_type (because I was adding on to an existing test and that's how it was done in others like verify_access), however this assertion uses a different call to has_access so I can't use the same helper method. Didn't want to make a helper method for one test but looking at the structure now there's a lot of unnecessary repeated calls to has_access so I'll look into changing it


> Loosening the regexp to allow uppercase letters for now - we can discuss
> if we want to tighten the validation as a separate question.

I'm personally :+1: for tightening the validation, that was basically one of the original reasons. I think that making things lowercase under the hood just hides that problem away. User should be aware of what's happening - i.e. the definition in DSL should be IMO as close to reality as possible with as little magic in the middle as possible.


@Seldaek I don't think this is needed as pressing <kbd>Tab</kbd> does the same.


This a stable version if you want to revert back to this.


Yes, they are. Will fix. Thanks


Hi @antirez , I didn't notice that, my bad.
The commit looks good to me. :-)


не вижу, что именно изменилось


By raises do you mean the VisibilityError object that can be returned?


Why choose to cache at this layer instead of in `CourseOverview`?


Interesting, I always thought you need to use the bracket notation (second example) to use multiple namespace in a single file.


Для чего нужен getattr? Я погуглила, получила очень общее представление, но когда я смотрю на этот код, то не понимаю, почему нельзя обойтись без него. Почему нельзя сразу как-нибудь объявить longestwords?


@radeksimko yeah I was just in "fix the tests" mode - I'd be okay with that. We'd just need to clean up the extra code for the downcase comparison as well.


реальные задачи


`<%==` equals `<%= raw`. So, no need to mark as `html_safe`.


"реальный задачи на реальных проектах" -> "реальные задачи на реальных проектах"

@BelkinaDasha bingo! =)


The retry mechanism (including backoff) should probably stay.


I think we can live with the rather flat structure for now. There are also references from Cluster Usage to these tools.


@phinze Understood. If tighten, then properly :smiley:


おk


понял, всем спасибо)


This was here to avoid `done(err);` getting called twice.
Without the check it's what happens, and the test is being completed twice in the log.

This is due because the  `close` event is emitted with **and** without errors.


有 UpdateOrderingRecordActionTemplate 可以用

$actionTemplate->register($runner, 'UpdateOrderingRecordActionTemplate', array(
    'namespace' => 'namespace',
    'model' => 'model'   // model's name
));


All the part 1 tests passed!

On Mon, Jun 29, 2015 at 10:31 PM, Mipmap <notifications@github.com> wrote:

> Looks 100% correct to me, nice job!
>
> Did all the part 1 tests past the unit tests?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/animals4all/Exercise04/commit/b86fa7d6f731bcd630eabfbe4ad46f23f1efbe59#commitcomment-11923098>
> .
>


Nope, because this would create Aerger instead. Btw. this line was just rearranged, see line 125 below.


Why setting to 0? enum class are strongly typed in c++11.


Can you revert this commit, please. The submit side explicitly drops and removes unknown values from the payloads, so it doesn't have to send a whole bunch of `{"ta": null, "snr": null}` etc. values over the wire to our backend.

If the submit side gives you any trouble, just leave the old preprocess code in place, and I'll take care of adjusting it. The whole PR is getting big enough on its own just for the locate side.


@Profpatsch @zanchey I've noticed this too: [the commit to remove the GREP_OPTIONS line](https://github.com/fish-shell/fish-shell/commit/efc3846fcfa6f0bae8312645c41b132c6156b3d1) is [in the history for the file in master](https://github.com/fish-shell/fish-shell/commits/master/share/functions/grep.fish), but [not in the history of the file for 2.1.2](https://github.com/fish-shell/fish-shell/commits/2.1.2/share/functions/grep.fish), even though the commit was authored Nov 24, 2014, and 2.1.2 was released on Feb 16, 2015.

Note that the release tarball (http://fishshell.com/files/2.1.2/fish-2.1.2.tar.gz) contains the line too, meaning [(re-)installing Fish via homebrew](https://github.com/Homebrew/homebrew/blob/967cb9ca97a830ce2c85b21fdbf7756629198a25/Library/Formula/fish.rb) does nothing.


You need to install autoconf, Paoloo. :)

On Tue, Jun 30, 2015 at 7:37 AM, Paolo Oliveira <notifications@github.com>
wrote:

> It gave a lot of errors, libuv is not present(perhaps you forgot to add *).
>
> paolo@daath:~/Public/dfg/node9-master$ ./rebuild.sh
> sh: 0: Can't open autogen.sh
> ./rebuild.sh: line 1: ./configure: No such file or directory
> make: *** No targets specified and no makefile found. Stop.
> rm: cannot remove ‘.libs/lib*.so*’: No such file or directory
> ==== Building LuaJIT 2.0.4 ====
> make -C src
> make[1]: Entering directory
> /home/paolo/Public/dfg/node9-master/LuaJIT-2.0.4/src'
> DYNLINK libluajit.so
> LINK luajit
> OK Successfully built LuaJIT
> make[1]: Leaving directory
> /home/paolo/Public/dfg/node9-master/LuaJIT-2.0.4/src'
> ==== Successfully built LuaJIT 2.0.4 ====
> make[1]: lib9.make: No such file or directory
> make[1]: *** No rule to make target lib9.make'. Stop.
> make: *** [clean] Error 2
> ./rebuild.sh: line 7: premake5: command not found
> ./rebuild.sh: line 8: premake5: command not found
> ==== Building lib9 (debug) ====
> make[1]: lib9.make: No such file or directory
> make[1]: *** No rule to make targetlib9.make'. Stop.
> make: *** [lib9] Error 2
> paolo@daath:~/Public/dfg/node9-master$
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jvburnes/node9/commit/0ca97e87e38515b6a2317d5a0548b8f28891cee4#commitcomment-11931684>
> .
>


람다에서  삭제가 문제네..


This is actually one of the caveats of genjavadoc that I have learned the hard way, there is no way to link to a nested object.

I actually made another genjavadoc mistake in the above doc. When linking to nested class as in `[[CurrentTopics]]` you must use qualify it like `[[DistributedPubSubMediator.CurrentTopics]]`


> This is interesting.

Yes, that's basically your idea from #16!

I already used your idea here: http://python-sounddevice.readthedocs.org/en/latest/#sounddevice.CallbackStop and I think it works quite well.

> I'm guessing you still want the other exceptions to be raised (without stopping the process function calling)?

That's very much open for discussion.

IMHO it would be best to stop calling the process function on any exception (this is what `error=STOP_CALLING` does).

If something goes wrong in the callback function, it's very likely to go wrong in the next invocation, too.
I actually had the experience before, when I had a typo or some other minor bug in the process callback, I got a continuous flood of tracebacks on stderr which was very annoying.

I think it's fair to say that if an exception occurs, something went wrong and it would be the safest thing to turn off callback processing.

The only difference between `CallbackExit` and all other exceptions would be that former is silent and doesn't print anything on stderr.


I don't think the 2nd option is workable because of the SQLite non-compatibility with NFS.
It would be good to put something in the --tempdir help about it having to be a local directory.
The load_chunk and merge_chunks commands should then work because they copy files to/from the tmp dir when they run into SQLite errors related to the NFS issue.


@mikepetersonccv Are you following a "best practices" doc somewhere?  How did you know what to look for?


Почему нельзя обойтись только функцией intersect? __and__ ведь просто ее и использует.


 preview before | after, this is lighter without privs requiered
![capture-10](https://cloud.githubusercontent.com/assets/7189389/8433323/522e7230-1f45-11e5-940f-88fcb33f9628.png)


Maybe add autocapitalization. Since we have no way to tell the user they must capitalized the characters(for now), it could be less confusing for the user.
`self.passphraseInputField.autocapitalizationType = UITextAutocapitalizationTypeAllCharacters;`


HBIRE_vector_take2 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1680 of 1682 tests passed)

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


``` javascript
(new TypeError() instanceof Error)
> true
function FooBarError(message) { this.message = message; }
FooBarError.prototype = new TypeError();
(new FooBarError() instanceof Error)
> true
```

Is it possible this error is getting propagated across frames?


Replace class var @@defaults with a class instance var.


More precise how?
I added it for safety and correctness (everything that has options has a sub_api, being different just because it's internal felt wrong).


thx


@miguelportilla good comment, but `forEachItem` is going to call the lambda for every item in the list. To exit early I'd have to overload `forEachItem` to handle functions that could exit early, and that's probably out of scope for this change set. I also need the local `exists` because this iteration happens through a lambda.


We should't use THREAD_INFOR_TYPE in mono-threads.c


Oh! Did not know that!


this also has to be "datacenters/*" - otherwise it lead very interesting exceptions while switching the connection from one datacenter to an another


Oh I see... tricky :~
I think Roland (not `@`-ing, he's supposed to be book writing ;-)) was fixing this one actually recently https://github.com/typesafehub/genjavadoc/commit/fd4782f94a8bbace4662770dbd47c6822e297a5c
May work with the upcoming release :)


This is probably outside the scope of this PR, but it'd be nice to check if the window is minimized using a model attribute rather than the height, since that could change in the future.


Since we can only clear for the current thread, we shouldn't make it possible to pass any thread as argument.


@chrisseaton @eregon This seems to work, but please let me know if there's a better way to build up a new frame for the call.


@TrySound Is this really required?


I filed a bug for this here: https://github.com/chef/chef/issues/3618

Chef doesn't use these automatic attributes for anything internally, the bug is actually a lot more subtle.


HBIRE_vector_take2 (Myoldmopar) - 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)


Why'd you do an ol instead of ul? Any particular reason?


Oops. Sorry. Fixed.


I added this because `dlib` is needed for Janez's `structured_learning` branch of pgmlink.  I guess it was a bit premature of me to add `dlib` here, since this build still uses the master branch (which doesn't need it).


11 out of 14 tests are failing when I run it locally.


1: M111 unrecognized component name: legacy


This is not equivalent. mono_thread_info_self_interrupt leaves the thread in the interrupt state.


30:1: I201 Missing newline before sections or imports.
31:1: I100 Imports statements are in the wrong order. import logging should be before from six
31:1: I201 Missing newline before sections or imports.
33:1: I201 Missing newline before sections or imports.
34:1: I101 Imported names are in the wrong order. Should be current_app, has_app_context
34:1: I100 Imports statements are in the wrong order. from flask should be before import six
34:1: I201 Missing newline before sections or imports.
35:1: I100 Imports statements are in the wrong order. from functools should be before from flask
35:1: I201 Missing newline before sections or imports.
35:1: F401 'wraps' imported but unused
36:1: I101 Imported names are in the wrong order. Should be find_modules, import_string
36:1: I201 Missing newline before sections or imports.
111:13: B901 blind except: statement
224:1: E302 expected 2 blank lines, found 1
228: D102 Missing docstring in public method
231: D102 Missing docstring in public method
239: D102 Missing docstring in public method
242: D102 Missing docstring in public method
246: D401 First line should be in imperative mood ('Run', not 'Runs')
298:23: E222 multiple spaces after operator


Thanks! Good point. it should be a ul! :)


25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. import sys should be before import time
28:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
32:1: I100 Imports statements are in the wrong order. from invenio.utils.date should be before from six
32:1: E402 module level import not at top of file
39:1: I101 Imported names are in the wrong order. Should be CFG_BIBRANK_SHOW_CITATION_LINKS, CFG_CACHEDIR, CFG_CERN_SITE, CFG_INSPIRE_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBSEARCH_SHOW_COMMENT_COUNT, CFG_WEBSEARCH_SHOW_REVIEW_COUNT
39:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.date
39:1: E402 module level import not at top of file
40:6: E126 continuation line over-indented for hanging indent
51:1: I101 Imported names are in the wrong order. Should be addadminbox, createhiddenform, get_def_name, get_languages, get_name, modify_translations, tupletotable, write_outcome
51:1: E402 module level import not at top of file
52:6: E126 continuation line over-indented for hanging indent
60:1: I101 Imported names are in the wrong order. Should be get_table_update_time, run_sql
60:1: E402 module level import not at top of file
61:6: E126 continuation line over-indented for hanging indent
63:1: I101 Imported names are in the wrong order. Should be external_collection_apply_changes, external_collection_get_state, external_collection_get_update_state_list, external_collection_sort_engine_by_name, external_collections_dictionary
63:1: E402 module level import not at top of file
64:6: E126 continuation line over-indented for hanging indent
69:1: E402 module level import not at top of file
70:6: E126 continuation line over-indented for hanging indent
71:1: I100 Imports statements are in the wrong order. from invenio.legacy.websearch_external_collections.config should be before from invenio.legacy.websearch_external_collections.utils
71:1: E402 module level import not at top of file
74:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from invenio.legacy.websearch_external_collections.config
74:1: E402 module level import not at top of file
75:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.legacy.bibdocfile.api
75:1: E402 module level import not at top of file
77:1: E402 module level import not at top of file
78:1: E402 module level import not at top of file
79:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.modules.access.local_config
79:1: E402 module level import not at top of file
80:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.ext.logging
80:1: I201 Missing newline before sections or imports.
80:1: E402 module level import not at top of file
81:1: I201 Missing newline before sections or imports.
81:1: E402 module level import not at top of file
82:1: E402 module level import not at top of file
84:1: E302 expected 2 blank lines, found 1
84:25: E251 unexpected spaces around keyword / parameter equals
84:27: E251 unexpected spaces around keyword / parameter equals
84: D202 No blank lines allowed after function docstring (found 1)
84: D400 First line should end with a period (not 'l')
91:1: E302 expected 2 blank lines, found 1
91: D200 One-line docstring should fit on one line with quotes (found 3)
99:1: E302 expected 2 blank lines, found 1
99: D209 Multi-line docstring closing quotes should be on a separate line
99: D400 First line should end with a period (not 'n')
99: D205 1 blank line required between summary line and description (found 0)
131:17: E221 multiple spaces before operator
156:41: F841 local variable 'e' is assigned to but never used
182:1: E302 expected 2 blank lines, found 1
182: D209 Multi-line docstring closing quotes should be on a separate line
182: D202 No blank lines allowed after function docstring (found 1)
182: D400 First line should end with a period (not 'n')
182: D205 1 blank line required between summary line and description (found 0)
191:5: F841 local variable 'rnk_dict' is assigned to but never used
200:15: E221 multiple spaces before operator
220:17: E221 multiple spaces before operator
226:172: E203 whitespace before ','
243:17: E221 multiple spaces before operator
250:172: E203 whitespace before ','
272:1: E302 expected 2 blank lines, found 1
272: D209 Multi-line docstring closing quotes should be on a separate line
272: D202 No blank lines allowed after function docstring (found 1)
272: D205 1 blank line required between summary line and description (found 0)
302:49: E225 missing whitespace around operator
307:5: F841 local variable 'tree' is assigned to but never used
319:75: E225 missing whitespace around operator
329:27: E225 missing whitespace around operator
340:18: E225 missing whitespace around operator
340:64: E225 missing whitespace around operator
357:1: E302 expected 2 blank lines, found 1
357: D209 Multi-line docstring closing quotes should be on a separate line
357: D202 No blank lines allowed after function docstring (found 1)
357: D205 1 blank line required between summary line and description (found 0)
389:1: E302 expected 2 blank lines, found 1
389: D209 Multi-line docstring closing quotes should be on a separate line
389: D202 No blank lines allowed after function docstring (found 1)
389: D205 1 blank line required between summary line and description (found 0)
394:11: E221 multiple spaces before operator
408:9: F841 local variable 'vir_sons' is assigned to but never used
445:1: E302 expected 2 blank lines, found 1
445: D209 Multi-line docstring closing quotes should be on a separate line
445: D202 No blank lines allowed after function docstring (found 1)
445: D205 1 blank line required between summary line and description (found 0)
460:5: F841 local variable 'fin_output' is assigned to but never used
469:30: E225 missing whitespace around operator
472:30: E225 missing whitespace around operator
478:30: E225 missing whitespace around operator
481:91: E231 missing whitespace after ','
481:30: E225 missing whitespace around operator
487:44: E225 missing whitespace around operator
487:112: E225 missing whitespace around operator
490:34: E225 missing whitespace around operator
509:48: E225 missing whitespace around operator
512:38: E225 missing whitespace around operator
522:36: E225 missing whitespace around operator
540:94: E225 missing whitespace around operator
545:55: E225 missing whitespace around operator
545:151: E225 missing whitespace around operator
566:44: E225 missing whitespace around operator
566:131: E225 missing whitespace around operator
569:44: E225 missing whitespace around operator
569:131: E225 missing whitespace around operator
575:29: F841 local variable 'e' is assigned to but never used
606:1: E302 expected 2 blank lines, found 1
606: D202 No blank lines allowed after function docstring (found 1)
606: D400 First line should end with a period (not 'y')
633:1: E302 expected 2 blank lines, found 1
633: D209 Multi-line docstring closing quotes should be on a separate line
633: D202 No blank lines allowed after function docstring (found 1)
633: D400 First line should end with a period (not 'x')
633: D205 1 blank line required between summary line and description (found 0)
638:5: F841 local variable 'col_dict' is assigned to but never used
660:15: E221 multiple spaces before operator
667:1: E302 expected 2 blank lines, found 1
667: D209 Multi-line docstring closing quotes should be on a separate line
667: D202 No blank lines allowed after function docstring (found 1)
667: D205 1 blank line required between summary line and description (found 0)
676:11: E221 multiple spaces before operator
682:5: F841 local variable 'col_dict' is assigned to but never used
683:5: F841 local variable 'pbx_dict' is assigned to but never used
688:13: E221 multiple spaces before operator
695:22: E126 continuation line over-indented for hanging indent
695:29: E221 multiple spaces before operator
715:72: E225 missing whitespace around operator
724:15: E221 multiple spaces before operator
732:15: E221 multiple spaces before operator
740:1: E302 expected 2 blank lines, found 1
740: D209 Multi-line docstring closing quotes should be on a separate line
740: D202 No blank lines allowed after function docstring (found 1)
740: D205 1 blank line required between summary line and description (found 0)
746:11: E221 multiple spaces before operator
753:13: F841 local variable 'pname' is assigned to but never used
759:5: F841 local variable 'col_dict' is assigned to but never used
765:13: E221 multiple spaces before operator
772:73: E221 multiple spaces before operator
788:15: E221 multiple spaces before operator
796:1: E302 expected 2 blank lines, found 1
796: D209 Multi-line docstring closing quotes should be on a separate line
796: D202 No blank lines allowed after function docstring (found 1)
796: D205 1 blank line required between summary line and description (found 0)
803:13: E221 multiple spaces before operator
804:11: E221 multiple spaces before operator
809:5: F841 local variable 'lang' is assigned to but never used
810:5: F841 local variable 'col_dict' is assigned to but never used
832:63: E225 missing whitespace around operator
881:15: E221 multiple spaces before operator
888:1: E302 expected 2 blank lines, found 1
888: D209 Multi-line docstring closing quotes should be on a separate line
888: D205 1 blank line required between summary line and description (found 0)
895:5: F841 local variable 'pbx_dict' is assigned to but never used
900:1: E302 expected 2 blank lines, found 1
900: D209 Multi-line docstring closing quotes should be on a separate line
900: D202 No blank lines allowed after function docstring (found 1)
900: D205 1 blank line required between summary line and description (found 0)
908:11: E221 multiple spaces before operator
918:8: E221 multiple spaces before operator
944:46: E225 missing whitespace around operator
944:85: E225 missing whitespace around operator
962:1: E302 expected 2 blank lines, found 1
962: D209 Multi-line docstring closing quotes should be on a separate line
962: D202 No blank lines allowed after function docstring (found 1)
962: D205 1 blank line required between summary line and description (found 0)
969:11: E221 multiple spaces before operator
997:1: E302 expected 2 blank lines, found 1
997: D209 Multi-line docstring closing quotes should be on a separate line
997: D202 No blank lines allowed after function docstring (found 1)
997: D205 1 blank line required between summary line and description (found 0)
1003:5: F841 local variable 'fmt_dict' is assigned to but never used
1008:1: E302 expected 2 blank lines, found 1
1008: D209 Multi-line docstring closing quotes should be on a separate line
1008: D202 No blank lines allowed after function docstring (found 1)
1008: D205 1 blank line required between summary line and description (found 0)
1013:5: F841 local variable 'fld_dict' is assigned to but never used
1025:1: E302 expected 2 blank lines, found 1
1025: D209 Multi-line docstring closing quotes should be on a separate line
1025: D202 No blank lines allowed after function docstring (found 1)
1025: D205 1 blank line required between summary line and description (found 0)
1030:5: F841 local variable 'name_1' is assigned to but never used
1031:5: F841 local variable 'name_2' is assigned to but never used
1036:1: E302 expected 2 blank lines, found 1
1036: D202 No blank lines allowed after function docstring (found 1)
1036: D205 1 blank line required between summary line and description (found 0)
1073:1: E302 expected 2 blank lines, found 1
1073: D202 No blank lines allowed after function docstring (found 1)
1073: D205 1 blank line required between summary line and description (found 0)
1096:31: E128 continuation line under-indented for visual indent
1097:31: E128 continuation line under-indented for visual indent
1098:31: E128 continuation line under-indented for visual indent
1099:31: E128 continuation line under-indented for visual indent
1100:31: E128 continuation line under-indented for visual indent
1101:31: E128 continuation line under-indented for visual indent
1102:31: E128 continuation line under-indented for visual indent
1104:31: E128 continuation line under-indented for visual indent
1105:31: E128 continuation line under-indented for visual indent
1106:31: E128 continuation line under-indented for visual indent
1107:31: E128 continuation line under-indented for visual indent
1108:31: E128 continuation line under-indented for visual indent
1109:31: E128 continuation line under-indented for visual indent
1110:31: E128 continuation line under-indented for visual indent
1129:1: E302 expected 2 blank lines, found 1
1129: D209 Multi-line docstring closing quotes should be on a separate line
1129: D202 No blank lines allowed after function docstring (found 1)
1129: D205 1 blank line required between summary line and description (found 0)
1145:11: E221 multiple spaces before operator
1182:1: E302 expected 2 blank lines, found 1
1182: D209 Multi-line docstring closing quotes should be on a separate line
1182: D202 No blank lines allowed after function docstring (found 1)
1182: D205 1 blank line required between summary line and description (found 0)
1189:11: E221 multiple spaces before operator
1191:5: F841 local variable 'col_dict' is assigned to but never used
1221:1: E302 expected 2 blank lines, found 1
1221: D202 No blank lines allowed after function docstring (found 1)
1221: D400 First line should end with a period (not 'y')
1221: D205 1 blank line required between summary line and description (found 0)
1228:11: E221 multiple spaces before operator
1248:1: E302 expected 2 blank lines, found 1
1248: D202 No blank lines allowed after function docstring (found 1)
1248: D400 First line should end with a period (not 'y')
1248: D205 1 blank line required between summary line and description (found 0)
1254:11: E221 multiple spaces before operator
1256:16: E222 multiple spaces after operator
1278:1: E302 expected 2 blank lines, found 1
1278: D209 Multi-line docstring closing quotes should be on a separate line
1278: D202 No blank lines allowed after function docstring (found 1)
1278: D205 1 blank line required between summary line and description (found 0)
1285:11: E221 multiple spaces before operator
1293:5: F841 local variable 'lang' is assigned to but never used
1294:10: E222 multiple spaces after operator
1295:5: F841 local variable 'col_dict' is assigned to but never used
1296:5: F841 local variable 'fld_dict' is assigned to but never used
1297:5: F841 local variable 'col_fld' is assigned to but never used
1298:14: E221 multiple spaces before operator
1299:5: F841 local variable 'fldv_dict' is assigned to but never used
1310:22: E221 multiple spaces before operator
1331:1: E302 expected 2 blank lines, found 1
1331: D209 Multi-line docstring closing quotes should be on a separate line
1331: D202 No blank lines allowed after function docstring (found 1)
1331: D205 1 blank line required between summary line and description (found 0)
1338:11: E221 multiple spaces before operator
1345:5: F841 local variable 'lang' is assigned to but never used
1346:10: E222 multiple spaces after operator
1347:5: F841 local variable 'col_dict' is assigned to but never used
1350:14: E221 multiple spaces before operator
1351:5: F841 local variable 'fldv_dict' is assigned to but never used
1355:9: E221 multiple spaces before operator
1378:15: E221 multiple spaces before operator
1391:1: E302 expected 2 blank lines, found 1
1391: D202 No blank lines allowed after function docstring (found 1)
1407:8: E221 multiple spaces before operator
1413:5: F841 local variable 'lang' is assigned to but never used
1415:5: F841 local variable 'fld_type_list' is assigned to but never used
1452:1: E302 expected 2 blank lines, found 1
1452: D202 No blank lines allowed after function docstring (found 1)
1468:8: E221 multiple spaces before operator
1474:5: F841 local variable 'lang' is assigned to but never used
1476:5: F841 local variable 'fld_type_list' is assigned to but never used
1513:1: E302 expected 2 blank lines, found 1
1513: D202 No blank lines allowed after function docstring (found 1)
1529:8: E221 multiple spaces before operator
1535:5: F841 local variable 'lang' is assigned to but never used
1537:5: F841 local variable 'fld_type_list' is assigned to but never used
1544:13: F841 local variable 'col_fld' is assigned to but never used
1575: D202 No blank lines allowed after function docstring (found 1)
1575: D400 First line should end with a period (not 'd')
1579:5: F841 local variable 'col_dict' is assigned to but never used
1591:8: E221 multiple spaces before operator
1596:5: F841 local variable 'lang' is assigned to but never used
1598:5: F841 local variable 'fld_type_list' is assigned to but never used
1637:1: E302 expected 2 blank lines, found 1
1637: D401 First line should be in imperative mood ('show', not 'shows')
1637: D209 Multi-line docstring closing quotes should be on a separate line
1637: D202 No blank lines allowed after function docstring (found 1)
1637: D400 First line should end with a period (not 'n')
1637: D205 1 blank line required between summary line and description (found 0)
1652:8: E221 multiple spaces before operator
1691:1: E302 expected 2 blank lines, found 1
1691: D103 Missing docstring in public function
1712:1: E302 expected 2 blank lines, found 1
1712: D202 No blank lines allowed after function docstring (found 1)
1738:1: E302 expected 2 blank lines, found 1
1738: D103 Missing docstring in public function
1763:1: E302 expected 2 blank lines, found 1
1763: D202 No blank lines allowed after function docstring (found 1)
1783:9: F841 local variable 'check' is assigned to but never used
1786:23: E231 missing whitespace after ':'
1787:23: E231 missing whitespace after ':'
1788:23: E231 missing whitespace after ':'
1798:1: E302 expected 2 blank lines, found 1
1801:5: F841 local variable 'changes' is assigned to but never used
1805:5: E303 too many blank lines (2)
1811:67: E502 the backslash is redundant between brackets
1813:2: E114 indentation is not a multiple of four (comment)
1813:2: E266 too many leading '#' for block comment
1829:78: E502 the backslash is redundant between brackets
1836: D209 Multi-line docstring closing quotes should be on a separate line
1836: D202 No blank lines allowed after function docstring (found 1)
1836: D205 1 blank line required between summary line and description (found 0)
1842:11: E221 multiple spaces before operator
1848:5: F841 local variable 'fmt_dict' is assigned to but never used
1849:5: F841 local variable 'col_dict' is assigned to but never used
1854:13: E221 multiple spaces before operator
1862:30: E221 multiple spaces before operator
1872:15: E221 multiple spaces before operator
1877:15: E221 multiple spaces before operator
1884:1: E302 expected 2 blank lines, found 1
1884: D209 Multi-line docstring closing quotes should be on a separate line
1884: D202 No blank lines allowed after function docstring (found 1)
1884: D205 1 blank line required between summary line and description (found 0)
1890:11: E221 multiple spaces before operator
1899:9: F841 local variable 'old_colNAME' is assigned to but never used
1904:5: F841 local variable 'col_dict' is assigned to but never used
1909:13: E221 multiple spaces before operator
1916:65: E221 multiple spaces before operator
1943:15: E221 multiple spaces before operator
1950:1: E302 expected 2 blank lines, found 1
1950: D202 No blank lines allowed after function docstring (found 1)
1950: D205 1 blank line required between summary line and description (found 0)
1957:11: E221 multiple spaces before operator
1983:1: E302 expected 2 blank lines, found 1
1983: D202 No blank lines allowed after function docstring (found 1)
1983: D200 One-line docstring should fit on one line with quotes (found 2)
1987:5: F841 local variable 'subtitle' is assigned to but never used
1991:5: F841 local variable 'output' is assigned to but never used
2002:227: E203 whitespace before ':'
2061:1: E302 expected 2 blank lines, found 1
2061: D401 First line should be in imperative mood ('Return', not 'Returns')
2061: D202 No blank lines allowed after function docstring (found 1)
2061: D400 First line should end with a period (not 'e')
2081:1: E302 expected 2 blank lines, found 1
2081: D401 First line should be in imperative mood ('Create', not 'Creates')
2081: D209 Multi-line docstring closing quotes should be on a separate line
2081: D202 No blank lines allowed after function docstring (found 1)
2081: D205 1 blank line required between summary line and description (found 0)
2093:9: F841 local variable 'move_from_id' is assigned to but never used
2122:37: F841 local variable 'e' is assigned to but never used
2197:187: E225 missing whitespace around operator
2197:267: E225 missing whitespace around operator
2197:277: E225 missing whitespace around operator
2197:375: E225 missing whitespace around operator
2197:484: E225 missing whitespace around operator
2212:1: E302 expected 2 blank lines, found 1
2212: D202 No blank lines allowed after function docstring (found 1)
2212: D400 First line should end with a period (not 'n')
2212: D205 1 blank line required between summary line and description (found 0)
2217:15: E225 missing whitespace around operator
2218:11: E221 multiple spaces before operator
2269:1: E302 expected 2 blank lines, found 1
2269: D209 Multi-line docstring closing quotes should be on a separate line
2269: D202 No blank lines allowed after function docstring (found 1)
2269: D205 1 blank line required between summary line and description (found 0)
2349:9: E271 multiple spaces after keyword
2369:1: E302 expected 2 blank lines, found 1
2369: D202 No blank lines allowed after function docstring (found 1)
2373:11: E221 multiple spaces before operator
2376:5: F841 local variable 'col_dict' is assigned to but never used
2390:5: B901 blind except: statement
2396:28: E128 continuation line under-indented for visual indent
2397:26: F841 local variable 'e' is assigned to but never used
2411:54: E225 missing whitespace around operator
2411:88: E225 missing whitespace around operator
2419:54: E225 missing whitespace around operator
2419:88: E225 missing whitespace around operator
2432:9: F841 local variable 'webcoll__update_time' is assigned to but never used
2433:54: E225 missing whitespace around operator
2433:88: E225 missing whitespace around operator
2443:54: E225 missing whitespace around operator
2443:88: E225 missing whitespace around operator
2462:1: E302 expected 2 blank lines, found 1
2462: D209 Multi-line docstring closing quotes should be on a separate line
2462: D202 No blank lines allowed after function docstring (found 1)
2462: D205 1 blank line required between summary line and description (found 0)
2467:11: E221 multiple spaces before operator
2485:1: E302 expected 2 blank lines, found 1
2485: D202 No blank lines allowed after function docstring (found 1)
2491:11: E221 multiple spaces before operator
2494:5: F841 local variable 'col_dict' is assigned to but never used
2496:13: E128 continuation line under-indented for visual indent
2498:27: E231 missing whitespace after ','
2499:13: E128 continuation line under-indented for visual indent
2500:5: F841 local variable 'rnk_list' is assigned to but never used
2511:56: E701 multiple statements on one line (colon)
2512:13: E701 multiple statements on one line (colon)
2561:1: E302 expected 2 blank lines, found 1
2561: D202 No blank lines allowed after function docstring (found 1)
2565:11: E221 multiple spaces before operator
2621:25: E126 continuation line over-indented for hanging indent
2621:36: E203 whitespace before ':'
2622:38: E203 whitespace before ':'
2635:29: E126 continuation line over-indented for hanging indent
2635:40: E203 whitespace before ':'
2636:42: E203 whitespace before ':'
2637:35: E203 whitespace before ':'
2638:39: E203 whitespace before ':'
2639:36: E203 whitespace before ':'
2640:33: E203 whitespace before ':'
2647:29: E126 continuation line over-indented for hanging indent
2647:40: E203 whitespace before ':'
2648:42: E203 whitespace before ':'
2661:29: E126 continuation line over-indented for hanging indent
2661:40: E203 whitespace before ':'
2662:42: E203 whitespace before ':'
2663:35: E203 whitespace before ':'
2664:39: E203 whitespace before ':'
2665:36: E203 whitespace before ':'
2666:33: E203 whitespace before ':'
2673:29: E126 continuation line over-indented for hanging indent
2673:40: E203 whitespace before ':'
2674:42: E203 whitespace before ':'
2682:25: E126 continuation line over-indented for hanging indent
2682:36: E203 whitespace before ':'
2683:38: E203 whitespace before ':'
2694:1: E302 expected 2 blank lines, found 1
2698:1: E302 expected 2 blank lines, found 1
2698: D401 First line should be in imperative mood ('Return', not 'Returns')
2698: D209 Multi-line docstring closing quotes should be on a separate line
2698: D202 No blank lines allowed after function docstring (found 1)
2698: D400 First line should end with a period (not 'n')
2698: D205 1 blank line required between summary line and description (found 0)
2718:17: F841 local variable 'score' is assigned to but never used
2732:29: F841 local variable 'e' is assigned to but never used
2736:1: E302 expected 2 blank lines, found 1
2736: D209 Multi-line docstring closing quotes should be on a separate line
2736: D202 No blank lines allowed after function docstring (found 1)
2736: D400 First line should end with a period (not ')')
2736: D205 1 blank line required between summary line and description (found 0)
2755:1: E302 expected 2 blank lines, found 1
2755: D202 No blank lines allowed after function docstring (found 1)
2755: D400 First line should end with a period (not 's')
2760:1: E302 expected 2 blank lines, found 1
2760:31: E251 unexpected spaces around keyword / parameter equals
2760:33: E251 unexpected spaces around keyword / parameter equals
2760: D401 First line should be in imperative mood ('Return', not 'Returns')
2760: D209 Multi-line docstring closing quotes should be on a separate line
2760: D202 No blank lines allowed after function docstring (found 1)
2760: D205 1 blank line required between summary line and description (found 0)
2781:1: E302 expected 2 blank lines, found 1
2781:42: E251 unexpected spaces around keyword / parameter equals
2781:44: E251 unexpected spaces around keyword / parameter equals
2781: D401 First line should be in imperative mood ('Return', not 'Returns')
2781: D209 Multi-line docstring closing quotes should be on a separate line
2781: D202 No blank lines allowed after function docstring (found 1)
2781: D205 1 blank line required between summary line and description (found 0)
2802:1: E302 expected 2 blank lines, found 1
2802: D401 First line should be in imperative mood ('Return', not 'Returns')
2802: D209 Multi-line docstring closing quotes should be on a separate line
2802: D202 No blank lines allowed after function docstring (found 1)
2802: D400 First line should end with a period (not 'n')
2802: D205 1 blank line required between summary line and description (found 0)
2812:1: E302 expected 2 blank lines, found 1
2812: D210 No whitespaces allowed surrounding docstring text
2812: D401 First line should be in imperative mood ('Return', not 'Returns')
2812: D209 Multi-line docstring closing quotes should be on a separate line
2812: D202 No blank lines allowed after function docstring (found 1)
2812: D400 First line should end with a period (not 'o')
2812: D205 1 blank line required between summary line and description (found 0)
2821:29: F841 local variable 'e' is assigned to but never used
2824:1: E302 expected 2 blank lines, found 1
2824: D401 First line should be in imperative mood ('Return', not 'Returns')
2824: D202 No blank lines allowed after function docstring (found 1)
2824: D400 First line should end with a period (not 's')
2830:1: E302 expected 2 blank lines, found 1
2830:25: E251 unexpected spaces around keyword / parameter equals
2830:27: E251 unexpected spaces around keyword / parameter equals
2830: D401 First line should be in imperative mood ('Return', not 'Returns')
2830: D202 No blank lines allowed after function docstring (found 1)
2830: D400 First line should end with a period (not 'e')
2842:1: E302 expected 2 blank lines, found 1
2842: D401 First line should be in imperative mood ('Return', not 'Returns')
2842: D202 No blank lines allowed after function docstring (found 1)
2842: D400 First line should end with a period (not 'x')
2854:1: E302 expected 2 blank lines, found 1
2854: D202 No blank lines allowed after function docstring (found 1)
2854: D400 First line should end with a period (not 's')
2863:1: E302 expected 2 blank lines, found 1
2863: D202 No blank lines allowed after function docstring (found 1)
2863: D400 First line should end with a period (not 's')
2870:1: E302 expected 2 blank lines, found 1
2870: D202 No blank lines allowed after function docstring (found 1)
2870: D400 First line should end with a period (not 's')
2877:1: E302 expected 2 blank lines, found 1
2877: D202 No blank lines allowed after function docstring (found 1)
2877: D400 First line should end with a period (not 's')
2884:1: E302 expected 2 blank lines, found 1
2884: D202 No blank lines allowed after function docstring (found 1)
2884: D400 First line should end with a period (not 'n')
2893:1: E302 expected 2 blank lines, found 1
2893: D202 No blank lines allowed after function docstring (found 1)
2893: D400 First line should end with a period (not 'n')
2902:1: E302 expected 2 blank lines, found 1
2902: D209 Multi-line docstring closing quotes should be on a separate line
2902: D202 No blank lines allowed after function docstring (found 1)
2902: D205 1 blank line required between summary line and description (found 0)
2921:1: E302 expected 2 blank lines, found 1
2921: D209 Multi-line docstring closing quotes should be on a separate line
2921: D202 No blank lines allowed after function docstring (found 1)
2921: D205 1 blank line required between summary line and description (found 0)
2944:1: E302 expected 2 blank lines, found 1
2944: D209 Multi-line docstring closing quotes should be on a separate line
2944: D202 No blank lines allowed after function docstring (found 1)
2944: D400 First line should end with a period (not 'n')
2944: D205 1 blank line required between summary line and description (found 0)
2950:9: F841 local variable 'res' is assigned to but never used
2956:1: E302 expected 2 blank lines, found 1
2956: D209 Multi-line docstring closing quotes should be on a separate line
2956: D202 No blank lines allowed after function docstring (found 1)
2956: D400 First line should end with a period (not 'n')
2956: D205 1 blank line required between summary line and description (found 0)
2962:9: F841 local variable 'res' is assigned to but never used
2968:1: E302 expected 2 blank lines, found 1
2968: D103 Missing docstring in public function
2973:9: F841 local variable 'res' is assigned to but never used
2979:1: E302 expected 2 blank lines, found 1
2979: D209 Multi-line docstring closing quotes should be on a separate line
2979: D202 No blank lines allowed after function docstring (found 1)
2979: D205 1 blank line required between summary line and description (found 0)
3001:1: E302 expected 2 blank lines, found 1
3001: D401 First line should be in imperative mood ('Remove', not 'Removes')
3001: D209 Multi-line docstring closing quotes should be on a separate line
3001: D202 No blank lines allowed after function docstring (found 1)
3001: D205 1 blank line required between summary line and description (found 0)
3008:9: F841 local variable 'res' is assigned to but never used
3014:1: E302 expected 2 blank lines, found 1
3014: D401 First line should be in imperative mood ('Remove', not 'Removes')
3014: D209 Multi-line docstring closing quotes should be on a separate line
3014: D202 No blank lines allowed after function docstring (found 1)
3014: D205 1 blank line required between summary line and description (found 0)
3020:9: F841 local variable 'res' is assigned to but never used
3026:1: E302 expected 2 blank lines, found 1
3026: D401 First line should be in imperative mood ('Remove', not 'Removes')
3026: D209 Multi-line docstring closing quotes should be on a separate line
3026: D202 No blank lines allowed after function docstring (found 1)
3026: D205 1 blank line required between summary line and description (found 0)
3040:9: F841 local variable 'res' is assigned to but never used
3046:1: E302 expected 2 blank lines, found 1
3046: D401 First line should be in imperative mood ('Delete', not 'Deletes')
3046: D209 Multi-line docstring closing quotes should be on a separate line
3046: D202 No blank lines allowed after function docstring (found 1)
3046: D400 First line should end with a period (not 'e')
3046: D205 1 blank line required between summary line and description (found 0)
3052:9: F841 local variable 'res' is assigned to but never used
3058:1: E302 expected 2 blank lines, found 1
3058: D401 First line should be in imperative mood ('Delete', not 'Deletes')
3058: D209 Multi-line docstring closing quotes should be on a separate line
3058: D202 No blank lines allowed after function docstring (found 1)
3058: D400 First line should end with a period (not 'x')
3058: D205 1 blank line required between summary line and description (found 0)
3064:9: F841 local variable 'res' is assigned to but never used
3070:1: E302 expected 2 blank lines, found 1
3070: D401 First line should be in imperative mood ('Delete', not 'Deletes')
3070: D209 Multi-line docstring closing quotes should be on a separate line
3070: D202 No blank lines allowed after function docstring (found 1)
3070: D400 First line should end with a period (not 't')
3070: D205 1 blank line required between summary line and description (found 0)
3077:9: F841 local variable 'res' is assigned to but never used
3083:1: E302 expected 2 blank lines, found 1
3083: D401 First line should be in imperative mood ('Delete', not 'Deletes')
3083: D209 Multi-line docstring closing quotes should be on a separate line
3083: D202 No blank lines allowed after function docstring (found 1)
3083: D400 First line should end with a period (not 'n')
3083: D205 1 blank line required between summary line and description (found 0)
3095:9: F841 local variable 'res' is assigned to but never used
3101:1: E302 expected 2 blank lines, found 1
3101: D209 Multi-line docstring closing quotes should be on a separate line
3101: D202 No blank lines allowed after function docstring (found 1)
3101: D205 1 blank line required between summary line and description (found 0)
3110:9: F841 local variable 'res' is assigned to but never used
3117:1: E302 expected 2 blank lines, found 1
3117: D209 Multi-line docstring closing quotes should be on a separate line
3117: D202 No blank lines allowed after function docstring (found 1)
3117: D400 First line should end with a period (not 'e')
3117: D205 1 blank line required between summary line and description (found 0)
3125:9: F841 local variable 'res' is assigned to but never used
3131:1: E302 expected 2 blank lines, found 1
3131: D209 Multi-line docstring closing quotes should be on a separate line
3131: D202 No blank lines allowed after function docstring (found 1)
3131: D400 First line should end with a period (not 'e')
3131: D205 1 blank line required between summary line and description (found 0)
3149:1: E302 expected 2 blank lines, found 1
3149: D103 Missing docstring in public function
3161:1: E302 expected 2 blank lines, found 1
3161: D401 First line should be in imperative mood ('Add', not 'Adds')
3161: D209 Multi-line docstring closing quotes should be on a separate line
3161: D400 First line should end with a period (not 'e')
3161: D205 1 blank line required between summary line and description (found 0)
3173:35: E231 missing whitespace after ','
3176:35: E231 missing whitespace after ','
3178:9: F841 local variable 'res' is assigned to but never used
3188:1: E302 expected 2 blank lines, found 1
3188: D209 Multi-line docstring closing quotes should be on a separate line
3188: D202 No blank lines allowed after function docstring (found 1)
3188: D205 1 blank line required between summary line and description (found 0)
3211:1: E302 expected 2 blank lines, found 1
3211: D209 Multi-line docstring closing quotes should be on a separate line
3211: D202 No blank lines allowed after function docstring (found 1)
3211: D205 1 blank line required between summary line and description (found 0)
3232:1: E302 expected 2 blank lines, found 1
3232: D209 Multi-line docstring closing quotes should be on a separate line
3232: D202 No blank lines allowed after function docstring (found 1)
3232: D205 1 blank line required between summary line and description (found 0)
3272:1: E302 expected 2 blank lines, found 1
3272: D209 Multi-line docstring closing quotes should be on a separate line
3272: D205 1 blank line required between summary line and description (found 0)
3280:9: F841 local variable 'res' is assigned to but never used
3286:1: E302 expected 2 blank lines, found 1
3286: D209 Multi-line docstring closing quotes should be on a separate line
3286: D202 No blank lines allowed after function docstring (found 1)
3286: D400 First line should end with a period (not 'x')
3286: D205 1 blank line required between summary line and description (found 0)
3304:13: F841 local variable 'res' is assigned to but never used
3310:1: E302 expected 2 blank lines, found 1
3310: D209 Multi-line docstring closing quotes should be on a separate line
3310: D202 No blank lines allowed after function docstring (found 1)
3310: D400 First line should end with a period (not 'e')
3310: D205 1 blank line required between summary line and description (found 0)
3323:13: F841 local variable 'res' is assigned to but never used
3329:1: E302 expected 2 blank lines, found 1
3329: D209 Multi-line docstring closing quotes should be on a separate line
3329: D202 No blank lines allowed after function docstring (found 1)
3329: D400 First line should end with a period (not 'e')
3329: D205 1 blank line required between summary line and description (found 0)
3342:13: F841 local variable 'res' is assigned to but never used
3348:1: E302 expected 2 blank lines, found 1
3348: D209 Multi-line docstring closing quotes should be on a separate line
3348: D202 No blank lines allowed after function docstring (found 1)
3348: D205 1 blank line required between summary line and description (found 0)
3360:9: F841 local variable 'res' is assigned to but never used
3366:1: E302 expected 2 blank lines, found 1
3366: D209 Multi-line docstring closing quotes should be on a separate line
3366: D202 No blank lines allowed after function docstring (found 1)
3366: D205 1 blank line required between summary line and description (found 0)
3378:9: F841 local variable 'res' is assigned to but never used
3384:1: E302 expected 2 blank lines, found 1
3384: D401 First line should be in imperative mood ('Return', not 'Returns')
3384: D400 First line should end with a period (not 'e')
3384: D205 1 blank line required between summary line and description (found 0)
3402:24: E203 whitespace before ':'
3404:24: E203 whitespace before ':'
3405:24: E203 whitespace before ':'
3406:24: E203 whitespace before ':'
3407:24: E203 whitespace before ':'
3408:24: E203 whitespace before ':'
3409:24: E203 whitespace before ':'
3410:24: E203 whitespace before ':'
3411:24: E203 whitespace before ':'
3414:74: E502 the backslash is redundant between brackets
3421:50: E703 statement ends with a semicolon
3444:9: E266 too many leading '#' for block comment
3445:9: E266 too many leading '#' for block comment
3446:9: E266 too many leading '#' for block comment
3447:9: E266 too many leading '#' for block comment
3448:9: E266 too many leading '#' for block comment
3449:9: E266 too many leading '#' for block comment
3454:9: E266 too many leading '#' for block comment
3455:9: E266 too many leading '#' for block comment
3456:9: E266 too many leading '#' for block comment
3457:9: E266 too many leading '#' for block comment
3464:25: E261 at least two spaces before inline comment
3466:41: E713 test for membership should be 'not in'
3477:14: E222 multiple spaces after operator
3493: D401 First line should be in imperative mood ('Return', not 'Returns')
3493: D202 No blank lines allowed after function docstring (found 1)
3493: D400 First line should end with a period (not 's')
3493: D205 1 blank line required between summary line and description (found 0)
3506:21: E261 at least two spaces before inline comment
3506:22: E262 inline comment should start with '# '
3507:20: E261 at least two spaces before inline comment
3507:21: E262 inline comment should start with '# '
3508:33: E203 whitespace before ':'
3509:33: E203 whitespace before ':'
3510:33: E203 whitespace before ':'
3511:30: E203 whitespace before ':'
3512:29: E203 whitespace before ':'
3523:26: E261 at least two spaces before inline comment
3523:26: E262 inline comment should start with '# '


1: D210 No whitespaces allowed surrounding docstring text
1: D400 First line should end with a period (not 's')
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import math should be before import time
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. import cgi should be before import shutil
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: I201 Missing newline before sections or imports.
32:1: E402 module level import not at top of file
36:1: I101 Imported names are in the wrong order. Should be datetime_format, run_sql
36:1: I100 Imports statements are in the wrong order. from invenio.legacy.dbquery should be before from six
36:1: E402 module level import not at top of file
37:1: I101 Imported names are in the wrong order. Should be CFG_COMMENTSDIR, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_RECORD, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBALERT_ALERT_ENGINE_EMAIL, CFG_WEBCOMMENT_ADMIN_NOTIFICATION_LEVEL, CFG_WEBCOMMENT_ALERT_ENGINE_EMAIL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_ALLOW_SHORT_REVIEWS, CFG_WEBCOMMENT_DEFAULT_MODERATOR, CFG_WEBCOMMENT_EMAIL_REPLIES_TO, CFG_WEBCOMMENT_MAX_COMMENT_THREAD_DEPTH, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_RESTRICTION_DATAFIELD, CFG_WEBCOMMENT_ROUND_DATAFIELD, CFG_WEBCOMMENT_TIMELIMIT_PROCESSING_COMMENTS_IN_SECONDS
37:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.dbquery
37:1: E402 module level import not at top of file
56:1: E402 module level import not at top of file
59:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.mail
59:1: E402 module level import not at top of file
60:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info
60:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.html
60:1: E402 module level import not at top of file
61:1: I101 Imported names are in the wrong order. Should be convert_datestruct_to_datetext, convert_datetext_to_dategui, datetext_default
61:1: E402 module level import not at top of file
62:29: E126 continuation line over-indented for hanging indent
64:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.utils.date
64:1: E402 module level import not at top of file
65:1: E402 module level import not at top of file
66:1: I101 Imported names are in the wrong order. Should be gettext_set_language, wash_language
66:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.ext.logging
66:1: E402 module level import not at top of file
67:1: E402 module level import not at top of file
68:1: I201 Missing newline before sections or imports.
68:1: E402 module level import not at top of file
71:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from .config
71:1: E402 module level import not at top of file
72:1: E402 module level import not at top of file
73:1: I101 Imported names are in the wrong order. Should be check_user_can_view_record, guess_primary_collection_of_a_record
73:1: I100 Imports statements are in the wrong order. from invenio.legacy.search_engine should be before from invenio.modules.access.models
73:1: E402 module level import not at top of file
76:1: E402 module level import not at top of file
77:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.collections.cache
77:1: E402 module level import not at top of file
78:1: E402 module level import not at top of file
82:1: B901 blind except: statement
86: D401 First line should be in imperative mood ('Return', not 'Returns')
86: D205 1 blank line required between summary line and description (found 0)
141:29: E271 multiple spaces after keyword
229:33: E261 at least two spaces before inline comment
230:15: E271 multiple spaces after keyword
231:49: E203 whitespace before ':'
233:49: E203 whitespace before ':'
233:51: E202 whitespace before ']'
234:14: E261 at least two spaces before inline comment
248:79: E261 at least two spaces before inline comment
255:8: E114 indentation is not a multiple of four (comment)
334:84: E502 the backslash is redundant between brackets
334:84: E251 unexpected spaces around keyword / parameter equals
336:88: E502 the backslash is redundant between brackets
336:88: E251 unexpected spaces around keyword / parameter equals
341:1: E302 expected 2 blank lines, found 1
341: D400 First line should end with a period (not 'w')
341: D205 1 blank line required between summary line and description (found 0)
367:1: E302 expected 2 blank lines, found 1
367: D210 No whitespaces allowed surrounding docstring text
367: D400 First line should end with a period (not 's')
367: D205 1 blank line required between summary line and description (found 0)
396:1: E302 expected 2 blank lines, found 1
396: D210 No whitespaces allowed surrounding docstring text
396: D400 First line should end with a period (not 's')
396: D205 1 blank line required between summary line and description (found 0)
419:1: E302 expected 2 blank lines, found 1
419: D210 No whitespaces allowed surrounding docstring text
419: D401 First line should be in imperative mood ('Check', not 'Checks')
419: D400 First line should end with a period (not 'd')
419: D205 1 blank line required between summary line and description (found 0)
441:1: E302 expected 2 blank lines, found 1
441: D400 First line should end with a period (not 'n')
441: D200 One-line docstring should fit on one line with quotes (found 3)
450:1: E302 expected 2 blank lines, found 1
450: D200 One-line docstring should fit on one line with quotes (found 3)
456:10: E222 multiple spaces after operator
458:49: E231 missing whitespace after ','
461:1: E302 expected 2 blank lines, found 1
461: D205 1 blank line required between summary line and description (found 0)
525:17: E127 continuation line over-indented for visual indent
525:18: E201 whitespace after '{'
525:44: E203 whitespace before ':'
526:44: E203 whitespace before ':'
527:44: E203 whitespace before ':'
528:44: E203 whitespace before ':'
529:44: E203 whitespace before ':'
530:44: E203 whitespace before ':'
531:80: E502 the backslash is redundant between brackets
531:44: E203 whitespace before ':'
532:47: E127 continuation line over-indented for visual indent
532:130: E502 the backslash is redundant between brackets
534:44: E203 whitespace before ':'
535:44: E203 whitespace before ':'
536:44: E203 whitespace before ':'
537:44: E203 whitespace before ':'
538:80: E502 the backslash is redundant between brackets
538:44: E203 whitespace before ':'
540:44: E203 whitespace before ':'
541:44: E203 whitespace before ':'
541:65: E225 missing whitespace around operator
541:84: E225 missing whitespace around operator
542:44: E203 whitespace before ':'
542:64: E261 at least two spaces before inline comment
542:65: E262 inline comment should start with '# '
543:17: E124 closing bracket does not match visual indentation
551:1: E302 expected 2 blank lines, found 1
551: D210 No whitespaces allowed surrounding docstring text
551: D401 First line should be in imperative mood ('Check', not 'Checks')
551: D400 First line should end with a period (not 't')
551: D205 1 blank line required between summary line and description (found 0)
573:1: E302 expected 2 blank lines, found 1
573: D400 First line should end with a period (not 'n')
573: D205 1 blank line required between summary line and description (found 0)
582:28: E127 continuation line over-indented for visual indent
583:24: E127 continuation line over-indented for visual indent
593: D400 First line should end with a period (not 'r')
593: D205 1 blank line required between summary line and description (found 0)
616:1: E302 expected 2 blank lines, found 1
616: D400 First line should end with a period (not 't')
616: D205 1 blank line required between summary line and description (found 0)
628:28: E127 continuation line over-indented for visual indent
629:24: E127 continuation line over-indented for visual indent
641:17: E225 missing whitespace around operator
646:1: E302 expected 2 blank lines, found 1
646: D400 First line should end with a period (not 't')
646: D205 1 blank line required between summary line and description (found 0)
667:1: E302 expected 2 blank lines, found 1
667: D400 First line should end with a period (not 'n')
667: D205 1 blank line required between summary line and description (found 0)
679:17: E225 missing whitespace around operator
692:1: E302 expected 2 blank lines, found 1
692: D400 First line should end with a period (not 'n')
692: D205 1 blank line required between summary line and description (found 0)
714:22: E201 whitespace after '{'
714:31: E203 whitespace before ':'
714:17: E222 multiple spaces after operator
715:31: E203 whitespace before ':'
716:31: E203 whitespace before ':'
717:31: E203 whitespace before ':'
718:31: E203 whitespace before ':'
719:31: E203 whitespace before ':'
720:21: E124 closing bracket does not match visual indentation
726:9: B901 blind except: statement
736:5: B901 blind except: statement
743:24: E127 continuation line over-indented for visual indent
744:24: E127 continuation line over-indented for visual indent
758:38: E203 whitespace before ':'
759:23: E122 continuation line missing indentation or outdented
759:38: E203 whitespace before ':'
760:1: E128 continuation line under-indented for visual indent
761:1: E128 continuation line under-indented for visual indent
762:23: E122 continuation line missing indentation or outdented
762:38: E203 whitespace before ':'
763:16: E128 continuation line under-indented for visual indent
764:16: E128 continuation line under-indented for visual indent
833:1: E302 expected 2 blank lines, found 1
833: D401 First line should be in imperative mood ('Return', not 'Returns')
833: D400 First line should end with a period (not 'm')
833: D205 1 blank line required between summary line and description (found 0)
865:1: E302 expected 2 blank lines, found 1
865: D400 First line should end with a period (not 'o')
865: D205 1 blank line required between summary line and description (found 0)
873:1: E302 expected 2 blank lines, found 1
873: D400 First line should end with a period (not 'n')
873: D205 1 blank line required between summary line and description (found 0)
983: D400 First line should end with a period (not 'd')
983: D205 1 blank line required between summary line and description (found 0)
994:35: E127 continuation line over-indented for visual indent
1012:1: E302 expected 2 blank lines, found 1
1012: D400 First line should end with a period (not 'r')
1012: D205 1 blank line required between summary line and description (found 0)
1027:9: B901 blind except: statement
1033:1: E302 expected 2 blank lines, found 1
1033: D401 First line should be in imperative mood ('Return', not 'Returns')
1033: D400 First line should end with a period (not ')')
1045:134: E502 the backslash is redundant between brackets
1045:36: E225 missing whitespace around operator
1045:55: E225 missing whitespace around operator
1050:1: E302 expected 2 blank lines, found 1
1050: D400 First line should end with a period (not 's')
1050: D205 1 blank line required between summary line and description (found 0)
1064:5: B901 blind except: statement
1068:1: E302 expected 2 blank lines, found 1
1082:5: B901 blind except: statement
1088:1: E302 expected 2 blank lines, found 1
1088: D401 First line should be in imperative mood ('Return', not 'Returns')
1088: D400 First line should end with a period (not 's')
1088: D205 1 blank line required between summary line and description (found 0)
1110:1: E302 expected 2 blank lines, found 1
1110: D401 First line should be in imperative mood ('Return', not 'Returns')
1158:24: E713 test for membership should be 'not in'
1160:58: E502 the backslash is redundant between brackets
1165:49: E502 the backslash is redundant between brackets
1167:49: E502 the backslash is redundant between brackets
1168:72: E202 whitespace before ')'
1170:1: E302 expected 2 blank lines, found 1
1170: D205 1 blank line required between summary line and description (found 0)
1217:25: E126 continuation line over-indented for hanging indent
1221:25: E126 continuation line over-indented for hanging indent
1288:1: E302 expected 2 blank lines, found 1
1288: D401 First line should be in imperative mood ('Return', not 'Returns')
1288: D400 First line should end with a period (not 'd')
1288: D205 1 blank line required between summary line and description (found 0)
1327:1: E302 expected 2 blank lines, found 1
1327: D400 First line should end with a period (not 'n')
1327: D205 1 blank line required between summary line and description (found 0)
1346:22: E231 missing whitespace after ':'
1346:29: E231 missing whitespace after ':'
1346:36: E231 missing whitespace after ':'
1346:43: E231 missing whitespace after ':'
1350:5: B901 blind except: statement
1389:1: E302 expected 2 blank lines, found 1
1389: D401 First line should be in imperative mood ('Get', not 'Gets')
1389: D205 1 blank line required between summary line and description (found 0)
1415:5: E266 too many leading '#' for block comment
1418:19: E261 at least two spaces before inline comment
1418:20: E262 inline comment should start with '# '
1423:13: E266 too many leading '#' for block comment
1432:13: E266 too many leading '#' for block comment
1437:10: E261 at least two spaces before inline comment
1437:11: E262 inline comment should start with '# '
1463:42: E261 at least two spaces before inline comment
1467:45: E261 at least two spaces before inline comment
1491:1: E302 expected 2 blank lines, found 1
1491: D400 First line should end with a period (not 'g')
1491: D200 One-line docstring should fit on one line with quotes (found 3)
1503:70: E502 the backslash is redundant between brackets
1504:17: F812 list comprehension redefines 'comment_round_name' from line 1498
1506:1: E302 expected 2 blank lines, found 1
1506: D400 First line should end with a period (not 'n')
1506: D205 1 blank line required between summary line and description (found 0)
1520:21: E222 multiple spaces after operator
1534:1: E302 expected 2 blank lines, found 1
1534: D400 First line should end with a period (not 'k')
1534: D205 1 blank line required between summary line and description (found 0)
1580:5: F841 local variable 'actions' is assigned to but never used
1583:5: E266 too many leading '#' for block comment
1637:67: E225 missing whitespace around operator
1764:1: E302 expected 2 blank lines, found 1
1764: D401 First line should be in imperative mood ('Send', not 'Sends')
1764: D400 First line should end with a period (not 'D')
1764: D200 One-line docstring should fit on one line with quotes (found 3)
1786:28: F841 local variable 'last_login' is assigned to but never used
1795:5: B901 blind except: statement
1822:10: E201 whitespace after '{'
1822:36: E203 whitespace before ':'
1822:51: E222 multiple spaces after operator
1824:36: E203 whitespace before ':'
1824:51: E222 multiple spaces after operator
1825:36: E203 whitespace before ':'
1826:36: E203 whitespace before ':'
1827:36: E203 whitespace before ':'
1828:36: E203 whitespace before ':'
1829:36: E203 whitespace before ':'
1830:36: E203 whitespace before ':'
1831:36: E203 whitespace before ':'
1832:36: E203 whitespace before ':'
1833:36: E203 whitespace before ':'
1833:60: E231 missing whitespace after ','
1834:36: E203 whitespace before ':'
1835:37: E203 whitespace before ':'
1836:36: E203 whitespace before ':'
1837:9: E124 closing bracket does not match visual indentation
1851:1: E302 expected 2 blank lines, found 1
1851: D400 First line should end with a period (not '0')
1851: D205 1 blank line required between summary line and description (found 0)
1863:5: B901 blind except: statement
1871:26: E231 missing whitespace after ','
1910:1: E302 expected 2 blank lines, found 1
1910: D202 No blank lines allowed after function docstring (found 1)
1910: D400 First line should end with a period (not 'e')
1910: D205 1 blank line required between summary line and description (found 0)
1952:1: E302 expected 2 blank lines, found 1
1952: D401 First line should be in imperative mood ('Return', not 'Returns')
1952: D400 First line should end with a period (not 'e')
1952: D205 1 blank line required between summary line and description (found 0)
1971:1: E302 expected 2 blank lines, found 1
1971: D400 First line should end with a period (not 'n')
1971: D205 1 blank line required between summary line and description (found 0)
1983:5: E266 too many leading '#' for block comment
1984:5: E266 too many leading '#' for block comment
1988:1: E302 expected 2 blank lines, found 1
1988: D400 First line should end with a period (not ',')
1988: D205 1 blank line required between summary line and description (found 0)
2009:15: E271 multiple spaces after keyword
2012:1: E302 expected 2 blank lines, found 1
2012: D400 First line should end with a period (not 'n')
2012: D205 1 blank line required between summary line and description (found 0)
2019:5: E266 too many leading '#' for block comment
2023:1: E302 expected 2 blank lines, found 1
2023: D400 First line should end with a period (not 'e')
2023: D205 1 blank line required between summary line and description (found 0)
2039:1: E302 expected 2 blank lines, found 1
2039: D400 First line should end with a period (not 's')
2039: D205 1 blank line required between summary line and description (found 0)
2046:5: E266 too many leading '#' for block comment
2047:5: E266 too many leading '#' for block comment
2051:1: E302 expected 2 blank lines, found 1
2051: D400 First line should end with a period (not 'e')
2051: D205 1 blank line required between summary line and description (found 0)
2094:1: E302 expected 2 blank lines, found 1
2094: D400 First line should end with a period (not 'e')
2094: D200 One-line docstring should fit on one line with quotes (found 3)
2106:1: E302 expected 2 blank lines, found 1
2106: D400 First line should end with a period (not 'e')
2120:1: E302 expected 2 blank lines, found 1
2155:120: E502 the backslash is redundant between brackets
2159:141: E502 the backslash is redundant between brackets
2162:131: E502 the backslash is redundant between brackets
2168:12: E127 continuation line over-indented for visual indent
2195:5: E303 too many blank lines (2)


This is part of the internal tizebraprint.xcodeproj file... I don't think it hurts anything to be here, but we can take it out if you want. That said, there's lots of other similar files that reference my user preferences for xcode, too.


I edited the makefile again, it works now ?


You can have a look at e.g. https://raw.githubusercontent.com/openhab/openhab2/master/targetplatform/openHAB2.setup
That should set it already.


I think, but unsure it break https://manual.limesurvey.org/Cron .

I doidn't use it (a own controller in same directory is not replaced by auto update but ... ;) )


@lynicidn maybe indicate extension?

For example :

imagine (provided by yii2-imagine extension)


+1 For the fix, but the unexplained question is: why is this delay needed at all? What does it prevent?


Because `auto-updater` and `autoconfig` are mutually recursive dependencies, we can't use `require('auto-updater').check()` in the first event loop tick.  It's just an empty exports table at that time since `autoconfig` is generally required first.


Is it not better to comment out the rest of the method, since you are returning a value in the first line.


Thanks, Tim!


Yeah but s is a common shortcut on a lot of sites too so I don't think it hurts.


you were faster than me :dancer:


3 almost the same blocks in a row - should be combined and used as function


Read the comments under the other commit.


Would make sense to add an `sol_arena` to builder? I remember doing it locally but there were not much use yet, now it seems there is.


Committed my change too. What's left now?


The `chaine` executable is not generated.


Fixed.


Why assign a temp var here ?


It would be `isCheckboxChecked`, not `get`.


@cfitz - nice catch. If this causes any side effects it might work just as well to clear the array after this line:
https://github.com/archivesspace/archivesspace/blob/81ef749fe2875f740c95799c8c6625200b7bdcce/frontend/app/assets/javascripts/tree.js.erb#L1181


I was referring to the name of the constant.


Needs an empty line after the label line. Sorry if my comment was not precise.
[Fails for me with `.../numpy_images.txt:134: WARNING: Explicit markup ends without a blank line; unexpected unindent.`]


There is one and this has been changed to use it, I just didn't push the rebased version after that.


Typo: available


Opps, sorry. forgot to paste:

cf_client.go: 172-173

I'm wondering if it should be more like line 40.


@alco and I had fun coming up with this. Any ideas how to improve it @josevalim? The problem is that in `before_compile` it's too late to make `__pool__` overridable.


When working with CAS vars, read them only once


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.702.1f5ad18c2bd2ded0d73fab9afe899b322e93fed3](http://build.palaso.org/viewLog.html?buildId=59100&buildTypeId=bt431) outcome was **FAILURE**
Summary: Tests failed: 3 (3 new), passed: 356, ignored: 3 Build time: 00:01:53
### Failed tests
```
GlyssenTests.dll: GlyssenTests.Character.CharacterGroupTemplateExcelFileTests.GetTemplate_1Actor_1Group: <no details avaliable>

GlyssenTests.dll: GlyssenTests.Character.CharacterGroupTemplateExcelFileTests.GetTemplate_28Actors_28Groups: <no details avaliable>

GlyssenTests.dll: GlyssenTests.Character.CharacterGroupTemplateExcelFileTests.GetTemplate_GroupContainsCharacter: <no details avaliable>

```


I believe the bootstrap script also needs to support proxy. Also how do one configures the proxy server?

The ideal would be getting the information from http_proxy and https_proxy environment variables.
Maybe implement something like this:
```
get_proxy(ProxyType) ->
    case os:getenv(ProxyType) of
        false ->
            false;
        Proxy ->
            {ok,   {_, _, Host, Port, _, _}} = http_uri:parse(Proxy),
            {ok, Host, Port}
    end.
```


add `white-space: nowrap;` here to prevent alignment bug : see 56d7879cecde5a6c01b8e22721ef691f520775ce


Good idea. Done.


Cheers ears


Hey, glad you're working on this, I already sank dozens of hours into research into this and I still haven't figured the best way to detect encoding in random strings.

The approach you are taking is fine if the user knows what he is doing, I should make the `$charEncodings` option available again - with the safe-ish defaults that are now `$_supportedCharsets`. I removed it because I thought it would be too advanced to allow the users to define their own strings as I have yet to find a way to differentiate charsets safely - if the user puts in wrong ones, the charset will be incorrectly recognized - and values might be poorly escaped leading to possible exploits.

Could you tell me about what is your experience in this field, cause it seems you know what you're doing..


We can eventually just use https://github.com/babel/babel/blob/master/src/babel/types/visitor-keys.json after adding es6 then?


This commit broke the parallax background image on iPhone :(


Get list of owned resource ids.


lodash's documentation does not make leading and trailing clear to me.  That, and they seem mutually exclusive.  What a goofy API! :scream:


HBIRE_vector_take2 (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1674 of 1676 tests passed)

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


Good catch. I didn't actually test that hook type.


This error message should read "Cannot run command from the EDT!"


I screwed this up on the comparison matrix. There's no maintenance mode for bare metal.


These checks are the same as those in `runMacro(String)`. For DRYness, should refactor into a common private `configureThread` method or similar.


You can't mix non atomic ops with atomics ops.

Use a store_release operation here.

Or, even better, a CAS that faults if the original state was not the expected one.


Same thing, read the var only once.


Looks good


Hmm, yes, but I think it's more than that. Basically I can't find any way to get the compiler to accept that approach (with a third line or not) unless the array being passed in has a compile time known size. Maybe I'm not finding the syntax but I've tried everything.

If you're interested you can take the mainline branch and make the change, try it under Xcode (gcc/LLVM) and maybe you'll have better luck.


Not for this PR, but in the future we probably need to pass information to this method.  Possibly we can make it a simple collection of name/value pairs that got deserialized by the Bridge.


Oh, wow, sorry, you're right. My brain miscounted the brackets.

One thing that concerns me with this though is that if someone tries to load multiple distinct VAST files, their callbacks will now interfere with one another, and if there's an error in the second VAST, the *first* callback will be fired. It might be better to instead add another argument to `queryVAST` (`onError` for example), and then pass that down the chain (i.e. to `new VASTAds`). This will still preserve the error propagation you are after, but also be safe for concurrent use.

Another problem with this approach is that the user's callback will be called if *any* child returns an error. It could be that the VAST file has multiple wrappers, and one of them containing no ads should *not* be reported as an error to the user. I think a better way to implement this feature would be to have code run after all nested `VASTAds` elements have loaded, and if there are then no ads, call `onAdsAvailable(null)`. This will then propagate up through nested `VASTAds`, all the way up to the user's `onFetched`.


We're already using that actually! The issue is when a file doesn't require react at all explicitly. Only when it's implicitly through JSX


Bool functions that check state are named with the is verb.
mono_lazy_is_....


Csv is not a good name for model.
In your case it should be Product - and `products` table in DB


:cake:


for future code maintainability, consider passing in `enrolled_course_overviews_dict` instead of just the names of the courses.


you're right. i don't know what happening, but the original stacktrce loss is sure. my code is similar to this:
code.js
var extModule=require('./extmodule')
var variable=extModule.prop1.prop2;
...
module.exports=function(){...}

test.js:
var requires={'./extmodule':{}}//not set the prop1 property
var codeToTest=sandboxedModule('code.js',{requires:requires})//require and mock the external module
codeToTest();


@mikeNG it's better do remove everything. I saw things my eye shouldn't have seen :P


Hello,

I think this is a problem with the terminal emulator. In gnome-terminal I get the weird behavior while in urxvt I do not.  Instead of modifying the theme I just added
```
# add indent to make it work in gnome-terminal...
export ZLE_RPROMPT_INDENT=1
```
after loading the theme in my `.zshrc`.  Probably an even better approach (in my case) would be to only do it in the gnome-terminal environment.


I created a seperated folder wich contrains all my source code and the CMakeList.txt .I have created a 'built' folder and run the Cmake command.It´s worked well.Now I have to git push all that


Initialize/cleanup are too nondescriptive names here.


Hm, I guess that's not very helpful for Neovim users. Change to `nvim -d`?


Please, rename `csvs` to `products`


Could you use the base URL stored in the package?


Please do not.
Add your target in the same CMakeLists.txt
And do not push your build directory.


If you add the arena, it seems this one is another potential user.


HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM


>This currently prevents us from running ilastik from a fresh conda checkout/update, as we do not fix a version of h5py

Yeah, the old spec `hdf5 >=1.8.14` was a bug in this `meta.yaml` file. (It turns out that hdf5 1.8.15 is not compatible with libraries that were compiled against hdf5 1.8.15.)  Because of this bug, conda has the following options when resolving dependencies:

    vigra=1.1.0=7_5dde887, hdf5=1.8.14, h5py=2.5.0=np19py27_2
    vigra=1.1.0=7_5dde887, hdf5=1.8.15, h5py=2.5.0=np19py27_3  <-- Broken. Allowed by `hdf5 >=1.8.14` spec, but will not work.
    vigra=1.1.0=8_5dde887, hdf5=1.8.14, h5py=2.5.0=np19py27_2

Ideally, we would simply require a particular **build** of `vigra` and/or `h5py` and/or `hdf5` instead of merely listing the version.  But unfortunately, we can't use explicit build string requirements in any `meta.yaml` files due to conda/conda#918. Right now, the only way to fix our problem is to make sure that conda can't see the `7_5dde887` vigra build any more, by removing it from binstar entirely.  I've removed the old version from the `ilastik` channel and (just now) removed it from the `stuarteberg` channel.  Are you picking it up from your own channel?

>Is there a solid reason for not using the newer HDF version in vigra/opengm/itk?

No, we can upgrade all hdf5-dependent packages if we need to.  Hopefully in the future we won't be forced to rebuild several packages every time Anaconda upgrades one of its packages.


@Dr15Jones  It is actually a new class -- see previous commit: https://github.com/cms-sw/cmssw/commit/5f9442183be9046ab0c3d47382bc49631ef5a642
I can change the name to ScoutingParticle if it will be clearer.


Potential NPE when no authentication exists


Nevermind, I got the code wrong.


This is not possible because I manually add the zero. Nonetheless a bad idea to have new random numbers each time so I added a seed.


Екстра е фикса, много ми харесва


The more general way to override a default service is, unfortunately, slightly more complex. [Here](https://github.com/scifio/scifio/blob/scifio-0.24.0/src/main/java/io/scif/services/SCIFIODatasetService.java#L228-L243) is an example from SCIFIO that overrides the `DefaultDatasetService` but then leans on the overridden instance to do the work of most (but not all) methods. This pattern accommodates theoretical situations where multiple components attempt to override the same service and only one of them can "win"—with this pattern, several such services can limitedly coexist and cooperate, whereas with a direct override they stomp each other.

I'm not necessarily suggesting we have to do this here—just wanted to bring it to your attention as a possible weakness of the design.


The code below will be fixed in the next PR.


Hi Loic,

thanks! If they are "local DBS samples" I assume DBS knows about them: do you have any example, so that I can check straight away? With all the SM samples I have in my json, the hack works fine.

By the way: the MVA ID for electron came out:
https://hypernews.cern.ch/HyperNews/CMS/get/egamma/1589.html
As you can see, as a basis they provide the output of the MVAs, but leave the choice of cut to the analyses.

How do we do that? Each of us adds a cut of his choice in the PatUtills electronID method, or we sit and see if we can perhaps use a common set of working points?

Cheers,
Pietro


@saintedlama that's my fault. It comes from my npm publish procedure where I use [geopkg](https://github.com/watson/geopkg) to tag all modules I release with the geo coordinates where I were when I released it :satellite: :stuck_out_tongue_winking_eye: - Feel free to remove it if you don't like it :smiley:


@pana1990  i don't know, need ask core developers


Calling `getContext().dispose()` doesn't do the job, eh? Too bad.


Thanks @sunheehnus! I figured that you didn't changed the code like me in order to avoid messing with the exported API. Sane thing to provide a PR for a fix in the most minimalistic fashion as you did. However I understand what limited you in reusing the code and tried to fix it. Cheers.


Why a promise? It doesn't make too much sense to me. There is nothing async in here :S


Does this work recursively or does it search only one level down?


fish 2.1.2 was a bugfix release only. The new code is in the upcoming 2.2 release.


Ok


Why did you use Ukrainian language instead of English in git commit messages? :scream_cat:
/play noooo


Done already.


I don't know much about Node.js or what this app is doing underneath, but I think it is probably running in one process so this check is unnecessary.


sure


That's already been fixed.


Can just the query parameter be used here? instead of pasting "fields" onto the URL.


FacilityTabGridView (evanweaver) - x86_64-MacOS-10.9-clang: Tests Failed

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


hmmm, ar not support configure


unrelevant => irrelevant ?

[Statisker] => [Statistiker], same missing "ti" later


And can this be in a separate file? (I'm a personal fan of when functions have their own file, there is some cleanup to do in this package).


My intuition is that there is a much better way to deal with the problem this commit, and the previous one, are trying to solve. The case logic here concerns me—it is very "ImageJ1"-ish and will probably bite us later somehow.

But unfortunately I do not immediately see a more proper solution. So I guess we can fix it later as needed.


Is correct to say: "And there's no need to copy it because the original options for the node is owned by the builder."?

Minor: if so, complement the comment with this.


website should already have a cheerio object with the content loaded in the property `$`. We can probably change the signature of `compareMarkup` to receive directly the cheerio objects and load in this test only the one for chrome.


Err, shouldn't that method now be made a class method? (Especially if its now going to be used as an utility method)
Also maybe refactor its name to reflect the new usage? Something like `parse_csv`?


You could use a for loop here?


Why would somebody run Eclipse without the PDE? :wink:

Just added it.


I like this idea, but the problem is that the constants are ran when the plugin is loaded, which means that plugins would have hard time actually hooking into the filter. The definition or the setup_constants() method should be moved to the init() method. Of course, that would mean running tests to make sure that that didn't break anything.


Looks good @EranGabber


I made it slightly more explicit, maybe a middle ground.


make this file comply with https://www.mediawiki.org/wiki/Manual:Coding_conventions/PHP


thanks for the catch. addressed in https://github.com/europeana/Europeana-Patternlab/commit/d0fc68999bd079e191033d8549e060e5a883cc5d


remove commented code


"to work with" => "for working with" ?


hola esto es una mierda