1: D100 Docstring missing
21:1: I201 Missing newline before sections or imports.
23:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibindex.engine_stopwords
23:1: F401 'CFG_ETCDIR' imported but unused
24:6: E126 continuation line over-indented for hanging indent
68:1: E302 expected 2 blank lines, found 1
68: D400 First line should end with '.', not 'g'
68: D205 Blank line missing between one-line summary and description
81:1: E302 expected 2 blank lines, found 0
81: D103 Docstring missing
92: D401 First line should be imperative: 'Return', not 'Returns'
92: D205 Blank line missing between one-line summary and description
92: D208 Docstring is over-indented
106: D401 First line should be imperative: 'Return', not 'Returns'
106: D205 Blank line missing between one-line summary and description
106: D208 Docstring is over-indented
120:1: E302 expected 2 blank lines, found 1
120: D401 First line should be imperative: 'Return', not 'Returns'
120: D208 Docstring is over-indented
130:1: E302 expected 2 blank lines, found 1
130: D400 First line should end with '.', not 'e'
130: D205 Blank line missing between one-line summary and description
159:1: E302 expected 2 blank lines, found 1
159: D400 First line should end with '.', not 'e'
159: D205 Blank line missing between one-line summary and description


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
33: D203 Expected 1 blank line *before* class docstring, found 0
33: D205 Blank line missing between one-line summary and description
33: D208 Docstring is over-indented
50:41: E251 unexpected spaces around keyword / parameter equals
50:43: E251 unexpected spaces around keyword / parameter equals
50:66: E251 unexpected spaces around keyword / parameter equals
50:68: E251 unexpected spaces around keyword / parameter equals
50:94: E251 unexpected spaces around keyword / parameter equals
50:96: E251 unexpected spaces around keyword / parameter equals
50:123: E251 unexpected spaces around keyword / parameter equals
50:125: E251 unexpected spaces around keyword / parameter equals
50: D102 Docstring missing
54:5: E303 too many blank lines (2)
54: D400 First line should end with '.', not 'e'
54: D205 Blank line missing between one-line summary and description
54: D208 Docstring is over-indented
60: D102 Docstring missing
63: D102 Docstring missing
66: D102 Docstring missing
69: D102 Docstring missing


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


1: D400 First line should end with '.', not 'e'
1: D208 Docstring is over-indented
48: D203 Expected 1 blank line *before* class docstring, found 0
48: D204 Expected 1 blank line *after* class docstring, found 0
48: D208 Docstring is over-indented
121: D290 White spaces around docstring should be trimmed.
121: D400 First line should end with '.', not 's'
125: D290 White spaces around docstring should be trimmed.
125: D400 First line should end with '.', not 's'
129: D290 White spaces around docstring should be trimmed.
129: D400 First line should end with '.', not 's'
134: D290 White spaces around docstring should be trimmed.
134: D400 First line should end with '.', not 's'
138: D290 White spaces around docstring should be trimmed.
138: D400 First line should end with '.', not 's'
142: D290 White spaces around docstring should be trimmed.
142: D400 First line should end with '.', not 's'
146: D401 First line should be imperative: 'Choose', not 'Chooses'
146: D209 Put multi-line docstring closing quotes on separate line
146: D400 First line should end with '.', not 's'
146: D205 Blank line missing between one-line summary and description
146: D208 Docstring is over-indented
151: D401 First line should be imperative: 'Choose', not 'Chooses'
151: D400 First line should end with '.', not 'n'
151: D205 Blank line missing between one-line summary and description
151: D208 Docstring is over-indented
159: D102 Docstring missing
169: D102 Docstring missing


1: D200 One-line docstring should not occupy 2 lines
23:6: E126 continuation line over-indented for hanging indent
28:1: E303 too many blank lines (3)
28: D203 Expected 1 blank line *before* class docstring, found 0
28: D208 Docstring is over-indented
28: D200 One-line docstring should not occupy 3 lines
33:41: E251 unexpected spaces around keyword / parameter equals
33:43: E251 unexpected spaces around keyword / parameter equals
33:66: E251 unexpected spaces around keyword / parameter equals
33:68: E251 unexpected spaces around keyword / parameter equals
33:94: E251 unexpected spaces around keyword / parameter equals
33:96: E251 unexpected spaces around keyword / parameter equals
33:123: E251 unexpected spaces around keyword / parameter equals
33:125: E251 unexpected spaces around keyword / parameter equals
33: D102 Docstring missing
35:49: E127 continuation line over-indented for visual indent
36:49: E127 continuation line over-indented for visual indent
37:49: E127 continuation line over-indented for visual indent
40:5: E303 too many blank lines (2)
40: D400 First line should end with '.', not 'e'
40: D205 Blank line missing between one-line summary and description
57:5: E303 too many blank lines (2)
57: D400 First line should end with '.', not 'r'
62:5: E303 too many blank lines (2)
62: D205 Blank line missing between one-line summary and description
62: D208 Docstring is over-indented
71:1: W391 blank line at end of file


@heejaechang, could you look into that?


Done :)


Why 42? It seems dangerous to have such a place hard-coded


> Sounds fine, as long as wherever it is merged in is easily accessible from the commands. What object do you think it makes sense to be attached to?

Not sure. I'm hoping that in that refactor something will make sense!


Added

On Fri, Mar 13, 2015 at 3:36 AM, nanflasted <notifications@github.com>
wrote:

> Hey Jack add me to this repo so I can push my music through
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/WJLiddy/ad2/commit/a9537b27f9cca5917032b7ffc0ea17c9b3920612#commitcomment-10180293>
> .
>

--
William "Jack" Liddy


Why adding the data here? Not really needed


Using -1 here and +1 up there seems like a bad idea because what if the player gets to a corner and would go down? I feel like you should look at the X/Y coords and compute the new index? Or just have a list with the things in any order with their X/Y totally determined by the value


passed `$scope.cvData`twice here, so doesn't work ...


@pippinsplugins not sure about that change as if you check any pot file:

"__;_e;_x:1,2c;_ex:1,2c;_n:1,2;_nx:1,2,4c;_n_noop:1,2;_nx_noop:1,2,3c;esc_"
"attr__;esc_html__;esc_attr_e;esc_html_e;esc_attr_x:1,2c;esc_html_x:1,2c;\n"

_n:1,2 so it should be _n:1,2,3d -


LGTM


I haven't heard that before. What about Dr. X instead of Professor X?

I just changed my advisor to Rebecca Williamson, Ph.D. but before it was
just Rebecca Williamson... based on her status as my advisor,
Ph.D/Dr/Professor are all implied anyway. I only changed it to make it
consistent with my other supervisors' titles (ex, Katie Walsh MSW)

On Fri, Mar 13, 2015 at 11:02 AM, Elsa Gonsiorowski <
notifications@github.com> wrote:

> You should use the title "Professor" where appropriate because it implies
> something higher/better than a PhD.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/annagons/annagons.github.io/commit/a2b40a37b9059e1967165778ef703ae65999825b#commitcomment-10187130>
> .
>

--
Anna R. Gonsiorowski, M.A.
Graduate Student
Learning and Development Lab
Georgia State University
agonsiorowski1@student.gsu.edu
(404) 413-5076


If it's IE, why even have the .svg version?


Sorry, could you put your name after Chris E's to keep the list sorted alphabetically by first name?


Links


Do we want to use "//www.cru.org/images/cru-logo.png" so it can call either protocol? Does IE support that?


The change to these two lines makes the datepicker never show up.


Good solution


Juste changé la classe ici pour coller au thème.


I put the `as` back in the general list because it is also used in `export ... as ... `;


