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_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
70:1: E402 module level import not at top of file
71:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.legacy.dbquery
71:1: E402 module level import not at top of file
72:1: I100 Imports statements are in the wrong order. from invenio.base.globals should be before from invenio.base.i18n
72:1: E402 module level import not at top of file
73:1: I101 Imported names are in the wrong order. Should be create_html_link, create_url, drop_default_urlargd, make_canonical_urlargd
73:1: E402 module level import not at top of file
74:1: I100 Imports statements are in the wrong order. from invenio.utils.html should be before from invenio.utils.url
74:1: E402 module level import not at top of file
75:1: I100 Imports statements are in the wrong order. from invenio.ext.legacy.handler should be before from invenio.utils.html
75:1: E402 module level import not at top of file
76:1: E402 module level import not at top of file
77:1: E402 module level import not at top of file
79:1: I100 Imports statements are in the wrong order. from intbitset should be before from invenio.modules.formatter
79:1: F401 'intbitset' imported but unused
79:1: E402 module level import not at top of file
81:1: E402 module level import not at top of file
86:1: E302 expected 2 blank lines, found 1
86: D101 Missing docstring in public class
120:34: E261 at least two spaces before inline comment
124: D102 Missing docstring in public method
134:13: E203 whitespace before ':'
137:32: E203 whitespace before ':'
138:32: E203 whitespace before ':'
139:32: E203 whitespace before ':'
140:32: E203 whitespace before ':'
141:32: E203 whitespace before ':'
142:32: E203 whitespace before ':'
143:32: E203 whitespace before ':'
145:32: E203 whitespace before ':'
146:32: E203 whitespace before ':'
147:32: E203 whitespace before ':'
149:32: E203 whitespace before ':'
150:32: E203 whitespace before ':'
151:32: E203 whitespace before ':'
152:32: E203 whitespace before ':'
155:13: E126 continuation line over-indented for hanging indent
155:17: E203 whitespace before ':'
156:20: E203 whitespace before ':'
157:21: E203 whitespace before ':'
158:22: E203 whitespace before ':'
159:21: E203 whitespace before ':'
160:22: E203 whitespace before ':'
161:22: E203 whitespace before ':'
162:19: E203 whitespace before ':'
163:20: E203 whitespace before ':'
164:20: E203 whitespace before ':'
165:19: E203 whitespace before ':'
166:19: E203 whitespace before ':'
167:19: E203 whitespace before ':'
168:20: E203 whitespace before ':'
169:21: E203 whitespace before ':'
170:21: E203 whitespace before ':'
171:21: E203 whitespace before ':'
172:19: E203 whitespace before ':'
173:20: E203 whitespace before ':'
174:20: E203 whitespace before ':'
175:20: E203 whitespace before ':'
176:20: E203 whitespace before ':'
177:21: E203 whitespace before ':'
178:19: E203 whitespace before ':'
179:18: E203 whitespace before ':'
180:22: E203 whitespace before ':'
181:22: E203 whitespace before ':'
182:22: E203 whitespace before ':'
183:26: E203 whitespace before ':'
184:21: E203 whitespace before ':'
185:25: E203 whitespace before ':'
186:24: E203 whitespace before ':'
187:25: E203 whitespace before ':'
188:25: E203 whitespace before ':'
189:23: E203 whitespace before ':'
190:25: E203 whitespace before ':'
191:24: E203 whitespace before ':'
192:24: E203 whitespace before ':'
193:24: E203 whitespace before ':'
194:24: E203 whitespace before ':'
195:28: E203 whitespace before ':'
196:23: E203 whitespace before ':'
197:24: E203 whitespace before ':'
198:25: E203 whitespace before ':'
199:26: E203 whitespace before ':'
200:25: E203 whitespace before ':'
201:26: E203 whitespace before ':'
202:26: E203 whitespace before ':'
203:27: E203 whitespace before ':'
204:21: E203 whitespace before ':'
205:25: E203 whitespace before ':'
206:23: E203 whitespace before ':'
207:24: E203 whitespace before ':'
208:23: E203 whitespace before ':'
209:24: E203 whitespace before ':'
210:24: E203 whitespace before ':'
211:22: E203 whitespace before ':'
212:26: E203 whitespace before ':'
213:23: E203 whitespace before ':'
214:25: E203 whitespace before ':'
215:23: E203 whitespace before ':'
216:25: E203 whitespace before ':'
217:24: E203 whitespace before ':'
218:22: E203 whitespace before ':'
219:26: E203 whitespace before ':'
220:25: E203 whitespace before ':'
221:25: E203 whitespace before ':'
227: D210 No whitespaces allowed surrounding docstring text
227: D400 First line should end with a period (not 'a')
227: D205 1 blank line required between summary line and description (found 0)
234:17: E266 too many leading '#' for block comment
273:17: F841 local variable 'pmid' is assigned to but never used
275:17: F841 local variable 'bibcode' is assigned to but never used
277:17: F841 local variable 'oai' is assigned to but never used
283:9: E266 too many leading '#' for block comment
287:18: E127 continuation line over-indented for visual indent
288:18: E127 continuation line over-indented for visual indent
289:18: E127 continuation line over-indented for visual indent
289:76: E271 multiple spaces after keyword
298:9: E266 too many leading '#' for block comment
300:17: E127 continuation line over-indented for visual indent
301:17: E127 continuation line over-indented for visual indent
302:17: E127 continuation line over-indented for visual indent
303:17: E127 continuation line over-indented for visual indent
310:9: E266 too many leading '#' for block comment
312:18: E127 continuation line over-indented for visual indent
313:18: E127 continuation line over-indented for visual indent
314:18: E127 continuation line over-indented for visual indent
318:13: F841 local variable 'journal_query' is assigned to but never used
320:9: E266 too many leading '#' for block comment
322:16: E127 continuation line over-indented for visual indent
331:9: E266 too many leading '#' for block comment
333:16: E127 continuation line over-indented for visual indent
334:16: E127 continuation line over-indented for visual indent
335:16: E127 continuation line over-indented for visual indent
339:13: F841 local variable 'issn_query' is assigned to but never used
341:9: E266 too many leading '#' for block comment
348:9: E266 too many leading '#' for block comment
349:18: E261 at least two spaces before inline comment
349:19: E262 inline comment should start with '# '
354:9: E266 too many leading '#' for block comment
358:24: E203 whitespace before ':'
359:25: E203 whitespace before ':'
360:25: E203 whitespace before ':'
364:24: E203 whitespace before ':'
365:25: E203 whitespace before ':'
366:25: E203 whitespace before ':'
370:24: E203 whitespace before ':'
371:25: E203 whitespace before ':'
372:25: E203 whitespace before ':'
376:24: E203 whitespace before ':'
377:25: E203 whitespace before ':'
378:25: E203 whitespace before ':'
383:24: E203 whitespace before ':'
384:25: E203 whitespace before ':'
385:25: E203 whitespace before ':'
388:24: E203 whitespace before ':'
389:25: E203 whitespace before ':'
390:25: E203 whitespace before ':'
392:9: E266 too many leading '#' for block comment
395:20: E203 whitespace before ':'
396:21: E203 whitespace before ':'
397:21: E203 whitespace before ':'
400:20: E203 whitespace before ':'
401:21: E203 whitespace before ':'
402:21: E203 whitespace before ':'
404:13: E266 too many leading '#' for block comment
406:25: E126 continuation line over-indented for hanging indent
406:28: E203 whitespace before ':'
407:29: E203 whitespace before ':'
408:29: E203 whitespace before ':'
410: D210 No whitespaces allowed surrounding docstring text
410: D401 First line should be in imperative mood ('Return', not 'Returns')
410: D200 One-line docstring should fit on one line with quotes (found 2)
430:3: E128 continuation line under-indented for visual indent
440: D210 No whitespaces allowed surrounding docstring text
440: D202 No blank lines allowed after function docstring (found 1)
440: D400 First line should end with a period (not 'h')
440: D205 1 blank line required between summary line and description (found 0)
472: D210 No whitespaces allowed surrounding docstring text
472: D202 No blank lines allowed after function docstring (found 1)
496: D202 No blank lines allowed after function docstring (found 1)
496: D400 First line should end with a period (not 'L')
523: D202 No blank lines allowed after function docstring (found 1)
523: D400 First line should end with a period (not 's')
533:17: E127 continuation line over-indented for visual indent
548:5: E303 too many blank lines (2)
548: D401 First line should be in imperative mood ('Create', not 'Creates')
548: D400 First line should end with a period (not ')')
569: D210 No whitespaces allowed surrounding docstring text
569: D401 First line should be in imperative mood ('Create', not 'Creates')
569: D201 No blank lines allowed before function docstring (found 1)
569: D202 No blank lines allowed after function docstring (found 1)
602:20: E126 continuation line over-indented for hanging indent
605:16: E126 continuation line over-indented for hanging indent
611:27: E201 whitespace after '{'
611:42: E203 whitespace before ':'
611:57: E202 whitespace before '}'
618:44: E203 whitespace before ':'
621: D401 First line should be in imperative mood ('Create', not 'Creates')
621: D400 First line should end with a period (not 's')
621: D205 1 blank line required between summary line and description (found 0)
633:38: E203 whitespace before ':'
633:66: E203 whitespace before ':'
637: D401 First line should be in imperative mood ('Produce', not 'Produces')
637: D202 No blank lines allowed after function docstring (found 1)
638:54: E261 at least two spaces before inline comment
667:9: E303 too many blank lines (2)
668:21: E127 continuation line over-indented for visual indent
676:84: E251 unexpected spaces around keyword / parameter equals
680:85: E502 the backslash is redundant between brackets
719:35: E231 missing whitespace after ':'
720:35: E231 missing whitespace after ':'
725:73: E502 the backslash is redundant between brackets
737:87: E502 the backslash is redundant between brackets
771:20: E203 whitespace before ':'
772:29: E203 whitespace before ':'
774:25: E203 whitespace before ':'
775:25: E203 whitespace before ':'
776:24: E203 whitespace before ':'
777:28: E203 whitespace before ':'
778:28: E203 whitespace before ':'
779:33: E203 whitespace before ':'
785: D401 First line should be in imperative mood ('Produce', not 'Produces')
785: D202 No blank lines allowed after function docstring (found 1)
816:9: E303 too many blank lines (2)
817:21: E127 continuation line over-indented for visual indent
848:20: E203 whitespace before ':'
849:29: E203 whitespace before ':'
851:25: E203 whitespace before ':'
852:25: E203 whitespace before ':'
853:24: E203 whitespace before ':'
854:31: E203 whitespace before ':'
855:28: E203 whitespace before ':'
856:28: E203 whitespace before ':'
857:33: E203 whitespace before ':'
861: D401 First line should be in imperative mood ('Produce', not 'Produces')
861: D202 No blank lines allowed after function docstring (found 1)
861: D208 Docstring is over-indented
862:36: E261 at least two spaces before inline comment
913:9: E303 too many blank lines (2)
914:18: E128 continuation line under-indented for visual indent
960:20: E203 whitespace before ':'
961:29: E203 whitespace before ':'
963:25: E203 whitespace before ':'
964:25: E203 whitespace before ':'
965:24: E203 whitespace before ':'
967:29: E203 whitespace before ':'
968:33: E203 whitespace before ':'
969:30: E203 whitespace before ':'
971:29: E203 whitespace before ':'
972:33: E203 whitespace before ':'
973:30: E203 whitespace before ':'
975:29: E203 whitespace before ':'
976:33: E203 whitespace before ':'
978:28: E203 whitespace before ':'
979:28: E203 whitespace before ':'
980:33: E203 whitespace before ':'
997:24: E126 continuation line over-indented for hanging indent
997:38: E203 whitespace before ':'
998:39: E203 whitespace before ':'
999:22: E126 continuation line over-indented for hanging indent
1044:21: E126 continuation line over-indented for hanging indent
1044:28: E203 whitespace before ':'
1045:28: E203 whitespace before ':'
1047:33: E203 whitespace before ':'
1048:33: E203 whitespace before ':'
1050:31: E203 whitespace before ':'
1051:34: E203 whitespace before ':'
1052:33: E203 whitespace before ':'
1053:34: E203 whitespace before ':'
1054:34: E203 whitespace before ':'
1055:37: E203 whitespace before ':'
1056:36: E203 whitespace before ':'
1057:19: E126 continuation line over-indented for hanging indent
1061:5: E303 too many blank lines (2)
1061: D202 No blank lines allowed after function docstring (found 1)
1061: D400 First line should end with a period (not 'e')
1061: D205 1 blank line required between summary line and description (found 0)
1082:18: E127 continuation line over-indented for visual indent
1088:37: E128 continuation line under-indented for visual indent
1088:42: E261 at least two spaces before inline comment
1089:37: E128 continuation line under-indented for visual indent
1089:43: E261 at least two spaces before inline comment
1090:37: E128 continuation line under-indented for visual indent
1091:37: E128 continuation line under-indented for visual indent
1092:37: E128 continuation line under-indented for visual indent
1096:5: E303 too many blank lines (2)
1096: D401 First line should be in imperative mood ('Create', not 'Creates')
1096: D202 No blank lines allowed after function docstring (found 1)
1148:27: E203 whitespace before ':'
1148:18: E225 missing whitespace around operator
1167:26: E203 whitespace before ':'
1168:16: E203 whitespace before ':'
1169:21: E203 whitespace before ':'
1170:22: E203 whitespace before ':'
1189:14: E225 missing whitespace around operator
1191:24: E203 whitespace before ':'
1192:31: E126 continuation line over-indented for hanging indent
1192:35: E251 unexpected spaces around keyword / parameter equals
1192:37: E251 unexpected spaces around keyword / parameter equals
1193:36: E251 unexpected spaces around keyword / parameter equals
1193:38: E251 unexpected spaces around keyword / parameter equals
1194:33: E251 unexpected spaces around keyword / parameter equals
1194:35: E251 unexpected spaces around keyword / parameter equals
1195:29: E126 continuation line over-indented for hanging indent
1196:24: E203 whitespace before ':'
1197:26: E203 whitespace before ':'
1198:28: E203 whitespace before ':'
1199:28: E203 whitespace before ':'
1204:5: E303 too many blank lines (2)
1204: D401 First line should be in imperative mood ('Return', not 'Returns')
1204: D202 No blank lines allowed after function docstring (found 1)
1204: D208 Docstring is over-indented
1227:22: E203 whitespace before ':'
1228:22: E203 whitespace before ':'
1229:60: E127 continuation line over-indented for visual indent
1229:66: E203 whitespace before ':'
1230:22: E203 whitespace before ':'
1231:60: E127 continuation line over-indented for visual indent
1231:66: E203 whitespace before ':'
1232:22: E203 whitespace before ':'
1233:60: E127 continuation line over-indented for visual indent
1233:66: E203 whitespace before ':'
1234:22: E203 whitespace before ':'
1235:60: E127 continuation line over-indented for visual indent
1235:66: E203 whitespace before ':'
1236:22: E203 whitespace before ':'
1237:60: E127 continuation line over-indented for visual indent
1237:66: E203 whitespace before ':'
1238:15: E124 closing bracket does not match visual indentation
1241: D401 First line should be in imperative mood ('Check', not 'Checks')
1241: D208 Docstring is over-indented
1256: D401 First line should be in imperative mood ('Return', not 'Returns')
1256: D202 No blank lines allowed after function docstring (found 1)
1256: D208 Docstring is over-indented
1278:22: E203 whitespace before ':'
1279:22: E203 whitespace before ':'
1279:66: E203 whitespace before ':'
1280:22: E203 whitespace before ':'
1280:66: E203 whitespace before ':'
1281:22: E203 whitespace before ':'
1281:66: E203 whitespace before ':'
1282:15: E124 closing bracket does not match visual indentation
1285: D401 First line should be in imperative mood ('Produce', not 'Produces')
1285: D208 Docstring is over-indented
1302:17: E126 continuation line over-indented for hanging indent
1302:23: E203 whitespace before ':'
1303:22: E203 whitespace before ':'
1304:22: E203 whitespace before ':'
1305:15: E126 continuation line over-indented for hanging indent
1314:18: E126 continuation line over-indented for hanging indent
1314:24: E203 whitespace before ':'
1315:23: E203 whitespace before ':'
1316:23: E203 whitespace before ':'
1317:16: E126 continuation line over-indented for hanging indent
1319:100: E502 the backslash is redundant between brackets
1320:93: E502 the backslash is redundant between brackets
1329:18: E126 continuation line over-indented for hanging indent
1329:24: E203 whitespace before ':'
1330:23: E203 whitespace before ':'
1331:23: E203 whitespace before ':'
1332:16: E126 continuation line over-indented for hanging indent
1339: D401 First line should be in imperative mood ('Produce', not 'Produces')
1339: D400 First line should end with a period (not 'e')
1339: D205 1 blank line required between summary line and description (found 0)
1339: D208 Docstring is over-indented
1357:22: E201 whitespace after '{'
1360:21: E124 closing bracket does not match visual indentation
1363: D401 First line should be in imperative mood ('Create', not 'Creates')
1363: D201 No blank lines allowed before function docstring (found 1)
1363: D202 No blank lines allowed after function docstring (found 1)
1363: D205 1 blank line required between summary line and description (found 0)
1409:41: E203 whitespace before ':'
1416:21: E201 whitespace after '{'
1421:100: E203 whitespace before ':'
1421:123: E202 whitespace before '}'
1423:118: E203 whitespace before ':'
1423:141: E202 whitespace before '}'
1429:23: E203 whitespace before ':'
1441:29: E201 whitespace after '{'
1441:39: E203 whitespace before ':'
1441:62: E203 whitespace before ':'
1444:76: E201 whitespace after '{'
1444:82: E203 whitespace before ':'
1444:100: E202 whitespace before '}'
1453:32: E203 whitespace before ':'
1460:37: E126 continuation line over-indented for hanging indent
1460:38: E201 whitespace after '{'
1460:48: E203 whitespace before ':'
1460:71: E203 whitespace before ':'
1469: D102 Missing docstring in public method
1493:34: E127 continuation line over-indented for visual indent
1493:35: E201 whitespace after '{'
1503: D202 No blank lines allowed after function docstring (found 1)
1527: D401 First line should be in imperative mood ('Display', not 'Displays')
1527: D202 No blank lines allowed after function docstring (found 1)
1527: D400 First line should end with a period (not 'e')
1542: D401 First line should be in imperative mood ('Display', not 'Displays')
1542: D202 No blank lines allowed after function docstring (found 1)
1542: D400 First line should end with a period (not 'e')
1557: D401 First line should be in imperative mood ('Display', not 'Displays')
1557: D202 No blank lines allowed after function docstring (found 1)
1557: D400 First line should end with a period (not 'e')
1573:5: E303 too many blank lines (2)
1573: D401 First line should be in imperative mood ('Format', not 'Formats')
1573: D202 No blank lines allowed after function docstring (found 1)
1602:17: E122 continuation line missing indentation or outdented
1603:17: E122 continuation line missing indentation or outdented
1616:23: E126 continuation line over-indented for hanging indent
1638:32: E203 whitespace before ':'
1638:73: E203 whitespace before ','
1639:30: E203 whitespace before ':'
1643:5: E303 too many blank lines (2)
1643: D401 First line should be in imperative mood ('Produce', not 'Produces')
1643: D202 No blank lines allowed after function docstring (found 1)
1663:26: E126 continuation line over-indented for hanging indent
1663:36: E203 whitespace before ':'
1664:36: E203 whitespace before ':'
1665:36: E203 whitespace before ':'
1666:24: E126 continuation line over-indented for hanging indent
1670: D401 First line should be in imperative mood ('Produce', not 'Produces')
1670: D400 First line should end with a period (not 'x')
1689:24: E203 whitespace before ':'
1690:20: E203 whitespace before ':'
1700:22: E126 continuation line over-indented for hanging indent
1700:32: E203 whitespace before ':'
1701:32: E203 whitespace before ':'
1702:32: E203 whitespace before ':'
1703:20: E126 continuation line over-indented for hanging indent
1708: D401 First line should be in imperative mood ('Display', not 'Displays')
1708: D202 No blank lines allowed after function docstring (found 1)
1708: D400 First line should end with a period (not 'd')
1733: D401 First line should be in imperative mood ('Display', not 'Displays')
1733: D400 First line should end with a period (not 'd')
1754:22: E126 continuation line over-indented for hanging indent
1754:29: E203 whitespace before ':'
1755:20: E126 continuation line over-indented for hanging indent
1768:76: E203 whitespace before ':'
1770:75: E203 whitespace before ':'
1770:131: E202 whitespace before '}'
1773:22: E126 continuation line over-indented for hanging indent
1773:27: E203 whitespace before ':'
1774:28: E203 whitespace before ':'
1775:20: E126 continuation line over-indented for hanging indent
1778: D401 First line should be in imperative mood ('Display', not 'Displays')
1778: D202 No blank lines allowed after function docstring (found 1)
1778: D400 First line should end with a period (not 'h')
1802: D401 First line should be in imperative mood ('Display', not 'Displays')
1802: D202 No blank lines allowed after function docstring (found 1)
1802: D400 First line should end with a period (not 'x')
1840:26: E261 at least two spaces before inline comment
1863: D401 First line should be in imperative mood ('Display', not 'Displays')
1863: D202 No blank lines allowed after function docstring (found 1)
1863: D400 First line should end with a period (not 'x')
1900:17: E126 continuation line over-indented for hanging indent
1900:23: E203 whitespace before ':'
1901:21: E203 whitespace before ':'
1902:15: E126 continuation line over-indented for hanging indent
1912:26: E203 whitespace before ':'
1935:30: E203 whitespace before ':'
1947:47: E203 whitespace before ':'
1955:22: E128 continuation line under-indented for visual indent
1956:22: E128 continuation line under-indented for visual indent
1957:22: E128 continuation line under-indented for visual indent
1958:22: E128 continuation line under-indented for visual indent
1958:26: E203 whitespace before ':'
1963:22: E128 continuation line under-indented for visual indent
1964:22: E128 continuation line under-indented for visual indent
1965:22: E128 continuation line under-indented for visual indent
1966:22: E128 continuation line under-indented for visual indent
1966:26: E203 whitespace before ':'
1978:23: E128 continuation line under-indented for visual indent
1979:60: E127 continuation line over-indented for visual indent
1980:44: E203 whitespace before ':'
1985: D401 First line should be in imperative mood ('Display', not 'Displays')
1985: D201 No blank lines allowed before function docstring (found 1)
1985: D202 No blank lines allowed after function docstring (found 1)
1985: D400 First line should end with a period (not 'x')
2048:9: E303 too many blank lines (2)
2065:64: E203 whitespace before ':'
2069:25: E203 whitespace before ':'
2083:35: E126 continuation line over-indented for hanging indent
2083:37: E251 unexpected spaces around keyword / parameter equals
2083:39: E251 unexpected spaces around keyword / parameter equals
2084:44: E251 unexpected spaces around keyword / parameter equals
2084:46: E251 unexpected spaces around keyword / parameter equals
2085:43: E251 unexpected spaces around keyword / parameter equals
2085:45: E251 unexpected spaces around keyword / parameter equals
2086:41: E251 unexpected spaces around keyword / parameter equals
2086:43: E251 unexpected spaces around keyword / parameter equals
2087:33: E126 continuation line over-indented for hanging indent
2145:26: E203 whitespace before ':'
2146:30: E203 whitespace before ':'
2147:28: E203 whitespace before ':'
2148:21: E203 whitespace before ':'
2149:32: E203 whitespace before ':'
2150:35: E126 continuation line over-indented for hanging indent
2154:33: E126 continuation line over-indented for hanging indent
2155:15: E131 continuation line unaligned for hanging indent
2155:26: E203 whitespace before ':'
2156:35: E126 continuation line over-indented for hanging indent
2159:33: E126 continuation line over-indented for hanging indent
2160:26: E203 whitespace before ':'
2161:19: E203 whitespace before ':'
2162:30: E203 whitespace before ':'
2163:35: E126 continuation line over-indented for hanging indent
2167:33: E126 continuation line over-indented for hanging indent
2168:26: E203 whitespace before ':'
2169:35: E126 continuation line over-indented for hanging indent
2172:33: E126 continuation line over-indented for hanging indent
2173:26: E203 whitespace before ':'
2174:19: E203 whitespace before ':'
2175:30: E203 whitespace before ':'
2176:35: E126 continuation line over-indented for hanging indent
2180:33: E126 continuation line over-indented for hanging indent
2181:23: E203 whitespace before ':'
2182:23: E203 whitespace before ':'
2183:24: E203 whitespace before ':'
2184:19: E203 whitespace before ':'
2219:15: E121 continuation line under-indented for hanging indent
2229:24: E203 whitespace before ':'
2230:28: E203 whitespace before ':'
2231:18: E203 whitespace before ':'
2232:29: E203 whitespace before ':'
2233:35: E126 continuation line over-indented for hanging indent
2237:33: E126 continuation line over-indented for hanging indent
2238:23: E203 whitespace before ':'
2239:23: E203 whitespace before ':'
2240:24: E203 whitespace before ':'
2241:19: E203 whitespace before ':'
2255:88: E502 the backslash is redundant between brackets
2256:19: E128 continuation line under-indented for visual indent
2257:19: E128 continuation line under-indented for visual indent
2258:19: E128 continuation line under-indented for visual indent
2259:19: E128 continuation line under-indented for visual indent
2276:15: E121 continuation line under-indented for hanging indent
2276:28: E203 whitespace before ':'
2287:24: E203 whitespace before ':'
2288:18: E203 whitespace before ':'
2289:29: E203 whitespace before ':'
2290:35: E126 continuation line over-indented for hanging indent
2294:33: E126 continuation line over-indented for hanging indent
2295:23: E203 whitespace before ':'
2296:23: E203 whitespace before ':'
2297:24: E203 whitespace before ':'
2298:19: E203 whitespace before ':'
2303:9: E266 too many leading '#' for block comment
2329:29: E203 whitespace before ':'
2330:30: E203 whitespace before ':'
2331:27: E203 whitespace before ':'
2332:18: E126 continuation line over-indented for hanging indent
2334:9: E266 too many leading '#' for block comment
2352:25: E126 continuation line over-indented for hanging indent
2352:34: E203 whitespace before ':'
2353:38: E203 whitespace before ':'
2354:29: E203 whitespace before ':'
2355:23: E126 continuation line over-indented for hanging indent
2357:9: E266 too many leading '#' for block comment
2359:17: E261 at least two spaces before inline comment
2361:13: F841 local variable 'cell_6_a' is assigned to but never used
2362:13: F841 local variable 'cell_6_b' is assigned to but never used
2381:25: E126 continuation line over-indented for hanging indent
2381:32: E203 whitespace before ':'
2382:32: E203 whitespace before ':'
2384:32: E203 whitespace before ':'
2385:32: E203 whitespace before ':'
2386:23: E126 continuation line over-indented for hanging indent
2388:9: E266 too many leading '#' for block comment
2394:33: E201 whitespace after '{'
2394:41: E203 whitespace before ':'
2394:53: E203 whitespace before ':'
2424:19: E126 continuation line over-indented for hanging indent
2424:28: E203 whitespace before ':'
2425:32: E203 whitespace before ':'
2426:31: E203 whitespace before ':'
2427:30: E203 whitespace before ':'
2428:30: E203 whitespace before ':'
2429:37: E126 continuation line over-indented for hanging indent
2429:44: E203 whitespace before ':'
2430:43: E203 whitespace before ':'
2431:35: E126 continuation line over-indented for hanging indent
2432:37: E126 continuation line over-indented for hanging indent
2432:44: E203 whitespace before ':'
2433:43: E203 whitespace before ':'
2434:35: E126 continuation line over-indented for hanging indent
2435:30: E203 whitespace before ':'
2436:30: E203 whitespace before ':'
2437:30: E203 whitespace before ':'
2438:37: E126 continuation line over-indented for hanging indent
2438:44: E203 whitespace before ':'
2439:43: E203 whitespace before ':'
2440:35: E126 continuation line over-indented for hanging indent
2441:37: E126 continuation line over-indented for hanging indent
2441:44: E203 whitespace before ':'
2442:43: E203 whitespace before ':'
2443:35: E126 continuation line over-indented for hanging indent
2444:30: E203 whitespace before ':'
2445:35: E126 continuation line over-indented for hanging indent
2449:17: E121 continuation line under-indented for hanging indent
2451:9: E266 too many leading '#' for block comment
2455: D210 No whitespaces allowed surrounding docstring text
2455: D401 First line should be in imperative mood ('Produce', not 'Produces')
2455: D400 First line should end with a period (not 'd')
2455: D300 Use """triple double quotes""" (found '-quotes)
2466:18: E126 continuation line over-indented for hanging indent
2466:24: E203 whitespace before ':'
2467:25: E203 whitespace before ':'
2468:16: E126 continuation line over-indented for hanging indent
2470: D401 First line should be in imperative mood ('Add', not 'Adds')
2470: D209 Multi-line docstring closing quotes should be on a separate line
2470: D202 No blank lines allowed after function docstring (found 1)
2470: D400 First line should end with a period (not 'y')
2470: D205 1 blank line required between summary line and description (found 0)
2479:32: E203 whitespace before ':'
2480:31: E203 whitespace before ':'
2484:40: E203 whitespace before ':'
2484: D400 First line should end with a period (not 'r')
2484: D300 Use """triple double quotes""" (found '-quotes)
2488:38: E203 whitespace before ':'
2488: D400 First line should end with a period (not 'r')
2488: D300 Use """triple double quotes""" (found '-quotes)
2492: D401 First line should be in imperative mood ('Print', not 'Prints')
2492: D201 No blank lines allowed before function docstring (found 1)
2492: D202 No blank lines allowed after function docstring (found 1)
2492: D205 1 blank line required between summary line and description (found 0)
2561:21: E126 continuation line over-indented for hanging indent
2562:30: E203 whitespace before ':'
2565:19: E126 continuation line over-indented for hanging indent
2570:26: E201 whitespace after '{'
2570:36: E203 whitespace before ':'
2570:51: E202 whitespace before '}'
2576:22: E126 continuation line over-indented for hanging indent
2576:34: E203 whitespace before ':'
2577:20: E126 continuation line over-indented for hanging indent
2583:26: E261 at least two spaces before inline comment
2599:17: E124 closing bracket does not match visual indentation
2626:49: E231 missing whitespace after ':'
2630:61: E128 continuation line under-indented for visual indent
2631:61: E128 continuation line under-indented for visual indent
2636:13: E303 too many blank lines (2)
2637:13: F841 local variable 'cc' is assigned to but never used
2638:13: F841 local variable 'sc' is assigned to but never used
2652:22: E126 continuation line over-indented for hanging indent
2652:28: E203 whitespace before ':'
2653:28: E203 whitespace before ':'
2654:20: E126 continuation line over-indented for hanging indent
2665:26: E126 continuation line over-indented for hanging indent
2665:32: E203 whitespace before ':'
2666:24: E126 continuation line over-indented for hanging indent
2673: D401 First line should be in imperative mood ('Print', not 'Prints')
2673: D201 No blank lines allowed before function docstring (found 1)
2673: D202 No blank lines allowed after function docstring (found 1)
2673: D205 1 blank line required between summary line and description (found 0)
2674:32: E128 continuation line under-indented for visual indent
2675:32: E128 continuation line under-indented for visual indent
2676:32: E128 continuation line under-indented for visual indent
2677:32: E128 continuation line under-indented for visual indent
2678:32: E128 continuation line under-indented for visual indent
2679:32: E128 continuation line under-indented for visual indent
2742:21: E126 continuation line over-indented for hanging indent
2743:30: E203 whitespace before ':'
2746:19: E126 continuation line over-indented for hanging indent
2751:26: E201 whitespace after '{'
2751:36: E203 whitespace before ':'
2751:51: E202 whitespace before '}'
2759:26: E126 continuation line over-indented for hanging indent
2759:38: E203 whitespace before ':'
2760:24: E126 continuation line over-indented for hanging indent
2773:26: E261 at least two spaces before inline comment
2789:17: E124 closing bracket does not match visual indentation
2816:49: E231 missing whitespace after ':'
2820:61: E128 continuation line under-indented for visual indent
2821:61: E128 continuation line under-indented for visual indent
2826:13: E303 too many blank lines (2)
2827:13: F841 local variable 'cc' is assigned to but never used
2828:13: F841 local variable 'sc' is assigned to but never used
2842:22: E126 continuation line over-indented for hanging indent
2842:28: E203 whitespace before ':'
2843:28: E203 whitespace before ':'
2844:20: E126 continuation line over-indented for hanging indent
2855:26: E126 continuation line over-indented for hanging indent
2855:32: E203 whitespace before ':'
2856:24: E126 continuation line over-indented for hanging indent
2863: D400 First line should end with a period (not 'g')
2863: D205 1 blank line required between summary line and description (found 0)
2890: D205 1 blank line required between summary line and description (found 0)
2911: D401 First line should be in imperative mood ('Return', not 'Returns')
2911: D400 First line should end with a period (not 't')
2911: D205 1 blank line required between summary line and description (found 0)
2926: D401 First line should be in imperative mood ('Return', not 'Returns')
2926: D400 First line should end with a period (not 't')
2926: D205 1 blank line required between summary line and description (found 0)
2939:15: E271 multiple spaces after keyword
2942:5: E303 too many blank lines (2)
2942: D401 First line should be in imperative mood ('Return', not 'Returns')
2942: D202 No blank lines allowed after function docstring (found 1)
2942: D400 First line should end with a period (not 'e')
2942: D205 1 blank line required between summary line and description (found 0)
2972:9: F841 local variable '_' is assigned to but never used
2975:13: F821 undefined name 'out'
2976:27: E203 whitespace before ':'
2977:27: E203 whitespace before ':'
2978:28: E203 whitespace before ':'
2984: D401 First line should be in imperative mood ('Print', not 'Prints')
2984: D202 No blank lines allowed after function docstring (found 1)
3024:21: E126 continuation line over-indented for hanging indent
3024:146: E502 the backslash is redundant between brackets
3024:29: E203 whitespace before ':'
3029:19: E126 continuation line over-indented for hanging indent
3036:25: E126 continuation line over-indented for hanging indent
3036:89: E502 the backslash is redundant between brackets
3036:33: E203 whitespace before ':'
3039:23: E126 continuation line over-indented for hanging indent
3044:25: E126 continuation line over-indented for hanging indent
3044:159: E502 the backslash is redundant between brackets
3044:33: E203 whitespace before ':'
3049:23: E126 continuation line over-indented for hanging indent
3073:39: E127 continuation line over-indented for visual indent
3073:51: E203 whitespace before ':'
3074:46: E203 whitespace before ':'
3075:51: E203 whitespace before ':'
3076:48: E203 whitespace before ':'
3083:39: E127 continuation line over-indented for visual indent
3083:51: E203 whitespace before ':'
3084:46: E203 whitespace before ':'
3085:51: E203 whitespace before ':'
3086:48: E203 whitespace before ':'
3095:5: E303 too many blank lines (2)
3095: D401 First line should be in imperative mood ('Print', not 'Prints')
3095: D400 First line should end with a period (not 't')
3106:9: F841 local variable '_' is assigned to but never used
3109:9: E303 too many blank lines (2)
3132:32: E203 whitespace before ':'
3134:26: E203 whitespace before ':'
3135:33: E203 whitespace before ':'
3139: D210 No whitespaces allowed surrounding docstring text
3139: D400 First line should end with a period (not 's')
3148:5: E303 too many blank lines (2)
3148: D202 No blank lines allowed after function docstring (found 1)
3148: D400 First line should end with a period (not 's')
3179:31: E203 whitespace before ':'
3186: D202 No blank lines allowed after function docstring (found 1)
3186: D400 First line should end with a period (not 's')
3200:17: E126 continuation line over-indented for hanging indent
3200:26: E203 whitespace before ':'
3201:15: E126 continuation line over-indented for hanging indent
3208:37: E126 continuation line over-indented for hanging indent
3211:69: E231 missing whitespace after ':'
3212:29: E203 whitespace before ':'
3218: D401 First line should be in imperative mood ('Display', not 'Displays')
3218: D400 First line should end with a period (not 'd')
3231:18: E127 continuation line over-indented for visual indent
3240:65: E126 continuation line over-indented for hanging indent
3261:37: E126 continuation line over-indented for hanging indent
3306: D202 No blank lines allowed after function docstring (found 1)
3306: D205 1 blank line required between summary line and description (found 0)
3306: D208 Docstring is over-indented
3335:16: E201 whitespace after '{'
3335:43: E202 whitespace before '}'
3340:23: E203 whitespace before ':'
3346: D401 First line should be in imperative mood ('Display', not 'Displays')
3346: D400 First line should end with a period (not 'y')
3360:18: E127 continuation line over-indented for visual indent
3382:9: E266 too many leading '#' for block comment
3385:18: E126 continuation line over-indented for hanging indent
3396: D401 First line should be in imperative mood ('Display', not 'Displays')
3396: D400 First line should end with a period (not 'y')
3410: D401 First line should be in imperative mood ('Create', not 'Creates')
3460:49: E502 the backslash is redundant between brackets
3461:34: E127 continuation line over-indented for visual indent
3462:51: E502 the backslash is redundant between brackets
3464:43: E502 the backslash is redundant between brackets
3466:45: E502 the backslash is redundant between brackets
3467:30: E128 continuation line under-indented for visual indent
3468:43: E502 the backslash is redundant between brackets
3470:47: E502 the backslash is redundant between brackets
3471:30: E128 continuation line under-indented for visual indent
3472:41: E502 the backslash is redundant between brackets
3473:30: E128 continuation line under-indented for visual indent
3474:42: E502 the backslash is redundant between brackets
3475:30: E128 continuation line under-indented for visual indent
3479:9: E124 closing bracket does not match visual indentation
3482: D401 First line should be in imperative mood ('Create', not 'Creates')
3489: D401 First line should be in imperative mood ('Create', not 'Creates')
3506:5: W191 indentation contains tabs
3506:5: E101 indentation contains mixed spaces and tabs
3511:1: W191 indentation contains tabs
3511:1: E101 indentation contains mixed spaces and tabs
3512:1: E101 indentation contains mixed spaces and tabs
3530:49: E502 the backslash is redundant between brackets
3531:34: E127 continuation line over-indented for visual indent
3532:51: E502 the backslash is redundant between brackets
3534:43: E502 the backslash is redundant between brackets
3536:45: E502 the backslash is redundant between brackets
3537:30: E128 continuation line under-indented for visual indent
3538:43: E502 the backslash is redundant between brackets
3540:17: E127 continuation line over-indented for visual indent
3545: D401 First line should be in imperative mood ('Create', not 'Creates')
3551: D401 First line should be in imperative mood ('Create', not 'Creates')
3556: D401 First line should be in imperative mood ('Create', not 'Creates')
3561: D401 First line should be in imperative mood ('Create', not 'Creates')
3566: D401 First line should be in imperative mood ('Create', not 'Creates')
3571: D401 First line should be in imperative mood ('Create', not 'Creates')
3576: D401 First line should be in imperative mood ('Create', not 'Creates')
3581: D401 First line should be in imperative mood ('Create', not 'Creates')
3586: D401 First line should be in imperative mood ('Create', not 'Creates')
3591: D401 First line should be in imperative mood ('Create', not 'Creates')
3596: D401 First line should be in imperative mood ('Create', not 'Creates')
3601: D401 First line should be in imperative mood ('Create', not 'Creates')
3608: D401 First line should be in imperative mood ('Create', not 'Creates')
3613: D401 First line should be in imperative mood ('Create', not 'Creates')
3613: D400 First line should end with a period (not ')')
3618: D401 First line should be in imperative mood ('Create', not 'Creates')
3618: D400 First line should end with a period (not ')')
3623: D200 One-line docstring should fit on one line with quotes (found 3)
3631: D200 One-line docstring should fit on one line with quotes (found 3)
3639:22: E201 whitespace after '{'
3646: D202 No blank lines allowed after function docstring (found 1)
3670:25: E126 continuation line over-indented for hanging indent
3676:25: E126 continuation line over-indented for hanging indent
3684:17: E126 continuation line over-indented for hanging indent
3684:26: E203 whitespace before ':'
3688: D401 First line should be in imperative mood ('Return', not 'Returns')
3688: D400 First line should end with a period (not 'd')
3708:9: F841 local variable '_' is assigned to but never used
3710:9: E266 too many leading '#' for block comment
3715: D401 First line should be in imperative mood ('Display', not 'Displays')
3715: D202 No blank lines allowed after function docstring (found 1)
3715: D400 First line should end with a period (not 's')
3715: D205 1 blank line required between summary line and description (found 0)
3750:25: E126 continuation line over-indented for hanging indent
3775:25: E126 continuation line over-indented for hanging indent
3785:33: E126 continuation line over-indented for hanging indent
3788:41: E128 continuation line under-indented for visual indent
3790:41: E128 continuation line under-indented for visual indent
3797:33: E126 continuation line over-indented for hanging indent
3798:45: E128 continuation line under-indented for visual indent
3800:45: E128 continuation line under-indented for visual indent
3812:33: E126 continuation line over-indented for hanging indent
3813:45: E128 continuation line under-indented for visual indent
3816:45: E128 continuation line under-indented for visual indent
3820:45: E128 continuation line under-indented for visual indent
3822:45: E128 continuation line under-indented for visual indent
3825:21: E126 continuation line over-indented for hanging indent
3828: D401 First line should be in imperative mood ('Display', not 'Displays')
3841:9: F841 local variable '_' is assigned to but never used
3891:18: E127 continuation line over-indented for visual indent
3894:48: E222 multiple spaces after operator
3902:5: E303 too many blank lines (2)
3902: D401 First line should be in imperative mood ('Return', not 'Returns')
3902: D400 First line should end with a period (not 'd')
3926:71: E211 whitespace before '('
3933:28: E201 whitespace after '{'
3934:30: E127 continuation line over-indented for visual indent
3936:30: E124 closing bracket does not match visual indentation
3942:68: E211 whitespace before '('
3950: D401 First line should be in imperative mood ('Return', not 'Returns')
3950: D202 No blank lines allowed after function docstring (found 1)
3950: D400 First line should end with a period (not 'd')
3963: D401 First line should be in imperative mood ('Return', not 'Returns')
3963: D202 No blank lines allowed after function docstring (found 1)
3963: D400 First line should end with a period (not 'd')
3976: D401 First line should be in imperative mood ('Return', not 'Returns')
3976: D400 First line should end with a period (not 'e')
4005:17: E122 continuation line missing indentation or outdented
4005:69: E261 at least two spaces before inline comment
4005:70: E262 inline comment should start with '# '
4011:39: E126 continuation line over-indented for hanging indent
4015: D401 First line should be in imperative mood ('Return', not 'Returns')
4015: D400 First line should end with a period (not 'd')
4016:63: E127 continuation line over-indented for visual indent
4029:9: F841 local variable '_' is assigned to but never used
4044: D401 First line should be in imperative mood ('Return', not 'Returns')
4044: D400 First line should end with a period (not 'd')
4058:9: F841 local variable '_' is assigned to but never used
4079: D401 First line should be in imperative mood ('Return', not 'Returns')
4079: D400 First line should end with a period (not 's')
4098:71: E211 whitespace before '('
4099:64: E211 whitespace before '('
4105:38: E201 whitespace after '{'
4106:65: E127 continuation line over-indented for visual indent
4107:57: E202 whitespace before '}'
4111:5: E303 too many blank lines (2)
4111: D401 First line should be in imperative mood ('Return', not 'Returns')
4111: D400 First line should end with a period (not 'd')
4130:30: E261 at least two spaces before inline comment
4130:31: E262 inline comment should start with '# '
4140:69: E211 whitespace before '('
4141:77: E211 whitespace before '('
4146:5: E303 too many blank lines (2)
4146: D401 First line should be in imperative mood ('Return', not 'Returns')
4146: D400 First line should end with a period (not 'd')
4164: D209 Multi-line docstring closing quotes should be on a separate line
4164: D400 First line should end with a period (not 's')
4170: D209 Multi-line docstring closing quotes should be on a separate line
4170: D400 First line should end with a period (not 's')
4176: D209 Multi-line docstring closing quotes should be on a separate line
4176: D400 First line should end with a period (not 'k')
4188:27: E127 continuation line over-indented for visual indent
4193: D102 Missing docstring in public method
4201:24: E127 continuation line over-indented for visual indent
4217:16: E127 continuation line over-indented for visual indent
4250:41: E127 continuation line over-indented for visual indent
4266:60: E127 continuation line over-indented for visual indent
4275:41: E126 continuation line over-indented for hanging indent
4279:57: E127 continuation line over-indented for visual indent
4290: D102 Missing docstring in public method
4293: D102 Missing docstring in public method
4298: D209 Multi-line docstring closing quotes should be on a separate line
4334:49: E127 continuation line over-indented for visual indent
4348:43: E127 continuation line over-indented for visual indent
4357: D400 First line should end with a period (not 'e')
4357: D205 1 blank line required between summary line and description (found 0)
4405: D400 First line should end with a period (not 's')
4418:109: E502 the backslash is redundant between brackets
4419:115: E502 the backslash is redundant between brackets
4420:109: E502 the backslash is redundant between brackets
4421:38: E128 continuation line under-indented for visual indent
4421:46: E502 the backslash is redundant between brackets
4422:38: E128 continuation line under-indented for visual indent
4423:22: E127 continuation line over-indented for visual indent
4426: D401 First line should be in imperative mood ('Return', not 'Returns')
4426: D400 First line should end with a period (not 's')


1: D400 First line should end with a period (not 's')
1: D205 1 blank line required between summary line and description (found 0)
1: D208 Docstring is over-indented
34:1: I100 Imports statements are in the wrong order. from flask_login should be before import six
37:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_is_user_in_role
37:1: I100 Imports statements are in the wrong order. from .control should be before from .engine
38:1: I101 Imported names are in the wrong order. Should be acc_firerole_check_user, compile_role_definition
39:1: I101 Imported names are in the wrong order. Should be CFG_WEBACCESS_WARNING_MSGS, SUPERADMINROLE
42: D401 First line should be in imperative mood ('Create', not 'Creates')
42: D202 No blank lines allowed after function docstring (found 1)
51: D203 1 blank line required before class docstring (found 0)
51: D200 One-line docstring should fit on one line with quotes (found 3)
56: D400 First line should end with a period (not 'e')
56: D205 1 blank line required between summary line and description (found 0)
56: D207 Docstring is under-indented


1: D100 Missing docstring in public module
4: L102 copyright year is outdated, expected 2015 but got 2014
20:1: I101 Imported names are in the wrong order. Should be Keyword, OneOrMore, quotedString, removeQuotes, restOfLine
21:1: I201 Missing newline before sections or imports.
23:1: I100 Imports statements are in the wrong order. from invenio.base.utils should be before from werkzeug.utils
29: D203 1 blank line required before class docstring (found 0)
29: D400 First line should end with a period (not ':')
44: D401 First line should be in imperative mood ('Set', not 'Sets')
44: D400 First line should end with a period (not 'n')
52: D400 First line should end with a period (not 's')
57: D401 First line should be in imperative mood ('Extend', not 'Extends')
57: D400 First line should end with a period (not 'g')
66: D400 First line should end with a period (not 't')
71: D401 First line should be in imperative mood ('Add', not 'Adds')
71: D400 First line should end with a period (not 'n')
76: D400 First line should end with a period (not 's')


boolean змінні краще називати is_registered
не перестворюй новий репозиторій а створи мігрейшн щоб виправити


Хм, а каким образом это можно сделать? Не до конца понял задачу.


що таке status2 status3?


Що це за атрибут?


I think we should first explain what we want to do.. and then explain why we use this neighborhood method.. What do we want to compute in the first step?


@jpodwys That's great! Thank you for the heads up! Will definitely keep you in the loop when I pick this up again (hopefully soon).


Это не нужно исправлять — это хинты для переносов


The second one could be === as well but it probably doesn't matter tbh


最简单的方格子动态规划,每次只能走两个方向,而且起点定,终点定.


I propose this link title changes to `Livestax API`, a we're gonna place the User API in the docs, also the link is defined at the bottom of the file so no need to place it in brackets, just override it there.


Я вот еще не пойму. У нас есть `init` доменов ibDomains, и есть `ibEngines`, который ты в этом коммите использовал впервые.
Так вот вопрос - не происходит переопределение разве?


Делай точечные исправления по одной запятой на коммит.
Иначе видишь вот это все в мерж не войдет.


Что у нас главнее, получается домены? Они удивают инит движков?


Do these bounds work if you do the following? It could make reading the bounds a *lot* more understandable.
```rust
where for<'a, 'k> Response<'a, 'k, D> : Cookies + Session<T>,
           T: AuthorizeSession
```


1. Make it a bit more object oriented - use class you created earlier.
1.1. Object which will take rest & convert it to names (a converter)


Rename the `arr` to a bit more meaning full name.


@henkieee You renamed the function from confirmOrder to saveOrder here. But you forgot to update the upper button. You only updated the lower button.


sorry for criticizing, but this is just `imgDockerBase =<< (imgDocker (configImage config))`.


это как по одной запятой на коммит, поясни, не совсем понимаю
14 лип. 2015 15:15, користувач "Namdak Tonpa" <notifications@github.com>
написав:

> Делай точечные исправления по одной запятой на коммит.
> Иначе видишь вот это все в мерж не войдет.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/IndiraMoiseevna/rnying.ma/commit/d2b82352485dce0241d104fb8acb8e891e785003#commitcomment-12154398>
> .
>


```ruby
cost, paid = line.strip.split(';').map(&:to_f)
```


should use say instead of puts in migration


У нас идёт наследование `домен -> движок -> база -> стандартный прототип объекта JS`. При вызове `aib.X` js-движок будет искать `X` сверху вниз и возвратить первое совпадение.


И поэтому ты использовал init: { value: null }, чтобы не допустить init: { value() {Cfg.fileThumb = 0;	return false;	} },

Ох, что-то до меня все туго доходит.


Move this responsibility to the converter class.


@henkieee You should have also renamed this function call. You renamed the function from confirmOrder to saveOrder, but didn't update this occurrence.


Add tests for the converter class.


Right, it seems that it is Ruby semantics that `Thread#run` does nothing unless the thread is in `#sleep`. So indeed we need to care about that case.


Move the const to the converter class.


Please don't consider this commit, but I suggest to consider this: https://github.com/gildniy/confide/commit/37314df21ef999c7bc28aed78e1a42f63afe0ec2

Regards


Hello Juan, the fact that boath `readium_plugins` and `readium_shared_js` packages have the same location seems to have broken the build, so I renamed those:
https://github.com/readium/readium-shared-js/commit/22b1aa19f0b987486b39d55230175fcaa5d7f069#diff-3917ab964dfc14d6f9668865a46a843c

However, I think we need to verify this: do we actually need a `readium_plugins` package? (why not just `readium_shared_js/plugins_controller`) A package is meant to scope the source tree from the root `location`, not to act as a shortcut to (in this case) `plugins_controller`


Еще раз спасибо за пояснение. Щито-то сегодня туго соображаю. Впрочем, как и всегда :D


Почему с места в карьер?
в перечислении к "как использвать" есть три пункта:
* в Node.js
* в браузере
* для сборки финального HTML


Making snf-image work correct for images that do not provide their own sysprep file is a feature. Someone who creates an image can provide his own sysprep file if he wants. I agree that we need to clean up the default sysprep.xml file we provide to make it contain only the very basic fields it needs, just to do an unattended setup, but I don't see why we need to cripple this feature.

I also agree that we should make snf-image inject all it needs into the sysprep.xml file without forcing it to have a specific structure but this is another thing.

An Administrator could for example change a policy in all the official Windows images the deployment host by configuring snf-image to use a different sysprep file and without having to alter every single image.


Thanks for spotting that and reporting it.  I had spotted it when adding the latest version string to the same source file (that was the last post to the PR package).  The fix is posted along with the "Update Snort package version" commit.


Helal


Fixed here:
https://github.com/readium/readium-shared-js/commit/b0baba58ee1b45b9ebe5a8496aeeff1573513ae6

Let me know what you think. Thanks! Dan


- changed the palindrome function from assignment 1.3 into a more "elegant"  method (I hope) and tried the Prime Spiral ex; I'm not sure it outputs what it should (~ if the solution is correct)


Well, putting the date format in locales is obvious and easy move. However using decorator is not. Decorators seems to behave like models they decorate. And method 'date_to_url' is not used on data that is fetched form DB. Examples of use below:
today = date_to_url(DateTime.now)
redirect_to dashboard_path(today)

redirect_to dashboard_path(date_to_url(params[:date]))

Where to put this method in this case?


isn't it some kind of ```SharedPreferences``` too?


I differentiated in the message but could have unified, agreed.
The warn level for an ignored exception seemed reasonable. I am not against
making it an error but is it really an error or merely a failure?

On Tue, Jul 14, 2015 at 2:10 PM, John Burwell <notifications@github.com>
wrote:

> Why not use multi-catch here? These catch blocks could be reduced to the
> following:
>
> } catch (BadServerResponse | XenAPIException | XMLRpcException e) {
> logger.warn("Failed to attach config drive ISO to VM " + vmName + " in
> host " + ipAddr + " due to the following error: " + e);
> return false;
> }`
>
> Also, why is that logger level WARN and not ERROR?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/shapeblue/cloudstack/commit/e62d95237534e856ed7e93615fde47ae3b20aef4#commitcomment-12154296>
> .
>

--
Daan


@jonathandavis It is a little lengthy. I was erring on the side of being explicit.  Since it will be minified, does it matter? Or does it aesthetically offend you :)


well they're both strings anyway so not like it makes a difference :P


You also need to remove `node_modules` folder from the repository


точно нужно? ниже есть пример с подключением конкретной библиотеки.
Этот документ будет читать тот, кто явно должен понимать, зачем подключать библиотеки. Кажется, здесь информация будет лишней.


@sitaramc I think the best solution would be for vim-gitgutter to avoid running on help files.


@jonathandavis This is actually a copy / paste from the original name copying function.  I wasn't sure exactly why it was written this way, so I decided to leave it alone in case there was an advantage. I can definitely see why it would be better to trim the individual fields.


ATM, the ResearchManager is used to link researches with everything else (rooms/traps/spells). So, there might be stuff that are not directly related to researches like the spell buttons cegui path. That's why I proposed to use the ResearchManager. However, if you want to go for the SpellManager (which I agree is more logical in this case), please try to call the ResearchManager to retrieve the button so that we don't spread this kind of data everywhere making harder to add new spells/rooms/traps.


it is my first time to use GitHub, I am studing how to use it,


The `apiKey` should be passed along in the constructor and these should be _instance_ methods (i.e. non-static).


This could probably be replaced with [a null `PrintWriter`](http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/io/CharStreams.html#nullWriter%28%29).


@signe What work arounds do you have in place? Are the changes in 1.6.0 enought? I am planning a 1.7.0 release that will try to tackle ubuntu's mutiple configuration file issue (different configs for cli, fpm, cgi, and apache)


it is my first time to use GitHub ,I an studing to use it


LOL, never mind. I read the next commit.


done


:+1:

People always forget to test the positive in cases like this.


Any chance of upgrading your terminal? ;)


我已经添加了一张小美女的图片


The error message from the exception should provide the details about the source/cause of the error.  Therefore, I think the code tidiness is consolidating the message.

I see you point on the ``WARN`` level and that makes sense now that I think about it a little more.

> On Jul 14, 2015, at 8:31 AM, Daan Hoogland <notifications@github.com> wrote:
>
> I differentiated in the message but could have unified, agreed.
> The warn level for an ignored exception seemed reasonable. I am not against
> making it an error but is it really an error or merely a failure?
>
> On Tue, Jul 14, 2015 at 2:10 PM, John Burwell <notifications@github.com>
> wrote:
>
> > Why not use multi-catch here? These catch blocks could be reduced to the
> > following:
> >
> > } catch (BadServerResponse | XenAPIException | XMLRpcException e) {
> > logger.warn("Failed to attach config drive ISO to VM " + vmName + " in
> > host " + ipAddr + " due to the following error: " + e);
> > return false;
> > }`
> >
> > Also, why is that logger level WARN and not ERROR?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/shapeblue/cloudstack/commit/e62d95237534e856ed7e93615fde47ae3b20aef4#commitcomment-12154296>
> > .
> >
>
>
>
> --
> Daan
> —
> Reply to this email directly or view it on GitHub <https://github.com/shapeblue/cloudstack/commit/e62d95237534e856ed7e93615fde47ae3b20aef4#commitcomment-12154605>.
>


ok I get it. CEGUI has interesting properties. The most difficult is to discover them ^^


Typically the left side is typed as the interface (`List<Event>`), not the specific implementation.  Not a big deal in this case, but I'd change it anyway.


I feel like this probably goes into too much detail. It would be great if we could test the help command just knows about all the other commands without having to list them here.

This will probably require some refactoring. *hint, hint*


Why? git blame shows you wrote replaceGenomes in the first place?
Are you talking about taking it out of the module?


Here we are, this can be used with Pathogen now or anything you like better ;)
I am okay to write the doc if you want.


Thanks Achin. Will push new patches shortly and profile the CPU boot times.

FWIW, we are more concerned about size now and are OK with the new CPU boot
time unless it is within "permissible" limits.

On Thu, Jul 9, 2015, 9:58 PM Achin Gupta <notifications@github.com> wrote:

> Please be aware that while disabling USE_COHERENT_MEM will save you
> around 4K worth of memory, the bakery lock implementation will use software
> based cache maintenance to make the locks work. On Juno we have seen that
> this adds to the latencies in the power up/down code paths. Have you had a
> chance to do some measurements at your end as well?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vwadekar/arm-trusted-firmware/commit/6241e78ea18d0a77c60019e615f5b1f91517015d#commitcomment-12088683>
> .
>


lighten background for selected text for better contrast


O `before_action` aceita alguns opções como por exemplo `only: [:show]` para especificar o action.


Just be sure to build an awesome all :)

On Tue, 14 Jul 2015 7:20 pm Alec Sloman <notifications@github.com> wrote:

> Thanks @lukesleeman <https://github.com/lukesleeman> for all this work, I
> really appreciate it! I'll get hacking.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rexmortus/GMScreen-Android/commit/c9e297bfcc4150114a37c476370c55aaa99cc767#commitcomment-12151366>
> .
>


I copied whatever the original repo had. I never considered removing the type check altogether as I haven't used Flask before.

The default value is from the code before, I just copied it.

I'll probably end up removing the type check and merging that instead.


@mstembera Thanks, you're right.
@jcalovski Well, I think with 16 or 32 cores it might happen we have split points with the same number of parent splits and the same depth, then joining the one with the lower moveCount may be slightly favourable.


`ira_id` is already a list (coming from search). Using `[ira_id]` causes an error later.


What about moving these commits not exactly related to the fix to a separated PR?


@sitaramc Please try 2e98692.


bullshitt


did we just lose all Lanyrd links from archive?


No feedback for user


есть удобная возможность внутри файла `vars/main.yml`  использовать [lookups](https://docs.ansible.com/playbooks_lookups.html) для того что бы исплользовать переменные окружения


No feedback for user (flash msgs).


No error fields


This is OK, however we could move it into partial - please check how use collections and partials


This commit shows how far I got with cleaning up the GPlates Plugin in the style of the Ascii Data Plugin and the transformation from spherical shell to box geometries (the actual mapping procedures still need to be implemented, but right now, I do not need them immediately).


We usually use just 'form'


@wedaly  `%s` is linked to `provider_url` attribute of the credit provider. Is it correct or we need to add some other url like ASU home page etc?


No. I am on a VAX teletype. Physically no space for the thousands of keys necessary to support unicode.


Отладка, там ошибка сидит и я ее ищу


ладно, всё равно эти велосипеды выкинутся потом)


Hey Sebastian, what was the importance of equating the "self" variable with the "this" variable? Just curious, as I am looking to merge parts of your caption code with my backstretch fork that has other features.


This is being discussed here: https://github.com/paragonie/random_compat/pull/14/files#r34523166


运行提示如下错误，我在的linux的nas上和在vps上运行，都提示如下错误，请帮忙看下，谢谢！

root@mynas:/usr/bin/dht# python collector.py result.json collector.state
Traceback (most recent call last):
  File "collector.py", line 216, in <module>
    sd.create_session(32900)
  File "collector.py", line 106, in create_session
    session.set_alert_mask(lt.alert.category_t.all_categories)
OverflowError: can't convert negative value to unsigned


What happens if you simply modify your `/etc/apt/sources.list` like I did?


I got this:
```
Testing gazebo-yarp-plugins
==> sh /private/tmp/gazebo-yarp-plugins20150714-13791-1rbiqag/test.sh
==> echo $?
```


Thanks @nijel - have patched this in staging and will push to master soon. Please let us know if you catch anything else in the translation project as well :)


