1: D400 First line should end with '.', not 's'
2: I102 copyright year is outdated, expected 2015 but got 2014
37:6: E126 continuation line over-indented for hanging indent
74:25: E203 whitespace before ':'
75:25: E203 whitespace before ':'
76:25: E203 whitespace before ':'
81:25: E203 whitespace before ':'
85:25: E203 whitespace before ':'
103: D400 First line should end with '.', not 'r'
103: D200 One-line docstring should not occupy 3 lines
131:1: E302 expected 2 blank lines, found 1
131: D202 No blank lines allowed *after* function docstring, found 1
131: D400 First line should end with '.', not 'r'
131: D200 One-line docstring should not occupy 3 lines
153:1: E302 expected 2 blank lines, found 1
153: D200 One-line docstring should not occupy 3 lines
163:1: E302 expected 2 blank lines, found 1
163: D401 First line should be imperative: 'Get', not 'Gets'
163: D202 No blank lines allowed *after* function docstring, found 1
163: D200 One-line docstring should not occupy 3 lines
171:9: E221 multiple spaces before operator
176:1: E302 expected 2 blank lines, found 1
176: D401 First line should be imperative: 'Return', not 'Returns'
176: D205 Blank line missing between one-line summary and description
186:1: E302 expected 2 blank lines, found 1
186: D400 First line should end with '.', not 'e'
186: D205 Blank line missing between one-line summary and description
196:1: E302 expected 2 blank lines, found 1
196: D400 First line should end with '.', not 'e'
196: D205 Blank line missing between one-line summary and description
206:1: E302 expected 2 blank lines, found 1
206: D209 Put multi-line docstring closing quotes on separate line
206: D202 No blank lines allowed *after* function docstring, found 1
206: D400 First line should end with '.', not 'r'
206: D205 Blank line missing between one-line summary and description
215:1: E302 expected 2 blank lines, found 1
215: D400 First line should end with '.', not 'e'
215: D205 Blank line missing between one-line summary and description
231:1: E302 expected 2 blank lines, found 1
231: D400 First line should end with '.', not 't'
231: D205 Blank line missing between one-line summary and description
263:85: E261 at least two spaces before inline comment
263:86: E262 inline comment should start with '# '
268:1: E302 expected 2 blank lines, found 1
268: D200 One-line docstring should not occupy 3 lines
281:9: E113 unexpected indentation
282:13: E113 unexpected indentation
283:17: E113 unexpected indentation
284:13: E113 unexpected indentation
285:17: E113 unexpected indentation
286:13: E113 unexpected indentation
287:17: E113 unexpected indentation
288:13: E113 unexpected indentation
289:17: E113 unexpected indentation
290:13: E113 unexpected indentation
291:17: E113 unexpected indentation
293:9: E113 unexpected indentation
294:13: E113 unexpected indentation
295:17: E113 unexpected indentation
296:13: E113 unexpected indentation
297:17: E113 unexpected indentation
298:13: E113 unexpected indentation
299:17: E113 unexpected indentation
301:1: E302 expected 2 blank lines, found 1
301: D401 First line should be imperative: 'Print', not 'Prints'
301: D202 No blank lines allowed *after* function docstring, found 1
318:37: E713 test for membership should be 'not in'
381:1: E302 expected 2 blank lines, found 1
381: D401 First line should be imperative: 'Generate', not 'Generates'
381: D202 No blank lines allowed *after* function docstring, found 1
400:1: E302 expected 2 blank lines, found 1
400: D401 First line should be imperative: 'Generate', not 'Generates'
400: D202 No blank lines allowed *after* function docstring, found 1
425:30: E261 at least two spaces before inline comment
458:1: E302 expected 2 blank lines, found 1
458: D401 First line should be imperative: 'List', not 'Lists'
458: D202 No blank lines allowed *after* function docstring, found 1
458: D200 One-line docstring should not occupy 3 lines
479: D401 First line should be imperative: 'Return', not 'Returns'
479: D202 No blank lines allowed *after* function docstring, found 1
495:12: E127 continuation line over-indented for visual indent
504:1: E303 too many blank lines (3)
504: D401 First line should be imperative: 'Generate', not 'Generates'
504: D202 No blank lines allowed *after* function docstring, found 1
504: D208 Docstring is over-indented
528:17: E128 continuation line under-indented for visual indent
529:17: E128 continuation line under-indented for visual indent
530:17: E128 continuation line under-indented for visual indent
531:17: E128 continuation line under-indented for visual indent
532:17: E128 continuation line under-indented for visual indent
548:1: E302 expected 2 blank lines, found 1
548: D200 One-line docstring should not occupy 3 lines
554:1: E302 expected 2 blank lines, found 1
554: D200 One-line docstring should not occupy 3 lines
562:1: E302 expected 2 blank lines, found 1
562: D401 First line should be imperative: 'Generate', not 'Generates'
567:1: E302 expected 2 blank lines, found 1
567: D401 First line should be imperative: 'Generate', not 'Generates'
571:1: E302 expected 2 blank lines, found 1
571: D401 First line should be imperative: 'Return', not 'Returns'
571: D209 Put multi-line docstring closing quotes on separate line
571: D400 First line should end with '.', not 'd'
571: D205 Blank line missing between one-line summary and description
587: D401 First line should be imperative: 'Return', not 'Returns'
587: D400 First line should end with '.', not 'C'
587: D200 One-line docstring should not occupy 3 lines
601: D290 White spaces around docstring should be trimmed.
615:29: E261 at least two spaces before inline comment
615:30: E262 inline comment should start with '# '
622:31: E261 at least two spaces before inline comment
622:32: E262 inline comment should start with '# '
636:1: E302 expected 2 blank lines, found 1
636: D401 First line should be imperative: 'Return', not 'Returns'
636: D200 One-line docstring should not occupy 3 lines
657:1: E302 expected 2 blank lines, found 1
657: D401 First line should be imperative: 'Generate', not 'Generates'
663:1: E302 expected 2 blank lines, found 1
663: D400 First line should end with '.', not 'e'
663: D205 Blank line missing between one-line summary and description
676:1: E302 expected 2 blank lines, found 1
676: D200 One-line docstring should not occupy 3 lines
682:1: E302 expected 2 blank lines, found 1
682: D401 First line should be imperative: 'Restore', not 'Restores'
682: D200 One-line docstring should not occupy 3 lines
691:1: E302 expected 2 blank lines, found 1
691: D200 One-line docstring should not occupy 3 lines
706:31: F841 local variable 'e' is assigned to but never used
710:1: E302 expected 2 blank lines, found 1
710: D200 One-line docstring should not occupy 3 lines
744:1: E302 expected 2 blank lines, found 1
744: D400 First line should end with '.', not 's'
744: D205 Blank line missing between one-line summary and description
756:39: E261 at least two spaces before inline comment
756:40: E262 inline comment should start with '# '
768:12: E713 test for membership should be 'not in'
769:16: E126 continuation line over-indented for hanging indent
772:18: E261 at least two spaces before inline comment
776:12: E127 continuation line over-indented for visual indent
785:12: E127 continuation line over-indented for visual indent
793:12: E127 continuation line over-indented for visual indent
806:12: E127 continuation line over-indented for visual indent
807:12: E127 continuation line over-indented for visual indent
813:12: E127 continuation line over-indented for visual indent
814:36: E261 at least two spaces before inline comment
820:12: E127 continuation line over-indented for visual indent
824:12: E127 continuation line over-indented for visual indent
829:12: E127 continuation line over-indented for visual indent
834:12: E127 continuation line over-indented for visual indent
839:1: E302 expected 2 blank lines, found 1
839: D401 First line should be imperative: 'Run', not 'Runs'
839: D400 First line should end with '.', not 'k'
839: D200 One-line docstring should not occupy 3 lines
845:90: E203 whitespace before ':'
845:91: E231 missing whitespace after ':'


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
5: I102 copyright year is outdated, expected 2015 but got 2014
33:28: E126 continuation line over-indented for hanging indent
55:1: E302 expected 2 blank lines, found 1
55: D203 Expected 1 blank line *before* class docstring, found 0
55: D400 First line should end with '.', not 'l'
58: D202 No blank lines allowed *after* method docstring, found 1
58: D400 First line should end with '.', not 'd'
58: D205 Blank line missing between one-line summary and description
91:13: F841 local variable 'last_comment_round_name' is assigned to but never used
97:139: E221 multiple spaces before operator
100:85: E231 missing whitespace after ','
100:87: E221 multiple spaces before operator
129:34: E127 continuation line over-indented for visual indent
141:13: E128 continuation line under-indented for visual indent
143:33: E203 whitespace before ':'
148:36: E225 missing whitespace around operator
149:168: E502 the backslash is redundant between brackets
149:57: E225 missing whitespace around operator
150:67: E127 continuation line over-indented for visual indent
153:13: E124 closing bracket does not match visual indentation
167:14: E127 continuation line over-indented for visual indent
169:14: E124 closing bracket does not match visual indentation
173: D401 First line should be imperative: 'Display', not 'Displays'
173: D205 Blank line missing between one-line summary and description
198: D400 First line should end with '.', not 'd'
198: D205 Blank line missing between one-line summary and description
231:26: E201 whitespace after '{'
231:45: E203 whitespace before ':'
231:22: E222 multiple spaces after operator
232:46: E203 whitespace before ':'
233:44: E203 whitespace before ':'
234:44: E203 whitespace before ':'
235:44: E203 whitespace before ':'
235:62: E261 at least two spaces before inline comment
235:63: E262 inline comment should start with '# '
236:44: E203 whitespace before ':'
236:62: E261 at least two spaces before inline comment
236:63: E262 inline comment should start with '# '
237:25: E124 closing bracket does not match visual indentation
247:13: F841 local variable 'last_comment_round_name' is assigned to but never used
274:106: E231 missing whitespace after ':'
274:143: E231 missing whitespace after ':'
275:32: E222 multiple spaces after operator
296:37: E225 missing whitespace around operator
316:13: E122 continuation line missing indentation or outdented
316:14: E201 whitespace after '{'
316:40: E203 whitespace before ':'
317:40: E203 whitespace before ':'
318:40: E203 whitespace before ':'
319:40: E203 whitespace before ':'
320:40: E203 whitespace before ':'
321:40: E203 whitespace before ':'
322:40: E203 whitespace before ':'
323:40: E203 whitespace before ':'
324:41: E203 whitespace before ':'
325:60: E225 missing whitespace around operator
326:40: E203 whitespace before ':'
327:13: E124 closing bracket does not match visual indentation
339:28: E128 continuation line under-indented for visual indent
340:28: E128 continuation line under-indented for visual indent
343: D400 First line should end with '.', not 'n'
343: D205 Blank line missing between one-line summary and description
382:35: E128 continuation line under-indented for visual indent
383:35: E126 continuation line over-indented for hanging indent
388:81: E225 missing whitespace around operator
388:100: E225 missing whitespace around operator
390:83: E225 missing whitespace around operator
413:105: E225 missing whitespace around operator
415:106: E225 missing whitespace around operator
421:110: E225 missing whitespace around operator
432:111: E271 multiple spaces after keyword
441:37: E126 continuation line over-indented for hanging indent
468:17: E127 continuation line over-indented for visual indent
468:33: E203 whitespace before ':'
469:33: E203 whitespace before ':'
470:33: E203 whitespace before ':'
480: D400 First line should end with '.', not 'n'
480: D205 Blank line missing between one-line summary and description
513:107: E231 missing whitespace after ':'
548:94: E225 missing whitespace around operator
554:99: E225 missing whitespace around operator
569:31: E203 whitespace before ':'
570:16: E128 continuation line under-indented for visual indent
571:16: E128 continuation line under-indented for visual indent
571:31: E203 whitespace before ':'
572:16: E128 continuation line under-indented for visual indent
572:31: E203 whitespace before ':'
573:16: E128 continuation line under-indented for visual indent
574:16: E128 continuation line under-indented for visual indent
574:31: E203 whitespace before ':'
575:16: E128 continuation line under-indented for visual indent
575:31: E203 whitespace before ':'
576:16: E128 continuation line under-indented for visual indent
576:31: E203 whitespace before ':'
577:16: E124 closing bracket does not match visual indentation
580: D400 First line should end with '.', not 's'
580: D205 Blank line missing between one-line summary and description
589:55: E231 missing whitespace after ','
672:13: F841 local variable 'c_round_name' is assigned to but never used
673:13: F841 local variable 'c_restriction' is assigned to but never used
682:26: E201 whitespace after '{'
682:45: E203 whitespace before ':'
682:22: E222 multiple spaces after operator
683:46: E203 whitespace before ':'
684:44: E203 whitespace before ':'
685:44: E203 whitespace before ':'
686:44: E203 whitespace before ':'
687:44: E203 whitespace before ':'
688:44: E203 whitespace before ':'
689:44: E203 whitespace before ':'
690:44: E203 whitespace before ':'
691:44: E203 whitespace before ':'
692:25: E124 closing bracket does not match visual indentation
699:22: E201 whitespace after '{'
699:37: E203 whitespace before ':'
699:19: E222 multiple spaces after operator
700:42: E203 whitespace before ':'
701:36: E203 whitespace before ':'
702:36: E203 whitespace before ':'
704:36: E203 whitespace before ':'
705:36: E203 whitespace before ':'
706:36: E203 whitespace before ':'
707:36: E203 whitespace before ':'
716:13: F841 local variable 'last_comment_round_name' is assigned to but never used
727:20: E127 continuation line over-indented for visual indent
734:35: E127 continuation line over-indented for visual indent
734:73: E221 multiple spaces before operator
743:132: E202 whitespace before ')'
744:33: E127 continuation line over-indented for visual indent
744:71: E221 multiple spaces before operator
745:140: E225 missing whitespace around operator
818:76: E261 at least two spaces before inline comment
826:275: E231 missing whitespace after ':'
827:163: E231 missing whitespace after ':'
860:38: E203 whitespace before ':'
860:62: E231 missing whitespace after ':'
862:38: E203 whitespace before ':'
862:61: E231 missing whitespace after ':'
863:38: E203 whitespace before ':'
863:63: E231 missing whitespace after ':'
865:35: E203 whitespace before ':'
1065:9: E122 continuation line missing indentation or outdented
1066:47: E203 whitespace before ','
1068:43: E225 missing whitespace around operator
1084: D401 First line should be imperative: 'print', not 'prints'
1084: D400 First line should end with '.', not 'm'
1092: D202 No blank lines allowed *after* method docstring, found 1
1092: D400 First line should end with '.', not 'n'
1092: D205 Blank line missing between one-line summary and description
1104:15: E221 multiple spaces before operator
1137: D400 First line should end with '.', not 'n'
1137: D205 Blank line missing between one-line summary and description
1155:15: E221 multiple spaces before operator
1157:9: E122 continuation line missing indentation or outdented
1158:9: E128 continuation line under-indented for visual indent
1159:9: E128 continuation line under-indented for visual indent
1176: D400 First line should end with '.', not 's'
1176: D205 Blank line missing between one-line summary and description
1196:22: E201 whitespace after '{'
1196:40: E203 whitespace before ':'
1197:40: E203 whitespace before ':'
1197:65: E202 whitespace before '}'
1202: D400 First line should end with '.', not 'r'
1202: D205 Blank line missing between one-line summary and description
1209:9: F841 local variable '_' is assigned to but never used
1218: D400 First line should end with '.', not 's'
1218: D205 Blank line missing between one-line summary and description
1237:22: E201 whitespace after '{'
1237:37: E203 whitespace before ':'
1237:19: E222 multiple spaces after operator
1238:42: E203 whitespace before ':'
1239:36: E203 whitespace before ':'
1240:36: E203 whitespace before ':'
1241:36: E203 whitespace before ':'
1242:36: E203 whitespace before ':'
1261:20: E222 multiple spaces after operator
1286:13: E122 continuation line missing indentation or outdented
1287:121: E502 the backslash is redundant between brackets
1288:28: E127 continuation line over-indented for visual indent
1289:100: E502 the backslash is redundant between brackets
1290:31: E127 continuation line over-indented for visual indent
1291:238: E271 multiple spaces after keyword
1300:50: E251 unexpected spaces around keyword / parameter equals
1300:52: E251 unexpected spaces around keyword / parameter equals
1335: D400 First line should end with '.', not 's'
1335: D205 Blank line missing between one-line summary and description
1353:22: E201 whitespace after '{'
1353:37: E203 whitespace before ':'
1353:19: E222 multiple spaces after operator
1354:42: E203 whitespace before ':'
1355:36: E203 whitespace before ':'
1356:36: E203 whitespace before ':'
1357:36: E203 whitespace before ':'
1358:36: E203 whitespace before ':'
1368:13: E128 continuation line under-indented for visual indent
1407:1: E128 continuation line under-indented for visual indent
1408:50: E251 unexpected spaces around keyword / parameter equals
1408:52: E251 unexpected spaces around keyword / parameter equals
1449:35: E203 whitespace before ':'
1449:42: E225 missing whitespace around operator
1450:35: E203 whitespace before ':'
1450:41: E225 missing whitespace around operator
1465: D400 First line should end with '.', not 'd'
1465: D205 Blank line missing between one-line summary and description
1472:22: E201 whitespace after '{'
1472:37: E203 whitespace before ':'
1472:19: E222 multiple spaces after operator
1473:42: E203 whitespace before ':'
1474:36: E203 whitespace before ':'
1475:36: E203 whitespace before ':'
1476:36: E203 whitespace before ':'
1477:36: E203 whitespace before ':'
1481:51: E221 multiple spaces before operator
1492:101: E222 multiple spaces after operator
1496: D401 First line should be imperative: 'Create', not 'Creates'
1496: D290 White spaces around docstring should be trimmed.
1496: D205 Blank line missing between one-line summary and description
1519:15: E221 multiple spaces before operator
1559: D400 First line should end with '.', not 'e'
1559: D200 One-line docstring should not occupy 3 lines
1585:19: E225 missing whitespace around operator
1589:36: E203 whitespace before ':'
1592:35: E203 whitespace before ':'
1593:35: E203 whitespace before ':'
1598:39: E225 missing whitespace around operator
1600: D400 First line should end with '.', not 'e'
1615:18: E225 missing whitespace around operator
1646: D400 First line should end with '.', not ')'
1646: D205 Blank line missing between one-line summary and description
1670:27: E127 continuation line over-indented for visual indent
1673:27: E127 continuation line over-indented for visual indent
1696:13: E201 whitespace after '{'
1696:25: E203 whitespace before ':'
1697:25: E203 whitespace before ':'
1698:25: E203 whitespace before ':'
1699:25: E203 whitespace before ':'
1701:26: E203 whitespace before ':'
1702:25: E203 whitespace before ':'
1703:25: E203 whitespace before ':'
1704:25: E203 whitespace before ':'
1734: D401 First line should be imperative: 'output', not 'outputs'
1734: D290 White spaces around docstring should be trimmed.
1734: D400 First line should end with '.', not 'd'
1738: D401 First line should be imperative: 'prepare', not 'prepares'
1738: D290 White spaces around docstring should be trimmed.
1738: D400 First line should end with '.', not 'r'
1753: D401 First line should be imperative: 'output', not 'outputs'
1753: D290 White spaces around docstring should be trimmed.
1753: D400 First line should end with '.', not 'w'
1768:34: E203 whitespace before ':'
1776: D400 First line should end with '.', not 't'
1776: D205 Blank line missing between one-line summary and description
1783:9: F841 local variable '_' is assigned to but never used
1822:17: E128 continuation line under-indented for visual indent
1822:50: E225 missing whitespace around operator
1822:69: E225 missing whitespace around operator
1823:17: E128 continuation line under-indented for visual indent
1823:36: E203 whitespace before ','
1823:23: E231 missing whitespace after ':'
1824:17: E128 continuation line under-indented for visual indent
1824:49: E203 whitespace before ','
1825:17: E128 continuation line under-indented for visual indent
1826:17: E128 continuation line under-indented for visual indent
1832:17: E128 continuation line under-indented for visual indent
1832:50: E225 missing whitespace around operator
1832:69: E225 missing whitespace around operator
1833:17: E128 continuation line under-indented for visual indent
1833:36: E203 whitespace before ','
1833:23: E231 missing whitespace after ':'
1834:17: E128 continuation line under-indented for visual indent
1835:17: E128 continuation line under-indented for visual indent
1840: D400 First line should end with '.', not 't'
1840: D205 Blank line missing between one-line summary and description
1846:9: F841 local variable '_' is assigned to but never used
1880:49: E225 missing whitespace around operator
1880:68: E225 missing whitespace around operator
1881:54: E272 multiple spaces before keyword
1883:49: E225 missing whitespace around operator
1883:68: E225 missing whitespace around operator
1884:54: E272 multiple spaces before keyword
1890:13: E128 continuation line under-indented for visual indent
1890:39: E203 whitespace before ','
1891:13: E128 continuation line under-indented for visual indent
1892:13: E128 continuation line under-indented for visual indent
1893:13: E128 continuation line under-indented for visual indent
1894:13: E128 continuation line under-indented for visual indent
1895:13: E128 continuation line under-indented for visual indent
1900: D400 First line should end with '.', not 't'
1900: D205 Blank line missing between one-line summary and description
1950:73: E261 at least two spaces before inline comment
1950:73: E262 inline comment should start with '# '
1952:81: E261 at least two spaces before inline comment
1952:81: E262 inline comment should start with '# '
1953:81: E261 at least two spaces before inline comment
1953:81: E262 inline comment should start with '# '
1954:81: E261 at least two spaces before inline comment
1954:81: E262 inline comment should start with '# '
1955:81: E261 at least two spaces before inline comment
1955:81: E262 inline comment should start with '# '
1956:81: E261 at least two spaces before inline comment
1956:81: E262 inline comment should start with '# '
1958:81: E261 at least two spaces before inline comment
1958:81: E262 inline comment should start with '# '
1959:81: E261 at least two spaces before inline comment
1959:81: E262 inline comment should start with '# '
1960:81: E261 at least two spaces before inline comment
1960:81: E262 inline comment should start with '# '
1961:82: E261 at least two spaces before inline comment
1961:82: E262 inline comment should start with '# '
1963:76: E261 at least two spaces before inline comment
1963:76: E262 inline comment should start with '# '
1965:84: E261 at least two spaces before inline comment
1965:84: E262 inline comment should start with '# '
1966:84: E261 at least two spaces before inline comment
1966:84: E262 inline comment should start with '# '
1967:84: E261 at least two spaces before inline comment
1967:84: E262 inline comment should start with '# '
1968:84: E261 at least two spaces before inline comment
1968:84: E262 inline comment should start with '# '
1969:84: E261 at least two spaces before inline comment
1969:84: E262 inline comment should start with '# '
1971:84: E262 inline comment should start with '# '
1972:84: E262 inline comment should start with '# '
1973:84: E262 inline comment should start with '# '
1974:84: E262 inline comment should start with '# '
1975:84: E262 inline comment should start with '# '
1977:83: E261 at least two spaces before inline comment
1980:65: E261 at least two spaces before inline comment
1980:66: E262 inline comment should start with '# '
1981:65: E261 at least two spaces before inline comment
1981:66: E262 inline comment should start with '# '
1982:66: E261 at least two spaces before inline comment
1982:66: E262 inline comment should start with '# '
1989:75: E261 at least two spaces before inline comment
1990:75: E261 at least two spaces before inline comment
1991:75: E261 at least two spaces before inline comment
1992:70: E261 at least two spaces before inline comment
2007:15: E128 continuation line under-indented for visual indent
2008:15: E128 continuation line under-indented for visual indent
2009:15: E128 continuation line under-indented for visual indent
2010:23: E211 whitespace before '('
2023:13: E122 continuation line missing indentation or outdented
2024:13: E122 continuation line missing indentation or outdented
2025:13: E122 continuation line missing indentation or outdented
2029:13: E122 continuation line missing indentation or outdented
2030:13: E122 continuation line missing indentation or outdented
2031:13: E122 continuation line missing indentation or outdented
2051:36: E225 missing whitespace around operator
2053:36: E225 missing whitespace around operator
2080: D400 First line should end with '.', not ','
2080: D205 Blank line missing between one-line summary and description
2092:37: E225 missing whitespace around operator
2092:86: E225 missing whitespace around operator
2104: D400 First line should end with '.', not ','
2104: D205 Blank line missing between one-line summary and description
2116:37: E225 missing whitespace around operator
2116:86: E225 missing whitespace around operator
2130:5: E303 too many blank lines (3)
2130: D400 First line should end with '.', not ','
2130: D205 Blank line missing between one-line summary and description
2142:37: E225 missing whitespace around operator
2142:86: E225 missing whitespace around operator
2154: D202 No blank lines allowed *after* method docstring, found 1
2154: D400 First line should end with '.', not ')'
2164:21: E126 continuation line over-indented for hanging indent
2167:26: E225 missing whitespace around operator
2203:9: E122 continuation line missing indentation or outdented
2204:9: E122 continuation line missing indentation or outdented
2205:9: E122 continuation line missing indentation or outdented
2206:9: E122 continuation line missing indentation or outdented
2207:9: E122 continuation line missing indentation or outdented
2208:9: E122 continuation line missing indentation or outdented
2209:9: E122 continuation line missing indentation or outdented
2210:9: E124 closing bracket does not match visual indentation
2213: D401 First line should be imperative: 'Print', not 'Prints'
2213: D400 First line should end with '.', not 'w'
2213: D205 Blank line missing between one-line summary and description
2235:15: E127 continuation line over-indented for visual indent
2235:109: E502 the backslash is redundant between brackets
2237:16: E127 continuation line over-indented for visual indent
2239:48: E225 missing whitespace around operator
2239:67: E225 missing whitespace around operator
2243: D401 First line should be imperative: 'Print', not 'Prints'
2243: D400 First line should end with '.', not 'w'
2243: D205 Blank line missing between one-line summary and description
2265:72: E221 multiple spaces before operator
2266:16: E127 continuation line over-indented for visual indent
2266:82: E502 the backslash is redundant between brackets
2266:44: E225 missing whitespace around operator
2266:63: E225 missing whitespace around operator
2270:81: E221 multiple spaces before operator
2271:20: E126 continuation line over-indented for hanging indent
2271:86: E502 the backslash is redundant between brackets
2271:48: E225 missing whitespace around operator
2271:67: E225 missing whitespace around operator
2275:79: E221 multiple spaces before operator
2276:20: E126 continuation line over-indented for hanging indent
2276:86: E502 the backslash is redundant between brackets
2276:48: E225 missing whitespace around operator
2276:67: E225 missing whitespace around operator
2280:16: E127 continuation line over-indented for visual indent
2284: D401 First line should be imperative: 'Print', not 'Prints'
2284: D400 First line should end with '.', not 'e'
2284: D205 Blank line missing between one-line summary and description
2311:15: E271 multiple spaces after keyword
2313: D202 No blank lines allowed *after* method docstring, found 1
2313: D400 First line should end with '.', not 'e'
2313: D205 Blank line missing between one-line summary and description
2351: D400 First line should end with '.', not 'r'
2393:78: E251 unexpected spaces around keyword / parameter equals
2393:80: E251 unexpected spaces around keyword / parameter equals
2394:78: E251 unexpected spaces around keyword / parameter equals
2394:80: E251 unexpected spaces around keyword / parameter equals
2395:79: E251 unexpected spaces around keyword / parameter equals
2395:81: E251 unexpected spaces around keyword / parameter equals
2396:55: E231 missing whitespace after ','
2396:78: E251 unexpected spaces around keyword / parameter equals
2396:80: E251 unexpected spaces around keyword / parameter equals
2404:22: E222 multiple spaces after operator
2439:9: E303 too many blank lines (3)
2502:34: E126 continuation line over-indented for hanging indent
2505:102: E502 the backslash is redundant between brackets
2505:77: E225 missing whitespace around operator
2505:96: E225 missing whitespace around operator
2510:98: E502 the backslash is redundant between brackets
2510:73: E225 missing whitespace around operator
2510:92: E225 missing whitespace around operator
2534:25: E127 continuation line over-indented for visual indent
2534:37: E203 whitespace before ':'
2535:37: E203 whitespace before ':'
2536:37: E203 whitespace before ':'
2537:37: E203 whitespace before ':'
2538:37: E203 whitespace before ':'
2539:37: E203 whitespace before ':'
2544:24: E261 at least two spaces before inline comment
2549:16: E127 continuation line over-indented for visual indent
2576:52: E126 continuation line over-indented for hanging indent


