1: D100 Docstring missing
21:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibedit.utils should be before from .backend
21:1: I201 Missing newline before sections or imports.
22:1: I101 Imported names are in the wrong order. Should be create_record, record_get_field_value
25:1: I101 Imported names are in the wrong order. Should be get_record, perform_request_search
26:1: I101 Imported names are in the wrong order. Should be field_get_subfield_values, print_rec, record_add_field, record_get_field_instances
26:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.search_engine
27:31: E126 continuation line over-indented for hanging indent
29:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
30:1: I101 Imported names are in the wrong order. Should be task_init, task_low_level_submission, task_sleep_now_if_required, task_update_progress, write_message
35:1: I100 Imports statements are in the wrong order. import string should be before from invenio.legacy.dbquery
36:1: I100 Imports statements are in the wrong order. import random should be before import string
38:1: I100 Imports statements are in the wrong order. import os should be before import time
39:1: I201 Missing newline before sections or imports.
40:1: I100 Imports statements are in the wrong order. from tempfile should be before from unidecode
40:1: I201 Missing newline before sections or imports.
57: D290 White spaces around docstring should be trimmed.
57: D203 Expected 1 blank line *before* class docstring, found 0
57: D204 Expected 1 blank line *after* class docstring, found 0
57: D400 First line should end with '.', not 'a'
57: D205 Blank line missing between one-line summary and description
64: D290 White spaces around docstring should be trimmed.
64: D203 Expected 1 blank line *before* class docstring, found 0
64: D204 Expected 1 blank line *after* class docstring, found 0
64: D400 First line should end with '.', not 'd'
64: D200 One-line docstring should not occupy 2 lines
70: D290 White spaces around docstring should be trimmed.
70: D400 First line should end with '.', not 'y'
75:29: E126 continuation line over-indented for hanging indent
86: D203 Expected 1 blank line *before* class docstring, found 0
86: D204 Expected 1 blank line *after* class docstring, found 0
86: D400 First line should end with '.', not 'r'
86: D200 One-line docstring should not occupy 3 lines
92: D401 First line should be imperative: 'Return', not 'Returns'
92: D400 First line should end with '.', not 'd'
114:45: E128 continuation line under-indented for visual indent
115:45: E128 continuation line under-indented for visual indent
116:45: E128 continuation line under-indented for visual indent
117:45: E128 continuation line under-indented for visual indent
122:45: E128 continuation line under-indented for visual indent
123:45: E128 continuation line under-indented for visual indent
124:45: E128 continuation line under-indented for visual indent
125:45: E128 continuation line under-indented for visual indent
127:33: E128 continuation line under-indented for visual indent
132:45: E128 continuation line under-indented for visual indent
133:45: E128 continuation line under-indented for visual indent
134:45: E128 continuation line under-indented for visual indent
135:45: E128 continuation line under-indented for visual indent
147:41: E127 continuation line over-indented for visual indent
148:41: E127 continuation line over-indented for visual indent
149:41: E127 continuation line over-indented for visual indent
150:41: E127 continuation line over-indented for visual indent
153:37: E128 continuation line under-indented for visual indent
154:37: E128 continuation line under-indented for visual indent
155:37: E128 continuation line under-indented for visual indent
156:37: E128 continuation line under-indented for visual indent
159:37: E128 continuation line under-indented for visual indent
160:37: E128 continuation line under-indented for visual indent
161:37: E128 continuation line under-indented for visual indent
162:37: E128 continuation line under-indented for visual indent
165:37: E128 continuation line under-indented for visual indent
166:37: E128 continuation line under-indented for visual indent
167:37: E128 continuation line under-indented for visual indent
168:37: E128 continuation line under-indented for visual indent
192:1: E266 too many leading '#' for block comment
194: D401 First line should be imperative: 'call', not 'calls'
194: D290 White spaces around docstring should be trimmed.
194: D400 First line should end with '.', not 'd'
222: D401 First line should be imperative: 'submit', not 'submits'
222: D290 White spaces around docstring should be trimmed.
222: D400 First line should end with '.', not 's'
235:39: E127 continuation line over-indented for visual indent
236:39: E127 continuation line over-indented for visual indent
239: D103 Docstring missing
245:1: E302 expected 2 blank lines, found 1
245: D290 White spaces around docstring should be trimmed.
245: D400 First line should end with '.', not 'h'
255: D290 White spaces around docstring should be trimmed.
255: D400 First line should end with '.', not 'y'
273: D401 First line should be imperative: 'Perform', not 'Performs'
273: D290 White spaces around docstring should be trimmed.
273: D209 Put multi-line docstring closing quotes on separate line
273: D400 First line should end with '.', not 'w'
273: D205 Blank line missing between one-line summary and description
336: D401 First line should be imperative: 'Construct', not 'Constructs'
340:9: E128 continuation line under-indented for visual indent
341:9: E128 continuation line under-indented for visual indent
342:9: E128 continuation line under-indented for visual indent
343:9: E128 continuation line under-indented for visual indent
344:9: E128 continuation line under-indented for visual indent
345:9: E128 continuation line under-indented for visual indent
346:9: E128 continuation line under-indented for visual indent
347:9: E128 continuation line under-indented for visual indent
348:5: E124 closing bracket does not match visual indentation


1: D100 Docstring missing
27: D103 Docstring missing


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
23:1: I101 Imported names are in the wrong order. Should be TexkeyNoAuthorError, TexkeySeq
25:1: E302 expected 2 blank lines, found 1
25: D200 One-line docstring should not occupy 3 lines
36:23: E261 at least two spaces before inline comment
40:21: E222 multiple spaces after operator
46:17: E128 continuation line under-indented for visual indent
48:1: W391 blank line at end of file


1: D100 Docstring missing


1: D400 First line should end with '.', not 'e'
1: D200 One-line docstring should not occupy 3 lines
4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: I101 Imported names are in the wrong order. Should be record_get_field_value, record_get_field_values
27:1: I101 Imported names are in the wrong order. Should be BibCatalogTagNotFound, load_tag_code_from_name, record_get_value_with_provenence, record_id_from_record, record_in_collection, split_tag_code
27:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.utils should be before from invenio.legacy.bibrecord
36: D401 First line should be imperative: 'Check', not 'Checks'
53: D401 First line should be imperative: 'Generate', not 'Generates'
53: D400 First line should end with '.', not 's'
53: D205 Blank line missing between one-line summary and description
125:15: E127 continuation line over-indented for visual indent
165: D401 First line should be imperative: 'Return', not 'Returns'
165: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 'I'
4: L102 copyright year is outdated, expected 2015 but got 2013
28:1: E302 expected 2 blank lines, found 1
56:1: W391 blank line at end of file


1: D400 First line should end with '.', not 'a'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
37: D103 Docstring missing


