1: D100 Missing docstring in public module
25:1: E402 module level import not at top of file
26:1: I100 Imports statements are in the wrong order. import cgi should be before import time
26:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. import re should be before import string
28:1: E402 module level import not at top of file
29:1: I100 Imports statements are in the wrong order. import locale should be before import re
29:1: E402 module level import not at top of file
30:1: I201 Missing newline before sections or imports.
30:1: E402 module level import not at top of file
31:1: I100 Imports statements are in the wrong order. from urllib should be before from six
31:1: I201 Missing newline before sections or imports.
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
34:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_BIBINDEX_CHARS_PUNCTUATION, CFG_BIBRANK_SHOW_CITATION_GRAPHS, CFG_BIBRANK_SHOW_CITATION_LINKS, CFG_BIBRANK_SHOW_CITATION_STATS, CFG_BIBRANK_SHOW_DOWNLOAD_GRAPHS, CFG_BIBRANK_SHOW_DOWNLOAD_STATS, CFG_BIBRANK_SHOW_READING_STATS, CFG_CERN_SITE, CFG_INSPIRE_SITE, CFG_SITE_ADMIN_EMAIL, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_VERSION, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBSEARCH_ADVANCEDSEARCH_PATTERN_BOX_WIDTH, CFG_WEBSEARCH_AUTHOR_ET_AL_THRESHOLD, CFG_WEBSEARCH_DEFAULT_SEARCH_INTERFACE, CFG_WEBSEARCH_DEF_RECORDS_IN_GROUPS, CFG_WEBSEARCH_LIGHTSEARCH_PATTERN_BOX_WIDTH, CFG_WEBSEARCH_MAX_RECORDS_IN_GROUPS, CFG_WEBSEARCH_PREV_NEXT_HIT_FOR_GUESTS, CFG_WEBSEARCH_PREV_NEXT_HIT_LIMIT, CFG_WEBSEARCH_RESULTS_OVERVIEW_MAX_COLLS_TO_PRINT, CFG_WEBSEARCH_RSS_TTL, CFG_WEBSEARCH_SHOW_COMMENT_COUNT, CFG_WEBSEARCH_SHOW_REVIEW_COUNT, CFG_WEBSEARCH_SIMPLESEARCH_PATTERN_BOX_WIDTH, CFG_WEBSEARCH_SPLIT_BY_COLLECTION, CFG_WEBSEARCH_USE_ALEPH_SYSNOS, CFG_WEBSEARCH_WILDCARD_LIMIT
34:1: F401 'CFG_WEBCOMMENT_ALLOW_REVIEWS' imported but unused
34:1: F401 'CFG_WEBSEARCH_SHOW_REVIEW_COUNT' imported but unused
34:1: F401 'CFG_WEBSEARCH_SHOW_COMMENT_COUNT' imported but unused
34:1: F401 'CFG_WEBSEARCH_DEF_RECORDS_IN_GROUPS' imported but unused
34:1: F401 'CFG_WEBSEARCH_USE_ALEPH_SYSNOS' imported but unused
34:1: F401 'CFG_WEBCOMMENT_ALLOW_COMMENTS' imported but unused
34:1: F401 'CFG_INSPIRE_SITE' imported but unused
34:1: F401 'CFG_WEBSEARCH_RESULTS_OVERVIEW_MAX_COLLS_TO_PRINT' imported but unused
34:1: E402 module level import not at top of file
35:6: E126 continuation line over-indented for hanging indent
71:1: E402 module level import not at top of file
72:6: E126 continuation line over-indented for hanging indent
73:1: I100 Imports statements are in the wrong order. from invenio.legacy.dbquery should be before from invenio.modules.search.services
73:1: E402 module level import not at top of file
74:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.legacy.dbquery
74:1: E402 module level import not at top of file
75:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.base.i18n
75:1: E402 module level import not at top of file
76:1: I101 Imported names are in the wrong order. Should be create_html_link, create_url, drop_default_urlargd, make_canonical_urlargd
76:1: E402 module level import not at top of file
77:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.url
77:1: E402 module level import not at top of file
78:1: I100 Imports statements are in the wrong order. from invenio.ext.legacy.handler should be before from invenio.utils.html
78:1: E402 module level import not at top of file
79:1: E402 module level import not at top of file
80:1: E402 module level import not at top of file
81:1: F999 redefinition of unused 'CFG_WEBSEARCH_MAX_SEARCH_COLL_RESULTS_TO_PRINT' from line 71
81:1: E402 module level import not at top of file
82:6: E126 continuation line over-indented for hanging indent
83:1: I100 Imports statements are in the wrong order. from invenio.modules.formatter should be before from invenio.modules.search.services
83:1: E402 module level import not at top of file
85:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.modules.formatter
85:1: F401 'intbitset' imported but unused
85:1: E402 module level import not at top of file
87:1: E402 module level import not at top of file
88:1: E402 module level import not at top of file
89:1: I100 Imports statements are in the wrong order. from invenio.legacy.websearch_external_collections.config should be before from invenio.legacy.websearch_external_collections.utils
89:1: E402 module level import not at top of file
90:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.websearch_external_collections.config
90:1: E402 module level import not at top of file
95:1: E302 expected 2 blank lines, found 1
95: D101 Missing docstring in public class
129:34: E261 at least two spaces before inline comment
133: D102 Missing docstring in public method
143:13: E203 whitespace before ':'
146:32: E203 whitespace before ':'
147:32: E203 whitespace before ':'
148:32: E203 whitespace before ':'
149:32: E203 whitespace before ':'
150:32: E203 whitespace before ':'
151:32: E203 whitespace before ':'
152:32: E203 whitespace before ':'
154:32: E203 whitespace before ':'
155:32: E203 whitespace before ':'
156:32: E203 whitespace before ':'
158:32: E203 whitespace before ':'
159:32: E203 whitespace before ':'
160:32: E203 whitespace before ':'
161:32: E203 whitespace before ':'
164:13: E126 continuation line over-indented for hanging indent
164:17: E203 whitespace before ':'
165:20: E203 whitespace before ':'
166:21: E203 whitespace before ':'
167:22: E203 whitespace before ':'
168:21: E203 whitespace before ':'
169:22: E203 whitespace before ':'
170:22: E203 whitespace before ':'
171:19: E203 whitespace before ':'
172:20: E203 whitespace before ':'
173:20: E203 whitespace before ':'
174:19: E203 whitespace before ':'
175:19: E203 whitespace before ':'
176:19: E203 whitespace before ':'
177:20: E203 whitespace before ':'
178:21: E203 whitespace before ':'
179:21: E203 whitespace before ':'
180:21: E203 whitespace before ':'
181:19: E203 whitespace before ':'
182:20: E203 whitespace before ':'
183:20: E203 whitespace before ':'
184:20: E203 whitespace before ':'
185:20: E203 whitespace before ':'
186:21: E203 whitespace before ':'
187:19: E203 whitespace before ':'
188:18: E203 whitespace before ':'
189:22: E203 whitespace before ':'
190:22: E203 whitespace before ':'
191:22: E203 whitespace before ':'
192:26: E203 whitespace before ':'
193:21: E203 whitespace before ':'
194:25: E203 whitespace before ':'
195:24: E203 whitespace before ':'
196:25: E203 whitespace before ':'
197:25: E203 whitespace before ':'
198:23: E203 whitespace before ':'
199:25: E203 whitespace before ':'
200:24: E203 whitespace before ':'
201:24: E203 whitespace before ':'
202:24: E203 whitespace before ':'
203:24: E203 whitespace before ':'
204:28: E203 whitespace before ':'
205:23: E203 whitespace before ':'
206:24: E203 whitespace before ':'
207:25: E203 whitespace before ':'
208:26: E203 whitespace before ':'
209:25: E203 whitespace before ':'
210:26: E203 whitespace before ':'
211:26: E203 whitespace before ':'
212:27: E203 whitespace before ':'
213:21: E203 whitespace before ':'
214:25: E203 whitespace before ':'
215:23: E203 whitespace before ':'
216:24: E203 whitespace before ':'
217:23: E203 whitespace before ':'
218:24: E203 whitespace before ':'
219:24: E203 whitespace before ':'
220:22: E203 whitespace before ':'
221:26: E203 whitespace before ':'
222:23: E203 whitespace before ':'
223:25: E203 whitespace before ':'
224:23: E203 whitespace before ':'
225:25: E203 whitespace before ':'
226:24: E203 whitespace before ':'
227:22: E203 whitespace before ':'
228:26: E203 whitespace before ':'
229:25: E203 whitespace before ':'
230:25: E203 whitespace before ':'
236: D210 No whitespaces allowed surrounding docstring text
236: D400 First line should end with a period (not 'a')
236: D205 1 blank line required between summary line and description (found 0)
243:17: E266 too many leading '#' for block comment
282:17: F841 local variable 'pmid' is assigned to but never used
284:17: F841 local variable 'bibcode' is assigned to but never used
286:17: F841 local variable 'oai' is assigned to but never used
292:9: E266 too many leading '#' for block comment
296:18: E127 continuation line over-indented for visual indent
297:18: E127 continuation line over-indented for visual indent
298:18: E127 continuation line over-indented for visual indent
298:76: E271 multiple spaces after keyword
307:9: E266 too many leading '#' for block comment
309:17: E127 continuation line over-indented for visual indent
310:17: E127 continuation line over-indented for visual indent
311:17: E127 continuation line over-indented for visual indent
312:17: E127 continuation line over-indented for visual indent
319:9: E266 too many leading '#' for block comment
321:18: E127 continuation line over-indented for visual indent
322:18: E127 continuation line over-indented for visual indent
323:18: E127 continuation line over-indented for visual indent
327:13: F841 local variable 'journal_query' is assigned to but never used
329:9: E266 too many leading '#' for block comment
331:16: E127 continuation line over-indented for visual indent
340:9: E266 too many leading '#' for block comment
342:16: E127 continuation line over-indented for visual indent
343:16: E127 continuation line over-indented for visual indent
344:16: E127 continuation line over-indented for visual indent
348:13: F841 local variable 'issn_query' is assigned to but never used
350:9: E266 too many leading '#' for block comment
357:9: E266 too many leading '#' for block comment
358:18: E261 at least two spaces before inline comment
358:19: E262 inline comment should start with '# '
363:9: E266 too many leading '#' for block comment
367:24: E203 whitespace before ':'
368:25: E203 whitespace before ':'
369:25: E203 whitespace before ':'
373:24: E203 whitespace before ':'
374:25: E203 whitespace before ':'
375:25: E203 whitespace before ':'
379:24: E203 whitespace before ':'
380:25: E203 whitespace before ':'
381:25: E203 whitespace before ':'
385:24: E203 whitespace before ':'
386:25: E203 whitespace before ':'
387:25: E203 whitespace before ':'
392:24: E203 whitespace before ':'
393:25: E203 whitespace before ':'
394:25: E203 whitespace before ':'
397:24: E203 whitespace before ':'
398:25: E203 whitespace before ':'
399:25: E203 whitespace before ':'
401:9: E266 too many leading '#' for block comment
404:20: E203 whitespace before ':'
405:21: E203 whitespace before ':'
406:21: E203 whitespace before ':'
409:20: E203 whitespace before ':'
410:21: E203 whitespace before ':'
411:21: E203 whitespace before ':'
413:13: E266 too many leading '#' for block comment
415:25: E126 continuation line over-indented for hanging indent
415:28: E203 whitespace before ':'
416:29: E203 whitespace before ':'
417:29: E203 whitespace before ':'
419: D210 No whitespaces allowed surrounding docstring text
419: D401 First line should be in imperative mood ('Return', not 'Returns')
419: D200 One-line docstring should fit on one line with quotes (found 2)
439:3: E128 continuation line under-indented for visual indent
449: D210 No whitespaces allowed surrounding docstring text
449: D202 No blank lines allowed after function docstring (found 1)
449: D400 First line should end with a period (not 'h')
449: D205 1 blank line required between summary line and description (found 0)
481: D210 No whitespaces allowed surrounding docstring text
481: D202 No blank lines allowed after function docstring (found 1)
505: D202 No blank lines allowed after function docstring (found 1)
505: D400 First line should end with a period (not 'L')
532: D202 No blank lines allowed after function docstring (found 1)
532: D400 First line should end with a period (not 's')
542:17: E127 continuation line over-indented for visual indent
557:5: E303 too many blank lines (2)
557: D401 First line should be in imperative mood ('Create', not 'Creates')
557: D400 First line should end with a period (not ')')
578: D210 No whitespaces allowed surrounding docstring text
578: D401 First line should be in imperative mood ('Create', not 'Creates')
578: D201 No blank lines allowed before function docstring (found 1)
578: D202 No blank lines allowed after function docstring (found 1)
611:20: E126 continuation line over-indented for hanging indent
614:16: E126 continuation line over-indented for hanging indent
620:27: E201 whitespace after '{'
620:42: E203 whitespace before ':'
620:57: E202 whitespace before '}'
627:44: E203 whitespace before ':'
630: D401 First line should be in imperative mood ('Create', not 'Creates')
630: D400 First line should end with a period (not 's')
630: D205 1 blank line required between summary line and description (found 0)
642:38: E203 whitespace before ':'
642:66: E203 whitespace before ':'
646: D401 First line should be in imperative mood ('Produce', not 'Produces')
646: D202 No blank lines allowed after function docstring (found 1)
647:54: E261 at least two spaces before inline comment
676:9: E303 too many blank lines (2)
677:21: E127 continuation line over-indented for visual indent
685:84: E251 unexpected spaces around keyword / parameter equals
689:85: E502 the backslash is redundant between brackets
728:35: E231 missing whitespace after ':'
729:35: E231 missing whitespace after ':'
734:73: E502 the backslash is redundant between brackets
746:87: E502 the backslash is redundant between brackets
780:20: E203 whitespace before ':'
781:29: E203 whitespace before ':'
783:25: E203 whitespace before ':'
784:25: E203 whitespace before ':'
785:24: E203 whitespace before ':'
786:28: E203 whitespace before ':'
787:28: E203 whitespace before ':'
788:33: E203 whitespace before ':'
794: D401 First line should be in imperative mood ('Produce', not 'Produces')
794: D202 No blank lines allowed after function docstring (found 1)
825:9: E303 too many blank lines (2)
826:21: E127 continuation line over-indented for visual indent
857:20: E203 whitespace before ':'
858:29: E203 whitespace before ':'
860:25: E203 whitespace before ':'
861:25: E203 whitespace before ':'
862:24: E203 whitespace before ':'
863:31: E203 whitespace before ':'
864:28: E203 whitespace before ':'
865:28: E203 whitespace before ':'
866:33: E203 whitespace before ':'
870: D401 First line should be in imperative mood ('Produce', not 'Produces')
870: D202 No blank lines allowed after function docstring (found 1)
870: D208 Docstring is over-indented
871:36: E261 at least two spaces before inline comment
922:9: E303 too many blank lines (2)
923:18: E128 continuation line under-indented for visual indent
969:20: E203 whitespace before ':'
970:29: E203 whitespace before ':'
972:25: E203 whitespace before ':'
973:25: E203 whitespace before ':'
974:24: E203 whitespace before ':'
976:29: E203 whitespace before ':'
977:33: E203 whitespace before ':'
978:30: E203 whitespace before ':'
980:29: E203 whitespace before ':'
981:33: E203 whitespace before ':'
982:30: E203 whitespace before ':'
984:29: E203 whitespace before ':'
985:33: E203 whitespace before ':'
987:28: E203 whitespace before ':'
988:28: E203 whitespace before ':'
989:33: E203 whitespace before ':'
1006:24: E126 continuation line over-indented for hanging indent
1006:38: E203 whitespace before ':'
1007:39: E203 whitespace before ':'
1008:22: E126 continuation line over-indented for hanging indent
1053:21: E126 continuation line over-indented for hanging indent
1053:28: E203 whitespace before ':'
1054:28: E203 whitespace before ':'
1056:33: E203 whitespace before ':'
1057:33: E203 whitespace before ':'
1059:31: E203 whitespace before ':'
1060:34: E203 whitespace before ':'
1061:33: E203 whitespace before ':'
1062:34: E203 whitespace before ':'
1063:34: E203 whitespace before ':'
1064:37: E203 whitespace before ':'
1065:36: E203 whitespace before ':'
1066:19: E126 continuation line over-indented for hanging indent
1070:5: E303 too many blank lines (2)
1070: D202 No blank lines allowed after function docstring (found 1)
1070: D400 First line should end with a period (not 'e')
1070: D205 1 blank line required between summary line and description (found 0)
1091:18: E127 continuation line over-indented for visual indent
1097:37: E128 continuation line under-indented for visual indent
1097:42: E261 at least two spaces before inline comment
1098:37: E128 continuation line under-indented for visual indent
1098:43: E261 at least two spaces before inline comment
1099:37: E128 continuation line under-indented for visual indent
1100:37: E128 continuation line under-indented for visual indent
1101:37: E128 continuation line under-indented for visual indent
1105:5: E303 too many blank lines (2)
1105: D401 First line should be in imperative mood ('Create', not 'Creates')
1105: D202 No blank lines allowed after function docstring (found 1)
1157:27: E203 whitespace before ':'
1157:18: E225 missing whitespace around operator
1176:26: E203 whitespace before ':'
1177:16: E203 whitespace before ':'
1178:21: E203 whitespace before ':'
1179:22: E203 whitespace before ':'
1198:14: E225 missing whitespace around operator
1200:24: E203 whitespace before ':'
1201:31: E126 continuation line over-indented for hanging indent
1201:35: E251 unexpected spaces around keyword / parameter equals
1201:37: E251 unexpected spaces around keyword / parameter equals
1202:36: E251 unexpected spaces around keyword / parameter equals
1202:38: E251 unexpected spaces around keyword / parameter equals
1203:33: E251 unexpected spaces around keyword / parameter equals
1203:35: E251 unexpected spaces around keyword / parameter equals
1204:29: E126 continuation line over-indented for hanging indent
1205:24: E203 whitespace before ':'
1206:26: E203 whitespace before ':'
1207:28: E203 whitespace before ':'
1208:28: E203 whitespace before ':'
1213:5: E303 too many blank lines (2)
1213: D401 First line should be in imperative mood ('Return', not 'Returns')
1213: D202 No blank lines allowed after function docstring (found 1)
1213: D208 Docstring is over-indented
1236:22: E203 whitespace before ':'
1237:22: E203 whitespace before ':'
1238:60: E127 continuation line over-indented for visual indent
1238:66: E203 whitespace before ':'
1239:22: E203 whitespace before ':'
1240:60: E127 continuation line over-indented for visual indent
1240:66: E203 whitespace before ':'
1241:22: E203 whitespace before ':'
1242:60: E127 continuation line over-indented for visual indent
1242:66: E203 whitespace before ':'
1243:22: E203 whitespace before ':'
1244:60: E127 continuation line over-indented for visual indent
1244:66: E203 whitespace before ':'
1245:22: E203 whitespace before ':'
1246:60: E127 continuation line over-indented for visual indent
1246:66: E203 whitespace before ':'
1247:15: E124 closing bracket does not match visual indentation
1250: D401 First line should be in imperative mood ('Check', not 'Checks')
1250: D208 Docstring is over-indented
1265: D401 First line should be in imperative mood ('Return', not 'Returns')
1265: D202 No blank lines allowed after function docstring (found 1)
1265: D208 Docstring is over-indented
1287:22: E203 whitespace before ':'
1288:22: E203 whitespace before ':'
1288:66: E203 whitespace before ':'
1289:22: E203 whitespace before ':'
1289:66: E203 whitespace before ':'
1290:22: E203 whitespace before ':'
1290:66: E203 whitespace before ':'
1291:15: E124 closing bracket does not match visual indentation
1294: D401 First line should be in imperative mood ('Produce', not 'Produces')
1294: D208 Docstring is over-indented
1311:17: E126 continuation line over-indented for hanging indent
1311:23: E203 whitespace before ':'
1312:22: E203 whitespace before ':'
1313:22: E203 whitespace before ':'
1314:15: E126 continuation line over-indented for hanging indent
1323:18: E126 continuation line over-indented for hanging indent
1323:24: E203 whitespace before ':'
1324:23: E203 whitespace before ':'
1325:23: E203 whitespace before ':'
1326:16: E126 continuation line over-indented for hanging indent
1328:100: E502 the backslash is redundant between brackets
1329:93: E502 the backslash is redundant between brackets
1338:18: E126 continuation line over-indented for hanging indent
1338:24: E203 whitespace before ':'
1339:23: E203 whitespace before ':'
1340:23: E203 whitespace before ':'
1341:16: E126 continuation line over-indented for hanging indent
1348: D401 First line should be in imperative mood ('Produce', not 'Produces')
1348: D400 First line should end with a period (not 'e')
1348: D205 1 blank line required between summary line and description (found 0)
1348: D208 Docstring is over-indented
1366:22: E201 whitespace after '{'
1369:21: E124 closing bracket does not match visual indentation
1372: D401 First line should be in imperative mood ('Create', not 'Creates')
1372: D201 No blank lines allowed before function docstring (found 1)
1372: D202 No blank lines allowed after function docstring (found 1)
1372: D205 1 blank line required between summary line and description (found 0)
1418:41: E203 whitespace before ':'
1425:21: E201 whitespace after '{'
1430:100: E203 whitespace before ':'
1430:123: E202 whitespace before '}'
1435:122: E203 whitespace before ':'
1435:145: E202 whitespace before '}'
1437:104: E203 whitespace before ':'
1437:127: E202 whitespace before '}'
1441:104: E203 whitespace before ':'
1441:127: E202 whitespace before '}'
1443:118: E203 whitespace before ':'
1443:141: E202 whitespace before '}'
1449:23: E203 whitespace before ':'
1461:29: E201 whitespace after '{'
1461:39: E203 whitespace before ':'
1461:62: E203 whitespace before ':'
1464:76: E201 whitespace after '{'
1464:82: E203 whitespace before ':'
1464:100: E202 whitespace before '}'
1473:32: E203 whitespace before ':'
1480:37: E126 continuation line over-indented for hanging indent
1480:38: E201 whitespace after '{'
1480:48: E203 whitespace before ':'
1480:71: E203 whitespace before ':'
1489: D102 Missing docstring in public method
1516:34: E127 continuation line over-indented for visual indent
1516:35: E201 whitespace after '{'
1526: D202 No blank lines allowed after function docstring (found 1)
1550: D401 First line should be in imperative mood ('Display', not 'Displays')
1550: D202 No blank lines allowed after function docstring (found 1)
1550: D400 First line should end with a period (not 'e')
1565: D401 First line should be in imperative mood ('Display', not 'Displays')
1565: D202 No blank lines allowed after function docstring (found 1)
1565: D400 First line should end with a period (not 'e')
1580: D401 First line should be in imperative mood ('Display', not 'Displays')
1580: D202 No blank lines allowed after function docstring (found 1)
1580: D400 First line should end with a period (not 'e')
1596:5: E303 too many blank lines (2)
1596: D401 First line should be in imperative mood ('Format', not 'Formats')
1596: D202 No blank lines allowed after function docstring (found 1)
1625:17: E122 continuation line missing indentation or outdented
1626:17: E122 continuation line missing indentation or outdented
1639:23: E126 continuation line over-indented for hanging indent
1661:32: E203 whitespace before ':'
1661:73: E203 whitespace before ','
1662:30: E203 whitespace before ':'
1666:5: E303 too many blank lines (2)
1666: D401 First line should be in imperative mood ('Produce', not 'Produces')
1666: D202 No blank lines allowed after function docstring (found 1)
1686:26: E126 continuation line over-indented for hanging indent
1686:36: E203 whitespace before ':'
1687:36: E203 whitespace before ':'
1688:36: E203 whitespace before ':'
1689:24: E126 continuation line over-indented for hanging indent
1693: D401 First line should be in imperative mood ('Produce', not 'Produces')
1693: D400 First line should end with a period (not 'x')
1712:24: E203 whitespace before ':'
1713:20: E203 whitespace before ':'
1723:22: E126 continuation line over-indented for hanging indent
1723:32: E203 whitespace before ':'
1724:32: E203 whitespace before ':'
1725:32: E203 whitespace before ':'
1726:20: E126 continuation line over-indented for hanging indent
1731: D401 First line should be in imperative mood ('Display', not 'Displays')
1731: D202 No blank lines allowed after function docstring (found 1)
1731: D400 First line should end with a period (not 'd')
1768: D401 First line should be in imperative mood ('Display', not 'Displays')
1768: D400 First line should end with a period (not 'd')
1789:22: E126 continuation line over-indented for hanging indent
1789:29: E203 whitespace before ':'
1790:20: E126 continuation line over-indented for hanging indent
1803:76: E203 whitespace before ':'
1805:75: E203 whitespace before ':'
1805:131: E202 whitespace before '}'
1808:22: E126 continuation line over-indented for hanging indent
1808:27: E203 whitespace before ':'
1809:28: E203 whitespace before ':'
1810:20: E126 continuation line over-indented for hanging indent
1813: D401 First line should be in imperative mood ('Display', not 'Displays')
1813: D202 No blank lines allowed after function docstring (found 1)
1813: D400 First line should end with a period (not 'h')
1837: D401 First line should be in imperative mood ('Display', not 'Displays')
1837: D202 No blank lines allowed after function docstring (found 1)
1837: D400 First line should end with a period (not 'x')
1875:26: E261 at least two spaces before inline comment
1898: D401 First line should be in imperative mood ('Display', not 'Displays')
1898: D202 No blank lines allowed after function docstring (found 1)
1898: D400 First line should end with a period (not 'x')
1935:17: E126 continuation line over-indented for hanging indent
1935:23: E203 whitespace before ':'
1936:21: E203 whitespace before ':'
1937:15: E126 continuation line over-indented for hanging indent
1947:26: E203 whitespace before ':'
1970:30: E203 whitespace before ':'
1982:47: E203 whitespace before ':'
1990:22: E128 continuation line under-indented for visual indent
1991:22: E128 continuation line under-indented for visual indent
1992:22: E128 continuation line under-indented for visual indent
1993:22: E128 continuation line under-indented for visual indent
1993:26: E203 whitespace before ':'
1998:22: E128 continuation line under-indented for visual indent
1999:22: E128 continuation line under-indented for visual indent
2000:22: E128 continuation line under-indented for visual indent
2001:22: E128 continuation line under-indented for visual indent
2001:26: E203 whitespace before ':'
2013:23: E128 continuation line under-indented for visual indent
2014:60: E127 continuation line over-indented for visual indent
2015:44: E203 whitespace before ':'
2020: D401 First line should be in imperative mood ('Display', not 'Displays')
2020: D201 No blank lines allowed before function docstring (found 1)
2020: D202 No blank lines allowed after function docstring (found 1)
2020: D400 First line should end with a period (not 'x')
2083:9: E303 too many blank lines (2)
2100:64: E203 whitespace before ':'
2104:25: E203 whitespace before ':'
2118:35: E126 continuation line over-indented for hanging indent
2118:37: E251 unexpected spaces around keyword / parameter equals
2118:39: E251 unexpected spaces around keyword / parameter equals
2119:44: E251 unexpected spaces around keyword / parameter equals
2119:46: E251 unexpected spaces around keyword / parameter equals
2120:43: E251 unexpected spaces around keyword / parameter equals
2120:45: E251 unexpected spaces around keyword / parameter equals
2121:41: E251 unexpected spaces around keyword / parameter equals
2121:43: E251 unexpected spaces around keyword / parameter equals
2122:33: E126 continuation line over-indented for hanging indent
2180:26: E203 whitespace before ':'
2181:30: E203 whitespace before ':'
2182:28: E203 whitespace before ':'
2183:21: E203 whitespace before ':'
2184:32: E203 whitespace before ':'
2185:35: E126 continuation line over-indented for hanging indent
2189:33: E126 continuation line over-indented for hanging indent
2190:15: E131 continuation line unaligned for hanging indent
2190:26: E203 whitespace before ':'
2191:35: E126 continuation line over-indented for hanging indent
2194:33: E126 continuation line over-indented for hanging indent
2195:26: E203 whitespace before ':'
2196:19: E203 whitespace before ':'
2197:30: E203 whitespace before ':'
2198:35: E126 continuation line over-indented for hanging indent
2202:33: E126 continuation line over-indented for hanging indent
2203:26: E203 whitespace before ':'
2204:35: E126 continuation line over-indented for hanging indent
2207:33: E126 continuation line over-indented for hanging indent
2208:26: E203 whitespace before ':'
2209:19: E203 whitespace before ':'
2210:30: E203 whitespace before ':'
2211:35: E126 continuation line over-indented for hanging indent
2215:33: E126 continuation line over-indented for hanging indent
2216:23: E203 whitespace before ':'
2217:23: E203 whitespace before ':'
2218:24: E203 whitespace before ':'
2219:19: E203 whitespace before ':'
2254:15: E121 continuation line under-indented for hanging indent
2264:24: E203 whitespace before ':'
2265:28: E203 whitespace before ':'
2266:18: E203 whitespace before ':'
2267:29: E203 whitespace before ':'
2268:35: E126 continuation line over-indented for hanging indent
2272:33: E126 continuation line over-indented for hanging indent
2273:23: E203 whitespace before ':'
2274:23: E203 whitespace before ':'
2275:24: E203 whitespace before ':'
2276:19: E203 whitespace before ':'
2290:88: E502 the backslash is redundant between brackets
2291:19: E128 continuation line under-indented for visual indent
2292:19: E128 continuation line under-indented for visual indent
2293:19: E128 continuation line under-indented for visual indent
2294:19: E128 continuation line under-indented for visual indent
2311:15: E121 continuation line under-indented for hanging indent
2311:28: E203 whitespace before ':'
2322:24: E203 whitespace before ':'
2323:18: E203 whitespace before ':'
2324:29: E203 whitespace before ':'
2325:35: E126 continuation line over-indented for hanging indent
2329:33: E126 continuation line over-indented for hanging indent
2330:23: E203 whitespace before ':'
2331:23: E203 whitespace before ':'
2332:24: E203 whitespace before ':'
2333:19: E203 whitespace before ':'
2338:9: E266 too many leading '#' for block comment
2364:29: E203 whitespace before ':'
2365:30: E203 whitespace before ':'
2366:27: E203 whitespace before ':'
2367:18: E126 continuation line over-indented for hanging indent
2369:9: E266 too many leading '#' for block comment
2387:25: E126 continuation line over-indented for hanging indent
2387:34: E203 whitespace before ':'
2388:38: E203 whitespace before ':'
2389:29: E203 whitespace before ':'
2390:23: E126 continuation line over-indented for hanging indent
2392:9: E266 too many leading '#' for block comment
2394:17: E261 at least two spaces before inline comment
2396:13: F841 local variable 'cell_6_a' is assigned to but never used
2397:13: F841 local variable 'cell_6_b' is assigned to but never used
2416:25: E126 continuation line over-indented for hanging indent
2416:32: E203 whitespace before ':'
2417:32: E203 whitespace before ':'
2419:32: E203 whitespace before ':'
2420:32: E203 whitespace before ':'
2421:23: E126 continuation line over-indented for hanging indent
2423:9: E266 too many leading '#' for block comment
2429:33: E201 whitespace after '{'
2429:41: E203 whitespace before ':'
2429:53: E203 whitespace before ':'
2459:19: E126 continuation line over-indented for hanging indent
2459:28: E203 whitespace before ':'
2460:32: E203 whitespace before ':'
2461:31: E203 whitespace before ':'
2462:30: E203 whitespace before ':'
2463:30: E203 whitespace before ':'
2464:37: E126 continuation line over-indented for hanging indent
2464:44: E203 whitespace before ':'
2465:43: E203 whitespace before ':'
2466:35: E126 continuation line over-indented for hanging indent
2467:37: E126 continuation line over-indented for hanging indent
2467:44: E203 whitespace before ':'
2468:43: E203 whitespace before ':'
2469:35: E126 continuation line over-indented for hanging indent
2470:30: E203 whitespace before ':'
2471:30: E203 whitespace before ':'
2472:30: E203 whitespace before ':'
2473:37: E126 continuation line over-indented for hanging indent
2473:44: E203 whitespace before ':'
2474:43: E203 whitespace before ':'
2475:35: E126 continuation line over-indented for hanging indent
2476:37: E126 continuation line over-indented for hanging indent
2476:44: E203 whitespace before ':'
2477:43: E203 whitespace before ':'
2478:35: E126 continuation line over-indented for hanging indent
2479:30: E203 whitespace before ':'
2480:35: E126 continuation line over-indented for hanging indent
2484:17: E121 continuation line under-indented for hanging indent
2486:9: E266 too many leading '#' for block comment
2490: D210 No whitespaces allowed surrounding docstring text
2490: D401 First line should be in imperative mood ('Produce', not 'Produces')
2490: D400 First line should end with a period (not 'd')
2490: D300 Use """triple double quotes""" (found '-quotes)
2501:18: E126 continuation line over-indented for hanging indent
2501:24: E203 whitespace before ':'
2502:25: E203 whitespace before ':'
2503:16: E126 continuation line over-indented for hanging indent
2505: D401 First line should be in imperative mood ('Add', not 'Adds')
2505: D209 Multi-line docstring closing quotes should be on a separate line
2505: D202 No blank lines allowed after function docstring (found 1)
2505: D400 First line should end with a period (not 'y')
2505: D205 1 blank line required between summary line and description (found 0)
2514:32: E203 whitespace before ':'
2515:31: E203 whitespace before ':'
2519:40: E203 whitespace before ':'
2519: D400 First line should end with a period (not 'r')
2519: D300 Use """triple double quotes""" (found '-quotes)
2523:38: E203 whitespace before ':'
2523: D400 First line should end with a period (not 'r')
2523: D300 Use """triple double quotes""" (found '-quotes)
2527: D401 First line should be in imperative mood ('Print', not 'Prints')
2527: D201 No blank lines allowed before function docstring (found 1)
2527: D202 No blank lines allowed after function docstring (found 1)
2527: D205 1 blank line required between summary line and description (found 0)
2596:21: E126 continuation line over-indented for hanging indent
2597:30: E203 whitespace before ':'
2600:19: E126 continuation line over-indented for hanging indent
2605:26: E201 whitespace after '{'
2605:36: E203 whitespace before ':'
2605:51: E202 whitespace before '}'
2611:22: E126 continuation line over-indented for hanging indent
2611:34: E203 whitespace before ':'
2612:20: E126 continuation line over-indented for hanging indent
2618:26: E261 at least two spaces before inline comment
2634:17: E124 closing bracket does not match visual indentation
2661:49: E231 missing whitespace after ':'
2665:61: E128 continuation line under-indented for visual indent
2666:61: E128 continuation line under-indented for visual indent
2671:13: E303 too many blank lines (2)
2672:13: F841 local variable 'cc' is assigned to but never used
2673:13: F841 local variable 'sc' is assigned to but never used
2687:22: E126 continuation line over-indented for hanging indent
2687:28: E203 whitespace before ':'
2688:28: E203 whitespace before ':'
2689:20: E126 continuation line over-indented for hanging indent
2700:26: E126 continuation line over-indented for hanging indent
2700:32: E203 whitespace before ':'
2701:24: E126 continuation line over-indented for hanging indent
2708: D401 First line should be in imperative mood ('Print', not 'Prints')
2708: D201 No blank lines allowed before function docstring (found 1)
2708: D202 No blank lines allowed after function docstring (found 1)
2708: D205 1 blank line required between summary line and description (found 0)
2709:32: E128 continuation line under-indented for visual indent
2710:32: E128 continuation line under-indented for visual indent
2711:32: E128 continuation line under-indented for visual indent
2712:32: E128 continuation line under-indented for visual indent
2713:32: E128 continuation line under-indented for visual indent
2714:32: E128 continuation line under-indented for visual indent
2777:21: E126 continuation line over-indented for hanging indent
2778:30: E203 whitespace before ':'
2781:19: E126 continuation line over-indented for hanging indent
2786:26: E201 whitespace after '{'
2786:36: E203 whitespace before ':'
2786:51: E202 whitespace before '}'
2794:26: E126 continuation line over-indented for hanging indent
2794:38: E203 whitespace before ':'
2795:24: E126 continuation line over-indented for hanging indent
2808:26: E261 at least two spaces before inline comment
2824:17: E124 closing bracket does not match visual indentation
2851:49: E231 missing whitespace after ':'
2855:61: E128 continuation line under-indented for visual indent
2856:61: E128 continuation line under-indented for visual indent
2861:13: E303 too many blank lines (2)
2862:13: F841 local variable 'cc' is assigned to but never used
2863:13: F841 local variable 'sc' is assigned to but never used
2877:22: E126 continuation line over-indented for hanging indent
2877:28: E203 whitespace before ':'
2878:28: E203 whitespace before ':'
2879:20: E126 continuation line over-indented for hanging indent
2890:26: E126 continuation line over-indented for hanging indent
2890:32: E203 whitespace before ':'
2891:24: E126 continuation line over-indented for hanging indent
2898: D400 First line should end with a period (not 'g')
2898: D205 1 blank line required between summary line and description (found 0)
2925: D205 1 blank line required between summary line and description (found 0)
2946: D401 First line should be in imperative mood ('Return', not 'Returns')
2946: D202 No blank lines allowed after function docstring (found 1)
2946: D400 First line should end with a period (not 't')
2946: D205 1 blank line required between summary line and description (found 0)
2961:9: F841 local variable '_' is assigned to but never used
2967:17: E126 continuation line over-indented for hanging indent
2967:26: E203 whitespace before ':'
2968:15: E126 continuation line over-indented for hanging indent
2972: D401 First line should be in imperative mood ('Return', not 'Returns')
2972: D202 No blank lines allowed after function docstring (found 1)
2972: D400 First line should end with a period (not 't')
2972: D205 1 blank line required between summary line and description (found 0)
2994:16: E126 continuation line over-indented for hanging indent
2995:18: E126 continuation line over-indented for hanging indent
2999: D401 First line should be in imperative mood ('Return', not 'Returns')
2999: D202 No blank lines allowed after function docstring (found 1)
2999: D400 First line should end with a period (not 'e')
2999: D205 1 blank line required between summary line and description (found 0)
3029:9: F841 local variable '_' is assigned to but never used
3046:27: E203 whitespace before ':'
3047:27: E203 whitespace before ':'
3048:28: E203 whitespace before ':'
3054: D401 First line should be in imperative mood ('Print', not 'Prints')
3054: D202 No blank lines allowed after function docstring (found 1)
3094:21: E126 continuation line over-indented for hanging indent
3094:146: E502 the backslash is redundant between brackets
3094:29: E203 whitespace before ':'
3099:19: E126 continuation line over-indented for hanging indent
3106:25: E126 continuation line over-indented for hanging indent
3106:89: E502 the backslash is redundant between brackets
3106:33: E203 whitespace before ':'
3109:23: E126 continuation line over-indented for hanging indent
3114:25: E126 continuation line over-indented for hanging indent
3114:159: E502 the backslash is redundant between brackets
3114:33: E203 whitespace before ':'
3119:23: E126 continuation line over-indented for hanging indent
3143:39: E127 continuation line over-indented for visual indent
3143:51: E203 whitespace before ':'
3144:46: E203 whitespace before ':'
3145:51: E203 whitespace before ':'
3146:48: E203 whitespace before ':'
3153:39: E127 continuation line over-indented for visual indent
3153:51: E203 whitespace before ':'
3154:46: E203 whitespace before ':'
3155:51: E203 whitespace before ':'
3156:48: E203 whitespace before ':'
3164:162: E251 unexpected spaces around keyword / parameter equals
3164:164: E251 unexpected spaces around keyword / parameter equals
3164: D202 No blank lines allowed after function docstring (found 1)
3164: D200 One-line docstring should fit on one line with quotes (found 2)
3187:29: E126 continuation line over-indented for hanging indent
3187:38: E203 whitespace before ':'
3188:40: E203 whitespace before ':'
3189:27: E126 continuation line over-indented for hanging indent
3205:36: E203 whitespace before ':'
3222: D401 First line should be in imperative mood ('Print', not 'Prints')
3222: D400 First line should end with a period (not 't')
3236:9: E303 too many blank lines (2)
3259:32: E203 whitespace before ':'
3261:26: E203 whitespace before ':'
3262:33: E203 whitespace before ':'
3270: D210 No whitespaces allowed surrounding docstring text
3270: D400 First line should end with a period (not 's')
3279:5: E303 too many blank lines (2)
3279: D202 No blank lines allowed after function docstring (found 1)
3279: D400 First line should end with a period (not 's')
3310:31: E203 whitespace before ':'
3317: D202 No blank lines allowed after function docstring (found 1)
3317: D400 First line should end with a period (not 's')
3331:17: E126 continuation line over-indented for hanging indent
3331:26: E203 whitespace before ':'
3332:15: E126 continuation line over-indented for hanging indent
3339:37: E126 continuation line over-indented for hanging indent
3342:69: E231 missing whitespace after ':'
3343:29: E203 whitespace before ':'
3349: D401 First line should be in imperative mood ('Display', not 'Displays')
3349: D400 First line should end with a period (not 'd')
3362:18: E127 continuation line over-indented for visual indent
3371:65: E126 continuation line over-indented for hanging indent
3392:37: E126 continuation line over-indented for hanging indent
3437: D202 No blank lines allowed after function docstring (found 1)
3437: D205 1 blank line required between summary line and description (found 0)
3437: D208 Docstring is over-indented
3466:16: E201 whitespace after '{'
3466:43: E202 whitespace before '}'
3471:23: E203 whitespace before ':'
3477: D401 First line should be in imperative mood ('Display', not 'Displays')
3477: D400 First line should end with a period (not 'y')
3491:18: E127 continuation line over-indented for visual indent
3513:9: E266 too many leading '#' for block comment
3516:18: E126 continuation line over-indented for hanging indent
3527: D401 First line should be in imperative mood ('Display', not 'Displays')
3527: D400 First line should end with a period (not 'y')
3541: D401 First line should be in imperative mood ('Create', not 'Creates')
3591:49: E502 the backslash is redundant between brackets
3592:34: E127 continuation line over-indented for visual indent
3593:51: E502 the backslash is redundant between brackets
3595:43: E502 the backslash is redundant between brackets
3597:45: E502 the backslash is redundant between brackets
3598:30: E128 continuation line under-indented for visual indent
3599:43: E502 the backslash is redundant between brackets
3601:47: E502 the backslash is redundant between brackets
3602:30: E128 continuation line under-indented for visual indent
3603:41: E502 the backslash is redundant between brackets
3604:30: E128 continuation line under-indented for visual indent
3605:42: E502 the backslash is redundant between brackets
3606:30: E128 continuation line under-indented for visual indent
3610:9: E124 closing bracket does not match visual indentation
3613: D401 First line should be in imperative mood ('Create', not 'Creates')
3620: D401 First line should be in imperative mood ('Create', not 'Creates')
3637:5: W191 indentation contains tabs
3637:5: E101 indentation contains mixed spaces and tabs
3642:1: W191 indentation contains tabs
3642:1: E101 indentation contains mixed spaces and tabs
3643:1: E101 indentation contains mixed spaces and tabs
3661:49: E502 the backslash is redundant between brackets
3662:34: E127 continuation line over-indented for visual indent
3663:51: E502 the backslash is redundant between brackets
3665:43: E502 the backslash is redundant between brackets
3667:45: E502 the backslash is redundant between brackets
3668:30: E128 continuation line under-indented for visual indent
3669:43: E502 the backslash is redundant between brackets
3671:17: E127 continuation line over-indented for visual indent
3676: D401 First line should be in imperative mood ('Create', not 'Creates')
3682: D401 First line should be in imperative mood ('Create', not 'Creates')
3687: D401 First line should be in imperative mood ('Create', not 'Creates')
3692: D401 First line should be in imperative mood ('Create', not 'Creates')
3697: D401 First line should be in imperative mood ('Create', not 'Creates')
3702: D401 First line should be in imperative mood ('Create', not 'Creates')
3707: D401 First line should be in imperative mood ('Create', not 'Creates')
3712: D401 First line should be in imperative mood ('Create', not 'Creates')
3717: D401 First line should be in imperative mood ('Create', not 'Creates')
3722: D401 First line should be in imperative mood ('Create', not 'Creates')
3727: D401 First line should be in imperative mood ('Create', not 'Creates')
3732: D401 First line should be in imperative mood ('Create', not 'Creates')
3739: D401 First line should be in imperative mood ('Create', not 'Creates')
3744: D401 First line should be in imperative mood ('Create', not 'Creates')
3744: D400 First line should end with a period (not ')')
3749: D401 First line should be in imperative mood ('Create', not 'Creates')
3749: D400 First line should end with a period (not ')')
3754: D200 One-line docstring should fit on one line with quotes (found 3)
3762: D200 One-line docstring should fit on one line with quotes (found 3)
3770:22: E201 whitespace after '{'
3777: D202 No blank lines allowed after function docstring (found 1)
3801:25: E126 continuation line over-indented for hanging indent
3807:25: E126 continuation line over-indented for hanging indent
3815:17: E126 continuation line over-indented for hanging indent
3815:26: E203 whitespace before ':'
3819: D401 First line should be in imperative mood ('Return', not 'Returns')
3819: D400 First line should end with a period (not 'd')
3839:9: F841 local variable '_' is assigned to but never used
3841:9: E266 too many leading '#' for block comment
3846: D401 First line should be in imperative mood ('Display', not 'Displays')
3846: D202 No blank lines allowed after function docstring (found 1)
3846: D400 First line should end with a period (not 's')
3846: D205 1 blank line required between summary line and description (found 0)
3881:25: E126 continuation line over-indented for hanging indent
3906:25: E126 continuation line over-indented for hanging indent
3916:33: E126 continuation line over-indented for hanging indent
3919:41: E128 continuation line under-indented for visual indent
3921:41: E128 continuation line under-indented for visual indent
3928:33: E126 continuation line over-indented for hanging indent
3929:45: E128 continuation line under-indented for visual indent
3931:45: E128 continuation line under-indented for visual indent
3943:33: E126 continuation line over-indented for hanging indent
3944:45: E128 continuation line under-indented for visual indent
3947:45: E128 continuation line under-indented for visual indent
3951:45: E128 continuation line under-indented for visual indent
3953:45: E128 continuation line under-indented for visual indent
3956:21: E126 continuation line over-indented for hanging indent
3959: D401 First line should be in imperative mood ('Display', not 'Displays')
3972:9: F841 local variable '_' is assigned to but never used
4022:18: E127 continuation line over-indented for visual indent
4025:48: E222 multiple spaces after operator
4033:5: E303 too many blank lines (2)
4033: D401 First line should be in imperative mood ('Return', not 'Returns')
4033: D400 First line should end with a period (not 'd')
4057:71: E211 whitespace before '('
4064:28: E201 whitespace after '{'
4065:30: E127 continuation line over-indented for visual indent
4067:30: E124 closing bracket does not match visual indentation
4073:68: E211 whitespace before '('
4081: D401 First line should be in imperative mood ('Return', not 'Returns')
4081: D202 No blank lines allowed after function docstring (found 1)
4081: D400 First line should end with a period (not 'd')
4094: D401 First line should be in imperative mood ('Return', not 'Returns')
4094: D202 No blank lines allowed after function docstring (found 1)
4094: D400 First line should end with a period (not 'd')
4107: D401 First line should be in imperative mood ('Return', not 'Returns')
4107: D400 First line should end with a period (not 'e')
4136:17: E122 continuation line missing indentation or outdented
4136:69: E261 at least two spaces before inline comment
4136:70: E262 inline comment should start with '# '
4142:39: E126 continuation line over-indented for hanging indent
4146: D401 First line should be in imperative mood ('Return', not 'Returns')
4146: D400 First line should end with a period (not 'd')
4147:63: E127 continuation line over-indented for visual indent
4160:9: F841 local variable '_' is assigned to but never used
4175: D401 First line should be in imperative mood ('Return', not 'Returns')
4175: D400 First line should end with a period (not 'd')
4189:9: F841 local variable '_' is assigned to but never used
4210: D401 First line should be in imperative mood ('Return', not 'Returns')
4210: D400 First line should end with a period (not 's')
4229:71: E211 whitespace before '('
4230:64: E211 whitespace before '('
4236:38: E201 whitespace after '{'
4237:65: E127 continuation line over-indented for visual indent
4238:57: E202 whitespace before '}'
4242:5: E303 too many blank lines (2)
4242: D401 First line should be in imperative mood ('Return', not 'Returns')
4242: D400 First line should end with a period (not 'd')
4261:30: E261 at least two spaces before inline comment
4261:31: E262 inline comment should start with '# '
4271:69: E211 whitespace before '('
4272:77: E211 whitespace before '('
4277:5: E303 too many blank lines (2)
4277: D401 First line should be in imperative mood ('Return', not 'Returns')
4277: D400 First line should end with a period (not 'd')
4295: D209 Multi-line docstring closing quotes should be on a separate line
4295: D400 First line should end with a period (not 's')
4301: D209 Multi-line docstring closing quotes should be on a separate line
4301: D400 First line should end with a period (not 's')
4307: D209 Multi-line docstring closing quotes should be on a separate line
4307: D400 First line should end with a period (not 'k')
4319:27: E127 continuation line over-indented for visual indent
4324: D102 Missing docstring in public method
4332:24: E127 continuation line over-indented for visual indent
4348:16: E127 continuation line over-indented for visual indent
4381:41: E127 continuation line over-indented for visual indent
4397:60: E127 continuation line over-indented for visual indent
4406:41: E126 continuation line over-indented for hanging indent
4410:57: E127 continuation line over-indented for visual indent
4421: D102 Missing docstring in public method
4424: D102 Missing docstring in public method
4429: D209 Multi-line docstring closing quotes should be on a separate line
4465:49: E127 continuation line over-indented for visual indent
4479:43: E127 continuation line over-indented for visual indent
4488: D400 First line should end with a period (not 'e')
4488: D205 1 blank line required between summary line and description (found 0)
4536: D400 First line should end with a period (not 's')
4549:109: E502 the backslash is redundant between brackets
4550:115: E502 the backslash is redundant between brackets
4551:109: E502 the backslash is redundant between brackets
4552:38: E128 continuation line under-indented for visual indent
4552:46: E502 the backslash is redundant between brackets
4553:38: E128 continuation line under-indented for visual indent
4554:22: E127 continuation line over-indented for visual indent
4557: D401 First line should be in imperative mood ('Return', not 'Returns')
4557: D400 First line should end with a period (not 's')


New relevance tracking pipe is now switched on. Known bugs (least severe to most):
*Green error pixels still occur, though slightly less than before.
*Blocks of terrain disappear/reappear near edge of map (rollover point).
*After 3 level loads, memory runs low and GC lags the VM.
Concentrating on fixing the last one, then looking into deployment tests to investigate AMD omega incompatability.


Any progress on this?


The overloaded method `String makePreparedQueryString(TableMetadata table, EntityMapper<?> mapper, SaveOptions options)` is not used anymore, so we should delete it.


Hi Yuriy,

I think we expect the tables and their content to be fairly dynamic
(adding, removing keys at runtime), so it's not obvious that Mach7
would be a great fit for their.

But we will probably have some static tables (dispatching on protocol
type, for example). Those are usually matched exactly with a switch
statement, or possibly in ranges with a binary search tree. I haven't
seen any examples of static table using wildcard patterns.

That said, extending Mach7 to include wildcard patterns would be
interesting: find the best match for 0b101**101 for example.

Andrew Sutton

On Fri, Jun 12, 2015 at 3:29 AM, Yuriy Solodkyy
<notifications@github.com> wrote:
> Andrew, can Mach7 help with this? I can help you guys with patterns that
> would be useful to your domain and interact with the rest of Mach7 library.
>
> —
> Reply to this email directly or view it on GitHub.


也好，不过感觉  破坏 比 损坏 稍好点。哈哈


Got it working!

Where should I post if I have any other questions?


Test edit to see what the + button does...


helo!


Excelent feature!


nice :+1:


@tchap Hm, looks about the same to me :)


Thanks. Obviously, I got the idea for this bot from you. Hope you don't mind blatant theft of ideas :) You shouldn't really mind, I didn't take any code....as you can tell by the fact it's in a completely different language....


You can also do `for i in (theta.args[0], theta.args[1])`


@bmsatierf hey man, do you need me to translate the **pt** to **en** (*en.yml*) or you will translate it first and then I will review the translation? Sorry, it got lost in translation ;)


Granted, `insert` is a short name, but it's not very meaningful imho; what about `saveStrategy`? BTW `StrategyType` would be better named `SaveStrategyType` while we're at it.


@mbernat :trollface: :+1:


DesignDaysGridView (evanweaver) - x86_64-MacOS-10.9-clang: Tests Failed

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


If a node is in a fgraph, node.fgraph will tell you which one it is. (node
can be an apply node or a variable)

a node (variable or apply node) can be in only 1 fgraph. FunctionGraph(...)
will clone by defaults what he receive.

What error did you get? I think it should have worked.

On Thu, Jun 11, 2015 at 11:27 PM, t13m <notifications@github.com> wrote:

> I think maybe in this test case toposort should not be used, so that
> there's no need to be worried about fgraph changing.
> local_dimshuffle_lift.transform(node) can be used instead.
>
>     def test_recursive_lift(self):
>         v = T.vector(dtype="float64")
>         m = T.matrix(dtype="float64")
>         out = ((v + 42) * (m + 84)).T
>         g = FunctionGraph([v, m], [out])
>         init_str_g = ("[DimShuffle{1,0}(Elemwise{mul,no_inplace}"
>                       "(DimShuffle{x,0}(Elemwise{add,no_inplace}"
>                       "(<TensorType(float64, vector)>, "
>                       "DimShuffle{x}(TensorConstant{42}))), "
>                       "Elemwise{add,no_inplace}"
>                       "(<TensorType(float64, matrix)>, "
>                       "DimShuffle{x,x}(TensorConstant{84}))))]")
>         self.assertTrue(str(g) == init_str_g)
>
>         # call transform function on the output node, get the new output node
>         new_out = local_dimshuffle_lift.transform(out.owner)[0]
>         opt_str_g = ("[Elemwise{mul,no_inplace}(Elemwise{add,no_inplace}"
>                      "(DimShuffle{0,x}(<TensorType(float64, vector)>), "
>                      "DimShuffle{x,x}(TensorConstant{42})), "
>                      "Elemwise{add,no_inplace}(DimShuffle{1,0}"
>                      "(<TensorType(float64, matrix)>), "
>                      "DimShuffle{x,x}(TensorConstant{84})))]")
>
>         # compare new output node's graph with the original one
>         self.assertTrue( str(fgraph_of(new_out)) == opt_str_g )
>
> It may be a stupid question, but is there a "fgraph_of(node)" function in
> theano? I tried to use gof.FunctionGraph([v, m], [new_out]), but some
> errors happened.
>
> Thanks
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/t13m/Theano/commit/f0522bff989f18b358cccce88379b7d2ad4cf573#commitcomment-11647017>
> .
>


On my site, this string is caused by an error when I change the size of the book:
pagesElement.turn ("size", 1000, 500);

Error - no length at undefined

I have corrected myself:
return this.data (). pageMv? this.data (). pageMv.length> 0: false;

Thanks for the plugin!  I hope I helped you :)