Ok, so you prefer this:
![screen shot 2015-03-13 at 9 52 52 am](https://cloud.githubusercontent.com/assets/6991149/6641956/cc2414a8-c966-11e4-9206-e791c30e675d.png)
to this, right?
![screen shot 2015-03-13 at 9 53 06 am](https://cloud.githubusercontent.com/assets/6991149/6641970/e73f52a2-c966-11e4-9a7d-12098d7fb693.png)
I do too.

When a new file upload field is added...are you talking about on the back-end?


why did you only move ```add_rostest``` and not all test related statements?


Please take care too not accidentally enable testdata!


Dans ce fichier j'ai juste repris le paramètre qui m'intéresse plutôt que tout le fichier et je l'ai changé pour qu'il utilise ma classe plutôt que celle d'origine.


https://github.com/node-xmpp/node-expat/issues/112 people with the same problem


Forgot about the pull request protocol.


No, its this change that caused it

Webstorm recommended that i changed

scope.enableDate = !(scope.enableDate == false);
scope.enableTime = !(scope.enableTime == false);

to

scope.enableDate = scope.enableDate === false;
scope.enableTime = scope.enableTime === false;

On Fri, Mar 13, 2015 at 3:53 PM, edmondchui <notifications@github.com>
wrote:

> The change to these two lines makes the datepicker never show up.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Gillardo/bootstrap-ui-datetime-picker/commit/3f097bf00f29e4abc94bdecd325baea46afea9a2#commitcomment-10188235>
> .
>


Je n'ai pas encore trouvé comment afficher la "locale" actuellement utilisée avec Sylius (hors controller/service). Pour l'instant c'est minime donc j'ai préféré faire simple. Suppression du span value donc.


LGTM.


Thinking more about it, what higher-level retry logic do you guys actually have in mind?
What would be a real-world use case for higher-level retry?


So I'd guess that, in principle, the global structure address and the offset (size of some struct?) could also be extracted by the [kernelinfo module](https://github.com/moyix/panda/blob/master/qemu/panda_plugins/osi_linux/utils/kernelinfo/kernelinfo.c) used by the `osi_linux` plugin?

Currently, `osi_linux` calculates the address of the current task struct using the ESP while in kernel mode. Which means that it can only retrieve the current process info when it executes in kernel mode.
On the upside, the ESP-based approach will run on all of x86, x86_64, arm. While the code in this file is architecture specific.


Yes, I do prefer the first one. In Chrome the second looks even worse.

When you have an upload field with multiple files allowed, after you select a file, another upload field appears below it and the first one is hidden


This does not work very well for the current live data, countries with a low user count are barely noticable (see Russia, but even worse for smaller countries like Ecuador).
![screenshot from 2015-03-13 16 53 28](https://cloud.githubusercontent.com/assets/149825/6641997/ce2a5d12-c9a1-11e4-8efe-db5f87e85bed.png)


You are no longer incrementing it by 1 though


Good point, I just copied it and just changed what I've seen so far.


I looked at this briefly when going through some other issues, and a question arose.

Why change just the password, why not specify a new set of ```Credentials``` entirely? It seems like this is fraught with peril, just changing the password. Wouldn't it make sense to set the entire credential from the BeforeInstall method?


Do we need a `@ReallyIgnore` annotation? ;)


@2beaucoup Thanks for the pointer to monodraw. Looks awesome!


Super neat now. :)


Wouldn't this make more sense in server.rb, to go along with destroy()?


oO


Hi! Yeah, I figured the chip has 64K (fast) CCM memory so we might was well use it, at least for the stack, state and a few LUTs. While my first tests after setting it up were positive, there seems to be a side effect loading kits that I need to track down, so I wouldn't merge it just yet :) That's the last status I gave Julian too. Like the circular DMA branch, it doesn't provide any real features but might save some cycles for useful stuff :)
Cheers,
-- Patrick


Thinking just in terms of consistency... I do like your addition of ", Ph.D." I think this is better than doing Dr. X, which makes me think of a research staff/someone that isn't tenured faculty. Honestly, I think you're right that a qualifier isn't really necessary for "Advisor." But that does make consistency difficult...


Its, without an apostrophe, is the possessive of the pronoun it.


Cambios mínimos


r+


@jordansissel
following your comment i could foresee two alternative distinct approaches
-  extending current format to something along ...

   ```
  # The local section covers local, client specific, configuration
  "local": {
    "host": "${rebrandedHostname}"
  },
  # The network section covers network configuration
  "remote": {
  },
  # The list of files configurations
  "files":{
  }
```
in this scenario, one could, also, argue that most existing command line flags would then make most sense in the local section either _too_ (duplicate ways of achieving same, messy) or _instead_ (more consistent, but then there would be the non trivial backward compatibiliy issue.

- alternativelly one could just extend it, inside the *files* block, to ...

  ```
"files": [
    {
      "paths": [
        (...)
        {
          "paths": [
            "/var/log/apache/httpd-*.log"
          ],
          "fields": { "type": "apache" },
          # optional
          "host":  "${rebrandedHostname}"
        }
     ]
```
at sight the later approach seems simpler and less intrusive in my view if not the most *aesthetical* ever.

so, want a PR for which one, or none of the above ? :smile:


Ok then, we have some conflicts (ftw-buildouts vs Plone KGS vs lovely.buildouthttp vs ftw.recipe.translations).
I'm looking into it..


If this will ever need change it may be a good idea to move it to settings. Also we may want to write some specs for this so that if someone adds something else that needs to be whitelisted without adding it here it'll break.


There is a problem with these data. A lot of villages are repeated and apparently the coordinates are wrong. Some villages are located in the sea.


Now that the UI Tool Bar button item of camera shows correctly on screen, the first responder for the valueInDollars field is broken, and the keyboard number pad no longer slides onto the screen!


@sils1297 Should i implement this in this issue ?


I think he means the last part of what I said. Approvers should be able to see all claims with the submitted status that don't match their name. We can further refine that too


Where to we obtain all this information?  I would hate to maintain it :scream:


no ensureGreen required


Nicely caught, thanks!


Oops.  Fixed in 1ac806f50bd1dada058eeba0734bcdd3a7377eee.


@corvannoorloos

You are more than welcome to remove it yourself in your theme.

```php
remove_action('wp_footer', 'Roots\\Soil\\GoogleAnalytics\\google_analytics', 20);
add_action('wp_head', 'Roots\\Soil\\GoogleAnalytics\\google_analytics', 20);
```


Non-standard transactions are invalid; can't have a "maybe", you know.
Undefined is a "no" IMHO. There is a single set of rules for everyone.


mips3 needs c++11, but we can disable it for now since it is still WIP.


can you also do a "delete by query" test ?


It's compiling now, thank you.


What about multicompany cases where the user is in a different company than `product.list0`?


Strongly suggest including the "RCD reveal" as part of TXID, i.e. -- hash as much of the (fixed parts of the) TX as possible.


@ch3cooli
What do you mean by?

> Also in GitLogListBase.cpp, please do error checking of SafeGetSimpleList()

Suppose you mean that we have to introduce try-catch inside SafeFetchFullInfo?


Stupid phone.

We can further refine that to approvers only being able to see submitted claims that don't match their name, and resubmitted claims that that don't match their name and which they were the approver of. The bit about resubmitted claims is not required, though we should probably do it anyway I think.


Github test


r+.  I'm sure I've seen this code before, not sure if it was from a previous review for this file or if there is similar code in another place.


testIndices isn't very descriptive :(


Should we remove the personality routines on Unix everywhere, not just in these two places?


LGTM


Nit: use double quotes


its the name of the method to test


@EssArrBee Just wondering, why was the after metadata removed?  Someone had to have put it there due to user or author suggestion.


important!!!


One example strategy could be something like "Retry every 5XX response up to Y times".


Do we have any version for these changes?


Well, I was thinking about that. `@Ignore` sucks, because it says what to do (ignore) but that can depend on circumstances and doesn't retain why it should be ignored. In hindsight we should have used something like `@Dpm`, `@Bridge`, `@Serialization` etc, just like java permits `BRIDGE` and `SYNTHETIC` in the class file flags.


This has flare.


Yes, I believe we should. I'll create a work item for that since I want to analyze the reason for their presence first.


Can we add an example to the README demonstrating how we can now bootstrap minions all at once.
And can we update CHANGELOG.


ack


Sorry, this should just be the following:

```ruby
header.field('xmlns:setSpec'), :as => :coll do
```


These changes are invasive. I need to fix the actual problem.


This is mostly to cover the case of multiple cursors inserting simultaneously. In the majority if not all cases, each cursor will have inserted the same text, so I'm just bundling up the first cursor's insertions. Before, if you inserted text with multiple cursors and then used `.`, all of the cursors' insertions would be concatenated together and inserted after the last cursor.


id_cate_livre n'est pas un "input" mais un "select". Désolé si je t'ai donné du mauvais code.
Je mettrais plutôt cette partie de JavaScript dans le bloc extra_head de livre_form.html, car il n'y a pas de raison de l'avoir sur toutes les pages.


Yep, I created the issue for this https://github.com/tutumcloud/tutum-app/issues/3345


Right. These would have to be extracted by kernelinfo. We do want to be able to get the current task struct in user mode, though. I wonder if it's possible to get the kernel-mode value of ESP from the `IA32_sysenter_esp` MSR?


façcon -> façon


> I'm sure I've seen this code before, not sure if it was from a previous review for this file or if there is similar code in another place.

There is similar code in the setup of GCLI on the web.

I fixed the ' to " in my working tree, but I've not pushed it yet


because the function can not return an error message as hadler is NULL


Hm. Yeah, I will get rid of the double negation. It's confusing me as well.


It would suffice. I actually meant to remove the `?` though, and just have the `and`, to preserve the symmetry between `isAppending` and `isRemovingFromEnd`. Sometimes, when there's two nearby blocks of code that do very similar things, I like to make slight style adjustments so that they look the same as each other. It's just a personal habit.


No because the same code is used for both (100 %coverage) and the this test tests the C API, not the pfw.


I populated the ROM database with the values and just copied the logic used for grabbing the players and rumble ability from the file.


Nice commit message. Explaining the fn could also be helpful in the fn doc string.


@foutoucour : Why this ?


Would it make sense to create the `Machinery::Config` object somewhere more central, so that you could just do something like `if @config.experimental_features` here (and in other places)?


nit: call this resourcetype to be consistent with naming


Dude imageclient is not building for me.  Its saying some properties file is missing.

Check that. I am having issues with speed of the internet, so can't do much today


could use `check_only` or `peek` for the name of this parameter.


ouaiis c'est cool git


ack


and a comment would help to understand this early return.


Furthermore, the imagePicker view refuses to appear, even upon tapping on the camera. What is going on?


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1002
success: http://build.servo.org/builders/linux2/builds/1001
success: http://build.servo.org/builders/android/builds/1036
success: http://build.servo.org/builders/mac1/builds/1217
success: http://build.servo.org/builders/mac2/builds/1218
success: http://build.servo.org/builders/gonk/builds/188


Any reason the use of result=~~result is being removed? I found without it hash codes were unreliable in GWT - and in fact found GWT used this approach in its JDK emulation.


Removed hacks in 77f9d1e223


Here is my comment.


Oversight, I used what eclipse auto picked when I used the class.  No need so I will make it lang


CyaSSL/my code won't load ca-certificates (OpenWrt BB) properly. The set_verify_locations call returns E_COMPRESS.

Some hypotheses:

* I somehow managed to compile without zlib
* There is a problem with the hash symlinks: OpenSSL c_rehash changed from MD5 to SHA1. However, CyaSSL apparently does not care about the naming conventions
* CyaSSL gets confused by the symlinks

Possible workarounds if I can't get it fixed:

* Let user specify single root CA
* Concatenate all CAs into single file


I'm a bit confused by the syntax here. The parser is not converted to a filter, but the filter options are parsed.


J'ai remplacé le type <Element> par <Exit> de la liste "exit" (anciennement "obstacles") puisse que l'on met que des Exit dedans...

Le bug téléporteurs provenait je pense de l'affectation :
- position = pos;
remplacé par :
- this.position.setAbsciss(pos.getAbsciss());
- this.position.setOrdinate(pos.getOrdinate());


My guessing is checking the return value of SafeGetSimpleList().


Over 3000 lines deleted for a "small typo" correction?
Please check.

Btw, perhaps we could split this into an extra subproject.
As it stands, I am doing changes in the work 23 branch, and when the merge fails because of such "small corrections" I'll be very upset. :)


fast-forwarding master to auto = a5080705


I throw stuff in and out if the window during development. Right now I have a new form builder for my local branch using sky-forms from Unify 1.7 ;) So right now I'm trying all form solutions haha.

Gonna fix breadcrumbs before merging into master.


r+


Perhaps we can make this hydrator class name configurable in Configuration.php ?


333th commit. So lucky :)