Then it should be ok... I still don't know how to properly output the result, but because there is an assert in the test function, if everything exited correctly then the test should have passed.

Thanks for the test :)


Hello,
I think this commit introduce an error in Webkit based navigators (tested on Safari and Chrome).
These are the steps to reproduce the error:
- Open a record record containing a CKEditor widget
- Edit, leave the value in the CKEditor empty
- Save

It raises the following error:
TypeError: undefined is not an object (evaluating 'self.editor.name').

If we revert this commit, everything works as expected.

Thank you!


I thought the default redirect was registered with the App, or am I thinking of something else? Isn't that the one that should be used if not specified here?


should this be either `read` or `write`?


Good call, missed one.


тут лучше дать пользователю самостоятельно назначать переменные окружения, к примеру он может хранить эти комманды в `.bashrc` или определять их в каждой комманде: `AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=yyy provision.sh`


there are constants that specifies the max key and value lengths


        } catch (XenAPIException | XmlRpcException e) {
            s_logger.warn("Failed to attach config drive ISO to the VM  "+
vmName + " In host " + ipAddr + " due to " + e);
            return false;
        }

it would have to be then
.

--
Daan


There is a typo in the word Application - the O is missing :smile: Just letting you know.


"do not use exceptions for flow control" thing


@sdodson - yes, what you've written here is correct.   With restrictions on both host ports and (potentially) placement the best way to upgrade a router is an node+1 scenario where you have an additional free host that can begin the process of accepting the upgraded router along with using @ramr 's ip failover.


