1: D100 Docstring missing
4: L102 copyright year is outdated, expected 2015 but got 2014
22:1: E402 module level import not at top of file
23:1: E402 module level import not at top of file
24:1: I100 Imports statements are in the wrong order. import re should be before from HTMLParser
24:1: E402 module level import not at top of file
25:1: I100 Imports statements are in the wrong order. import base64 should be before import re
25:1: F401 'base64' imported but unused
25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: F401 'sys' imported but unused
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. import Queue should be before import sys
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
30:1: I100 Imports statements are in the wrong order. import signal should be before import threading
30:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be CFG_CACHEDIR, CFG_HEPDATA_FIELD, CFG_HEPDATA_INDEX, CFG_HEPDATA_PLOTSIZE, CFG_HEPDATA_THREADS_NUM, CFG_HEPDATA_URL, CFG_LOGDIR, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_TMPSHAREDDIR
32:1: F401 'CFG_CACHEDIR' imported but unused
32:1: F401 'CFG_HEPDATA_PLOTSIZE' imported but unused
32: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 datetime should be before from invenio.utils.json
43:1: I201 Missing newline before sections or imports.
43:1: E402 module level import not at top of file
44:1: I100 Imports statements are in the wrong order. import time should be before from datetime
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: I100 Imports statements are in the wrong order. from invenio.base.wrappers should be before from invenio.legacy
46:1: E402 module level import not at top of file
49:1: I100 Imports statements are in the wrong order. import cPickle should be before from invenio.base.wrappers
49:1: E402 module level import not at top of file
53:1: I101 Imported names are in the wrong order. Should be task_get_option, task_has_option, task_init, task_low_level_submission, task_read_status, task_set_option, task_sleep_now_if_required, task_update_progress, write_message
53:1: E402 module level import not at top of file
60:1: E302 expected 2 blank lines, found 1
60:38: E251 unexpected spaces around keyword / parameter equals
60:40: E251 unexpected spaces around keyword / parameter equals
60:50: E251 unexpected spaces around keyword / parameter equals
60:52: E251 unexpected spaces around keyword / parameter equals
60:64: E251 unexpected spaces around keyword / parameter equals
60:66: E251 unexpected spaces around keyword / parameter equals
60: D103 Docstring missing
68:63: E251 unexpected spaces around keyword / parameter equals
68:65: E251 unexpected spaces around keyword / parameter equals
69:51: E251 unexpected spaces around keyword / parameter equals
69:53: E251 unexpected spaces around keyword / parameter equals
76:1: E302 expected 2 blank lines, found 1
76: D290 White spaces around docstring should be trimmed.
76: D400 First line should end with '.', not 'd'
78:47: E251 unexpected spaces around keyword / parameter equals
78:49: E251 unexpected spaces around keyword / parameter equals
80:1: E302 expected 2 blank lines, found 1
80: D400 First line should end with '.', not 'r'
82:47: E251 unexpected spaces around keyword / parameter equals
82:49: E251 unexpected spaces around keyword / parameter equals
86:1: E303 too many blank lines (3)
88:17: E203 whitespace before ':'
89:11: E203 whitespace before ':'
91:11: E203 whitespace before ':'
92:11: E203 whitespace before ':'
93:10: E203 whitespace before ':'
94:15: E203 whitespace before ':'
97:1: E302 expected 2 blank lines, found 1
97: D103 Docstring missing
109:70: E201 whitespace after '('
109:69: E225 missing whitespace around operator
111:1: E302 expected 2 blank lines, found 1
111: D101 Docstring missing
112: D102 Docstring missing
119: D102 Docstring missing
120:69: E502 the backslash is redundant between brackets
121:21: E127 continuation line over-indented for visual indent
126:5: E303 too many blank lines (2)
127: D400 First line should end with '.', not 'd'
143:33: E126 continuation line over-indented for hanging indent
143:39: E203 whitespace before ':'
144:46: E203 whitespace before ':'
147:67: E251 unexpected spaces around keyword / parameter equals
147:69: E251 unexpected spaces around keyword / parameter equals
147:80: E251 unexpected spaces around keyword / parameter equals
158: D401 First line should be imperative: 'Return', not 'Returns'
158: D400 First line should end with '.', not 's'
158: D205 Blank line missing between one-line summary and description
167:63: E502 the backslash is redundant between brackets
168:62: E251 unexpected spaces around keyword / parameter equals
168:64: E251 unexpected spaces around keyword / parameter equals
168:74: E251 unexpected spaces around keyword / parameter equals
168:76: E251 unexpected spaces around keyword / parameter equals
170:34: E502 the backslash is redundant between brackets
171:79: E502 the backslash is redundant between brackets
172:17: E131 continuation line unaligned for hanging indent
172:79: E502 the backslash is redundant between brackets
173:17: E131 continuation line unaligned for hanging indent
173:37: E203 whitespace before ','
175:54: E251 unexpected spaces around keyword / parameter equals
175:56: E251 unexpected spaces around keyword / parameter equals
179:9: E303 too many blank lines (2)
182:9: E301 expected 1 blank line, found 0
202:31: E225 missing whitespace around operator
208:25: E261 at least two spaces before inline comment
212:31: E251 unexpected spaces around keyword / parameter equals
212:33: E251 unexpected spaces around keyword / parameter equals
213:32: E251 unexpected spaces around keyword / parameter equals
213:34: E251 unexpected spaces around keyword / parameter equals
215:9: E731 do not assign a lambda expression, use a def
218:39: E502 the backslash is redundant between brackets
226:33: E502 the backslash is redundant between brackets
227:88: E502 the backslash is redundant between brackets
228:40: E127 continuation line over-indented for visual indent
228:88: E502 the backslash is redundant between brackets
228:87: E211 whitespace before '['
229:40: E127 continuation line over-indented for visual indent
229:55: E502 the backslash is redundant between brackets
230:40: E127 continuation line over-indented for visual indent
230:61: E203 whitespace before ','
232:58: E251 unexpected spaces around keyword / parameter equals
232:60: E251 unexpected spaces around keyword / parameter equals
233:54: E126 continuation line over-indented for hanging indent
239:55: E251 unexpected spaces around keyword / parameter equals
239:57: E251 unexpected spaces around keyword / parameter equals
239:67: E251 unexpected spaces around keyword / parameter equals
239:69: E251 unexpected spaces around keyword / parameter equals
258:59: E502 the backslash is redundant between brackets
259:48: E127 continuation line over-indented for visual indent
259:79: E502 the backslash is redundant between brackets
259:57: E251 unexpected spaces around keyword / parameter equals
259:59: E251 unexpected spaces around keyword / parameter equals
260:48: E127 continuation line over-indented for visual indent
260:79: E502 the backslash is redundant between brackets
261:55: E127 continuation line over-indented for visual indent
268:59: E502 the backslash is redundant between brackets
269:48: E127 continuation line over-indented for visual indent
269:66: E251 unexpected spaces around keyword / parameter equals
269:68: E251 unexpected spaces around keyword / parameter equals
274: D290 White spaces around docstring should be trimmed.
274: D400 First line should end with '.', not 'g'
274: D205 Blank line missing between one-line summary and description
280:76: E502 the backslash is redundant between brackets
280:56: E251 unexpected spaces around keyword / parameter equals
280:58: E251 unexpected spaces around keyword / parameter equals
280:68: E251 unexpected spaces around keyword / parameter equals
280:70: E251 unexpected spaces around keyword / parameter equals
281:44: E127 continuation line over-indented for visual indent
281:58: E502 the backslash is redundant between brackets
281:53: E251 unexpected spaces around keyword / parameter equals
281:55: E251 unexpected spaces around keyword / parameter equals
282:21: E122 continuation line missing indentation or outdented
283:21: E122 continuation line missing indentation or outdented
284:21: E122 continuation line missing indentation or outdented
284:46: E231 missing whitespace after ','
288: D203 Expected 1 blank line *before* class docstring, found 0
288: D204 Expected 1 blank line *after* class docstring, found 0
288: D400 First line should end with '.', not 't'
288: D205 Blank line missing between one-line summary and description
292: D102 Docstring missing
296:23: E261 at least two spaces before inline comment
302:26: E261 at least two spaces before inline comment
302:27: E262 inline comment should start with '# '
310: D102 Docstring missing
314: D400 First line should end with '.', not 'n'
325:39: E251 unexpected spaces around keyword / parameter equals
325:41: E251 unexpected spaces around keyword / parameter equals
325: D401 First line should be imperative: 'Produce', not 'Produces'
325: D209 Put multi-line docstring closing quotes on separate line
325: D400 First line should end with '.', not 'L'
325: D205 Blank line missing between one-line summary and description
325: D208 Docstring is over-indented
334: D401 First line should be imperative: 'Produce', not 'Produces'
334: D400 First line should end with '.', not 'd'
334: D205 Blank line missing between one-line summary and description
334: D208 Docstring is over-indented
349:20: E261 at least two spaces before inline comment
350:9: E301 expected 1 blank line, found 0
350: D400 First line should end with '.', not 'd'
354:47: E251 unexpected spaces around keyword / parameter equals
354:49: E251 unexpected spaces around keyword / parameter equals
354:59: E251 unexpected spaces around keyword / parameter equals
354:61: E251 unexpected spaces around keyword / parameter equals
354: D400 First line should end with '.', not 't'
355:44: E251 unexpected spaces around keyword / parameter equals
355:46: E251 unexpected spaces around keyword / parameter equals
355:59: E251 unexpected spaces around keyword / parameter equals
355:61: E251 unexpected spaces around keyword / parameter equals
365:54: E251 unexpected spaces around keyword / parameter equals
365:56: E251 unexpected spaces around keyword / parameter equals
365:70: E251 unexpected spaces around keyword / parameter equals
365:72: E251 unexpected spaces around keyword / parameter equals
368:61: E502 the backslash is redundant between brackets
368:29: E251 unexpected spaces around keyword / parameter equals
368:31: E251 unexpected spaces around keyword / parameter equals
368:41: E251 unexpected spaces around keyword / parameter equals
368:43: E251 unexpected spaces around keyword / parameter equals
368:58: E251 unexpected spaces around keyword / parameter equals
368:60: E251 unexpected spaces around keyword / parameter equals
372:54: E251 unexpected spaces around keyword / parameter equals
372:56: E251 unexpected spaces around keyword / parameter equals
372:70: E251 unexpected spaces around keyword / parameter equals
372:72: E251 unexpected spaces around keyword / parameter equals
373:54: E251 unexpected spaces around keyword / parameter equals
373:56: E251 unexpected spaces around keyword / parameter equals
373:70: E251 unexpected spaces around keyword / parameter equals
373:72: E251 unexpected spaces around keyword / parameter equals
379:59: E502 the backslash is redundant between brackets
379:29: E251 unexpected spaces around keyword / parameter equals
379:31: E251 unexpected spaces around keyword / parameter equals
379:56: E251 unexpected spaces around keyword / parameter equals
379:58: E251 unexpected spaces around keyword / parameter equals
380:22: E127 continuation line over-indented for visual indent
381:24: E127 continuation line over-indented for visual indent
384:9: E303 too many blank lines (2)
387:55: E251 unexpected spaces around keyword / parameter equals
387:57: E251 unexpected spaces around keyword / parameter equals
387:67: E251 unexpected spaces around keyword / parameter equals
387:69: E251 unexpected spaces around keyword / parameter equals
404:9: E303 too many blank lines (2)
407:29: E502 the backslash is redundant between brackets
408:26: E127 continuation line over-indented for visual indent
408:57: E502 the backslash is redundant between brackets
408:35: E251 unexpected spaces around keyword / parameter equals
408:37: E251 unexpected spaces around keyword / parameter equals
409:26: E127 continuation line over-indented for visual indent
409:57: E502 the backslash is redundant between brackets
410:33: E127 continuation line over-indented for visual indent
414:9: E303 too many blank lines (3)
415:62: E251 unexpected spaces around keyword / parameter equals
415:64: E251 unexpected spaces around keyword / parameter equals
416:65: E251 unexpected spaces around keyword / parameter equals
416:67: E251 unexpected spaces around keyword / parameter equals
421:30: E251 unexpected spaces around keyword / parameter equals
421:40: E251 unexpected spaces around keyword / parameter equals
421:42: E251 unexpected spaces around keyword / parameter equals
422:27: E251 unexpected spaces around keyword / parameter equals
422:29: E251 unexpected spaces around keyword / parameter equals
425:9: E303 too many blank lines (2)
427:55: E251 unexpected spaces around keyword / parameter equals
427:57: E251 unexpected spaces around keyword / parameter equals
427:71: E251 unexpected spaces around keyword / parameter equals
427:73: E251 unexpected spaces around keyword / parameter equals
428:60: E251 unexpected spaces around keyword / parameter equals
428:62: E251 unexpected spaces around keyword / parameter equals
429:63: E251 unexpected spaces around keyword / parameter equals
429:65: E251 unexpected spaces around keyword / parameter equals
430:61: E251 unexpected spaces around keyword / parameter equals
430:63: E251 unexpected spaces around keyword / parameter equals
431:64: E251 unexpected spaces around keyword / parameter equals
431:66: E251 unexpected spaces around keyword / parameter equals
437:62: E251 unexpected spaces around keyword / parameter equals
437:64: E251 unexpected spaces around keyword / parameter equals
437:32: E222 multiple spaces after operator
438:58: E128 continuation line under-indented for visual indent
438:64: E251 unexpected spaces around keyword / parameter equals
438:66: E251 unexpected spaces around keyword / parameter equals
452:33: E251 unexpected spaces around keyword / parameter equals
452:35: E251 unexpected spaces around keyword / parameter equals
452:45: E251 unexpected spaces around keyword / parameter equals
452:47: E251 unexpected spaces around keyword / parameter equals
452:62: E251 unexpected spaces around keyword / parameter equals
452:64: E251 unexpected spaces around keyword / parameter equals
458:53: E251 unexpected spaces around keyword / parameter equals
458:55: E251 unexpected spaces around keyword / parameter equals
458:69: E251 unexpected spaces around keyword / parameter equals
458:71: E251 unexpected spaces around keyword / parameter equals
461:29: E251 unexpected spaces around keyword / parameter equals
461:31: E251 unexpected spaces around keyword / parameter equals
461:41: E251 unexpected spaces around keyword / parameter equals
461:43: E251 unexpected spaces around keyword / parameter equals
465:59: E251 unexpected spaces around keyword / parameter equals
465:61: E251 unexpected spaces around keyword / parameter equals
466:62: E251 unexpected spaces around keyword / parameter equals
466:64: E251 unexpected spaces around keyword / parameter equals
468:29: E251 unexpected spaces around keyword / parameter equals
468:31: E251 unexpected spaces around keyword / parameter equals
468:41: E251 unexpected spaces around keyword / parameter equals
468:43: E251 unexpected spaces around keyword / parameter equals
472:9: E303 too many blank lines (2)
475:17: E251 unexpected spaces around keyword / parameter equals
475:19: E251 unexpected spaces around keyword / parameter equals
475:29: E251 unexpected spaces around keyword / parameter equals
475:31: E251 unexpected spaces around keyword / parameter equals
478:71: E251 unexpected spaces around keyword / parameter equals
478:73: E251 unexpected spaces around keyword / parameter equals
479:71: E251 unexpected spaces around keyword / parameter equals
479:73: E251 unexpected spaces around keyword / parameter equals
483: D290 White spaces around docstring should be trimmed.
483: D400 First line should end with '.', not 's'
523:13: E303 too many blank lines (2)
528:36: E251 unexpected spaces around keyword / parameter equals
528:38: E251 unexpected spaces around keyword / parameter equals
529:36: E251 unexpected spaces around keyword / parameter equals
529:38: E251 unexpected spaces around keyword / parameter equals
531:9: E731 do not assign a lambda expression, use a def
537:69: E502 the backslash is redundant between brackets
538:68: E502 the backslash is redundant between brackets
546:9: E731 do not assign a lambda expression, use a def
551:9: E731 do not assign a lambda expression, use a def
556:33: E251 unexpected spaces around keyword / parameter equals
556:35: E251 unexpected spaces around keyword / parameter equals
557:33: E251 unexpected spaces around keyword / parameter equals
557:35: E251 unexpected spaces around keyword / parameter equals
559:64: E502 the backslash is redundant between brackets
560:25: E127 continuation line over-indented for visual indent
560:64: E502 the backslash is redundant between brackets
561:25: E127 continuation line over-indented for visual indent
562:25: E127 continuation line over-indented for visual indent
562:68: E502 the backslash is redundant between brackets
568:9: B901 blind except: statement
572:9: E303 too many blank lines (2)
578:73: E502 the backslash is redundant between brackets
578:68: E251 unexpected spaces around keyword / parameter equals
578:70: E251 unexpected spaces around keyword / parameter equals
579:25: E126 continuation line over-indented for hanging indent
579:43: E502 the backslash is redundant between brackets
580:29: E131 continuation line unaligned for hanging indent
580:44: E502 the backslash is redundant between brackets
581:44: E502 the backslash is redundant between brackets
582:45: E502 the backslash is redundant between brackets
583:46: E502 the backslash is redundant between brackets
584:68: E502 the backslash is redundant between brackets
585:29: E126 continuation line over-indented for hanging indent
587:73: E502 the backslash is redundant between brackets
587:68: E251 unexpected spaces around keyword / parameter equals
587:70: E251 unexpected spaces around keyword / parameter equals
588:25: E126 continuation line over-indented for hanging indent
588:45: E502 the backslash is redundant between brackets
589:29: E131 continuation line unaligned for hanging indent
589:44: E502 the backslash is redundant between brackets
590:44: E502 the backslash is redundant between brackets
591:44: E502 the backslash is redundant between brackets
592:68: E502 the backslash is redundant between brackets
593:29: E126 continuation line over-indented for hanging indent
598:47: E251 unexpected spaces around keyword / parameter equals
598:49: E251 unexpected spaces around keyword / parameter equals
603: D102 Docstring missing
605:53: E502 the backslash is redundant between brackets
606:17: E122 continuation line missing indentation or outdented
606:66: E203 whitespace before ','
607:17: E122 continuation line missing indentation or outdented
611:27: F841 local variable 'e' is assigned to but never used
612:96: E225 missing whitespace around operator
617: D401 First line should be imperative: 'Generate', not 'Generates'
617: D400 First line should end with '.', not 'e'
617: D205 Blank line missing between one-line summary and description
624:39: E502 the backslash is redundant between brackets
625:27: E127 continuation line over-indented for visual indent
625:80: E502 the backslash is redundant between brackets
626:32: E127 continuation line over-indented for visual indent
627:54: E502 the backslash is redundant between brackets
630:41: E128 continuation line under-indented for visual indent
631:60: E502 the backslash is redundant between brackets
632:45: E126 continuation line over-indented for hanging indent
632:74: E502 the backslash is redundant between brackets
633:66: E502 the backslash is redundant between brackets
635:77: E502 the backslash is redundant between brackets
636:43: E127 continuation line over-indented for visual indent
636:82: E502 the backslash is redundant between brackets
638:77: E502 the backslash is redundant between brackets
639:43: E127 continuation line over-indented for visual indent
640:26: E261 at least two spaces before inline comment
642: D400 First line should end with '.', not 't'
642: D205 Blank line missing between one-line summary and description
642: D208 Docstring is over-indented
646:17: E261 at least two spaces before inline comment
654:80: E502 the backslash is redundant between brackets
655:36: E127 continuation line over-indented for visual indent
656:29: E203 whitespace before ':'
657:32: E203 whitespace before ':'
666:35: E261 at least two spaces before inline comment
673:66: E502 the backslash is redundant between brackets
674:35: E127 continuation line over-indented for visual indent
678:60: E251 unexpected spaces around keyword / parameter equals
678:62: E251 unexpected spaces around keyword / parameter equals
679:48: E251 unexpected spaces around keyword / parameter equals
679:50: E251 unexpected spaces around keyword / parameter equals
679:65: E251 unexpected spaces around keyword / parameter equals
679:67: E251 unexpected spaces around keyword / parameter equals
683: D401 First line should be imperative: 'Create', not 'Creates'
683: D400 First line should end with '.', not 'd'
698:87: E502 the backslash is redundant between brackets
699:26: E127 continuation line over-indented for visual indent
699:80: E502 the backslash is redundant between brackets
700:25: E127 continuation line over-indented for visual indent
700:36: E502 the backslash is redundant between brackets
701:74: E502 the backslash is redundant between brackets
702:66: E127 continuation line over-indented for visual indent
702:78: E502 the backslash is redundant between brackets
702:70: E251 unexpected spaces around keyword / parameter equals
702:72: E251 unexpected spaces around keyword / parameter equals
703:66: E127 continuation line over-indented for visual indent
703:70: E251 unexpected spaces around keyword / parameter equals
703:72: E251 unexpected spaces around keyword / parameter equals
712:35: E502 the backslash is redundant between brackets
713:25: E127 continuation line over-indented for visual indent
713:77: E502 the backslash is redundant between brackets
714:25: E127 continuation line over-indented for visual indent
714:81: E502 the backslash is redundant between brackets
715:25: E127 continuation line over-indented for visual indent
715:27: E222 multiple spaces after operator
735:9: E303 too many blank lines (2)
739:55: E231 missing whitespace after ':'
753:25: E251 unexpected spaces around keyword / parameter equals
753:27: E251 unexpected spaces around keyword / parameter equals
759:27: E261 at least two spaces before inline comment
762:26: E261 at least two spaces before inline comment
770:39: E203 whitespace before ':'
770:65: E203 whitespace before ':'
778:40: E203 whitespace before ':'
778:67: E203 whitespace before ':'
788:32: E261 at least two spaces before inline comment
800:20: E261 at least two spaces before inline comment
804:29: E261 at least two spaces before inline comment
818:28: E251 unexpected spaces around keyword / parameter equals
818:30: E251 unexpected spaces around keyword / parameter equals
819:28: E261 at least two spaces before inline comment
824:27: E261 at least two spaces before inline comment
825:28: E261 at least two spaces before inline comment
859:50: E203 whitespace before ':'
866:42: E203 whitespace before ':'
874:9: B901 blind except: statement
879: D209 Put multi-line docstring closing quotes on separate line
879: D400 First line should end with '.', not 't'
879: D205 Blank line missing between one-line summary and description
886:68: E502 the backslash is redundant between brackets
887:21: E126 continuation line over-indented for hanging indent
887:50: E502 the backslash is redundant between brackets
888:25: E131 continuation line unaligned for hanging indent
888:72: E502 the backslash is redundant between brackets
889:25: E131 continuation line unaligned for hanging indent
889:69: E502 the backslash is redundant between brackets
890:25: E131 continuation line unaligned for hanging indent
890:58: E502 the backslash is redundant between brackets
891:25: E131 continuation line unaligned for hanging indent
891:66: E502 the backslash is redundant between brackets
892:31: E126 continuation line over-indented for hanging indent
892:51: E502 the backslash is redundant between brackets
894:27: F841 local variable 'e' is assigned to but never used
895:25: E702 multiple statements on one line (semicolon)
899:5: E303 too many blank lines (3)
899: D401 First line should be imperative: 'Write', not 'Writes'
899: D209 Put multi-line docstring closing quotes on separate line
899: D202 No blank lines allowed *after* method docstring, found 1
899: D400 First line should end with '.', not 's'
899: D205 Blank line missing between one-line summary and description
899: D208 Docstring is over-indented
907:81: E502 the backslash is redundant between brackets
907:51: E251 unexpected spaces around keyword / parameter equals
907:53: E251 unexpected spaces around keyword / parameter equals
907:69: E251 unexpected spaces around keyword / parameter equals
907:71: E251 unexpected spaces around keyword / parameter equals
908:49: E127 continuation line over-indented for visual indent
908:52: E251 unexpected spaces around keyword / parameter equals
908:54: E251 unexpected spaces around keyword / parameter equals
916:81: E502 the backslash is redundant between brackets
916:52: E251 unexpected spaces around keyword / parameter equals
916:54: E251 unexpected spaces around keyword / parameter equals
916:69: E251 unexpected spaces around keyword / parameter equals
916:71: E251 unexpected spaces around keyword / parameter equals
917:50: E127 continuation line over-indented for visual indent
917:53: E251 unexpected spaces around keyword / parameter equals
917:55: E251 unexpected spaces around keyword / parameter equals
924:9: E303 too many blank lines (2)
926:1: E302 expected 2 blank lines, found 1
926: D101 Docstring missing
927: D102 Docstring missing
931:36: E261 at least two spaces before inline comment
934: D102 Docstring missing
955:5: E303 too many blank lines (2)
955: D102 Docstring missing
962: D102 Docstring missing
966:20: E222 multiple spaces after operator
973:5: E303 too many blank lines (2)
973: D102 Docstring missing
985:5: E303 too many blank lines (2)
985: D102 Docstring missing
994: D102 Docstring missing
999:1: E303 too many blank lines (3)
1002:1: E302 expected 2 blank lines, found 3
1002: D290 White spaces around docstring should be trimmed.
1002: D203 Expected 1 blank line *before* class docstring, found 0
1002: D204 Expected 1 blank line *after* class docstring, found 0
1002: D400 First line should end with '.', not 's'
1004: D400 First line should end with '.', not 'r'
1004: D200 One-line docstring should not occupy 3 lines
1014: D102 Docstring missing
1021:39: E261 at least two spaces before inline comment
1049: D102 Docstring missing
1053: D102 Docstring missing
1059: D102 Docstring missing
1063: D102 Docstring missing
1080:16: E714 test for object identity should be 'is not'
1088:1: E302 expected 2 blank lines, found 1
1088: D101 Docstring missing
1089: D102 Docstring missing
1095: D102 Docstring missing
1104: D102 Docstring missing
1110: D102 Docstring missing
1114: D102 Docstring missing
1120: D102 Docstring missing
1125: D101 Docstring missing
1127: D102 Docstring missing
1131: D102 Docstring missing
1134:24: E201 whitespace after '['
1136: D102 Docstring missing
1142: D102 Docstring missing
1145: D102 Docstring missing
1150: D102 Docstring missing
1153:1: E302 expected 2 blank lines, found 1
1153: D101 Docstring missing
1154: D102 Docstring missing
1160: D102 Docstring missing
1163: D400 First line should end with '.', not 'x'
1167: D102 Docstring missing
1173:5: E303 too many blank lines (2)
1173: D400 First line should end with '.', not 'e'
1178: D102 Docstring missing
1181: D102 Docstring missing
1184: D102 Docstring missing
1188:5: E303 too many blank lines (2)
1188: D102 Docstring missing
1189:30: E711 comparison to None should be 'if cond is not None:'
1194: D102 Docstring missing
1196:30: E711 comparison to None should be 'if cond is not None:'
1202:5: E303 too many blank lines (2)
1202: D102 Docstring missing
1207:30: E711 comparison to None should be 'if cond is not None:'
1212: D102 Docstring missing
1213:30: E711 comparison to None should be 'if cond is not None:'
1244: D102 Docstring missing
1245:30: E711 comparison to None should be 'if cond is not None:'
1250:1: E302 expected 2 blank lines, found 1
1250: D103 Docstring missing
1253:1: E302 expected 2 blank lines, found 1
1253: D301 Use r""" if any backslashes in a docstring
1253: D400 First line should end with '.', not 'g'
1253: D200 One-line docstring should not occupy 2 lines
1271:1: E302 expected 2 blank lines, found 1
1271: D103 Docstring missing
1275:65: E225 missing whitespace around operator
1283:5: E303 too many blank lines (2)
1286:5: E303 too many blank lines (2)
1287:5: E731 do not assign a lambda expression, use a def
1290:67: E502 the backslash is redundant between brackets
1295:9: E303 too many blank lines (2)
1295:58: E251 unexpected spaces around keyword / parameter equals
1295:60: E251 unexpected spaces around keyword / parameter equals
1304:23: E222 multiple spaces after operator
1324:1: E303 too many blank lines (3)
1324: D401 First line should be imperative: 'retrieve', not 'retrieves'
1324: D400 First line should end with '.', not 'e'
1331: D290 White spaces around docstring should be trimmed.
1331: D400 First line should end with '.', not 's'
1331: D200 One-line docstring should not occupy 2 lines
1336:1: E302 expected 2 blank lines, found 1
1336: D401 First line should be imperative: 'Return', not 'Returns'
1336: D290 White spaces around docstring should be trimmed.
1336: D400 First line should end with '.', not 'd'
1336: D200 One-line docstring should not occupy 2 lines
1341:1: E302 expected 2 blank lines, found 1
1341: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
1341: D400 First line should end with '.', not 'n'
1348:5: B901 blind except: statement
1356:1: E302 expected 2 blank lines, found 1
1356: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
1356: D205 Blank line missing between one-line summary and description
1376:9: B901 blind except: statement
1384:9: B901 blind except: statement
1390:1: E302 expected 2 blank lines, found 1
1390: D400 First line should end with '.', not 'd'
1390: D205 Blank line missing between one-line summary and description
1402:1: E302 expected 2 blank lines, found 1
1402: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
1402: D209 Put multi-line docstring closing quotes on separate line
1402: D400 First line should end with '.', not 'd'
1414:5: E301 expected 1 blank line, found 0
1416:12: E713 test for membership should be 'not in'
1420:116: E502 the backslash is redundant between brackets
1420:34: E203 whitespace before ','
1421:20: E128 continuation line under-indented for visual indent
1423:1: E302 expected 2 blank lines, found 1
1423: D401 First line should be imperative: 'Return', not 'Returns'
1423: D400 First line should end with '.', not 'n'
1423: D208 Docstring is over-indented
1433:1: E302 expected 2 blank lines, found 1
1433: D400 First line should end with '.', not 'd'
1433: D205 Blank line missing between one-line summary and description
1446:13: E126 continuation line over-indented for hanging indent
1450:1: E302 expected 2 blank lines, found 1
1450: D209 Put multi-line docstring closing quotes on separate line
1450: D400 First line should end with '.', not 'r'
1450: D205 Blank line missing between one-line summary and description
1450: D208 Docstring is over-indented
1461: D103 Docstring missing
1465:40: E261 at least two spaces before inline comment
1468: D401 First line should be imperative: 'Retrieve', not 'Retrieves'
1468: D400 First line should end with '.', not 'r'
1468: D205 Blank line missing between one-line summary and description
1476:25: E261 at least two spaces before inline comment
1484:1: E303 too many blank lines (3)
1484: D201 No blank lines allowed *before* function docstring, found 1
1484: D202 No blank lines allowed *after* function docstring, found 2
1484: D400 First line should end with '.', not 'o'
1484: D205 Blank line missing between one-line summary and description
1484: D208 Docstring is over-indented
1512:5: E303 too many blank lines (2)
1518:5: E731 do not assign a lambda expression, use a def
1519:66: E231 missing whitespace after ','
1519:29: E251 unexpected spaces around keyword / parameter equals
1519:31: E251 unexpected spaces around keyword / parameter equals
1532:5: F401 'tempfile' imported but unused
1563:64: E502 the backslash is redundant between brackets
1563:61: E251 unexpected spaces around keyword / parameter equals
1563:63: E251 unexpected spaces around keyword / parameter equals
1564:44: E127 continuation line over-indented for visual indent
1565:73: E502 the backslash is redundant between brackets
1565:70: E251 unexpected spaces around keyword / parameter equals
1565:72: E251 unexpected spaces around keyword / parameter equals
1566:44: E127 continuation line over-indented for visual indent
1591: D400 First line should end with '.', not 'e'
1598:1: E302 expected 2 blank lines, found 1
1598: D209 Put multi-line docstring closing quotes on separate line
1598: D400 First line should end with '.', not ','
1598: D205 Blank line missing between one-line summary and description
1612:5: E303 too many blank lines (2)
1620:1: E302 expected 2 blank lines, found 1
1620: D290 White spaces around docstring should be trimmed.
1620: D301 Use r""" if any backslashes in a docstring
1620: D400 First line should end with '.', not 'e'
1620: D205 Blank line missing between one-line summary and description
1641:1: E302 expected 2 blank lines, found 1
1641: D205 Blank line missing between one-line summary and description
1641: D208 Docstring is over-indented
1646:35: E251 unexpected spaces around keyword / parameter equals
1646:37: E251 unexpected spaces around keyword / parameter equals
1647:13: E128 continuation line under-indented for visual indent
1647:30: E251 unexpected spaces around keyword / parameter equals
1647:32: E251 unexpected spaces around keyword / parameter equals
1648:13: E128 continuation line under-indented for visual indent
1648:24: E251 unexpected spaces around keyword / parameter equals
1648:26: E251 unexpected spaces around keyword / parameter equals
1654:13: E128 continuation line under-indented for visual indent
1654:35: E502 the backslash is redundant between brackets
1654:32: E251 unexpected spaces around keyword / parameter equals
1654:34: E251 unexpected spaces around keyword / parameter equals
1655:1: E128 continuation line under-indented for visual indent
1662:13: E128 continuation line under-indented for visual indent
1663:13: E128 continuation line under-indented for visual indent
1664:18: E128 continuation line under-indented for visual indent
1664:19: E201 whitespace after '['
1664:59: E202 whitespace before ']'
1665:13: E128 continuation line under-indented for visual indent
1665:57: E251 unexpected spaces around keyword / parameter equals
1665:59: E251 unexpected spaces around keyword / parameter equals
1667:13: E128 continuation line under-indented for visual indent
1667:25: E251 unexpected spaces around keyword / parameter equals
1667:27: E251 unexpected spaces around keyword / parameter equals
1670: D400 First line should end with '.', not 's'
1670: D205 Blank line missing between one-line summary and description
1684:5: E303 too many blank lines (2)
1685:71: E502 the backslash is redundant between brackets
1685:43: E251 unexpected spaces around keyword / parameter equals
1685:45: E251 unexpected spaces around keyword / parameter equals
1685:60: E251 unexpected spaces around keyword / parameter equals
1685:62: E251 unexpected spaces around keyword / parameter equals
1686:41: E127 continuation line over-indented for visual indent
1686:44: E251 unexpected spaces around keyword / parameter equals
1686:46: E251 unexpected spaces around keyword / parameter equals
1696:1: E302 expected 2 blank lines, found 1
1696: D400 First line should end with '.', not 's'
1703:177: E251 unexpected spaces around keyword / parameter equals
1703:179: E251 unexpected spaces around keyword / parameter equals
1703:214: E251 unexpected spaces around keyword / parameter equals
1703:216: E251 unexpected spaces around keyword / parameter equals
1703: D103 Docstring missing
1709:9: B901 blind except: statement
1720:51: E251 unexpected spaces around keyword / parameter equals
1720:53: E251 unexpected spaces around keyword / parameter equals
1721:175: E202 whitespace before ')'
1724:85: E502 the backslash is redundant between brackets
1725:39: E127 continuation line over-indented for visual indent
1729:84: E502 the backslash is redundant between brackets
1730:35: E127 continuation line over-indented for visual indent
1734:13: E303 too many blank lines (2)
1737:34: E225 missing whitespace around operator
1760:22: E261 at least two spaces before inline comment
1760:23: E262 inline comment should start with '# '
1763:1: E302 expected 2 blank lines, found 1
1763: D101 Docstring missing
1764: D102 Docstring missing
1779: D102 Docstring missing
1780:88: E502 the backslash is redundant between brackets
1781:35: E127 continuation line over-indented for visual indent
1781:94: E502 the backslash is redundant between brackets
1782:35: E127 continuation line over-indented for visual indent
1782:134: E251 unexpected spaces around keyword / parameter equals
1782:136: E251 unexpected spaces around keyword / parameter equals
1784:1: E302 expected 2 blank lines, found 1
1784: D203 Expected 1 blank line *before* class docstring, found 0
1784: D204 Expected 1 blank line *after* class docstring, found 0
1784: D400 First line should end with '.', not 's'
1786: D102 Docstring missing
1792: D102 Docstring missing
1798:1: E302 expected 2 blank lines, found 1
1798: D209 Put multi-line docstring closing quotes on separate line
1798: D203 Expected 1 blank line *before* class docstring, found 0
1798: D205 Blank line missing between one-line summary and description
1798: D208 Docstring is over-indented
1802: D102 Docstring missing
1806: D102 Docstring missing
1809: D102 Docstring missing
1812: D102 Docstring missing
1816: D102 Docstring missing
1820: D102 Docstring missing
1823:1: E302 expected 2 blank lines, found 1
1823: D301 Use r""" if any backslashes in a docstring
1823: D400 First line should end with '.', not 'e'
1823: D208 Docstring is over-indented
1823: D200 One-line docstring should not occupy 2 lines
1831:1: E302 expected 2 blank lines, found 1
1831: D400 First line should end with '.', not 'd'
1831: D200 One-line docstring should not occupy 2 lines
1838:1: E302 expected 2 blank lines, found 1
1838: D103 Docstring missing
1845:5: E303 too many blank lines (2)
1849:30: E203 whitespace before ':'
1850:36: E203 whitespace before ':'
1851:37: E203 whitespace before ':'
1852:35: E203 whitespace before ':'
1876:5: E303 too many blank lines (2)
1884:5: E303 too many blank lines (2)
1887:200: E251 unexpected spaces around keyword / parameter equals
1887:202: E251 unexpected spaces around keyword / parameter equals
1909:9: E303 too many blank lines (2)
1918:127: E251 unexpected spaces around keyword / parameter equals
1918:129: E251 unexpected spaces around keyword / parameter equals
1918:156: E251 unexpected spaces around keyword / parameter equals
1918:158: E251 unexpected spaces around keyword / parameter equals
1923:63: E502 the backslash is redundant between brackets
1924:23: E127 continuation line over-indented for visual indent
1928:54: E251 unexpected spaces around keyword / parameter equals
1928:56: E251 unexpected spaces around keyword / parameter equals
1932:55: E251 unexpected spaces around keyword / parameter equals
1932:57: E251 unexpected spaces around keyword / parameter equals
1934:64: E502 the backslash is redundant between brackets
1935:23: E127 continuation line over-indented for visual indent
1954:9: F841 local variable 'index_tasknum' is assigned to but never used
1958:75: E502 the backslash is redundant between brackets
1959:24: E127 continuation line over-indented for visual indent
1959:76: E502 the backslash is redundant between brackets
1960:53: E502 the backslash is redundant between brackets
1961:59: E502 the backslash is redundant between brackets
1962:75: E502 the backslash is redundant between brackets
1963:23: E127 continuation line over-indented for visual indent
1964:75: E502 the backslash is redundant between brackets
1965:23: E127 continuation line over-indented for visual indent
1970: D401 First line should be imperative: 'Create', not 'Creates'
1970: D400 First line should end with '.', not 'a'
1970: D205 Blank line missing between one-line summary and description


Okay, it's a problem on my end. My IDE didn't automatically regenerate the resources when I created the new APK. I have updated the APKs, so this should be fixed.
Thanks for reporting this!


Exactly. In your original implementation of nextTuple, the spout thread is
almost always running the nextTuple method (if there is a continous
incoming messages flow). That's situation make ack and fail methods are
waiting until nextTuple finish (like says the spout documentation)

2015-03-04 16:48 GMT+01:00 ppat <notifications@github.com>:

> Thinking about it more... I think I understand what you're saying, you're
> saying that ack/fail/etc is starved due to the while loop in the nextTuple.
> I think changing the while condition to just an if condition will help in
> there. Let me think about this some more.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/frascuchon/storm-rabbitmq/commit/a3f317078b27bed8b4f1944e095b29d957bbfda2#commitcomment-10032207>
> .
>


I would suggest reverting my commit, it is redundant because it was based on an older version.
It is even the case that ${libnabo_LIBRARIES} would have been the right variable.

That I used ${NABO_LIBRARY} instead is probably causing the problem with a static libnabo as discovered here:

http://jenkins.ros.org/job/devel-indigo-libpointmatcher/ARCH_PARAM=amd64,UBUNTU_PARAM=trusty,label=devel/120/changes

Sorry for the trouble. In future please don't merge PR s from me that quick :) - apparently it is a bad idea.


nice


gigiygy


:eyes: you may want to visit that :page_facing_up: homepage.


I was being more generic anticipating there may be other edge constraints in the future... but this is fine :)


As you don't necessarily know what will be the last thing in the content sidebar, would this be better done as bottom padding on the content sidebar itself? It's 10em in the default layout.scss, this was presumably overridden for oxfordshire previously due to it not being a full screen map, but removing more overrides is probably good!


ok, will check it now.
P.s. I've been thinking about LCD freq too. There's commit to change this freq via sysfs: https://github.com/ChronoMonochrome/Chrono_Kernel/commit/1fd2308ffeb8e8f3ff5ef3f6dbb3abb40220125c
but I'm not sure whether it actually works, because I don't have tearings at all with original LCDCLK freq.


Pretty sure you meant "TRIANGLE_MESH"


This method seems suspect for a couple of reasons:

  1. The method is called `_stopPropagation()` but does not actually appear to prevent any event from being propagated.
  2. The method does send a simulated `click` and `mouseup` event within a `setTimeout()`, which seems like a hack upon a hack.

There are probably good reasons for this, but unfortunately I couldn't understand the [link](http://stackoverflow.com/questions/22406505/jquery-ui-datepicker-next-and-prev-buttons-only-have-one-ancestor-e-target-p) you posted either, so could really do with an explanation of what's happening here, and why we're having to resort to trickery.


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


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

There are valid reasons for not wanting to send `If-None-Match` and `If-Modified-Since` in the request. A user should be able to activate this feature on a per-url basis. There are several ways to accomplish this, but I think the easiest is to activate the feature with key-value pairs in the metadata that are distinct from the HTTP header fields which were gathered from a previous fetch.

> 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.

I was thinking that metadata would be stored as index fields, but after looking more closely at the elasticsearch spout, it looks like we're using a `key:value\n` serialization method. So this isn't actually a problem right now. However, if we *were* to store metadata (such as HTTP headers) in their own index fields, those names will need to be JSON-compatible. The most likely candidate for `last-modified` would then be `lastModified`.

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

Because ETag generation has no standard in the HTTP specification, and some websites don't return a simple hash of the content. Occasionally this value is a revision number, in which case it could be useful to compare these revisions. Overwriting the value would prevent this.


yay


nullable = false?


I don't mean to be nit-picky, but the `set_under('w')` and `set_over('w')` methods of the colormap are no-longer being used in the test.  Actually, I am not familiar with the `values` keyword argument of `colorbar`, but it is changing the meaning of the colors in the lower and upper extensions, is this the expected behavior?


Note this is actually slightly different check... `sanityCheck` says "every producer has a consumer". This check says "every LMP has a LMC" -- it's more specific.

We could

1. add the more specific check to `sanityCheckEdges`, or
2. we could re-add this code.
3. (Or maybe we could get rid of the differences between consumers, where appropriate. Aren't they all ultimately the same?)

 Up to you.


This is super dangerous. stratajs can push breaking changes and PCM would pull it in.


just another example, any pattern like this will break: `a/**/foo.js`. The parent is returned as `a/**/foo.js`.


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


I support this primarily since if you're going to `push!` a splatted collection onto something, you should be using `append!` anyway, which handles the zero elements case correctly.


It's not ideal for us, but issues are specific to a repository, so ampersand and ampersand-models each have their own list of issues (and wiki.) You can cross reference by adding user/repo, e.g. AmpersandTarski/ampersand#35


That's great Chrono !!

Very weird.. with org freq i've even tearings with APE DDR 100% and even on min cpu 600Mhz !! I believe smthg is wrong with my sources :-( (but as i said.. with plugged charger it's ok.. that's what i can't understand ... )


I just want to know where this comes from ?


maybe you can load the bundle which registers extension listener services later than your own? If you use symfony2 it is a matter of order you load bundles into app kernel. Otherwise, entities which are persisted on flush, may have their dates set manually. This is wrong of course since it introduces a BC break, but it fixes another issue, if there is a simple solution like loading extension listeners later. then maybe that won't be a big problem. What do you think?


thanks!


why do we need this ?


... "(ie not a "large" country)" to be explicit


test


Nice form.


Which freq do you mean by original? 4992..(which is by samsung), or increased freq by TC?


@antoniogarrote Thank you.


Nice.


yeah 4992 ! But with 62400000 absoulutely smooth (even without charger) .. that' creazy ..


rax retry tests


Will checkstyle complain about this not having a comment?


I am on a mac OSx 10.8.5

On Tue, Mar 3, 2015 at 11:59 AM David Mermelstein <damerms@gmail.com> wrote:

> Sorry I copied what you sent me. v0.12.0 is what I get.
> ᐧ
>
> Thanks
> David
>
> Shaping Connected Experiences
>
> <http://davidmermelstein.dunked.com/>  Portfolio
> <http://davidmermelstein.com/>     <http://www.linkedin.com/in/merms>
> Linkedin <http://www.linkedin.com/in/merms>    Twitter
> <http://www.twitter.com/dmerms>      773.744.0760
>
> On Tue, Mar 3, 2015 at 11:33 AM, Martin N. <notifications@github.com>
> wrote:
>
>> Just "node", a space, "--version". That should print out the node.js
>> version you're using.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/AVGP/susi/commit/fa59094a26641840530c9fef5110fa1f75d7b7e0#commitcomment-10012101>
>> .
>>
>
>


Hmmm, I can't get this to work.
I inserted this in my md1Overlay.kll

DebounceDivThreshold = 0xFFFFFFFF

I get a parsing error:

Error parsing home/blais/src/infinity/controller/kll/layouts/config/md1Overlay.kll. should have reached <EOF>: 11,1-11,12: USBCode 'U"Function2"'

Notes:
- I pulled controller
- I pulled controller/kll

Just reporting for now (too busy  at work) will peek at it closerr later on.


LOLLL ^ Colin.


Please write down meaningful GIT commit messages!


@JRHerlehy I've been working on some modifications to your tiny leaders code, but before I go too far I wanted to see what your plans were in regards to any future updates you have planned. Email may be a better way to accomplish these communications. my address is nick.myers46_@_gmail.com (take the underscores out).


You're also using CFG_WITH_FORTUNA_PRNG in the code, which is not visible in the configuration. Also we don't know if both may be enabled at the same time.
A solution to this may be to *always* set *all* configuration variables in mk/config.mk when we're adding such variables. Then, `mk/config.mk` would be a central location where default values would be properly shown and documented.
So,  for the current patch I would add:
```
# PRNG <blah blah>
# When all PRNGs are disabled (default). use platform-specific
# implementation: hw_get_random_byte()
# <Also say what happens when several PRNGs are enabled...>
CFG_WITH_YARROW_PRNG ?= n
CFG_WITH_FORTUNA_PRNG ?= n
```


then also the `unittest` import is missing.


For many MVC applications, the default route works fine. You'll learn later in this tutorial to pass data using the model binder, and you won't have to  modify the default route for that.

In these examples the controller has been doing the "VC" portion  of MVC — that is, the view and controller work. The controller is returning HTML  directly. Ordinarily you don't want controllers returning HTML directly, since  that becomes very cumbersome to code. Instead we'll typically use a separate  view template file to help generate the HTML response. Let's look next at how  we can do this.


Tidy solution to the open/closed project requirement. 1/3


In addition, don't add the generated files such as `hello/hello` into GIT repository.


@Tharper84 So I think what you have is a good start. However, we will need to estimate autocorrelation and effective size for each parameter of each chain (i.e chain 1 estimation of theta1). Additionally, we should also probably estimate the 95% HPD (highest posterior density) region for each parameter. I'm not sure if there is a function in R to do this, or if you will have to come up with something manually. Also, try writing these r functions in a .Rmd (R markdown) or .Rnw file, so that we can have reproducible research. I think Rob mentioned that a portion of the grade was doing this.

@KhatriVivek I'm still wrapping up the code to produce the MCMC estimates. Almost done. I think once you are done reading through the code, you can let me know if you see any problems. I will read about this too, but can you read about implementation of reversible jump MCMC in the context of mixture models? I'm hopeful that we can find a good algorithm. I'm not sure what your question is regarding input X.


Tidy solution to the open/closed project requirement. 2/3


Hi, if I build the project with QtCreator starting from qwtplot3d.pro then I get a bunch of errors like:
qwt3d_types.h:247: error: C3861: 'isnan': identifier not found
It seems the check for Q_OS_WIN failed at the beginning of that file.


see what you mean thx


just ignore this


Tidy solution to the open/closed project requirement. 3/3


its just undoing last commit


Semantics- "Closed" might make more sense than "Filled" because a project lead could opt to close a project without filling it. Maybe they just change their mind. Not required though.


Doze is working fine on my end, what exactly are the issues that you have noticed? I will watch for it and advise my testers.


This was fixed later in a PR :P


Is it imperative to need to pass the Game object here?


changed server.js endpoint to retrieve response data from UserCtrlr/getUser


I made the same comment: https://github.com/GoodBoyDigital/pixi.js/pull/1484/files#r25791929

we are totally on the same wavelength lol


I agreed with @jbech-linaro.


So, then it's "ok". I mean that's why TC did that fix. Btw, instant use of this freq is unsafe - after long usage it ends up with graphical glitches in the form of grey lines, filling the display sometimes :/ Polishvodka wrote about it (in polish forum).
As for this build - have got random reboot after loading to system, will upload last_kmsg soon.


And you're sure `component-docs { display: none; }` isn't being overridden somewhere down the line? It it layout FOUC?


` document.GetLinkedDocumentIds()` extract to a local variable if the result is expected to be the same list of DocumentId


This could be all on the return line.


I think that in this case needkey should be used. perhaps only one CP element had an override for the pssh and the other keysystems are using the pssh from the media.


Excellent!  Thanks for the feedback.


The connection I think is strong, you shall not return True. So why is it bad style?


Excellent, thanks for the feedback.

On Wed, Mar 4, 2015 at 9:05 AM, Sevgimontix <notifications@github.com>
wrote:

> Works!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wikkawik/WikkaWiki/commit/417296beda3762ac5a38ea9fed6f0a4486c1bfa2#commitcomment-10032640>
> .
>


Sorry.

$ npm install -g grunt-cli

Gives me the same error.

On Sun, Mar 1, 2015 at 4:44 PM Martin N. <notifications@github.com> wrote:

> Hm, are you running this (old) version of SuSi or did you accidentally put
> this as a comment on this commit?
>
> The error seems to be npm-related. Can you install other modules globally?
> For instance try
>
> $ npm install -g grunt-cli
>
> does that give you the same error?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AVGP/susi/commit/fa59094a26641840530c9fef5110fa1f75d7b7e0#commitcomment-9977182>
> .
>


OK, I will pay attention about it next time.


no I thought you provided the real deal example :O


Okay so not inside the test class, good to know.


Recommend leaving since CurrentSkill is a join table for Employee and Skill.


I wonder if this should be called `edition` instead?

We only ever expect to describe dependencies from an edition to another object


what????


where do I must to put these codes? command line? which command line? actually I am beginner and use easyPHP and its engine. How I can apply encrypt program?


**Troubleshooting:** "./osbuild build" might raise some errors if you are behind a proxy. A quick work-around is to remove the modules that are causing the problem from build/modules.json (most often sugar-web, sugar-web-template, and sugar-web-test).


May not be needed.


Taken from the docs, but you're right


Don't do this.  cfn-init will fail silently.


Same as CurrentSkill.


I ran into this so I changed PHP_INT_MAX * -1 to PHP_INT_MIN. The lint check complains:

    Parse error: parse error, expecting `','' or `';'' in /Users/franco/Documents/opnsense/core/src/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/IntegerField.php on line 55
    Errors parsing /Users/franco/Documents/opnsense/core/src/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/IntegerField.php
    *** Error code 1


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


Move `envify` and `unreachable-branch-transform` to normal dependencies for external browserify support.


Two typos.


SELECT area FROM country WHERE gaul_code = location.country_gaul_code


For what it's worth, I deleted this for a reason. Looping over the entire table is bad style. The normal idiom would be to do:

location.types

To get all the types, contextually, for a given location. However since we have this funny multi-join-on array, that probably doesn't work (which means I introduced a bug when I deleted it). However, a much better solution would be to add logic to the Location model (i.e., a types method if it doesn't already exist) that does the lookup of associated types:

def types
  Type.where("id IN ?",self.type_ids)
end


damn completely forgot. That's the thing if you don't have return types in the declaration...


ref: e0f232bc530b42911405c62a73e20f90d862e0bf


Pls don't delete this file, it is used in continuous integration test for windows.
Restore the file, amend the commit, and push


Using the Digital Ocean Provider, I'm getting an error:
This worked earlier. :)
```
Running handlers:
[2015-03-04T12:31:27-05:00] ERROR: Exception handlers complete
[2015-03-04T12:31:27-05:00] FATAL: Stacktrace dumped to /home/pair/src/chris/clutch/clutch-chef-repo/.chef/local-mode-cache/cache/chef-stacktrace.out
[2015-03-04T12:31:27-05:00] DEBUG: Chef::Exceptions::RunFailedWrappingError: Found 1 errors, they are stored in the backtrace
1) NoMethodError -  machine_batch[default] (@recipe_files::/home/pair/src/chris/clutch/clutch-chef-repo/provisioning/camaro.rb line 42) had an error: NoMethodError: undefined method `addresses' for #<Fog::Compute::DigitalOcean::Server:0x00000005f54588>
/home/pair/.chefdk/gem/ruby/2.1.0/bundler/gems/chef-provisioning-fog-c8df0ed605db/lib/chef/provisioning/fog_driver/driver.rb:472:in `find_floating_ips'
/home/pair/.chefdk/gem/ruby/2.1.0/bundler/gems/chef-provisioning-fog-c8df0ed605db/lib/chef/provisioning/fog_driver/driver.rb:432:in `converge_floating_ips'
/home/pair/.chefdk/gem/ruby/2.1.0/bundler/gems/chef-provisioning-fog-c8df0ed605db/lib/chef/provisioning/fog_driver/driver.rb:208:in `ready_machine'
/home/pair/.chefdk/gem/ruby/2.1.0/bundler/gems/chef-provisioning-97b6a66ac612/lib/chef/provisioning/driver.rb:247:in `block in ready_machines'
/home/pair/.chefdk/gem/ruby/2.1.0/gems/chef-12.1.0/lib/chef/chef_fs/parallelizer/parallel_enumerable.rb:267:in `call'
/home/pair/.chefdk/gem/ruby/2.1.0/gems/chef-12.1.0/lib/chef/chef_fs/parallelizer/parallel_enumerable.rb:267:in `process_input'
/home/pair/.chefdk/gem/ruby/2.1.0/gems/chef-12.1.0/lib/chef/chef_fs/parallelizer/parallel_enumerable.rb:257:in `process_one'
/home/pair/.chefdk/gem/ruby/2.1.0/gems/chef-12.1.0/lib/chef/chef_fs/parallelizer.rb:93:in `call'
/home/pair/.chefdk/gem/ruby/2.1.0/gems/chef-12.1.0/lib/chef/chef_fs/parallelizer.rb:93:in `worker_loop'
```


This is a Plugin for a Minecraft Server with PC Version.


Depends. It looks like the goal of the test is really to just confirm we can load the config? If so, I'd just add a test in the base framework (not generated), to make sure the mechanics work.


Thanks for always being amazing @yterajima


if there's a but you should not place a dot between them.


@kirkshoop Excellent catch!  I actually had this code in here before and I'm not sure what happened to it.  New commit incoming...


I thought since it's used only one time I named it shortly.
Will rename to `compiled_pattern`


Good to keep.


should unsubscribe ksSelected


You could simplify this by following rails naming conventions and calling this association:

```
has_many :edition_dependencies
```

you could then also say:

```
has_many :dependencies, through: :edition_dependencies
```

I think you can also do something along the lines of:

```
has_many :contact_dependencies, through: :edition_dependencies, class: "Contact"
```

not 100% sure of the syntax however.


Do we send an event when we invalidate the cache?


Nit pick. This is extra white space being added. Might be errant editor config.


it was a real one but if you looked at the thing you would have seen that its at module level.


Recommend keeping all these. Can cull later- but I think you'll want the methods they provide.


May not need.


Can't you use [scrambleFont.getSize()](http://api.itextpdf.com/itext/com/itextpdf/text/Font.html#getSize()) wherever you need the font size?


:smile:


oops... PHP_INT_MIN isn't always present, that's why I've chosen the negative max. Shall I change it in the code which uses it?


this should be an observer on the `publish` and `force_publish` event. You can add observers in the `edition_services` file:

https://github.com/alphagov/whitehall/blob/master/config/initializers/edition_services.rb


This is a very good catch! I thought about this and I think the easiest solution will be to call the user after `try_reconnect` is invoked. Will add a test for this.


develop (DavidGoldwasser) - i386-Windows-7-VisualStudio-12: OK (2189 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-98.96%25-yellow.svg)


Looks like the DO addresses are spread across two attributes:
```ruby
        attribute :public_ip_address, :aliases => 'ip_address'
        attribute :private_ip_address
```

https://github.com/fog/fog/blob/01202f61327392142fa3a28b2cda7f870199214e/lib/fog/digitalocean/models/compute/server.rb#L15


Interesting, I have a recollection (and an inline comment) that you argued passionately that the category should be 0 (no category) for new types until assigned by you.

I think assigning to human by default is a fine approach, but want to note that this is a reversal on our previous policy.


Code won't compile like this, fixing right now.


Will `addTenantKeyValue` re-populate the cache on that node? I see we broadcast, but does the current node also gets notified?

What I want to avoid:

* Thread 1: `tenantKVCache.remove(tenantKey);`
* Thread 2: retrieve the key, which triggers a cache miss
* Thread 1: `tenantDao.addTenantKeyValue(key, value, isSingleValueKey(key), internalContext);`

Now, the cache has the old value.


That's completely legal.


Nope, link?


How do you find the URI of a WeMo device? I can get the ip address, and also find information about it using miranda.py, can you also include a sample of what goes in this field?


Sure, although `deleteFromTransaction` simply returns `null`, so no need to cache the result.


Sorry T.T


do you have a better fix? my problem still persists


86605784-RefrigNoNodeCrash (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1637 of 1647 tests passed)

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


Why did you do that?


Makes more sense.


88620944-FluidCoolerWithLowSpeedAuto (jasondegraw) - i386-Windows-7-VisualStudio-12: OK (1635 of 1635 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)


@walterbender I have updated the pr. Kindly review it.


Could we meet sometime tomorrow to run through the code you've written? I
am free any time before 1:30 and after 5pm.

On Wed, Mar 4, 2015 at 12:32 PM, Jacob Carey <notifications@github.com>
wrote:

> @Tharper84 <https://github.com/Tharper84> So I think what you have is a
> good start. However, we will need to estimate autocorrelation and effective
> size for each parameter of each chain (i.e chain 1 estimation of theta1).
> Additionally, we should also probably estimate the 95% HPD (highest
> posterior density) region for each parameter. I'm not sure if there is a
> function in R to do this, or if you will have to come up with something
> manually. Also, try writing these r functions in a .Rmd (R markdown) or
> .Rnw file, so that we can have reproducible research. I think Rob mentioned
> that a portion of the grade was doing this.
>
> @KhatriVivek <https://github.com/KhatriVivek> I'm still wrapping up the
> code to produce the MCMC estimates. Almost done. I think once you are done
> reading through the code, you can let me know if you see any problems. I
> will read about this too, but can you read about implementation of
> reversible jump MCMC in the context of mixture models? I'm hopeful that we
> can find a good algorithm. I'm not sure what your question is regarding
> input X.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Jacobcvt12/bm1_project/commit/53330c151aa257fd625bd594c3f29b6e8256a860#commitcomment-10034601>
> .
>


Add login capability


You were right : you don't need to run the usual script increasing the number of nodes. This one is useless with the new patch (and the two previous ones).


great work man!


That's a good idea. I think I screwed that up then before, sorry!


Even if this is just line-stripping, you should wrap it like before in braces. Escaping really looks awkward


CVCZVDV


Nice touch, having admin option and privileges.


No strong feeling. The only reason I use immutable collections is because `List` operations (`add`, etc.) very much depend on the implementation. When calling a method returning a `List`, I simply assume the worst (unavailable operations) and if I need transformations, I just copy it into something I know (`LinkedList`, `ArrayList`, etc.).


Shit... thanks.


I think the issue here is because of the Tuple type that refers back to `Term`.

I believe this is not possible in Z3, in the same way one cannot define Trees as
```scala
sealed abstract class Tree
case class Node(children: Set[Tree]) extends Tree
case class Leaf(value: Int) extends Tree
```

I think you can work around this limitation in this case by defining a custom Tuple case class.


Please take another look.


hm. will do.


So higher-order functions: 1, Z3: 0 !!


@gabizou are your auto-formatting settings wonky? There are a bunch of lines reformatted here which were perfectly fine before but now seem to be wrapped much more agressively:

* [Line 51-52 in DataSource.java](#diff-f78539508d0175ac94503be427865184R51)
* [Line 394-395 in DataView.java](#diff-cb17ef96d0835b599ecc372e1f3cd2a7R394)
* [Line 58-60 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R58)
* [Line 123-124 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R123)
* [Line 159-160 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R159)
* [Line 186-187 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R186)
* [Line 217-218 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R217)
* [Line 223-224 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R223)
* [Line 240-243 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R240)
* [Line 245-247 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R245)
* [Line 314-315 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R314)
* [Line 512-515 in MemoryDataView.java](#diff-cfd77ac8aab856b17efb8ce6e02d35e1R512)


This commit is taken care of in another branch.


Yeah i know the 624 .. is to fix tearing.. yeah yesterday + today i pm'ed with PolishVodka and he tell me about that story ! That's why i'm looking for org freq.. but trying to fix tearing without increasing that lcd freq... Very weird @ random reboot.. maybe due to disabled 2TB+ in block layer ??? But for me no reboots !


@akbertram we have serious bottleneck here. For some databases we have more than 10000 indicators. Locally on my machine such sync always fail due to mysql timeout of 5 seconds. It looks as 79 indicators 42ms, 436 - 536ms, 551-710ms. I'm going to read it by chunks of 1000 indicators, then we don't have to play with timeout much.
Thoughts? (Should we index source and destination columns in indicatorlink table?)


88620944-FluidCoolerWithLowSpeedAuto (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)


Dunno so far, for some reason can't upload last_kmsg too. I believe it has something to do with my custom changes to ext4 (I've disabled journaling). Will reenable it and see if it helps.


Should this be applied to the base base stylesheet, to prevent possible similar issues in other cobrands?


For even better compatibility with 1.9 please see my last comment on issue #194 to fix it


Fixed with 58eee60


Sorry that I've forgotten to mention this in the prev commit, is this codestyle according?


Can be viewed on Heroku: https://blooming-dusk-5504.herokuapp.com/


English is not my first language so you are probably right. I just figured the plural of progress would be progress. Will change it later.


Thanks!


nice! elegant and localized


Ah, that totally makes sense. Thanks for the explanation.


Fixed with 3071460


it is actually. Problem is if I use hanging indent there's no difference to the indentation of the next line so I need to increase indent by one. Somehow makes sense. Somehow looks weird. But I don't know a better option that is consisten with codestyle.


Okay thank u very much :-)


looks good


I would squash this in with d7125b4 and a062e82.


Could use a switch statement here


<!-- PMABOT:SOB -->
This commit is missing Signed-Off-By line to indicate that you agree with phpMyAdmin Developer's Certificate of Origin. Please check [contributing documentation](https://github.com/phpmyadmin/phpmyadmin/blob/master/CONTRIBUTING.md) for more information.


Seems that it wasn't good idea to disable journaling :D I've got fs corruption on /data once again :/


Wouldn't it make more sense to have this check in the header file?


Aren't these equivalent??


what? disabled journaling can also cause data corruption ?!
btw: why u don't use f2fs anymore ?!


Right


I'm free from 12-1:30 tomorrow. Do you want to meet then? Also, I think one helpful thing will be to turn this into a package. there's a function in Rcpp called Rcpp.skeleton.package (i think). Do one of you want to try running that and then migrate the existing code into the skeleton package format? Apparently you can only have multiple C++ files if you make a package, and I think multiple C++ files will make this easier to understand.


It used to be that way before, I can't remember whether there was a specific problem I was fixing or not.

https://github.com/ppat/storm-rabbitmq/commit/2c64d540c37ecb82e2ace6db4dbb0120267ce5ff


After extensive testing, I cannot reproduce this, despite it occuring reproducibly in a process that was previously running. Killing the process and mucking about, later I could not reproduce this error. I don't have a copy/paste of the logs because it was running in a screen/tmux session which died, but if memory serves the gist of the error was that the /dataset/<id>/display url wasn't working, while the history version which used an API url, did work.

As mentioned in IRC, I still believe this change needs to happen, though with fallback for the url key not existing. If I can reproduce this error ever again (I'll work from d1bc7e05 in case I can cause it to happen), I'll comment here again with debugging info.


I'll tackle this sometime over the weekend and integrate flux. Do you have a preferred flux implementation I should use?


ok thanks for the explanation as to why the rendering is now failing. Now I fail to see why we shouldn't create a jira issue to add the license headers on l10. Thanks.


calculateResolutionWeighting


Rodo existe la posibilidad de devolver junto con los resultados paginados algun boolean que indique que ya no hay mas resultados para buscar? o por ahi si vuelve vacia la lista cuando me paso lo puedo determinar yo en el cliente. Que decis?


As I said I need to test LK3.1 sometimes which doesn't have f2fs support(I'm really don't want to spend time on backporting it to LK3.1 too).


Without this change, I think the implementation could still just try matching against the `parameters.first`. By swapping the order, I think it makes it more obvious that you need to use `parameters.any?`.


Could this be made static? I imagine that would speed things up a bit since the regular expression needs to be compiled. Additionally shouldn't this instead be `[0-9]+ms`, as I don't think we want to catch cases that have just the text "ms".


this is so neat.  yea!


You seem to be missing a semicolon at the end of the line.


Where is in_progress defined? I didn't see it in project_requests model or controller.


What about admin units with area > 115000?


It ain't whack my nogger


Since codestyle is okay, **ack** for this commit


Sorry. I did not copy-pasted and changed but written by hand.


@TagForce its working here ! thanks! can you PR do SR?


unappy?


The `staytus:upgrade` command will run the database migrations for you :smile:


If the `on_map_list_items.html` template was used, I think this would simplify a little bit of #1045.


Where is in_progress defined? Didn't see it in model or controller... ah, found it! Helper.


Should this be squashed in with 74338a7c6805f11935ce269a0623acd0c414479f or is it different?


It's a minimal code change (with no breaking change), which happened to work better with a new method name rather than a less intuitive extra parameter. It is still harmless and adds only a few bytes.


Looks good!


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


1: M111 unrecognized component name: docextract


1: M111 unrecognized component name: general


1: D100 Docstring missing


1: M111 unrecognized component name: i18n


1: M111 unrecognized component name: bibrank


1: M111 unrecognized component name: oauthclient


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


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


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: 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


1: D200 One-line docstring should not occupy 3 lines
2: L102 copyright year is outdated, expected 2015 but got 2013
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
32:1: I100 Imports statements are in the wrong order. import cgi should be before import unittest
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: I100 Imports statements are in the wrong order. from functools should be before from warnings
36:1: E402 module level import not at top of file
37:1: E402 module level import not at top of file
38:1: I100 Imports statements are in the wrong order. from urllib should be before from urlparse
38:1: E402 module level import not at top of file
39:1: I100 Imports statements are in the wrong order. from itertools should be before from urllib
39:1: E402 module level import not at top of file
48:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_JSTESTDRIVER_PORT, CFG_LOGDIR, CFG_PREFIX, CFG_PYLIBDIR, CFG_SITE_NAME_INTL, CFG_SITE_SECURE_URL, CFG_SITE_URL, CFG_WEBDIR
48:1: E402 module level import not at top of file
57:1: I101 Imported names are in the wrong order. Should be CFG_TESTS_REQUIRE_HTML_VALIDATION, w3c_errors_to_str, w3c_validate
57:1: E402 module level import not at top of file
58:36: E128 continuation line under-indented for visual indent
59:36: E128 continuation line under-indented for visual indent
69:1: E302 expected 2 blank lines, found 1
70: D202 No blank lines allowed *after* function docstring, found 1
70: D400 First line should end with '.', not 'y'
70: D205 Blank line missing between one-line summary and description
126:1: E302 expected 2 blank lines, found 1
127: D290 White spaces around docstring should be trimmed.
127: D400 First line should end with '.', not 's'
132:1: E302 expected 2 blank lines, found 1
133: D400 First line should end with '.', not 'e'
133: D205 Blank line missing between one-line summary and description
143:1: E302 expected 2 blank lines, found 1
143: D290 White spaces around docstring should be trimmed.
143: D209 Put multi-line docstring closing quotes on separate line
143: D202 No blank lines allowed *after* function docstring, found 1
143: D400 First line should end with '.', not 'y'
143: D205 Blank line missing between one-line summary and description
154:1: E302 expected 2 blank lines, found 1
154: D290 White spaces around docstring should be trimmed.
154: D209 Put multi-line docstring closing quotes on separate line
154: D202 No blank lines allowed *after* function docstring, found 1
154: D400 First line should end with '.', not 'y'
154: D205 Blank line missing between one-line summary and description
165:1: E302 expected 2 blank lines, found 1
165: D290 White spaces around docstring should be trimmed.
165: D209 Put multi-line docstring closing quotes on separate line
165: D202 No blank lines allowed *after* function docstring, found 1
165: D400 First line should end with '.', not 'y'
165: D205 Blank line missing between one-line summary and description
176:1: E302 expected 2 blank lines, found 1
176: D203 Expected 1 blank line *before* class docstring, found 0
176: D204 Expected 1 blank line *after* class docstring, found 0
180:1: E302 expected 2 blank lines, found 1
181: D205 Blank line missing between one-line summary and description
190:5: B901 blind except: statement
194:1: E302 expected 2 blank lines, found 1
194: D400 First line should end with '.', not 'd'
194: D205 Blank line missing between one-line summary and description
204:37: E261 at least two spaces before inline comment
219:1: E302 expected 2 blank lines, found 1
220: D400 First line should end with '.', not 's'
220: D205 Blank line missing between one-line summary and description
220: D208 Docstring is over-indented
272:55: W602 deprecated form of raising exception
273:23: E126 continuation line over-indented for hanging indent
289:55: W602 deprecated form of raising exception
290:23: E127 continuation line over-indented for visual indent
299:20: E126 continuation line over-indented for hanging indent
304:20: E127 continuation line over-indented for visual indent
319:59: W602 deprecated form of raising exception
320:27: E126 continuation line over-indented for hanging indent
328:35: E126 continuation line over-indented for hanging indent
330:55: W602 deprecated form of raising exception
333:5: E303 too many blank lines (2)
334:80: E502 the backslash is redundant between brackets
337:82: E502 the backslash is redundant between brackets
356:1: E302 expected 2 blank lines, found 1
356: D400 First line should end with '.', not 'y'
356: D205 Blank line missing between one-line summary and description
356: D208 Docstring is over-indented
366:1: E302 expected 2 blank lines, found 1
367: D202 No blank lines allowed *after* function docstring, found 1
367: D400 First line should end with '.', not 'd'
367: D205 Blank line missing between one-line summary and description
390:1: E302 expected 2 blank lines, found 1
391: D400 First line should end with '.', not 'h'
391: D205 Blank line missing between one-line summary and description
397: D400 First line should end with '.', not 'd'
397: D200 One-line docstring should not occupy 3 lines
418: D400 First line should end with '.', not 'n'
418: D205 Blank line missing between one-line summary and description
432:145: E502 the backslash is redundant between brackets
442:9: E128 continuation line under-indented for visual indent
464:1: E302 expected 2 blank lines, found 1
465: D202 No blank lines allowed *after* function docstring, found 1
465: D400 First line should end with '.', not 'y'
465: D205 Blank line missing between one-line summary and description
490:1: E302 expected 2 blank lines, found 1
491: D202 No blank lines allowed *after* function docstring, found 1
491: D400 First line should end with '.', not 'y'
491: D205 Blank line missing between one-line summary and description
517: D203 Expected 1 blank line *before* class docstring, found 0
517: D204 Expected 1 blank line *after* class docstring, found 0
517: D300 Expected """-quotes, got '-quotes
528: D290 White spaces around docstring should be trimmed.
528: D203 Expected 1 blank line *before* class docstring, found 0
528: D400 First line should end with '.', not 's'
528: D205 Blank line missing between one-line summary and description
533: D202 No blank lines allowed *after* method docstring, found 1
536:9: E266 too many leading '#' for block comment
547: D202 No blank lines allowed *after* method docstring, found 1
553: D290 White spaces around docstring should be trimmed.
553: D202 No blank lines allowed *after* method docstring, found 1
553: D400 First line should end with '.', not 's'
553: D205 Blank line missing between one-line summary and description
566:9: B901 blind except: statement
569: D290 White spaces around docstring should be trimmed.
569: D202 No blank lines allowed *after* method docstring, found 1
569: D400 First line should end with '.', not 's'
569: D205 Blank line missing between one-line summary and description
582:9: B901 blind except: statement
585: D290 White spaces around docstring should be trimmed.
585: D202 No blank lines allowed *after* method docstring, found 1
585: D400 First line should end with '.', not 's'
585: D205 Blank line missing between one-line summary and description
598:9: B901 blind except: statement
601: D290 White spaces around docstring should be trimmed.
601: D202 No blank lines allowed *after* method docstring, found 1
601: D400 First line should end with '.', not 's'
601: D205 Blank line missing between one-line summary and description
622:9: B901 blind except: statement
629:123: E225 missing whitespace around operator
630:13: B901 blind except: statement
637: D290 White spaces around docstring should be trimmed.
637: D202 No blank lines allowed *after* method docstring, found 1
637: D400 First line should end with '.', not 's'
637: D205 Blank line missing between one-line summary and description
650:9: B901 blind except: statement
653: D290 White spaces around docstring should be trimmed.
653: D202 No blank lines allowed *after* method docstring, found 1
653: D400 First line should end with '.', not 's'
653: D205 Blank line missing between one-line summary and description
666:9: B901 blind except: statement
669: D290 White spaces around docstring should be trimmed.
669: D202 No blank lines allowed *after* method docstring, found 1
669: D400 First line should end with '.', not 's'
669: D205 Blank line missing between one-line summary and description
682:9: B901 blind except: statement
685: D290 White spaces around docstring should be trimmed.
685: D202 No blank lines allowed *after* method docstring, found 1
685: D400 First line should end with '.', not 's'
685: D205 Blank line missing between one-line summary and description
697:9: B901 blind except: statement
700: D290 White spaces around docstring should be trimmed.
700: D400 First line should end with '.', not 'd'
700: D205 Blank line missing between one-line summary and description
710:9: B901 blind except: statement
713: D290 White spaces around docstring should be trimmed.
713: D400 First line should end with '.', not 'd'
713: D205 Blank line missing between one-line summary and description
723:9: B901 blind except: statement
726: D290 White spaces around docstring should be trimmed.
726: D400 First line should end with '.', not 'n'
726: D205 Blank line missing between one-line summary and description
741:16: E713 test for membership should be 'not in'
765: D290 White spaces around docstring should be trimmed.
765: D202 No blank lines allowed *after* method docstring, found 1
765: D400 First line should end with '.', not 'n'
765: D200 One-line docstring should not occupy 2 lines
773:66: E502 the backslash is redundant between brackets
773: D290 White spaces around docstring should be trimmed.
773: D202 No blank lines allowed *after* method docstring, found 1
773: D400 First line should end with '.', not 'n'
773: D205 Blank line missing between one-line summary and description
823: D290 White spaces around docstring should be trimmed.
823: D202 No blank lines allowed *after* method docstring, found 1
823: D400 First line should end with '.', not 's'
823: D205 Blank line missing between one-line summary and description
861: D290 White spaces around docstring should be trimmed.
861: D202 No blank lines allowed *after* method docstring, found 1
861: D400 First line should end with '.', not 'n'
861: D205 Blank line missing between one-line summary and description
887: D290 White spaces around docstring should be trimmed.
887: D202 No blank lines allowed *after* method docstring, found 1
887: D400 First line should end with '.', not 'n'
887: D205 Blank line missing between one-line summary and description
910: D290 White spaces around docstring should be trimmed.
910: D202 No blank lines allowed *after* method docstring, found 1
910: D400 First line should end with '.', not 'n'
910: D205 Blank line missing between one-line summary and description
936: D290 White spaces around docstring should be trimmed.
936: D202 No blank lines allowed *after* method docstring, found 1
936: D400 First line should end with '.', not 't'
936: D205 Blank line missing between one-line summary and description
957: D290 White spaces around docstring should be trimmed.
957: D209 Put multi-line docstring closing quotes on separate line
957: D202 No blank lines allowed *after* method docstring, found 1
957: D400 First line should end with '.', not 'n'
957: D205 Blank line missing between one-line summary and description
964:9: B901 blind except: statement
968: D203 Expected 1 blank line *before* class docstring, found 0
968: D400 First line should end with '.', not 't'
968: D205 Blank line missing between one-line summary and description
995: D103 Docstring missing
1003: D401 First line should be imperative: 'Make', not 'Makes'
1003: D400 First line should end with '.', not 'r'