Should onKeyEvent first increment it by 1 and then pass it into the
returned game?

On Friday, March 13, 2015, Jay McCarthy <notifications@github.com> wrote:

> You are no longer incrementing it by 1 though
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/alalcantara/game1/commit/99f0e1b657842e2ea27ffeaef46a1953e040fd43#commitcomment-10188320>
> .
>


What happens, if the description passed here is different from the description passed to `inspect`? This will result in inconsistent results.


@jmchilton, this look correct? Fixes Pulsar in my testing.


I uploaded the latest version here.
https://github.com/higebu/packer/releases/tag/v0.7.5.higebu2
I'll test on Windows tomorrow.


It feels unnatural to have this function in the inspector, if it only uses methods from the description.


this indentation is actually wrong. I know the right one is ugly but we agreed on that.


Django model name is translated automatically by Django using model Meta class.
You should use model Meta class for translations:

```py
from django.utils.translation import ugettext_lazy as _

class Client(models.Model):
    name = models.CharField(max_length=256, verbose_name=_('name'))
    class Meta:
        verbose_name = _('client')
        verbose_name_plural = _('clients')
```

If i will accept your PR then it will be translated once more by already translated string.


Shouldn't ';' be ',', and .format(indentStr)?


@Cain-Ish wymusiłem kolejność ładowania naszych resources. Sprawdź, czy jest poprawna.


maybe add parameter description? (your choice but I think it's not bad to have)


Wow great idea!


Согласен: https://msdn.microsoft.com/en-us/library/ms256152(v=vs.110).aspx


i keep banging my head on the keyboard about this


So what's going on here?  I don't see this as related?


changed title bar


You're the opposite of Mischa. He comments everything (e.g. "Throwing exception" <- real life example) while you don't comment at all. Maybe you want to leave a word or two on why this works since we had some misunderstandings about this during last review?


Странный коммит :) Как так вышло?


This is true, I'll tell to Alioune to review the file.


too much is never enough... lets keep w o r d s.


Sorry i can't accept PR, because changes must be made in .LESS files not .CSS
Could you tell me more or show the screenshot what is the difference?


is it possible that the second condition part yields true?


My understanding is that these are the bound values which flow through from changes to the DOM, so unless we're doing some automatic conversion I expect they are `String`s.


^ and the first doesnt


Perhaps you should think about moving to another compiler, c++11 will probably be required for v0.2.97.36, and your compiler seems to handle c++11 badly.


`julia 0.3` already means "0.3 and higher". `julia 0.3-` means "any 0.3 prerelease and higher"


Is this the right place to apply the filter? I would see the filter and the description as two independent objects and expect the calling code to apply the filter.


Thanks, I thought I removed that.


good job


Shouldn't this change in TextRange have happened in src/modules rather than in lib?  It looks like this change has been lost.


SLPG ne fonctionne pas; J'ai tenté de détecter le problème mais on nage là dedans
Commente tes méthodes stp


I think I would be better off making a separate initialization function so the c++ compiler would not complain about the vector.

Or i could not be doing something right with the constructor since the compiler complained that the constructor parameters in movement.hpp is inaccessible


Yet another nail in the coffin of that codebase then.


true


Yes, and I'm thinking we need to know if it's the last one in the list or not, because some JS is really mean about the trailing `,`.


Please remove debugging code.


Fatcow Icons!


Reverted.