Тогда уж сразу можно было на GitHub.


GitHub


Thanks


这里写插件说明


Quien hizo esta Yoda-condition? Eso es muy Pro!


use-retval is meant to used for functions where there is no possibility to have reasonable code without capturing the return value (e.g. std::abs()). Here it is possible because there are out-parameters which will get filled by the API call.


It is, but you can optionally pass a different redirect URI. I guess that we should change a bit this section in the Dev Portal so people would only register their base URL (for security reasons) and not the full callback url.  WDYT?
@yardenr


Yeap, I added a comment to the bug. We need to revisit it.


@Thilas, I've already done proper modification to your PR.

The point is that also when I've no verb and just one option class, the behaviour must be consistent.


If we were added into a write-access team only for the `influxdb-r` repository then we could merge some of these repositories, keep this being the original repository, and continue its maintenance.


Also this:
+repalceGenomes [] _   = []
  replaceGenomes pop [] = pop


Resolved


venia, y si eso es muy bueno, evitas el bug del =

2015-07-14 10:01 GMT-03:00 Nicolás Wolovick <notifications@github.com>:

> Quien hizo esta Yoda-condition? Eso es muy Pro!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/WaVEV/facultad/commit/daed021f3a5421d92f44279a52e158ca3e63754d#commitcomment-12155029>
> .
>