22:1: F401 'subprocess' imported but unused


199:1: E303 too many blank lines (3)


4: L102 copyright year is outdated, expected 2015 but got 2013
25:1: I100 Imports statements are in the wrong order. import StringIO should be before import sys
26:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite
26:1: I201 Missing newline before sections or imports.
31:5: E266 too many leading '#' for block comment
119:5: E303 too many blank lines (2)


Hi,
technically the layout handles are not related to the root block at all. Also the fact that the full action name maps to one handle might be misleading.
I like the idea of showing handle information (and even if not related to the root block, this might be a good place to show it - so we don't have to introduce a new UI element), but I think we should show the full list of handles instead.


Also, if you override `report/_item.html` here, it would be also used on the all reports page and the front page (I don't know if the latter is wanted).


this is wonderful


Oh, I guess the code I had was out of date. I guess that's the source of the problem :3 I could have sworn I git pulled it.


What does user see if attepts to respond to project request more than once?


You can get all handles from the layout object:
See: http://snipplr.com/view/61215/


I couldn't find why the switch to java8 was made here, can you explain that?


Makes sense. Puppet acceptance (and setup) no longer use the `host['group']` style invocation as part of https://tickets.puppetlabs.com/browse/PUP-3969, and I verified in https://gist.github.com/joshcooper/933f46b241f87f5957f8.

>  just supposed to be used for Beaker's ssh connections

This makes me think we should drop `group` entirely, and just keep `user` based on *nix or Windows.


closes #20


@proAlexandr независим, но замысел мог быть как раз такой, что не мы обеспечиваем независимость, а разработчик Ai. Иначе бы зачем нам считать фейлы и пересоздавать Ai, когда их слишком много?


I'm not sure this is true. The cluster can lose quorum due to network partitioning, and once the partition is dropped the cluster self-heals. Bootstrapping would not be required in this case; fixing the network partition would also resolve the problem.

I was thinking it would be useful to include some suggested steps like, "before bootstrapping, check that all nodes can reach one another".