1: D400 First line should end with '.', not 'k'
4: L102 copyright year is outdated, expected 2015 but got 2014
26:1: I100 Imports statements are in the wrong order. import getopt should be before import sys
29:1: I100 Imports statements are in the wrong order. import time should be before import traceback
30:1: I100 Imports statements are in the wrong order. import inspect should be before import time
34:1: I100 Imports statements are in the wrong order. from ConfigParser should be before from collections
37:1: I101 Imported names are in the wrong order. Should be get_modified_records_since, task_get_option, task_get_task_param, task_has_option, task_init, task_low_level_submission, task_set_option, task_sleep_now_if_required, task_update_progress, write_message
37:1: I201 Missing newline before sections or imports.
47:1: I101 Imported names are in the wrong order. Should be CFG_CERN_SITE, CFG_ETCDIR, CFG_PYLIBDIR, CFG_SITE_URL, CFG_TMPSHAREDDIR, CFG_VERSION
47:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibsched.bibtask
54:1: I101 Imported names are in the wrong order. Should be perform_request_search, search_pattern, search_unit_in_bibxxx
58:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibedit.utils should be before from invenio.legacy.search_engine
59:1: I101 Imported names are in the wrong order. Should be record_add_field, record_xml_output
60:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.legacy.bibrecord
60:1: I201 Missing newline before sections or imports.
61:1: I201 Missing newline before sections or imports.
62:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibcatalog.api should be before from invenio.legacy.dbquery
64:1: I100 Imports statements are in the wrong order. from invenio.utils.json should be before from invenio.utils.shell
68:1: E302 expected 2 blank lines, found 1
68: D290 White spaces around docstring should be trimmed.
68: D203 Expected 1 blank line *before* class docstring, found 0
68: D204 Expected 1 blank line *after* class docstring, found 0
68: D400 First line should end with '.', not 'n'
70: D102 Docstring missing
72:13: E128 continuation line under-indented for visual indent
75: D290 White spaces around docstring should be trimmed.
75: D203 Expected 1 blank line *before* class docstring, found 0
75: D204 Expected 1 blank line *after* class docstring, found 0
75: D400 First line should end with '.', not 'n'
77: D102 Docstring missing
88: D401 First line should be imperative: 'Iterate', not 'Iterates'
149:55: E261 at least two spaces before inline comment
163: D290 White spaces around docstring should be trimmed.
163: D400 First line should end with '.', not 'n'
169:57: E261 at least two spaces before inline comment
175: D290 White spaces around docstring should be trimmed.
175: D400 First line should end with '.', not 'e'
182: D401 First line should be imperative: 'Change', not 'Changes'
182: D400 First line should end with '.', not 'e'
182: D205 Blank line missing between one-line summary and description
201:25: E128 continuation line under-indented for visual indent
204: D400 First line should end with '.', not 'd'
204: D200 One-line docstring should not occupy 3 lines
216: D290 White spaces around docstring should be trimmed.
216: D400 First line should end with '.', not 'd'
222: D290 White spaces around docstring should be trimmed.
222: D400 First line should end with '.', not 'd'
226:13: E128 continuation line under-indented for visual indent
228: D290 White spaces around docstring should be trimmed.
228: D400 First line should end with '.', not 'd'
231:17: E128 continuation line under-indented for visual indent
237: D290 White spaces around docstring should be trimmed.
237: D400 First line should end with '.', not 'd'
240:17: E128 continuation line under-indented for visual indent
244: D290 White spaces around docstring should be trimmed.
244: D400 First line should end with '.', not 'd'
248:17: E128 continuation line under-indented for visual indent
250: D290 White spaces around docstring should be trimmed.
250: D400 First line should end with '.', not 't'
254: D401 First line should be imperative: 'Yield', not 'Yields'
254: D400 First line should end with '.', not 'g'
265:5: E129 visually indented line with same indent as next logical line
271: D102 Docstring missing
276: D290 White spaces around docstring should be trimmed.
276: D202 No blank lines allowed *after* function docstring, found 1
276: D400 First line should end with '.', not 'k'
301:1: E302 expected 2 blank lines, found 1
341:25: E128 continuation line under-indented for visual indent
367:5: E266 too many leading '#' for block comment
379:1: E302 expected 2 blank lines, found 1
379: D290 White spaces around docstring should be trimmed.
379: D202 No blank lines allowed *after* function docstring, found 1
379: D400 First line should end with '.', not 'g'
422: D290 White spaces around docstring should be trimmed.
422: D202 No blank lines allowed *after* function docstring, found 1
422: D400 First line should end with '.', not 'd'
448:1: E302 expected 2 blank lines, found 1
448: D400 First line should end with '.', not 'e'
448: D200 One-line docstring should not occupy 3 lines
458:1: E302 expected 2 blank lines, found 1
458: D400 First line should end with '.', not 'e'
458: D200 One-line docstring should not occupy 3 lines
468:1: E302 expected 2 blank lines, found 1
468: D400 First line should end with '.', not 'e'
468: D205 Blank line missing between one-line summary and description
481: D202 No blank lines allowed *after* function docstring, found 1
481: D400 First line should end with '.', not 'd'
481: D205 Blank line missing between one-line summary and description
493:20: E261 at least two spaces before inline comment
498: D400 First line should end with '.', not 'e'
498: D205 Blank line missing between one-line summary and description
505:1: E302 expected 2 blank lines, found 1
528:1: E302 expected 2 blank lines, found 1
528: D290 White spaces around docstring should be trimmed.
528: D400 First line should end with '.', not 'e'
537: D290 White spaces around docstring should be trimmed.
537: D400 First line should end with '.', not 's'
554:47: E127 continuation line over-indented for visual indent
587: D400 First line should end with '.', not 's'
587: D200 One-line docstring should not occupy 3 lines
611: D401 First line should be imperative: 'Generate', not 'Generates'
652:16: E713 test for membership should be 'not in'
662: D400 First line should end with '.', not 'e'
662: D205 Blank line missing between one-line summary and description
675:1: E302 expected 2 blank lines, found 1
675: D400 First line should end with '.', not 'a'
675: D205 Blank line missing between one-line summary and description
730: D401 First line should be imperative: 'Print', not 'Prints'
730: D400 First line should end with '.', not 't'
732:12: E221 multiple spaces before operator
748: D401 First line should be imperative: 'Print', not 'Prints'
748: D400 First line should end with '.', not 't'
762: D401 First line should be imperative: 'Construct', not 'Constructs'
801:36: E127 continuation line over-indented for visual indent
820:19: E128 continuation line under-indented for visual indent
821:19: E128 continuation line under-indented for visual indent
824:1: W391 blank line at end of file


31:1: I100 Imports statements are in the wrong order. import getopt should be before import sys
34:1: I201 Missing newline before sections or imports.
37:1: I101 Imported names are in the wrong order. Should be CFG_OAI_FAILED_HARVESTING_EMAILS_ADMIN, CFG_OAI_FAILED_HARVESTING_STOP_QUEUE, CFG_SITE_SUPPORT_EMAIL
37:1: I100 Imports statements are in the wrong order. from invenio.config should be before from sqlalchemy
37:1: I201 Missing newline before sections or imports.
43:1: I101 Imported names are in the wrong order. Should be task_get_option, task_get_task_param, task_init, task_set_option, write_message
43:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.modules.oaiharvester.models
49:1: I100 Imports statements are in the wrong order. from invenio.legacy.oaiharvest should be before from invenio.legacy.oaiharvest.config
50:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.oaiharvest
52:1: I100 Imports statements are in the wrong order. from invenio.base.factory should be before from invenio.ext.logging
54:1: I101 Imported names are in the wrong order. Should be compare_timestamps_with_tolerance, create_ticket, generate_harvest_report
59:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.legacy.webuser
61:1: I101 Imported names are in the wrong order. Should be BibWorkflowEngineLog, BibWorkflowObjectLog, Workflow
64:1: I100 Imports statements are in the wrong order. from invenio.modules.workflows.api should be before from invenio.modules.workflows.registry
66:1: I100 Imports statements are in the wrong order. import invenio.legacy.template should be before from invenio.modules.workflows.errors
241:17: E266 too many leading '#' for block comment
258:21: E266 too many leading '#' for block comment
274: D290 White spaces around docstring should be trimmed.
280:13: E266 too many leading '#' for block comment
281:13: E266 too many leading '#' for block comment
388:27: F821 undefined name '__revision__'


1: M111 unrecognized component name: docextract


Why not six.iteritems?


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
4: L102 copyright year is outdated, expected 2015 but got 2013
26:1: I100 Imports statements are in the wrong order. from invenio.bibknowledge should be before from invenio.utils.crossref
27:1: I100 Imports statements are in the wrong order. import difflib should be before from invenio.bibknowledge
27:1: I201 Missing newline before sections or imports.
30:1: E302 expected 2 blank lines, found 1
30: D290 White spaces around docstring should be trimmed.
30: D400 First line should end with '.', not 's'
34:1: E302 expected 2 blank lines, found 1
34: D290 White spaces around docstring should be trimmed.
34: D400 First line should end with '.', not 'y'
41:1: E302 expected 2 blank lines, found 1
41: D290 White spaces around docstring should be trimmed.
41: D400 First line should end with '.', not 'l'
48:1: E302 expected 2 blank lines, found 1
48: D400 First line should end with '.', not 'f'
48: D205 Blank line missing between one-line summary and description
109:5: E303 too many blank lines (2)
130: D400 First line should end with '.', not 'e'
130: D205 Blank line missing between one-line summary and description
146:1: W391 blank line at end of file