@bochoven or @nbalonso -- Any chance you guys could help me figure out why this isn't adding each profile payload to the database. I stole code from the display_info but it doesn't seem to save the data on the iterations through the for loop. Basically - it will right the first payload into the database but nothing after. I have the PayloadData set to "test" right now for testing. This is the file I am parsing.
```
ProfileUUID = 6e1c8360-6ce3-0132-898f-10ddb1d12656
ProfileName = Settings for test
ProfileRemovalDisallowed = no
PayloadName = com.apple.wifi.managed
PayloadDisplayName = WiFi (TEST#1)
PayloadData = test
---------
ProfileUUID = 97856B72-A033-4C70-B938-81036F79176C
ProfileName = Remote Management
ProfileRemovalDisallowed = no
PayloadName = com.apple.mdm
PayloadDisplayName = Device Management
PayloadData = test
---------
ProfileUUID = 97856B72-A033-4C70-B938-81036F79176C
ProfileName = Remote Management
ProfileRemovalDisallowed = no
PayloadName = com.apple.security.scep
PayloadDisplayName = Device Credential Request
PayloadData = test
---------
```


The values were filled automatically by the way, I just pulled a few tables off Wikipedia and did a loose match on the game name. 30 or so games had different values for the Players field so I checked Google to see which ones were correct. Minor things like Bomberman Hero actually only having singleplayer, not 4-player multiplayer.

Then I figured why not populate it with the other fields in the table so people can sort by release date if they want, or search for games made by a certain developer or whatever. Might need to add attribution tho.


Ah, I missed the very first file on the page since it was collapsed.  Wow!!

Would you mind submitting that file as a pull request to upstream?
https://github.com/mupen64plus/mupen64plus-core/tree/master/data


Or pass "time + 1"

On Fri, Mar 13, 2015 at 12:21 PM, alalcantara <notifications@github.com>
wrote:

> Should onKeyEvent first increment it by 1 and then pass it into the
> returned game?
>
> On Friday, March 13, 2015, Jay McCarthy <notifications@github.com> wrote:
>
> > You are no longer incrementing it by 1 though
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/alalcantara/game1/commit/99f0e1b657842e2ea27ffeaef46a1953e040fd43#commitcomment-10188320
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/alalcantara/game1/commit/99f0e1b657842e2ea27ffeaef46a1953e040fd43#commitcomment-10188898>
> .
>

--
Jay McCarthy
http://jeapostrophe.github.io

           "Wherefore, be not weary in well-doing,
      for ye are laying the foundation of a great work.
And out of small things proceedeth that which is great."
                          - D&C 64:33


Perfect. With the autofocus property and the left-align margin in input. That's our home page. (y)


True, contrary to script, install stops on first error.


port too?


Please, use more descriptive commit messages


@jgawor
This is kind of what you asked for?Thanks!.


Maybe should not have used isdigit, but seems silly to check if char in '0123456789' instead of just calling char.isdigit()


Why are we sending the same value to two different props?


-ms-box-sizing?


Tagging @Narann


What's the difference between todo_list_items_path and todo_list_path(@todo_list)?


Omg Dan, I can't believe you did the same mistake twice with the typo'ed name


Remove line   "Find me in app/views/pages/course.html.erb". It's a bad practice to show guts of application in production


I see only a single constructor?


The unit tests in this branch test autobridging functionality. This code forces use of the old 0.27.x semantics which don't include autobridging until March 30th at 13:00 PDT.

Without this test, unit tests would fail until that time. By having the server enforce 0.28.x semantics when in stanalone mode we work around this issue and allow testing to be performed against the new code, instead of the 0.27.x version.


We'd be glad to if we could, but there are no C++11 compilers for some of the platforms we're targeting. PS3 and BlackBerry, for example.


How about adding a "title" attribute to display the full username without having to go to the profile page?


could you add something more complex here? `a(b|(c)d`


"mimetype"


Sounds like a bad idea to consumer reference a plugin (whose implementation can change - and might be out of date), from the library


I know it doesn't really matter for this particular implementation


@mattss that seems to have been the culprit.


could you do `((a|b)|c|d)` also?


You don't need to specify on create and update - it should work by default.


remove duplicated route


Using case class and multiple parameters to mark unsafaInstanceAccess private for me is misleading. I think
case class EventHandlerMapping(id: String,
                                                      name: String,
                                                      private val unsafeInstanceAccess: DebugEventHandler)
is more readable


Push élémentaire :
-Déplacer solGauche et solDroite dans leurs tests respectifs au cas ou on en ait besoin ds le futur
-Reindentation de SLG dans ma tentative de compréhension
-Preuve que SLG ne fonctionne pas en ne lançant pas solCaseSure avant


I think it would be cleaner to raise a generic CalicoError inside get_container_info, that way we don't have to know about the internals to be sure we're catching all exceptions here.


RIP host


I think Autoprefixer added them at some point. Must have been a bug.

https://github.com/tastejs/todomvc-app-css/commit/81e39e0044b757896411b770982cd79897e159bc


s/method/function/


I'll use std=c++11 only for fba-libretro mips3-enabled then, seems like mips3 will be a dynarec only available for x86/x86_64 (and perhaps arm).


What does this line mean? We have an amazon translator and I still hope that my pull request https://github.com/zotero/translators/pull/857 will be accepted.


Yes, but you'd have to somehow be able to reasonably expect that the error from the server is non-deterministic.
I'm not sure that this is actually true in the majority of cases.
And if it is indeed the case the user can still and easily apply the retry logic on her layer.

So, I'd even argue that we don't need *any* additional support for high-level request retry at all. The implemented transport-level retry should be all that's required.


Build HTML for Student Homepage. #42
48aa9c7a231c2c4850f79c5f7206c9b2089a29ca


@gwensmu I think your specs will be more robust if you add `.iso8601` to the end of timestamp output in the reports and specs. I came across this same issue in the think_feel_do_so_engine report specs.


maybe we could just do a few lists in the beginning so test cases can be extended easily. I imagine something like

```python
fail_list = ["(", ")", "a(", "a)"]  # usw
test_strings = {
"(a|b)": ["a", "b"]  # usw
}
```

Also I'd like to have some testcase for an empty alternative in: `(a|)`


Or you could have added the bm.timelimit permissions to the plugin.yml :-)


You could extract this to `user.remove_token!` method.


Works :+1:


@erikreid just make sure you aren't merging in the future. I didn't have a chance to test it before it got pushed into Esri/s-g-t. Thanks.


@frap129 Haha, sorry, I was getting errors with it and I don't have the time to debug. Will give it a go again soon! Thank you for this btw.


I think we must improve the media query for measures based on standards. Let's say 480px,768px and 992px. We choose px or rem, but it seems to me 1200 px (85, 100 or 120 rem) is too large for a breakpoint.


SO HTML5. MUCH LOCATION.


Don't break routes naming convention.
Use lowercase:

    get "newslist" => 'pages#newslist'


The reason the Metadata document defines `property value` is to remove such ambiguity. The metadata document _should_ say that the property value of a boolean atomic property is `false` unless specifically set to `true`. It does this for `required`, but should make a blanket statement. That helps avoid an awkward phrasing in this document, so you can say "if the property is false".


hahahaha

On Fri, Mar 13, 2015 at 8:31 AM, Charlie Bini <notifications@github.com>
wrote:

> Haha, I was just showing Tyler Dockins how git works (mostly...)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/TEAMSchools/mandi/commit/ff2c58bad330e3bada34d39bb50cec7632f05c2b#commitcomment-10184246>
> .
>


the only change it did was one line in the doc/chapterexpr.tex.
But I did run the build afterwards and that appears to have touched the other files.
What ist best? Shall I roll back, branch off 23 and do my edits on a branch that you can later merge in?


LGTM


ใช้ตาม document angular [ng-cloak](https://docs.angularjs.org/api/ng/directive/ngCloak)


r+


This is incorrect, you're replacing the `AddinReference ` addin-engine based assembly resolution with pkg-config.


FIY this breaks https://github.com/webhippie/po_to_json and https://github.com/webhippie/gettext_i18n_rails_js which is their responsibility to fix, but this should have had a major version bump.


Searching PATH would make more sense than LD_LIBRARY_PATH.


Make sure to do a pull request so that we can review it as well :)


@dbarnett `IsEqual` doesn't accept a message, so it's probably cleaner to write this out longhand, then.


Folow Rails naming convention.
Rename action to news_list