The fact that we do not check the value in most properties is a bug, but If i register an image with OFFLINE_RESIZE=1 then a user would naturally expect that by changing this value to 0, it would disable the OFFLINE_RESIZE. I'm thinking of extending this to accept more values that just "yes" and fix the code to check for the value of the property, but I think that expecting the user to only set it with any value would be more error prone.

Right now snf-image will work as expected without even providing a single image property in the vast majority of the cases. When a novice user deploys an Windows XP image, it should work as expected. I'm not talking about enabling the NOCHECK thing, only the resize. The ntfs-3g project is a very mature project. It shouldn't have problems with so old operating systems. Windows Vista introduced new features like persistent shadow copies, but it should work as expected in Windows XP:
`The ntfsresize program safely resizes Windows XP, Windows Server 2003, Windows 2000, Windows NT4 and Longhorn NTFS filesystems without data loss. `
Are you aware of any issues of ntfsresize with windows XP?

Concerning the DO_SYNC thing, it's fine with me. We can removing it and putting it in the configuration file of snf-image-host to allow the administrator to enable it if he wants.


COLLECT


collect


@tcavaletto , not all databases would have a personaliasid=10, and even for those that do, it may not be the person you'd expect. This migration didn't work for our production db. I fixed it here: https://github.com/SparkDevNetwork/Rock/commit/dd3ef24ea5e57bc7d013811114d08f1b6f81f583 ( and then moved the SQL to a resource file here: https://github.com/SparkDevNetwork/Rock/commit/d0677e8a84f2640a96fe5495e88f3127a3351caf). Most of the time you want to avoid using hard-coded id values in a migration.