1: D400 First line should end with '.', not 'd'
1: D205 Blank line missing between one-line summary and description
2: L102 copyright year is outdated, expected 2015 but got 2014
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_URL
25:1: I201 Missing newline before sections or imports.
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. from invenio.base.i18n should be before from invenio.utils.url
28:1: E402 module level import not at top of file
31:25: E126 continuation line over-indented for hanging indent
33:1: E302 expected 2 blank lines, found 1
33: D290 White spaces around docstring should be trimmed.
33: D203 Expected 1 blank line *before* class docstring, found 0
33: D400 First line should end with '.', not 's'
36: D400 First line should end with '.', not 'e'
36: D208 Docstring is over-indented
36: D200 One-line docstring should not occupy 3 lines
47: D209 Put multi-line docstring closing quotes on separate line
47: D400 First line should end with '.', not 'l'
47: D205 Blank line missing between one-line summary and description
47: D208 Docstring is over-indented
50:9: F841 local variable '_' is assigned to but never used
55: D401 First line should be imperative: 'Draw', not 'Draws'
55: D400 First line should end with '.', not 'r'
55: D205 Blank line missing between one-line summary and description
55: D208 Docstring is over-indented
73:5: E303 too many blank lines (2)
73: D401 First line should be imperative: 'Draw', not 'Draws'
73: D400 First line should end with '.', not 'r'
73: D205 Blank line missing between one-line summary and description
73: D208 Docstring is over-indented
87: D401 First line should be imperative: 'Draw', not 'Draws'
87: D400 First line should end with '.', not 'r'
87: D205 Blank line missing between one-line summary and description
87: D208 Docstring is over-indented
99: D209 Put multi-line docstring closing quotes on separate line
99: D400 First line should end with '.', not 'l'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
112: D102 Docstring missing
127: D401 First line should be imperative: 'Draw', not 'Draws'
127: D400 First line should end with '.', not 'x'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
146: D401 First line should be imperative: 'Draw', not 'Draws'
146: D400 First line should end with '.', not 'x'
146: D205 Blank line missing between one-line summary and description
146: D208 Docstring is over-indented
164: D401 First line should be imperative: 'Draw', not 'Draws'
164: D400 First line should end with '.', not 's'
164: D205 Blank line missing between one-line summary and description
164: D208 Docstring is over-indented
197: D401 First line should be imperative: 'Draw', not 'Draws'
197: D400 First line should end with '.', not 't'
197: D205 Blank line missing between one-line summary and description
197: D208 Docstring is over-indented
241:79: E502 the backslash is redundant between brackets
242:74: E502 the backslash is redundant between brackets
245:95: E502 the backslash is redundant between brackets
246:86: E502 the backslash is redundant between brackets
247:87: E502 the backslash is redundant between brackets
254:5: E303 too many blank lines (2)
254: D401 First line should be imperative: 'Draw', not 'Draws'
254: D209 Put multi-line docstring closing quotes on separate line
254: D400 First line should end with '.', not 'x'
254: D205 Blank line missing between one-line summary and description
254: D208 Docstring is over-indented
259:9: F841 local variable '_' is assigned to but never used
268:42: E261 at least two spaces before inline comment
268:43: E262 inline comment should start with '# '
272:31: F841 local variable 'e' is assigned to but never used
280: D401 First line should be imperative: 'Return', not 'Returns'
280: D400 First line should end with '.', not ':'
280: D205 Blank line missing between one-line summary and description
289:9: F841 local variable '_' is assigned to but never used
294:18: E225 missing whitespace around operator
296:18: E127 continuation line over-indented for visual indent
299: D401 First line should be imperative: 'Output', not 'Outputs'
299: D400 First line should end with '.', not 'o'
306: D401 First line should be imperative: 'Output', not 'Outputs'
306: D400 First line should end with '.', not 'o'
313: D401 First line should be imperative: 'Output', not 'Outputs'
313: D400 First line should end with '.', not 's'
315:9: F841 local variable '_' is assigned to but never used
322: D401 First line should be imperative: 'Print', not 'Prints'
322: D209 Put multi-line docstring closing quotes on separate line
322: D400 First line should end with '.', not 't'
322: D205 Blank line missing between one-line summary and description
322: D208 Docstring is over-indented
336: D401 First line should be imperative: 'Print', not 'Prints'
336: D400 First line should end with '.', not 'e'
338:9: F841 local variable '_' is assigned to but never used
343: D102 Docstring missing
347: D400 First line should end with '.', not 'n'
360:15: E221 multiple spaces before operator
377: D401 First line should be imperative: 'Print', not 'Prints'
377: D400 First line should end with '.', not ','
377: D205 Blank line missing between one-line summary and description
406: D102 Docstring missing
408:22: E711 comparison to None should be 'if cond is not None:'
415: D102 Docstring missing
418: D102 Docstring missing
424:21: E711 comparison to None should be 'if cond is not None:'
429: D102 Docstring missing
435:21: E711 comparison to None should be 'if cond is not None:'
440: D102 Docstring missing
443: D102 Docstring missing
446: D400 First line should end with '.', not 'y'
449:65: E502 the backslash is redundant between brackets
451:46: E231 missing whitespace after ':'
457:34: E127 continuation line over-indented for visual indent
459: D102 Docstring missing
467: D102 Docstring missing
471: D102 Docstring missing
474: D102 Docstring missing
477: D102 Docstring missing
483: D102 Docstring missing
489: D401 First line should be imperative: 'construct', not 'constructs'
489: D400 First line should end with '.', not 'r'
492:26: E711 comparison to None should be 'if cond is None:'
508:68: E502 the backslash is redundant between brackets
510:49: E231 missing whitespace after ':'
515:68: E502 the backslash is redundant between brackets
517:49: E231 missing whitespace after ':'
527: D102 Docstring missing
534: D401 First line should be imperative: 'Write', not 'Writes'
534: D400 First line should end with '.', not 's'
578: D401 First line should be imperative: 'Create', not 'Creates'
578: D205 Blank line missing between one-line summary and description
603: D102 Docstring missing
607: D400 First line should end with '.', not 'u'
607: D208 Docstring is over-indented
607: D200 One-line docstring should not occupy 3 lines
620:70: E502 the backslash is redundant between brackets
624:72: E502 the backslash is redundant between brackets
625:38: E128 continuation line under-indented for visual indent
626:38: E128 continuation line under-indented for visual indent
627:38: E128 continuation line under-indented for visual indent
628:70: E502 the backslash is redundant between brackets
632:70: E502 the backslash is redundant between brackets
636:73: E502 the backslash is redundant between brackets
641:63: E203 whitespace before ','
644:23: E711 comparison to None should be 'if cond is not None:'
646:23: E126 continuation line over-indented for hanging indent
654: D401 First line should be imperative: 'Convert', not 'Converts'
654: D400 First line should end with '.', not 's'
654: D205 Blank line missing between one-line summary and description
665: D401 First line should be imperative: 'format', not 'formats'
665: D400 First line should end with '.', not 't'
665: D205 Blank line missing between one-line summary and description
671:17: E711 comparison to None should be 'if cond is None:'
675: D102 Docstring missing
676:17: E711 comparison to None should be 'if cond is None:'
680: D102 Docstring missing
681:25: E711 comparison to None should be 'if cond is None:'
684:16: E127 continuation line over-indented for visual indent
685:16: E127 continuation line over-indented for visual indent
687: D102 Docstring missing
698: D400 First line should end with '.', not 'w'
698: D205 Blank line missing between one-line summary and description
698: D208 Docstring is over-indented
710:21: E126 continuation line over-indented for hanging indent
711:28: E203 whitespace before ':'
712:17: E121 continuation line under-indented for hanging indent
725:22: E203 whitespace before ':'
726:28: E203 whitespace before ':'
727:8: E122 continuation line missing indentation or outdented
729: D400 First line should end with '.', not 'e'
729: D205 Blank line missing between one-line summary and description
750:16: E713 test for membership should be 'not in'


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
4: L102 copyright year is outdated, expected 2015 but got 2013
30:1: E302 expected 2 blank lines, found 1
30: D401 First line should be imperative: 'Correct', not 'Corrects'
30: D400 First line should end with '.', not 's'
31:9: E128 continuation line under-indented for visual indent
32:9: E128 continuation line under-indented for visual indent
32:35: E231 missing whitespace after ','
32:37: E231 missing whitespace after ','
76:21: E261 at least two spaces before inline comment
80:1: W391 blank line at end of file


2: L101 copyright is missing


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not ')'
4: L102 copyright year is outdated, expected 2015 but got 2013
24:1: I100 Imports statements are in the wrong order. from invenio.bibupload should be before from invenio.utils.crossref
27: D400 First line should end with '.', not 'd'
27: D205 Blank line missing between one-line summary and description
53:17: E128 continuation line under-indented for visual indent


3: L102 copyright year is outdated, expected 2015 but got 2014


@SandeepRaparthi1 why don't you assign it the same value as that in the default constructor?


....  e starò attento anche ad usare l'account corretto, sorry !


I concur. My initial look into this yielded little. I'm looking into replacing bats with shunit2 possibly. Need to do a PoC to see if its any better.


I'm not sure if this is Mac OS spefic but I cant seem to resize the popup,


Takie przykłady są właśnie w `sesje/2015-03-04/funcs_*.py`...


```/datasets/<dataset_id>/display``` without ```/api``` works for me on Galaxy dev, am I missing something?


2x racja :)


Yep, seems to be OS X issue, I also don't see the resize on my Mac.

Honza


s/uint64_t/val_t , here and below in gc_swap_marker()


Where does ``modelClassName`` come from? - There was no such variable.


done.


Connection is not closed. Innobackupex querying MySQL variables to determine which features are supported by server. Special interest are backup locks, changed page bitmaps, GTID mode, etc.


all applications in the project starts with small caps.


86605784-RefrigNoNodeCrash (jasondegraw) - 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)


Please use @unittest.skipIf([some executable condition]) rather than leaving an enormous block of commented-out code in the body of the test.


Merge branch 'master' of github.com:Ultimaker/CuraEngine


Another case for unittest.skipIf?


Fixes various issues with saving in Metroid Fusion.


No need to reconnect to the server.


This commit breaks windows builds as windows does not know netif/in.h used in SerializerUtil.cc. I think on windows you can use Winsock2.h instead. But do we really want platform dependent stuff here?


This default should go away now that this is a non-nullable field in the workflow db.


We are not going to apply it.
1) `scanner.c.top` is under git.
2) fb2ba24a47bf249d47fadb42b74045e6414492a5  remove `scanner.c.bottom` after use.


This has nothing to do with Python 3; please propose it in a separate pull request.


How are these used?


Why allow a blank password when validating for minimum length of 6?


This very welcome clean-up has nothing to do with Python 3; please propose it in a separate pull request (and consider dropping the unnecessary parentheses on line 103).


1: M111 unrecognized component name: i18n


It seems that style here is not perfect according to the lecture 2 (plus every other comparison operators are surrounded with spaces).
Although it looks like a heart so it should be forgiven :)


I can't test it properly, can you test with
```c++
std::string::iterator result = std::find_if(toParse.begin(), toParse.end(), [](char x) { return std::isalnum(x, g_langInfo.GetLocale()); });
```


Actually even with my fix this commit prevents automatic style injection on https://feedly.com - I have to manually re-enable the style. So I reverted the commit and the problem was gone.


Even though all don't use initargs, etc., should they all follow the same pattern?


Overall, I think the RunOfCards class is pretty solid.  I will be moving onto CanastaPlayer, but again I have to split up my time between making some progress on the different views for the system and reviewing Rails.  I had mentioned moving some of the methods to a private or protected status, you can comment on that idea if you want.  I would rather not expose is_wild? or is_natural? etc. to the outside world.  I have to figure out how to do this given we have classes defined within the RunOfCards class.  This is something I can do at a later time.


not trying to be a pita but wondering if:

"Kodi movie playback progress are up to date"

should be

"Kodi movie(s) playback progress are up to date"