Why is this commented out?


Cool, thanks will do.

On Fri, Mar 13, 2015 at 11:38 AM Eric Carty-Fickes <notifications@github.com>
wrote:

> @gwensmu <https://github.com/gwensmu> I think your specs will be more
> robust if you add .iso8601 to the end of timestamp output in the reports
> and specs. I came across this same issue in the think_feel_do_so_engine
> report specs.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cbitstech/social_networking/commit/b10cfd33d840515b287d1c2c5a1485964a6975c2#commitcomment-10189201>
> .
>


Good catch, fixed in master.


Solución bug


I'd prefer to keep it Debug for now until it's more mature.


Not possible at the plugin.yml level, as the permission nodes are based on the names defined in your config


Esto da un pete que lo flipas


Got it!


Muy bien lo de poner Mancha en mayúscula


Gracias!


Is `IA32_sysenter_esp` always up to date? (Intuitively, it must be. But I'm no x86 expert.)

If it is only has a usable value prior to a `sysenter` instruction, then we won't gain much. I.e. `get_current_process()` would still have to be called within a specific context and not at any point of the execution.


Removing the dot prefix would lead to the invocation of the Rcpp function when this line is executed


*arduíno


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


merging luniv/servo/viewport-length-units-reftests = d80abce1 into auto


luniv/servo/viewport-length-units-reftests = d80abce1 merged ok, testing candidate = 2382d712


Hm, may have triggered a bug in GitHub there – I tried to edit the file directly knowing I didn't have access, since it gives you the option to automatically fork and submit it as a pull request, but that led to a 404 page instead. Might have to fork and edit manually.


Using Option[_] seems hacky. I don't think that boolean is also good choice.

sealed trait JdiEventCommand
object SuspendJVM extends JdiEventCommand
//and we can add some operation later

Handling using classes from above will be much more readable. And if we support more than one eventhandlers we should work with list of JdiEventCommand instead of first one.


As discussed on IRC, this looks like it would open up an issue in which the last gcli actor initialized wins as far as the window the types are seeing (since the type objects are shared across actors)


This would perhaps be the second best. I was going to update the lang spec, and chances are high that any other changes will conflict. So I'd prefer you wait a bit and announce the changes you want in the issues like last week.

Changes on the mastet README will be okay, though.


This was a revert of a previous change where I removed it.  The remainder of the current diff between this branch and OData/OData.net has no changes in this file, so I didn't think I should change just this one file just to remove a using :-).


Ok, will revert it back then ...


How are you compiling the chunks?


I would suggest something like:

    var mdpath =
        //get the bin paths
        Environment.GetEnvironmentVariable ("PATH")
        .Split (new[] { Path.PathSeparator }, StringSplitOptions.RemoveEmptyEntries)
        //if monodevelop exists
        .Where (p => File.Exists (Path.Combine (p, "monodevelop")))
        //get its exe directory
        .Select (p => Path.Combine (p, "..", "lib", "monodevelop", "bin"))
        //check that the exe exists
        .FirstOrDefault (p => File.Exists (Path.Combine (p, "MonoDevelop.exe")));


```
scala> case class X(i: Int, private val j: Int)
defined class X

scala> X(5, 3) == X(5, 4)
res0: Boolean = false

scala> case class X(i: Int)(j: Int)
defined class X

scala> X(5)(3) == X(5)(4)
res1: Boolean = true
```
I don't want to leak the unsafeInstanceAccess somehow in compiler generated methods.


Ok, I'll have a look at the data behind the service and see what's up with that.


LGTM. Thanks.


Add impossible exception here


ok


r+


Não entendi como modificar o tipo professor. Fiz a conversão porque foi o único jeito que funcionou pra mim. O mesmo trackId já estava como NSstring


no


Shouldn't matter for testing purposes, but I'm curious... why Encoding.Unicode?


I did solve the inaccessibility problem, but when I compiled the code, I get the error of the following:

error C2797: list initialization inside member initializer list or non-static data member initializer is not implemented

\These errors seem to affect Movement::args and Movement::name


Ok, will do :)


It is possible!!!!!


Feel free to write cleaner solution.

The problem here is that after standing up, the switch time between MG and deployed MG is about 1700. This patch will limit it to 250 ( normal switch time ) in the situation where a player tries to change weapon right after undeploying MG, so there won't be a little pause while changing weapon.


I wasn't sure about what we can get as answer from the event handler. If the answer is not arbitrary, the trait is indeed a better choice.


Is it good for CS-Studio to be building against this nightly repository? I now see quite a few dependencies (e.g. `org.eclipse.osgi`) being downloaded from the efx repo, whereas before they were downloaded from the Eclipse release or updates repos. Then again the versions might be the same...


Try _.getName() -> _


Im not sure about sustain here.


The problem is caused by a filename with non-ASCII Chinese characters , not
with what I had though a msword file. Then I rename the file with english
word, and use download = "文件.doc" in the attribute of the a href code, the
problem is solved. Don't know if there are cleaner way to do this. Thank
you for your work, and I must say your project is so considerate because
there are so many functions that I  haven't before expected.

BTW, I am in such a hurry that the cause is open to student, and I must
close Debug parameter and do the debugging work locally. Glad to hear your
further suggestions.

2015-03-13 19:52 GMT+08:00 Andreas Klöckner <notifications@github.com>:

> By the way, while you're still debugging, I would recommend that you keep
> "DEBUG" set to True.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/inducer/relate/commit/4144fd10e666f8bd855bfe5183bb5216c9dd9983#commitcomment-10183687>
> .
>


Try using a for yield instead


Why does the test need two commands at the start of the array that are just `{ item: 'converter' }`?


Handling list of events also seems reasonable. Though, I don't know of scenarios where multiple event handlers would conflict with each other. Probably that is not likely.


this commit introduced bower & grunt.  just using it to build a minified deployment, and I'm really trying to keep it as unobtrusive as possible.  so far, it doesn't really change the structure of the source files


It could be done, significant modifications to the logic are required. as currently we expect 1 file per language, and the file name is expected to be that languages name (and we increase lang_id per file parsed)


I'm assuming you meant to get rid of the from: 'json' / to: 'dom' converter here?


I actually did this already closes #2


You can safely remove the `message = ` and `content = ` bits up here. They are dead code.


did you try to uncomment the lines? ;-)


To be honest I needed to specify one, and used Encoding.Unicode because I
thought it was the default one for StreamWriter. But now when I think about
it the default one is actually Encoding.Default... :-)

Do you have any suggestions for what encoding to use? Shouldn't matter like
you say, but if you have a specific preference I will happily change it.
On Mar 13, 2015 5:50 PM, "Stephen Toub" <notifications@github.com> wrote:

> Shouldn't matter for testing purposes, but I'm curious... why
> Encoding.Unicode?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/patriksvensson/corefx/commit/4cc41a9eadeaa591c7143f55607bffa64e1a5f7a#commitcomment-10189493>
> .
>


its in `src/core/dom` and still in master https://github.com/timdown/rangy/blob/master/src/core/dom.js#L323


ちょっとまって、これsingle.css消してないですか！？


ここの箇所消しちゃだめだと思います！


ah i see, for rangy-textrange it might be lost :/


Naturally these never change if they are not initialized by the constructor


Right here the ticker value is forgotten


I don't know. It'd be very old (these are in chronological order) and has been in there for ages, probably to fix an old bug. Note it misses the last bit of the ID from our current translator, so wouldn't affect that.


These publish events appeared while trying to merge. I changed all these over to updating the data on window locally (as here), but there is no conflict when merging back. Thanks.


@shroffk I thought I remeber Kunal had a reason for the nightly url, Kunal?


some of the changes from 1.0.0 to 1.1.0 caused a regression in my code, probably this one, will investigate it further to find the issue and report in the proper project


字体测试


This commit breaks non Windows build + when building TDM GCC 4.9.2 64 bit


Oh, I see - more is added in https://github.com/joewalker/gcli/commit/989537615525b0d5ac980b1681e12177d8506fc4


1348-IDFMeasureWorkspace (kbenne) - x86_64-MacOS-10.9-clang: Tests Failed

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