To było dobrze


Interestingly enough that mistake compiles because GHC thinks it is a new function definition. I noticed it because of the warnings of incomplete pattern matching and top level function with no signature


Yes, adding events to tickets would work. OrderResponseReceived,
OrderEventReceived or something like that. OrderResponse event would not be
entirely a duplication because it's possible to have error response without
order status change, and I would have to scan orderticket to learn that
there was an error. Callback is more timely.

On Mon, Jul 13, 2015 at 6:18 PM, Michael <notifications@github.com> wrote:

> @dpavlenkov <https://github.com/dpavlenkov> Please let me know if the
> current code will work for you,if we are missing something we're happy to
> bring it back, it was my understanding that it may be duplication. Jared
> and I have recently been discussing attaching events to the OrderTicket
> object itself, which would also provide task support and the great deal of
> flexibility that follows :).
>
> We've opened a new issue for this: #140
> <https://github.com/QuantConnect/Lean/issues/140>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/QuantConnect/Lean/commit/704bfc2298f93b3901f855d8f86f2fa2dd4aa14d#commitcomment-12144120>
> .
>


Unificar el coding-style de los `else`.


Ok, tak też działa, ale jest bardziej brzydko niż to, co usunąłeś. I przydałoby się przesunąć to niżej


I'd still prefer us to be precise, but I'm not going to kick up a fuss about it.