I have not looked at them yet, but we could possibly duplicate those intrinsic macros that we need if that would be more portable/predictable then overriding the existing ones. It sounds less hackish anyways :)


`破坏`的意思中带一股“熊孩子把代码改坏了”的感觉，但是`损坏`稍微好一点。确实欠妥当，这里的原意应该是“本来就没写好或者写烂了”


We should be able to normalize any number, for example, `10` should be normalized to `10 - 2*pi` because it falls in `[2*pi, 4*pi)`. For now you can raise a `NotImplementedError`.


I was hoping nobody would notice my insanity! lol!


Are you sure you want to push this? And the MultiRinger?


Previously the changeable parameters were being sent to the target rather than the modified current parameters.


You shouldn't commit this file. It is meant to be generated locally.


Yes, let's keep adding more bullshit since that's the easiest way.
Sadly, I'm not even joking, I'm often doing the same :)


@gorhill you will send this version to chorme store?


This one introduces the test error for `DbusDocumentTest`.


@tchap my standard question when I see twice copy&pasted code: is there no way to abstract this away?


Carelessness.  Though this is still fine for 9 hours of play. :-)


broken 一般泛指 不兼容的变更吧。原文的意思应该是 某些新特性的实现细节可能变更，甚至 spec 发生细节的调整等。