1: D290 White spaces around docstring should be trimmed.
2: I102 copyright year is outdated, expected 2015 but got 2014
277:23: E203 whitespace before ':'
278:26: E203 whitespace before ':'
279:28: E203 whitespace before ':'
280:27: E203 whitespace before ':'
281:24: E203 whitespace before ':'
286:23: E203 whitespace before ':'
287:26: E203 whitespace before ':'
288:28: E203 whitespace before ':'
289:27: E203 whitespace before ':'
290:24: E203 whitespace before ':'
298:23: E203 whitespace before ':'
299:26: E203 whitespace before ':'
300:28: E203 whitespace before ':'
301:27: E203 whitespace before ':'
302:24: E203 whitespace before ':'
347:28: E222 multiple spaces after operator
356:22: E203 whitespace before ':'
368:48: E203 whitespace before ','
368:49: E231 missing whitespace after ','
376:16: E231 missing whitespace after ':'
389:16: E231 missing whitespace after ':'
496:16: E126 continuation line over-indented for hanging indent
502:58: E203 whitespace before ','
562:15: E126 continuation line over-indented for hanging indent
598:17: E203 whitespace before ':'
599:22: E203 whitespace before ':'
600:20: E203 whitespace before ':'
601:18: E203 whitespace before ':'
602:24: E203 whitespace before ':'
603:22: E203 whitespace before ':'
604:19: E203 whitespace before ':'
605:20: E203 whitespace before ':'
606:23: E203 whitespace before ':'
607:18: E203 whitespace before ':'
608:17: E203 whitespace before ':'
609:19: E203 whitespace before ':'
610:20: E203 whitespace before ':'
611:21: E203 whitespace before ':'
612:19: E203 whitespace before ':'
613:19: E203 whitespace before ':'
614:20: E203 whitespace before ':'
615:17: E203 whitespace before ':'
616:24: E203 whitespace before ':'
617:23: E203 whitespace before ':'
618:21: E203 whitespace before ':'
619:37: E203 whitespace before ':'
633:4: E131 continuation line unaligned for hanging indent
662:1: W391 blank line at end of file