No lo entendí muy bien al commit, pero si veo que es un cambio bien circunscripto.


@sgrif Ping


I don't know why this was not needed before, but it is in the latest version. I hacked the retrieval of the resource config in the test, but it may be a good idea to expose this in `Application` somehow (if not already). cc @ewencp


Na pewno wyłącz stąd index, bo jego obsługujesz przez root_path.


Small remark @StanCallewaert make sure your code comments are consistent, if you use capital letters to start your comment, do that with all comments, the same goes if you're using small letters. Consistency is key.


To ci daje resources


Yes, but if this always overrides it how does a client indicate that they want to use the default?

and if they're going to override it would they not want/need to specify the full redirect URL?


To też Ci daje resources.


Esto no se hace! Tenés que eliminar el código y ya. Total si le pifiaste, revertís el commit.


Please append the new currency


why not just
```c
else if (num_dig > 6)
```
?


Please open an issue with a script that demonstrates the bug, as per our contributing guidelines.


:blush:


I'm not sure I understand this comment. I get that the code is checking to see if "simpleErrors" are the only errors available in "errorsObject" but the comment didn't help because of that weird "given given" phrase.


Ok.. I added a success message at the end of the test.

I've also tried gazebo with the plugins installed from the brew formula, and they work correctly.
So we are now left to do some more tests (optional) and to decide where to publish this formula.
For this: @traversaro and @iron76