or

"Kodi movie playback progress is up to date"

the tense seemed wrong to me, if so it would apply to the following as well:

"%i movie playback progress will be updated in Kodi"
"Kodi episode playback progress are up to date"

the easiest solution may be to add (s) to movie and episode in each case

just some thoughts, didnt want to do a pr until you decided if anything actually needed changing


You dont need a pointer for the thread. Unless, you are trying not to leak Boost library.


Revert this.


why commented line ? Then this is not checking anything right ?


Looks very good to me! Merged to staging.


@dkayiwa have Done that :)


Oh, my last question got factored out.


What is happening here ?


I was wondering if it might be possible to move this into `Govspeak::ContactsExtractor` as well? e.g.

```ruby

class ContactsExtractor
  def replace_contacts(&block)
    govspeak.gsub(EMBEDDED_CONTACT_REGEXP) do
      yield $1
    end
  end
end
```

that way the contact regexp is entirely contained within the extractor.

It might require some jigging around to ensure that you can call `#render` on the correct object (ie. `self` needs to point to the correct thing in the block passed in).

if you don't see an obvious way to make this work, don't worry too much!


@devernay sure i can. I need to get linux snapshot with your changes.
i'll try to download the latest snapshot tomorrow and give you to know if everything is ok. :)
Thank you!!!!!


Isn't :employee_id already known from the session? Why have it in the form?


Why is userObject set to nil in cleanup? This commit that originated it seems to imply it is something related to CCBAnimationManager when using Spritebuilder - but that code vanished in a later commit.

By its name 'userObject' is for user code - not the engine to use.


Redstone mod


Why now


Thanks about that.

About this `todo/fix: allow four-letter codes` we have 5-letter codes as well (ie: niort or nimes)  and we might have even more.


I see version 1.4.5 released on rubygems, but it is not tagged on this repo...
and in this commit, I see a bump from 1.4.4 to 1.5.0 ?!?

I'm lost...


gc_swap_marker removed, was part of a different approach, which is obsoleted by marking via null terminator of previous string


Hi Andrew,
Sorry about the problem and thanks for letting us know. We did replace the
apache lang library with lang3. Please do the following in the eclipse:
1. right click on the project, select build path->config build path
2. select library tab.
3. remove the apache lang library.
4. click on add jars, add the lang3 jar under BoxJavaLibraryV2/libs folder.

Thanks,
Jian

On Tue, Mar 3, 2015 at 11:38 PM, Andrew El-Masry <notifications@github.com>
wrote:

> [image: boxandroidsdkerror]
> <https://cloud.githubusercontent.com/assets/8506868/6479680/5310367e-c217-11e4-8b20-b384f65b6810.png>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/box/box-java-sdk-v2/commit/63da03ac75ef48ed6784c5fe4fc9eeeec2909a58#commitcomment-10023637>
> .
>


Hello @bradical

It looks like Open Office may have been the culprit to the unreadability. I've recommitted hopefully as plain text. Let me know if this is better.

Regards,

Eric


Hana


In a way, this does have to do with python3.  Python2 will work with mixed tabs and spaces, but if you try to run it in Python3, it will fail immediately.


> This should be changed to a normal fetched status.
> Unless you use a separate status (CacheFetched), the bolt receiving the status stream will need to check the status code to differentiate between either a 200 and 304 or a 301/302 and 304.

I think a NotModified status would be the right way to go here


You're right, we don't actually have it at this point. It can be composed from package name + convention to Domain/Model + expected filename based on given Form class name.

We need the model class name to be the index of entries so that it is in sync with `\FluidTYPO3\Flux\Core::registerFormForModelObjectClassName` and others. Flux identifies these registrations by their model class name so this function should deliver the same pragma.


I am not having issues with it, I will pull in the new ones from your dev branch to test and get back to you.


This thread is blocked until the listening thread set "blocked_" to false.


Thanks for the suggestion. We do not use const for [manually managed code]( https://github.com/dotnet/coreclr/blob/master/Documentation/mscorlib.md), e.g. no FCALL signature uses const. It would just get into way.


What does it do other than writing the info ?


Note the typo on line 42. `".github.iom"`. =)


Wow; I didn't know that. Okay, great. :-)


I wonder if this code might be easier to read if this variable was named `edition` instead of `dependant` (and similarly for the `@dependant` instance variable).

Since we are only ever describing the dependency of an edition on something, we don't need to generalise that word.


suggest s/sizeof(val_t)/sizeof(h)


Have you indexed foreign key employee_id on ProjectRequest table? Could speed up this kind of query.


sizeof(h)


I don't think "|| true" achieves anything here.

Rather, I think you should combine the last two lines as:
tox "$@" && coverage html


What about `  h = (uint64_t) v;` below.

Making it `  h = (val_t) v;` might be confusing (not as if this beast here is not already confusing enough)


This is just to be sure that the CMakeLists.txt in tests folder is working. No tests at all for now.


@orenmnero


1: M111 unrecognized component name: bibrank


2: L102 copyright year is outdated, expected 2015 but got 2012
24:1: E402 module level import not at top of file
26:1: I101 Imported names are in the wrong order. Should be error_page, page
26:1: E402 module level import not at top of file
27:1: I101 Imported names are in the wrong order. Should be CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_URL
27:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.webpage
27:1: F401 'CFG_SITE_NAME' imported but unused
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
30:1: E302 expected 2 blank lines, found 1
30: D103 Docstring missing
31:48: E261 at least two spaces before inline comment
35:5: B901 blind except: statement
38:30: E231 missing whitespace after ','
41:17: E128 continuation line under-indented for visual indent
42:17: E128 continuation line under-indented for visual indent
43:17: E128 continuation line under-indented for visual indent
44:17: E128 continuation line under-indented for visual indent
44:25: E251 unexpected spaces around keyword / parameter equals
44:27: E251 unexpected spaces around keyword / parameter equals
45:17: E128 continuation line under-indented for visual indent
46:17: E128 continuation line under-indented for visual indent
50:1: E302 expected 2 blank lines, found 1
50: D103 Docstring missing
55:5: B901 blind except: statement
58:30: E231 missing whitespace after ','
61:17: E128 continuation line under-indented for visual indent
65:17: E128 continuation line under-indented for visual indent
66:17: E128 continuation line under-indented for visual indent
67:17: E128 continuation line under-indented for visual indent
67:25: E251 unexpected spaces around keyword / parameter equals
67:27: E251 unexpected spaces around keyword / parameter equals
68:17: E128 continuation line under-indented for visual indent
69:17: E128 continuation line under-indented for visual indent
73:1: E302 expected 2 blank lines, found 1
73:75: E251 unexpected spaces around keyword / parameter equals
73:77: E251 unexpected spaces around keyword / parameter equals
73: D103 Docstring missing
78:5: B901 blind except: statement
81:30: E231 missing whitespace after ','
92:29: E251 unexpected spaces around keyword / parameter equals
92:31: E251 unexpected spaces around keyword / parameter equals
97:1: E302 expected 2 blank lines, found 1
97: D103 Docstring missing
102:5: B901 blind except: statement
105:30: E231 missing whitespace after ','
108:17: E128 continuation line under-indented for visual indent
109:50: E128 continuation line under-indented for visual indent
110:50: E128 continuation line under-indented for visual indent
111:50: E128 continuation line under-indented for visual indent
112:50: E128 continuation line under-indented for visual indent
113:17: E128 continuation line under-indented for visual indent
114:17: E128 continuation line under-indented for visual indent
115:17: E128 continuation line under-indented for visual indent
116:17: E128 continuation line under-indented for visual indent
116:25: E251 unexpected spaces around keyword / parameter equals
116:27: E251 unexpected spaces around keyword / parameter equals
117:17: E128 continuation line under-indented for visual indent
121:1: E302 expected 2 blank lines, found 1
121: D103 Docstring missing
126:5: B901 blind except: statement
129:30: E231 missing whitespace after ','
132:17: E128 continuation line under-indented for visual indent
133:50: E127 continuation line over-indented for visual indent
134:50: E127 continuation line over-indented for visual indent
135:17: E128 continuation line under-indented for visual indent
136:17: E128 continuation line under-indented for visual indent
137:17: E128 continuation line under-indented for visual indent
138:17: E128 continuation line under-indented for visual indent
138:25: E251 unexpected spaces around keyword / parameter equals
138:27: E251 unexpected spaces around keyword / parameter equals
139:17: E128 continuation line under-indented for visual indent
143:1: E302 expected 2 blank lines, found 1
143: D103 Docstring missing
148:5: B901 blind except: statement
151:30: E231 missing whitespace after ','
154:17: E128 continuation line under-indented for visual indent
160:17: E128 continuation line under-indented for visual indent
161:17: E128 continuation line under-indented for visual indent
162:17: E128 continuation line under-indented for visual indent
163:17: E128 continuation line under-indented for visual indent
163:25: E251 unexpected spaces around keyword / parameter equals
163:27: E251 unexpected spaces around keyword / parameter equals
164:17: E128 continuation line under-indented for visual indent
168:1: E302 expected 2 blank lines, found 1
168: D103 Docstring missing
173:5: B901 blind except: statement
176:30: E231 missing whitespace after ','
179:17: E128 continuation line under-indented for visual indent
181:17: E128 continuation line under-indented for visual indent
182:17: E128 continuation line under-indented for visual indent
183:17: E128 continuation line under-indented for visual indent
184:17: E128 continuation line under-indented for visual indent
184:25: E251 unexpected spaces around keyword / parameter equals
184:27: E251 unexpected spaces around keyword / parameter equals
185:17: E128 continuation line under-indented for visual indent