This function should support all real sets instead of just Intervals, for example, `{0, pi, 3*pi}` should return `{0, pi}`. If you don't want to spend time writing a generalized function then check if the input is interval and do your computations, for other real sets raise a `NotImplementedError` and for non real sets raise `ValueError`.


- Additional theme classes moved into separate theming file.
- Keeps optional classes organised in one file for users creating easier setup.
- Brief descriptions should be added for users understanding.


> see meduz@f7e3c48

You need to make it into a PR.

> how do you install that package without that it asks for root privileges?

You don’t. It’s a limitation of it being a pkg.


@akhayrutdinov could we do:
if ( Number.class.isAssignableFrom( classType ) ) {
  return ( ( Number ) value ).longValue()
}

To handle all of the number cases in one if?


Sure, you are correct. The three column file supplied are NOT bed coordinates. These are 1-index, with both positions included. Sorry about the confusion.


Aquí sería bueno mencionar que al crear el Identifier es importante habilitar el servicio de notificaciones push.
![image](https://cloud.githubusercontent.com/assets/313750/8130911/fcb171ec-10ec-11e5-8760-5a2f981e43c1.png)


@akhayrutdinov could we do:
else if ( Number.class.isAssignableFrom( classType ) ) {
  return ( ( Number ) value ).longValue()
}

To handle all of the number cases in one if?


I think, that's a good idea.


Yep, it works :+1:


Offensichtliche Dinge bedürfen keines Kommentars ^^


A futuro yo vendría a editar este post para explicar lo de Amazon SNS antes de rpush (rpush es bastante complejo!)


Once it is released, I will wait a couple of days to confirm there is no bad regression.


Ich würde darauf achten wollen das wir trailing spaces vermeiden. Ich dachte eigentlich das VS 2013 das schon alleine macht... Vielleicht bau ich da mal einen Pre-Commit hook für. Solange müssen wir das wohl noch mit der Hand machen


thanks


It should be built with x86, otherwise pjsip4net assembly will fail to load the x86 pjsip binaries on x64 platforms. The applications using pjsip4net are thus warned that they can only work in x86 WOW64 compatibility mode.

Did you test these builds on x64? Do they work?


sorry, i'm just really oligophrenic these days


@mbernat Let me see...


Valid point.


Where is `Db.VGPU.set_currently_attached` currently set for "real" vGPUs? It's there in `update_pci`, but that's only for passthrough?


I'm nitpicking but I'd prefer `NON_NULL_FIELDS_ONLY` instead of `NOT_NULL_FIELDS`.


for the full file timings, rather than "FULL FILE CHECK", could you set test_name to the test file name? Then it would be unique across test files.


Often you need to worry about checking for null in these situations, but since duration is required you should be fine


hey @NileFrater `null` isn't a valid value in an exit example. It needs to be a string, number, etc.


You probably figured this out already, but this requires adding a matching outer constructor.


On Friday June 12 2015 06:14:39 Hans Kristian Rosbach wrote:
>I have not looked at them yet, but we could possibly duplicate those intrinsic macros that we need if that would be more portable/predictable then overriding the existing ones. It sounds less hackish anyways :)