aRescale, bRescale as two first arguments? This way it will be assume standard partial application convention. It would also be easier to reuse the code.


Antes habia hecho en la funcion bsplvb un cacheo, me di cuenta de cuando lo hacia y lo saque, de esa manera no se necesita el catching. y es mejor


Pilnuj wcięć, nawet HTML ładniej wygląda z wcięciami.


Si funciona igual, es un golazo, porque moviste arriba `bsplvb` dos niveles de lazo!


Thank you


This is my python project, I will keep updated for several versions


Idem acá! muchísimo menos cálculo debería ser.


On 07/14/2015 06:15 PM, Andy Stewart wrote:
> @sitaramc <https://github.com/sitaramc> Please try 2e98692 <https://github.com/airblade/vim-gitgutter/commit/2e98692278aa25413d36b1d32bf01c2442a42f51>.

Thanks; it works fine now!


@kishan110 that doesn't seem like you issue would be related to the use of this plugin.  Any focus commands are limited to the scope of the select object.  If you want to PM me some details or demo code I'd be happy to help troubleshoot.


I changed the wording according to your comments:
Here is the new text:

Note that the interpreters shipped with zeppelin have a [default configuration](https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L397) which is used when there is no zeppelin-site.xml.


I plan to have it in separate method or even class to supported nested configuration. Also second TODO is related as I plan to add user friendly API for augeas tree entries.


Przydałby się jakiś flash wyświetlający błędy.


Está bueno esto, declarar y definir las variables cerca de donde se usan, para tener el scope visual bien apretadito.


there is no data API yet, only hash one used below for changing value.


Poczytaj sobie o link_to i używaj.


¿Cuánto mejoró con esto? Acordate de poner en cada commit: corrección y desempeño.


For some reason, I'm just now seeing these comments. Does the graph API support search? If so, we could fairly easily implement something like select2 to do the ajax search/selection.


link_to, jak w komentarzu wyżej.


Continuing the discussion in https://github.com/robotology/gazebo-yarp-plugins/issues/174


Length of CRTL field in forwarder encapsulation packet is 1 octet and not 2. Change it to:

    uint8_t ctrl;


I think the semantic distinction between this file-system reference and the symlink + filesystem 'hack' mentioned immediately above needs a bit of clarification.


Ładne potwierdzenie widzę :)


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


si, esto es de la ultima mejora que reporte en el readme, osea todas sin omp, con omp se logro mucho mas.
Donde se paralelizo el calculo de knot_pesos.


done.
https://github.com/GirlsCodersWarsaw/CakeMaster_Ania/commit/f715b1dfc30108cdf1ac2d60901f35a0787f2754


Might it be sufficient to cast after the product? Anyway, it probably is not performance relevant and thus does not do any significant harm. What would be more interesting: Has anyone seen a reduced iteration count from that?


I dislike having such high-res textures in the default game. It increases server connection time.


Separated.


Length of CRTL field in forwarder encapsulation packet is 1 octet and not 2. Change to:

    *wireless_node_id = &packet[3] ;


Length of CRTL field in forwarder encapsulation packet is 1 octet and not 2. Change to:

    *wireless_node_id_len = packet[0] - 3 ;


Why you made this change ?


not sure what you mean by symlink? (Or 'hack' for that matter!) All `jsnext:main` does is define the package's interface


I initially did it this way thinking that I hadn't verified it for FreeBSD.  But this library isn't building for FreeBSD yet, anyway, nevermind tests running, so it probably does make sense to keep this active for it, and then it can be disabled if it ends up using the same implementation as OSX.  Added.


Personally I would keep this one (but change the name to `appliedProperties`) for the sake of readability.


I consider this the wrong approach: As discussed above, the Image is bound to contain a SYSPREP.INF file. So the only potential use case is the administrator wishing to mass-replace all SYSPREP.INF files in all Images. I cannot think of any logical use case for this, because it is *certain* that there will be at least one Image having custom changes in its SYSPREP.INF, which will cause it to break if replaced. It does not make sense to mess with this file. I would propose to drop this feature even from the existing Windows support, instead of enforcing it on this new support for Windows XP.

However, if you insist, and you still consider this a feature, I will include this capability in a new commit, after this patch set has been merged, along with the necessary documentation fixes wrt the handling of boolean Image properties.


гораздо удобнее создать новый  ключ и сохранить его локально, например:
```yaml
    - name: make a keypair with the specified name
      ec2_key:
        name: main
        wait: yes
      register: key_data

    - name: save the key file to local host
      copy:
        content: "{{ key_data.key.private_key }}"
        dest: keys/private.key
        mode: 0600
      when: key_data.key.private_key|default(0)
```


pls fix whitespace


Ajajaaa, hiciste un commit que no compila.
![never-commit-broken-code](https://cloud.githubusercontent.com/assets/669067/8674056/b2605728-2a11-11e5-895c-4e821db8adbb.png)


no need to change order, just replace set_metadata with %SET_....


If they don't set the redirect uri then it will be set to the page where he started the auth flow (so the client doesn't have to do anything and this is the default behaviour).
If he sets it explicitly as a parameter in the options (redirectUri), then this will override the default behaviour


Início do versionamento #1


Yup, fixed.


Hi, sorry for delay.

$watermarkimage is a variable that store watermark image path. It can be setted on initilize method.

Cheers!


Yes, but I'm thinking it should NOT be your current page. It should be the redirect that was registered with the App.


Sure, added.


lgtm


Have you made an npm package?


This doesn't work. Remove the quotes arount `$_LP_SHELL_zsh`.


Closes #1


weird, a `LUI` is decompiled as a `MIPS_INSN_LL`(348) instead of `MIPS_INSN_LUI`(352)... and it seems  to be the case for all instructions with some random id. Something is fishy with `instr`.


Makes sense have this flag in both cflags and ldflags ?


Típico commit que deberías partir en dos, una del `Readme` y otro de los diversos cambios que hiciste!


I'd use "Show info for all unwatched items" as the plot or thumbnail shown may contain no "spoilers", however "info" is more ambiguous but that is where the help text comes in to explain. I have no strong opinion on this however, so I'm willing to leave it to your judgement what is best here.


nooo, cuando uuh jaja. perdon


No, it's not sufficient.  The product of two single precision numbers strictly requires a double precision number to store the result without round off.  This is something I'd been planning on fixing for a while, but it was motivated here because @alexstrel has been seeing unexpected convergence bahaviour that I suspect could be causes by inaccurate inner products.

Long term, for double precision data, similarly, I plan to have the inner products evaluated in double-double (quad) precision.  Our expectation is that this will improve convergence and/or deflation quality (in the large volume / chiral limit).


Makes sense to me (assuming we only run one... it'd be nice if we could run both, or at least have a periodic job in Jenkins that runs both... @mmitche?)


@rodfersou the main problem was your change reverting what I've done on the template


And just to note, this change has negligible effect on performance, since the reduction kernels are completely bandwidth and latency bound, and never flops bound.


@simonmcmanus so we are using Lanyard still


Did you use the master branch from the repo here? Can you check your cmake output? Did it use Qt4 or Qt5?


Pointers being pointers. A miserable __(*)__ fucking all the function! Thanks, Rafa.


заверни в синглетон и инжекти сюда


Тут как-то непноятно два раза Всех Победителей.


`precmd()` is already the hook used to update the prompt. See the `prompt_on` function. So the `precmd` will be overriden.

This patch has some interesting bits, but is not yet a finished solution.


Fijate que estas son pruebas tuyas, porque estás aprendiendo a como se hacen las cosas con OMP, no debería haber commits así. A lo mejor usás git para backupear o para transferir archivos a mini? La solución para ambas cosas es montar un directorio de mini local en tu máquina con el manejador de archivos de GNOME e ir haciendo las pruebas remoto. Cuando tenés algo que te gusta y pensás que funciona y está prolijo, ahi hacés el commit.


The MeinBerlin button theme has ended up a bit messy due to plain buttons having been implemented as cta2 buttons as this was all before we defined what cta2 was properly. Ideally the plain looking buttons are just 'buttons' and there is no cta2 in this context. I plan to refactor this @xi ?


плохой метод. по сути ничего не инкапсулирует. логика утекает в контроллер. надо делать методы типа GetById, GetByName и т.д.


This comment is probably misleading because I think we will never call `update()` from the moment we set a style to the moment the style gets loaded.

IIRC this check exist to protect this code from a pending update at the moment we are destroying the `MapContext`.


To the lazy eye, the distinction between `import cheekyHack from 'undocumented/private/module'` and `export { partition } from './src/collection/partition' ` isn't significant.

Presumably what's needed is to deprecate NPM's ability to crawl registered dependencies' folders?


there is no more `.dockercfg.template` on master branch


Excelente.


Makes sense.  Looks like we can merge then.


for now, we'll just use a text input for greater than 199 groups: https://github.com/WebDevStudios/aad-sso-wordpress/commit/4dd606b417c454ebca33b8b120c2cf8efead110b


I think it would be useful to mention in the commit note that this is not enabled in production simply because we don't know if there's anything wrong with it rather than an unspecified important reason.

Also, it still feels wrong to me to return markup (govspeak) when plain text is requested. However, since nothing but regression tests depend on it, we can always change it later :)