sorry, never gisted before. when i click on "your gists" it bring me to

https://gist.github.com/Lotto2
https://gist.github.com/Lotto2/86ef0518a24e688d6099

hope you can follow these links without being logged in as Lotto2;-)


The blocked_ variable seems tobe used in multiple threads ? There is no issue with thread safety ?


Then the configure script should check for the existence of ruby in the system?


Thank you for remarks. As for the extra assignement, do i put it in he same
place  as this one?

2015-03-03 18:34 GMT+02:00 Cosma Alex <notifications@github.com>:

> Even though you may not consider it as being terribly important,
> variable/function naming is terribly important so work on it a bit harder!
> Good job otherwise
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/birladeanuadrian/DSA-lab/commit/482672ecb7aab77bf8e1ee070e1afbac92c5a360#commitcomment-10010814>
> .
>


Should `deepcopy` be used here instead?

I'm not sure if anything in the state_dict is mutated etc. during serialization, but it would be the most defensive of the object state's to not return references.


Errr, why not ?


Will do


FYI @ferventcoder we're going to have to create these dirs as part of the MSI


does angular strap needs to be updated?


I would think it's safe to assume that these are good to go.  Technically people can change this, but that'd be insane.  It may not be necessary to use this at all though, maybe I can grab the jar directly and add it here (which might be better), will rewrite this.


Probably. This was ported from a private repo to the public monodevelop repo. I just realised this was probably a bad idea as we've hardcoded mac paths in this. I'll revert this as we need to do it a better way


Virtual attribute?


Just adds param to the arguments. There was some type mismatch between args and params that I couldn't assign it directly.
http://gradle.org/docs/current/dsl/org.gradle.api.tasks.JavaExec.html


Somewhere in here, you might also want to consider having track_visited_links = False.  We do that in several other places in anaconda where there's a label-as-link, and I think having some of the text be purple is pretty ugly in this case.  We're not a web browser.


@mbilbille   Merci. Good point. Thanks for the comment. Will try to get it fixed and allow up-to-five alphanums.  Thanks for keeping the match schedule up-to-date. Keep it up. Cheers.


1: M111 unrecognized component name: general


noo... i thought we can change this directly in source here ??
The thing is that: i've changes LCD Freq @ stock 499 and now i've screen tearing and laggs on simple 2D Games .. but the strange thing is: when i plug the charger.. then tearing are gone .. and laggs is then also less.. but not fully smooth like OC LCD freq.. (this is ok for me) but i can't understand why it makes so much difference with charger and without .. ?! usually i've all your patches for removing usell APE/DDR requirements too.. but it will be very friendly from u if u can check such things in my repo ??
Many thanks !!
btw: with org. LCD Freq the Power Consumption is 10% less !!!


@dkayiwa this commit seems to break redirects... for pages that hit line 198 (return "redirect:" + successUrl;) now instead of actually redirecting it simply displays a page with the redirect as the content.

I haven't found an example of this in the ref app yet, but it happens when ordering an x-ray in Mirebalais.

Going to look into one other failing smoke test on Mirebalais to see if it gives any more hints, but I may need to revert this until we get it fixed.


search gists for "GermanLanguageGenerator" should at least work.


Besides, it may be uneccessary to pull in ruby just for this.


:+1: :mailbox:


It will initiate in the future the known command transfert from Livre. It will also notify the RenderinRessourceManager of Livre crashes. It does nothing now but we said we need little commits.


Use proper indent. Ctrl-A, Ctrl+I hotkey will autoindent this file in Qt Creator


done


I would change the semantic of *!*:
```
super + !button{1-3}
	bspc pointer -g {move,resize_side,resize_corner}
```
In the above example, *!* would mean: start capturing motion events. A passive grab ends when its triggering button is released (cf. `xcb_grab_button(3)`).


partly because the compiler can't help with integers and booleans


Typo: 'recof' instead of 'record'


The reason I added `|| true` is to allow for the possibility that there's no coverage to erase, but it turns out that always returns zero, so I agree.


This PR is in response to your previous comment.

    (2) Some number of pull requests containing changes to the project configuration - .travis.yml and .tox.ini and so forth.

(0) and (1) were in reference to Python3, but I thought (2) was just a general comment, not specific to Python3.


Or rather, I think I should remove `||true` but leave the rest.


huh? no, i just needed to switch up my output to better coincide with reporting


This will be changed. I think, unfortunately, I will need to write another query.


Добавление файлов в гит-игнор —это конечно хорошо, но эти файлы уже с репозитории, нужно их оттуда удалить. А в будущем они уже будут игнориться.


Could be deleted, since it isn't used anywhere


I don't think so... The thread number1 is in an infinite loop until thread number2 set blocked_ to false.


Just a note - I'll be pulling this into pocketlint at some point, just as soon as I get around to wading through package review.


:+1: thanks @gab1one !


Is it something wrong with <string name="settings">Ustawienia</string>?? App still shows Settings instead Ustawienia


@BrandonBrowning could you try this version?
https://github.com/charsyam/twemproxy/tree/feature/issue-323
Thank you.


Should be deleted.


Have to update geometry.py. It is a minor patch


I believe there's a bug in bugzilla about this - should reference it in the commit.


ok. thanks for catching this.
Let me commit a hack. If it does not fix this, just revert. :)

On Wed, Mar 4, 2015 at 7:44 PM, Mark Goodrich <notifications@github.com>
wrote:

> @dkayiwa <https://github.com/dkayiwa> this commit seems to break
> redirects... for pages that hit line 198 (return "redirect:" + successUrl;)
> now instead of actually redirecting it simply displays a page with the
> redirect as the content.
>
> I haven't found an example of this in the ref app yet, but it happens when
> ordering an x-ray in Mirebalais.
>
> Going to look into one other failing smoke test on Mirebalais to see if it
> gives any more hints, but I may need to revert this until we get it fixed.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openmrs/openmrs-module-uiframework/commit/5c9b32da6666c2aa3f0d338c74b9892d0554b185#commitcomment-10033537>
> .
>

--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.


old 2 comment


> usually i've all your patches for removing usell APE/DDR requirements too.. but it will be very friendly from u if u can check such things in my repo ??

Didn't get it. What should I check?


What works for install only is
```
$(selector).flowplayer({ config });
```
No immediate api retrieval possible with:
```js
var player = $(selector).flowplayer({ config });
```
only with
```js
var player = flowplayer($(selector), { config });
```
So in our examples I will never use the first incantation, even for installation only (brainwash).
Unless you're inclined to implement that too.


old 3 comment


old 4 comment


I think you forgot to change the function name in the last line when making it a function for the Vasp class.


88620944-FluidCoolerWithLowSpeedAuto (jasondegraw) - x86_64-MacOS-10.9-clang: OK (1629 of 1629 tests passed)

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


Code style: spaces between pointer identifier and operator aren't allowed


The way I was thinking about keeping the etags or lastModified from the fetcher is simply to reply on the MetadataTransfer - more specifically the filter() method. Assuming we have 2 parameters in the conf indicating whether to track them or not, the values would be stored in whichever storage is used for the status. I assumed we'd keep the key names returned by the server after lowercasing (`last-modified` and `etag`).

When refetching the same page later, the protocol would get these key values in the metadata and if found, would send their values with the keys `If-Modified-Since` and `If-None-Match`.

I makes no difference whether the metadata comes from a previous fetch or has been generated from an external source.

> The cached* prefix is to preempt user confusion and to make it clear that the metadata value is a cached, previously-known value. For Last-Modified data, you could otherwise end up with lastModified and last-modified in the tuple metadata.

why would we get these variations? When doing the initial fetch we'd store `last-modified` in the metadata and reuse its value next time round.

Where would the 'lastModified' come from? Is that a variant that web sites return? if so let's do like in Nutch and add a normalisation step to the HTTP headers that goes beyond lowercasing.

> And for ETags, if you ingested a tuple with an etag key in its metadata, and then after fetching wrote the HTTP headers to the metadata, after down casing the field names the previous etag metadata value would be overwritten.

why does it matter if it is overwritten? The latest value is the one you'd send to the server next time round.


yes you're right.


Minor adjustment must be made.


How do you generate this sprites?


ah, thought it looked familiar, but just wanted to make sure :)


ggg


> Sure if you prefer Fetched over Redirection.

don't you think it is a more accurate status for it?

> Unless you use a separate status (CacheFetched), the bolt receiving the status stream will need to check the status code to differentiate between either a 200 and 304 or a 301/302 and 304.

yep. probably don't need yet another status but merely a check on the status code.


`assert` is a keyword, not a function, so use `assert numpy.shape(v)[0] == 1`


Benchmarking result of the original non-Clonable version

```
test coroutine::bench::bench_coroutine_counting              ... bench:     10980 ns/iter (+/- 2008)
test coroutine::bench::bench_coroutine_spawning_with_recycle ... bench:       246 ns/iter (+/- 86)
test coroutine::bench::bench_normal_counting                 ... bench:      6293 ns/iter (+/- 1203)
```

Best result of the current version,

```
test coroutine::bench::bench_coroutine_counting              ... bench:    286036 ns/iter (+/- 698990)
test coroutine::bench::bench_coroutine_spawning_with_recycle ... bench:   1658288 ns/iter (+/- 1833851)
test coroutine::bench::bench_normal_counting                 ... bench:      6321 ns/iter (+/- 2782)
```

