25:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite
43:152: E203 whitespace before ':'
50:160: E203 whitespace before ':'
57:160: E203 whitespace before ':'
65:107: E203 whitespace before ':'
73:96: E203 whitespace before ':'
81:96: E203 whitespace before ':'
89:101: E203 whitespace before ':'
97:101: E203 whitespace before ':'
105:116: E203 whitespace before ':'
113:116: E203 whitespace before ':'
121:107: E203 whitespace before ':'
129:114: E203 whitespace before ':'
137:131: E203 whitespace before ':'
155:18: E128 continuation line under-indented for visual indent
155:83: E203 whitespace before ':'
166:18: E128 continuation line under-indented for visual indent
166:88: E203 whitespace before ':'
177:18: E128 continuation line under-indented for visual indent
177:88: E203 whitespace before ':'
188:18: E128 continuation line under-indented for visual indent
188:101: E203 whitespace before ':'
203:18: E128 continuation line under-indented for visual indent
203:101: E203 whitespace before ':'
216:18: E128 continuation line under-indented for visual indent
216:108: E203 whitespace before ':'
229:18: E128 continuation line under-indented for visual indent
229:126: E203 whitespace before ':'
232:13: E128 continuation line under-indented for visual indent
233:13: E128 continuation line under-indented for visual indent
234:13: E128 continuation line under-indented for visual indent
235:13: E128 continuation line under-indented for visual indent
236:13: E128 continuation line under-indented for visual indent
237:13: E128 continuation line under-indented for visual indent
238:13: E128 continuation line under-indented for visual indent
239:13: E128 continuation line under-indented for visual indent
240:13: E128 continuation line under-indented for visual indent
241:13: E128 continuation line under-indented for visual indent
242:13: E128 continuation line under-indented for visual indent
243:13: E128 continuation line under-indented for visual indent
244:13: E128 continuation line under-indented for visual indent
245:13: E128 continuation line under-indented for visual indent
246:13: E128 continuation line under-indented for visual indent
247:13: E128 continuation line under-indented for visual indent
248:13: E128 continuation line under-indented for visual indent
249:13: E128 continuation line under-indented for visual indent
250:13: E128 continuation line under-indented for visual indent
251:13: E128 continuation line under-indented for visual indent
252:13: E128 continuation line under-indented for visual indent
253:13: E128 continuation line under-indented for visual indent
254:13: E128 continuation line under-indented for visual indent
263:18: E128 continuation line under-indented for visual indent
263:97: E203 whitespace before ':'
283:1: E303 too many blank lines (3)
320:1: E303 too many blank lines (3)
325:5: E303 too many blank lines (2)
334:42: E231 missing whitespace after ','
334:47: E231 missing whitespace after ','
334:53: E231 missing whitespace after ','
340:39: E231 missing whitespace after ','
340:45: E231 missing whitespace after ','
340:51: E231 missing whitespace after ','
340:57: E231 missing whitespace after ','
340:63: E231 missing whitespace after ','
346:39: E231 missing whitespace after ','
346:45: E231 missing whitespace after ','
346:51: E231 missing whitespace after ','
346:57: E231 missing whitespace after ','
359:90: E231 missing whitespace after ','
359:96: E231 missing whitespace after ','


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