Fixed: https://github.com/WebDevStudios/aad-sso-wordpress/commit/d6043b9a87cc5054dc6d202668ce4ce3296a8c14


@psignoret nah, should be fine. Updated: https://github.com/WebDevStudios/aad-sso-wordpress/commit/3f987887510a8e0c7edc5bf174fb68a368b8459c


:) glad its fixed!
Alan
On Jul 14, 2015 4:42 AM, "Dave" <notifications@github.com> wrote:

> Found the problem - another rogue version of functions.php sitting in the
> /var/www/ directory so all the function calls were being made to there
> apparently.
> Thanks for your help.
> Dave
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/astead/rasptimer-1/commit/9eb6f2bc4964eddeb219461091e720267419ada7#commitcomment-12153838>
> .
>


This MIPS version of capstone sounds broken. While the disassembly is correct, the ID is wrong.


¿Está bien esto? El corrimiento de `i` en `1`, debería cambiar acá también en uno y yo veo dos de diferencia en el offset, o sea de `+1` a `-1`.


`const TimePoint& now`?


Ta, si lo hacia asi, pues hasta que subía mis cosas al mini por medio de ssh o haciendo copy paste en vim (que mal) tardaba y lo otro era mas fácil. Bueno ahora hago cambios que deben ser. Pero puede ser.


ToDo: inicializar a NULL todos los punteros que declares. `double * vx = NULL, * vw = NULL;`


This commit LGTM.


Nope. SELinxux is messed up. I need to make it from sources.
And I also have to update it to the latest preview :/
I heard you was working on it too


copy-pasta?


Well, if you can set up the redirect url that is different than your current page, why not setting it in the initialization of your Client instead of setting it inside your App registration page?


This commit LGTM


Great, I wanted to use this method!
Thanks for this contribution, it looks good for me.


wrong closing apostrophe


It boots fine
But there is an error with libc ( segfault ) and libs aren't loaded
I'm happy with android m & adb shell xD


To replace by name of the module as title


Please make errors appear within given input - if name is empty then error should be visible underneath or above :name field


OK. Thanks. I'll add that to the commit note.


A suggestion:

[Enabled] Shows the plot information for movies, and for TV shows the plot information and episode thumbnails, this applies to all unwatched items.
[Disabled] Hides plot information for movies, and for TV shows the plot information and episode thumbnails, this applies to all unwatched items to prevent possible spoilers.


No se si sirve agregar el binario del `gprof` ya que debe estar ligado al binario ejecutable. Deberías ver como obtener la información en plaintext usando `gprof` sobre el output generado por la corrida.


We should definitely refactor buttons. I am not yet sure about the details. We should make sure whether we need 3 types of buttons in core.


"Temporary" means it will be gone once the `client` attribute/property is present?


плохо. надо добавить в репозиторий метод Delete


Info doesnt cover the thumbnails while spoilers covers all that could constitute a spoiler irrespective if the plot/thumbnail contains one or not. Its impossible to determine where a spoiler exists and what may constitute a spoiler for any given user imo.

Also Its extremely difficult to keep this label short while modifying it enough to cover the whole range of the two actions that are covered by enabled/disabled state here in respect to movies and episodes at same time.
This was the best I could come up with and I dont think I can come up with any better alternative.


Yes, I know your facing that :p
LIBCXX flag was introduce. And mess up a lot of things...
I have a lot of time to work this summer.
I know you are from the titan community and if you want we could work together ?


esta bien, el código de antes estaba corrido en 1 y así que lo moví
Ahora que lo vuelvo a pensar puede que tengas razón, pero en un primer momento saque el +1 solamente y no basto. Luego probé con el -1  no me acuerdo que se me cruzó. Pero con el -1 anduvo, y lo dejé.
Me acuerdo que lo pensé así el arreglo debe setearse a lo sumo en n - 1

AAAh si, es eso, el i empezaba en 1 y el arreglo estaba indexado en 1 tambien


This commit LGTM.


@alisha-ajency move to separate less file


This commit LGTM


ah, sorry pensé que servia. Luego lo paso ( a copy paste ) a un log


@ceolin I removed from CFLAGS and its still working, nice catch (:


Fixes this: https://github.com/qgis/QGIS-Website/issues/271 (wrong repo)


hm, since we are going to store this in a global Downloads dir, there is a nice chance that someone can have some file called ca.crt there we would override.
I would propose to either rename it to movirtca.crt or create a subdir movirt and add the file there.

But anyway, it does not seem to work on android 5.x anyway, so I will have to investigate a bit more what the issue is and maybe this patch will not need to get in after all...


@alisha-ajency  define colors in variables.less


Join irc freenode @ #titandev ;)


Please replace `reserved keywords` with just `keys`.


@alisha-ajency avoid using !important so much. Be more specific when targeting a class instead.


I did `len(cli_sections) > 1` since the default section is every time existent. I just tested to create a coafile from command line and using `len(cli_sections) > 0` yielded the same warning as before.
But you are right just invoking `--save` should also trigger no warning, `save` is the better way to go.


Fixed in fbfeb931aa1ee2b27ab5d4dbdb1862485b28c744.


@gsscoder, that's what I'm saying. This commit don't change a thing: both tests you added (`if (parsed.Value is T)` and `if (notParsed.Value is T)`) are always true because `Value` type is `T` by definition.
Otherwise, I you want to keep these lines because you want the code to be the similar between each methods, then I understand.
Promise, I don't bother you again on this commit :smile:.


Typo here


At some point soon I'm going to rewrite this entire README since it's not such an experimental project any more (we're using it in production) - when I do, I'll try and make all this a bit clearer. I can't imagine the node module resolution process ever changing, since it's the only tool we have to prevent unnecessary code inclusion with CommonJS modules, but if ES6 modules reach a wider audience hopefully that practice will die off by itself!


Agree. Will change.


To be honest I wasn't sure what I should use else. Since coala executes an empty `Default` section, it does something, so writing "Doing nothing" is also wrong.
Wanted to kick off a little discussion about that :)
So do you have an idea?
@coala-analyzer/coala-contributors Maybe someone else?


#drinking_a_glass_of_wine_during_a_backflip


Dodaj zagrade radi citljivosti `(0 + Task01.CIRCLE_SIZE / 2)`


This commit LGTM


thanks :) i am not very "in" the cm12.1 development currently. Why isn't it used? Is there another way to get this working on cm12.1?


Please don't couple this to the package manager. It's fine if day-to-day usage relies on the package manager, but it makes no sense for it to *require* using the package manager.


I use https://launch.usegalaxy.org with the default bucket (cludman-test I think) - is that the tip?


This commit LGTM.


Hmm, I can look into that.  This might be a useful case for a mock since we don't really need to query the BTS to verify the functionality.  We just need server.get_status() to provide data that looks like it came from the BTS.


Posto se `repaint()` poziva nakon svakog uslova nema potrebe da bude u svakom `if`, tako samo ga stavi dole ispod. Tri linije code-a manje.


As I said no strong opinion on this one as it's not something I'd use either.


Hi - you do not need to copy all the web templates to do a new cobrand. Templates are inherited, as explained at http://fixmystreet.org/customising/templates/ so if you put the "parent" in path_to_web_templates in your .pm file, it will look there first, see the existing entries. This should make it much simpler, and also make it easier to pick up  updates from upstream.


Isto


Thanks!


That changes don't work

TypeError: Cannot read property 'match' of undefined
    at Object.compile (http://localhost:9000/bower_components/oi.multiselect/dist/multiselect-tpls.js:343:37)


I like this. :+1:


Hi, Slávek confirmed, that we want also admins derived from groups. For you it's simple change, just switch last param to ``false``. Thank you.
```java
userAdminList = sess.getPerunBl().getGroupsManagerBl().getAdmins(sess, group, false);
```


@alisha-ajency this isnt a web font so has this font file been added to the site? Also is this font being used anywhere else on the site?


Fixes #498 (Forgot symbol).


Posto je `@Overide` znaci da postoji `default` implementacija, i mi ovdje `overload-amo` metodu. E buduci da ne radimo nista u istoj mozemo to izbrisati.


You could retrieve the domain class using the GdtService.getInstanceByEntityName method


Comment removed, thanks!


I think it would be better to also implement the method in TableHeader and let that return no classes (like TableCell).


This goes away in 28c6d44 :-)


I would suggest to keep the logic inside the service, but call the service methods within the controller, and pass the results of the service to the view


This commit LGTM.


The same applies to the main pormibarrio templates too, it looks like many of them are shared with the parent, which may make it easier to merge upstream. Hope that's helpful :)


What @henrikhodne said. I think this changed the meaning, will fix. Otherwise :+1: <3 <3 thanks for the changes.


Super, komentari su tu dosta ih se primjenjuje na vise mjesta tako prepoustam tebi da to pregledas. Pomoc je uvijek ok, i lijepo od tebe sto si naglasila al nije bitno. Bitno je kao sto kazes da znas uraditi sama. Sve super, fix pa moze :checkered_flag:


So what is the purpose of the redirect in the App registration page if clients are not able to utilize it? I'm not saying this is important, it just seems strange that we would have a redirect registered with the App but then we don't allow clients to use it.


did you hear about ``np.where()``?


any reason to do so?


error updated


why did you chose to use circleci instead ?


This variable is never defined in the function scope, just in the if ... else scope, which I think will generate a notice in PHP.


The use of "should" here is best avoided because "should" has a specific RFC2119 meaning that isn't what you intend here. I might say "[…] explicitly documented in the spec, therefore the second caption must not be affected by the use of ```deleteCaption```"


Minor, "styling" and "style" is specific to the use but ambiguous to the relevance to a check. Instead, since it's value is based off a check's result, how about naming it something that includes "result"?


I don't understand "may not have a caption may not be present".


Gee. I find this format easier to read when scanning the code.


"similarities to other standards" or "similar features in other standards"?