Most of them are similar as

```
test coroutine::bench::bench_coroutine_counting              ... bench:    871559 ns/iter (+/- 617235)
test coroutine::bench::bench_coroutine_spawning_with_recycle ... bench:   1236920 ns/iter (+/- 145835)
test coroutine::bench::bench_normal_counting                 ... bench:      5810 ns/iter (+/- 1833)
```

I think we should not accept this feature, because it is not useful in most cases. If some one wants to get a `Handle` of the current coroutine, it should be an **unsafe** operation.


:-D sorry for my bed english... i like to know / see , what happens when charger is plugged.. i mean why it's the smoother ? and also tearing is then also fixed .. i like to fix this so that to have the same smoothness with charger.. but also with unplugged charger... did u now understand this ? xD


Perhaps because I'm not a native English speaker, my brain parses this as if it was the monitors that were dead. Not sure how to fix it. "Agent**s**"? "Dead**-**Agent"?

But maybe it's OK just the way it is...


Should there be a space here?


Should I be running the other SQL file that increases the pool limit of game objects as well as these patches? (I didn't for the most recent one).


Well spotted. This makes me feel very stupid.


Thanks man :)


:es:


[R/simulator_class.R:16:29:](https://github.com/paulstaab/coalsimr/blob/7e671d57439c276155d2995f6e1ee68e12e085d5/R/simulator_class.R#L16) *style:* **Opening curly braces should never go on their own line and should always be followed by a new line.**
```r
    initialize = function() {}
                            ^
```
[R/simulator_class.R:16:30:](https://github.com/paulstaab/coalsimr/blob/7e671d57439c276155d2995f6e1ee68e12e085d5/R/simulator_class.R#L16) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
    initialize = function() {}
                             ^
```
[R/simulator_msms.R:150:1:](https://github.com/paulstaab/coalsimr/blob/7e671d57439c276155d2995f6e1ee68e12e085d5/R/simulator_msms.R#L150) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/simulator_ms.R:21:31:](https://github.com/paulstaab/coalsimr/blob/7e671d57439c276155d2995f6e1ee68e12e085d5/R/simulator_ms.R#L21) *style:* **Commas should always have a space after.**
```r
      cmd <- c(cmd, '"-em"', ',', feat['time.point'], ',',
                              ^
```


So, should I check it with your kernel? If you can upload it somewhere, then yes, otherwise I don't have time for its compiling. It's definetely more than 17 minutes like on your machine :)


I'm adding my comments to your code.  This is a great start Matt... now get going =)


86605784-RefrigNoNodeCrash (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (633 of 633 tests passed)

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


This is not created by the MSI.  Only `var` is - see https://github.com/puppetlabs/puppet_for_the_win/blob/master/wix/puppet.wxs#L344-L349


@mogoodrich tell me if these commits fix the problem: https://github.com/openmrs/openmrs-module-uiframework/commit/dae554f93ee82b9d01bc83eb376f1025a343d150
https://github.com/openmrs/openmrs-module-uiframework/commit/72771580e45ec907b4c7a302c53524a60b62b919


thanks for adding the full list - found some kinks and working on ironing them out


I think self.word_space already does that for us.


В остальном на данном этапе более-менее норм. :+1:


Jacob,

What needs to be done next? Let me know how I can contribute. Still working through this code. What is your input X?

Thanks

Vivek


Thanks but I'm not ready for this yet --- even I haven't tried compiling this!


Of note, there is no `hiera_interactive.bat`

Also present:

* `puppet_shell.bat`
* `run_cfacter_interactive.bat`
* `run_facter_interactive.bat`
* `run_puppet_interactive.bat`


I've added my comment to line 4... can you see it?


Ah, oh, this EXTERNAL_LIBS is only 13 days old (from b85d2c659). I did not look at that recent code. Sorry, that was my fault then :(. I bet this does solve this problem already.


Cool, thanks! Unfortunately looks like there is emr-api weirdness going on right now that might need to be fixed first.


Ok I just looked at your changes, and you need to know that this method
stock.parsePrice(...) was removed in the latest version, so it wont work for you this way.

The problem with this one is that adding custom currencies changed a lot of the code that was responsilbe to transactions, calculating prices and so on.

As If you awnt hack yourself on thiss I will help you, just ask what you need and I will try to explain how to getto this thing.


develop (DavidGoldwasser) - 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)


There is also the `mco` wrapper present here.


Thank you telling me about this.:)


i mean if u found that weird thing directly in my sources.. but if it'S easy for u to test kernel directly.. then i'll upload it now ! That's cool !


develop (macumber) - Win64-Windows-7-VisualStudio-12: OK (2198 of 2212 tests passed)

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


Also includes `extlookup2hiera` but not sure you care about it.


Aaaah, the reason they are different is that `OpenSelectedDeclarationHandler` needs to accommodate links to _both_ Java and Ceylon.


Didn't mean to commit this here but I'll just leave it.


See [SpellCheckedMetadata](https://github.com/apache/nutch/blob/trunk/src/java/org/apache/nutch/metadata/SpellCheckedMetadata.java) for the normalisation of HTTP headers in Nutch


:-1: until comments are addressed.


I have no idea... Are you using the latest APK?


Oh, okay. Just play around with the pretty printer (maybe write some pretty tests?) and ensure that it does look like what you want it to


I've asked this before, but can't we just enforce that the offset is always `nil` when `null`, either by never passing `null` into the constructor or by moving this conditional to the constructor itself?


Haha okay... I'm just too excited. If it makes sense i'd really like to
help. The fixed size array issue is blocking everything for me ( at least
if i want to do things properly)

On Wed, 4 Mar 2015 17:58 Jeff Bezanson <notifications@github.com> wrote:

> Thanks but I'm not ready for this yet --- even I haven't tried compiling
> this!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/JuliaLang/julia/commit/246c0784bae64a7ec9d88838c650b040fc205150#commitcomment-10033849>
> .
>


Ack


To keep the commit small. A lot of tests need to be done.


Yes am looking into that right now.

On Wed, Mar 4, 2015 at 7:58 PM, Mark Goodrich <notifications@github.com>
wrote:

> Cool, thanks! Unfortunately looks like there is emr-api weirdness going on
> right now that might need to be fixed first.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openmrs/openmrs-module-uiframework/commit/5c9b32da6666c2aa3f0d338c74b9892d0554b185#commitcomment-10033865>
> .
>

--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.


Re: card puritanism - I would argue that clubs and spades are always black, and hearts and diamonds are always black, therefore the checking of color is just an extension of the suit of the card and is something the card should be responsible for answering. Either way, you've got the code working, so moving on is the easiest thing to do

For protected/private methods, I would say _any_ method that you don't want exposed to the outside world should at least be `protected`. But, if a certain methods needs to be exposed to another object in order to provide needed functionality, then there is no getting around just leaving it as a public method.

Just as an aside, in my opinion, `private` should hardly ever be used. Most times `protected` will accomplish the desired effect of keeping other objects from accessing that method on an object. Here's a good StackOverflow question on [ruby method visibility](http://stackoverflow.com/questions/3534449/why-does-ruby-have-both-private-and-protected-methods).


Is this a project lead assigning an employee to a project? Is the lead expected to know an employee's id to enter into  the form- seems like there should be a better way.


Ah, you mean as a generated test so it ends up in each plugin?


blabla


Same comment.


I don't think we really need to load the `dependable` because we can just check for the presence or absence of it based on `dependable_type` and `dependable_id`.


I just tried that again. Things broke and I couldn't figure it out. The core of the problem is I can't figure out what @offset is. Is it always seconds? Can it be something else? Is nil ok? Is float? Not really sure anymore.


@melissa filed a PR https://github.com/puppetlabs/puppet_for_the_win/pull/101


Be aware that `styles.scss` is a leftover file from the previous styles not used anymore and should be removed.


1: M111 unrecognized component name: oauthclient


25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
28:1: I100 Imports statements are in the wrong order. import httpretty should be before from six.moves.urllib_parse
34:1: I100 Imports statements are in the wrong order. from .helpers should be before from ..contrib.orcid


I am confused; all i am doing is materializing that variable so i can use it later.


I'm using https://github.com/TibiaJS/sprites-extractor slightly modified (to preserve order from filenames when marging) + https://github.com/RemoveIt/TibiaJS/blob/master/resources/merge.bat
(you need http://www.imagemagick.org/ to run this)


Argh yes


In the BattleGrounds your in spectator mode so you can't pop :(


Help would be great! If you look at the diff so far, it gives an idea of some of the tedious work needed: anywhere the system was using `jl_tuple*` on a tuple value, it should use `jl_sv*` instead. Anywhere we are operating on tuple types, we should use `jl_datatype_t` and `jl_datatype_t->parameters` instead.


Original comments in 0103cf939ddeefd7c887829edf5fef388c8ea06a


Original comments in 3cae6ea531a1faeeaa1a9e8e21bee5252644fc26


Original comments in 1eb0554b16c2bac3b4c580949a10fdd42a908b1d


Builded right now.. codina f2fs .. right ??


Plz change that PLz


a very very minor point for consideration.. as a good habit, I prefer to try to avoid mutating the memo passed to inject. It's a small thing but I've come more-and-more to realise that mutation of state is the source of many bugs, and if you can avoid it you will make programs easier to reason about.

So you could do instead:

```
attributes + [{ dependant: @dependant, dependable: dependable }]
```


Let's make it open the account modal, instead of going to the /account page, like the account button on this page does.


nope, I forgot to say that I still use ext4 :D


wait, `dispatch()` would catch help on subcommands, are you sure this would work? :

    python ice_setup.py help


@aliuk2012: nit for your patch (max chars per line is 80)

Honza


Yes, that is one of the thing i wanted to discuss; having to fetch the key and parse the yaml on each request is yucky...

I am not fond of the polling, but the alternate solution is relying on ext bus events (why not?), except in the end this end up being polling as well..


ohh.. okk mom


this is wrong :)


ACK, will do.


IMO the system is unbootable when the fs is not writable as the bundle cache can not be written.
Therefore we will not end up here or not?

On the other hand, why should `initialize.php` be writable let alone the previous `constants.php`?
We might want to rather check if `parameters.yml` and `localconfig.php` and the caches are writable but this will also not help that much.
IMO we can skip all these checks in here... we should discuss this in a feature ticket.


@TagForce thanks! will test it


We actually had this issue come up just recently, where QA requested we make a change to one of these because they are conflated, and we decided to roll that change back: https://github.com/puppetlabs/beaker/pull/671.

The host `user` and `group` setting are actually just supposed to be used for Beaker's ssh connections, and have nothing to do with Puppet and what it needs.  We've had this come up enough where I think this should be included in our set of properties that if used, should issue deprecation warnings, or fail tests.  So, in short, yes, I agree.


Sure, would make sense.


Ok will do.


It looks used down on L197


Yeah, that's a good idea, I'll tweak it.


Why list id's? Wouldn't name or title make more sense for person reading the list?


I tried running my tests through with `--pretty normal`, and the output looks normal.


Thanks Eric. Was this an auto-generated README?


@anjain , what does this extra if else block do? #128

Is it related to the bug I'm seeing?


in a sense, the agent monitors are dead :-)


Also: Disable pulseaudio.


slightly modified sprites-extractor -> https://github.com/RemoveIt/sprites-extractor


Copy-paste error?
It may also be useful to be more specific than "The country's area", perhaps "...according to postgres's st_area" and also include units (km?).


Seems some issue with Doze mode and hotplug suspend-resume


I installed the module and broswerify cannot find 'audioContext', shouldn't it be

```
var defaultAudioContext = require('audio-context');
```
as the name of the package is 'audio-context'?


Not nullable so double?


Thank you. Could you maybe squash the current state of things into one commit against master, and force-push?

There were so many back-and-forth changes that they probably won't look good in the repo history.


This test is probably a bit unconventional but I decided that I prefer it over a simple (and easily missed) comment. Let me know whether you agree - I'm open to different ideas here.


ok... it's with org lcd freq:

http://d-h.st/pJwq


D you check the branch I pushed?
On Mar 4, 2015 7:09 PM, "Kyle Robinson Young" <notifications@github.com>
wrote:

> It looks used down on L197
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gruntjs/grunt-contrib-jshint/commit/8c062cb056db1bee25a918bfb7d797e241a5a2ce#commitcomment-10034121>
> .
>


yes, we can definitely do this.  Older versions of acceptance still use this setting, so that'll be only for AIO and onward, however.


This parameter is used in line 231... So maybe just put a `(void)para` around line 235 instead of commenting the parameter?


Add units to comment explain conversion factor magic number 1000000


@adamcooke This is missing bundle exec rake db:migrate from build commands. I came across this issue a few days ago when deploying an updated version with db migrations pending.


HttpServerUtility.HtmlEncode Method (String)


I think the race exists in either cases (we may end up reading the old value). However on single node scenario, that would only occur if we were to fetch the value prior that call has returned.

In multi-node, since we rely on broadcast (polling), it does not even matter.


same remark.


Love this! So much more efficient...


Delete "Summary"


You mean :
result = deleteFromTransaction(key, entitySqlDaoWrapperFactory, context);
broadcastConfigurationChangeFromTransaction(entitySqlDaoWrapperFactory, key, context);
return result;


OK will do.


Yeah, I tested it.  If dispatch() doesn't trigger a subcommand (line 258), then it calls self.parse_args(), which will look for help and version at the top level.


Because of the commit reordering, this commit (1) has the vcxproj files out of date (need to run `scons vcxproj`), and (2) doesn't build with either version of the vcxproj files.

I don't know if it's worth fixing, or if everything will get squashed down anyway, but I did want to raise the flag.


Hi jarvist. I am very interested in the CH3NH3SnI3 POSCAR. Could you share this POSCAR with me.


How to: Protect Against Script Exploits in a Web Application by Applying HTML Encoding to Strings


`extra` seems poorly named. What kinds of extra information? It looks like parameters. If so, change that to `params`


You're setting a T to null. This is weird.


And set m_values to NULL?


i think this is a left-over from my first caching implementation; probably we don't need it anymore. And yes we are not consistent. My preference would be:
* For all internal operations, and java API never return immutable
* Jaxrs level return immutable (serialized in json anyways)


This try catch is janky


@es128 sorry had a call. yeah, your example is similar to what I was going to post.

> Which tests? The ones I have here pass.

Sorry I meant tests in a project I was working on. what I posted made no sense lol

> Going to add you to the repo

nice, thanks! happy to help


Since prng is part of crypto_ops, I think crypto_ops.init() should also take care of initializing the PRNG.


Yep, got that in my notes ;-)


Where is this json data used, what is the intent?


yeah, option 4 is actually what we were going for.  This was put in because when @nwolfe , @whopper , and myself were all sitting around trying to make acceptance work for this, @nwolfe noticed that we are separating where puppet's binary is from where ruby is, so we added this setting for ruby and those resources.  We can definitely change the name, I would love something that's more descriptive.


try catch is just size comparison. Also im not entirely sure how to declare the double pointer to NULL by default.


hahaha


Same comments as before- is user expected to know project/employees by id?


juego de cartas


The changing the function name ga() to __gaTracker() breaks event logging. What is the purpose of using __gaTracker() instead of the function Google recommends: ga()?


use Mesh *for* now


I think you meant DisplayObjectContainer


@bradical You're welcome!  No it was not auto-generated. It was more of a 'mock' example that I hand typed using Open Office for MAC and I guess it was some issues when I added to git.

-Eric


1: M111 unrecognized component name: docextract


Going to try and make sure all output is working correctly then will merge back with master


31:1: I100 Imports statements are in the wrong order. import getopt should be before import sys
34:1: I201 Missing newline before sections or imports.
37:1: I101 Imported names are in the wrong order. Should be CFG_OAI_FAILED_HARVESTING_EMAILS_ADMIN, CFG_OAI_FAILED_HARVESTING_STOP_QUEUE, CFG_SITE_SUPPORT_EMAIL
37:1: I100 Imports statements are in the wrong order. from invenio.config should be before from sqlalchemy
37:1: I201 Missing newline before sections or imports.
43:1: I101 Imported names are in the wrong order. Should be task_get_option, task_get_task_param, task_init, task_set_option, write_message
43:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.modules.oaiharvester.models
49:1: I100 Imports statements are in the wrong order. from invenio.legacy.oaiharvest should be before from invenio.legacy.oaiharvest.config
50:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.oaiharvest
52:1: I100 Imports statements are in the wrong order. from invenio.base.factory should be before from invenio.ext.logging
54:1: I101 Imported names are in the wrong order. Should be compare_timestamps_with_tolerance, create_ticket, generate_harvest_report
59:1: I100 Imports statements are in the wrong order. from invenio.ext.email should be before from invenio.legacy.webuser
61:1: I101 Imported names are in the wrong order. Should be BibWorkflowEngineLog, BibWorkflowObjectLog, Workflow
64:1: I100 Imports statements are in the wrong order. from invenio.modules.workflows.api should be before from invenio.modules.workflows.registry
66:1: I100 Imports statements are in the wrong order. import invenio.legacy.template should be before from invenio.modules.workflows.errors
241:17: E266 too many leading '#' for block comment
258:21: E266 too many leading '#' for block comment
274: D290 White spaces around docstring should be trimmed.
280:13: E266 too many leading '#' for block comment
281:13: E266 too many leading '#' for block comment
388:27: F821 undefined name '__revision__'


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


1: D400 First line should end with '.', not 'd'
1: D205 Blank line missing between one-line summary and description
2: L102 copyright year is outdated, expected 2015 but got 2014
23:1: E402 module level import not at top of file
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_URL
25:1: I201 Missing newline before sections or imports.
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. from invenio.base.i18n should be before from invenio.utils.url
28:1: E402 module level import not at top of file
31:25: E126 continuation line over-indented for hanging indent
33:1: E302 expected 2 blank lines, found 1
33: D290 White spaces around docstring should be trimmed.
33: D203 Expected 1 blank line *before* class docstring, found 0
33: D400 First line should end with '.', not 's'
36: D400 First line should end with '.', not 'e'
36: D208 Docstring is over-indented
36: D200 One-line docstring should not occupy 3 lines
47: D209 Put multi-line docstring closing quotes on separate line
47: D400 First line should end with '.', not 'l'
47: D205 Blank line missing between one-line summary and description
47: D208 Docstring is over-indented
50:9: F841 local variable '_' is assigned to but never used
55: D401 First line should be imperative: 'Draw', not 'Draws'
55: D400 First line should end with '.', not 'r'
55: D205 Blank line missing between one-line summary and description
55: D208 Docstring is over-indented
73:5: E303 too many blank lines (2)
73: D401 First line should be imperative: 'Draw', not 'Draws'
73: D400 First line should end with '.', not 'r'
73: D205 Blank line missing between one-line summary and description
73: D208 Docstring is over-indented
87: D401 First line should be imperative: 'Draw', not 'Draws'
87: D400 First line should end with '.', not 'r'
87: D205 Blank line missing between one-line summary and description
87: D208 Docstring is over-indented
99: D209 Put multi-line docstring closing quotes on separate line
99: D400 First line should end with '.', not 'l'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
112: D102 Docstring missing
127: D401 First line should be imperative: 'Draw', not 'Draws'
127: D400 First line should end with '.', not 'x'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
146: D401 First line should be imperative: 'Draw', not 'Draws'
146: D400 First line should end with '.', not 'x'
146: D205 Blank line missing between one-line summary and description
146: D208 Docstring is over-indented
164: D401 First line should be imperative: 'Draw', not 'Draws'
164: D400 First line should end with '.', not 's'
164: D205 Blank line missing between one-line summary and description
164: D208 Docstring is over-indented
197: D401 First line should be imperative: 'Draw', not 'Draws'
197: D400 First line should end with '.', not 't'
197: D205 Blank line missing between one-line summary and description
197: D208 Docstring is over-indented
241:79: E502 the backslash is redundant between brackets
242:74: E502 the backslash is redundant between brackets
245:95: E502 the backslash is redundant between brackets
246:86: E502 the backslash is redundant between brackets
247:87: E502 the backslash is redundant between brackets
254:5: E303 too many blank lines (2)
254: D401 First line should be imperative: 'Draw', not 'Draws'
254: D209 Put multi-line docstring closing quotes on separate line
254: D400 First line should end with '.', not 'x'
254: D205 Blank line missing between one-line summary and description
254: D208 Docstring is over-indented
259:9: F841 local variable '_' is assigned to but never used
268:42: E261 at least two spaces before inline comment
268:43: E262 inline comment should start with '# '
272:31: F841 local variable 'e' is assigned to but never used
280: D401 First line should be imperative: 'Return', not 'Returns'
280: D400 First line should end with '.', not ':'
280: D205 Blank line missing between one-line summary and description
289:9: F841 local variable '_' is assigned to but never used
294:18: E225 missing whitespace around operator
296:18: E127 continuation line over-indented for visual indent
299: D401 First line should be imperative: 'Output', not 'Outputs'
299: D400 First line should end with '.', not 'o'
306: D401 First line should be imperative: 'Output', not 'Outputs'
306: D400 First line should end with '.', not 'o'
313: D401 First line should be imperative: 'Output', not 'Outputs'
313: D400 First line should end with '.', not 's'
315:9: F841 local variable '_' is assigned to but never used
322: D401 First line should be imperative: 'Print', not 'Prints'
322: D209 Put multi-line docstring closing quotes on separate line
322: D400 First line should end with '.', not 't'
322: D205 Blank line missing between one-line summary and description
322: D208 Docstring is over-indented
336: D401 First line should be imperative: 'Print', not 'Prints'
336: D400 First line should end with '.', not 'e'
338:9: F841 local variable '_' is assigned to but never used
343: D102 Docstring missing
347: D400 First line should end with '.', not 'n'
360:15: E221 multiple spaces before operator
377: D401 First line should be imperative: 'Print', not 'Prints'
377: D400 First line should end with '.', not ','
377: D205 Blank line missing between one-line summary and description
406: D102 Docstring missing
408:22: E711 comparison to None should be 'if cond is not None:'
415: D102 Docstring missing
418: D102 Docstring missing
424:21: E711 comparison to None should be 'if cond is not None:'
429: D102 Docstring missing
435:21: E711 comparison to None should be 'if cond is not None:'
440: D102 Docstring missing
443: D102 Docstring missing
446: D400 First line should end with '.', not 'y'
449:65: E502 the backslash is redundant between brackets
451:46: E231 missing whitespace after ':'
457:34: E127 continuation line over-indented for visual indent
459: D102 Docstring missing
467: D102 Docstring missing
471: D102 Docstring missing
474: D102 Docstring missing
477: D102 Docstring missing
483: D102 Docstring missing
489: D401 First line should be imperative: 'construct', not 'constructs'
489: D400 First line should end with '.', not 'r'
492:26: E711 comparison to None should be 'if cond is None:'
508:68: E502 the backslash is redundant between brackets
510:49: E231 missing whitespace after ':'
515:68: E502 the backslash is redundant between brackets
517:49: E231 missing whitespace after ':'
527: D102 Docstring missing
534: D401 First line should be imperative: 'Write', not 'Writes'
534: D400 First line should end with '.', not 's'
578: D401 First line should be imperative: 'Create', not 'Creates'
578: D205 Blank line missing between one-line summary and description
603: D102 Docstring missing
607: D400 First line should end with '.', not 'u'
607: D208 Docstring is over-indented
607: D200 One-line docstring should not occupy 3 lines
620:70: E502 the backslash is redundant between brackets
624:72: E502 the backslash is redundant between brackets
625:38: E128 continuation line under-indented for visual indent
626:38: E128 continuation line under-indented for visual indent
627:38: E128 continuation line under-indented for visual indent
628:70: E502 the backslash is redundant between brackets
632:70: E502 the backslash is redundant between brackets
636:73: E502 the backslash is redundant between brackets
641:63: E203 whitespace before ','
644:23: E711 comparison to None should be 'if cond is not None:'
646:23: E126 continuation line over-indented for hanging indent
654: D401 First line should be imperative: 'Convert', not 'Converts'
654: D400 First line should end with '.', not 's'
654: D205 Blank line missing between one-line summary and description
665: D401 First line should be imperative: 'format', not 'formats'
665: D400 First line should end with '.', not 't'
665: D205 Blank line missing between one-line summary and description
671:17: E711 comparison to None should be 'if cond is None:'
675: D102 Docstring missing
676:17: E711 comparison to None should be 'if cond is None:'
680: D102 Docstring missing
681:25: E711 comparison to None should be 'if cond is None:'
684:16: E127 continuation line over-indented for visual indent
685:16: E127 continuation line over-indented for visual indent
687: D102 Docstring missing
698: D400 First line should end with '.', not 'w'
698: D205 Blank line missing between one-line summary and description
698: D208 Docstring is over-indented
710:21: E126 continuation line over-indented for hanging indent
711:28: E203 whitespace before ':'
712:17: E121 continuation line under-indented for hanging indent
725:22: E203 whitespace before ':'
726:28: E203 whitespace before ':'
727:8: E122 continuation line missing indentation or outdented
729: D400 First line should end with '.', not 'e'
729: D205 Blank line missing between one-line summary and description
750:16: E713 test for membership should be 'not in'


2: L101 copyright is missing


3: L102 copyright year is outdated, expected 2015 but got 2014


3: L102 copyright year is outdated, expected 2015 but got 2011


1: D100 Docstring missing
4: L102 copyright year is outdated, expected 2015 but got 2013
26:1: I100 Imports statements are in the wrong order. from invenio.legacy.docextract.text should be before from invenio.legacy.refextract.kbs
45: D103 Docstring missing
57: D103 Docstring missing
66:1: E302 expected 2 blank lines, found 1
66: D103 Docstring missing
74: D103 Docstring missing
78: D400 First line should end with '.', not 'e'
101: D400 First line should end with '.', not 'd'
101: D205 Blank line missing between one-line summary and description
101: D208 Docstring is over-indented
117: D103 Docstring missing
142: D400 First line should end with '.', not 'e'
142: D205 Blank line missing between one-line summary and description
142: D208 Docstring is over-indented


1: M111 unrecognized component name: general


1: D100 Docstring missing
24: D103 Docstring missing


4: L102 copyright year is outdated, expected 2015 but got 2014
28:1: E402 module level import not at top of file
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
37:1: I100 Imports statements are in the wrong order. import cgi should be before import time
37:1: E402 module level import not at top of file
38:1: E402 module level import not at top of file
39:1: I100 Imports statements are in the wrong order. import binascii should be before import subprocess
39:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. import StringIO should be before import binascii
40:1: E402 module level import not at top of file
42:1: E402 module level import not at top of file
43:1: I100 Imports statements are in the wrong order. from functools should be before from flask
43:1: I201 Missing newline before sections or imports.
43:1: E402 module level import not at top of file
44:1: E402 module level import not at top of file
45:1: I201 Missing newline before sections or imports.
45:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: I100 Imports statements are in the wrong order. from urllib should be before from six.moves.urllib.parse
47:1: I201 Missing newline before sections or imports.
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. from itertools should be before from urllib
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
133:1: E402 module level import not at top of file
136:1: F401 'pyparsing' imported but unused
136:1: E402 module level import not at top of file
137:1: I100 Imports statements are in the wrong order. from flask.ext.testing should be before import pyparsing
137:1: I201 Missing newline before sections or imports.
137:1: E402 module level import not at top of file
215: D101 Docstring missing
216: D102 Docstring missing
251:5: E731 do not assign a lambda expression, use a def
371:5: B901 blind except: statement
792:9: B901 blind except: statement
813:9: B901 blind except: statement
837:9: B901 blind except: statement
869:9: B901 blind except: statement
880:13: B901 blind except: statement
903:9: B901 blind except: statement
924:9: B901 blind except: statement
941:9: B901 blind except: statement
1191:9: B901 blind except: statement