1: D400 First line should end with '.', not 'n'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
29: D203 Expected 1 blank line *before* class docstring, found 0
29: D400 First line should end with '.', not 'n'
29: D205 Blank line missing between one-line summary and description
29: D208 Docstring is over-indented
40:41: E251 unexpected spaces around keyword / parameter equals
40:43: E251 unexpected spaces around keyword / parameter equals
40:66: E251 unexpected spaces around keyword / parameter equals
40:68: E251 unexpected spaces around keyword / parameter equals
40:94: E251 unexpected spaces around keyword / parameter equals
40:96: E251 unexpected spaces around keyword / parameter equals
40:123: E251 unexpected spaces around keyword / parameter equals
40:125: E251 unexpected spaces around keyword / parameter equals
40: D102 Docstring missing
45:5: E303 too many blank lines (2)
45: D401 First line should be imperative: 'Use', not 'Uses'
45: D209 Put multi-line docstring closing quotes on separate line
45: D400 First line should end with '.', not 's'
45: D205 Blank line missing between one-line summary and description
45: D208 Docstring is over-indented
48:55: E231 missing whitespace after ','
50: D205 Blank line missing between one-line summary and description
58: D102 Docstring missing
61: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
32:1: E303 too many blank lines (3)
32: D203 Expected 1 blank line *before* class docstring, found 0
41:41: E251 unexpected spaces around keyword / parameter equals
41:43: E251 unexpected spaces around keyword / parameter equals
41:66: E251 unexpected spaces around keyword / parameter equals
41:68: E251 unexpected spaces around keyword / parameter equals
41:94: E251 unexpected spaces around keyword / parameter equals
41:96: E251 unexpected spaces around keyword / parameter equals
41:123: E251 unexpected spaces around keyword / parameter equals
41:125: E251 unexpected spaces around keyword / parameter equals
41: D102 Docstring missing
43:49: E127 continuation line over-indented for visual indent
44:49: E127 continuation line over-indented for visual indent
45:49: E127 continuation line over-indented for visual indent
71:35: E203 whitespace before ':'
72:35: E203 whitespace before ':'
73:35: E203 whitespace before ':'
74:35: E203 whitespace before ':'
75:35: E203 whitespace before ':'
89:25: E116 unexpected indentation (comment)
100:21: E116 unexpected indentation (comment)
106: D202 No blank lines allowed *after* method docstring, found 1
128:61: E251 unexpected spaces around keyword / parameter equals
128:63: E251 unexpected spaces around keyword / parameter equals
142:22: E711 comparison to None should be 'if cond is not None:'
159:9: F841 local variable 'raw' is assigned to but never used
180: D202 No blank lines allowed *after* method docstring, found 1
196: D401 First line should be imperative: 'List', not 'Lists'
196: D400 First line should end with '.', not ']'
198:21: E711 comparison to None should be 'if cond is None:'
202: D401 First line should be imperative: 'List', not 'Lists'
202: D400 First line should end with '.', not 'l'
212: D401 First line should be imperative: 'Bring', not 'Brings'
212: D202 No blank lines allowed *after* function docstring, found 1
212: D400 First line should end with '.', not 's'
229: D401 First line should be imperative: 'Run', not 'Runs'
229: D400 First line should end with '.', not 'l'
232:18: E272 multiple spaces before keyword
238: D401 First line should be imperative: 'Find', not 'Finds'
238: D400 First line should end with '.', not "'"
261:5: E303 too many blank lines (2)
288:5: E303 too many blank lines (2)
288: D205 Blank line missing between one-line summary and description
288: D208 Docstring is over-indented
297:5: E303 too many blank lines (2)
297: D400 First line should end with '.', not 'r'
302:5: E303 too many blank lines (2)
302: D290 White spaces around docstring should be trimmed.
326:5: E303 too many blank lines (2)
326: D205 Blank line missing between one-line summary and description
326: D208 Docstring is over-indented
336:1: W391 blank line at end of file


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
24:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info, isGuestUser
28:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.url
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: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_AUTHOR_DELETE_COMMENT_OPTION, CFG_WEBCOMMENT_MAX_ATTACHED_FILES, CFG_WEBCOMMENT_MAX_ATTACHMENT_SIZE, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_USE_RICH_TEXT_EDITOR
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.mail
31:1: E402 module level import not at top of file
32:28: E126 continuation line over-indented for hanging indent
47:1: I101 Imported names are in the wrong order. Should be create_html_select, get_html_text_editor
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
50:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.formatter
50:1: E402 module level import not at top of file
51:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_get_user_roles_from_user_info
51:1: I100 Imports statements are in the wrong order. from invenio.modules.access.control should be before from invenio.modules.access.engine
51:1: E402 module level import not at top of file
52:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.access.control
52:1: E402 module level import not at top of file
54:1: E302 expected 2 blank lines, found 1
54: D203 Expected 1 blank line *before* class docstring, found 0
54: D400 First line should end with '.', not 'l'
57: D202 No blank lines allowed *after* method docstring, found 1
57: D400 First line should end with '.', not 'd'
57: D205 Blank line missing between one-line summary and description
92:13: F841 local variable 'last_comment_round_name' is assigned to but never used
98:139: E221 multiple spaces before operator
101:85: E231 missing whitespace after ','
101:87: E221 multiple spaces before operator
140:34: E127 continuation line over-indented for visual indent
152:13: E128 continuation line under-indented for visual indent
154:33: E203 whitespace before ':'
159:36: E225 missing whitespace around operator
160:168: E502 the backslash is redundant between brackets
160:57: E225 missing whitespace around operator
161:67: E127 continuation line over-indented for visual indent
164:13: E124 closing bracket does not match visual indentation
178:14: E127 continuation line over-indented for visual indent
180:14: E124 closing bracket does not match visual indentation
184: D401 First line should be imperative: 'Display', not 'Displays'
184: D205 Blank line missing between one-line summary and description
209: D400 First line should end with '.', not 'd'
209: D205 Blank line missing between one-line summary and description
244:26: E201 whitespace after '{'
244:45: E203 whitespace before ':'
244:22: E222 multiple spaces after operator
245:46: E203 whitespace before ':'
246:44: E203 whitespace before ':'
247:44: E203 whitespace before ':'
248:44: E203 whitespace before ':'
248:62: E261 at least two spaces before inline comment
248:63: E262 inline comment should start with '# '
249:44: E203 whitespace before ':'
249:62: E261 at least two spaces before inline comment
249:63: E262 inline comment should start with '# '
250:25: E124 closing bracket does not match visual indentation
260:13: F841 local variable 'last_comment_round_name' is assigned to but never used
294:106: E231 missing whitespace after ':'
294:143: E231 missing whitespace after ':'
295:32: E222 multiple spaces after operator
316:37: E225 missing whitespace around operator
336:13: E122 continuation line missing indentation or outdented
336:14: E201 whitespace after '{'
336:40: E203 whitespace before ':'
337:40: E203 whitespace before ':'
338:40: E203 whitespace before ':'
339:40: E203 whitespace before ':'
340:40: E203 whitespace before ':'
341:40: E203 whitespace before ':'
342:40: E203 whitespace before ':'
343:40: E203 whitespace before ':'
344:41: E203 whitespace before ':'
345:60: E225 missing whitespace around operator
346:40: E203 whitespace before ':'
347:13: E124 closing bracket does not match visual indentation
359:28: E128 continuation line under-indented for visual indent
360:28: E128 continuation line under-indented for visual indent
363: D400 First line should end with '.', not 'n'
363: D205 Blank line missing between one-line summary and description
402:35: E128 continuation line under-indented for visual indent
403:35: E126 continuation line over-indented for hanging indent
408:81: E225 missing whitespace around operator
408:100: E225 missing whitespace around operator
410:83: E225 missing whitespace around operator
433:105: E225 missing whitespace around operator
435:106: E225 missing whitespace around operator
441:110: E225 missing whitespace around operator
452:111: E271 multiple spaces after keyword
461:37: E126 continuation line over-indented for hanging indent
488:17: E127 continuation line over-indented for visual indent
488:33: E203 whitespace before ':'
489:33: E203 whitespace before ':'
490:33: E203 whitespace before ':'
500: D400 First line should end with '.', not 'n'
500: D205 Blank line missing between one-line summary and description
533:107: E231 missing whitespace after ':'
534:9: E266 too many leading '#' for block comment
568:94: E225 missing whitespace around operator
574:99: E225 missing whitespace around operator
589:31: E203 whitespace before ':'
590:16: E128 continuation line under-indented for visual indent
591:16: E128 continuation line under-indented for visual indent
591:31: E203 whitespace before ':'
592:16: E128 continuation line under-indented for visual indent
592:31: E203 whitespace before ':'
593:16: E128 continuation line under-indented for visual indent
594:16: E128 continuation line under-indented for visual indent
594:31: E203 whitespace before ':'
595:16: E128 continuation line under-indented for visual indent
595:31: E203 whitespace before ':'
596:16: E128 continuation line under-indented for visual indent
596:31: E203 whitespace before ':'
597:16: E124 closing bracket does not match visual indentation
600: D400 First line should end with '.', not 's'
600: D205 Blank line missing between one-line summary and description
609:55: E231 missing whitespace after ','
692:13: F841 local variable 'c_round_name' is assigned to but never used
693:13: F841 local variable 'c_restriction' is assigned to but never used
702:26: E201 whitespace after '{'
702:45: E203 whitespace before ':'
702:22: E222 multiple spaces after operator
703:46: E203 whitespace before ':'
704:44: E203 whitespace before ':'
705:44: E203 whitespace before ':'
706:44: E203 whitespace before ':'
707:44: E203 whitespace before ':'
708:44: E203 whitespace before ':'
709:44: E203 whitespace before ':'
710:44: E203 whitespace before ':'
711:44: E203 whitespace before ':'
712:25: E124 closing bracket does not match visual indentation
719:22: E201 whitespace after '{'
719:37: E203 whitespace before ':'
719:19: E222 multiple spaces after operator
720:42: E203 whitespace before ':'
721:36: E203 whitespace before ':'
722:36: E203 whitespace before ':'
724:36: E203 whitespace before ':'
725:36: E203 whitespace before ':'
726:36: E203 whitespace before ':'
727:36: E203 whitespace before ':'
731:9: E266 too many leading '#' for block comment
736:13: F841 local variable 'last_comment_round_name' is assigned to but never used
747:20: E127 continuation line over-indented for visual indent
754:35: E127 continuation line over-indented for visual indent
754:73: E221 multiple spaces before operator
763:132: E202 whitespace before ')'
764:33: E127 continuation line over-indented for visual indent
764:71: E221 multiple spaces before operator
765:140: E225 missing whitespace around operator
838:76: E261 at least two spaces before inline comment
846:275: E231 missing whitespace after ':'
847:163: E231 missing whitespace after ':'
880:38: E203 whitespace before ':'
880:62: E231 missing whitespace after ':'
882:38: E203 whitespace before ':'
882:61: E231 missing whitespace after ':'
883:38: E203 whitespace before ':'
883:63: E231 missing whitespace after ':'
885:35: E203 whitespace before ':'
892:9: E266 too many leading '#' for block comment
917:9: E266 too many leading '#' for block comment
1085:9: E122 continuation line missing indentation or outdented
1086:47: E203 whitespace before ','
1088:43: E225 missing whitespace around operator
1104: D401 First line should be imperative: 'print', not 'prints'
1104: D400 First line should end with '.', not 'm'
1112: D202 No blank lines allowed *after* method docstring, found 1
1112: D400 First line should end with '.', not 'n'
1112: D205 Blank line missing between one-line summary and description
1124:15: E221 multiple spaces before operator
1157: D400 First line should end with '.', not 'n'
1157: D205 Blank line missing between one-line summary and description
1175:15: E221 multiple spaces before operator
1177:9: E122 continuation line missing indentation or outdented
1178:9: E128 continuation line under-indented for visual indent
1179:9: E128 continuation line under-indented for visual indent
1196: D400 First line should end with '.', not 's'
1196: D205 Blank line missing between one-line summary and description
1216:22: E201 whitespace after '{'
1216:40: E203 whitespace before ':'
1217:40: E203 whitespace before ':'
1217:65: E202 whitespace before '}'
1222: D400 First line should end with '.', not 'r'
1222: D205 Blank line missing between one-line summary and description
1229:9: F841 local variable '_' is assigned to but never used
1238: D400 First line should end with '.', not 's'
1238: D205 Blank line missing between one-line summary and description
1257:22: E201 whitespace after '{'
1257:37: E203 whitespace before ':'
1257:19: E222 multiple spaces after operator
1258:42: E203 whitespace before ':'
1259:36: E203 whitespace before ':'
1260:36: E203 whitespace before ':'
1261:36: E203 whitespace before ':'
1262:36: E203 whitespace before ':'
1281:20: E222 multiple spaces after operator
1306:13: E122 continuation line missing indentation or outdented
1307:121: E502 the backslash is redundant between brackets
1308:28: E127 continuation line over-indented for visual indent
1309:100: E502 the backslash is redundant between brackets
1310:31: E127 continuation line over-indented for visual indent
1311:238: E271 multiple spaces after keyword
1320:50: E251 unexpected spaces around keyword / parameter equals
1320:52: E251 unexpected spaces around keyword / parameter equals
1355: D400 First line should end with '.', not 's'
1355: D205 Blank line missing between one-line summary and description
1373:22: E201 whitespace after '{'
1373:37: E203 whitespace before ':'
1373:19: E222 multiple spaces after operator
1374:42: E203 whitespace before ':'
1375:36: E203 whitespace before ':'
1376:36: E203 whitespace before ':'
1377:36: E203 whitespace before ':'
1378:36: E203 whitespace before ':'
1388:13: E128 continuation line under-indented for visual indent
1427:1: E128 continuation line under-indented for visual indent
1428:50: E251 unexpected spaces around keyword / parameter equals
1428:52: E251 unexpected spaces around keyword / parameter equals
1469:35: E203 whitespace before ':'
1469:42: E225 missing whitespace around operator
1470:35: E203 whitespace before ':'
1470:41: E225 missing whitespace around operator
1485: D400 First line should end with '.', not 'd'
1485: D205 Blank line missing between one-line summary and description
1492:22: E201 whitespace after '{'
1492:37: E203 whitespace before ':'
1492:19: E222 multiple spaces after operator
1493:42: E203 whitespace before ':'
1494:36: E203 whitespace before ':'
1495:36: E203 whitespace before ':'
1496:36: E203 whitespace before ':'
1497:36: E203 whitespace before ':'
1501:51: E221 multiple spaces before operator
1512:101: E222 multiple spaces after operator
1516: D401 First line should be imperative: 'Create', not 'Creates'
1516: D290 White spaces around docstring should be trimmed.
1516: D205 Blank line missing between one-line summary and description
1539:15: E221 multiple spaces before operator
1579: D400 First line should end with '.', not 'e'
1579: D200 One-line docstring should not occupy 3 lines
1605:19: E225 missing whitespace around operator
1609:36: E203 whitespace before ':'
1612:35: E203 whitespace before ':'
1613:35: E203 whitespace before ':'
1618:39: E225 missing whitespace around operator
1620: D400 First line should end with '.', not 'e'
1635:18: E225 missing whitespace around operator
1666: D400 First line should end with '.', not ')'
1666: D205 Blank line missing between one-line summary and description
1690:27: E127 continuation line over-indented for visual indent
1693:27: E127 continuation line over-indented for visual indent
1716:13: E201 whitespace after '{'
1716:25: E203 whitespace before ':'
1717:25: E203 whitespace before ':'
1718:25: E203 whitespace before ':'
1719:25: E203 whitespace before ':'
1721:26: E203 whitespace before ':'
1722:25: E203 whitespace before ':'
1723:25: E203 whitespace before ':'
1724:25: E203 whitespace before ':'
1754: D401 First line should be imperative: 'output', not 'outputs'
1754: D290 White spaces around docstring should be trimmed.
1754: D400 First line should end with '.', not 'd'
1758: D401 First line should be imperative: 'prepare', not 'prepares'
1758: D290 White spaces around docstring should be trimmed.
1758: D400 First line should end with '.', not 'r'
1773: D401 First line should be imperative: 'output', not 'outputs'
1773: D290 White spaces around docstring should be trimmed.
1773: D400 First line should end with '.', not 'w'
1788:34: E203 whitespace before ':'
1796: D400 First line should end with '.', not 't'
1796: D205 Blank line missing between one-line summary and description
1803:9: F841 local variable '_' is assigned to but never used
1842:17: E128 continuation line under-indented for visual indent
1842:50: E225 missing whitespace around operator
1842:69: E225 missing whitespace around operator
1843:17: E128 continuation line under-indented for visual indent
1843:36: E203 whitespace before ','
1843:23: E231 missing whitespace after ':'
1844:17: E128 continuation line under-indented for visual indent
1844:49: E203 whitespace before ','
1845:17: E128 continuation line under-indented for visual indent
1846:17: E128 continuation line under-indented for visual indent
1852:17: E128 continuation line under-indented for visual indent
1852:50: E225 missing whitespace around operator
1852:69: E225 missing whitespace around operator
1853:17: E128 continuation line under-indented for visual indent
1853:36: E203 whitespace before ','
1853:23: E231 missing whitespace after ':'
1854:17: E128 continuation line under-indented for visual indent
1855:17: E128 continuation line under-indented for visual indent
1860: D400 First line should end with '.', not 't'
1860: D205 Blank line missing between one-line summary and description
1866:9: F841 local variable '_' is assigned to but never used
1900:49: E225 missing whitespace around operator
1900:68: E225 missing whitespace around operator
1901:54: E272 multiple spaces before keyword
1903:49: E225 missing whitespace around operator
1903:68: E225 missing whitespace around operator
1904:54: E272 multiple spaces before keyword
1910:13: E128 continuation line under-indented for visual indent
1910:39: E203 whitespace before ','
1911:13: E128 continuation line under-indented for visual indent
1912:13: E128 continuation line under-indented for visual indent
1913:13: E128 continuation line under-indented for visual indent
1914:13: E128 continuation line under-indented for visual indent
1915:13: E128 continuation line under-indented for visual indent
1920: D400 First line should end with '.', not 't'
1920: D205 Blank line missing between one-line summary and description
1970:73: E261 at least two spaces before inline comment
1970:73: E262 inline comment should start with '# '
1972:81: E261 at least two spaces before inline comment
1972:81: E262 inline comment should start with '# '
1973:81: E261 at least two spaces before inline comment
1973:81: E262 inline comment should start with '# '
1974:81: E261 at least two spaces before inline comment
1974:81: E262 inline comment should start with '# '
1975:81: E261 at least two spaces before inline comment
1975:81: E262 inline comment should start with '# '
1976:81: E261 at least two spaces before inline comment
1976:81: E262 inline comment should start with '# '
1978:81: E261 at least two spaces before inline comment
1978:81: E262 inline comment should start with '# '
1979:81: E261 at least two spaces before inline comment
1979:81: E262 inline comment should start with '# '
1980:81: E261 at least two spaces before inline comment
1980:81: E262 inline comment should start with '# '
1981:81: E261 at least two spaces before inline comment
1981:81: E262 inline comment should start with '# '
1984:76: E261 at least two spaces before inline comment
1984:76: E262 inline comment should start with '# '
1986:84: E261 at least two spaces before inline comment
1986:84: E262 inline comment should start with '# '
1987:84: E261 at least two spaces before inline comment
1987:84: E262 inline comment should start with '# '
1988:84: E261 at least two spaces before inline comment
1988:84: E262 inline comment should start with '# '
1989:84: E261 at least two spaces before inline comment
1989:84: E262 inline comment should start with '# '
1990:84: E261 at least two spaces before inline comment
1990:84: E262 inline comment should start with '# '
1992:84: E262 inline comment should start with '# '
1993:84: E262 inline comment should start with '# '
1994:84: E262 inline comment should start with '# '
1995:84: E262 inline comment should start with '# '
1996:84: E262 inline comment should start with '# '
1998:84: E261 at least two spaces before inline comment
2001:65: E261 at least two spaces before inline comment
2001:66: E262 inline comment should start with '# '
2002:65: E261 at least two spaces before inline comment
2002:66: E262 inline comment should start with '# '
2003:66: E261 at least two spaces before inline comment
2003:66: E262 inline comment should start with '# '
2010:75: E261 at least two spaces before inline comment
2011:75: E261 at least two spaces before inline comment
2012:75: E261 at least two spaces before inline comment
2013:70: E261 at least two spaces before inline comment
2028:15: E128 continuation line under-indented for visual indent
2029:15: E128 continuation line under-indented for visual indent
2030:15: E128 continuation line under-indented for visual indent
2031:23: E211 whitespace before '('
2044:13: E122 continuation line missing indentation or outdented
2045:13: E122 continuation line missing indentation or outdented
2046:13: E122 continuation line missing indentation or outdented
2050:13: E122 continuation line missing indentation or outdented
2051:13: E122 continuation line missing indentation or outdented
2052:13: E122 continuation line missing indentation or outdented
2072:36: E225 missing whitespace around operator
2074:36: E225 missing whitespace around operator
2101: D400 First line should end with '.', not ','
2101: D205 Blank line missing between one-line summary and description
2113:37: E225 missing whitespace around operator
2113:86: E225 missing whitespace around operator
2125: D400 First line should end with '.', not ','
2125: D205 Blank line missing between one-line summary and description
2137:37: E225 missing whitespace around operator
2137:86: E225 missing whitespace around operator
2151:5: E303 too many blank lines (3)
2151: D400 First line should end with '.', not ','
2151: D205 Blank line missing between one-line summary and description
2163:37: E225 missing whitespace around operator
2163:86: E225 missing whitespace around operator
2175: D202 No blank lines allowed *after* method docstring, found 1
2175: D400 First line should end with '.', not ')'
2185:21: E126 continuation line over-indented for hanging indent
2188:26: E225 missing whitespace around operator
2224:9: E122 continuation line missing indentation or outdented
2225:9: E122 continuation line missing indentation or outdented
2226:9: E122 continuation line missing indentation or outdented
2227:9: E122 continuation line missing indentation or outdented
2228:9: E122 continuation line missing indentation or outdented
2229:9: E122 continuation line missing indentation or outdented
2230:9: E122 continuation line missing indentation or outdented
2231:9: E124 closing bracket does not match visual indentation
2234: D401 First line should be imperative: 'Print', not 'Prints'
2234: D400 First line should end with '.', not 'w'
2234: D205 Blank line missing between one-line summary and description
2256:15: E127 continuation line over-indented for visual indent
2256:109: E502 the backslash is redundant between brackets
2258:16: E127 continuation line over-indented for visual indent
2260:48: E225 missing whitespace around operator
2260:67: E225 missing whitespace around operator
2264: D401 First line should be imperative: 'Print', not 'Prints'
2264: D400 First line should end with '.', not 'w'
2264: D205 Blank line missing between one-line summary and description
2286:72: E221 multiple spaces before operator
2287:16: E127 continuation line over-indented for visual indent
2287:82: E502 the backslash is redundant between brackets
2287:44: E225 missing whitespace around operator
2287:63: E225 missing whitespace around operator
2291:81: E221 multiple spaces before operator
2292:20: E126 continuation line over-indented for hanging indent
2292:86: E502 the backslash is redundant between brackets
2292:48: E225 missing whitespace around operator
2292:67: E225 missing whitespace around operator
2296:79: E221 multiple spaces before operator
2297:20: E126 continuation line over-indented for hanging indent
2297:86: E502 the backslash is redundant between brackets
2297:48: E225 missing whitespace around operator
2297:67: E225 missing whitespace around operator
2301:16: E127 continuation line over-indented for visual indent
2305: D401 First line should be imperative: 'Print', not 'Prints'
2305: D400 First line should end with '.', not 'e'
2305: D205 Blank line missing between one-line summary and description
2332:15: E271 multiple spaces after keyword
2334: D202 No blank lines allowed *after* method docstring, found 1
2334: D400 First line should end with '.', not 'e'
2334: D205 Blank line missing between one-line summary and description
2372: D400 First line should end with '.', not 'r'
2414:78: E251 unexpected spaces around keyword / parameter equals
2414:80: E251 unexpected spaces around keyword / parameter equals
2415:78: E251 unexpected spaces around keyword / parameter equals
2415:80: E251 unexpected spaces around keyword / parameter equals
2416:79: E251 unexpected spaces around keyword / parameter equals
2416:81: E251 unexpected spaces around keyword / parameter equals
2417:55: E231 missing whitespace after ','
2417:78: E251 unexpected spaces around keyword / parameter equals
2417:80: E251 unexpected spaces around keyword / parameter equals
2425:22: E222 multiple spaces after operator
2460:9: E303 too many blank lines (3)
2523:34: E126 continuation line over-indented for hanging indent
2526:102: E502 the backslash is redundant between brackets
2526:77: E225 missing whitespace around operator
2526:96: E225 missing whitespace around operator
2531:98: E502 the backslash is redundant between brackets
2531:73: E225 missing whitespace around operator
2531:92: E225 missing whitespace around operator
2555:25: E127 continuation line over-indented for visual indent
2555:37: E203 whitespace before ':'
2556:37: E203 whitespace before ':'
2557:37: E203 whitespace before ':'
2558:37: E203 whitespace before ':'
2559:37: E203 whitespace before ':'
2560:37: E203 whitespace before ':'
2565:24: E261 at least two spaces before inline comment
2570:16: E127 continuation line over-indented for visual indent
2597:52: E126 continuation line over-indented for hanging indent