Was that in reaction to my overriding suggestion? I wasn't suggesting to override the macros, but only to override the mechanism through which those macros are made available only when you pass -msseN etc. to the compiler.
That would only require keeping track of which preprocessor flags the compiler sets that are checked in the respective ?mmintrin.h files.
For instance, gcc and clang use __SSE4_2__ to enable the SSE4.2 intrinsics macros in smmintrin.h . MSVC clearly uses another mechanism, but things work differently there anyway. (Is it even possible to activate the SSE4 set there, or does it come with /ARCH:SSE or whatever the exact syntax is?)


Thanks to Gnome


I don't know yet, likely some object that represents the data about the tile lazily created.


Would be great if that can be merged!


Not correct naming "AdapterSpisok". You should use English words and choose the names which explane the sense of the variable/method/Class-name.


I switched the order of fields to match the order of `Nullable`, but recent changes to the `Nullable` API make me think we should switch all of these constructors back to `NullableArray(data, mask)` order.


s/It the anchor/It's the anchor/


Hi Dom, spotted and removed the duplicated wrapper layer.


@tchap This seems like a weird behavior. Why would you want to stage a release that has only been started and is potentially full of bugs before it was reviewed and tested?


nice.


Awesome. Glad you're hitting code like the `isbits` check that lets you not worry about undefined references in the `values` array.