I think here is better to use Ptpar with Pfindur.


r+


Remapping `Q`, that I can understand. But `q`! So much power gone to waste :cry:

Please reconsider. Maybe this will help sway you: I recommend reading this: http://usevim.com/2012/08/10/macros/

My opinions aside, thanks for sharing your dotfiles!


LGTM


Email me, I will try to explain tomorrow :)


@fczuardi probably this https://github.com/facebook/jstransform/issues/78


I'll push my code later this evening so that you're not suck waiting for me sorry :frowning:


Rename to addrOf


I *think* this will cause it to hang, since I can't find a goroutine that drains the `PipeReader`. I'm probably missing something?


i can't see it, but i'll take your word for it


I am not sure why. `gnu++11` is not required for building wxWidgets (wxWidgets itself does not require the `c++11` flag, only CodeLite does)


Hmm. That's not what it looks like in my working tree. https://github.com/joewalker/gcli/blob/pr77-tip/lib/gcli/test/mockCommands.js
Something funny must have happened with a rebase. The contents are added back in again here: https://github.com/joewalker/gcli/commit/989537615525b0d5ac980b1681e12177d8506fc4


No, because am unary function cannot have 3 arguments, and, in addition, constructors must not be used partially applied.

But just because you got it wrong doesn't mean that it doesn't work at all.

Try some parentheses, please!


What do you mean "compiling"?

> On 13 mar 2015, at 17:47, Ryan James <notifications@github.com> wrote:
>
> How are you compiling the chunks?
>
> —
> Reply to this email directly or view it on GitHub.
>


По заданиям - ок. Но нужно реализовывать каждое задание в своем файле, а название папки с заданием должно начинаться с 14, например, 14task


Yes, because opening delimiters are only beeing looked for in the left side oft the closing delimiter as I told you before. If there is no closing delimiter, closing_pos is -1 and therefore opening delimiters are only being looked for in pattern[:-1] which means the last character is excluded. That's why I need to check it here separately.

BTW. What's wrong with the indentation? Doulded hanging indent because the following lines are indented once?


I need to know how to you are sending the packets for chunks.

On Friday, March 13, 2015, Niclas Olofsson <notifications@github.com> wrote:

> What do you mean "compiling"?
>
>
> > On 13 mar 2015, at 17:47, Ryan James <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> >
> > How are you compiling the chunks?
> >
> > —
> > Reply to this email directly or view it on GitHub.
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/NiclasOlofsson/MiNET/commit/9ca443f8d8b3ebeed0c8aaedfe9525f876ebdea5#commitcomment-10189745>
> .
>


r+.  No idea if you need to null check on process.title


so where should I initialize this? Im a little confused how its getting left behind, how is it related to the constructor? I guess this is the same issue with both score and ticker huh? Do I need to add fields to my game1 constructor to make them elements of game1?


Constructors must not be partially applied IN PATTERNS, that is.


sure


By the way, this plugin still beaks vim-repeat, by overwriting `<Plug>(RepeatUndo)`, doesn't it? The only workaround I could think of was
```
" Save current u map in <SID>(u)
let nu = maparg('u','n',0,1)
if exists('nu.rhs')
  execute (nu.noremap ? 'nnoremap' : 'nmap') . (nu.expr ? '<expr>' : '') . ' <SID>(u) '.nu.rhs
else | nnoremap  <SID>(u) u | endif
unlet nu
```
but this is far from infallible (though mostly works).


i just replied to your comments on github Im not sure if it notified you
but what I said is:

so where should I initialize this[score and ticker]? Im a little confused
how its getting left behind, how is it related to the constructor? I guess
this is the same issue with both score and ticker huh? Do I need to add
fields to my game1 constructor to make them elements of game1?

On Fri, Mar 13, 2015 at 12:57 PM, Jay McCarthy <notifications@github.com>
wrote:

> Right here the ticker value is forgotten
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/payounger/game1/commit/b673785cf9b9322e3f488ea74ffc4baba0353046#commitcomment-10189637>
> .
>


I checked all these before so I know they work (or raise exceptions)

But yes I will add a duct here later on with more examples


Kaum macht man's richtig - schon funktioniert's :-)


When you create a "new Game1()" then all the fields are re-initialized to their default values. If you want them to be something else, they need to be set to that "else" in the constructor.


r+


I'll do that specific correction right on the master branch, ok?


That line was removed in 4fb5a421d365d791874bc904051caf2341d9944a


nice


@domenic +1
@DanielBaulig Do you remember why you imported `define` before `jsdom`? When I tried to update jsdom I got some errors when running the tests but I could fix the error by importing `jsdom` before `define`. There might be some side effects on `jsdom` that affects the `html` module.


I suppose that we could have a future nodejs/iojs that had a process without a title. I'm willing to risk it until that happens. That code came from a stack-overflow answer, so I suspect many people have done the same thing, which means we're more likely to be safe!


Why don't you use the existing `shutdown()` method: https://github.com/doanduyhai/Achilles/blob/master/achilles-core/src/main/java/info/archinnov/achilles/persistence/PersistenceManagerFactory.java#L683 ?


I think Mom is the only other person who has seen my page anyways

She was very impressed :P

On Fri, Mar 13, 2015 at 12:00 PM, Elsa Gonsiorowski <
notifications@github.com> wrote:

> Thinking just in terms of consistency... I do like your addition of ",
> Ph.D." I think this is better than doing Dr. X, which makes me think of a
> research staff/someone that isn't tenured faculty. Honestly, I think you're
> right that a qualifier isn't really necessary for "Advisor." But that does
> make consistency difficult...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/annagons/annagons.github.io/commit/a2b40a37b9059e1967165778ef703ae65999825b#commitcomment-10188373>
> .
>

--
Anna R. Gonsiorowski, M.A.
Graduate Student
Learning and Development Lab
Georgia State University
agonsiorowski1@student.gsu.edu
(404) 413-5076


Yep!  Salt is empty.  Salt and context information are very similar in the HKDF scheme.


Yes. At least I had some entertaining while waiting at the security check
... :)
Am 13.03.2015 18:04 schrieb "Dierk König" <notifications@github.com>:

> I'll do that specific correction right on the master branch, ok?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Frege/frege/commit/4aa288280507cc1951914a90f71fc5f9df4ce8cf#commitcomment-10189816>
> .
>


this commit has caused http://hercules.ws/board/tracker/issue-8544-map-freeblock-timer/ I'll address within minutes


Rejected with extreme predjudice


safe travels, man!

> Am 13.03.2015 um 18:06 schrieb Ingo Wechsung <notifications@github.com>:
>
> Yes. At least I had some entertaining while waiting at the security check
> ... :)
> Am 13.03.2015 18:04 schrieb "Dierk König" <notifications@github.com>:
>
> > I'll do that specific correction right on the master branch, ok?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/Frege/frege/commit/4aa288280507cc1951914a90f71fc5f9df4ce8cf#commitcomment-10189816>
> > .
> >
> —
> Reply to this email directly or view it on GitHub.
>


Meh.  I don't expect `struct` to be deep.


I'd be willing to copy on creation.  I'll start doing that.


Nice, was going to suggest this :)


Addressed in 2b71c036298756d294d10141ce6196a48d783930


Put p_ inside back-ticks
```
`p_`
```

:bowtie: Thanks :bow:


前端的笔试题，比较全面了。


@vangheem in my experience install.py is not working anymore on Plone 5 (not from Plone, but it is from ZMI)


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1003
success: http://build.servo.org/builders/linux2/builds/1002
success: http://build.servo.org/builders/android/builds/1037
success: http://build.servo.org/builders/mac1/builds/1218
success: http://build.servo.org/builders/mac2/builds/1219
success: http://build.servo.org/builders/gonk/builds/189


On Debian 7, I am getting `Error: {undef, [{rabbit_auth_backend_internal,check_user_login,` ...

Are we really supposed to be using `rabbit_auth_backend_internal`? The module behaves as expected when calling `rabbit_access_control:check_user_login` instead.


Only (U) ? what about the other regions?


so I need to add a score and tick parameter to my game1 constructor?