Added 1 point


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
32: D103 Docstring missing
41: D103 Docstring missing
50: D103 Docstring missing
59: D103 Docstring missing
63: D209 Put multi-line docstring closing quotes on separate line
63: D203 Expected 1 blank line *before* class docstring, found 0
63: D302 Use u""" for docstrings with Unicode
63: D205 Blank line missing between one-line summary and description
63: D208 Docstring is over-indented
69:41: E251 unexpected spaces around keyword / parameter equals
69:43: E251 unexpected spaces around keyword / parameter equals
69:66: E251 unexpected spaces around keyword / parameter equals
69:68: E251 unexpected spaces around keyword / parameter equals
69:94: E251 unexpected spaces around keyword / parameter equals
69:96: E251 unexpected spaces around keyword / parameter equals
69:123: E251 unexpected spaces around keyword / parameter equals
69:125: E251 unexpected spaces around keyword / parameter equals
69: D400 First line should end with '.', not 'n'
72:49: E127 continuation line over-indented for visual indent
73:49: E127 continuation line over-indented for visual indent
74:49: E127 continuation line over-indented for visual indent
77:5: E303 too many blank lines (2)
77: D400 First line should end with '.', not 'r'
82:5: E303 too many blank lines (2)
82: D401 First line should be imperative: 'Split', not 'Splits'
82: D400 First line should end with '.', not 's'
82: D205 Blank line missing between one-line summary and description
104:22: E201 whitespace after '['
129:5: E303 too many blank lines (2)
129: D102 Docstring missing
132: D102 Docstring missing


1: D400 First line should end with '.', not 's'
25:1: I100 Imports statements are in the wrong order. from flask_login should be before from invenio.modules.alerts.models
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
28:1: E302 expected 2 blank lines, found 1
28: D101 Docstring missing
34: D102 Docstring missing
36:26: E261 at least two spaces before inline comment
36:27: E262 inline comment should start with '# '
42: D102 Docstring missing
73: D102 Docstring missing
75:16: E126 continuation line over-indented for hanging indent


1: D100 Docstring missing
22: D203 Expected 1 blank line *before* class docstring, found 0
22: D204 Expected 1 blank line *after* class docstring, found 2
22: D400 First line should end with '.', not ')'
22: D205 Blank line missing between one-line summary and description
22: D208 Docstring is over-indented
30:5: E303 too many blank lines (2)
30: D102 Docstring missing
34:5: E303 too many blank lines (2)
34: D401 First line should be imperative: 'Return', not 'Returns'
34: D400 First line should end with '.', not 'n'
38: D205 Blank line missing between one-line summary and description
45:15: F821 undefined name 'get_record'
49: D401 First line should be imperative: 'Return', not 'Returns'
49: D200 One-line docstring should not occupy 3 lines


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


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
25:6: E126 continuation line over-indented for hanging indent
27:1: I101 Imported names are in the wrong order. Should be strip_accents, wash_for_utf8
28:1: I101 Imported names are in the wrong order. Should be apply_stemming, length_check, lower_index_term, remove_latex_markup, remove_stopwords
28:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_washer should be before from invenio.utils.text
29:6: E126 continuation line over-indented for hanging indent
31:1: I101 Imported names are in the wrong order. Should be latex_formula_re, re_arxiv, re_block_punctuation_begin, re_block_punctuation_end, re_punctuation, re_separators
31:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_utils should be before from invenio.legacy.bibindex.engine_washer
32:6: E126 continuation line over-indented for hanging indent
41:1: E303 too many blank lines (3)
41: D203 Expected 1 blank line *before* class docstring, found 0
41: D205 Blank line missing between one-line summary and description
41: D208 Docstring is over-indented
47:41: E251 unexpected spaces around keyword / parameter equals
47:43: E251 unexpected spaces around keyword / parameter equals
47:66: E251 unexpected spaces around keyword / parameter equals
47:68: E251 unexpected spaces around keyword / parameter equals
47:94: E251 unexpected spaces around keyword / parameter equals
47:96: E251 unexpected spaces around keyword / parameter equals
47:123: E251 unexpected spaces around keyword / parameter equals
47:125: E251 unexpected spaces around keyword / parameter equals
47: D400 First line should end with '.', not 'n'
55:5: E303 too many blank lines (2)
55: D401 First line should be imperative: 'Pick', not 'Picks'
55: D400 First line should end with '.', not ')'
66:5: E303 too many blank lines (3)
66: D202 No blank lines allowed *after* method docstring, found 1
66: D400 First line should end with '.', not 's'
66: D205 Blank line missing between one-line summary and description
66: D208 Docstring is over-indented
117:5: E303 too many blank lines (2)
117: D202 No blank lines allowed *after* method docstring, found 1
117: D400 First line should end with '.', not 's'
117: D205 Blank line missing between one-line summary and description
117: D208 Docstring is over-indented
159:5: E303 too many blank lines (2)
159: D400 First line should end with '.', not 's'
159: D205 Blank line missing between one-line summary and description
159: D208 Docstring is over-indented
167: D401 First line should be imperative: 'Pick', not 'Picks'
167: D400 First line should end with '.', not 'n'
167: D205 Blank line missing between one-line summary and description


1: D208 Docstring is over-indented
29: D203 Expected 1 blank line *before* class docstring, found 0
29: D205 Blank line missing between one-line summary and description
29: D208 Docstring is over-indented
39:41: E251 unexpected spaces around keyword / parameter equals
39:43: E251 unexpected spaces around keyword / parameter equals
39:66: E251 unexpected spaces around keyword / parameter equals
39:68: E251 unexpected spaces around keyword / parameter equals
39:94: E251 unexpected spaces around keyword / parameter equals
39:96: E251 unexpected spaces around keyword / parameter equals
39:123: E251 unexpected spaces around keyword / parameter equals
39:125: E251 unexpected spaces around keyword / parameter equals
39: D400 First line should end with '.', not 'y'
39: D205 Blank line missing between one-line summary and description
39: D208 Docstring is over-indented
48:5: E303 too many blank lines (2)
48: D401 First line should be imperative: 'Pick', not 'Picks'
48: D400 First line should end with '.', not ')'
57: D401 First line should be imperative: 'Pick', not 'Picks'
57: D400 First line should end with '.', not 'n'
57: D205 Blank line missing between one-line summary and description
65: D102 Docstring missing
68: D102 Docstring missing
71: D102 Docstring missing
73:1: W391 blank line at end of file


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
20:21: W291 trailing whitespace
29:1: E303 too many blank lines (4)
29: D203 Expected 1 blank line *before* class docstring, found 0
29: D204 Expected 1 blank line *after* class docstring, found 0
29: D205 Blank line missing between one-line summary and description
34:41: E251 unexpected spaces around keyword / parameter equals
34:43: E251 unexpected spaces around keyword / parameter equals
34:66: E251 unexpected spaces around keyword / parameter equals
34:68: E251 unexpected spaces around keyword / parameter equals
34:94: E251 unexpected spaces around keyword / parameter equals
34:96: E251 unexpected spaces around keyword / parameter equals
34:123: E251 unexpected spaces around keyword / parameter equals
34:125: E251 unexpected spaces around keyword / parameter equals
34: D102 Docstring missing
36:49: E127 continuation line over-indented for visual indent
37:49: E127 continuation line over-indented for visual indent
38:49: E127 continuation line over-indented for visual indent
40: D401 First line should be imperative: 'Return', not 'Returns'
40: D200 One-line docstring should not occupy 3 lines


1: D400 First line should end with '.', not 's'
23:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from flask_login should be before from invenio.ext.template
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
31: D101 Docstring missing
33: D102 Docstring missing
40: D102 Docstring missing
68: D102 Docstring missing
70:16: E126 continuation line over-indented for hanging indent


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
27: D203 Expected 1 blank line *before* class docstring, found 0
27: D205 Blank line missing between one-line summary and description
27: D208 Docstring is over-indented
43:41: E251 unexpected spaces around keyword / parameter equals
43:43: E251 unexpected spaces around keyword / parameter equals
43: D102 Docstring missing
44:24: E127 continuation line over-indented for visual indent
44:40: E251 unexpected spaces around keyword / parameter equals
44:42: E251 unexpected spaces around keyword / parameter equals
45:24: E127 continuation line over-indented for visual indent
45:42: E251 unexpected spaces around keyword / parameter equals
45:44: E251 unexpected spaces around keyword / parameter equals
46:24: E127 continuation line over-indented for visual indent
46:43: E251 unexpected spaces around keyword / parameter equals
46:45: E251 unexpected spaces around keyword / parameter equals
50:5: E303 too many blank lines (2)
50: D208 Docstring is over-indented
68: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26: D203 Expected 1 blank line *before* class docstring, found 0
26: D205 Blank line missing between one-line summary and description
26: D208 Docstring is over-indented
39:41: E251 unexpected spaces around keyword / parameter equals
39:43: E251 unexpected spaces around keyword / parameter equals
39:66: E251 unexpected spaces around keyword / parameter equals
39:68: E251 unexpected spaces around keyword / parameter equals
39:94: E251 unexpected spaces around keyword / parameter equals
39:96: E251 unexpected spaces around keyword / parameter equals
39:123: E251 unexpected spaces around keyword / parameter equals
39:125: E251 unexpected spaces around keyword / parameter equals
39: D102 Docstring missing
43:5: E303 too many blank lines (2)
43: D208 Docstring is over-indented
61: D102 Docstring missing
64: D102 Docstring missing
67: D102 Docstring missing
70: D102 Docstring missing


1: D100 Docstring missing
20:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.search_engine
23:1: E302 expected 2 blank lines, found 1
23: D203 Expected 1 blank line *before* class docstring, found 0
23: D400 First line should end with '.', not 'g'
23: D205 Blank line missing between one-line summary and description
23: D208 Docstring is over-indented
53: D102 Docstring missing
57:5: E303 too many blank lines (2)
57: D102 Docstring missing
70:60: W601 .has_key() is deprecated, use 'in'
72:39: E127 continuation line over-indented for visual indent
73:47: W601 .has_key() is deprecated, use 'in'
80: D400 First line should end with '.', not 'd'
80: D205 Blank line missing between one-line summary and description


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
25:1: I100 Imports statements are in the wrong order. import logging should be before import sys
27:1: I100 Imports statements are in the wrong order. import re should be before import urllib2
31:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_FULLTEXT_INDEX_LOCAL_FILES_ONLY, CFG_BIBINDEX_SPLASH_PAGES, CFG_SOLR_URL, CFG_XAPIAN_ENABLED
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from six
32:6: E126 continuation line over-indented for hanging indent
37:1: I100 Imports statements are in the wrong order. from invenio.legacy.websubmit.file_converter should be before from invenio.utils.html
38:1: I100 Imports statements are in the wrong order. from invenio.legacy.miscutil.solrutils_bibindex_indexer should be before from invenio.legacy.websubmit.file_converter
40:1: I101 Imported names are in the wrong order. Should be BibRecDocs, InvenioBibDocFileError, bibdocfile_url_p, bibdocfile_url_to_bibdoc, download_url
40:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from invenio.legacy.miscutil.xapianutils_bibindex_indexer
41:6: E126 continuation line over-indented for hanging indent
45:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.legacy.bibsched.bibtask
46:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.ext.logging
46:1: I201 Missing newline before sections or imports.
47:1: I201 Missing newline before sections or imports.
49:29: E261 at least two spaces before inline comment
52: D203 Expected 1 blank line *before* class docstring, found 0
52: D208 Docstring is over-indented
52: D200 One-line docstring should not occupy 3 lines
57:41: E251 unexpected spaces around keyword / parameter equals
57:43: E251 unexpected spaces around keyword / parameter equals
57:66: E251 unexpected spaces around keyword / parameter equals
57:68: E251 unexpected spaces around keyword / parameter equals
57:94: E251 unexpected spaces around keyword / parameter equals
57:96: E251 unexpected spaces around keyword / parameter equals
57:123: E251 unexpected spaces around keyword / parameter equals
57:125: E251 unexpected spaces around keyword / parameter equals
57: D102 Docstring missing
60:49: E127 continuation line over-indented for visual indent
61:49: E127 continuation line over-indented for visual indent
62:49: E127 continuation line over-indented for visual indent
64: D401 First line should be imperative: 'Allow', not 'Allows'
64: D400 First line should end with '.', not 'g'
68: D400 First line should end with '.', not 'r'
73:5: E303 too many blank lines (2)
73: D401 First line should be imperative: 'Return', not 'Returns'
73: D400 First line should end with '.', not 'y'
73: D205 Blank line missing between one-line summary and description
73: D208 Docstring is over-indented
101:28: E713 test for membership should be 'not in'
158:66: E261 at least two spaces before inline comment
185:5: E303 too many blank lines (2)
185: D102 Docstring missing
189:5: E303 too many blank lines (2)
189: D102 Docstring missing
192: D102 Docstring missing
194:1: W391 blank line at end of file


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26: D203 Expected 1 blank line *before* class docstring, found 0
26: D208 Docstring is over-indented
26: D200 One-line docstring should not occupy 3 lines
31:41: E251 unexpected spaces around keyword / parameter equals
31:43: E251 unexpected spaces around keyword / parameter equals
31:66: E251 unexpected spaces around keyword / parameter equals
31:68: E251 unexpected spaces around keyword / parameter equals
31:94: E251 unexpected spaces around keyword / parameter equals
31:96: E251 unexpected spaces around keyword / parameter equals
31:123: E251 unexpected spaces around keyword / parameter equals
31:125: E251 unexpected spaces around keyword / parameter equals
31: D102 Docstring missing
35:5: E303 too many blank lines (2)
35: D401 First line should be imperative: 'Tokenize', not 'Tokenizes'
35: D400 First line should end with '.', not 'y'
46: D102 Docstring missing
49: D102 Docstring missing
52: D102 Docstring missing
55: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
30:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.modules.indexer.tokenizers.BibIndexMultiFieldTokenizer
50: D203 Expected 1 blank line *before* class docstring, found 0
50: D205 Blank line missing between one-line summary and description
50: D208 Docstring is over-indented
60:41: E251 unexpected spaces around keyword / parameter equals
60:43: E251 unexpected spaces around keyword / parameter equals
60:66: E251 unexpected spaces around keyword / parameter equals
60:68: E251 unexpected spaces around keyword / parameter equals
60:94: E251 unexpected spaces around keyword / parameter equals
60:96: E251 unexpected spaces around keyword / parameter equals
60:123: E251 unexpected spaces around keyword / parameter equals
60:125: E251 unexpected spaces around keyword / parameter equals
60: D102 Docstring missing
67:5: E303 too many blank lines (2)
67: D400 First line should end with '.', not 's'
67: D205 Blank line missing between one-line summary and description
112: D401 First line should be imperative: 'Tokenize', not 'Tokenizes'
112: D205 Blank line missing between one-line summary and description
128: D102 Docstring missing
131: D102 Docstring missing
134: D102 Docstring missing
137: D102 Docstring missing
140: D102 Docstring missing


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
26:1: F401 'CFG_BIBINDEX_INDEX_TABLE_TYPE' imported but unused
31:1: E303 too many blank lines (3)
31: D203 Expected 1 blank line *before* class docstring, found 0
31: D205 Blank line missing between one-line summary and description
31: D208 Docstring is over-indented
59:41: E251 unexpected spaces around keyword / parameter equals
59:43: E251 unexpected spaces around keyword / parameter equals
59:66: E251 unexpected spaces around keyword / parameter equals
59:68: E251 unexpected spaces around keyword / parameter equals
59:94: E251 unexpected spaces around keyword / parameter equals
59:96: E251 unexpected spaces around keyword / parameter equals
59:123: E251 unexpected spaces around keyword / parameter equals
59:125: E251 unexpected spaces around keyword / parameter equals
59: D400 First line should end with '.', not 'y'
59: D205 Blank line missing between one-line summary and description
59: D208 Docstring is over-indented
68:5: E303 too many blank lines (2)
68: D401 First line should be imperative: 'Pick', not 'Picks'
68: D400 First line should end with '.', not ')'
73:5: E303 too many blank lines (2)
73: D102 Docstring missing
76: D102 Docstring missing
79: D102 Docstring missing
81:1: W391 blank line at end of file


Nieuwe JDK vereist: Java SE Development Kit 8u40


I know in this case you probably don't need to worry about security, but in general, simple quoting isn't enough. What if `path` contains quote characters? The "--" is also important as it instructs the program to disable option parsing for the remaining arguments.

Threads would be nice :)


Well hardcoded stuff is always nasty and I haven't seen this code as I just ported the old one.
But from my understanding, this shouldn't cause much problems? It's just calculating the window height and the correct position for the list and the image.


С++14 шагает по миру, думаю, что стоит забыть про C++0x


@luiges90 只能在这找你了，安装版怎么弄啊？我下载N次都生成不了EXE应用程序:sweat:


Зачем оно в public? У тебя есть getInstance().


TeamCity xBIM :: XbimExchange :: Build [Build 132](http://ncl-xbim.hq.4projects.com:8080/viewLog.html?buildId=1185&buildTypeId=XBIM_XbimExchange_Build) is now running


Мне все же кажется что в сленг Ru Rust комьюнити достаточно прочно уже засел этот термин. Впервые я его увидел [тут](http://www.ibm.com/developerworks/ru/library/l-rust_15/index.html), после встречал на нескольких выступлениях, посвященных Rust. Переводить как "ящик" - по мне так не очень красиво звучит. Думаю пока этот вопрос оставить открытым и следить за изменениями сленга Ru Rust комьюнити.


@matthew-andrews why?


Yeah. I was looking through the frameworks and noticed you added quick unlock, but I can't find it anywhere in the settings. Decided to check it out and turns out you accidentally deleted them when you added lock screen shortcuts lol.


Реализацию лучше в .cpp поместить. Также, проверь, что этот метод не будет вызываться из нескольких тредов, т.к. он не потокобезопасен.


TeamCity xBIM :: XbimExchange :: Build [Build 132](http://ncl-xbim.hq.4projects.com:8080/viewLog.html?buildId=1185&buildTypeId=XBIM_XbimExchange_Build) outcome was **FAILURE**
Summary: Compilation error: Xbim.COBieLite.SerialisationHelper\SerialisationHelper.csproj Build time: 00:00:42


Тебе точно нужен этот оператор? Для чего тебе копировать Game?


Individual commits are not tagged unless someone specifically tags it before pushing their changes to the repo. I was hoping that we as a group would decice on when it was apropiate for a commit to be tagged as the next version of the scripts (v0.1, v0.2, v0.3) at which point it would be uploaded to the public testing server by a script running on my own server.


Awesome, thanks.


... and sorry, I hadn't realized when I wrote that that you already updated the example in the docstring and removed the flux rescaling.  So in the commit I pushed, I just updated the docstring to be a bit more explicit about the flux scaling, and made clear in demo11 that it's a rescaling by effective area taking into account obscuration.  (This is only a 10% effect for HST but since it could be significant for some telescopes, I thought it was worth including it in the demo.)


Resolves #3


Same on Linux, also reported in issue #455.

I also have:
[ 74%] Scanning dependencies of target yarpmotorgui-gtk
Building CXX object src/yarpmotorgui-qt/CMakeFiles/yarpmotorgui-qt.dir/main.cpp.o
/usr/local/src/robot/icub-src/yarp/src/yarpmotorgui-qt/main.cpp:18:24: fatal error: yarp/os/os.h: No such file or directory
 #include <yarp/os/os.h>

using capital <yarp/os/Os.h> fix this


Well, you should think that part. Your shorthand is right when you want fo execute this on `ready`. But you should run Lazy whenever the window was loaded and all initial images are available. [$(window).load()](http://api.jquery.com/load-event/) is executed exactly then. IMO is `ready`a bit to early and not so `lazy`. ;)


@locutus2

Thanks...I wouldn't be able to do this without you implementing cmh in the first place.


This revision is clean.


Typo -INIFINITY -> -INFINITY


@barbalberto isn't it better to have `yarp/os/all.h`?


Убрать эту зависимость. Количество аргументов должно храниться в каждой команде.


what type should be used for temperature?

the relation between type and signature (in REG_DATA) is very simple:
int8_t -> 'i8'
int16_t -> 'i16'
int32_t -> 'i32'
double -> 'd' (8 bytes)

all of these types should be written as:
SendBytes(&value, sizeof(value));

you can check received bytes on gateway side to evaluate your changes.

2015-03-23 15:52 GMT+03:00 thakorjay <notifications@github.com>:

> But using this SendString(value) function, the device didnt send the value
> as a notification to gateway. So there would be no output on gateway.
>
> And i also cant use int or double data type for temperature because of
> type conversion error.
>
> What can be done for this ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/devicehive/devicehive-cpp/commit/3319387fab4cee5747676aa5bf61924a8ef893cc#commitcomment-10343673>
> .
>


I'd call it simply `getPatchType` since the vertex count options plays a role in the options only if the patch type is polygon.

I would elaborate in the H1 line along these lines: depending on the number of vertices, patches can be triangular, rectangular or polygons (see 5.8.1 Additional Patch Types -  patchplots library). Polygons require the vertex count = # in the options.


You may have to experiment around with this to find a solution that works with the current V8. JS peers of dead ruby objects are enqueued because the `destroy` method is called from within the Ruby GC thread, and it is critical to not acquire *any* locks or do *any* extra work from there.

The solution was to use a [lock-free queue] so that references could be safely enqueued from any thread, and then de-queued from within the V8 GC thread.

I imagine that the solution now will be to have each Isolate contain its own queue.

[1]: http://www.drdobbs.com/parallel/writing-lock-free-code-a-corrected-queue/210604448


Спасибо, понял.


Actually, any wile can be a member of a Group. User is just the most common.


ゲームクラスっぽいものを追加してみました。
自機の移動と弾が撃てます。弾をいっぱい打つと出なかったりしてますが多分バグってます；

とりあえずで作ったものなので今後の方針で合わないようなら全消してしまってください


That should say, "any role"


Maybe we should call it `setColor`?


I think I have to update also the cmake file. Working on it


Good point!


+1 za czujność ;)


この変更は
　・Paused(一時停止)の場合は先頭から再生
　・Stopped(=停止)の場合は停止位置から今の位置(？)から再生
ってことになると思うけど、この意図がわかりません。
var restart = true;
じゃダメなの？


Sounds like a plan, and thanks for updating my script. #operationrookiestillineffect


I think I have to update the cmake file. Working on it


Так же как и часть кода с коментарием выше, был взят из просторов сети на тему `cpp singleton example`. Если он не является необходимым, то удалю.


yea, I have just done it. Using temperatur:u8  in notification registration.


Check line 35 for typo?

Actually, "exists" gives the answer regardless of permissions. Because a user can always detect the existence of a record anyway, by trying to create it.


![screenshot 2015-03-23 09 27 03](https://cloud.githubusercontent.com/assets/636651/6780823/d5bf30c6-d13e-11e4-9005-e515888445e6.png)

Thanks for the comment! Though I may do it all differently these days, I was trying to go for a word that fit the fishing domain better than just `delete`


Ты конечно же можешь использовать $scope, только есть вопрос: почему бы не следовать best practices?


Doesn't this copyright claim conflict with:

Copyright (c) 2011-2012 The Linux Foundation. All rights reserved.

?


I did Google define it, I thought it was just bazaar then when your commit message said it too I was a little confused but yeah, learn something new every day :D


Right, thanks, will edit.


Hi Akshat,

I'm sorry that I didn't notice this difference. I went through the codes you wrote for parsing the sushi pref, but I still don't understand which method requires the certain format of sushi pref.

Thanks


Typo canols, did you wanted to write canola instead?


If you want to remove an unused function that you introduced in the previous commit, please amend said commit or use `git reset` to undo the commit.
In any case it's advisable to clean up such manoeuvres in your local history before you push your branch on master, as they unnecessarily clutter the history.
`git rebase -i` is your friend here.

We won't revert anything here, of course, but please keep in mind for the future.


Using Blender's display of executed commands is great for getting your hands on the right commands quickly, but if you do so, please make sure to get rid of stuff like `7.54979e-08` and put a `0` instead.


You filter for exactly the phrase "Limited Draft / Sealed".
It should be more general. Other server owners might use a different label or have independent labels for Draft and Sealed. Wooger used "Draft/Sealed" before as well. Others just go for "Limited". I can imagine a mixture of these being used by server owners.

Search for one of the word matches "limited", "draft" or "sealed" instead?


- `NOTE The two templates` is also `COMPATIBILITY`
- 5th bullet: please remove empty lines inside
- maybe 3rd and 4th bullet can be joined


The name is a bit counter intuitive. I was thinking about `hideFromLegend` but then it would read as if it was always hiding it. I feel this function is missing something, like some unity in the action of adding a legend entry or not.


btw:

that's the reason array literals are still created as non dense array and
why we need two constructors for arrays:
the first step was to improve `arguments` arrays (e.g. for calls to
cfunctions). It turns out the improvements are tiny in the overall execution
although the improvements are substantial in some cases.

On Sun, Mar 22, 2015 at 11:40 AM, Sergey Lyubka <notifications@github.com>
wrote:

> Here are some sparse arrays (there are many of those actually):
>
> tail -c +7726031 tests/ecmac.db|head -c 588
> tail -c +7790745 tests/ecmac.db|head -c 572
>
> Having two codepaths sucks IMO.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cesanta/v7/commit/e49b146c2b6f78dc7cd7fe09407ef7b02de73a1a#commitcomment-10332761>
> .
>


Ok, cool


Ugh, this was driving me crazy!  I was looking for it all over Friday.


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
3: L102 copyright year is outdated, expected 2015 but got 2013
29: D400 First line should end with '.', not 's'
29: D205 Blank line missing between one-line summary and description
66:5: B901 blind except: statement
77:5: B901 blind except: statement
95: D400 First line should end with '.', not '2'
95: D205 Blank line missing between one-line summary and description
110:9: E128 continuation line under-indented for visual indent
120: D203 Expected 1 blank line *before* class docstring, found 0
120: D204 Expected 1 blank line *after* class docstring, found 0
128: D102 Docstring missing


you will have to rebase on current version


Thanks very much!!!!!!!!!!!!!! Can you tell me this function works with which sensor? I tried some apps with proximity sensor but it's very annoying when my finger is on the sensor.


вот здесь возможна мотеря данных. Проглатываются ошибки


would it be possible to have someting like command/Parser.h ?


i really don't think, that this string need to be uncommented.


Please make .mo yourself.
I don't know how to load it here.


Also, just wanted to report, I have had no issues using these commits. No reboots, nothing. The only reboots I have had were caused by LCD_Notify and Ambient Display. I was able to use a commits from Boeffla that tied LCD_Notify to the backlight instead of MDSS. Reboots are gone for me now. I don't know if this is related or not but thought I would share. I don't know if you use LCD_Notify.


> I think you'll also agree to "workTreePath" then.

yes.

> A submodule only exists (and has a worktree), if the parent repository is checked out (non-bare).

Not only that; but also: It cannot be initialised in a bare repository (needs a checked out tree) :)

> We have the ".gitmodules" file sleeping in the commits, which acutally carries the information, which submodules are linked. If this file exists, we can actually provide the information, that a) the repo links submodules and optionally b) a preview of those nasty url's. This information has to be gathered from the commits though and that's why I think we should do it in a future version. I'll write a feature request for MGV v0.2 in redmine, to not forget about it.

This information is hard to get (and can easily be wrong); i.e. you're right that we'd have to do that all by ourselves: libgit2 only considers a submodule when it's correctly mentioned in the `config` file and has a worktree...


= = clean files.


congratulations! reg_data is very important, because gateway has no
information except this REG_DATA to process/interpret incoming bytes.

2015-03-23 16:28 GMT+03:00 thakorjay <notifications@github.com>:

> yea, I have just done it. Using temperatur:u8 in notification registration.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/devicehive/devicehive-cpp/commit/3319387fab4cee5747676aa5bf61924a8ef893cc#commitcomment-10344429>
> .
>


This commit breaks phing execution with the following exeception.
```
12:49:07 FATAL: Unable to serialize hudson.plugins.phing.PhingInstallation$1@7e0942e0
12:49:07 java.io.IOException: Unable to serialize hudson.plugins.phing.PhingInstallation$1@7e0942e0
12:49:07 at hudson.remoting.UserRequest.serialize(UserRequest.java:169)
12:49:07 at hudson.remoting.UserRequest.<init>(UserRequest.java:63)
12:49:07 at hudson.remoting.Channel.call(Channel.java:750)
12:49:07 at hudson.plugins.phing.PhingInstallation.getExecutable(PhingInstallation.java:105)
12:49:07 at hudson.plugins.phing.PhingBuilder.computePhingCommand(PhingBuilder.java:244)
12:49:07 at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:168)
12:49:07 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
12:49:07 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
12:49:07 at hudson.model.Build$BuildExecution.build(Build.java:203)
12:49:07 at hudson.model.Build$BuildExecution.doRun(Build.java:160)
12:49:07 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
12:49:07 at hudson.model.Run.execute(Run.java:1751)
12:49:07 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
12:49:07 at hudson.model.ResourceController.execute(ResourceController.java:89)
12:49:07 at hudson.model.Executor.run(Executor.java:240)
12:49:07 Caused by: java.io.NotSerializableException: hudson.Launcher$RemoteLauncher
12:49:07 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183)
12:49:07 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547)
12:49:07 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508)
12:49:07 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
12:49:07 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
12:49:07 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
12:49:07 at hudson.remoting.UserRequest._serialize(UserRequest.java:158)
12:49:07 at hudson.remoting.UserRequest.serialize(UserRequest.java:167)
12:49:07 ... 14 more
```

Phing installation is configured with Phing HOME: `$WORKSPACE/vendor/phing/phing`, Jenkins 1.605.


You added something wrong


Arh. Great. Now it's exactly like mine :)


What do you think about adding a new service for NFS3? The nfs service is for nfs4, which is not using udp. Or do you have another reason to request to add 2049/udp?


@bors: retry
* #5285


It will happen if color is 'flat' and cdata is a n by 3, e.g. when each point of a patch has its color. I deal with this in `drawPatch`. There is room for refactoring getColor, since this is also relevant for the scatterplot issue with n by 3 color data. However, it is not trivial, time consuming, and of low priority since not many use that much customization in their plots.


This method could probably be renamed to `GetTargetPlatformString` or similar.


I am coding the PHP part and Jquery part using Notepad++
I hope thats ok?


No I don't use it.
On 23 Mar 2015 14:40, "RenderBroken" <notifications@github.com> wrote:

> Also, just wanted to report, I have had no issues using these commits. No
> reboots, nothing. The only reboots I have had were caused by LCD_Notify and
> Ambient Display. I was able to use a commits from Boeffla that tied
> LCD_Notify to the backlight instead of MDSS. Reboots are gone for me now. I
> don't know if this is related or not but thought I would share. I don't
> know if you use LCD_Notify.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AK-Kernel/AK-OnePone/commit/b1871e4c7141964c87377b483c7f7a4e193adf03#commitcomment-10344642>
> .
>


Out of curiosity, how does this work if I have a `:load-path` for that package? I use `:load-path` for packages that I have forked from github. So it is very likely that the same package in my Melpa too. In that case, if a `use-package` call has `:load-path`, will it still force install the version from Melpa?


It is like systemd it is taking over everything


:heart:


I agree


Only if you use slim roms.
On 23 Mar 2015 02:08, "jgcaap" <notifications@github.com> wrote:

> whats this for exacly? thanks
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/anarkia1976/AK-OnePone/commit/624bb4b20188ae2783403698e6254e65b5ccf16b#commitcomment-10336195>
> .
>


Фильтр здесь совсем не нужен


COOL


да это фриз версий зависимостей и их зависимостей


canUpやcanDownで浮動小数点を比較しているけど、本当に大丈夫？
浮動小数点は誤差が出るからある程度の桁数で丸めてから比較したほうが安全ではないでしょうか？


Этим кодом ты просто дублируешь функционал энгулара


@okomarov, you are running in the same trap. The note was added by @egeerardyn in the meanwhile. May be have the complete PR diff open in a separate window to check, if this was already addressed.


https://github.com/kolloch/marathon/blob/master/src/main/scala/mesosphere/mesos/TaskBuilder.scala#L266-L288

There is also a `PORTS` variable.

And a `PORT_{SERVICE_PORT}` variable for every port.

Did you not document them on purpose?


убери этот файл из коммита


seems like a min-height might be desirable as well, so the scrollbar wont start from lilke 10px or so :P. too bad it wont autoscroll as well to the last msg


Тебе действительно нужен еще один модуль?


done


Even though, it appears obvious, I would describe every environment variable mentioned. A sample value is also nice.


I agree with both.

When the PR is big, it really isn't easy to see the whole PR, thus I too find it easier and faster to comment single commits. The automatic updates by github are a useful feature to keep track ov the overall progress on the comments. There is a trade-off.


This line of code should delete the bat file that was created before to run the wrapper but I always get a win32 error I can't work it out


Problem with the older version was, that it works against the function parameter type matching that is done in ChaiScript. It seems to prefer param1 to find the right overload.

I would change your generic version to:
```cpp
method_missing(<param1>, <method_name>, {<param2>, <param3>, ...});
```

This would help the <param1> to resolve to methods that actually are meant for the class.

To have an array of additional arguments would help for a generic `method_missing`. I only need it for property systems. So it does not matter to me.

The question that remains is, if you allow global method_missing. Your generic version or mine are optimized for class methods or do you use void as param1 for global methods?


@eviltoylet I did a bunch of changes. Things are a bit more stable now. Probably the main thing to understand there is that in order to make it possible to implement editors, I made the reduce thinger return first React element it finds. Otherwise it just passes value around.

Due to the amount of cases I need to support it's more complex than I would like. That said, the definition is quite flexible as you can inject `props`, create new elements, update value and so on.

I also thought more about that scheme you proposed. What if we passed an object as a parameter instead? In this case you would end up with something simple to use (with small perf hit).

Example:

```
cell: (o) => parseFloat(o.value).toFixed(2)
```

Then you could have something like `values` there (just a list of values of previous stages). Out of curiosity, where do you need that data? Do you have some specific use cases in mind?


зачем?


Nice :+1:


We might as well support it again. I think the `timeout` ends up being applied to each individual request in the multi-request (as opposed to the whole multi-request) which is fine. We originally blocked `_all`-type requests back when kibana3 seemed to be making searches against that index for a reason that we could not reproduce, so disabling was the easiest solution.

We may want to drop the nginx-based request manipulation since kibana4 has [configuration options](http://www.elastic.co/guide/en/kibana/current/settings.html#id-1.8.47.3) applicable to timeouts which it takes care of adding to requests.


is `data` an idiomatic name for built assets?


Since we want to get rid of those (sometime) we could sacrifice the order in which they are listed by Matlab in the `go to` dropdown and call them `opts2legacy` and `legacy2opts`. I personally find it faster to read and understand.


1: M111 unrecognized component name: bibcirculation


We could also add a test for the `style.width.px` form just to play it on the safe-side.


返り値は、
```
[{
    music_name: 'HELL SCAPER -Last Escape Remix-',
    artist: 'Remixed by DJ TECHNORCH fw. GUHROOVY',
    genre: 'GABBAH',
    bpm: [ 180 ],
    spn_difficulty: 5,
    sph_difficulty: 8,
    spa_difficulty: 11,
    dpn_difficulty: 6,
    dph_difficulty: 9,
    dpa_difficulty: 11,
    spn_cn: false,
    sph_cn: false,
    spa_cn: false,
    dpn_cn: false,
    dph_cn: false,
    dpa_cn: false,
    spn_bss: false,
    sph_bss: false,
    spa_bss: false,
    dpn_bss: false,
    dph_bss: false,
    dpa_bss: false
},
...]
```
のようになります。


I'm not sure what issue this solves, running phpunit gives this output using a clone of the current repo:

```
PHPUnit 4.4.5 by Sebastian Bergmann.

Configuration read from /home/tom/srv/Dice/phpunit.xml

................................................................. 65 / 83 ( 78%)
..................

Time: 86 ms, Memory: 7.00Mb

OK (83 tests, 133 assertions)
```


"Riseup peuvent sont également"
Juste mettre "sont" non ? Ou tourner la phrase autrement pour utiliser peuvent mais pas garder les deux ^^


この中身って
return this.audioPlayers.Any(item => item.PlayState == PlayState.Playing);
だけでよくない？


ㄅ


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1109
success: http://build.servo.org/builders/linux2/builds/1109
success: http://build.servo.org/builders/android/builds/1143
success: http://build.servo.org/builders/mac1/builds/1323
success: http://build.servo.org/builders/mac2/builds/1325
success: http://build.servo.org/builders/gonk/builds/291


In fact, the problem with `RegularStatement` is that it doesn't carry the values' types, so we have no way to deserialize them back.
I think it's fair to assume that queries that run multiple times with different parameters should use bound statements, so there should be no ambiguity for a regular statement, even if it's values are not logged.
So let's keep this the way it is.


Мы не будем использовать этот модуль...


Você chegou a alguma conclusão sobre tempo para calcular 1Kb?


auto &

 in c++11, is `item` is taken by copy, put `auto &` to take by reference. (corrected in c++14)


add @param $method


Fix no pull teste


Cna we call it `is*`?


Você chegou a alguma conclusão sobre tempo para calcular a criptografia de 1Kb?


That's right, it's not a valid C. Declarations should be at the beginning of the block.


Почему не стандартый native(!) оптимизированны(!) метод массива, а angular.forEach?


ovoid or avoid?


fast-forwarding master to auto = f9826c3a


Да и почему forEach? Есть [].filter()


Codebook is included here.


Will respond to this later today or tomorrow morning at latest.


can we call it
`[data, env, sColumn] =  getScatterData(...'?


если цена меньше минимума...


Tabs are pretty janky on different machines, I'd use 2 spaces (mostly because our style guide says to) :smile:

You can usually add a setting to your editor to use 2 spaces for tabs.


@tkelman Here you go #10606


I think I like your most recently proposal the best:

```
method_missing(<param1>, <method_name>, {<param2>, <param3>, ...});
```

This feels more natural, and goes with the name of it "*method*_missing"

I don't think we should allow a 0-parameter global version at all, being able to do:

`some_unknown_name()` and have it call `method_missing(void, "some_unknown_name")` doesn't make much sense to me.


saw approval from Ms2ger
at https://github.com/frewsxcv/servo/commit/c0ea1e633045b0b4592808b426c4d3e08ad77537


merging frewsxcv/servo/patch-1 = c0ea1e63 into auto


frewsxcv/servo/patch-1 = c0ea1e63 merged ok, testing candidate = ca79abe4


Thats we need


No... but in this project I noticed it's where the other committed-to-git-built-asset is (allDeps.zip).


Здесь for(var i...), а ниже в коде - forEach...  Использование .filter() сократило код до 3 строк.


Использование .filter() сократило код до 3 строк.


что это?


[R/coalesce_na.R:26:17:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/coalesce_na.R#L26) *style:* **Only use double-quotes.**
```r
        warning('object length is not a multiple of first object length')
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/coalesce_na.R:28:19:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/coalesce_na.R#L28) *style:* **Place a space before left parenthesis, except in a function call.**
```r
      x[pos] <- y[(pos - 1) %% y.len + 1]
                  ^
```
[R/export.R:20:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/export.R#L20) *style:* **lines should not be more than 80 characters.**
```r
export.list <- function(arg.list, arg.names=names(arg.list), target.env=.GlobalEnv) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/export.R:20:73:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/export.R#L20) *style:* **Variable and function names should be all lowercase.**
```r
export.list <- function(arg.list, arg.names=names(arg.list), target.env=.GlobalEnv) {
                                                                        ^~~~~~~~~~
```
[R/export.R:22:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/export.R#L22) *style:* **lines should not be more than 80 characters.**
```r
  for (i in seq_along(arg.names)) assign(arg.names[i], arg.list[[i]], target.env)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/export.R:44:36:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/export.R#L44) *style:* **Variable and function names should be all lowercase.**
```r
export <- function(..., target.env=.GlobalEnv) {
                                   ^~~~~~~~~~
```
[R/export.R:47:3:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/export.R#L47) *warning:* **no visible global function definition for ‘export.list’**
```r
  export.list(arg.list, arg.names, target.env)
  ^~~~~~~~~~~
```
[R/gdiff.R:37:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/gdiff.R#L37) *style:* **lines should not be more than 80 characters.**
```r
      x <- FUN(x[i1, , drop = FALSE], x[-nrow(x):-(nrow(x) - lag + 1L), , drop = FALSE])
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/hms_to_seconds.R:17:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L17) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
hms.to.seconds <- function(x) {
^~~~~~~~~~~~~~
```
[R/hms_to_seconds.R:18:9:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L18) *style:* **Only use double-quotes.**
```r
  re <- '^([0-9]+):([0-9]+):([0-9]+)|.*$'
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/hms_to_seconds.R:19:32:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L19) *style:* **Only use double-quotes.**
```r
  hours <- as.integer(gsub(re, '\\1', x))
                               ^~~~~
```
[R/hms_to_seconds.R:20:34:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L20) *style:* **Only use double-quotes.**
```r
  minutes <- as.integer(gsub(re, '\\2', x))
                                 ^~~~~
```
[R/hms_to_seconds.R:21:34:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L21) *style:* **Only use double-quotes.**
```r
  seconds <- as.integer(gsub(re, '\\3', x))
                                 ^~~~~
```
[R/hms_to_seconds.R:24:13:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/hms_to_seconds.R#L24) *style:* **Only use double-quotes.**
```r
    warning('NAs introduced by coercion')
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/in_interval.R:16:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L16) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
nin.interval.ro <- function(x, lo, hi) is.na(.bincode(x, c(lo, hi), right=F))
^~~~~~~~~~~~~~~
```
[R/in_interval.R:34:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L34) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
in.interval.ro <- function(x, lo, hi) !nin.interval.ro(x, lo, hi)
^~~~~~~~~~~~~~
```
[R/in_interval.R:34:40:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L34) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
in.interval.ro <- function(x, lo, hi) !nin.interval.ro(x, lo, hi)
                                       ^~~~~~~~~~~~~~~
```
[R/in_interval.R:51:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L51) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
nin.interval.lo <- function(x, lo, hi) is.na(.bincode(x, c(lo, hi), right=T))
^~~~~~~~~~~~~~~
```
[R/in_interval.R:69:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L69) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
in.interval.lo <- function(x, lo, hi) !nin.interval.lo(x, lo, hi)
^~~~~~~~~~~~~~
```
[R/in_interval.R:69:40:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/in_interval.R#L69) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
in.interval.lo <- function(x, lo, hi) !nin.interval.lo(x, lo, hi)
                                       ^~~~~~~~~~~~~~~
```
[R/nlist.R:50:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/nlist.R#L50) *style:* **Variable and function names should be all lowercase.**
```r
setMissingNames <- function(object, nm) {
^~~~~~~~~~~~~~~
```
[R/nlist.R:63:3:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/nlist.R#L63) *style:* **Variable and function names should be all lowercase.**
```r
  setMissingNames(object, vapply(expr, deparse, character(1)))
  ^~~~~~~~~~~~~~~
```
[R/sample_data_frame.R:17:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/sample_data_frame.R#L17) *style:* **Opening curly braces should never go on their own line and should always be followed by a new line.**
```r
{
^
```
[R/seconds_to_hms.R:15:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/seconds_to_hms.R#L15) *style:* **Words within variable and function names should be separated by '_' rather than '.'.**
```r
seconds.to.hms <- function(x) {
^~~~~~~~~~~~~~
```
[R/seconds_to_hms.R:25:18:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/seconds_to_hms.R#L25) *style:* **Only use double-quotes.**
```r
  ret <- sprintf('%.2d:%.2d:%.2d', hours, abs(minutes), abs(seconds))
                 ^~~~~~~~~~~~~~~~
```
[R/thisfile.R:40:3:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L40) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgs <- commandArgs(trailingOnly = FALSE)
  ^~~~~~~
```
[R/thisfile.R:41:3:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L41) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgsTrailing <- commandArgs(trailingOnly = TRUE)
  ^~~~~~~~~~~~~~~
```
[R/thisfile.R:42:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L42) *style:* **lines should not be more than 80 characters.**
```r
  cmdArgs <- cmdArgs[seq.int(from=1, length.out=length(cmdArgs) - length(cmdArgsTrailing))]
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/thisfile.R:42:3:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L42) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgs <- cmdArgs[seq.int(from=1, length.out=length(cmdArgs) - length(cmdArgsTrailing))]
  ^~~~~~~
```
[R/thisfile.R:42:14:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L42) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgs <- cmdArgs[seq.int(from=1, length.out=length(cmdArgs) - length(cmdArgsTrailing))]
             ^~~~~~~
```
[R/thisfile.R:42:56:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L42) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgs <- cmdArgs[seq.int(from=1, length.out=length(cmdArgs) - length(cmdArgsTrailing))]
                                                       ^~~~~~~
```
[R/thisfile.R:42:74:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L42) *style:* **Variable and function names should be all lowercase.**
```r
  cmdArgs <- cmdArgs[seq.int(from=1, length.out=length(cmdArgs) - length(cmdArgsTrailing))]
                                                                         ^~~~~~~~~~~~~~~
```
[R/thisfile.R:43:46:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/thisfile.R#L43) *style:* **Variable and function names should be all lowercase.**
```r
  res <- gsub("^(?:--file=(.*)|.*)$", "\\1", cmdArgs)
                                             ^~~~~~~
```
[R/tll.R:18:5:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/R/tll.R#L18) *style:* **Variable and function names should be all lowercase.**
```r
    setMissingNames(object=seq_along(l[[1]]), nm=names(l[[1]])),
    ^~~~~~~~~~~~~~~
```
[tests/testthat/test-gdiff.R:8:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/tests/testthat/test-gdiff.R#L8) *style:* **lines should not be more than 80 characters.**
```r
  expect_equal(gdiff(x, lag = 4, differences = 5), diff(x, lag = 4, differences = 5))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[tests/testthat/test-vswitch.R:6:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/tests/testthat/test-vswitch.R#L6) *style:* **lines should not be more than 80 characters.**
```r
  expect_equal(vswitch(LETTERS, A=1, B=2, 3), c(1:3, rep(3, length(LETTERS) - 3)))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[tests/testthat/test-vswitch.R:7:1:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/tests/testthat/test-vswitch.R#L7) *style:* **lines should not be more than 80 characters.**
```r
  expect_equal(vswitch(LETTERS, A=1, B=1+1, 3, D=2*2), c(1:4, rep(3, length(LETTERS) - 4)))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[tests/testthat/test-vswitch.R:7:41:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/tests/testthat/test-vswitch.R#L7) *style:* **Put spaces around all infix operators.**
```r
  expect_equal(vswitch(LETTERS, A=1, B=1+1, 3, D=2*2), c(1:4, rep(3, length(LETTERS) - 4)))
                                       ~^~
```
[tests/testthat/test-vswitch.R:7:51:](https://github.com/krlmlr/kimisc/blob/8a6ae176630064f03fcf5040cd7bba14e1c0465a/tests/testthat/test-vswitch.R#L7) *style:* **Put spaces around all infix operators.**
```r
  expect_equal(vswitch(LETTERS, A=1, B=1+1, 3, D=2*2), c(1:4, rep(3, length(LETTERS) - 4)))
                                                 ~^~
```


But if it gets propagated, the strings with comments are replaced with the english ones.


J'aime bien <3


^_^ ce sera corrigé, merci.


Maybe a nice addition to do this for the Rails migration date format (eg 20150223152956_my_migration) as well? I understand this is less predictable because in theory users can have a filename starting with 14 numbers, but I doubt that that would ever be a problem.

The following regex and dateformat should work:

```
/([1-9][0-9]{13})/
```
```
yyyyMMddHHmmss
```


> NOTE The two templates is also COMPATIBILITY
@jirikuncar Hmm, do we have a syntax for expressing this?


Merged commit from dlpwx


Hello, after this commit, logSuccess is loosed (never extend config root)
Regards


@knu @flavorjones confirm, that was the intention of `cross_compiling`, to allow define some requirements only present in the cross compiled gem.

I wasn't aware that `required_ruby_version` supported multiple definitions (like any other requirement in RubyGems).

This definitely will help all those reports on every new version of Ruby that do not have binaries yet.

Hopefully other gem authors will follow.


Real estate project


Do we need to keep the old version of jsoncpp?


Kannte bis eben nichtmal bcrypt werde es mir mal angucken :D


We're merging and maintaining as part of the driver so we are able to devote more resources to it.
It was announced here last week: https://groups.google.com/d/topic/cqlengine-users/9_hPowKoL2Y/discussion


Does that mean io.js is not officially supported? Are there any plans to add official io.js support?


font


Hello @marcominetti

I'm not sure that this change is correct. @bajtos , why we use `/debug` path, is this related to embedding system?


Leave a comment


С оф. сайта: there are advantages to binding properties directly to the controller and avoiding scope.

Using controller as makes it obvious which controller you are accessing in the template when multiple controllers apply to an element.
If you are writing your controllers as classes you have easier access to the properties and methods, which will appear on the scope, from inside the controller code.
Since there is always a . in the bindings, you don't have to worry about prototypal inheritance masking primitives.


Вызов функции orderByKey лишний


@edolstra I don't think so, the new version should be API compatible. In the changes I pushed to `staging`, I have removed the old version of `jsoncpp` and all the old versions of `cmake`, so once that builds, we'll know if it's safe to remove. I just didn't want to keep breaking `master`!


Qué signifca 'we have to leave'? Leave qué?


@ipgray We need to solve the IPCC institution problem.
Left to be added:
  David J. Griggs, IPCC Technical Support Unit, UK
  Catherine A. Johnson, IPCC Technical Support Unit, UK
  Kathy Maskell, IPCC Technical Support Unit, UK
  Maria Noguer, IPCC Technical Support Unit, UK
  Robert T. Watson, IPCC, USA

Jim M. Haywood, Hadley Centre for Climate Prediction and Research, UK : I have a James M. Haywood and a J. Haywood, which one is the good one?

The others are done.


Tenía la misma duda. Copié literal lo que resumiste en friday fun:
"Postear en #accountability el plan para el día en los primeros 10min o te tenés que ir antes", pero está pendiente por cambiar. Sólo necesito que me expliqués a qué te referías


Эх. И тут мне внезапно грустно стало.


Possibly, just wasn't sure if we were going to have access to the socket if we abstract away the message code (or if it would make to have access to it given the abstraction)


where is public from?


@gitscrubz Ah, that's a shame. Any help stabilizing the drag/drop feature would be greatly appreciated.


Ya veo. Me refería a que si tienes que salir a las 11am por ejemplo (1 hora antes de que acaben las 4 horas), eso también cuenta como no estar disponible durante las 4 horas.


Notes\Model\Note Object
(
   [id] => 1
   [userId] => 1
   [title] => Web
   [body] => PHP is a powerful tool for making dynamic Web pages.
   [createdOn] =>
   [lastUpdatedOn] =>
   [isDeleted] => 0
   [noteTag] => Notes\Collection\Collection Object
       (
           [total:Notes\Collection\Collection:private] => 2
           [count:Notes\Collection\Collection:private] => 0
           [pointer:Notes\Collection\Collection:private] => 0
           [objects:Notes\Collection\Collection:private] => Array
               (
                   [0] => Notes\Model\NoteTag Object
                       (
                           [id:Notes\Model\NoteTag:private] => 1
                           [noteId:Notes\Model\NoteTag:private] => 1
                           [userTagId:Notes\Model\NoteTag:private] => 1
                           [isDeleted:Notes\Model\NoteTag:private] => 1
                           [userTag:Notes\Model\NoteTag:private] => Notes\Model\UserTag Object
                               (
                                   [id:Notes\Model\UserTag:private] => 1
                                   [userId:Notes\Model\UserTag:private] => 1
                                   [tag:Notes\Model\UserTag:private] => OOP PHP
                                   [isDeleted:Notes\Model\UserTag:private] => 1
                               )

                       )

                   [1] => Notes\Model\NoteTag Object
                       (
                           [id:Notes\Model\NoteTag:private] => 3
                           [noteId:Notes\Model\NoteTag:private] => 1
                           [userTagId:Notes\Model\NoteTag:private] => 3
                           [isDeleted:Notes\Model\NoteTag:private] =>
                           [userTag:Notes\Model\NoteTag:private] => Notes\Model\UserTag Object
                               (
                                   [id:Notes\Model\UserTag:private] => 3
                                   [userId:Notes\Model\UserTag:private] => 1
                                   [tag:Notes\Model\UserTag:private] => PDOException
                                   [isDeleted:Notes\Model\UserTag:private] =>
                               )

                       )

                   [2] => Notes\Model\NoteTag Object
                       (
                           [id:Notes\Model\NoteTag:private] => 4
                           [noteId:Notes\Model\NoteTag:private] => 1
                           [userTagId:Notes\Model\NoteTag:private] => 4
                           [isDeleted:Notes\Model\NoteTag:private] =>
                           [userTag:Notes\Model\NoteTag:private] => Notes\Model\UserTag Object
                               (
                                   [id:Notes\Model\UserTag:private] => 4
                                   [userId:Notes\Model\UserTag:private] => 1
                                   [tag:Notes\Model\UserTag:private] => Runtime
                                   [isDeleted:Notes\Model\UserTag:private] =>
                               )

                       )

               )

       )

)


I think lodash/underscore has some stuff like this already.


For profile specific parameter, you should add a OS environment variable to control it.  Also, please add a sample run script under ../scripts to demo how to use it. Eventually, I will use the script as base for profile document.


E-commerce in real estate


g


it seems you are not using .indexGroup, may take this out


@pchlupacek you broke the "ordered alphabetically by last name" rule! :-)


Le prof nous avait dit de ne pas toucher au framerate.


~~~ {cpp}
struct help { std::string usage; std::string description; };
std::vector<help> helps = {{helpCommand, helpCommandDescription}};
~~~


Nice! It is always quite possible that I have no idea what I'm typing anyways - so it never hurts to have the conversation.


Yeah, not every URI is defined in the API root. This particular link relation is available on the user resource and already expanded for you: https://api.github.com/users/lalalah

While we want Octokit to be eventually completely hypermedia-driven, until we can get a caching mechanism in place to offset needing to make multiple API calls to get get the right link relation, we'll need to do exactly as you've done here.


Good catch. Those must have been auto-corrected for me during the upgrade as I missed them but was still able to build. Can you add brackets around the 1-line if statement(s)?


Woops, I misused the $log statement. The changes to the dist were just from running grunt.  Just pushed the changes.


well done, @glogiotatidis


Minor, but would assert() or assert.isTrue() be more straightforward?   Also it's good to have hint text as the final argument, so that if one of the asserts fail you know which one failed.

```
assert.isTrue(result.contextIsOk, "contextIsOk");
assert.isTrue(result.selectorTargetIsOk, "selectorTargetIsOk");
```

Same comment for the asserts below.


It restarts the game a lot, and saves information to data files each time. Does it also save the game every turn because of permadeath?

Most of the restarts are in just a few tests - Starting Kits does it the most, restarting the game up to 256 times.


I think it is fixws now. I added some files but i did not update the cmake


Player1で設定した音楽の演奏時間に設定しているけど、必ずしもすべてのPlayerの演奏時間が同じではないのでは？
再生位置を同期するだけじゃないの？


I just ran it with `python tock/manage.py test` and it passed travis. Do you want me to merge, or change it in a commit? Then I'll merge.


After thinking about this, I prefer to not ping read to particular workers, instead, you can add a percentage, such as 10% of the Next operation is Read. Still use environment variable to control the percentage.


This check is redundant as the check above would throw an error if `config` was not enabled.