The message should have been ``for compliance with django 1.8's discoverrunner``


Well, no. But it's been cleaned up in the next commit, already: https://github.com/golgauth/odbc_fdw/commit/c77827eca6d3641666782c7c498d7c4cca50b88b


Why did you change this? They seem to be equivalent and `back()` is shorter/cleaner.
Space is needed after `if`, one space too many before brace.


at the end of self-closing element declararion is good form to use space before "/>"

For instance:

 not


Please update application.yml.example to include example values for:
STUDY_TYPE_QUESTIONS           = config['study_type_questions']
STUDY_TYPE_ANSWERS             = config['study_type_answers']


basic tips about semiconductor\<br>for better review


Is there still another constructor that lets you pass in the mask along with an `AbstractArray` values array?


So the "edit a file in place" is kind of an anti-pattern in chef - the path of least resistance is to check your config files in as templates and substitute values into those.

This whole file probably doesn't need to be managed in the config management because we don't change anything important - we should just check in the file with the current state.


Thanks to Gnome


j'ai fait au départ avec, puis une fois que j'ai su que c'était pas bon, j'ai commencé à les remplacés... mais je n'ai pas tout remplacé. Dans tout les cas le prof ne va pas chercher la petit instruction qui va pas xD


relative imports don't work?


I think the estimated completion time of the update should be displayed. I think under the progress bar might be a good place to display the values. I not sure if this decision belongs to the design team, but for mere mortals that tip could be helpful.