@fabiomcosta I don't think there was a specific reason for the order other than maybe lexical ordering.


Maybe this can go elsewhere ? It's a problem when you compile all your style files in one using less. (?)


asd


Ради двух строчек, повторяющихся только два раза, создавать отдельный класс? Серьёзно?
Тем более после переворота, последующего за изменениями предыдущего комментария, всё будет иначе...


fast-forwarding master to auto = 2382d712


Можно поплакать?


Plz update to "The fingers you have used to dial are too fat. To obtain a special dialing wand, please mash the keypad with your palm now."


Let's see if I can resurrect this. I think I aborted due to merge conflicts, and the lack of useful context for errors :)


There is none with compass, because the library only has css stylesheets and compass doesn't know what to do with that.


@jabley yeah. About 10 lines below this (line 288) the Response.Body gets set to the `PipeReader`. The user is responsible for draining that and closing it when done, as with regular net/http requests.


Commiteando voy commiteando vengo


Consider the function:
```
void C::foo (T t) { sink = std::move(t); }
```

The reason to pass-by-value and then move is to handle both l-values and r-values nicely (for cases where moving is cheap). The number of copies and moves for l-values and r-values are:

r-value: 2 moves (one into t and one into sink)
l-value: 1 move, 1 copy (copy into t, move into sink)

If we instead declare a pair of functions:
```
void C::foo (T const& t) { sink = t; }
void C::foo (T&& t) { sink = std::move(t); }
```

The costs are now:
r-value: 1 move
l-value: 1 copy

So we save one move at the cost of maintaining two functions instead on one. Since moves are presumably cheap this is a good tradeoff. If moves are expensive then don't use this idiom.

Of course, if there are multiple sink parameters, then you need 2^n overloads, as @HowardHinnant points out.

Now let's consider your example:
```
void C::foo (T const& t) { t_ = t; }
void C::foo (T t) { T = std::move(t); }
```

You would never write that. Depending on how `T` behaved, you would write:

1) Just the `T const& t` overload if T is as expensive to move as it is to copy.
2) Just `T t` overload if T is cheap to move and we have to deal with both l-vals and r-vals.
3) A `T const& t` and `T&& t` overload if I care about the cost of the extra move.

I agree with both of you that this idiom is not approprite for Buffer, as it is not copyable. However, I still like this idiom for sink parameters with cheap moves.


Done -- in the reworked version, the per-algorithm test code almost entirely disappears. Thanks for the push to make that happen.


No, because when you have an open pull request and you do a commit, the commit will be added to your open pull request! @anpegar thanks a lot!

Gracias! :D


ok, I see that Lelys erased the testing .xlsx file from this morning. I see the backup file for it is still there, it is a file called ~$testing.xlsx, I will erase that one.


Looks fine to me.


Она на меня ругается, если я это убираю -_-


There is no backup file, I must have seen some previous version.


solves #3


Почему?


During my consumer testing of the lazy broker stuff I also realized our consumer logging is pretty useless, adding some there would be nice if you're in the area :)


LGTM


Hrm, this is questionable because you're changing the struct inline.  Even though it's a copy, it feels questionable.


FYI: lepiej unikać przycisków 'save' w formularzach i robić je "ręcznie" w szablonie - dzięki temu jeśli kiedyś trzeba będzie to możemy użyć `TaskType` jako podformularza


We probably need to make a more elaborated check, because technically the user part is case sensitive. I bet MMS has some library for that ;-)


ок


This is really verbose.  Not terrible, just verbose.


Replace the raise 404 with a raise 403 when user hasn't the access according to http status.

(And why not adding a "you don't have the {rule} right" text on the 403 page)


У меня же может и не быть такого файла.


@QWp6t I know, thanks for the example. Also, digging the logging feature :+1:

But as Soil already somewhat supports WordPress SEO by Yoast, and because this function will be a new feature to Soil, shouldn't this plugin go with the official snippet placed in the document header instead of using the example made at h5bp?


A minor comment.

----- Original Message -----
> @smarterclayton PTAL, is this what you were thinking?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openshift/origin/commit/6e0c6b9973e5c65f631880796f27723659e4d403#commitcomment-10188036


Thanks for the suggestion. Done!


> Replace the raise 404 with a raise 403 when user hasn't the access according to http status.
>
> (And why not adding a "you don't have the {rule} right" text on the 403 page)

I am working on this now :)


depends what you want to do with it.
if find_chain is what i called find_length (find the length of the parent
chain), then what you re interested in is an integer, (when writing the
.mol file lines you'll have to iterate  this number of time)
you can define the hash keys as string and not symbol  (a symbol start with
a colon)  so something like {"meth" => 1, "eth"= >2....}

NB : - in your find_chain function the parent_chain (as well as value main
chain ..) will be an undefined variable
PS: I think comp_name =~ /#{k}/ may be faster than comp_name.include? k

On 13 March 2015 at 16:29, mohitgautam05 <notifications@github.com> wrote:

> parent_chain =
> {
> :methane => "meth",
> :ethane => "eth",
> :propane => "prop",
> :butane => "but",
> :pentane => "pent",
> :hexane => "hex",
> :heptane => "hept",
> :octane=> "oct",
> :nonane=> "non",
> :decane=> "dec",
> :undecane=> "undec",
> :dodecane=> "dodec",
>
> }
>
> def find_chain
> if parent_chain.values.find {|k| k.include? comp_name}
> main_chain= parent_chain[value]
> end
>
> This is the approach i'm following that to find the particular sub string
> using the hash and then later on we can concatenate them together ? Is it
> the right approach ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/nicolejung/IUPAC/commit/725e68e572ed75c66ce857fdea80ce6bf6121874#commitcomment-10187674>
> .
>


What happens if sp_session_player_load fails? Before, we removed the track. Now we will try to load it again and again if I'm right. Not sure if this can happen e.g. if the track is really invalid and this will repeatedly failed.
Maybe having a non const& |pb::spotify::PlaybackRequest| parameter (so this will perform a copy) would be enough (supposing those objects are copyable)? So we don't end up with a dangling reference.

I don't have tested, so maybe it's fine like this :)