It would also be nice to add a check on $wxWidgets_CONFIG_EXECUTABLE --version that ensure compatibility with the WX28_API option


Many thanks!


cool man


chur restarted with a different kernel yesterday, could be related to this.

@eugeneia can help you get the test working there perhaps?


(Good idea about setting `PACKET_CSUM_VALID` btw!)


Yeah! Thanks!


Build is still broken. Please see http://ci.cgeo.org/job/c-geo/3219/console
Build was first broken at http://ci.cgeo.org/job/c-geo/3129/


Should use `rose_arch` consistently within the documentation.


Remove `Python` here. It is a Rose built-in application.


`at` instead of `as`?


I would recommend adding this batch update as extra activation step. It's much better than to be stuck on same page without knowing what's happening for some period of time. Even, if you split query/updates into batches, you still need to find right number per batch (considering shared hosting resources, etc).

Regarding extra step:
* Store some kinda flag in option, to check if post were updated.
* Add sub-page to "Tools", you can display or hide it based on that flag.
* Create the page that handles batch updating posts. Check this one for example - https://github.com/thomasgriffin/tgm-batch-updates/blob/master/tgm-batch-updates.php.
* You can redirect users to this page after activation or just document extra step in readme (but end-users usually don't read those).


Shouldn't it be  ```indexes.put("dichroicIndex", d);```


Thank you. You right, test configuration hard-coded right now, I will configure to run tests on CI (Travis or AppVeyor) asap.


It was firewalled to single IP for this account


@mcostalba Ok, got it.


Let me disagree with you; when coding with C# (and alike) importing whole module is commonly used. So why this should not be done here also?


Logic from template doesn't work after first change of *this.labelNode.textContent*.
As far as I understand, this is because the code, generated by Template, tries to update *nodeValue* of the text node,  added into *labelNode* in the time of DOM creating:
```javascript
var c2 = this.labelNode = register.createElement('span');
...
var c2c1t1 = document.createTextNode('');
c2.appendChild(c2c1t1);
...
if('checked' in props || 'checkedLabel' in props || 'label' in props)
   c2c1t1.nodeValue = (this.checked && this.checkedLabel ? this.checkedLabel : this.label);
```
However, after change of *this.labelNode.textContent* this node already doesn't exist and reference *c2c1t1.nodeValue* isn't valid.


I'm glad to see this. That part of the video had made me a bit nervous. ;)


What is difference between caf and non-caf?


Please add your own name here, as I haven't contributed to that file. Also, could you add a comment with the license (probably LGPL?)?


This should also be done for GenericReferenceTest and DetectorSettingsDetectorTest.
@emilroz: I am happy to make the changes.


jo sage ja immer deutsch wahr ich immer schlechter als in englisch, darum frag ich ja,
fand es nur so sperrig als ich es beim spielen gelesen habe, zwar positven kommentar aus Freundeskreis erhalten, dass es nun auf deutsch ist aber es hat mir missfallen^^


I just realize it's made for both Linux and Darwin

...


unclosed tag


due to the loss of readability from this, maybe this change should only be enabled when --single-line-screen-kwargs (make it --single-line-kwargs or something) or --comparable is enabled.


@shiftkey okay, understood. Next time, just shoot me (or any *Git for Windows* developer) a message; I do not want to cause you gentle people unnecessary churn.


Good point, have you seen @mistotebe's [python3 branch](https://github.com/mistotebe/ledger/commits/python3)?

We're close to having Python 3 support for the Ledger module, but aren't quite there yet.
If I remember correctly importing ledger from Python 3 works fine, but `ledger python` has some issues
in `hack_system_paths()`


Differently than for Combobox, here's deliteful/Select with vertical-align: middle removed:

![image](https://cloud.githubusercontent.com/assets/1583981/5626368/b89b0a50-958a-11e4-810b-410e290b77d2.png)

instead of the current result:

![image](https://cloud.githubusercontent.com/assets/1583981/5626425/76f99dcc-958b-11e4-9fd1-98635f767a9e.png)

This holds at least for Chrome, FF and IE11 / Win7.
That is, with this settings removed, we don't get a baseline alignment of the text inside the widget, but a bottom alignement of the root node of the widget - and it doesn't look that great, isn't it? I'm not sure how I could change the CSS such that I get baseline alignment with the text inside the inner native select. Would you have an idea? I've extracted it as pure HTML/CSS here: http://jsfiddle.net/adrian_vasiliu/aet207dy/

> This reinforces my opinion because I think baseline alignment should be the default.

So, besides the general philosophical aspect, it seems we need to be careful about different impact of this change that might hold for some widgets/browsers (the picture looks a bit different in IE11 at least for Combobox). So if we'd want to go this way consistently for Combobox, Select, Button, ProgressBar, ProgressIndicator, Slider, ToggleButton and sublcasses, we'd need to carefully test the impact for each (ideally on all browsers since there can be differences of behavior).


Code_Cleanups (DeadParrot) - x86_64-MacOS-10.9-clang: Tests Failed

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


Build is still broken. Please see http://ci.cgeo.org/job/c-geo/3220/console
Build was first broken at http://ci.cgeo.org/job/c-geo/3129/


Похоже ты не используешь эти 2 функции, но идея их заиспользовать хорошая!


coding style nits:
 i2c->dir = 1;  // for use PMIC I2C.


Название совершенно непонятное☺


gonna add that


@dscho sure thing, I'd love to keep in touch (I need to give some time to look over the v2 changes). ping me on whatever address is suitable - [my handle] at github dot com


For what reason it may return NULL?


this file awfully seemed familiar [to me](https://github.com/ahmetalpbalkan/Docker.DotNet/blob/master/Docker.DotNet/JsonSerializer.cs) :)


selon moi le thread.sleep permet de faire dormir le thread ajax, mais à condition que l'appel ajax soit effectué à l'infini, sinon c'est inutile...


IDFXT (Unknown) - i386-Windows-7-VisualStudio-12: Build Failed

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


I'm seeing both "mt_*" and "mtk_*" in your file names. Is there some special reason? Otherwise we should just unify the naming rules - always mtk_*.


la donnée "5" attitrée au paramétrage "frequency" est en seconde ? ou en nombre d'appels ?


Basically we can revert on a PR and if Travis doesn't error on JRuby we should be good.

One of the failing builds was https://travis-ci.org/fog/fog/builds/45783030

If I restart it and they pass we'll probably get the same feedback... (starting)


Coregister DEM A to DEM B (master DEM)


It's not ideal but I think it would be best to use an `ng-click` that calls a method of the main controller. In this way we avoid using element selectors in the js code. Would that work?


This turns into a general discussion. Every sensor has its own noise characteristics. You could generalize it, but to me it seems more suitable to model each sensor individually.


Ah, fair point - thanks for answering!


Usually we prefer to make sure every commit won't break build system. Since the GPIO and I2C drivers are provided later, I'd recommend to leave this board_setup as empty (with a comment as TODO) instead of using unavailable function calls.


@michalc you are right, anyhow, this does not change the nature and will wait for an answer to https://github.com/angular/angular.js/issues/10635#issuecomment-68642139 before moving forward


you should read this

http://docs.travis-ci.com/user/how-to-skip-a-build/


TESTS PASSED
 Mr.Roboto url : http://jenkins.plone.org/roboto/get_info?push=bbd5401e55724a6e80b2234430aa99ba
 plone-5.0-python-2.7 [SUCCESS]


@shiftkey alright!


This is what you can see with FF:
![ff_not_well_formed](https://cloud.githubusercontent.com/assets/5304821/5626680/6cbe0382-9597-11e4-8875-a2ab02e6ccac.gif)
Problem disappears if ampersands are changed by corresponding entities.
``` && ``` works anyway. So, if you think, that it isn't important, I can remove these changes.


Wait, 3.4 works for Julia 0.3.x. I guess it would be good to state it as long as it's the stable series.


In general we encourage using enum instead of #define for constants.

Can you change these #define to enum?


Jeg kiggede på testen og jeg blev imponeret over din kreativitet i forhold til at detektere cache misses, og så dryssede jeg en frisk `[Ignore]`-bandit på testen, og voilá! ![green check mark](http://www.slgu.org/Images/site/tick.png)


@domcleal - fixed in edaf4b


LGTM


unclosed tag


We hadden afgesproken geen minified source te includen. Nu werken de sourcemaps niet.


Mostly it comes down to trace things back to where it happened (Eg: from the framework displaying the wrong value back to libril)

Fixing native code is actually not so hard as you can just recompile parts of the system and restart the daemon using the library.

Eg: to fix ril, it is enough to re-compile it with 'mm', push it to the device and restart rild


I had just moved the code, i haven't changed the constants


Hey Attila,

I would love to use your tool but IFAIK it is not usable under MAC OS X, even it passed 2 years since it was released. Here's my original post about it http://forum.kodi.tv/showthread.php?tid=149658&pid=1349656#pid1349656  There are at least 4 KODI skinners using OS X, AFAIK.

I just don't have a time to fiddle with this manually. Anyhow, I will renaming the folder, that one is easy.


Yep. With the newer version of gems getting pulled down, those builds pass.

I'll revert this change now.


....men jeg er helt klart modtagelig overfor at genindføre intelligens omkring eager load af events - jeg satte mig ikke ind i hvad din implementation havde gang i, men man kunne måske med fordel benytte noget lignende det, som computere gør når de læser fra disk, hvor der altid indlæses flere KB til RAM uanset hvor lidt man er nede på disken efter.


Actually source has been updated to allow usage of both sampling rates


The code sample for the creating a service has misaligned ``` chars


yep :) I examine your repo for some practices. I have to put reference links.


ads


not really, you don't need to do that. :)


@adz ooops yes it is, thanks for spotting this :)


1) Changes for supporting View API - submit a document via public url.
2) Removed unused imports
3) Content API - Upload pre-flight implemented.


...men ja, jeg tror at #21 er vejen frem :) og nej, jeg er ikke sikker på at jeg har fantasi til at forestille mig en fornuftig API.

En ting tror jeg at jeg er sikker på, og det er at event-processerings-profileren skal være bundet til `ViewManagerEventDispatcher` - altså på den måde at vi ikke skal forsøge at tænke noget generisk, men bare tænke på hvilke info vi kan suge ud af det nuværende view-system.


fix indents


But I confirm that you have to convert these values to decimal if you want this to work. I did it here https://github.com/libretro/retroarch-joypad-autoconfig/commit/8bc0547aba7829760dc3358cb8fa490e611e704f so it's done. To check if it works, you can delete the *input_device* key, and see if it match. I tested with some other gamepads.


setbits_le32(MTK_WDT_MODE, (MTK_WDT_MODE_KEY | MTK_WDT_MODE_EXTEN) | (mode ? MTK_WDT_MODE_AUTO_RESTART : 0))


Why would I skip this build?


Please add a comment of reference for why we need to delay here.


体裁をbootcampの「Git Manual for Windows」に合わせる。
``` Generateボタン ```  ⇒ ``` [Generate] ボタン ```


PowerOps *pass_through


Could we use `$this->updateKeys` instead to generate a suitable list of keys? I'm uncomfortable with traversing the object and assuming which properties we want.


You are the best :-)


同じく、``` Save praivate key ``` ⇒ ``` [Save praivate key] ```


```setting → SSH kyes → Add SSH key で公開鍵``` ⇒ ``` [setting] → [SSH kyes] → [Add SSH key] で公開鍵 ```


The problem is that if you multiple test a patch, due to how statistic
work, sooner or later it will pass, no matter if good or bad.

That's why we try to limit the number of attempts on a specific topic to
just a few, otherwise our SPRT testing system is no more reliable.

So it is not because I don't want you to test, but because to consider the
test result valid, few attempts at max should be done.

On Tue, Jan 6, 2015 at 8:27 AM, rohanryan <notifications@github.com> wrote:

> Hi Marco,
>
> It was my first attempt at contributing, so may not have made optimum use
> of FishTest so far. My apologies.
>
> I have two "Yellow" results so far.
> Total: 64025 W: 10836 L: 10630 D: 42559 sprt @ 60+0.05 th 1
> Total: 103449 W: 20945 L: 20765 D: 61739 sprt @ 15+0.05 th 1
>
> There is more than one parameter to tune in the code and I do not think I
> have achieved anywhere near what is possible.
>
> Parameter 1) When a Quick move is made, how to use the saved time? I've
> added code to allot time to the next move. Need to identify what is
> optimum
> time to use on next move. (Half the saved time, all the saved time, 3/4th
> the saved time?)
>
> Parameter 2) How much time to spend searching for 2nd best move. (To what
> depth to search?)
>
> Parameter 3) When to play a Quick Move? When the best move score is 2
> pawns
> better than 2nd best?
>
> I think with Ponder On, a measurable ELO gain will come from Quick move
> code. But, I don't know of a way to test this. Does FishTest support
> testing with Ponder On?
>
> What is the optimal way to tune for multiple parameters like this? Should
> I
> use the SPSA feature?
>
> I will limit the test runs to 20,000 games & sprt @ 15+0.05 th 1 and keep
> the priority low. (What priority do you suggest -3?)
> Please consider letting me pursue this till I am convinced no further
> gains
> are available.
>
> Regards,
> Rohan
>
>
>
>
> On Tue, Jan 6, 2015 at 12:14 PM, Marco Costalba <notifications@github.com>
>
> wrote:
>
> > You are now starting to overtune this series: already 5 tests on the
> same
> > topic. Please consider changing topic.
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/rohanryan/Stockfish/commit/820a793530495825ffd3548a634b3fdb8ac74bd1#commitcomment-9164938>
>
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rohanryan/Stockfish/commit/820a793530495825ffd3548a634b3fdb8ac74bd1#commitcomment-9165173>
> .
>


Is there any reason to have an intermediary `PATCH_CONTENT_TYPE` const?


We prefer to put public function usage comments in *.h files instead of C files in Depthcharge.


Should we use the layer id or make the name unique ?


Hey @arturoc , just tested on Windows / OpenGL 4.5 and the #ifdefs resolve properly. All good.

@procedural I'm inclined to side with Arturo on this issue. Since latest Ubuntu appears to have the most current GLEW version included, you're getting the best of both worlds anyway.

I think a design guidance in such cases could be that openFrameworks should be easy to compile for beginners, whilst advanced programmers (or those with up-to date systems) should be able to get pro features without much hassle, something this PR incorporates.


а надо, да? то есть мы хотим возвращать сразу два масива  - состояния и скрытые состояния?


Please remove these commented dead code.


Wow thanks @Absentee23!! I've fixed it now in the latest build :+1:


Small typo: "in in" should be just "in"


ditto - remove commented dead code.


Never mind, I see it now :)


It is encourage to use inline instead of define.


But i see not immediatly available. Was eager to test it :smile:


Can't this be a static or public function?
Please avoid using #define.


r=huonw p=10000


now probably we can use our audio hal instead of LegacXperia's audio-hal
https://github.com/sirmordred/android_hardware_qcom_audio-caf/commit/7699da2ef3b0a2fcefc7e62c8eef5bc2e31f528b


No, I mean something that doesn't explicitly take strings, but could for
example calculate distances between strings were it given a custom function
to do so. I don't have concrete examples, but we should perhaps anticipate
that things are being used in circumstances beyond their docstrings'
specifications (just as some were used for >2d)

On 7 January 2015 at 10:54, Andreas Mueller <notifications@github.com>
wrote:

>  Hum.... so you mean an estimator that takes strings as input, which is
> the skearn.feature_extraction.text module. That doesn't use check_array.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/amueller/scikit-learn/commit/2c54c5e409a3fc700c88bf93f06d1a734555e213#commitcomment-9177697>
> .
>


s/Infludb/Influxdb/ (though if I were being super nitpicky, it's apparently "InfluxDB")

Otherwise LGTM.


Are these the same URL?


I believe no. Simply installing & running the server is enough to update .c9/project.settings, which then shows up in git as changed. The pull request just changes .c9/* to /.c9/ which I perceive to have the same expected impact (exclude all of .c9). Will see what killing /project.settings does once nodemon/EMFILE is fixed on c9.


I am experiencing huge differences between     "https://github.com/nohros/nsPopover.git#62c928bc66dc98cacb61310e9a1463469848f4f1"

and this branch. I am happy to see setDefaults back, but my embedded directives are not parsing when I use this latest master.


I want to keep all the implemented methods together, which is why I moved it.


Cheers!

On Tue, Jan 6, 2015, 6:29 PM Mahmal Sami <notifications@github.com> wrote:

> Thank you for your PR @leif81 <https://github.com/leif81> .
> Don't hesitate to comment if the script didn't match your requirements,
> and don't hesitate to send any improvements.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/leif81/migrate-github-gitlab/commit/a8122afa222c61ead29ad40885795a32f35686ff#commitcomment-9177407>
> .
>


Hmmm no explicit imports. With all the clones/copys/crazyness I highly recommend http://stackoverflow.com/a/147461 those namespaces include a ton of names... I recommend staying out of Jar-Hell.


I thought this was cleaner and easier to read. It is not used in a future commit either :)
I'll take it out.


I just realized I need to fix these, I don't believe we ever *officially* added the sys-hack.


Should we also switch this one now?


Ah, I see what you mean now.... that is... tricky...
(concrete example might be string kernels on an SVM with a callable)
Do you have any ideas how to handle this?
We could "try" and not fail. That might still break things if you pass strings that could be converted to float.
There  are also issues with what to do with ``y``.


For SPSA sessions, you need to test this branch against itself, not against master.


ok removed.


You would be better to have a "GetById" method generally rather than a long if/else tree.


@caitp: feel free to comment on which branches you want or just cherry pick the patches.


I made garbage!


The only problem you may have with this, is that you may want to search titles within a genre.


yep. It's not necessary to include the hostname at all since both urls (the url we link to and the url we put in the return_to param to redirect to after signing in) are on the same host, so I just removed the hostname instead of changing it to use the new method.


Thanks. Fixed in 51f0daab2a54ac545288f9e912616765ef6f29bc


Generally speaking, you would want to initialize these in a constructor (Especially since when you move to using DI, you will be setting them in the constructor anyway).


Overall looks good. I'm not positive if everything is related to the canonical_url change/update.


the doc-only commits should probably be [ci skip], or at the very least [av skip]


Thanks.  How do you test the recorder?


Can you remove this extra duplicate line please.


Correct the file name.


You can accept an Int as the parameter for the action instead of parsing it here.


Add the correct date and your name if this is new code (or is it moved from another file)?


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1091 of 1091 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)


Ah, yes.  Forgot about that.  Even travis is pretty backed up today.


r-, see https://github.com/rust-lang/rust/pull/20662#issuecomment-68958509


Can you remove this line given it's no longer true.


Yes.  John merged the change I made in my fork into the Khan fork.  And the HEAD is attached now.


It looks good to me, although due to recent changes, some merge conflicts will definitely need to get taken care of ...


i had it like that before, but it meant I had GetMovies, GetMoviesByTitle, GetMoviesByGenre, GetMoviesById which felt super repetitive... are you saying a combo is better? ie GetMovies(title, genre) and GetMoviesById?


The protoc here should be $(PROTOC) I believe, in case anyone changes it.


This is almost correct. The problem here is that there are different number of asterisks for the over- and under-lines, which is not valid ReST syntax for heading markup.


what was on that partition originally? Kernel2? I actually did something similar, but I used /efs. But I like the idea :) Does it make your kernel work with jb and kk?


Generally speaking, you create a base class called "GetById" so you don't have to implement it each time, and then you create a a base class for your models that always enforce an integer ID. Hold on, I'll create something for you.


To keep in line with the other files, I'll change it back to asterisks then.


And the parallelization begins! What's your end goal with SCARLETT?

Btw, did you know that Tony made something called HOMER and PEPPER (a v2 and v3 of JARVIS respectively)?

```
mind.blown = true
```


Status bar quick settings pulldown fix, not clock.


@ajoslin Did you really mean to get rid of the card margin? According to [the spec](http://www.google.com/design/spec/components/cards.html#cards-usage) it should have an 8dp margin and the card content should have 16dp padding:

>Card gutters on mobile
>
>Padding from edge of screen to card: 8dp
>Gutters between cards: 8dp
>
>Content padding
>
>16dp


Good q. I don't actually use live-editor demo out of this repo, so I don't recall if there's a record button enabled for it. I've just tested it out of our local app and it works fine.


That builds in Mingw/Ubuntu for me, and OS X. Still need to work on a Mingw64 toolchain.

Changes here and in the other commits look good. Minor item - I suggest renaming CHECK_CFLAG to ADD_CFLAG_IF_SUPPORTED (or similar) - to make it more evident that the macro has a side effect.


NewVSHPWH (shenb) - x86_64-MacOS-10.9-clang-Debug: OK (1580 of 1580 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)


Its aweaume to watch you work wish I had the knowledge..


@PabloCastellano secp256k1 uses package config, so this wouldn't be the proper technique for locating its installation.


there is no longer any way to see what branches the pull requests which were closed were using. The PRs in question were #1932, #2004, #2010, and #2080

If you can provide the branch names for these, or re-open pull requests, we can certainly look at them.

I understand that it's frustrating when long periods of time go by without PRs being merged or commented on, but you can always ping us and we will get the message and take another look. Sorry if I seemed mean or anything, that was not my intent =)


@andreychernih Since hashes respond to `each` this change breaks the rendering of hashes. (They are now converted into multi-level arrays.)


+INSERT INTO `item_mods` VALUES(11146, 484, 10); -- WAS ALREADY IN NOT SURE WHAT THIS IS
=
MOD_AUSPICE_EFFECT	          = 0x1E4, // Bonus to Auspice Subtle Blow Effect.
to lazy to erase the not sure what it is thing  lol


`in_array(@$_SERVER['REMOTE_ADDR'], explode(',', @$_SERVER['SYMFONY__TRUSTED_HOSTS']))` would be `true` if neither `$_SERVER['REMOTE_ADDR']` nor `$_SERVER['SYMFONY__TRUSTED_HOSTS']` is set, since it becomes evaluated to `in_array(null, array(""))` and without setting `$strict` to `true` when calling `in_array` there is  no type check.

I would prefer to check if `$_SERVER['SYMFONY__TRUSTED_HOSTS']` is set and fallback to the default list or maybe merge both arrays if `$_SERVER['SYMFONY__TRUSTED_HOSTS']` is set.

To make it more comfortable, what about removing whitespace before explode or after by `array_map('trim', explode(...))`?


r+


First Paint


Maybe no login button? Just change the keyboard submit button to say "Go" when pw box has focus? And "Next" when username has focus?

Also, I like "Sign In" better. Don't know why I used "Login" here.


Was removing the comment icon for specs intentional? I liked being able to tell them apart easily.


saw approval from jdm
at https://github.com/servo/servo/commit/bf54de870aad51018b921c0845b10906cdc800eb


merging servo/servo/rustup_20141221 = bf54de87 into auto


servo/servo/rustup_20141221 = bf54de87 merged ok, testing candidate = e3f3a862


This is pretty much a copy of ola-protoc.cpp, so not really worth changing IMO.


done


你格式化过一些文章的格式？


huh? what was re fixed here?


Resolves #3


Gonna move both textboxes and forgot password link up above the fold, so that the keyboard doesn't cover it and no need to scroll.

Also note: The forgot link should just open an email to support@bluefeedapp.com with subject "Help! I forgot my password!"


This was addressed in [6c756ba3e9f32804802ce1a0c0835db5483f3ad2].


some tests failed:
failure: http://build.servo.org/builders/android/builds/501


so what's more fragile, sourceforge or the url / filename combination in upstream homebrew?


The following text (lines 4336 through 4343 in this commit) still uses the original syntax with significant references about its exact look. Please change the following text as well.


See #102

Yes I agree, telling them apart easily was good.

Would you prefer the same icon again or perhaps a ruby icon with a different colour?


I can't reopen the same PRs because GitHub can't match the repositories to the previous PRs even if they have the same name, which they do. I had a PR for each branch I have here. The only way is to make new PRs...


hola


hps


Thanks for the PR. That makes sense.

I'm going to do some more testing to make sure it doesn't break horribly if those default env vars are not present on the system.


I tested this quickly with the example pages and a [Command-Line HTTP Server](https://github.com/bahamas10/node-httpserver).  I got this in console:

```
TypeError: undefined is not a function
    at draw (http://localhost:8080/ng-google-chart.js:246:38)
    at http://localhost:8080/ng-google-chart.js:253:29
    at C (http://ajax.googleapis.com/ajax/libs/angularjs/1.2.8/angular.min.js:92:375)
    at http://ajax.googleapis.com/ajax/libs/angularjs/1.2.8/angular.min.js:94:28
    at h.$eval (http://ajax.googleapis.com/ajax/libs/angularjs/1.2.8/angular.min.js:102:293)
    at h.$digest (http://ajax.googleapis.com/ajax/libs/angularjs/1.2.8/angular.min.js:100:50)
    at h.$apply (http://ajax.googleapis.com/ajax/libs/angularjs/1.2.8/angular.min.js:103:100)
    at http://localhost:8080/ng-google-chart.js:191:48
    at Ot.<anonymous> (https://www.google.com/uds/api/visualization/1.0/ff67c3772da186a412ae3231c32409e9/format+fr,default+fr,ui+fr,gauge+fr,corechart+fr.I.js:272:131)
    at Pt (https://www.google.com/uds/api/visualization/1.0/ff67c3772da186a412ae3231c32409e9/format+fr,default+fr,ui+fr,gauge+fr,corechart+fr.I.js:236:368)
```
Which points right here:
``` JavaScript
$timeout.clear(draw.recallTimeout);
```


Actually, now that you mention it, a green ruby would be nice!


I have to point out that removing the -g flag removes ~300KB from the final executable.


Please ignore the merging and fallback stuff. I think it is better to simple add another condition as it is. But the rest of my comment is still in effect.


`&:` isn't explained in this guide in it looks very weird to a stranger. Would it be possible to explain it here?


Doesn't it make more sense to call it arrows `arrow keys` instead of `cursors`?


Ah yes, near identical.


Great - this is the source of the exact problem I was having. I was about to submit a patch but I see you have already beaten me to it. I hope he merges it in soon as it's a simple fix to the default value.


This seemed way better than running a proxy to live-intercept requests, when we could just rewrite the string the requests are using in the first place.  Also, the URL they're downloading from hasn't changed since the first added the ability to specify custom bottle urls.  Finally, this should fail gracefully, since if it can't replace the URL with our own, Homebrew should still be able to use its default server.  (Unless a failure in the `sed` command causes the script to stop, but I don't think it should)


yes I know, that's what I meant. If you want, you can open new PRs for those branches, or alternatively you can identify the branch names for each one (although it's significantly harder to review code that way)


Maybe I'm missing the context and I know this edit was a bit too old to ask, but out of curiosity why only correcting this one in particular?

Other generators still use 'pass', in pretty much the same statement.
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/assets/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/generator/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/helper/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/integration_test/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/migration/USAGE#L2
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/resource/USAGE#L3
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/scaffold/USAGE#L6
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/scaffold_controller/USAGE#L3
https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/task/USAGE

Not sure which is grammatically correct.


as long as I remember to not replace the semicolon on that line with `&&`, yeah I think it should work?


You can update the Google.Apis, Google.Apis.Core and Google.Apis.Auth libraries to 1.9.1


Another geat bug catch which was also evident in my setup. i.e. in the default case of pam_filter not being set, the script returns all SSH keys defined in LDAP. Again, I hope this gets merged in quickly.


If no differences ignore.  Was moving a bit fast earlier and thought I upped the wrong one….

As long as the first enrty is this its ok:

                if (trade:hasItemQty(3115,8) and trade:hasItemQty(12013,1) and trade:getItemCount() == 9) then                         --head

                                player:addItem(11169);

                                player:messageSpecial(ITEM_OBTAINED,11169);

                                player:tradeComplete();

From: TeoTwawki [mailto:notifications@github.com]
Sent: Tuesday, January 06, 2015 6:33 PM
To: LegionXI/darkstar
Cc: Keegan Carr
Subject: Re: [darkstar] npcs/AF3_Trade_Moogle.lua re-fixed (8176416)

huh? what was re fixed here?

—
Reply to this email directly or view it on GitHub <https://github.com/LegionXI/darkstar/commit/81764168641f2887dd155411faa8e56b0385ee38#commitcomment-9178081> .


Yep, completely valid.


Break emulation on Android + warning


Yes, it's kernel2.


@vitaut This undid 2a95cc2aa46b2a2e2a8357b2f90f6df0feaa8f7a so I'm getting undefined references. What's the best way of preventing regressing this again?


Yup, I'm removing composite spoilers. 2 spoiler types cause too many problems.


Looks like you have a `:` separator instead of `,` after `'Undo'`


[optional] Sort usings


Oh, it's simple - if you installed mingw-w64, just configure like so:

CC=x86_64-w64-mingw32-gcc ./configure --host=x86_64-w64-mingw32


Remove extra empty lines here


This should really be an interface to be honest.... Not an abstract class.


I guess I'll just make news ones then. Though, you could just cherry pick the ones you want and wouldn't result in somehow duplicate PRs.


[optional] I should consider change the namespace to not include "_"s.
You should also consider using your your site name \ nickname - Daimto.
So in general (maybe in the next samples) consider changing your namespace to "Daimto.Google.Calendar"

Also I would not use Clndr. Calendar is much cleaner.


Tomorrow, I'll need some clarification of the liferay-ui:toggle's hideMessage, showMessage, hideImage, and showImage attributes. Thanks.


Job pr-scala failed for 92015082 Took 108 min. (ping @kanielc) [(results)](https://scala-webapps.epfl.ch/jenkins/job/pr-scala/9442/):

To retry exactly this commit, comment `PLS REBUILD/pr-scala@920150824022359d59c511398bb6f575d30ec90d` on PR 4233.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.


weird space issue. I think that by default in VS whenever you save a file it will auto fix space issues. What IDE are you using, if it's VS - maybe it's just a small thing that you need to configure


port_ingress1 and port_ingress2 are not defined here


one of the files in doc (describing --list=) mentions that the sequence of fields in --list=format-all-details is the same as in --list=formatdetails.
This is no longer true with your patch.


I would prefer to see await and async and this case and not using Task.Result


r+


Test


@tkelman Ah, sorry. I'll send a patch to David to avoid such regression in the future. For reference, what is the exact error that you get?


After saving an raft snapshot to disk, SaveSnapshot method should be called to record it. So WAL can match with the saved snapshot when restarting.


I don't think that you should catch here *general* Exception.
I don't think that you should catch an exception at all. It's a sample. The main service was filed to be created, in my opinion it's OK to crash.


If there is no snapshot, an empty snapshot should be passed in.


Looks good.


David - thanks. Let's discuss when c9 is working for us.

On Tue, Jan 6, 2015 at 7:04 PM, David Johnson <notifications@github.com>
wrote:

> I believe no. Simply installing & running the server is enough to update
> .c9/project.settings, which then shows up in git as changed. The pull
> request just changes .c9/* to /.c9/ which I perceive to have the same
> expected impact (exclude all of .c9). Will see what killing
> /project.settings does once nodemon/EMFILE is fixed on c9.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/xavid/mgt656-spring-2015-project/commit/db97afb1759327096a8b47e4c3d9f3e9397d16d8#commitcomment-9177798>
> .
>


I think I will change the docs then... any objections?


No.


nit: spaces after commas


It's when trying to link Ipopt to the libasl.dll I just built - it compiled fine, but doesn't have ASL symbols exported now. MinGW exports everything if you don't have any dllexport decorations, but here with just this one dllexport this becomes the only thing exported from the DLL. I could also use `-Wl,--export-all-symbols` but that can cause name collisions elsewhere. I'll see if I can find a way of checking for the exported symbols in Travis.

The full error is
```
[  219s] i686-w64-mingw32-g++ -shared -nostdlib /usr/i686-w64-mingw32/sys-root/mingw/lib/../lib/dllcrt2.o /usr/lib64/gcc/i686-w64-mingw32/4.9.2/crtbegin.o  .libs/AmplTNLP.o  ../../Interfaces/.libs/libipopt.dll.a -L/usr/lib64/gcc/i686-w64-mingw32/4.9.2/ -L/usr/lib64/gcc/i686-w64-mingw32/4.9.2 -L/usr/i686-w64-mingw32/lib -L/usr/mingw/lib -lasl -L/usr/lib64/gcc/i686-w64-mingw32/4.9.2/../../../../i686-w64-mingw32/lib/../lib -L/usr/i686-w64-mingw32/sys-root/mingw/lib/../lib -L/usr/lib64/gcc/i686-w64-mingw32/4.9.2/../../../../i686-w64-mingw32/lib -L/usr/i686-w64-mingw32/sys-root/mingw/lib /usr/lib64/gcc/i686-w64-mingw32/4.9.2/libstdc++.dll.a -lmingw32 -lgcc_s -lgcc -lmoldname -lmingwex -lmsvcrt -ladvapi32 -lshell32 -luser32 -lkernel32 -lmingw32 -lgcc_s -lgcc -lmoldname -lmingwex -lmsvcrt /usr/lib64/gcc/i686-w64-mingw32/4.9.2/crtend.o  -mms-bitfields -Wl,--exclude-libs=libintl.a -Wl,--exclude-libs=libiconv.a -Wl,--no-keep-memory -o .libs/libipoptamplinterface-1.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/libipoptamplinterface.dll.a
[  219s] .libs/AmplTNLP.o: In function `get_haltonerror_opt':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:925: undefined reference to `C_val_ASL'
[  219s] .libs/AmplTNLP.o: In function `get_int_opt':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:889: undefined reference to `I_val_ASL'
[  219s] .libs/AmplTNLP.o: In function `get_num_opt':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:871: undefined reference to `D_val_ASL'
[  219s] .libs/AmplTNLP.o: In function `get_str_opt':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:907: undefined reference to `C_val_ASL'
[  219s] .libs/AmplTNLP.o: In function `write_solution_file':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:771: undefined reference to `write_sol_ASL'
[  219s] .libs/AmplTNLP.o: In function `finalize_solution':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:670: undefined reference to `suf_rput_ASL'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:671: undefined reference to `suf_rput_ASL'
[  219s] .libs/AmplTNLP.o: In function `PrepareAmplForSuffixes':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1530: undefined reference to `suf_declare_ASL'
[  219s] .libs/AmplTNLP.o: In function `GetIntegerSuffixValues':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1557: undefined reference to `suf_get_ASL'
[  219s] .libs/AmplTNLP.o: In function `GetNumberSuffixValues':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1600: undefined reference to `suf_get_ASL'
[  219s] .libs/AmplTNLP.o: In function `ZN5Ipopt8AmplTNLPD2Ev':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:265: undefined reference to `ASL_free'
[  219s] .libs/AmplTNLP.o: In function `get_var_con_metadata':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:330: undefined reference to `var_name_ASL'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:338: undefined reference to `con_name_ASL'
[  219s] .libs/AmplTNLP.o: In function `Keywords':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1024: undefined reference to `WS_val_ASL'
[  219s] .libs/AmplTNLP.o: In function `get_options':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1386: undefined reference to `WS_desc_ASL'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:1456: undefined reference to `getstops_ASL'
[  219s] .libs/AmplTNLP.o: In function `ZN5Ipopt8AmplTNLPC2ERKNS_8SmartPtrIKNS_10JournalistEEENS1_INS_11OptionsListEEERPPcNS1_INS_17AmplSuffixHandlerEEEbNS1_INS_15AmplOptionsListEEEPKcSH_SH_PSs':
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:77: undefined reference to `ASL_alloc'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:93: undefined reference to `jac0dim_ASL'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:146: undefined reference to `pfgh_read_ASL'
[  219s] /home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver/AmplTNLP.cpp:100: undefined reference to `jac0dim_ASL'
[  219s] collect2: error: ld returned 1 exit status
[  219s] make[2]: *** [libipoptamplinterface.la] Error 1
[  219s] make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps/AmplSolver'
[  219s] make[1]: *** [all-recursive] Error 1
[  219s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/Ipopt-3.11.9/src/Apps'
[  219s] make: *** [all-recursive] Error 1
```


is this working?


@cprice404 @joshcooper I've opened https://github.com/puppetlabs/puppet/pull/3454 to add this back in.


LGTM


But we might then need to document the sequence of fields in --list=format-details!
Otherwise, you'd have to study the source code to find out what each column means.


fixed


if ur items are not showing run a binding.pry before this and check to see that there are actually items in the DB saved to that list.
also don't render this if items is empty :)


I think it might be ok to use the testimonials shortcode instead of prefixing it, since I think it is reasonable to assume that the user would be using just one testimonials plugin, also we could check if that testimonials exits as a shortcode already by checking the global $shortcode_tags array. See https://core.trac.wordpress.org/browser/tags/4.1/src/wp-includes/shortcodes.php#L89


delete this file and see what happens ;)


:tada:


Can you add the @since tag?


:no_bell: i think some of this could be tidied up with react's [classSet addon](http://facebook.github.io/react/docs/class-name-manipulation.html)


Aggregates blocked by buttercoin/engine#2 and API revision.


iOS大作业


А я думаю, чому оно на крауте не работало.


You forgot to update second condition! It is len_b still.


Is it possible for me to set up the local app on my machine to test this kind of stuff before pushing?


We could add a columns header to format-details. I thought about that several times in the past.


This was just an update on the about me section. Forgot to add that in my commit. Oops :P


Do not leave debugging code!


Thanks, was fixed already in bugfix branch


Why is the annotation support aborted? I love this function :(


make a change


With a header you'd be sure you pick the right stuff with `../run/john --list=format-details | cut -f1,14 | head -1`


This doesn't appear to be working for me on WAMP 64-bit. It still says a recent post was 8 hours ago.


No, unfortunately, it's not open source. I think Record theoretically works
locally, I just haven't tinkered with the demo in a while.

On Tue, Jan 6, 2015 at 5:10 PM, Kevin Barabash <notifications@github.com>
wrote:

> Is it possible for me to set up the local app on my machine to test this
> kind of stuff before pushing?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Khan/live-editor/commit/2d3381d6e4b91627eb92d541811d22ab7d99a77f#commitcomment-9178366>
> .
>


Ooh, that's cool.


Then again, that could possibly break some script out there...


But you would break existing scripts;)


I won ;-)


The example is never fixed in the rest of the guide and it's not very clear how to do it. Perhaps all the numeric types implement some common trait we can use? But it's not obvious which one is it.


It is 02:16 AM here, time to get some sleep.


We could output the header to stderr... but it could be confusing.


Yeah I think I'll leave this until tomorrow


i think it'd be better to just assign this to a `var` in the `render` function, since it only appears to be used there.  react doesn't really want you to define props anywhere but in the `getDefaultProps` method and by passing them in.  Not that it would happen in this case, but _if_ this component were to be re-rendered with a different thingId, this would get out of sync (you'd have to re-calculate it in the `componentWillReceieveProps` method).


I managed to solve the immediate problem of using the built-in counters
associated with captions more or less along the lines you suggested —
doing some of the work in the EnvionmentBlock processor and the rest
in the HTML backend.

 I’m happy with it as it is, but would be nice
to have the ability to register changes in the references
map if we need it.

> On Jan 6, 2015, at 2:10 AM, Dan Allen <notifications@github.com> wrote:
>
> It looks like you are hitting a problem in Asciidoctor core. The :ids table is overwriting any existing entry with the same id value. Ideally, it should only write if a key does not already exist. Otherwise, there's no way to prevent it from clobbering the entry. Here's are relevant lines:
>
> https://github.com/asciidoctor/asciidoctor/blob/master/lib/asciidoctor/document.rb#L535-L539 <https://github.com/asciidoctor/asciidoctor/blob/master/lib/asciidoctor/document.rb#L535-L539>
> We could fix this in 1.5.3. Perhaps we should add an "overwrite" parameter as the third argument to the register method which will overwrite an existing key if true, but default to false. wdyt?
>
> Btw, the hack to work around this issue (if you really don't want to wait) is either:
>
> a) maintain a separate key in the references table, then merge those entries into the :ids key in a Treeprocessor
> b) assign a custom Hash implementation to the :ids key that prevents keys from being overwritten (isn't Ruby grand?)
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/jxxcarlson/asciidoctor-latex/commit/5fae8d8273426423669420d125bb2b53949dc4e5#commitcomment-9165076>.
>


https://2ch.hk/test/res/80941940.html
https://2ch.hk/cc/res/75674.html
Например.


does this have the same bad behavior that the other place you're doing this has?


great work!


Yeah, good catch. A lot of my key / id generation code is scattered. I'll do a cleanup round on all of that for consistency.


Nope - apparently because this is the top level element, I can do it with props.


Gonna make a question here, because curious, and I wouldn't mind a response.  Was the separation of everything to individual lines just for readability, or was there legitimate purpose for this?  (Extra line breaks, extra spacing and white space, add to the file size, and that's my only question on this)


Robo looks like a nice tool but in order to use the github release feature, we would need to pull in additional tools and all of that is probably not worth the effort for ... a versionnumber.

>If no one else finds it useful than im fine omitting it, if that is what you are suggesting @julianseeger

That was my conclusion, yes. It's nice to have the version printed but a ```composer show -i``` does the job, too.


Privacy wise, elements won't protect you here..


Removing this line, killed the async-data example.


develop (lefticus) - Win64-Windows-8.1-VisualStudio-14: OK (331 of 331 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)


Goddamn Xcode removing indenting *curses*


Sorry I made a mistake here.   :(
The original code is correct. I have deleted the change of the bit operator.


Usually updates return the number of rows updated. That's not possible for views... but then, updates aren't really feasible for views anyway. So should update live here?


Why not a protocol?


@tkelman Thanks. I've reapplied the change in https://github.com/ampl/mp/commit/df77c5b48888d7cb2d5d7d6ab8eda791dbaac4dc and sent it "upstream".


I don't think it makes sense for a testing mock to inherit from a class that does per-profile database storage…


`DatabaseAccountProfile`?


Great, thanks, I'll send across a PR to check for the exported symbols if it works in testing.


r=huonw p=1


Wait, actually now I'm not sure what the purpose of `BaseProfile` is. Could you explain and add a comment?


Change the default here as well.


will need the mingw64-x-gcc cross-compiler in `$PACKAGES` to install before running cmake, which comes from a ppa


On my Ubuntu system the `ldap.conf` file is in `/etc/ldap.conf`. Is there a simple way to have the script look in both places and have one take precedence?


rax retry tests


Is a `BrowserDB` cheap to create?


I see a pattern forming here!


Looks like a good start!


I had already re-merged it back in to the Q1--2014 branch...


Oops, indeed. Thanks!


Should 10 seconds be a named constant somewhere?  It's hard to tell what it's for by reading the code here.


sever => server


If it blocks the thread, perhaps it should be called Run()?


Wasn't much of an optimization anyway.


see berkshelf/vagrant-berkshelf#249 for a fix


I assume this is a GET.  In that case, we should probably update the comment to indicate that this handles GET methods as well, even if it just ignores them.

Also, should you ignored all GETs rather than just ones for /favicon.ico?


This should probably be fixed some time. It still exists.


Hello CodePath


Look great, thanks


I keep seeing these three lines over and over.  Should we make it a function or method, like:

httpError(http.StatusBadRequest, "Invalid path: " + r.URL.Path", w, c.db)


:+1:
i am also meet this issue.


Well, it looks like it is still there, so I'll get back to work on improving the probabilities module.


Similarly here, it could be:

wsError("Duplicated register request", ws, c.db)


Why not "rooms *roomTable"?


Please also make a change of android_gdb_module() in util.py.


dash *dashboard

?


Yes, you're right! Good catch.

I wish Z3Bool's simply didn't have an `==` method, but Java :(


May have caused [JENKINS-26312](https://issues.jenkins-ci.org/browse/JENKINS-26312).


Would it make sense to pass in a port?


AM980859 is test


nops, I think the env() function enter after it.


Several things -
1. You committed the protolang binary. Oops.
2. Why is there a funcToStr() function?
Imo I don't see a use for that.
3. Instead of an if-elseif chain, use a switch statement.


Oh... then you'd have cl.rooms.rooms.   That's not very nice.

Perhaps you could just embed the room table like so:

type Collider struct {
  roomTable
  db *dashboard
}

Then you could just use the collider as a room table.


Do we need to ensure that `rcc` would be `null` if we called it again?


Sorry, yes same issue. What we really want is to construct a Z3 AST that represents equality. I think it is called `z3.mkEqual` (or something like it).

Do this, add a method called eq to the trait:

`def eq(e1: Z3Bool, e2: Z3Bool): Z3Bool`

Implement it using `z3.mkEqual` and use it in the tests.

We'll have to override some operator to make it easy to use, but we can sort that out later.


This snippet was duplicated in the Project ;)


This is the completion of https://courses.thinkful.com/pip-001v2/assignment/2.2.5


Hmm... I'm not sure. Let's sort out the other things first.


Changed to var as let was causing errors.


因为当时只有迅雷那边才支持bt和磁力链接等，所以只有迅雷后端才会返回多文件列表，其他后端暂时没有多文件，当时为了处理方便决定在文件列表中多加一项大小为-1的项表示多文件的总文件名。不过这种做法不合理，没考虑完全，所以后面要改。


Hopefully all of the merge mess is behind us now. I am going to pull the
Domination stuff back out of the master branch, don't know what I was
thinking there. You keep working in the Q1--2015 branch and if there are
any issue that need fixing we will fix them in this branch then I will pull
them over into the master branch.

//FC

On Tue, Jan 6, 2015 at 7:46 PM, anandaguneratne <notifications@github.com>
wrote:

> Well, it looks like it is still there, so I'll get back to work on
> improving the probabilities module.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/sIKE23/Mage-Wars/commit/9fc2da2d5f36c9f8c47ae28e8b91cf052d7f38e0#commitcomment-9178663>
> .
>


I didn't really read this. I assume it gets fixed in a later commit.


I think out parameters should be last in function signature, right?


Moved to main.js so it will have access to self.port.


This makes sense; can you please say more about the resulting effect of this bug? E.g., could a fragment end up permanently not-started?


won't this only process 15 /16 ?


Added IIFE to reduce global namespace pollution.


Cu was never used - removed.


rax retry tests


why this?


viewFor, tab_utils, data, and, doc were never used - removed.


Typo here with `exlude` ... should be `exclude`. Removing from OUJS. Please fix this before you reupload. You also have one other script on OUJS that doesn't meet the TOS requirement for library metadata blocks. Thanks.


renamed tmr -> timers


I think the result is great. You kept my original idea and made it look even better! I am happy to see that going in!


I just noticed--you aren't using `formula` anywhere in the body of this function.

Up to this point, the expressions  built with `and`, `or`, etc. only construct a big boolean expression. You need to also assert that `formula` is true in this function

    solver.assertCnstr(formula) // between push and pop


Ah, good!


If the page is already open, focus the tab and exit.


not needed any more?


I just saw the next commit!


LGTM


Open new tab, on load attach script files and execute scan.


Yeah, still wrong, based on your earlier analysis. Basically, calling `==` gives us object-equality in Scala/Java. We want to only construct Z3 expressions.


Great!


Not a big deal since its only used on the summary when the file is open, so maybe leave it and we can change it if/when we use it when no file is open ?


@jtpox $id_perms is not defined


you don't implement callbackParam is thread-safe


*shakes fist at sky* I guess I have to clone on my develop branch lol.


TeamCity Reaver Project :: Vapor :: Test Build with GCC [Build 18](http://ci.reaver-project.org/viewLog.html?buildId=408&buildTypeId=vapor_TestBuildWithGcc&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 3 Build time: 00:02:55


still weird


why this name is queue?


develop (lefticus) - x86_64-MacOS-10.9-clang-Debug: OK (331 of 331 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)


why inline?


It's OK if this checking is limited in this test module.


This already supports multi map server, since each map-server should have his own database table. The only problem could be if you switch one map from one map-server to another.


Just grab the new package <https://github.com/adamgoose/laravel-annotations>


I see what is wrong now, it should probably be `if ( empty( $spiBinaryFile->mimeType ) )`
right? Cause why load it if it is already set, or?


Support for gnome 3.14


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


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/9810/testReport/) for this commit**


Thanks, very helpful! :+1:


Please keep the function calls consistent:

- Either `helper.chain [initializeFilters, filterAwards]`
- or `helper.chain([configurePipeline, filterAwards])`

What does our style guide suggest? And if there is no rule: Can you think of any?


Since this is one of our library functions, please add tests for it.


why use static variable instead of member variable?
Remember WebCL object can be created in multiple time in same process. e.g. main frame and iframe use webcl. another tab but same site use webcl


ups :)


For the right language would be useful that you can give that
{
"id": "weather",
"class": "WeatherDevice",
"name": "Weather Geneva",
"location": "Geneva, Switzerland",
"degreeType": "C",
"lang": "nl-NL",
"timeout": 300000
},
{
"id": "forecast",
"class": "WeatherForecastDevice",
"name": "Forecast 1 day for Geneva",
"location": "Geneva, Switzerland",
"degreeType": "C",
"lang": "nl-NL",
"timeout": 300000,
"day": 1
}


why unsigned long. we hardly use long type


welldone! tremendous effort guys!


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/9811/testReport/) for this commit**


It indeed doesn't make much sense.

To fix, with a test covering this...


I was actually thinking about it the other way: having everything defined in the object.


Hm, what about redirect_after_create - explains itself better.


Enabling it in .travis.yml seems a good idea to me.
Linking to =Debug would work for me, but then does travis already builds with Debug on, and should it ?

I dunno what it means to use it in test. I think (but should be checked) that the model tester runs tests as the model is used, at different states that may not be reached during the run of the (finite) testsuite, while could be reached during arbitrary user interaction. Restricting use of the model tester during run of the testsuite could in this case reduce its effectiveness.


don't create thread every time.


yeah, much better :)
will replace


Let's add the rule: Only the outermost function call is without parentheses, nested calls require parantheses.


how do you make sure that postTask executed already?


I see, any ideas?


Yes but it is not what we are doing everywhere else in the code. And I don't like to have to create a object with named parameter for all parameters of a javascript function.


I've explained above--remove the dep entirely and rescue LoadError on `require 'slop'`. @bbatsov, how horrible is this solution in your opinion?


* Z modelu to odstraním - jednalo se pravděpodobně o nějaký workaround pro
případy když se PRIMARY key nejmenuje id
* v schema.rb, ale id právě už není :
      *-* t.integer "id", limit: 4, null: false

On Wed Jan 07 2015 at 10:14:59 AM Bohuslav Blín <notifications@github.com>
wrote:

> Odstran ten limit. Resp. id by vubec v schema.rb nemelo byt. Kdyz si
> zkusis vytvorit testovaci model/tabulku, tak to uvidis.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/boblin/nastenka/commit/3e76ba5bf44c603845f360578cf7594c2d41e233#commitcomment-9181941>
> .
>


I'm


Makes sense :+1:


Argh, you know what, re-reading this I realize this isn't quite right. I think what we want is

    tr.input_types().iter().flat_map(|t| t.walk()).any(is_ty_param)

in other words

    where int : Foo<X>

is ok.


this looks like a severe bug


If I understand you correctly, you want assign a value to state.saturation[pu.phase_pos[ Oil] ] after state.rs and state.rv is assigned i.e after # 559. My concern with this solution is that the phase pressure calculations in #545 that depends on the oil saturation will use the old oil saturation rather than the new one.


Good job.


Vector<unsigned, 2>


No longer valid. Should be replaced with mentioning the example file.


Please use color variables, e.g. `$white`.


The same as above.


odstraním - jednalo se pravděpodobně o nějaký workaround pro případy když se PRIMARY key nejmenuje id


Ye. Where possible, that's how we're doing it (imagine if you will, you want to add another variant in there that will start with a comma or something and you'll see where we're coming from).


This seems like a good addition. Care to issue a pull request to the upstream master?


@all:  pushed with changes as discussed
Note: shuffle mode should always be used for CTPS surrogate analysis. The shift mode (as it is implemented) will be frequency dependent.

@fboers: the stats output (text) of the CTPS surrogate analysis you/we may want to change into a json file (if wanted)


events.size() && clEvents.size() != events.size() ?


Yes, the hard coded values are just placeholder, and I do remember Warwick mentioning that weighted mood values had been entered.


Nice!

Weeeeee


@bjornblissing thanks! We will update the status of the work packages accordingly.


Do not leave logs in commit


Same here


Sweet.


Vector<RefPtr<WebCLContext>> is not needed?


why comment out. add comment to explain


:+1: this was required.


Comparing the same types is enough, converting it to strings is useless


trying to correct a bug on commit...


its not because of this Zoey broke it with libs update.


I'd rather use MoveChase() here, but the adds need to get somewhat into him.


thought we no longer need {{ homeCtrl.day }} if we are using ng-bind??


Me too, I've never been excited by annotations but this feature add/remove (and related blog posts and laracasts) indicates a somehow schizophrenic (no offence, eh) development


Again do not convert it to string when comparing the same types


Depends where. There are cases where we actually use objects like that, for instance when passing a whole lot of arguments. This one seems one of them, since we keep on adding new parameters (previously role, now channel).

I'm okay to keep it like that for now and change it later, but I would feel more future proof by using an object.


only WebCLContext use it. so WeakPtr<WebCLContext> more clearly.


Yes. I didn't notice ^^


thanks


Is this really people? Given we refer to persons as the collection this is a bit surprising to me.


Thanks all, should be fixed now. Tested with GHC 7.4 / 7.6 / 7.8 / 7.10.

http://hackage.haskell.org/package/fclabels-2.0.2.2


PTAL

when I clicked the button in cc::LayerTreeHostImpl in browser process, I got this error.
"Uncaught TypeError: Cannot read property 'clone' of undefined", source: chrome://tracing/tracing.js (32594)
so I add 'cc::SurfaceLayerImpl' to iterate all layers in browser process.

And, I am trying to add cc.debug.picture and separate picture info from cc.debug due to
heavy IPC burst.  https://codereview.chromium.org/828703002/


why this change?


r+


I understand. Vector<WeakPtr<WebCLObject>> is right. change it to Vector<WeakPtr<WebCLContext>>


Like


这里应该依然需要fork吧？pagelet模式下，多个pagelets加载的时候也是走这里的逻辑么？


Seems pretty horrible to me, but I can live with it. The more I think about it, however, the more I believe that using the built-in `optparse` is the best option. RuboCop has a pretty complex CLI and optparse has been sufficient there, so it should be sufficient for `parser` itself as well.


I've updated the PR to do the check in the Gemfile. I think it's less horrible than your approach. The other solution seems to be to do the version checks in a dummy c-extension.


hi, i could fix the unreported 'un-needed comma', see here http://dojo-toolkit.33424.n3.nabble.com/dojo-js-is-empty-after-the-build-td4004847.html (my last post ). needs a patch of gcc. would love to see that in the public versions as this wasted so many hours, not only mine :-) thank you.


Nice, thanks Sir! Fixed for me!


Because otherwise it would be picked up by the new error, since `int` is copy.

(I could've also just added the appropriate `//~ ERROR` line, but this seemed slightly cleaner to me. *shrug*)


Check if new syntax is avaible for this


This is covered in the above `*` rule.


In my opinion, thats the responsibility of the meta object.


(y)


Trailing whitespace is recommended in Markdown to do newlines


Thank you, that fixed the issue


Everything else seems to be okay.


Duplicated. `font-awesome` is the one we want.


Empty file now? Can be removed.


It fails only on HHVM. I have no idea why and unable to check such environment.


is this change by purpose?
```$model->load($data, false)``` does not work anymore


r+ rollup


Hi,

This is great plugin for zoom an image. I want to drag zoom frame on mouse movement how we can do this. Please explain.


php -S localhost:8000 -t public works better than the experimental file.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/9815/testReport/) for this commit**


r+


Probably better use `<span>` when you need inner `ng-bind`


Making an int larger won't cause any pain. It will just result in more zero bits. Since there's only one of these in the structure, it's hard to see any benefit to making it smaller than native size.


TESTS FAILED
 Mr.roboto url : http://jenkins.plone.org/roboto/get_info?push=06aa50ea6da6419bbb76ed2b9c2f8bb5
 plone-5.0-python-2.7 [FAILURE]


I don't think this step is meaningful unless you define "Retrieve" somewhere.


I still cannot make my mind consistent about this. PgArray is an object, that represents postgres array. In postgres equals operation between int2[] and int4[] is not defined at all so to compare them one would convert one into another...

So probably your implementation is correct :smile:


okay, will check it myself then.


comment to unify with the reste
```las = getImageLongAnnotations(session, ids) returns all long annotations linked to the image specified by the input identifiers ids and owned by the session user.```
it should be the ```images```.


`font-awesome` is the official package: https://github.com/FortAwesome/Font-Awesome/blob/master/bower.json#L2


Always render does not exists on old portlets, get this this info in a save way.


As discussed previously, I don't think it is useful to define "generic" errors. It is expected that implementation will throw if they are in unexpected/broken states but those are not defined because they can't be defined. We should only define specific errors that can happen to the eyes of the specification (for example, NetworkError if it is sane to expect a network request).


We fixed that


I would slightly change the wording here to removed "retrieved" and add "associated with the webapp" (from the removed step).


Je to standardni zpusob jak rict, ze primary key je jiny atribut, napr. UUID.


This is unnecessary.


Jasne. Mas pravdu :-)


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/9819/testReport/) for this commit**


That should be 6144


This is useful for multi-threaded applications.


Was zur hoelle? In master war bereits ne form drinn, und jetzt hast du die 2 forms zusammen ... und der Compilor is noch gar nicht fertig... wiso merged du den in die Master?


This should, IMO, be the 2X value times six, to scale similarly to the amount of available RAM, so 24. Or not?


Right, for some basic stuff it might not make sense to follow that (although for compat it potentially could I guess).