we might want to wait for saveBatch(zones) to resolve before returning zones unless we want it to take place in the background in that case, a comment will make it clear.


@tchap I think this is about fifth time I see this text. Please create a function for it.


Should we maybe support a special nullable literal like `NULL` when using a macro like `@nullable`?


No problem,  I'm not sure how it got left out.

Andrew

________________________________
From: owner-sparc_request@musc.edu [owner-sparc_request@musc.edu] on behalf of robertjamesmiller [notifications@github.com]
Sent: Friday, June 12, 2015 09:34
To: sparc-request/sparc-request
Subject: Re: [sparc-request] Merge pull request #63 from sparc-request/study_type_questionaire (755b000)

Please update application.yml.example to include example values for:
STUDY_TYPE_QUESTIONS = config['study_type_questions']
STUDY_TYPE_ANSWERS = config['study_type_answers']

—
Reply to this email directly or view it on GitHub<https://github.com/sparc-request/sparc-request/commit/755b000c96d21626d274ac512be4cfa0879b2f11#commitcomment-11654095>.


@bhklein Not sure if you had a different idea in mind, but I introduced this to handle the PubFig sigsets where some of the files exist but are empty.


basic tips about semiconductor<br /\>for better review


I would have kept it as Log as otherwise you should write HingeLoss etc...


but it's a nitpick...


Thanks, my migration failed because I didn't have them defined:
rake db:migrate
==  CreateStudyTypeQuestions: migrating =======================================
-- create_table(:study_type_questions)
   -> 0.2795s
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

undefined method `each_with_index' for nil:NilClass/Users/rmjames/git/sparc-request/db/migrate/20150326155450_create_study_type_questions.rb:13:in `change'ENGINE=InnoDB/Users/rmjames/.rvm/gems/ruby-1.9.3-p551/gems/activerecord-3.2.21/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245:in `query'


basic tips about semiconductor
for better review


I was expecting some config to come out of a VGPU object... Is all this encoded in platform keys?


Das nennt man perfekt komplementär :D.


from LOG
<6>SELinux:  Context u:object_r:acurafixril_exec:s0 is not valid (left unmapped).
not working...


@mbernat Tried to do something about it in a following commit. This is bit of a pain in Go, though...