Just reverse the logic so it is if
if config.EnableSelinuxSupport {
if selinuxEnabled() {
+ // As Docker on btrfs and SELinux are incompatible at present, error on both being enabled
+ if driver.String() == "btrfs" {
+ return nil, fmt.Errorf("SELinux is not supported with the BTRFS graph driver")
+ }
+ log.Debugf("SELinux enabled successfully")
+ } else {
+ log.Warnf("SELinux is not enabled on the host system. Docker is not able to enable SELinux")
+ } else {
selinuxSetDisabled()
}


Qualquer resposta inválida, definida no parâmetro `pattern_nocache` em `config.xml`, estava sendo descartada. Mas a validação nesta classe serve apenas para descartar conteúdo impróprio para a cache, e não para o cliente.

Exemplo: O XML a seguir exibe um erro temporário para a região consultada.

	<cServico>
		<Codigo>41068</Codigo>
		<Valor>77,81</Valor>
		<PrazoEntrega>13</PrazoEntrega>
		<ValorSemAdicionais>76,51</ValorSemAdicionais>
		<ValorMaoPropria>0,00</ValorMaoPropria>
		<ValorAvisoRecebimento>0,00</ValorAvisoRecebimento>
		<ValorValorDeclarado>1,30</ValorValorDeclarado>
		<EntregaDomiciliar>S</EntregaDomiciliar>
		<EntregaSabado>N</EntregaSabado>
		<Erro>010</Erro>
		<MsgErro>
			<![CDATA[
				O CEP de destino está sujeito a condições especiais de entrega pela ECT e será realizada com o acréscimo de até 7 (sete) dias ao prazo regular.
			]]>
		</MsgErro>
	</cServico>

Não é recomendado gerar cache de situações temporárias, causadas por chuvas, eventos, etc.


Hay que hacer SF aquí


I burned up my Printrboard by mistake, so my 1403 is now running on a RAMPS.  I really miss the M212, and I think it would be useful to other Marlin users as well.  Would you consider making a pull request to MarlinFirmware/Marlin to add this M code?


Shouldn't this be docker.real.sock


ok, I reverted this specific commit (the typo is fixed, though). It will appear in the history as an additional commit that puts the files back in, again. That is usually a better idea than trying to rewrite the history...
When merging work23 in, this could still produce a conflict. I'd suggest trying to rebase work23 against master first.
Sorry for the hassle.


Andreas,
I get a "Not Autorised" error. Even after registering a new number WART, I still get same error could you helpme please


@megawac The idea of #1862 was to implement a cache interface to allow devs to swap it out with Map/WeakMap in envrios that support it (this way it punts on Underscore from having to support it but lets devs easily enhance).


Property order


You're right to spot this ... but it is _not_ the behaviour we want.

The algorithm states

> If the valueUrl for the current cell is not null, then valueUrl identifies a node Vurl that is related the current subject using the predicate P

My intent was that _because_ "Sir Alan" has a `null` value for `reportsTo` then this triple would not get included. Of course, now that you point it out. the URI Template with a null value _does_ get evaluated as you've shown above.

I will add another clause into the algorithm ...


here is my change


git status


what about increasing version number and add a note to changelog?


"medium" does not compute with "color"


@corvannoorloos agree, document header is best


> because there's inevitably an unintuitive reason a value might be a specific value, or temporarily toggled to another value, etc.

Reasonable enough.  I'm not against having comments in the config, nor do I have a strong opinion on the matter.   We can switch back to toml.


please send the comment. Negusu


git add


:heart:


Travis will yell at you no matter what


Types missing


Fixed via 8f4c342. Thanks for the heads up.


This change seems to have fixed the test discovery issue for conditional fact/theory.


On Fri, Mar 13, 2015 at 11:17 AM, Vern <notifications@github.com> wrote:

> First thing next week when I'm done with my driver.
>
Excellent, thanks.


Why silence errors?


@michaelficarra
> @megawac See https://people.mozilla.org/~jorendorff/es6-draft.html#sec-properties-of-the-symbol-constructor. Each of the well-known symbols there changes how the object behaves in some way. It is not safe in a future with additional well-known symbols to modify these fields arbitrarily.

It should be fine as the temp object isn't used in a way that would be affected by the well-known symbols.


@therabidsquirel you are right about claimants viewing submitted claims, I don't know why I thought they werent supposed to appear in the list. I will fix that.

@kuzi117 Yea, I will make that change too.


In fact - I will raise an issue against this so we can track it


That's tested in TestQueueRetryManager_retries

----- Original Message -----
> Deleting this test reduces coverage: without it, there's no test for
> `RetryFunc` returning `false` resulting in a call to `ForgetFunc`.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/smarterclayton/origin/commit/55c175fd35911c5353034ccd8d7ffda51dd96c2c#commitcomment-10184857


Alrighty. Normally we could just revert the commit, but there's some small + unrelated changes in the same commit.

Do you want to just add another commit swapping back to toml?


I'm not huge fan of installing stuff to `/usr/local` - it causes lots of confusion down the line when you forget you have an old build, etc.


Ok I miss this. I am convinced :)


Can you change is to
PythonFunction<ISMRMRD::ImageHeader> modify_img_header


sure.


Can you add note about source of file?


Are there any alternatives to Taskmaster that you are aware of, that have a similar use-case. Message queues seem to be meant for realtime async processing rather than a large queue of work that needs to be done.


:+1: pushed!


Wait. Wasn't there something about spaces in something that didn't work with toml?


Proposal: Change the namespace from `GoogleAnalytics`, less specific and open to more code snippets in the future. Could possibly reduce the function name down to `google()` as well.


@yeban thanks - unfortunately this breaks search engines and links people may have in their signatures. Can you please put a redirect as well? Details here: https://help.github.com/articles/redirects-on-github-pages
Thanks
y


This'll cause a slight breaking change when `isSorted` and the first value is `null`.

```javascript
_.uniq([null, 1, 2], true); // => [1, 2]
```


Now that I think about it... there should never be a cutoff at the root.  Otherwise it will not search the remaining moves.


so first question is: why you want a standalone output?
it's not working with bundles by default because it's standalone ;) so no require is available.

if you really need the standalone with bundles, you need to provide require through your global app.
for instance in your core:
```
var core = whatEver;

core.require = require;
module.exports = core;
```

and then every bunde which use the core, needs to write (if the core component is exposed as `core`)
 `core.require('foobar')` instead of `require('foobar')`

but this looks ugly


Weird. Let me know what it was if you can find it. Strings are quoted, so unless you were trying to have a *key name* with spaces (which I wouldn’t understand why), I can't imagine what it would be.


I have added kill back button and advanced reboot menu. working and compiling :+1:


Let's use hex color for making sense everywhere and not only on a browser


Could you replace this with the long php opening tag?


we don't need the actual guid value here?


Both Sage and Soil will be using short opening tags moving forward, as part of the PHP 5.4 minimum.


This is still wrong. Discussed personally


Thanks for the patch!

I'll be moving soon all the vertex shader code to the pixel shader since it doesn't make sense in modern GPUs to offload such simple stuff to vertex shader (as there is no hardware interpolation anymore). That will get rid of this problem altogether :)


This is _virtual_ function and args used in Creature::IsImmuneToSpell overwrite for creatures and totems


The main component *must* be attached here as well.


Especialy that currenly I we need only one Command - StopJVM. So for now we can just change Option[_] to Option[SuspendJVM] and left handleEvent logic.


Horde_Mail_Rfc822_Address@matchInsensitive().

Although it would require a bit of refactoring to work in this case since the matching emails are being stored as strings in a hashed array - although I will point out that this only works if the email in the key has previously been stored lowercase (which it shouldn't).


@kevlarkevin ?


@kalenjohnson didn't realize that. Thanks!


I can do a var


Yeah, it's not my favorite, but it works for now...


Curious: What was the behaviour before this commit? Did it NOT return?


StreamWriter by default uses UTF8.


This is still wrong


Local XML also modified, at

    /home/icub/.local/share/yarp/applications/poeticon++_perception_mode.xml


Hmm, I think you're right.


Quoting Jan Schneider <notifications@github.com>:

> We probably need to make a more elaborated check, because
> technically the user part is case sensitive. I bet MMS has some
> library for that ;-)

I agree and brought that up in the related Bug: 12505.

Kronolith is already always lower-casing the attendees when they are
read from storage so if/when we decide to enforce case-sensitive user
parts we need to stop doing that as well.

--
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject


Other docs added.

----- Original Message -----
> Hmm, I think you're right.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/smarterclayton/origin/commit/55c175fd35911c5353034ccd8d7ffda51dd96c2c#commitcomment-10190559


HumidifierSizing_#4688 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1149 of 1149 tests passed)

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


For the JRuby bits, unless I've really needed to copy them, I've been pushing them out to StringSupport so the code can be shared.  I haven't looked in this case, but just a general FYI.


@MaruthiPrasadA is your API test key  / secret valid? I will test here if it is valid.


Commented code :)


Added a responsive navbar that drops down when resized.


Yeah, I got that but this implementation doesn't currently work towards that goal as values are being stored in an array correct - will it not cause memory leaks by default for memoize?


Почему этот цикл находится внутри первого цикла? Сначала надо заполнить очередь, а потом запускать потоки. То есть этот цикл должен идти после первого цикла, а не внутри.


Ah, ok :-)

So do you want me to change it to UTF-8?
On Mar 13, 2015 6:47 PM, "Stephen Toub" <notifications@github.com> wrote:

> StreamWriter by default uses UTF8.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/patriksvensson/corefx/commit/4cc41a9eadeaa591c7143f55607bffa64e1a5f7a#commitcomment-10190547>
> .
>


Why would you change this?


This test errs on the corrupt deployment with Exit code: 128, suggest to expand the array. Why rely on stderr, why not improve the error_message_regex to be meaningful?


Thx, I keep forgetting this. Amended the commit.


extension points are public API, they need to be more future proof. Therefore using a trait as return value was the right idea.


Looks fine apart from commented code. :) I'll test asap