27:1: I100 Imports statements are in the wrong order. from invenio.base.helpers should be before from six
28:1: I101 Imported names are in the wrong order. Should be CFG_BINDIR, CFG_SITE_LANG, CFG_SITE_URL
29:1: I101 Imported names are in the wrong order. Should be addadminbox, createhiddenform, get_def_name, get_languages, get_name, modify_translations, tupletotable, write_outcome
38:1: I101 Imported names are in the wrong order. Should be get_table_status_info, run_sql, wash_table_column_name
38:1: I100 Imports statements are in the wrong order. from invenio.legacy.dbquery should be before from invenio.modules.access.engine
40:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_stemmer should be before from invenio.legacy.dbquery
42:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_COLUMN_VALUE_SEPARATOR, CFG_BIBINDEX_SYNONYM_MATCH_TYPE
42:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_config should be before import invenio.legacy.template
45:1: I101 Imported names are in the wrong order. Should be get_all_index_names_and_column_values, get_all_indexes, get_all_virtual_indexes, get_idx_indexer, get_index_fields, get_index_name_from_index_id, get_index_virtual_indexes, get_virtual_index_building_blocks, is_index_virtual, load_tokenizers
45:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibindex.engine_utils should be before from invenio.modules.knowledge.api
503: D103 Docstring missing
534: D202 No blank lines allowed *after* function docstring, found 1
569: D202 No blank lines allowed *after* function docstring, found 1
603: D202 No blank lines allowed *after* function docstring, found 1
638: D209 Put multi-line docstring closing quotes on separate line
638: D202 No blank lines allowed *after* function docstring, found 1
638: D205 Blank line missing between one-line summary and description
669: D209 Put multi-line docstring closing quotes on separate line
669: D205 Blank line missing between one-line summary and description
669: D208 Docstring is over-indented
724: D209 Put multi-line docstring closing quotes on separate line
724: D202 No blank lines allowed *after* function docstring, found 1
724: D400 First line should end with '.', not 'x'
724: D205 Blank line missing between one-line summary and description
806: D209 Put multi-line docstring closing quotes on separate line
806: D202 No blank lines allowed *after* function docstring, found 1
806: D400 First line should end with '.', not 'd'
806: D205 Blank line missing between one-line summary and description
887: D209 Put multi-line docstring closing quotes on separate line
887: D202 No blank lines allowed *after* function docstring, found 1
887: D205 Blank line missing between one-line summary and description
930: D209 Put multi-line docstring closing quotes on separate line
930: D202 No blank lines allowed *after* function docstring, found 1
930: D205 Blank line missing between one-line summary and description
969: D209 Put multi-line docstring closing quotes on separate line
969: D202 No blank lines allowed *after* function docstring, found 1
969: D205 Blank line missing between one-line summary and description
1003: D202 No blank lines allowed *after* function docstring, found 1
1003: D205 Blank line missing between one-line summary and description
1046: D202 No blank lines allowed *after* function docstring, found 1
1046: D205 Blank line missing between one-line summary and description
1084: D205 Blank line missing between one-line summary and description
1084: D208 Docstring is over-indented
1129: D209 Put multi-line docstring closing quotes on separate line
1129: D400 First line should end with '.', not 'x'
1129: D205 Blank line missing between one-line summary and description
1129: D208 Docstring is over-indented
1214:15: E221 multiple spaces before operator
1224: D400 First line should end with '.', not 't'
1224: D205 Blank line missing between one-line summary and description
1224: D208 Docstring is over-indented
1239: D103 Docstring missing
1290: D209 Put multi-line docstring closing quotes on separate line
1290: D202 No blank lines allowed *after* function docstring, found 1
1290: D205 Blank line missing between one-line summary and description
1326:15: E221 multiple spaces before operator
1336: D209 Put multi-line docstring closing quotes on separate line
1336: D202 No blank lines allowed *after* function docstring, found 1
1336: D205 Blank line missing between one-line summary and description
1401:15: E221 multiple spaces before operator
1411: D209 Put multi-line docstring closing quotes on separate line
1411: D205 Blank line missing between one-line summary and description
1411: D208 Docstring is over-indented
1463:15: E221 multiple spaces before operator
1473: D202 No blank lines allowed *after* function docstring, found 1
1473: D205 Blank line missing between one-line summary and description
1473: D208 Docstring is over-indented
1564: D202 No blank lines allowed *after* function docstring, found 1
1564: D400 First line should end with '.', not 'n'
1564: D205 Blank line missing between one-line summary and description
1564: D208 Docstring is over-indented
1629: D209 Put multi-line docstring closing quotes on separate line
1629: D202 No blank lines allowed *after* function docstring, found 1
1629: D205 Blank line missing between one-line summary and description
1629: D208 Docstring is over-indented
1698: D209 Put multi-line docstring closing quotes on separate line
1698: D202 No blank lines allowed *after* function docstring, found 1
1698: D205 Blank line missing between one-line summary and description
1698: D208 Docstring is over-indented
1767: D209 Put multi-line docstring closing quotes on separate line
1767: D202 No blank lines allowed *after* function docstring, found 1
1767: D205 Blank line missing between one-line summary and description
1767: D208 Docstring is over-indented
1837: D209 Put multi-line docstring closing quotes on separate line
1837: D202 No blank lines allowed *after* function docstring, found 1
1837: D205 Blank line missing between one-line summary and description
1873:15: E221 multiple spaces before operator
1923:8: E221 multiple spaces before operator
1952: D202 No blank lines allowed *after* function docstring, found 1
1968:8: E221 multiple spaces before operator
2009: D205 Blank line missing between one-line summary and description
2009: D208 Docstring is over-indented
2040:24: W601 .has_key() is deprecated, use 'in'
2074: D209 Put multi-line docstring closing quotes on separate line
2074: D202 No blank lines allowed *after* function docstring, found 1
2074: D205 Blank line missing between one-line summary and description
2119: D209 Put multi-line docstring closing quotes on separate line
2119: D202 No blank lines allowed *after* function docstring, found 1
2119: D205 Blank line missing between one-line summary and description
2154: D209 Put multi-line docstring closing quotes on separate line
2154: D202 No blank lines allowed *after* function docstring, found 1
2154: D205 Blank line missing between one-line summary and description
2181:18: E713 test for membership should be 'not in'
2195: D209 Put multi-line docstring closing quotes on separate line
2195: D202 No blank lines allowed *after* function docstring, found 1
2195: D205 Blank line missing between one-line summary and description
2229: D209 Put multi-line docstring closing quotes on separate line
2229: D202 No blank lines allowed *after* function docstring, found 1
2229: D205 Blank line missing between one-line summary and description
2243: D209 Put multi-line docstring closing quotes on separate line
2243: D202 No blank lines allowed *after* function docstring, found 1
2243: D205 Blank line missing between one-line summary and description
2249:11: E221 multiple spaces before operator
2263:9: E221 multiple spaces before operator
2270:23: W601 .has_key() is deprecated, use 'in'
2306:15: E221 multiple spaces before operator
2314: D202 No blank lines allowed *after* function docstring, found 1
2314: D400 First line should end with '.', not 's'
2320: D401 First line should be imperative: 'Return', not 'Returns'
2320: D209 Put multi-line docstring closing quotes on separate line
2320: D202 No blank lines allowed *after* function docstring, found 1
2320: D205 Blank line missing between one-line summary and description
2339: D103 Docstring missing
2353: D401 First line should be imperative: 'Return', not 'Returns'
2353: D202 No blank lines allowed *after* function docstring, found 1
2353: D400 First line should end with '.', not 'e'
2362: D401 First line should be imperative: 'Return', not 'Returns'
2362: D202 No blank lines allowed *after* function docstring, found 1
2362: D400 First line should end with '.', not 'e'
2371: D401 First line should be imperative: 'Return', not 'Returns'
2371: D202 No blank lines allowed *after* function docstring, found 1
2371: D400 First line should end with '.', not 'e'
2380: D401 First line should be imperative: 'Return', not 'Returns'
2380: D202 No blank lines allowed *after* function docstring, found 1
2380: D400 First line should end with '.', not 'e'
2389: D401 First line should be imperative: 'Return', not 'Returns'
2389: D202 No blank lines allowed *after* function docstring, found 1
2389: D400 First line should end with '.', not 'e'
2398: D401 First line should be imperative: 'Return', not 'Returns'
2398: D209 Put multi-line docstring closing quotes on separate line
2398: D202 No blank lines allowed *after* function docstring, found 1
2398: D205 Blank line missing between one-line summary and description
2420: D401 First line should be imperative: 'Return', not 'Returns'
2420: D209 Put multi-line docstring closing quotes on separate line
2420: D202 No blank lines allowed *after* function docstring, found 1
2420: D205 Blank line missing between one-line summary and description
2439: D401 First line should be imperative: 'Return', not 'Returns'
2439: D202 No blank lines allowed *after* function docstring, found 1
2439: D400 First line should end with '.', not 'd'
2454: D401 First line should be imperative: 'Return', not 'Returns'
2454: D202 No blank lines allowed *after* function docstring, found 1
2454: D400 First line should end with '.', not 'e'
2464: D401 First line should be imperative: 'Return', not 'Returns'
2464: D202 No blank lines allowed *after* function docstring, found 1
2464: D400 First line should end with '.', not 'e'
2494: D202 No blank lines allowed *after* function docstring, found 1
2502: D202 No blank lines allowed *after* function docstring, found 1
2510: D202 No blank lines allowed *after* function docstring, found 1
2510: D400 First line should end with '.', not 'x'
2518: D202 No blank lines allowed *after* function docstring, found 1
2518: D400 First line should end with '.', not 's'
2528: D401 First line should be imperative: 'Remove', not 'Removes'
2528: D209 Put multi-line docstring closing quotes on separate line
2528: D202 No blank lines allowed *after* function docstring, found 1
2528: D205 Blank line missing between one-line summary and description
2545: D209 Put multi-line docstring closing quotes on separate line
2545: D202 No blank lines allowed *after* function docstring, found 1
2545: D400 First line should end with '.', not 'd'
2545: D205 Blank line missing between one-line summary and description
2558: D401 First line should be imperative: 'Remove', not 'Removes'
2558: D209 Put multi-line docstring closing quotes on separate line
2558: D202 No blank lines allowed *after* function docstring, found 1
2558: D205 Blank line missing between one-line summary and description
2571: D401 First line should be imperative: 'Delete', not 'Deletes'
2571: D209 Put multi-line docstring closing quotes on separate line
2571: D202 No blank lines allowed *after* function docstring, found 1
2571: D400 First line should end with '.', not 'd'
2571: D205 Blank line missing between one-line summary and description
2642: D209 Put multi-line docstring closing quotes on separate line
2642: D208 Docstring is over-indented
2736: D401 First line should be imperative: 'Create', not 'Creates'
2736: D205 Blank line missing between one-line summary and description
2736: D208 Docstring is over-indented
2759: D401 First line should be imperative: 'Drop', not 'Drops'
2759: D205 Blank line missing between one-line summary and description
2759: D208 Docstring is over-indented
2770: D401 First line should be imperative: 'Add', not 'Adds'
2770: D205 Blank line missing between one-line summary and description
2770: D208 Docstring is over-indented
2786: D401 First line should be imperative: 'Add', not 'Adds'
2786: D400 First line should end with '.', not 'f'
2786: D205 Blank line missing between one-line summary and description
2786: D208 Docstring is over-indented
2803: D401 First line should be imperative: 'Add', not 'Adds'
2803: D400 First line should end with '.', not 'x'
2814: D209 Put multi-line docstring closing quotes on separate line
2814: D202 No blank lines allowed *after* function docstring, found 1
2814: D205 Blank line missing between one-line summary and description
2833: D400 First line should end with '.', not 'e'
2833: D205 Blank line missing between one-line summary and description
2833: D208 Docstring is over-indented
2869: D202 No blank lines allowed *after* function docstring, found 1
2869: D400 First line should end with '.', not 'x'
2884: D401 First line should be imperative: 'Update', not 'Updates'
2884: D400 First line should end with '.', not 'x'
2884: D205 Blank line missing between one-line summary and description
2884: D208 Docstring is over-indented
2903: D400 First line should end with '.', not 'e'
2922: D202 No blank lines allowed *after* function docstring, found 1
2922: D400 First line should end with '.', not 'e'
2933: D400 First line should end with '.', not 'e'
2942: D400 First line should end with '.', not 'e'
2942: D205 Blank line missing between one-line summary and description
2942: D208 Docstring is over-indented
2960: D202 No blank lines allowed *after* function docstring, found 1
2960: D400 First line should end with '.', not 'e'
2960: D205 Blank line missing between one-line summary and description
2960: D208 Docstring is over-indented
2974: D202 No blank lines allowed *after* function docstring, found 1
2974: D400 First line should end with '.', not 'e'
2985: D202 No blank lines allowed *after* function docstring, found 1
2985: D400 First line should end with '.', not 'e'
2996: D202 No blank lines allowed *after* function docstring, found 1
2996: D400 First line should end with '.', not 'x'
3007: D209 Put multi-line docstring closing quotes on separate line
3007: D202 No blank lines allowed *after* function docstring, found 1
3007: D400 First line should end with '.', not 'd'
3007: D205 Blank line missing between one-line summary and description
3021: D202 No blank lines allowed *after* function docstring, found 1
3021: D205 Blank line missing between one-line summary and description
3021: D208 Docstring is over-indented
3037: D209 Put multi-line docstring closing quotes on separate line
3037: D205 Blank line missing between one-line summary and description
3060: D103 Docstring missing
3076: D103 Docstring missing


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
30:1: I101 Imported names are in the wrong order. Should be DatabaseError, run_sql
32:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.legacy.dbquery
33:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.bibsched.bibtask
34:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_CHARS_ALPHANUMERIC_SEPARATORS, CFG_BIBINDEX_CHARS_PUNCTUATION
34:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
35:6: E126 continuation line over-indented for hanging indent
55: D200 One-line docstring should not occupy 3 lines
65:9: E128 continuation line under-indented for visual indent
68:1: E302 expected 2 blank lines, found 1
68: D401 First line should be imperative: 'Return', not 'Returns'
68: D209 Put multi-line docstring closing quotes on separate line
68: D205 Blank line missing between one-line summary and description
68: D208 Docstring is over-indented
84: D401 First line should be imperative: 'Return', not 'Returns'
84: D209 Put multi-line docstring closing quotes on separate line
84: D400 First line should end with '.', not 'e'
84: D205 Blank line missing between one-line summary and description
84: D208 Docstring is over-indented
99: D401 First line should be imperative: 'Return', not 'Returns'
99: D400 First line should end with '.', not 'e'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
107:5: B901 blind except: statement
114: D401 First line should be imperative: 'Get', not 'Gets'
114: D290 White spaces around docstring should be trimmed.
114: D209 Put multi-line docstring closing quotes on separate line
114: D400 First line should end with '.', not 'd'
114: D205 Blank line missing between one-line summary and description
114: D208 Docstring is over-indented
120:5: B901 blind except: statement
127: D401 First line should be imperative: 'Get', not 'Gets'
127: D290 White spaces around docstring should be trimmed.
127: D209 Put multi-line docstring closing quotes on separate line
127: D400 First line should end with '.', not 'd'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
133:5: B901 blind except: statement
140: D205 Blank line missing between one-line summary and description
170: D400 First line should end with '.', not 's'
170: D205 Blank line missing between one-line summary and description
170: D208 Docstring is over-indented
181:11: E271 multiple spaces after keyword
187:1: F401 'get_idx_indexer' imported but unused
190: D401 First line should be imperative: 'Return', not 'Returns'
190: D209 Put multi-line docstring closing quotes on separate line
190: D205 Blank line missing between one-line summary and description
190: D208 Docstring is over-indented
212: D401 First line should be imperative: 'Return', not 'Returns'
212: D290 White spaces around docstring should be trimmed.
221: D401 First line should be imperative: 'Return', not 'Returns'
221: D209 Put multi-line docstring closing quotes on separate line
221: D400 First line should end with '.', not 'h'
221: D205 Blank line missing between one-line summary and description
221: D208 Docstring is over-indented
232: D401 First line should be imperative: 'Check', not 'Checks'
232: D400 First line should end with '.', not 'l'
241:1: E302 expected 2 blank lines, found 1
241: D400 First line should end with '.', not 's'
241: D205 Blank line missing between one-line summary and description
241: D208 Docstring is over-indented
255:1: E302 expected 2 blank lines, found 1
255: D401 First line should be imperative: 'Return', not 'Returns'
255: D205 Blank line missing between one-line summary and description
255: D208 Docstring is over-indented
268: D401 First line should be imperative: 'Return', not 'Returns'
268: D209 Put multi-line docstring closing quotes on separate line
268: D205 Blank line missing between one-line summary and description
268: D208 Docstring is over-indented
281: D401 First line should be imperative: 'Return', not 'Returns'
281: D209 Put multi-line docstring closing quotes on separate line
281: D205 Blank line missing between one-line summary and description
281: D208 Docstring is over-indented
291: D401 First line should be imperative: 'Return', not 'Returns'
291: D400 First line should end with '.', not 's'
291: D205 Blank line missing between one-line summary and description
291: D208 Docstring is over-indented
299:5: F841 local variable 'out' is assigned to but never used
321: D401 First line should be imperative: 'Return', not 'Returns'
321: D209 Put multi-line docstring closing quotes on separate line
321: D400 First line should end with '.', not 'g'
321: D205 Blank line missing between one-line summary and description
321: D208 Docstring is over-indented
326:26: E261 at least two spaces before inline comment
326:27: E262 inline comment should start with '# '
327:26: E261 at least two spaces before inline comment
327:27: E262 inline comment should start with '# '
342:25: E261 at least two spaces before inline comment
342:26: E262 inline comment should start with '# '
362: D401 First line should be imperative: 'Return', not 'Returns'
362: D209 Put multi-line docstring closing quotes on separate line
362: D400 First line should end with '.', not 'g'
362: D205 Blank line missing between one-line summary and description
362: D208 Docstring is over-indented
399: D401 First line should be imperative: 'Return', not 'Returns'
399: D205 Blank line missing between one-line summary and description
399: D208 Docstring is over-indented
437: D401 First line should be imperative: 'Return', not 'Returns'
437: D400 First line should end with '.', not ':'
437: D205 Blank line missing between one-line summary and description
437: D208 Docstring is over-indented
442:10: E225 missing whitespace around operator
450: D401 First line should be imperative: 'Remove', not 'Removes'
450: D205 Blank line missing between one-line summary and description
450: D208 Docstring is over-indented
463: D208 Docstring is over-indented
463: D200 One-line docstring should not occupy 3 lines
477: D401 First line should be imperative: 'Create', not 'Creates'
477: D400 First line should end with '.', not 'd'
477: D205 Blank line missing between one-line summary and description
477: D208 Docstring is over-indented
487: D101 Docstring missing
491: D401 First line should be imperative: 'Return', not 'Returns'
491: D300 Expected """-quotes, got '-quotes
501: D401 First line should be imperative: 'Return', not 'Returns'
501: D400 First line should end with '.', not 'y'
501: D205 Blank line missing between one-line summary and description
501: D208 Docstring is over-indented
512:47: E202 whitespace before ')'
516: D401 First line should be imperative: 'Check', not 'Checks'
516: D400 First line should end with '.', not 't'
519:25: E272 multiple spaces before keyword
526: D401 First line should be imperative: 'Check', not 'Checks'
526: D209 Put multi-line docstring closing quotes on separate line
526: D400 First line should end with '.', not ';'
526: D205 Blank line missing between one-line summary and description
526: D208 Docstring is over-indented
532: D401 First line should be imperative: 'Return', not 'Returns'
532: D209 Put multi-line docstring closing quotes on separate line
532: D400 First line should end with '.', not ';'
532: D205 Blank line missing between one-line summary and description
532: D208 Docstring is over-indented
541: D401 First line should be imperative: 'Find', not 'Finds'
541: D400 First line should end with '.', not 'n'
541: D205 Blank line missing between one-line summary and description
541: D208 Docstring is over-indented


23:1: I100 Imports statements are in the wrong order. import ConfigParser should be before import os
26:6: E126 continuation line over-indented for hanging indent
28:1: I100 Imports statements are in the wrong order. from invenio.base.helpers should be before from invenio.config
30:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before import invenio.modules.access.engine
35: D103 Docstring missing
42: D103 Docstring missing
49: D290 White spaces around docstring should be trimmed.
54: D202 No blank lines allowed *after* function docstring, found 1
83: D202 No blank lines allowed *after* function docstring, found 1
83: D400 First line should end with '.', not 'o'
100:15: E221 multiple spaces before operator
120:17: E221 multiple spaces before operator
158:17: E221 multiple spaces before operator
187: D202 No blank lines allowed *after* function docstring, found 1
187: D400 First line should end with '.', not 'd'
215:13: E221 multiple spaces before operator
244:41: F841 local variable 'e' is assigned to but never used
269: D202 No blank lines allowed *after* function docstring, found 1
269: D400 First line should end with '.', not ':'
273:11: E221 multiple spaces before operator
343:41: F841 local variable 'e' is assigned to but never used
357: D202 No blank lines allowed *after* function docstring, found 1
357: D400 First line should end with '.', not 'd'
374:11: E221 multiple spaces before operator
477:29: F841 local variable 'e' is assigned to but never used
485: D400 First line should end with '.', not 'd'
485: D200 One-line docstring should not occupy 2 lines
489:11: E221 multiple spaces before operator
529:115: E221 multiple spaces before operator
536:37: F841 local variable 'e' is assigned to but never used
545: D401 First line should be imperative: 'Return', not 'Returns'
545: D202 No blank lines allowed *after* function docstring, found 1
545: D400 First line should end with '.', not 'D'
555:9: E221 multiple spaces before operator
605:9: F821 undefined name 'CFG_ETCDIR'
613:29: F841 local variable 'e' is assigned to but never used
620: D103 Docstring missing
624: D401 First line should be imperative: 'Return', not 'Returns'
624: D209 Put multi-line docstring closing quotes on separate line
624: D202 No blank lines allowed *after* function docstring, found 1
624: D400 First line should end with '.', not 't'
624: D205 Blank line missing between one-line summary and description
631:29: F841 local variable 'e' is assigned to but never used
635: D209 Put multi-line docstring closing quotes on separate line
635: D202 No blank lines allowed *after* function docstring, found 1
635: D400 First line should end with '.', not 's'
635: D205 Blank line missing between one-line summary and description
647:29: F841 local variable 'e' is assigned to but never used
651: D401 First line should be imperative: 'Return', not 'Returns'
651: D209 Put multi-line docstring closing quotes on separate line
651: D202 No blank lines allowed *after* function docstring, found 1
651: D400 First line should end with '.', not 'd'
651: D205 Blank line missing between one-line summary and description
659:29: F841 local variable 'e' is assigned to but never used
663: D202 No blank lines allowed *after* function docstring, found 1
663: D400 First line should end with '.', not 's'
672: D202 No blank lines allowed *after* function docstring, found 1
672: D400 First line should end with '.', not 's'
680: D401 First line should be imperative: 'Return', not 'Returns'
680: D290 White spaces around docstring should be trimmed.
680: D209 Put multi-line docstring closing quotes on separate line
680: D202 No blank lines allowed *after* function docstring, found 1
680: D400 First line should end with '.', not 'o'
680: D205 Blank line missing between one-line summary and description
690:29: F841 local variable 'e' is assigned to but never used
694: D290 White spaces around docstring should be trimmed.
694: D202 No blank lines allowed *after* function docstring, found 1
694: D400 First line should end with '.', not "'"
705: D209 Put multi-line docstring closing quotes on separate line
705: D202 No blank lines allowed *after* function docstring, found 1
705: D400 First line should end with '.', not 'n'
705: D205 Blank line missing between one-line summary and description
711:9: F841 local variable 'res' is assigned to but never used
718: D209 Put multi-line docstring closing quotes on separate line
718: D202 No blank lines allowed *after* function docstring, found 1
718: D400 First line should end with '.', not 'n'
718: D205 Blank line missing between one-line summary and description
724:9: F841 local variable 'res' is assigned to but never used
731: D401 First line should be imperative: 'Delete', not 'Deletes'
731: D209 Put multi-line docstring closing quotes on separate line
731: D202 No blank lines allowed *after* function docstring, found 1
731: D400 First line should end with '.', not 'd'
731: D205 Blank line missing between one-line summary and description
745:13: F841 local variable 'res' is assigned to but never used
751: D209 Put multi-line docstring closing quotes on separate line
751: D202 No blank lines allowed *after* function docstring, found 1
751: D400 First line should end with '.', not 'n'
751: D205 Blank line missing between one-line summary and description
757:9: F841 local variable 'res' is assigned to but never used
764: D401 First line should be imperative: 'Add', not 'Adds'
764: D209 Put multi-line docstring closing quotes on separate line
764: D202 No blank lines allowed *after* function docstring, found 1
764: D400 First line should end with '.', not 'D'
764: D205 Blank line missing between one-line summary and description
779: D209 Put multi-line docstring closing quotes on separate line
779: D202 No blank lines allowed *after* function docstring, found 1
779: D208 Docstring is over-indented
828: D202 No blank lines allowed *after* function docstring, found 1
828: D207 Docstring is under-indented
911: D209 Put multi-line docstring closing quotes on separate line
911: D202 No blank lines allowed *after* function docstring, found 1
911: D208 Docstring is over-indented
938: D401 First line should be imperative: 'add', not 'adds'
938: D209 Put multi-line docstring closing quotes on separate line
938: D202 No blank lines allowed *after* function docstring, found 1
938: D208 Docstring is over-indented
963: D209 Put multi-line docstring closing quotes on separate line
963: D202 No blank lines allowed *after* function docstring, found 1
963: D400 First line should end with '.', not 'n'
963: D208 Docstring is over-indented
999: D103 Docstring missing
1007: D401 First line should be imperative: 'Return', not 'Returns'
1007: D209 Put multi-line docstring closing quotes on separate line
1007: D202 No blank lines allowed *after* function docstring, found 1
1007: D400 First line should end with '.', not 'e'
1007: D205 Blank line missing between one-line summary and description
1014:9: F841 local variable 'name' is assigned to but never used
1024:29: F841 local variable 'e' is assigned to but never used
1028: D401 First line should be imperative: 'Return', not 'Returns'
1028: D209 Put multi-line docstring closing quotes on separate line
1028: D202 No blank lines allowed *after* function docstring, found 1
1028: D400 First line should end with '.', not 'e'
1028: D205 Blank line missing between one-line summary and description
1064:29: F841 local variable 'e' is assigned to but never used
1068: D401 First line should be imperative: 'Return', not 'Returns'
1068: D202 No blank lines allowed *after* function docstring, found 1
1068: D400 First line should end with '.', not 's'
1068: D205 Blank line missing between one-line summary and description
1088:29: F841 local variable 'e' is assigned to but never used
1092: D202 No blank lines allowed *after* function docstring, found 1
1092: D400 First line should end with '.', not 'e'
1092: D205 Blank line missing between one-line summary and description
1129: D202 No blank lines allowed *after* function docstring, found 1


Could not evaluate contents of __all__. That means pep257 cannot decide which definitions are public. Variable __all__ should be present at most once in each file, in form `__all__ = ('a_public_function', 'APublicClass', ...)`. More info on __all__: http://stackoverflow.com/q/44834/.


Oh my mistake - I thought this was `getCallerFrame`, which we used to implement ourselves but is now in the Truffle API. Anyway, this appeared to be dead code. Were you using it for something?


9: M102 unrecognized bullet/signature


@AriDEV: you can get it from areatable.dbc and highest value is 191 there


Yes, I agree - it doesn't cover the cases as is.


1277852-CommandLineInterface (nealkruis) - Win64-Windows-7-VisualStudio-12: OK (1586 of 1592 tests passed)

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


Looks good to me, analytics still flowing through Google's machinery.


Once I'm done with this PR, feel free to change the values as you will


웟더


No, I was just wondering :)


TeamCity xBIM :: Xbim Geometry :: Release [Build 22](http://ncl-xbim:8080/viewLog.html?buildId=763&buildTypeId=XBIM_XbimGeometry_Release) is now running


Tell me more about case sensitive issues. I would prefer to leave case as user put it, unless there is a good reason to not.


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1975](http://teamcity.monogame.net/viewLog.html?buildId=5093&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 366, ignored: 6 Build time: 00:16:10


1: M111 unrecognized component name: authorids


Typo?


I don't know. This stuff comes from https://github.com/onomojo/i18n-country-translations/tree/master/rails/locale/iso_639-1, so I didn't write it.


As described in work-ticket CP-10954 and its parent, rather than accepting only "1", this should be more permissive, accepting anything except the empty string or zero. This leaves scope for future changes to the guest agent to convey additional information by using some other string, without having to update this code.

For example,
```
let v = List.assoc "feature-ts2" other in
    (v <> "") && (v <> "0")
```
or
```
match List.assoc "feature-ts2" other with
    | ""
    | "0" -> false
    | _ -> true
```
or even
```
match List.assoc "feature-ts2" other with
    | "" -> false
    | v -> try
        (int_of_string v) <> 0
    with Failure _ -> true
```
which I think matches the pull-request in XenCenter.


Ok


Don't know why I did that in the first place.


sure?


CSS is case-insensitive. Now what happens the author names a layer Rect and another rect? They are different for case sensitive and the same for insensitive. It gets more interesting with UTF8 names. This always caused confusions for authors and we got complains about that  in the CSS WG.


Neat!
We can already interrupt some IO :)
(but yeah Java limitations on read from stdin etc apply)


Phil, you probably want to update your README, the very first section that shows Maven dependency and change it to 4.0-SNAPSHOT because ahuge chunk of documentation does not apply to 3.6 and there is no warning for that.
Cheers.


This is confusing. Maybe extract method with then name `extract_country` or something.


There are examples with "Rectangle 1" in the changed test files. They are probably not set in the PS file, are they? Because at least for the examples and rect it doesn't seem to work and we still get an id.


How could we make it work with multiple processes? (I wish to use it to see what mspec is doing and typically it's using ruby_exe)


Fair enough, what to do with names like “🎈”?


Ah indeed an attempt to export it to SVG with the ending "*.svg".


Approximation errors might occur by converting pixel to coordinate then coordinate to pixel.
What about passing the pixel to `ol.renderer.webgl.ImageLayer.prototype.forEachLayerAtPixel`?


Personally - my workflow is that when I start a new project, I composer create-project nette/sandbox, I remove all the presenters, templates, styles, javascript (jquery, netteForms) and start using 3rd party solutions - webloader, jquery from composer repository, nette.ajax.js, live-validation-form, etc. etc. For me the skeleton would be great. Just the minimal running sandbox which ends up with
It works!
 template. The problem can be just that the skeleton wouldnt have the javascript forms validations, which is not a problem IMHO, because skeleton would be run by more experienced users. Or am I missing something?


I wonder why his layer's name is Rectangle.


> So commonmark.js is faster and markdown-it significantly slower under 0.11. Have you noticed this?

I know about markdown-it slowdown (~25% in our benchmark) in 0.11. Didn't digged yet, because there is possibility that 0.11 will bump again v8 version.

Anyway, madkdown-it can become slower after [next refactoring](https://github.com/markdown-it/markdown-it/issues/37) with renderer rewrite.


почему приложил лицензию 2-ой версии, когда в виджете указана 3-я? lol


I face with this error
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .btn-xs' has no matches
extend ' .btn-sm' has no matches
extend ' .btn-lg' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .img-responsive' has no matches
extend ' .clearfix' has no matches
extend ' .clearfix' has no matches
extend ' .img-responsive' has no matches
The compress option has been deprecated. We recommend you use a dedicated css minifier, for instance see less-plugin-clean-css.


But I, for one, always put ids to the layers, when exporting from Ai. Would be sad to lose this feature.


1: M111 unrecognized component name: authorids


So if a user opens a PSD file with the file endings added (maybe because this was the way to extract things in the past) then we will always add an id? Should we get smarter here? Maybe default name + ending `.svg`, `.jpg` and `.png`?


The method is called `forEachLayerAtPixel` but takes a coordinate. In this case, it should be renamed to `forEachLayerAtCoordinate`. There are several such cases. See related comment https://github.com/tsauerwein/ol3/commit/69e4a6ac2df69a29800b875214703ed248257d77#commitcomment-9456418


TeamCity xBIM :: Xbim Geometry :: Release [Build 22](http://ncl-xbim:8080/viewLog.html?buildId=763&buildTypeId=XBIM_XbimGeometry_Release) outcome was **FAILURE**
Summary: Tests failed: 4 (4 new), passed: 64 Build time: 00:14:25
### Failed tests
```
MSTest: GeometryTests.IfcExtrudedAreaSolidTests.IfcExtrudedArea_With_IfcArbritraryClosedProfileDef_And_IfcCompositeCurve: <no details avaliable>

MSTest: GeometryTests.IfcSweptSolidTests.IfcSurfaceCurveSweptAreaSolid: <no details avaliable>

MSTest: GeometryTests.WholeModelTests.TestAllModels: <no details avaliable>

MSTest: GeometryTests.WholeModelTests.TestCuttingOpenings: <no details avaliable>

```


README updated to clarify this


fix  #2890 #2775


Yeah - haven't thought about that much yet. It does work with mspec though - I'm not sure sure how to pass the parameters in but you can modify `Options` to set a port directly - and it gives useful output. Best to use with `fast` to avoid further sub-processes.


Incredible how one single line can add so much value.


Well this is good example when default layer names sneaked in. My question is: why they are paths? Somehow they are not rectangles, therefore I don’t recognise them as ones.


It should be `github.com/jubatus/....` because user always doesn't copy common to local. `go get` command, that can clone repository to local $GOPATH directory.


I think this is a bug that it does not set the value by given argument.

BTW, I think the configured matcher should be set at UrlHelper#createDefaultRule.


Great post! I hadn't seen that [GAO report](http://www.gao.gov/products/GAO-14-476) before. Fascinating.
"GAO estimates with 95 percent confidence that between 2 percent and 7 percent of the awards contained information that was fully consistent with agencies' records for all 21 data elements examined." Ouch.

In that report, there's a [great footnote](http://www.gao.gov/assets/670/664536.pdf#page=15) that actually speaks to your point pretty well:

> "There is no authoritative source which identifies all of the contracts issued by each agency. As such, we could not verify whether all contracts were displayed on the website and only determined whether at least one contract was displayed for each agency."

If _GAO_ can't figure out whether all the contracts are reported in 2014 (!), standardization and reporting of procurement data in a structured may be the best way forward to ensure accountability _and_ promote efficiency.

I'm also intrigued by your point about federal financial assistance transparency. Why do you think this statement--"unlike a contract, it is nearly impossible to track down grant recipients with accuracy"--is so? Is it a political issue? A methodological issue? What can be done to improve the situation? (Or is it your argument that the DATA Act will do so?)


I don’t know. It’s a group. Group’s default name is “Group 1”.


Thanks for telling me :).


I found them ↓. They are not rectangles.


Commit message plz !


@ipolevoy, yes this is backwards compatible. [Generics](http://docs.oracle.com/javase/tutorial/extra/generics/wildcards.html) were introduced in Java 5 and this is the preferred way of declaring a generic type that accepts any argument. While declaring it without the `<?>` would treat it as a [raw type](http://docs.oracle.com/javase/tutorial/java/generics/rawTypes.html).


Assignment in condition - you probably meant to use `==`.


`end` at 6, 11 is not aligned with `variable = lambda do |i|` at 4, 0


`end` at 2, 16 is not aligned with `if` at 1, 11


Literal `true` appeared in a condition.
Useless assignment to variable - `variable`.
Trailing whitespace detected.


Useless assignment to variable - `variable`.


Use 2 (not -9) spaces for indentation.


`END` found in method definition. Use `at_exit` instead.<br>Avoid the use of `END` blocks. Use `Kernel#at_exit` instead.


The use of `eval` is a serious security risk.


Literal `true` appeared in a condition.<br>Don't use parentheses around the condition of an `if`.


Use `Kernel#loop` with `break` rather than `begin/end/until`(or `while`).


Avoid rescuing the `Exception` class.


Shadowing outer local variable - `x`.


Useless assignment to variable - `x`.


Unreachable code detected.


Useless assignment to variable - `b`.


Operator `*` used in void context.


Literal `'aaaa'` used in void context.


Variable `SOME_VAR` used in void context.


Yeah they are rectangles where we couldn't get the geometry right... because of transforms or unsupported corner radii. In this case we transform them to <path>


I mean, not `Cyclist` class itself, but a `FileCyclist` vs `LineCyclist` inheritance. I could pinpoint a few flaws (IMHO, of course) in current architecture:

* `Cyclist` class (as a main working class that does all the stuff) and `FileCyclist` + `LineCyclist` have almost nothing in common. You're right - it's exactly as you say - `FileCyclist` + `LineCyclist` do the job of providing the enumerator, while `Cyclist` in fact uses it. It's clearly not inheritance, it's two distinct use cases - if you'd want them to be classes, they'd rather should be named something like `Cyclist` vs `FileEnumeratorProvider` + `LineEnumeratorProvider`.

* There's really no point in having these one-liners as separate classes (besides, the practice of doing lots of artificial classes like `SomethingDoer`, which is usually the only way in languages like Java, is generally frowned upon in Ruby). In our case, it only increases confusion and does not really bring any realistic benefits. IMHO, it's more than ok to replace

```ruby
  def parse(content, opts = {}, &block)
    TSV::StringCyclist.new(content, opts, &block)
  end

  def parse_file(filename, opts = {}, &block)
    TSV::FileCyclist.new(filename, opts, &block)
  end
```
  with something like that:
```ruby
  def parse(content, opts = {}, &block)
    TSV::Cyclist.new(content, opts, &block)
  end

  def parse_file(filename, opts = {}, &block)
    TSV::Cyclist.new(File.new(content), opts, &block)
  end
```

* `Cyclist` name isn't a really good choice of name; it strongly associates with biking culture (while TSV has generally nothing to do with bikers), and, even if we neglect that, "cyclist" would be rather associated with rocket science-level stuff (thinking "cycles" in algebraic topology, graph theory, number theory, etc). In fact, it's basically a read-only per-row-access-providing container for the TSV file. Why not call it something like `TSV::File`, `TSV::Rows`, or something like that?

* Using very abstract `source` everywhere does not really achieve anything. `Cyclist` now struggles a lot to store it, to propagate it to `FileCyclist` + `LineCyclist`, to maintain it in case of re-building the class with `self.class.new`, but it's not really needed there. It's only used in `FileCyclist` + `LineCyclist`.

* `with_header` and `without_header` don't really cope well with other invocation mechanisms (like `opts` and a given block in `TSV::parse`) and I'm not sure if they're really necessary given that one can always specify `header: true` or `header: false` directly in options.

I can do these simplifications and propose a pull request, if you want :)


why this? even in standalone mode, it should be able to activate TLS if certificates are found


Change to `Standalone mode (skips node registration with Tutum)`


Wow, cool, thanks :) This is exactly what I had in mind...
I would change some things a bit, like renaming the fluid_pressure function to fluid_pressure_gradient, and then it would probably be reasonable to really calculate the gradient (rho * gravity instead of just rho), so that also also an inflow from the side boundaries can be prescribed, but that is something I can do and this is the perfect starting point for me!
Thanks again!


Exactly. That is what I mean with UTF8 names... We had endless discussions about that.


@Subjunk stupid question, how can i test that exactly? I just want to know what to look for in a successful test of that version. Anything in the debug logs to look out for?


Removed test file


Could you please avoid code duplication here?

```
File ["/etc/nagios/nrpe.d/${command_name}.cfg"] ~> Service[$icinga2::params::nrpe_daemon_name]
```

I would prefer that in an if block :)


Anyway, this is fine for the 1.5.1 release. We're freezing commits for now, right? Otherwise we'll never release 1.5.0...  :- )


I think I know why, I built a user rom instead of userdebug..


You should remove this file.


You don't need this


where do you use this?


PHP Type Hinting 好像還不支援原生型態 http://php.net/manual/en/language.oop5.typehinting.php


Look at what the checkpoints says:

```
Routing

Nest the comments resource under resources :posts in routes.rb. You only have one comment action for now -- create -- so only create the routes that you need;

Note that nesting comments inside of posts means they'll be nested inside topics as well. As the create url -- /topics/:topic_id/posts/:post_id/comments -- suggests, this "deep nesting" can get complicated, and we'll refactor it shortly.
```


哈哈，雖然寫法沒錯，不過以後遵循 PSR 之後反而是用 space 取代 tab，模組倒還不必遵從。


You may want to use 'rm -f' as this doesn't complain about file existance


`cacert` file is sent by tutum-api.
If tutum-agent doesn't register to tutum before running in standalone mode, there is no cacert file on the node. As a result, docker will fail to start.


thanks to @olivierlesnicki for much help on this one.


> 呀忘了把
> if (adminAuthenticate('check') === true ) return; //no captcha for admin mode
> 也加上去orz

先等你加上去 :smile:


Well, the problem was that Mode and SecondMode were initialized in two different PaperScreen, and since init order of those varied, we could not rely on specific default ID. Then maybe it's a papart bug/feature ;)

As for the relevant theoretical question, while you decide you could remove SecondMode.create(). Because ID is even more complex than that, what happen when calles to SecondMode() and SecondMode(name, id) are mixed? Or the same with Mode(), for that matter.


As described in work-ticket CP-10954 and its parent, rather than accepting only "1", this should be more permissive, accepting anything except the empty string or zero. This leaves scope for future changes to the guest agent to convey additional information by using some other string, without having to update this code.

For example,
```
let v = List.assoc "feature-ts2" other in
    (v <> "") && (v <> "0")
```
or
```
match List.assoc "feature-ts2" other with
    | ""
    | "0" -> false
    | _ -> true
```
or even
```
match List.assoc "feature-ts2" other with
    | "" -> false
    | v -> (try
        (int_of_string v) <> 0
      with Failure _ -> true)
```
which I think matches the pull-request in XenCenter.


In standalone mode


Please fix the "sanitze$" typo


Syntax is not correct here.


@ckprice I already filed a bug.
https://bugzilla.mozilla.org/show_bug.cgi?id=1125623
Check it.


Use localStorage instead. Cookies is extra overhead, because they are carried over on each HTTP request.


develop (rraustad) - i386-Windows-7-VisualStudio-12: OK (1098 of 1098 tests passed)

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


What happens in the case where an updated package introduces new dependencies?


`querydb.first.typ` - Typo?


This page also needs a redesign.


A quick test can't reproduce the issue. When I run the tumblr/collins from
the hub, it fails. When I rebuild it using the GIT, it works.
I used another docker server at the office (Centos 7), and wasn't able to
start the container either.
This issue is weird..

On Tue, Jan 27, 2015 at 7:44 AM, Wim Fournier <hsmade@gmail.com> wrote:

> That makes sense. The multiple variables in one line is only supported
> when using '='
>
> I get this on 1.4.1:
> csnlwfournier:~ wfournier$ docker run -p 9000:9000 tumblr/collins
> Error: Could not find or load main class play.core.server.NettyServer
> To enable GC log rotation, use -Xloggc:<filename>
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=<num_of_files>
> -XX:GCLogFileSize=<num_of_size>
> where num_of_file > 0 and num_of_size > 0
> GC log rotation is turned off
> csnlwfournier:~ wfournier$ docker -v
> Docker version 1.4.1, build 5bc2ff8
>
> When I change the dockerfile to have the 2 vars on separate lines, it
> works, just like with 1.3.
> I did get the same on 1.3.1. The var=value is only supported in 1.4 btw.
> Anyway, this looks like a bug in docker. Does the image work for you?
>
> If I find the time, I'll do a quick test with a simple docker file to see
> if it's a bug in docker, and report it if it is.
>
> Wim
>
> On Mon, Jan 26, 2015 at 10:49 PM, Gabe Conradi <notifications@github.com>
> wrote:
>
>> @hsmade <https://github.com/hsmade> checking the build logs, it appears
>> the hub is running the build with 1.3.3. The current docs state that both
>> with and without '=' are acceptable syntax. When i try a build with
>>
>> ENV APP_HOME /opt/collins \
>>     LOG_HOME /var/log/collins
>>
>> It sets the APP_HOME var to '/opt/collins LOG_HOME /var/log/collins'.
>>
>> Let us know how it goes!
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/tumblr/collins/commit/f0b8be6e58974dda66d61306b6ef7a274c736757#commitcomment-9448686>
>> .
>>
>
>


Taking a look at the dumps I noticed the patch that reimplemented the indirect descriptors logic introduced some trace aborts due to "NYI: bytecode 51". I was working on a patch to eliminate these NYI. I still didn't run your patch and looked if all NYI are gone in virtq.lua, but I believe yes. I will check it anyway.


I have added ```pmap_extract``` in b2c3402a0db08b4c8a00b0fd5eb1c63af93382f9


Actually, I don’t see this as a case here, but I get your point. May be we could check for id before we do transformation?


Can't you just have a reader read everything from the InputStream and a writer write it to the OutputStream?


Also noticed you are missing https://github.com/bakape/meguca/blob/master/client/options.js#L713-L730 for toggling the options, volume, schedule, etc. menus.


OK so can we make it so, in standalone mode:
* If `cacert` exists, it uses TLS with client authentication
* If it doesn't, it still uses TLS but without client authentication (removing `--tlscacert` and replacing `--tlsverify` with `--tls`) and generates a `WARNING: standalone mode activated but no CA certificate found - client authentication disabled` to `stderr`?


Probably.


log filen ame, line number and method name


OTRS scheduler operation script for systemd without relationship any database.
1) Place to '/usr/lib/systemd/system/'.
2) Exec 'systemctl daemon-reload' to recognize OTRS to systemd.
3) You can operate OTRS scheduler with 'systemctl {start|stop|restart|status} otrs[.service]'.


Should be "This email address is already registered in our newsletter."


It's not totally clear what these files are - but I'm not that worried, as it'll soon be encoded in the language and example recipes.


maximum-scale=1.0, är det verkligen så bra? Att kunna zooma brukar vara bra för folk med dålig syn!


Like!


Really good points about the cost-benefit analysis of opening government data sets. As I read the post, I started to wonder: who should be in a position to make these decisions?

In that vein, one topic we'll be discussing in session 3 is open-data policies. Based on your post, I wonder whether--as an institutional matter--you'd argue that legislatures should be more active in deciding which datasets should be opened. On one hand, there's the democratic benefit of allowing a deliberative body explicitly balancing the competing public interests. On the other hand, there's the realpolitik that legislatures are slow to act, at least compared to the relative ability of agencies to decide to open up specific datasets.

In Wednesday's class, during the presentation about the technological side of open government data, consider whether the technologies that are currently available (screen scraping in particular) affects the calculus about whether and how to publish data.


The try statement works fine. Apparently he has a issue with Mac failing with this and files overwriting? However, I fail to see how this is useful.


This is easy, but what if default names were transformed by some other scripts in some other way?

May be create special format, for example, if you want you layer name to end up in SVG prefix it with “svg:” for example? I don’t like it very much, due to discoverability issue, but…


@dfeyer Thanks a lot for this addition! ;)
Just a minor typo - I don't know how to alter existing PR that are not mine..


We still need to copy files around, to keep a repo format going.


why are you specifying the keywords if you're testing tags?


That's the point of the second statement. it makes sure the files are at the same path


「取り消しました」メッセージが出てから急に画面が切り替わるのが気になります。
OKボタンを押したら画面が切り替わるほうがよいと思います。


Ah, sorry, I didn't read that correctly.
This is still a bit of a hacky thing though - we should verify if the destination exists.


Maybe you checkout how extraction with Generator works for layers. There are a bunch of options that you can add as well like size and scale and so on. I hope they don't make ids invalid somehow.

http://helpx.adobe.com/photoshop/using/generate-assets-layers.html


I think we should download incase the JSON changed on the remote end


Object.prototype.hasOwnProperty.call(obj, key) 너무 길어...

hasOwnProperty.call(obj, key)  나혼자 쓸라하면 그냥...

OP.call(obj, key) 이런 식...


well, could we do a File.delete in any case then? that solves all issues.


Unless you're deleting the source file?


Why didn't you add Thumbs.db to a .gitignore, so these don't get regenerated?


^ Never mind, saw a more recent commit.


-o


Пиши не http://, а //reslib.org итп. Везде так нужно когда обращаешься на сторонние ресурсы, это нужно для поддержки правильной загрузки ресурсов если где нибудь окажется включен https.


Um? Why would we delete the source file? We can't in most cases.


Обычно принято сохранять селекторы начиная с $headerDom итп. Но в целом и так нормально.


Nice. These patches really boost performance. I benchmark each patch individually and compared with current straigthline branch. These is what I got:

**Settings** (Grindelwald)
```
NFV_PCI0="0000:05:00.0"
PCAP=/opt/bench/256xff.pcap
```

**Straightline**

```
Rate(Mpps): 4.453
Rate(Mpps): 4.424
Rate(Mpps): 4.457
Rate(Mpps): 4.395
Rate(Mpps): 4.439
```

**All changes**

```
Rate(Mpps): 4.857
Rate(Mpps): 4.849
Rate(Mpps): 4.916
Rate(Mpps): 4.816
Rate(Mpps): 4.846
```

**net_device:map_from_guest: remove cache**

```
Rate(Mpps): 4.449
Rate(Mpps): 4.417
Rate(Mpps): 4.53
Rate(Mpps): 4.53
Rate(Mpps): 4.411
```

**virtq: Optimize LuaJIT behavior [DRAFT]**

```
Rate(Mpps): 4.739
Rate(Mpps): 4.644
Rate(Mpps): 4.39
Rate(Mpps): 4.497
Rate(Mpps): 4.912
```

**Disable with_restart() [TEMPORARY]**

```
Rate(Mpps): 4.683
Rate(Mpps): 4.681
Rate(Mpps): 4.664
Rate(Mpps): 4.7
Rate(Mpps): 4.714
```

**Reduce packets-per-pull, perform voodoo**

```
Rate(Mpps): 3.206
Rate(Mpps): 3.245
Rate(Mpps): 3.215
Rate(Mpps): 3.245
Rate(Mpps): 3.255
```

The performance for reduce-packets-per-pull is worse than current straightline. I turned the number of packets pulled to 128 and run the benchmark again:

```
Rate(Mpps): 5.941
Rate(Mpps): 6.004
Rate(Mpps): 5.931
Rate(Mpps): 5.963
Rate(Mpps): 5.938
```

The performance gain due to calling ```os.getenv()``` seem to be necessary. I removed it, while keep n=128, and I got the following results:

```
Rate(Mpps): 5.219
Rate(Mpps): 4.714
Rate(Mpps): 5.16
Rate(Mpps): 5.216
Rate(Mpps): 5.17
```

I want to take a look at the ```os.getenv()``` call and check there are not more NYI in virtq.lua due to the indirect descriptors.


The pretty solution is to create SVG editor as powerful as Ai, but SVG oriented. Or add SVG options into UI and annoy people who don’t care about SVG, may be separate panel :( or export options :(. Frankly, I don’t see pretty solution.


You have now updated #2029 ;)


Снова селекторы по idшникам...


Никогда, никогда"! не вхерачивай HTML в js! это потом невозможно поддерживать.


it's right :) - finded as ItemBonusDebug


Андрей, проблема в том, что код сильно дублируется. Можно сделать метод `dragBubble(MAX, event)`


Ah! You're absolutely right.
Should've thought of that before.


If we delete the current file, but the current file is also the output file, then we've deleted the file that we need to copy, which is the same problem I was trying to solve.


Helt ärligt tror jag att jag bara saxade det där från internet någonstans. Jag plockar bort just den biten. `initial-scale=1.0` och `width=device-width` antar jag att du inte har något emot?


Снова селекторы.. Да и вообще с temlatами нужно что то делать, к примеру перевести на плагин text для require.


why not use gevent?


Тянуть вместе 2 элемента мы не можем. Лучше добавить 2 константы: MAX_BUBBLE, MIN_BUBBLE

И сделать переменную `currentDragBubble = MAX_BUBBLE | MIN_BUBBLE | false`


:+1: to @ksoll's observation that open government data policies both reflect the state of nations' development and have the potential to improve them. I am especially taken by the argument that harmonization of core open-government-data principles can be a driver for developing countries in particular. In that regard, what can be done to help advance the goal of harmonization? Is it time? Is it iteration and experimentation? Is it simply a matter of leadership and consensus-building?


Extra line?


The idea was, that we use every color only one time. But maybe you are right and this is more harm than help.

@Zauberstuhl What do you think?


It's part of my DAGOLDEN bundle.
https://metacpan.org/pod/Dist::Zilla::Plugin::BumpVersionAfterRelease

On Tue, Jan 27, 2015 at 4:01 AM, Michael Gray <notifications@github.com>
wrote:

> Quick question - do you do this by hand or do you have a script to do the
> version bumping?
>
> Thanks
> Michael
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dagolden/Sub-Uplevel/commit/d2bbae35547b8db394dd29b0d7d30e47778c9f08#commitcomment-9455022>
> .
>

--
David Golden <dagolden@cpan.org> Twitter/IRC: @xdg


Еще было бы хорошо все структурировать:
- инициализация переменных
- подписка на события
- методы


We have to write 2 types of HTML anyway if we want to make the navbar responsive right? That is of course if Bootstrap is included. But if it's not, we don't need a responsive nav and using the same code wouldn't make sense? Just a thought, maybe I'm wrong :)


This still depends on protobuf for the ola/host compilation. Are there any docs on how dependencies are handled within the build system?


Hey!

This version keeps my original approach. I ended up adding lots of refinements and config options to care for multiple scenarios and when I got it ready there were already plenty of changes (and time). It simplified things (at least on my head) to deal with conflicts at the end of the process independently.

Anyhow, if you see anything worth changing any enhancements are welcome! :D


Unfortunately the scope is not updated and it always uses the latter condition.


Please take a moment to test this source code. You will find a bug.
As an exercise I will not point the bug out for you but will rather leave the task of finding the bug to you.
It would be a great step forward if you started testing all your source code before commiting :smile_cat:


Initialisation du dépot


This extra line still needs removal.


This change shouldn't be here.


Okay, so it should be encoded to utf-8 before it's returned.

I wanted to suggest adding `from __future__ import unicode_literals` to every file, in order to be completely done with unicode issues.  I'm browsing a lot of profiles that are not in English, so I've gotten a lot of unicode errors, and while I think I fixed most or all of them in this pull request, unicode literals would be a better solution.  Is there anywhere in the code that you can think of that might have a problem with unicode literals?  I'd be happy to send the pull request if that sounds okay to you.


I would cache the return value of `o1.isOnline()` and `o2.isOnline()`.
Maybe rename `o1` --> `p1` and `o2` --> `p2`. Then do `boolean o1 = p1.isOnline` etc.
The new cached values could be used in the if statements.
By doing this we will reduce calculation strain by 0%, 25% or 50%.


Hello,
thank you for your feedback of you all.
We corrected the code you pointed in the last comments. We hope this patch will feet your needs, it contains also the part you already integrated.
Regards


Asymmetry Nr1: Is this comparator supposed to return 0 or not?


/ping @evert and @armin-hackmann on this one.
I am confused.

The `URI` property type described in http://tools.ietf.org/html/rfc6350#section-4.2 (vCard) does not explicitely speak about the comma. Also, the grammar of the `URI` property type is not given.

But, the `GEO` property is of kind `URI`, and has the following syntax: `GEO:geo:1.2345,6.789` according to http://tools.ietf.org/html/rfc6350#section-6.5.2. However, I thought it was incorrect and it failed my tests. So, I checked errata and found this: http://www.rfc-editor.org/errata_search.php?rfc=6350&eid=3846. I am quoting it here for the record:

> Section 6.5.2 says:
>
>            GEO:geo:37.386013,-122.082932
>
> It should say:
>
>            GEO:geo:37.386013\,-122.082932
>
> Notes:
>
> Section 3.4 states that all property values must have COMMA characters escaped with a BACKSLASH character. The GEO property value in the example contains a comma. Therefore it must be escaped with a backslash.

So, this patch fixes the `URI` property by escaping the comma. But there is this whole paragraph that @armin-hackmann pointed me out: http://tools.ietf.org/html/rfc6350#section-3.4 about escaping. To be frank, it drives me crazy :stuck_out_tongue_closed_eyes:.

**But**, least but not last, the `SOURCE` property is of kind `URI` according to http://tools.ietf.org/html/rfc6350#section-6.1.3. The given example is: `SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US`. So, it is wrong? Commas must be escaped here too. If yes, I will report a new erratum the RFC editors.

I am lost!

Thoughts?


Put dmc_fe_stream_id initialization (-1) to dvb_mux_create0().


Minor reword:

```diff
- "Follow us on twitter"
+ "Follow us on Twitter"
```

I'd probably drop the pipe:

**-**

![screen shot 2015-01-27 at 11 24 52](https://cloud.githubusercontent.com/assets/282788/5917661/403dfce6-a617-11e4-9383-d39180714e88.png)

**+**

![screen shot 2015-01-27 at 11 24 41](https://cloud.githubusercontent.com/assets/282788/5917660/38460452-a617-11e4-85d7-b2672660900d.png)


Thanks!


Done. See PR for updates.


I think it was just to be a container of the labels, but actually there is no really reason.


It's i18n？


develop (rraustad) - Win64-Windows-7-VisualStudio-12: OK (1098 of 1098 tests passed)

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


`let`/`var` can be in swift func, but `(` appear before `let`/`var` only happens when `private(set)` or `internal(set)` is used


Maybe rename this to `show faction status`?
We may specify another faction than our own using the command argument.
With that in mind the word `your` in `status of your faction` is misleading.

Another thing to keep in mind is that permission node descriptions must match the format `You don't have permission to X.`. Compare the following two for better understanding:

* You don't have permission to `status of your faction`.
* You don't have permission to `show faction status`.


/ping @evert and @armin-hackmann on this one.

There is no test about this so I don't know if I am wrong or not. There is only one test with jCard but an incomplete one (not a roundtrip). If you agree on this one, I will update the jCard test.


moby


Censorship ftw, huh?


Forget what I said about jCard, it's about jCal, and the `GEO` property is not consistent between these two, so it's not a problem. I am just asking a review for the patch, nothing more.

PS: here is the patch to resolve the conflict between `GEO` in xCard and xCal: https://github.com/Hywan/sabre-vobject/commit/c802ff5a80397fc5905b4f62499b7bc298824c2b.


I could get on board with that. Areas where we might encounter issues:

- lxml - lxml seems to insist on returning ascii/byte strings, unless unicode objects are explicitly requested (even in python3).
- serialization with sqlalchemy
- (testing only) vcrpy request matching
- (unlikely) in interface with requests    when sending raw data


Done https://github.com/postcss/autoprefixer-core/commit/7e8c099501dff068f0245e82332706f8a7b00319


Crappy comment ftw, yeah. Who cares if it's micro optimization or what.


Sorry, we just forgot two files in the last commit of the corrected patch.
You might prefer using the macro VER with the ifdef condition instead of the G_ENCODE_VERSION we use here. It's up to you.
Regards


looking good overall, but i'm wondering if this is not the work of the view: properly hiding itself (buttons included)?


This line breaks my module with the Error

typeError: Object #<Console> has no method 'warning'
    at Ftp.setDebugMode (/private/var/folders/6b/mdkb0cdj2pdf47ll4wv14s440000gn/T/iron-worker-ng-20150127-34897-17nysz5-container/node_modules/jsftp/lib/jsftp.js:107:11)


TeamCity Ylab :: synteny/ylab [Build 43](http://192.168.30.225:8111/viewLog.html?buildId=674&buildTypeId=Ylab_SyntenyYlab&guest=1) is now running


Ouch. I wish I hadn't been stupid enough to listen to the suggestion from @ccrs :
https://github.com/TrinityCore/TrinityCore/pull/13941#discussion-diff-23185135 + https://github.com/TrinityCore/TrinityCore/pull/13941#discussion_r23185135

Basically what you are saying is that I ought to revert to my deleted PR #13941 ... D'oh! -- /facepalm


Make this a utility method somewhere instead of inlining it?


deleted


@Oted Wow, thanks for pointing that out. Should be `console.warn` instead. I will patch it ASAP.


I test now new image flash on OS1+  - it's ok, no error


@drewolson this should fix your other bug. Please let me know if everything is good on master and i will publish 0.7.1!


No need to split lines here


This design allows silent failure rather than throwing a warning.
What if a user types `f status 1 somefaction brööööl`?
The user should get a warning saying the sorting bröööl is unknown.
I think you need to return null per default and ARAbstractSelect will take care of the rest.


Better just revert b8a70f4 ("rxe: Add bypass arbiter")


Great post! A couple of reactions:

1. In your opening paragraphs you hit on a key point: ensuring healthy open-government cannot be exclusively a governmental function; it requires civic engagement. In the case of open-government data, ensuring healthy practices requires a "technologically-democratized society". :+1:

2. I am intrigued by your critique of separating data/interaction and the analogy to First Amendment jurisprudence. Under the traditional First Amendment jurisprudence, it is practically an article of faith that the solution to harmful speech is "more speech." So, one could argue, so what if Westboro Baptist Church uses government data to advance the political agenda? Others can compete with that speech using the same or other data sets. But your argument goes a little deeper, and is reminiscent of [the debate on hate speech](http://opinionator.blogs.nytimes.com/2012/11/12/going-in-circles-with-hate-speech/). More pointedly, at what point is the government responsible for promoting or discouraging harmful speech?

To that end, your suggestion about redaction (and we'll discuss alternative screening mechanisms in the Privacy session) seems to be that it can actually be a democracy-enhancing mechanism. Do I have your argument right?

Also, because @gcooper08 and @ais2 commented [here](1647ea760ec0839971e4c329083108d16bd52893), I'm going to suggest that we continue the conversation on this post. Also, @ais2, what took two years to redact?


This is the strangest error code.

It returns success with 0 length, which has probably some meaning, because there does not exist a client sockname.

Should we return something more practical, like EBADF, or leave it like this?


Ignore me, I was confused - thought these were dangling changes for the official repo not my old version of the sdo-stantz branch.


http://i.gyazo.com/1f530e240cd07a306d419cf234c161ff.png
Is it just me or does the sorting by time look a bit strange still?
* 2months3weeks20h
* 2months5days1h
* 2months3weeks20h


This error code is strange too.

We are listening with a server, so the server has no peername, yet it returns UV_ENOTCONN...

Leave it or change it?


Why not remove this function at all and call dev_queue_xmit() from the NF_*()?


This is already the case of the form view, but not of pivot. I can fix it.


TeamCity Ylab :: synteny/ylab [Build 43](http://192.168.30.225:8111/viewLog.html?buildId=674&buildTypeId=Ylab_SyntenyYlab&guest=1) outcome was **FAILURE**
Summary: Tests passed: 101; exit code 1 (new) Build time: 00:08:52


Do any of the curl experts have any idea how this crash could happen? I saw it multiple times now in the forum:

http://forum.kodi.tv/showthread.php?tid=209855&pid=1904516#pid1904516

@arnova @ulion @Karlson2k


Double indent here. You should remove one of the two tabs since there is an extra one.


In the list view of KBArticles , status column shows Integer values, whereas it shouldn't.
liferay-ui:search-container-column-text was causing the issue , so i have replaced it with <liferay-ui:search-container-column-status.
Now this functionality is working as expected like other portlets (web content etc).


I am unhappy that there is no normal standard deployment for JS, so this is just desperate solution. I'll move it to separated branch, probably the best is simply to not solve it.


Done, sorry for the inconvenience, @Oted. Hopefully it works just fine now. Please update to v1.4.1.


ServerConnectedEvent only adds handlers for existing channels, and as the server just connected there won't be any!

Needs to listen for a ChannelSelfJoinEvent as well, I think.


You may want to remove that `'` at the end.


Whoop! :smile:


Why would a guru haul a [canvas sack](http://thumbs.dreamstime.com/x/burlap-sacks-potatoes-8293765.jpg) around?


well, I like the idea behind it, but dimaursu has a valid point. It could lead to some difficulties since your project relies on integration into different pages.


A new authoring tool? Yeah, this should be fixed in another bug report :P.


Please don't use `mixed`. :)


OTRS scheduler start/stop script for systemd with mariadb.
If mariadb is not running when starting OTRS, start mariadb automatically.
1) Place it to /usr/lib/systemd/system.
2) Exec 'systemctl daemon-reload' to recognize OTRS to systemd.
3) You can operate OTRS scheduler with 'systemctl {start|stop|restart|status} otrs[.service]'.


There's probably cause to update code references and use the newer version of superclosure but I've not looked in to that at all due to time constraints; updating composer.json to stick to 1.x resolves the issue quickly.


we should use $.util.log instead.


Just checking....


OTRS scheduler start/stop script for systemd with oracle.
If oracle is not running when starting OTRS, start oracle automatically.
1) Place it to /usr/lib/systemd/system.
2) Exec 'systemctl daemon-reload' to recognize OTRS to systemd.
3) You can operate OTRS scheduler with 'systemctl {start|stop|restart|status} otrs[.service]'.


Should return void


this should go into the queries-api


OTRS scheduler start/stop script for systemd with postgresql.
If postgresql is not running when starting OTRS, start postgresql automatically.
1) Place it to /usr/lib/systemd/system.
2) Exec 'systemctl daemon-reload' to recognize OTRS to systemd.
3) You can operate OTRS scheduler with 'systemctl {start|stop|restart|status} otrs[.service]'.


Right... loss of functionality/feature would be backwards incompatible which this is not.


@JimBobSquarePants - I'm happy to add you as a committer - if you want?
I'd prefer to still deal with PRs for bigger stuff - I like the discussions.


Yes, your findings are correct. Using an `Uint8Array` (`[]byte` in Go) for `send` is better in the regard that it avoids encoding issues. Also see my explanations in #167.


Should we really change the faction with `this.changeFaction()` before checking if a change is required with `isChangeRequired`?


This is a perfectly fine solution from an elisp standpoint, but this `cl-loop` portion is meant to pivot the data and is already fairly complex; I think I would prefer that we tack on the temperature unit symbols in the `sunshine-build-simple-forecast` function, which is where the raw data from the API is "massaged" into a nice elisp structure.

Do you want to take a stab at that? I agree this is a needed enhancement and would be happy for the help.


Yes. Changing the respeaking mechanism seems to make a bug for original recording. I'll fix it soon.


isChangeRequired only checks for rank change, not faction change. Sommeren might also do /f rank Cayorion derp, even of Cayorion is already a member of derp.


Hi,

On 27.01.2015 00:48, probonopd wrote:
>
> There is http://nginx.org/download/nginx-1.7.9.tar.gz now; is there a
> reason we still use 1.4.7?
>

Feel free to submit a seperate pull request.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/openwrt/packages/commit/e9da522f68ab4553ad16c077a59a38171664fdd3#commitcomment-9450319>.
>

cheers
thomas


@clicman nope, I already release it.


not sure if this makes really sense, but it would be so cool if you could just pass a parameter { trace: true } and you get both trace + response automatically. This way we could turn it on for the cellstore manager UI.

what do you think?


Agreed!


send a pull request


Could you please fill the release notes? https://github.com/allure-framework/allure-cucumber-jvm-adaptor/releases You can use this page https://github.com/allure-framework/allure-core/releases as example


Agreed, they shouldn't rely on anything connected with the user. Checking if they exist seems to be more reasonable indeed.


Should be consistent with use of colons after form labels:

![screen shot 2015-01-27 at 11 56 24](https://cloud.githubusercontent.com/assets/282788/5918030/a71779fc-a61b-11e4-9126-104c60abcb89.png)


Bad practice! Arguments are to be read. Not set.


構文エラー


наверное, перепутал)


Musste es sowieso anpassen und habe dann ein .txt daraus gemacht. Jetzt funktioniert es einwandfrei.


Bad Practice! What's wrong with using?:
`if (target.getRole() == Rel.RECRUIT && rank == Rel.RECRUIT)`
`if (target.getRole() == Rel.LEADER && rank == Rel.LEADER)`

How about grouping these two together even further using?:
```java
if (target.getRole() == rank)
{
    msg("%s <b>is already %s.", target.describeTo(msender), Txt.getNicedEnum(rank));
    return false;
}
```


Looks perfect! :smile_cat:


もしかして `entity` ではなく `domain` ではないですか？


Need to adjust the tabindex so that it goes `name -> email -> password -> confirm password`.

![2095-tab-index](https://cloud.githubusercontent.com/assets/282788/5918074/5ec9f43a-a61c-11e4-8b3b-5ee32bcaa155.gif)


You should remove this empty line again.


Please make this code conditional: test `PyInstaller.compat.is_py3`.


1st commit


Will this have any impact on buildtools-tarball.bb


Because we are going to add the FCoE like xmit function here, The commit under testing.


This line break is not part of our coding style.
Could you make it just one long line please? :smile_cat:


Why do you like www better? I don't!


are you out of your mind?
i suggest you remove this file immediately...
there are enough leaks of it already...
and you will get reported now as leaker as well...


Mariage de qui ?


Closed Visual Studio Online Task [vso#4345](https://azurecom.visualstudio.com/DefaultCollection/ACOM/_workitems#_a=edit&id=4345): 'This is a test usersnap task submission'

VSO State: Done


missing semicolon


i'll do it.

Thanks.


Why does this work on real hardware when it's not supposed to work? I think adding a better solution would be to fix the PIC IRQ behavior instead of a kludge/workaround like this. The name-calling and swear-words in the help text don't make it look very professional either...


Please write `// Args` here.


Please write `// Create Messages` here.


:cake:


Please write `// Send Messages` here.


Ok.


Ok, than I will fix and merge, if there are no open issues left yet.


Please make this one long line instead of word wrapping manually like this.


Please write `// NoChange` here.


Please write `// Args` here instead of `Reading arguments`.


@liewegas ，my thought :
for selfmanaged snapshot mode ,  snapshot info of rbd is stored in objectmap, we can not get snapshot id through snapshot name.  for pool snapshot mode , snapshot info is stored in osdmap , but for both snapshot modes , pg_pool_t::snap_seq is increased by one when you create or delete snapshots,   so we can use snap id as parameter

how to list objects for specific snapshot

when you update objects , current seq will stored in object xattr,  named as xattr_seq , when specify a snapshot, we can get snap_seq for that snapshot , named as snapshot_seq ,  if xattr_seq >= snapshot_seq , then objects exist in that snapshot. for removed objects , we should make sure HashIndex::get_path_contents_by_hash to list these objects (oid.snap == CEPH_SNAPDIR)

any comment on this ?


Please make this one long line instead of manually word wrapping like this.


Thanks! I'll work on my squashing for future contributions. :)


Nej, dom är jävligt vettiga! maximum-scale är egentligen najs också, för folk som ser okej, så slipper man råka pinch-to-zooma. Men för folk som måste zooma för att kunna läsa så är det lite kefft. Det här har jag iofs också bara läst på internet... :stuck_out_tongue:


from my understanding , pool snap_seq is also greater than 0 if we are using selfmanaged snaps, am i  miss something?


It is no longer possible to save changes (e.g. model parameters), see error below.

Traceback (most recent call last):
  File "/Users/benedikt/phd-project/software/owl/owl.py", line 544, in closeEvent
    self.fileLoader.saveModels()
  File "/Users/benedikt/phd-project/software/owl/cxi/fileloader.py", line 227, in saveModels
    m.saveParams()
  File "/Users/benedikt/phd-project/software/owl/parameters.py", line 96, in saveParams
    if n in grp:
  File "/Users/benedikt/phd-project/software/owl/cxi/fileloader.py", line 14, in __getitem__
    return self._ds[args]
  File "/Library/Python/2.7/site-packages/h5py/_hl/group.py", line 153, in __getitem__
    oid = h5o.open(self.id, self._e(name), lapl=self._lapl)
  File "/Library/Python/2.7/site-packages/h5py/_hl/base.py", line 113, in _e
    name = name.encode('ascii')
AttributeError: 'int' object has no attribute 'encode'


why not second spi_transfer_internal(spi_dev, flags, byte_out) call here?


Where is "mixediterateiterate" definition ?


should it be centos6/7?
are we going to build/support el6?


btw, time to bump copyright templates in IDEs to 2015 ;)


Thanks! That could save a wee bit of time in the future yeah. Being able to make feature branches would be great.

I'm a big fan of the discussions also. They're a great sanity check and learning tool.


Please move this line (`List<String> messages = new ArrayList<String>();`) down to just above line 67 (`messages.add(Txt.titleize("Flag for " + faction.describeTo(msender, true)));`).


Since the spec says that public clients *may* be authenticated, I think a different name for the configuration option should be used here (since public clients may still be authenticated) - instead of "allowPublicClients", how about "allowUnauthenticatedClients"?


Please move this line (`List<String> messages = new ArrayList<String>();`) down to just above line 67 (`messages.add(Txt.titleize("Perm for " + faction.describeTo(msender, true)));`).


@arjuntemurnikar @rnysto: there is already a reduced depth based on depth = 1 + level in SF. what are you talking about ?


Please write `// Create Messages` here.


Please write `// Send Messages` here.


I fixed a similar defect in libfoundation in a slightly different way in commit 6d2ceeeda4a2baf0ce9e593a5ff1fd2cf54bb807.


squash 하면서 이 커밋 유실된 듯?


nope . In wod, if player Stuck and died on textures , player teleported to near graveyard.


treatment of prostatitis


Don't word wrap like this please.


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


Indent errors above.


Missing `@author` annotation here.


Even with public clients, the client should always exist -  you may not need a client secret but a clientId is required.


Remove this double empty line, please.


Oh yea, minor oversight, I guess I only tested loading it after I'd joined.


Done, ta-dah! :sparkles:


Missing `return` here, nop ?


/CC @jmervine https://github.com/XhmikosR/bootstrap-cdn/commit/e3760da9c0dd4c175fcac3796a272f892a174844?w=1


Why not just remove the dead code entirely?


I'm still interested in seeing a SilentPermittedCommandSender implementation.
But if you want to use reflection packets instead, feel free to do so.
They both have their upsides and downsides.


The Swanna front models aren't uploaded yet, but it's the actual sizes they are now.


I'm assuming you are using these messages to debug the software :smile_cat:


Missing a space between the "catch" and the "(".


Need to fix the spec since the title text has been changed:

```diff
diff --git a/spec/integration/alaveteli_dsl.rb b/spec/integration/alaveteli_dsl.rb
index b408bc4..370628d 100644
--- a/spec/integration/alaveteli_dsl.rb
+++ b/spec/integration/alaveteli_dsl.rb
@@ -21,7 +21,7 @@ module AlaveteliDsl
     response.should redirect_to(:controller => 'user', :action => 'signin', :token =>
     follow_redirect!
     response.should render_template("user/sign")
-    response.body.should match(/To send your FOI request, please sign in or make a new
+    response.body.should match(/To send your FOI request, create an account or sign in
   end

 end
```


`const` input values just look funny - in my opinion.


Please write
````java
// -------------------------------------------- //
// CONSTANTS
// -------------------------------------------- //
```
here.


@smcv sorry to bug you with this, I figured it out myself; Python is awesome


Mince, lotte ne s'est pas ajouté en devDependancies, npm install -g lotte --save-dev n'a pas ajouté de ligne à package.json..


@konklone [Rep. Hurd](https://hurd.house.gov/), formerly of the CIA a cybersecurity firm!


Sure! I like it that you are interested in the internals of the compiler :smiley: . The lexer and parser are just the first entry points to it, not related to the real semantics, but they are still part of it :-)

So, the question is how to know if a `/` is division operator or the start of a regex. I don't know how Ruby does it, and I tried in different ways to achieve it and this is the solution I came to that works. So I'm sure there must be other ways. But, as long as the specs pass, and as long as the code doesn't become a mess (here it's just one flag to control the lexer), I'm fine with it (the end-user of the language usually doesn't care about the code of the compiler, only that it works and that it's efficient).

So, for example, if you have `foo(` and then a `/` comes, it must definitely be a regex. It can't be a division because it doesn't make sense there. Same goes with `a = `, `if `, etc. So before tokenizing those things I set the "slash_is_regex" flag to true. Then if the lexer finds a `/` it treats it as a regex start. By default the `slash_is_regex` starts being true, so parsing `/ /` will work, but after a non-space token is it set to false unless explicitly set to true by the parser.

It could be done the other way around too: set the flag to false in some places. But I found those places harder to think of (after a parenthesis, after an if, after a conditional if, etc.).

I don't know if this can be done without a flag.

Then there's another flag, `@wants_regex`. If the lexer sees `/a` you might think it's a regex, as in `foo /a/`. However if in the previous expression `foo` is a variable (and this is determined by the parser) then a slash , even if followed by a non-space, will be a division operator.

In Ruby this is the same:

```ruby
def foo(x)
  puts x
end

# foo = 1
foo /a/
```

The above parses well if you keep the "foo = 1" commented, but gives a syntax error if you uncomment it.

If there's something more you need to know, please let me know :smile_cat:


Change to:
```java
private List<String> errorMsgs = new ArrayList<String>();
```


Remove this line.


Change to:
```java
public MassiveCommandException(Collection<String> msgs)
```


Well its not dead-code - just unfinished - it should perhaps be factored onto a separate branch for someone to debug and try to get to work at some point.


No need to copy & paste the documentation - in my opinion it should be in the `cpp` file.


Fuck yeah! Look at all these removed lines! Aint life with exceptions grand? :smile_cat:


Cody style 没有 lint 过。能不要在这么简单的问题上反复出问题吗？


Re search_images - this API call is currently under review and might get deprecated and revised soon, and as such we'd prefer not adding this binding to the SDK


@mcostalba: ok. maybe we drop level 0 and go from 1 to 40.


@baev Done!


@dkayiwa We would have to call getters several times otherwise


A more general thought: Do we really need to implement the errorMsgs field ourselves? Isn't there some sort of built in message feature in some existing Exception class we could extend?


Done.


Ah, you have corrected it here, sorry for the noise.


The `max` initialization does not make any sense - it is never checked for and it is certainly not a valid return value.


You removed the dollar sign from the $3 in the mod function.


We can probably provide much better backwards compatibility than this, right?
Deprecated methods should provide the same functionality as they did before deprecation.
This way old plugins will still work perfectly fine.


This could just return an actual completion; i.e. `return m_completions[closest]`?


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1976](http://teamcity.monogame.net/viewLog.html?buildId=5095&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 366, ignored: 6 Build time: 00:16:50


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


Case insensitive?


This looks wrong, inside the brackets should be the type, which in this case is presumably {Object}.

Likewise for below.


But in all honesty backwards compatibility is not too important in this case.
Code a perfectly working backwards compatibility or... eeeh remove it alltogether :smile_cat:


Merci beaucoup!

1/ Est-ce possible de tester si le service qWat existe et l'utiliser? Comme ça pas besoin de rentrer de paramètre.

2/ Est-ce qu'on devrait pas faire des processus distincts pour les 2 schémas? Ca peut attendre, mais ca peut être bien de pouvoir faire les updates que sur un seul schéma.


soooo pretty!


Snyggt jobbat!


There is no need to compare `invalid` to boolean value since it's a boolean value.


moved TFPlayer inside TF


I realize there are quite wide differences in opinion regarding inline documentation, but to me:
```C++
/// Helper for orderCompletions.
```
actually reduces the readability of the code - which I guess is really contrary to the purpose. But no big deal.


dsdsd


You should.


I guess with the new constructor implementation you could just use the `(10,10,10)` constructor and remove the inlined deck?


It does. It could however be that this "bug" comes from TimeDiffUtil.limit, where we currently limit it to 3 times. Let's see how this changes the appearence. Mostly though, it will not make such a difference. (the kick time is much shorter than months  ;) )


Timmy ska vi ta rast och gå till hemköp?


The only issue I had was using the git clone command because I was using the parentheses at first, but we talked about that in the email and everything else was straight forward.


ack


Das wird so aber nix, die Klasse heisst nicht so :)

Vermute search and replace Fehler.


I remember this having been introduced earlier than 1.12 :)


I'm not sure if this isn't to general name, because sooner or later you will probably add a validation method for other inputs, e. g. username.


The same as above.


ack - this is the better way


Checking them against the database may add unnecessary overhead as every single code needs to be checked and probably needs to be recalculated. I've nothing against it but tbh I don't think it's necessary.


I already figured out that having the if-then-else statement inside of the loop is bad so I would have pulled it out next and just inserted the value in the format string. But I'm not sure where I would tack that on in the cl-loop inside of `sunshine-build-simple-forecast`, as you do the high and low calculation inside of `sunshine-pivot-forecast-rows`. I guess you would need to pull out the max min thing into `sunshine-build-simple-forecast` as well, wouldn't you?


@Razzeee any news on the cert error? thanks!


Could you please only update the scss file and compile it again?
https://github.com/contao-community-alliance/dc-general/blob/develop/contao/html/sass/generalDriver.scss

Now the css and scss are out of sync and I have no clue what you changed.


Can we provide some suggestions on what one could do to make it writable? I have seen a number of people, on the mailing list, facing this. And hence giving them a clue as to what command they could execute to make it writable, will be very helpful. not so? :)


Would it be possible to mark the `std::vector<const CompletionPtr>` of `CompletionSet` mutable, and thereby avoid the copy operation here? Or is that to much abuse of the `mutable` keyword?


Hi could do with your help I don't understand this email. Have I received it for a reason and what action do I need to take if any. Much appreciated thanks.

On 27 January 2015, at 12:17, Alemesegd <notifications@github.com> wrote:

￼

treatment of prostatitis

—
Reply to this email directly or view it on GitHub.￼


This method wasn't publicly available til now. Should i remove the annotation?


I didn't think that you would set state for each input in this method like you did in the next commit. It's ok :).


I would think it was possible to insert one new completion, in an otherwise sorted list, as an O(n) operation?


Let us make it public and preserve the annotation. But just put the correct version in which it was put.


Thanks, fixed in 226562bfed0db6aa291e37eed6e4c8163e37117b.


I unfortunately can't get closure compiler not complaining with type checking here.


과연. 그리고 버그가 있어서 새로 ba391d9 에 커밋함


shouldn't it be get_histories?


is this not used anywhere?


Flexibility is good but it does me feel blind sometimes.


    moviuro@psychoticdelirium ~ % lol=foo/bar
    moviuro@psychoticdelirium ~ % echo ${lol%/}
    foo/bar
    moviuro@psychoticdelirium ~ % lol=/foo/bar/
    moviuro@psychoticdelirium ~ % echo ${lol%/}
    /foo/bar
Nothing funny, works as expected ;-)


same as above


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1977](http://teamcity.monogame.net/viewLog.html?buildId=5097&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 366, ignored: 6 Build time: 00:16:10


<img src="http://stream1.gifsoup.com/view/1036636/cat-in-bathtub-o.gif">


Since you have change your url pattern, all links related to it should also change.
For your convenience, use {{ group.name }} rather than a hard code one.


I hereby release all of my contributions to this project under the terms of the Apache 2 license.


Yes, so I moved it to the new _variables.scss file https://github.com/Financial-Times/o-ft-typography/blob/ac9afe5ce3b6c059a64ea42718e1043d283616ab/scss/deprecated/_variables.scss


I don't either. But, since Fastmail is handling my DNS now I had to switch to `www`. (I might have misread their docs on this, but this all that seems to work).
Chris Russo writes:

> Why do you like www better? I don't!
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/kostajh/kostajh.github.io/commit/77d0f596a8d795a885c55dd027e659214bff1789#commitcomment-9457767

--
kostaharlan.net | @kostajh


Ali pa uporabita urejevalnik besedila, ki ne deluje na zobata kolesa in golobe, ampak zna sam pravilno zamikati kodo.


Can you drop the `:` and append it in code instead?


Good FIX.

This change worked again very well, but... nevermind, none will have that setup where this change needs set "char.count" to ZERO...

SettingsWIPE,
---

set your character count as "0" and you got settings wiped.

If settingwipe is added to UI, it must go in hidden settings, xD.


I did't really understand this part:

> but after a non-space token is it set to false

The only place it is setting the flag to false is when there is a `SPACE` after a call arg, or something like that, right?


This is veery old code ;-) And `_handleValid` is general here on purpose because all components use the same callback later. Please refer to file:

https://github.com/squerb/squerb_foundation/blob/master/vendor/assets/javascripts/squerb_auth/components/register/email/email.coffee.cjsx

How it supposed to look at finish.


Great job! Thank you for puttin in the time to do this. I am sure @KoffeinFlummi & Co. will appreciate it as much as I do.

:+1:


Because it is written as a loop... Looking at this now it seems less than obvious. Should I unroll this for code readability?


`{Object}` ?


>  I'd prefer to leave release cherry-picks to Quintus, though.

This is so simple a change that I don’t mind if anyone of you cherry-picks it to `release-2.0.0`. However, if you do cherry-pick, please use the `-x` option so there’s a marker in the commit message that actually says the commit has been cherry-picked.

> To clarify my primary worry is the translation subsystem.

Static strings in XML files never make it to the translation system usually, with very few exceptions such as the colour names. This is bad, but that’s how it stands currently.

Also. I remember someone of you saying that this space before the final punctuation of a sentence was a German habit. I highly object that! (note missing space). This is invalid syntax in German also.

Vale,
Quintus


We assume the "evothings" library was loaded first.


I’ve done the cherry-picks now.


ACK this commit


Maybe add:
```
@see <a href="https://github.com/scijava/scijava-common/issues/12345">issue #12345</a>
```
Where `12345` is an issue describing the fact that we want to eventually stuff this information into a proper cache, rather than this eternal `HashMap`.


`HasTimer()` also uses the lock, can you move the lock to after the check?


This assignment is already done a few lines up.


@mcostalba: the depth modulo 4 effect is **not** going away at higher levels, as you anticipated:
http://tests.stockfishchess.org/tests/view/54c62fed0ebc592af9bfe088
http://tests.stockfishchess.org/tests/view/54c630580ebc592af9bfe090
http://tests.stockfishchess.org/tests/view/54c786ea0ebc593c176ab8c8
http://tests.stockfishchess.org/tests/view/54c78b370ebc593c176ab8d0


looks good - lets just cleanup the format of this file.


... weird. It was present on my install (fresh from yesterday), but indeed is removed from the patch. Maybe the update did not run completely through ... Will have to keep an eye on that. I'm closing the PR.


Commentaire test pour la version 1.1


maybe instead of depth we should use a nodes limit. this would resolve the problem more correctly.


This could be `executeVoid` as it's only ever used in a sequence and not at the end, so that's the method that will be called. You can then return `nil` in `execute` (which I don't imagine will ever actually be called).


`GetClientLocalizedString` would probably be more obvious


printFun ||= console.log;


23:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. from invenio.ext.template should be before from wtforms.widgets


white.orElse(black).fold(0)(_.assessment)


lets delete this line - since we know moving forward all posts will be associated with a user when we create them


Use single quote (') for python coding style
The tabs in this code seem to be 2 space instead of 4


`GetTimerTypeLocalizedStringId` is long and ugly but at least to me more clear than this.


Lol


It would be much more readable to create a class that extends `HashMap<Class<?>, List<Field>>` called e.g. `ClassFields`. Then create another class called e.g. `FieldCache` that extends `HashMap<Class<?>, ClassFields>`. Then make the `fields` variable here be a `FieldCache` and you're good to go. Then below, you won't have any more explicit `Map<...>` references, which will improve succinctness. Yes, we can even be DRY when it comes to typing! :joy:


need to add an ending </small> here

also - lets cleanup the formatting(tabs) here.


en?