I don't know why this [pull request](https://github.com/rails/rails/pull/20521/files) didn't update the code, but the test in this [commit](https://github.com/dcrec1/rails/commit/584cd13c51d77c773f8d5fcc223dfc948a68f729) shows that is possible to keep this behaviour:

```
model.attribute = value
assert_equal model.attribute, model.tap(&:save).reload.attribute
```

and still fixing the weird behaviour reported in this [issue](https://github.com/rails/rails/issues/20478).

Sorry but this sentence:

    `serialize` makes the contract that if it is given a class name, it will never return
    something other than an instance of that class.

doesn't mean this:

    This means that it must cast `nil` to the empty form of that object.

and again, as I've already shown you, not casting `{}` to `nil` doesn't break this contract:

    ```
    model.attribute = value
    assert_equal model.attribute, model.tap(&:save).reload.attribute
    ```

About your commit, sorry but I think some things are wrong.

First of all, the test name says you're testing a thing, but you're testing another different thing. A correct test for your test name would be:

    ````
    Topic.serialize(:content, Hash)
    topic = Topic.create!(content: nil)
    assert_equal [topic], Topic.where(content: nil)
    ````

This test wouldn't break with my commit.

Secondly, you're commenting in your test that you're testing something to fulfil a contract, but your code is not testing this contract neither has a relation with this contract. If you want to guarantee this contract, then test the contract, not another thing. Sorry if you're tired of hearing this, but just to be in the same page, this contract is already tested in the commit I sent:

https://github.com/dcrec1/rails/commit/584cd13c51d77c773f8d5fcc223dfc948a68f729#diff-d5fc467bd1cb0f9a9b1f8f2dec3ab8c8R284

What you're really testing is that an empty serialized attribute is persisted as `nil`. This doesn't make any sense, an empty hash is different from no hash at all.


thus, please either add a rollback to drop table study_type_questions or check that STUDY_TYPE_QUESTIONS has been defined.


this is a bit confusing, it doesn't look like c... (maybe k&r but no one sane uses it ;)
why can't this be "void set_name(const char *my_name)" ?


@tchap no problem, I thought it might not be easy. You did a good job though.


Well, it seemed unnecessary at the time.


This is a good idea. I think that there will be additional properties coming that could be placed there, too.

In the end, wouldn't it make sense to dump the analysis-collector plug-in (or a part of it) and move functionality to your new plug-in?

E.g. : https://wiki.jenkins-ci.org/download/attachments/42469302/Bildschirmfoto+2014-03-09+um+17.16.57.png?version=1&modificationDate=1394381957000
or
https://wiki.jenkins-ci.org/download/attachments/42469302/warnings-portlet-icons.png?version=1&modificationDate=1268977552000

I startet this issue already quite some time ago but actually never managed it it finish it. The current state of this experiment is visible in https://issues.jenkins-ci.org/browse/JENKINS-17168 and https://github.com/jenkinsci/analysis-core-plugin/tree/JENKINS-17168 (especially https://github.com/jenkinsci/analysis-core-plugin/blob/JENKINS-17168/src/main/java/hudson/plugins/analysis/collector/AnalysisPlugin.java)


@bittorf Can you add this to the for-14.07 branch, too? tia!


s/we can be double-check/we can double-check/


@mbernat Ok, there is obviously this making sure that the release can be staged as point 1, will modify the message...


Now this is some good looking and accurate test.


Yea that seems better. It's a weird one to name.


:+1: :)


@cooldeeparmar Please create an issue instead to comment a commit. It is very difficult to track this way.

Anyway I am pretty sure that you missed the `use fedemotta\datatables\DataTables;` as the documentation says.


@jonuy just made all edits - let me know if I can merge!


checked - all good


Thanks for the heads up.  I took care of it slightly differently so as not to expose the tmpl variable which I sort of consider internal.


This line needs to get fixed (I think there's a later commit that removes it?)


> Just compiled without .iter() without problems. Release notes about this change can be found here:
>
> - https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-100-alpha2-february-2015

Thanks for the link, @oblitum. I wasn't aware of all behaviours. I'm aware now, but the code still looks fine (`contacts` is taken by copy, so no hidden side-effects).


@mbernat Fixed.


On 12/06/2015 15:22, Vítor Galvão wrote:
>
>     see meduz@f7e3c48
>     <https://github.com/meduz/homebrew-cask/commit/f7e3c48>
>
> You need to make it into a PR.
>

ok, see https://github.com/caskroom/homebrew-cask/pull/11856
>
>     how do you install that package without that it asks for root
>     privileges?
>
> You don’t. It’s a limitation of it being a pkg.
>

dooh.


А никак нельзя сказать latest?


Fixed https://github.com/enaqx/awesome-react/commit/3541173bf11391d7ae8fa3e2a1d90c95170bc302


The error was
```
MissingInputError: A variable that is an input to the graph was neither provided as an input to the function nor given a value. A chain of variables leading from this input to an output is [<TensorType(float64, matrix)>, DimShuffle{1,0}.0, Elemwise{add,no_inplace}.0, Elemwise{mul,no_inplace}.0]. This chain may not be unique
Backtrace when the variable is created:
  File "<ipython-input-2-b090bb7461d9>", line 8, in <module>
    m = T.matrix(dtype="float64")
```

I think it was because that `FunctionGraph` clone the inputs and outputs, so when it is called like `gof.FunctionGraph([v, m], [new_out])`, `new_out` and `[v, m]` are not in same graph, so error happened. I use `FunctionGraph(g.inputs, [new_out])` in the new commit instead.

Thanks


With this PR, the startup behaviour is:

* xapi (pool level) - assign VGPUs to PGPUs and add the platform keys to the VM
* xapi (host level) - convert these platform keys into the nice types and send it down to xenopsd

Previously, the platform keys were what got sent down to xenopsd and it had to reconstruct them. I think this is an improvement but still not ideal - I'm trying to find a better way to do this with the GVT-g specific stuff I'm working on now.


The link text should probably also be adjusted.


Découpage du HTML dans le forms.py (UpdatePasswordForm)
Ajout de la traduction


Thanks! :+1:


Thanks – just pushed a fix for these specs.


DesignDaysGridView (evanweaver) - x86_64-Linux-Ubuntu-14.04-clang-3.5: Build Failed

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


"to persistent memory/storage" sounds better


`Log` just felt to close from np.log...
anyway, I reverted


ok


You're assuming that `serialize` can only be used with `Hash`, which happens to not be a useable value for a query. Here's another example.

```ruby
Address = Struct.new(:street, :city, :state, :country)

class Person < ActiveRecord::Base
  serialize :address, Address
end

Person.where(address: Address.new) # => SELECT * FROM people WHERE addresses IS NULL
```

Your proposed change would break that behavior. As I've said before, I'm sorry that you disagree with the current behavior. I'm not fond of it either. However, I have not seen a compelling enough use case to make a breaking change to it, especially given that we're actively discouraging the feature for new apps. The desire to separate an empty hash from nil is not a compelling enough use case. You would not be able to query for the empty hash, and you would not be able to distinguish between them after reading from the database since `nil` would still be cast to an empty hash.

Please understand that I'm not trying to be dismissive. I've heard your concerns. You're not the first one to have raised them on this issue. But I feel like I've thoroughly explained why we will not be accepting that change at this time, and have not accepted it in the past multiple times now.


I *think* you've now marked everything as cachable, and we could be [serving stale responses](https://tools.ietf.org/html/rfc7234#page-15)?

Did you mean to use `private` and / or `must-revalidate`?


In practice, any error will come from qb_ipcc_connect(), which will set errno, so crm_perror() will give enough information to see what went wrong.

crm_ipc_get_fd() can theoretically return EINVAL but it'll never show up in practice (it would have to be a bug in the caller). I assumed that since the existing code called crm_perror() if that failed that it set errno too, but it actually does not, so I'll fix that at some point.


I was conservative on the changes for this first commit.

Thread will own `event_receiver` and it seems this is the only place where it is used. So it's fine to remove `.iter()`.


LGTM


lgtm


I tried this before adding a .pxd...
It does work now with relative import.


Maybe we can place the upgrade info across all versions into a separate document discoverable via the side bar and a pointer in this paragraph? What do you think?


Haven't tried it out yet but it reads well :+1:
Also it might be noted that in these special grammars you can't specify two spoken variations to perform the same action, I think only one spoken command will be available per action even if the .json includes several.


Sounds good. It's just confusing to see upgrade instructions for older versions without upgrade instructions for the current version. A single doc (linked on the sidebar, and in this paragraph) sounds great!


ok @gorhill thanks


That makes sense, would do that in the next commit.


In case someone looks at this commit, it's PR #7087. Referenced the old one.


Oh, no, it's fine. Everyone needs some inspiration.


This would load the entire log file into the memory every time its changed, no? Anyway to do it better?


所以应该如何翻译……


You could npm install -g origami-build-tools@beta as this is a beta as well


@A-Shahbazi,

> the issue strangely begins just from 0.7.26.20141003.1-signed!

What issue? The label looks correct (on one line with "about:addons" label). Please provide more details:
* OS.
* DE if you use GNU/Linux.
* Screnshot like my below (with Search bar).
* Screenshot with disabled/removed extension.

I tested latest version with Firefox 38.0.5 and all looks fine except color maybe (Arch Linux, GNOME):
![screenshot from 2015-06-12 19-45-14](https://cloud.githubusercontent.com/assets/1687481/8131526/392faebc-1134-11e5-9c8f-a76347c45834.png)


Why not the function directly?


could you define "localhost:19000" as a constant ?


What nodes should be added into failed_list? only elemwise nodes in for loop (line 245), or their inputs and outputs (line 270, 271)?


True - though it does mean we'll need to spec behavior for <bookid>@<ver>:<pageid>@<ver-not-in-book>
I guess we need to in any case - the obvious behavior being "ignore the page version"


```javascript
`${}`
```


Hello, @dshvedchenko

Corresponding issue is closed (http://jira.pentaho.com/browse/BISERVER-12360).
You should create new one in order to implement your changes. You also can attach patch to new one.


To know if the checkbox was left unchecked.
Without this there is no difference in unchecked checkbox and no checkbox. And we need to know precisely if it was there and unchecked to disable foreign key checks.


good


You may want to rebase it with current master:

```powershell
cd into\corefx
git remote add corefx https://github.com/dotnet/corefx
git pull --rebase corefx master
git push -f
```

BTW is it ready for the PR? ::)


yeah, agreed.


If I'm not mistaken, phylip's consense is not used anymore, so we don't have to install phylip.
Also attempting to install nlopt as a package, to shorten installation time.
On travis, we have 50 minutes for running puppet, installing the cpan dependencies and running the tests.  Our runs take always around 50 minutes;  if we're lucky it works, otherwise we get a timeout error. This is annoying. I hope this quickens the puppet run a bit.


DesignDaysGridView (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


You need a new list:
changed_node_since_validate=[]
You should put in the failed_list all the node in that list + the current node.


ok you're right


Need warning style for #24


Translate with a parameter this.i1_n('message', param)


Please Updates


You have committed Teclib color hack on an unrelated fix.
Please revert !


Because I prefer calling `numberFormatter.format(number)` than calling `numberFormatter(number)`


I think logging to avocado.test should be enough for information purposes. Let me test it here.


@amadeus Hmm. It's been awhile (and a few newer versions of XCode) since I last built this so I'm not immediately sure what the problem you're encountering might be. I've turned on Issues in this repository so if you wouldn't mind it'd be great if you could sent a bug report with more information about your system setup, what you've attempted to do, and full error messages.

In the meantime, there is a compiled version of the plugin available at https://github.com/bmcmurray/Adinline/downloads


This was wrong, you should only put AssemblyVersion here


I'm wondering what this is used for? I couldn't find it being used in this module


nit: space after `for`


Great!!!


note: does for...of work in node? I think the build scripts are meant to work in both node and xpcshell, but not sure


Hi Michel,

If I install the RestServices module in Mendix version 5.16 I cannot run my project anymore ('compilation of Java actions failed'). I think this has to do with the file I have to overrun when adding this module (userlib\commons-httpclient-3.1.jar). Could you help me make the Restservices compatible in Mendix 5.16? Thanks!

Mark


This looks pretty cool can i try it out?


same "node" remark here. But maybe we don't really care ?


@lmr should we expect a new version with the dual inheritance?


Adaur,

Just a word of caution - the regex parser can blow up when confronted with a
large text input (post) having a certain composition. If you decide to use
this parser, I would stongly recommend limiting the maximum post size to
32KB. The 1.4.5 FluxBB version has a post size limit == 1MB which is TOO
BIG.

Jeff

----- Original Message -----
From: "adaur" <notifications@github.com>
To: "featherbb/featherbb" <featherbb@noreply.github.com>
Cc: "Jeff Roberson" <widgewunner@gmail.com>
Sent: Thursday, June 11, 2015 3:26 PM
Subject: [featherbb] Add new parser (231184a)

> Add new parser
>
> Thanks to @ridgerunner
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/featherbb/featherbb/commit/231184ab41c70123553faf1ddb021a3ff7f2ba92


almost, since I did a lot of refactoring, I'm going over it again to make sure I didn't make any mistakes.   I've got something going on today, so I suspect I'll have it ready either tonight or tomorrow.
 And yes I'll rebase it before doing the PR


What is "x" in debug=x?


typo


fix #2


Rubocop ne le fait pas déjà ?


I was specified, that is should be 2 types of offers: standard and premium. My idea was to use single boolean value "premium".


`format` seems to be a special name


Ok


Woo! :+1: :+1: :+1: :+1:


|| tf-idf | tf |
| ---- | ---- | ---- |
| delStopwords, lemmatize | 0.109126689198 | 0.0883092245275 |
| delStopwords | 0.109149179354 | 0.0903570432903 |
| lemmatize | 0.103440885264 | 0.0463208771413 |
| no options | 0.101778833083 | 0.0431799440003 |


@mjwitte @kbenne Just letting you know I started the v8.4.0 branch over here in case you make any changes toward the v8.4.0 release.


OK


Hi Edwin,

This module isn't finished yet and the debug values are temporary.
On 13/06/2015 12:08 AM, "Edwin Chiu" <notifications@github.com> wrote:

> What is "x" in debug=x?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/wimnat/ansible-modules/commit/4d2c2d2e103be806558d4fec412ea77cab889953#commitcomment-11654713>
> .
>


you could also use : `Array.from(mockScripts).forEach(mockScript => mockScript.remove())` (or `Array.from(mockScripts).forEach(HTMLElement.prototype.remove.bind)` :D )


ah no sorry the last one doesn't work :D


he was born and died on the same day so it's a moot point


thanks!


Why don't you push your patches to CM's git


Nice catch on the PhantomJS error. This seems like a good fix.

One important note: instead of including the username/password in the `drainHost` string, we should set `drainUsername` and `drainPassword` separately, along with `{ drainType: 'elasticsearch' }` (see [app/models/log_drain.rb](https://github.com/aptible/api.aptible.com/blob/master/app/models/log_drain.rb) in API for context). This probably requires adding `drainUsername` and `drainPassword` to the attributes to the Ember model: [app/models/log_drain.rb](https://github.com/aptible/ember-cli-aptible-shared/blob/master/app/models/log_drain.js) in ember-cli-aptible-shared.


Is this error stream actually needed? It doesn't seem to be used


Hmmm, yes, I guess.


Bah ouais, puis ça fait gagner du temps, ils autorisent la qui se traduit par 3 instructions, pourquoi pas le reste? :°


One thing I am myself wondering is ... should this be re-jigged to avoid the `$password_required_msg` being truncated (where someone customizes it to a length exceeding the cut off for truncation)?


Did you draw this??


You have the right explanation.


I'm not assuming that `serialize` can only be used with `Hash`, sorry for the misunderstanding.

About your example, who does this and where it's documented and why is not tested? In either case, this shouldn't break with my commit and if it's breaking, I may be able to fix it.

Again, the pull request is not a breaking change. There is no test neither any documentation that says that the current behaviour is working as expected.

About `serialized` being deprecated, I know it will be replaced by `ActiveRecord::Attributes`, but this behaviour will continue is this new model, as the real problem is in the dirty module who's not recognising the value as changed.

About this sentences:

    The desire to separate an empty hash from nil is not a compelling enough use case.
    You would not be able to query for the empty hash, ...

Sure I will not be able to query for an empty hash, but I will be able to query for values different than `nil` and  if I persisted a not `nil` value, I expect the query to return that records with a not `nil` value. Basically, this is the current behaviour:

     Topic.create! content: {}
     Topic.where("content is not null").count # 0 Records

Isn't this weird? We can fix this without breaking anything.


<script>alert('FFFF')</script>


co to ma byc?


the method name was fine I think; @jmchilton was probably referring to the argument name which is camelCase (unlike the rest of the Galaxy)


@Swapnil133609 you did not author this -_-


Remove console.info?


@sunilkumarr honeycomb is version 11, this checknisbfor version 8


> Isn't this weird?

I'd say quirky, but yes.

> We can fix this without breaking anything.

Changing this behavior could absolutely break for anybody who is relying on it. I don't know how else to express this to you.


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 543](http://build.prxm.it:8811/viewLog.html?buildId=3005&buildTypeId=Jarvis_DocumentStore_CI) is now running


83811490-Fault_DirtyAirFilter (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


ho


@valerandanne


@Swapnil133609 give credits to author -_-


Si, mais comme j'avais un probleme d'installation des hooks chez moi ca marchait pas, du coup j'ai tente ca, mais j'ai resolu le probleme d'installation, du coup j'ai re push -f au commit precedent.


Creating Repo


Indeed, that's only for passthrough. It doesn't look like the old code ever sets currently_attached to true for "real" vGPUs :disappointed:


did you mean to add this?


[fiverr.com](http://fiverr.com) FTW!


awesomeness!


Have you seen gulp-html-validator? Might be what you want: https://github.com/hoobdeebla/gulp-html-validator


This shouldn't be necessary; this function is local to the `let` block but somehow something earlier in the file is making it global.


@hazmi, what version of NPM are you using?


thanks for the info. i liked your output (and not touching the stream), whick gulp-html-validator does not provide


Why is that? Because of ref counting?


shouldn't you still return this ?


TeamCity Jarvis :: Jarvis.DocumentStore :: Debug / Test / Release [Build 543](http://build.prxm.it:8811/viewLog.html?buildId=3005&buildTypeId=Jarvis_DocumentStore_CI) outcome was **SUCCESS**
Summary: Tests passed: 201 Build time: 00:05:53


removed already


Fair enough. See this, too: https://github.com/thomasdavis/w3cjs/issues/17


It's Author is Me -_-


should dayDiff be global?


would be nice if you could condense


Are you nuts -_- I modified evrything -_-


DesignDaysGridView (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2186 of 2213 tests passed)

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


Nice.


Good coverage.


`===` is prefered.


woooopppppssss


Already reviewed, LGTM.


You forgot to actually delete the "vc++" directory from the repository :)


83811490-Fault_DirtyAirFilter (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1672 of 1672 tests passed)

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


not a massive deal but checking 'http$' first would be cheaper


Can't this use the `requirements.txt` file somehow?


public class ProyectoFinal{
public static void main(Stromng [] args){
system.out.println("hola mundo esto es mi primir proyecto en github");
system.out.println("Pariona Huaraca wilber");

}
}


Why do you normalize the half vector? If I understand you correctly, the method returns the vector which has the same distance to both supplied vectors. Wouldn't you rather use `this.add(other).mul(0.5)`?


I guess this is lacking a way to show the infringements, so people have an easier time fixing the offenders.


TeamCity Azmq :: Build (OSX) [Build 103](https://78.46.71.115/viewLog.html?buildId=558&buildTypeId=Azmq_BuildOsx&guest=1) is now running


TeamCity Azmq :: Build (Linux) [Build 119](https://78.46.71.115/viewLog.html?buildId=557&buildTypeId=Azmq_BuildLinux&guest=1) is now running


TeamCity Azmq :: Build (Windows) [Build 150](https://78.46.71.115/viewLog.html?buildId=559&buildTypeId=Azmq_Build&guest=1) is now running


TeamCity Azmq :: Build (Linux) [Build 119](https://78.46.71.115/viewLog.html?buildId=557&buildTypeId=Azmq_BuildLinux&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 19 Build time: 00:00:07


TeamCity Azmq :: Build (OSX) [Build 103](https://78.46.71.115/viewLog.html?buildId=558&buildTypeId=Azmq_BuildOsx&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 19 Build time: 00:00:13


TeamCity Azmq :: Build (Windows) [Build 150](https://78.46.71.115/viewLog.html?buildId=559&buildTypeId=Azmq_Build&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 19 Build time: 00:00:18


@st3v / @goonzoid - do you think we should make a new method for this that the client implements? ProvisonAsync? Currently this implementation is a breaking change for users of the Library (we are on a branch), but adding a new method to the interface would also be a breaking change right? Perhaps another interface? Maybe we can have a brainstorm when we are free, want to keep this high quality.

I am thinking the web handler can decide which client method to call based on the accepts incomplete flag on the provision.


1: M111 unrecognized component name: legacy


1: M111 unrecognized component name: oauth2server


26:1: F401 'CFG_DEVEL_SITE' imported but unused
80: D102 Missing docstring in public method
109: D209 Multi-line docstring closing quotes should be on a separate line
109: D203 1 blank line required before class docstring (found 0)
109: D400 First line should end with a period (not 'f')
109: D205 1 blank line required between summary line and description (found 0)
115: D102 Missing docstring in public method
169: D102 Missing docstring in public method
177: D210 No whitespaces allowed surrounding docstring text
177: D209 Multi-line docstring closing quotes should be on a separate line
177: D203 1 blank line required before class docstring (found 0)
177: D400 First line should end with a period (not 'l')
177: D205 1 blank line required between summary line and description (found 0)
207: D102 Missing docstring in public method
233: D102 Missing docstring in public method


80: D102 Missing docstring in public method
109: D209 Multi-line docstring closing quotes should be on a separate line
109: D203 1 blank line required before class docstring (found 0)
109: D400 First line should end with a period (not 'f')
109: D205 1 blank line required between summary line and description (found 0)
115: D102 Missing docstring in public method
175: D102 Missing docstring in public method
183: D210 No whitespaces allowed surrounding docstring text
183: D209 Multi-line docstring closing quotes should be on a separate line
183: D203 1 blank line required before class docstring (found 0)
183: D400 First line should end with a period (not 'l')
183: D205 1 blank line required between summary line and description (found 0)
214: D102 Missing docstring in public method
245: D102 Missing docstring in public method