Same here. Additionally `drag` will not be minified, so you increase the size.


sdf >asdfasdf
asdfasdf
<


sdf
> asdfasdf
asdfasdf
<


@jundl77 In the PropertiesAssistant some methods are not used....are they obsolete?


sdf

> asdf
aasdfsadf

asdfsadf


Good point, I'll do this, here we're come to V5.


And for now I don't see how I can reimplement this condition in SDL_KEYDOWN\SDL_KEYUP handlers. And placing this condition in SDL's WM_KEYDOWN\WM_KEYUP handlers is also not a best idea. So I'm asking your help how if we can refactor this somehow


I meant the lines after "proc.kill()", which are repeated, sometimes verbatim, sometimes with just a couple changes, at least 4 times.


いい問題だね


Why 0776 here? I know that was the old value but I don't understand why it was that either.


*Edited above comment*

This points out something - I just noticed I've blindly copied the same logic in the defaultSerializer. This assert isn't required there.


OK, I'll do this for V5.


nested resource는 member 없어도 됨 http://guides.rubyonrails.org/routing.html#nested-resources


@mickadoo - sendQuote will return an object, so you should better check the objects status. be aware that the response object`s code is always 200, you need to check the payload to see any error


Se la risposta é null il dizionario é null, OK!
Ma se la risposta non é null e il risultato non contiene poll é meglio ritornare il dizionario vuoto, quindi semplicemente allocato e inizializzato


Please follow this code. It reflects the essence of the problem.

```
	public class Test extends ScrollContainer
	{
		public function Test() {
			super();

			addRawChild(new Sprite());
			addRawChild(new Sprite());
			addChild(new Sprite());
		}
	}
```


Hemos conversado de esto aquí internamente. La lógica es que si no bloquea otra cosa, lo podemos dejar ya que quizás nos salve la vida con un usuarios pesado en alguna oportunidad. En adelante, no se tiene que cuidar IE6-8, pero para los códigos que *ya están*, es mejor guardarlos para aumentar la compatibilidad de Chamilo con estos.


위의 두 줄은 이제 필요없음 (동작 안 함)


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


We should be smarter about this.
 - Practically, b43-fwcutter and drivers get close to 1 meg and we have to pull it from the internet. This adds up quick.
 - Philosophically, there's no reason to throw non-free firmware on a system unless it needs it.

Should take a look on Sat.


1: M110 missing component name


26:1: I101 Imported names are in the wrong order. Should be CFG_WEBSEARCH_EXTERNAL_COLLECTION_SEARCH_MAXRESULTS, CFG_WEBSEARCH_EXTERNAL_COLLECTION_SEARCH_TIMEOUT
26:1: E402 module level import not at top of file
27:6: E126 continuation line over-indented for hanging indent
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
72:122: E502 the backslash is redundant between brackets
73:125: E502 the backslash is redundant between brackets
74:125: E502 the backslash is redundant between brackets
133:93: E231 missing whitespace after ':'


31:1: I100 Imports statements are in the wrong order. import datetime should be before import itertools
32:1: I201 Missing newline before sections or imports.
34:1: I100 Imports statements are in the wrong order. from invenio.base.utils should be before import six


1: D100 Docstring missing
4: L102 copyright year is outdated, expected 2015 but got 2013
20:1: I101 Imported names are in the wrong order. Should be OperationalError, run_sql
21:1: I201 Missing newline before sections or imports.
22:1: I100 Imports statements are in the wrong order. import logging should be before from six.moves
22:1: I201 Missing newline before sections or imports.
28:1: E302 expected 2 blank lines, found 1
28: D103 Docstring missing
31:1: E302 expected 2 blank lines, found 1
31: D290 White spaces around docstring should be trimmed.
31: D400 First line should end with '.', not 'e'
45:1: E302 expected 2 blank lines, found 1
45: D290 White spaces around docstring should be trimmed.
52:1: E302 expected 2 blank lines, found 1
52: D290 White spaces around docstring should be trimmed.
57:8: E713 test for membership should be 'not in'
60:1: E302 expected 2 blank lines, found 1
60: D290 White spaces around docstring should be trimmed.
70: D401 First line should be imperative: 'Thi', not 'This'
70: D400 First line should end with '.', not 'n'
83:5: E303 too many blank lines (2)
106:1: E302 expected 2 blank lines, found 1
106: D401 First line should be imperative: 'Thi', not 'This'
106: D400 First line should end with '.', not 'n'
112: D401 First line should be imperative: 'Thi', not 'This'
123:32: F841 local variable 'e' is assigned to but never used
129: D401 First line should be imperative: 'Return', not 'Returns'
129: D209 Put multi-line docstring closing quotes on separate line
129: D400 First line should end with '.', not 't'
129: D205 Blank line missing between one-line summary and description
203:109: E202 whitespace before ')'
208:13: E303 too many blank lines (2)


big thanks:) by any chance you guys were able to fix double tap wake? I cant find a proper fix which has been a pain :( lol


This 666 need a comment


As a auxiliary fact: LINQ implementation raises a NullRefException in such
cases.... I think we can throw it or not. I mean, currently it will mostly
save time of calling where() when there are nulls in there. Or in case
nulls where not to be there might hide a bug. Which will probably be fixed
by calling where() anyway. I think its fine. Whichever option can mask bugs
and/or cause nuisances.

I will always be in the team of what is more useful. And I think not
throwing an exception is more useful, but,  on the other hand I might be
adding a null check when its not needed at all, so performance must be a
concern too...As always: trade offs...

Em ter, 24 de mar de 2015 às 10:09, sergiotaborda <notifications@github.com>
escreveu:

> The stream cannot alter the elements on its own. The programmer most have
> control, he will call where () if he whants them filtered. Nulls mean
> something. You can introduce a compacted stream that garanties not to have
> Nulls, and do stream.compact () to access it.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zbra-solutions/android-linq/commit/f89360972c5a1fb9233966bd47d5094d2fc99e99#commitcomment-10366422>
> .
>


`counter_cache`도 제대로 동작하지 않게 되는데, 일단 얘도 빼자


`0` could be returned if no child has changed its state. We would not need to search through the job table.


1: D400 First line should end with '.', not 'r'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
30:1: I101 Imported names are in the wrong order. Should be DatabaseError, run_sql
32:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.legacy.dbquery
33:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.bibsched.bibtask
34:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_CHARS_ALPHANUMERIC_SEPARATORS, CFG_BIBINDEX_CHARS_PUNCTUATION
34:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
35:6: E126 continuation line over-indented for hanging indent
56: D200 One-line docstring should not occupy 3 lines
66:9: E128 continuation line under-indented for visual indent
69:1: E302 expected 2 blank lines, found 1
69: D401 First line should be imperative: 'Return', not 'Returns'
69: D209 Put multi-line docstring closing quotes on separate line
69: D205 Blank line missing between one-line summary and description
69: D208 Docstring is over-indented
85: D401 First line should be imperative: 'Return', not 'Returns'
85: D209 Put multi-line docstring closing quotes on separate line
85: D400 First line should end with '.', not 'e'
85: D205 Blank line missing between one-line summary and description
85: D208 Docstring is over-indented
100: D401 First line should be imperative: 'Return', not 'Returns'
100: D400 First line should end with '.', not 'e'
100: D205 Blank line missing between one-line summary and description
100: D208 Docstring is over-indented
108:5: B901 blind except: statement
115: D401 First line should be imperative: 'Get', not 'Gets'
115: D290 White spaces around docstring should be trimmed.
115: D209 Put multi-line docstring closing quotes on separate line
115: D400 First line should end with '.', not 'd'
115: D205 Blank line missing between one-line summary and description
115: D208 Docstring is over-indented
121:5: B901 blind except: statement
128: D401 First line should be imperative: 'Get', not 'Gets'
128: D290 White spaces around docstring should be trimmed.
128: D209 Put multi-line docstring closing quotes on separate line
128: D400 First line should end with '.', not 'd'
128: D205 Blank line missing between one-line summary and description
128: D208 Docstring is over-indented
134:5: B901 blind except: statement
141: D205 Blank line missing between one-line summary and description
171: D400 First line should end with '.', not 's'
171: D205 Blank line missing between one-line summary and description
171: D208 Docstring is over-indented
182:11: E271 multiple spaces after keyword
188:1: I100 Imports statements are in the wrong order. from invenio.modules.indexer.utils should be before from invenio.utils.memoise
188:1: F401 'get_idx_indexer' imported but unused
188:1: E402 module level import not at top of file
191: D401 First line should be imperative: 'Return', not 'Returns'
191: D209 Put multi-line docstring closing quotes on separate line
191: D205 Blank line missing between one-line summary and description
191: D208 Docstring is over-indented
213: D401 First line should be imperative: 'Return', not 'Returns'
213: D290 White spaces around docstring should be trimmed.
222: D401 First line should be imperative: 'Return', not 'Returns'
222: D209 Put multi-line docstring closing quotes on separate line
222: D400 First line should end with '.', not 'h'
222: D205 Blank line missing between one-line summary and description
222: D208 Docstring is over-indented
233: D401 First line should be imperative: 'Check', not 'Checks'
233: D400 First line should end with '.', not 'l'
242:1: E302 expected 2 blank lines, found 1
242: D400 First line should end with '.', not 's'
242: D205 Blank line missing between one-line summary and description
242: D208 Docstring is over-indented
256:1: E302 expected 2 blank lines, found 1
256: D401 First line should be imperative: 'Return', not 'Returns'
256: D205 Blank line missing between one-line summary and description
256: D208 Docstring is over-indented
269: D401 First line should be imperative: 'Return', not 'Returns'
269: D209 Put multi-line docstring closing quotes on separate line
269: D205 Blank line missing between one-line summary and description
269: D208 Docstring is over-indented
282: D401 First line should be imperative: 'Return', not 'Returns'
282: D209 Put multi-line docstring closing quotes on separate line
282: D205 Blank line missing between one-line summary and description
282: D208 Docstring is over-indented
293: D401 First line should be imperative: 'Return', not 'Returns'
293: D400 First line should end with '.', not 's'
293: D205 Blank line missing between one-line summary and description
293: D208 Docstring is over-indented
305: D401 First line should be imperative: 'Return', not 'Returns'
305: D209 Put multi-line docstring closing quotes on separate line
305: D400 First line should end with '.', not 'g'
305: D205 Blank line missing between one-line summary and description
305: D208 Docstring is over-indented
310:26: E261 at least two spaces before inline comment
310:27: E262 inline comment should start with '# '
311:26: E261 at least two spaces before inline comment
311:27: E262 inline comment should start with '# '
326:25: E261 at least two spaces before inline comment
326:26: E262 inline comment should start with '# '
346: D401 First line should be imperative: 'Return', not 'Returns'
346: D209 Put multi-line docstring closing quotes on separate line
346: D400 First line should end with '.', not 'g'
346: D205 Blank line missing between one-line summary and description
346: D208 Docstring is over-indented
384: D401 First line should be imperative: 'Return', not 'Returns'
384: D205 Blank line missing between one-line summary and description
384: D208 Docstring is over-indented
422: D401 First line should be imperative: 'Return', not 'Returns'
422: D400 First line should end with '.', not ':'
422: D205 Blank line missing between one-line summary and description
422: D208 Docstring is over-indented
427:10: E225 missing whitespace around operator
435: D401 First line should be imperative: 'Remove', not 'Removes'
435: D205 Blank line missing between one-line summary and description
435: D208 Docstring is over-indented
448: D208 Docstring is over-indented
448: D200 One-line docstring should not occupy 3 lines
462: D401 First line should be imperative: 'Create', not 'Creates'
462: D400 First line should end with '.', not 'd'
462: D205 Blank line missing between one-line summary and description
462: D208 Docstring is over-indented
472: D101 Docstring missing
476: D401 First line should be imperative: 'Return', not 'Returns'
476: D300 Expected """-quotes, got '-quotes
486: D401 First line should be imperative: 'Return', not 'Returns'
486: D400 First line should end with '.', not 'y'
486: D205 Blank line missing between one-line summary and description
486: D208 Docstring is over-indented
497:47: E202 whitespace before ')'
501: D401 First line should be imperative: 'Check', not 'Checks'
501: D400 First line should end with '.', not 't'
504:25: E272 multiple spaces before keyword
511: D401 First line should be imperative: 'Check', not 'Checks'
511: D209 Put multi-line docstring closing quotes on separate line
511: D400 First line should end with '.', not ';'
511: D205 Blank line missing between one-line summary and description
511: D208 Docstring is over-indented
517: D401 First line should be imperative: 'Return', not 'Returns'
517: D209 Put multi-line docstring closing quotes on separate line
517: D400 First line should end with '.', not ';'
517: D205 Blank line missing between one-line summary and description
517: D208 Docstring is over-indented
526: D401 First line should be imperative: 'Find', not 'Finds'
526: D400 First line should end with '.', not 'n'
526: D205 Blank line missing between one-line summary and description
526: D208 Docstring is over-indented


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


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
24:1: E402 module level import not at top of file
27:1: E402 module level import not at top of file
28:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info, isGuestUser
28:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.url
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_AUTHOR_DELETE_COMMENT_OPTION, CFG_WEBCOMMENT_MAX_ATTACHED_FILES, CFG_WEBCOMMENT_MAX_ATTACHMENT_SIZE, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_USE_RICH_TEXT_EDITOR
31:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.mail
31:1: E402 module level import not at top of file
32:28: E126 continuation line over-indented for hanging indent
47:1: I101 Imported names are in the wrong order. Should be create_html_select, get_html_text_editor
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
50:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.formatter
50:1: E402 module level import not at top of file
51:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_get_user_roles_from_user_info
51:1: I100 Imports statements are in the wrong order. from invenio.modules.access.control should be before from invenio.modules.access.engine
51:1: E402 module level import not at top of file
52:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.access.control
52:1: E402 module level import not at top of file
54:1: E302 expected 2 blank lines, found 1
54: D203 Expected 1 blank line *before* class docstring, found 0
54: D400 First line should end with '.', not 'l'
57: D202 No blank lines allowed *after* method docstring, found 1
57: D400 First line should end with '.', not 'd'
57: D205 Blank line missing between one-line summary and description
92:13: F841 local variable 'last_comment_round_name' is assigned to but never used
98:139: E221 multiple spaces before operator
101:85: E231 missing whitespace after ','
101:87: E221 multiple spaces before operator
140:34: E127 continuation line over-indented for visual indent
152:13: E128 continuation line under-indented for visual indent
154:33: E203 whitespace before ':'
159:36: E225 missing whitespace around operator
160:168: E502 the backslash is redundant between brackets
160:57: E225 missing whitespace around operator
161:67: E127 continuation line over-indented for visual indent
164:13: E124 closing bracket does not match visual indentation
178:14: E127 continuation line over-indented for visual indent
180:14: E124 closing bracket does not match visual indentation
184: D401 First line should be imperative: 'Display', not 'Displays'
184: D205 Blank line missing between one-line summary and description
209: D400 First line should end with '.', not 'd'
209: D205 Blank line missing between one-line summary and description
244:26: E201 whitespace after '{'
244:45: E203 whitespace before ':'
244:22: E222 multiple spaces after operator
245:46: E203 whitespace before ':'
246:44: E203 whitespace before ':'
247:44: E203 whitespace before ':'
248:44: E203 whitespace before ':'
248:62: E261 at least two spaces before inline comment
248:63: E262 inline comment should start with '# '
249:44: E203 whitespace before ':'
249:62: E261 at least two spaces before inline comment
249:63: E262 inline comment should start with '# '
250:25: E124 closing bracket does not match visual indentation
260:13: F841 local variable 'last_comment_round_name' is assigned to but never used
294:106: E231 missing whitespace after ':'
294:143: E231 missing whitespace after ':'
295:32: E222 multiple spaces after operator
316:37: E225 missing whitespace around operator
336:13: E122 continuation line missing indentation or outdented
336:14: E201 whitespace after '{'
336:40: E203 whitespace before ':'
337:40: E203 whitespace before ':'
338:40: E203 whitespace before ':'
339:40: E203 whitespace before ':'
340:40: E203 whitespace before ':'
341:40: E203 whitespace before ':'
342:40: E203 whitespace before ':'
343:40: E203 whitespace before ':'
344:41: E203 whitespace before ':'
345:60: E225 missing whitespace around operator
346:40: E203 whitespace before ':'
347:13: E124 closing bracket does not match visual indentation
359:28: E128 continuation line under-indented for visual indent
360:28: E128 continuation line under-indented for visual indent
363: D400 First line should end with '.', not 'n'
363: D205 Blank line missing between one-line summary and description
402:35: E128 continuation line under-indented for visual indent
403:35: E126 continuation line over-indented for hanging indent
408:81: E225 missing whitespace around operator
408:100: E225 missing whitespace around operator
410:83: E225 missing whitespace around operator
433:105: E225 missing whitespace around operator
435:106: E225 missing whitespace around operator
441:110: E225 missing whitespace around operator
452:111: E271 multiple spaces after keyword
461:37: E126 continuation line over-indented for hanging indent
488:17: E127 continuation line over-indented for visual indent
488:33: E203 whitespace before ':'
489:33: E203 whitespace before ':'
490:33: E203 whitespace before ':'
500: D400 First line should end with '.', not 'n'
500: D205 Blank line missing between one-line summary and description
533:107: E231 missing whitespace after ':'
534:9: E266 too many leading '#' for block comment
568:94: E225 missing whitespace around operator
574:99: E225 missing whitespace around operator
589:31: E203 whitespace before ':'
590:16: E128 continuation line under-indented for visual indent
591:16: E128 continuation line under-indented for visual indent
591:31: E203 whitespace before ':'
592:16: E128 continuation line under-indented for visual indent
592:31: E203 whitespace before ':'
593:16: E128 continuation line under-indented for visual indent
594:16: E128 continuation line under-indented for visual indent
594:31: E203 whitespace before ':'
595:16: E128 continuation line under-indented for visual indent
595:31: E203 whitespace before ':'
596:16: E128 continuation line under-indented for visual indent
596:31: E203 whitespace before ':'
597:16: E124 closing bracket does not match visual indentation
600: D400 First line should end with '.', not 's'
600: D205 Blank line missing between one-line summary and description
609:55: E231 missing whitespace after ','
692:13: F841 local variable 'c_round_name' is assigned to but never used
693:13: F841 local variable 'c_restriction' is assigned to but never used
702:26: E201 whitespace after '{'
702:45: E203 whitespace before ':'
702:22: E222 multiple spaces after operator
703:46: E203 whitespace before ':'
704:44: E203 whitespace before ':'
705:44: E203 whitespace before ':'
706:44: E203 whitespace before ':'
707:44: E203 whitespace before ':'
708:44: E203 whitespace before ':'
709:44: E203 whitespace before ':'
710:44: E203 whitespace before ':'
711:44: E203 whitespace before ':'
712:25: E124 closing bracket does not match visual indentation
719:22: E201 whitespace after '{'
719:37: E203 whitespace before ':'
719:19: E222 multiple spaces after operator
720:42: E203 whitespace before ':'
721:36: E203 whitespace before ':'
722:36: E203 whitespace before ':'
724:36: E203 whitespace before ':'
725:36: E203 whitespace before ':'
726:36: E203 whitespace before ':'
727:36: E203 whitespace before ':'
731:9: E266 too many leading '#' for block comment
736:13: F841 local variable 'last_comment_round_name' is assigned to but never used
747:20: E127 continuation line over-indented for visual indent
754:35: E127 continuation line over-indented for visual indent
754:73: E221 multiple spaces before operator
763:132: E202 whitespace before ')'
764:33: E127 continuation line over-indented for visual indent
764:71: E221 multiple spaces before operator
765:140: E225 missing whitespace around operator
838:76: E261 at least two spaces before inline comment
846:275: E231 missing whitespace after ':'
847:163: E231 missing whitespace after ':'
880:38: E203 whitespace before ':'
880:62: E231 missing whitespace after ':'
882:38: E203 whitespace before ':'
882:61: E231 missing whitespace after ':'
883:38: E203 whitespace before ':'
883:63: E231 missing whitespace after ':'
885:35: E203 whitespace before ':'
892:9: E266 too many leading '#' for block comment
917:9: E266 too many leading '#' for block comment
1085:9: E122 continuation line missing indentation or outdented
1086:47: E203 whitespace before ','
1088:43: E225 missing whitespace around operator
1104: D401 First line should be imperative: 'print', not 'prints'
1104: D400 First line should end with '.', not 'm'
1112: D202 No blank lines allowed *after* method docstring, found 1
1112: D400 First line should end with '.', not 'n'
1112: D205 Blank line missing between one-line summary and description
1124:15: E221 multiple spaces before operator
1157: D400 First line should end with '.', not 'n'
1157: D205 Blank line missing between one-line summary and description
1175:15: E221 multiple spaces before operator
1177:9: E122 continuation line missing indentation or outdented
1178:9: E128 continuation line under-indented for visual indent
1179:9: E128 continuation line under-indented for visual indent
1196: D400 First line should end with '.', not 's'
1196: D205 Blank line missing between one-line summary and description
1216:22: E201 whitespace after '{'
1216:40: E203 whitespace before ':'
1217:40: E203 whitespace before ':'
1217:65: E202 whitespace before '}'
1222: D400 First line should end with '.', not 'r'
1222: D205 Blank line missing between one-line summary and description
1229:9: F841 local variable '_' is assigned to but never used
1238: D400 First line should end with '.', not 's'
1238: D205 Blank line missing between one-line summary and description
1257:22: E201 whitespace after '{'
1257:37: E203 whitespace before ':'
1257:19: E222 multiple spaces after operator
1258:42: E203 whitespace before ':'
1259:36: E203 whitespace before ':'
1260:36: E203 whitespace before ':'
1261:36: E203 whitespace before ':'
1262:36: E203 whitespace before ':'
1281:20: E222 multiple spaces after operator
1306:13: E122 continuation line missing indentation or outdented
1307:121: E502 the backslash is redundant between brackets
1308:28: E127 continuation line over-indented for visual indent
1309:100: E502 the backslash is redundant between brackets
1310:31: E127 continuation line over-indented for visual indent
1311:238: E271 multiple spaces after keyword
1320:50: E251 unexpected spaces around keyword / parameter equals
1320:52: E251 unexpected spaces around keyword / parameter equals
1355: D400 First line should end with '.', not 's'
1355: D205 Blank line missing between one-line summary and description
1373:22: E201 whitespace after '{'
1373:37: E203 whitespace before ':'
1373:19: E222 multiple spaces after operator
1374:42: E203 whitespace before ':'
1375:36: E203 whitespace before ':'
1376:36: E203 whitespace before ':'
1377:36: E203 whitespace before ':'
1378:36: E203 whitespace before ':'
1388:13: E128 continuation line under-indented for visual indent
1427:1: E128 continuation line under-indented for visual indent
1428:50: E251 unexpected spaces around keyword / parameter equals
1428:52: E251 unexpected spaces around keyword / parameter equals
1469:35: E203 whitespace before ':'
1469:42: E225 missing whitespace around operator
1470:35: E203 whitespace before ':'
1470:41: E225 missing whitespace around operator
1485: D400 First line should end with '.', not 'd'
1485: D205 Blank line missing between one-line summary and description
1492:22: E201 whitespace after '{'
1492:37: E203 whitespace before ':'
1492:19: E222 multiple spaces after operator
1493:42: E203 whitespace before ':'
1494:36: E203 whitespace before ':'
1495:36: E203 whitespace before ':'
1496:36: E203 whitespace before ':'
1497:36: E203 whitespace before ':'
1501:51: E221 multiple spaces before operator
1512:101: E222 multiple spaces after operator
1516: D401 First line should be imperative: 'Create', not 'Creates'
1516: D290 White spaces around docstring should be trimmed.
1516: D205 Blank line missing between one-line summary and description
1539:15: E221 multiple spaces before operator
1579: D400 First line should end with '.', not 'e'
1579: D200 One-line docstring should not occupy 3 lines
1605:19: E225 missing whitespace around operator
1609:36: E203 whitespace before ':'
1612:35: E203 whitespace before ':'
1613:35: E203 whitespace before ':'
1618:39: E225 missing whitespace around operator
1620: D400 First line should end with '.', not 'e'
1635:18: E225 missing whitespace around operator
1666: D400 First line should end with '.', not ')'
1666: D205 Blank line missing between one-line summary and description
1690:27: E127 continuation line over-indented for visual indent
1693:27: E127 continuation line over-indented for visual indent
1716:13: E201 whitespace after '{'
1716:25: E203 whitespace before ':'
1717:25: E203 whitespace before ':'
1718:25: E203 whitespace before ':'
1719:25: E203 whitespace before ':'
1721:26: E203 whitespace before ':'
1722:25: E203 whitespace before ':'
1723:25: E203 whitespace before ':'
1724:25: E203 whitespace before ':'
1754: D401 First line should be imperative: 'output', not 'outputs'
1754: D290 White spaces around docstring should be trimmed.
1754: D400 First line should end with '.', not 'd'
1758: D401 First line should be imperative: 'prepare', not 'prepares'
1758: D290 White spaces around docstring should be trimmed.
1758: D400 First line should end with '.', not 'r'
1773: D401 First line should be imperative: 'output', not 'outputs'
1773: D290 White spaces around docstring should be trimmed.
1773: D400 First line should end with '.', not 'w'
1788:34: E203 whitespace before ':'
1796: D400 First line should end with '.', not 't'
1796: D205 Blank line missing between one-line summary and description
1803:9: F841 local variable '_' is assigned to but never used
1842:17: E128 continuation line under-indented for visual indent
1842:50: E225 missing whitespace around operator
1842:69: E225 missing whitespace around operator
1843:17: E128 continuation line under-indented for visual indent
1843:36: E203 whitespace before ','
1843:23: E231 missing whitespace after ':'
1844:17: E128 continuation line under-indented for visual indent
1844:49: E203 whitespace before ','
1845:17: E128 continuation line under-indented for visual indent
1846:17: E128 continuation line under-indented for visual indent
1852:17: E128 continuation line under-indented for visual indent
1852:50: E225 missing whitespace around operator
1852:69: E225 missing whitespace around operator
1853:17: E128 continuation line under-indented for visual indent
1853:36: E203 whitespace before ','
1853:23: E231 missing whitespace after ':'
1854:17: E128 continuation line under-indented for visual indent
1855:17: E128 continuation line under-indented for visual indent
1860: D400 First line should end with '.', not 't'
1860: D205 Blank line missing between one-line summary and description
1866:9: F841 local variable '_' is assigned to but never used
1900:49: E225 missing whitespace around operator
1900:68: E225 missing whitespace around operator
1901:54: E272 multiple spaces before keyword
1903:49: E225 missing whitespace around operator
1903:68: E225 missing whitespace around operator
1904:54: E272 multiple spaces before keyword
1910:13: E128 continuation line under-indented for visual indent
1910:39: E203 whitespace before ','
1911:13: E128 continuation line under-indented for visual indent
1912:13: E128 continuation line under-indented for visual indent
1913:13: E128 continuation line under-indented for visual indent
1914:13: E128 continuation line under-indented for visual indent
1915:13: E128 continuation line under-indented for visual indent
1920: D400 First line should end with '.', not 't'
1920: D205 Blank line missing between one-line summary and description
1970:73: E261 at least two spaces before inline comment
1970:73: E262 inline comment should start with '# '
1972:81: E261 at least two spaces before inline comment
1972:81: E262 inline comment should start with '# '
1973:81: E261 at least two spaces before inline comment
1973:81: E262 inline comment should start with '# '
1974:81: E261 at least two spaces before inline comment
1974:81: E262 inline comment should start with '# '
1975:81: E261 at least two spaces before inline comment
1975:81: E262 inline comment should start with '# '
1976:81: E261 at least two spaces before inline comment
1976:81: E262 inline comment should start with '# '
1978:81: E261 at least two spaces before inline comment
1978:81: E262 inline comment should start with '# '
1979:81: E261 at least two spaces before inline comment
1979:81: E262 inline comment should start with '# '
1980:81: E261 at least two spaces before inline comment
1980:81: E262 inline comment should start with '# '
1981:81: E261 at least two spaces before inline comment
1981:81: E262 inline comment should start with '# '
1984:76: E261 at least two spaces before inline comment
1984:76: E262 inline comment should start with '# '
1986:84: E261 at least two spaces before inline comment
1986:84: E262 inline comment should start with '# '
1987:84: E261 at least two spaces before inline comment
1987:84: E262 inline comment should start with '# '
1988:84: E261 at least two spaces before inline comment
1988:84: E262 inline comment should start with '# '
1989:84: E261 at least two spaces before inline comment
1989:84: E262 inline comment should start with '# '
1990:84: E261 at least two spaces before inline comment
1990:84: E262 inline comment should start with '# '
1992:84: E262 inline comment should start with '# '
1993:84: E262 inline comment should start with '# '
1994:84: E262 inline comment should start with '# '
1995:84: E262 inline comment should start with '# '
1996:84: E262 inline comment should start with '# '
1998:84: E261 at least two spaces before inline comment
2001:65: E261 at least two spaces before inline comment
2001:66: E262 inline comment should start with '# '
2002:65: E261 at least two spaces before inline comment
2002:66: E262 inline comment should start with '# '
2003:66: E261 at least two spaces before inline comment
2003:66: E262 inline comment should start with '# '
2010:75: E261 at least two spaces before inline comment
2011:75: E261 at least two spaces before inline comment
2012:75: E261 at least two spaces before inline comment
2013:70: E261 at least two spaces before inline comment
2028:15: E128 continuation line under-indented for visual indent
2029:15: E128 continuation line under-indented for visual indent
2030:15: E128 continuation line under-indented for visual indent
2031:23: E211 whitespace before '('
2044:13: E122 continuation line missing indentation or outdented
2045:13: E122 continuation line missing indentation or outdented
2046:13: E122 continuation line missing indentation or outdented
2050:13: E122 continuation line missing indentation or outdented
2051:13: E122 continuation line missing indentation or outdented
2052:13: E122 continuation line missing indentation or outdented
2072:36: E225 missing whitespace around operator
2074:36: E225 missing whitespace around operator
2101: D400 First line should end with '.', not ','
2101: D205 Blank line missing between one-line summary and description
2113:37: E225 missing whitespace around operator
2113:86: E225 missing whitespace around operator
2125: D400 First line should end with '.', not ','
2125: D205 Blank line missing between one-line summary and description
2137:37: E225 missing whitespace around operator
2137:86: E225 missing whitespace around operator
2151:5: E303 too many blank lines (3)
2151: D400 First line should end with '.', not ','
2151: D205 Blank line missing between one-line summary and description
2163:37: E225 missing whitespace around operator
2163:86: E225 missing whitespace around operator
2175: D202 No blank lines allowed *after* method docstring, found 1
2175: D400 First line should end with '.', not ')'
2185:21: E126 continuation line over-indented for hanging indent
2188:26: E225 missing whitespace around operator
2224:9: E122 continuation line missing indentation or outdented
2225:9: E122 continuation line missing indentation or outdented
2226:9: E122 continuation line missing indentation or outdented
2227:9: E122 continuation line missing indentation or outdented
2228:9: E122 continuation line missing indentation or outdented
2229:9: E122 continuation line missing indentation or outdented
2230:9: E122 continuation line missing indentation or outdented
2231:9: E124 closing bracket does not match visual indentation
2234: D401 First line should be imperative: 'Print', not 'Prints'
2234: D400 First line should end with '.', not 'w'
2234: D205 Blank line missing between one-line summary and description
2256:15: E127 continuation line over-indented for visual indent
2256:109: E502 the backslash is redundant between brackets
2258:16: E127 continuation line over-indented for visual indent
2260:48: E225 missing whitespace around operator
2260:67: E225 missing whitespace around operator
2264: D401 First line should be imperative: 'Print', not 'Prints'
2264: D400 First line should end with '.', not 'w'
2264: D205 Blank line missing between one-line summary and description
2286:72: E221 multiple spaces before operator
2287:16: E127 continuation line over-indented for visual indent
2287:82: E502 the backslash is redundant between brackets
2287:44: E225 missing whitespace around operator
2287:63: E225 missing whitespace around operator
2291:81: E221 multiple spaces before operator
2292:20: E126 continuation line over-indented for hanging indent
2292:86: E502 the backslash is redundant between brackets
2292:48: E225 missing whitespace around operator
2292:67: E225 missing whitespace around operator
2296:79: E221 multiple spaces before operator
2297:20: E126 continuation line over-indented for hanging indent
2297:86: E502 the backslash is redundant between brackets
2297:48: E225 missing whitespace around operator
2297:67: E225 missing whitespace around operator
2301:16: E127 continuation line over-indented for visual indent
2305: D401 First line should be imperative: 'Print', not 'Prints'
2305: D400 First line should end with '.', not 'e'
2305: D205 Blank line missing between one-line summary and description
2332:15: E271 multiple spaces after keyword
2334: D202 No blank lines allowed *after* method docstring, found 1
2334: D400 First line should end with '.', not 'e'
2334: D205 Blank line missing between one-line summary and description
2372: D400 First line should end with '.', not 'r'
2414:78: E251 unexpected spaces around keyword / parameter equals
2414:80: E251 unexpected spaces around keyword / parameter equals
2415:78: E251 unexpected spaces around keyword / parameter equals
2415:80: E251 unexpected spaces around keyword / parameter equals
2416:79: E251 unexpected spaces around keyword / parameter equals
2416:81: E251 unexpected spaces around keyword / parameter equals
2417:55: E231 missing whitespace after ','
2417:78: E251 unexpected spaces around keyword / parameter equals
2417:80: E251 unexpected spaces around keyword / parameter equals
2425:22: E222 multiple spaces after operator
2460:9: E303 too many blank lines (3)
2523:34: E126 continuation line over-indented for hanging indent
2526:102: E502 the backslash is redundant between brackets
2526:77: E225 missing whitespace around operator
2526:96: E225 missing whitespace around operator
2531:98: E502 the backslash is redundant between brackets
2531:73: E225 missing whitespace around operator
2531:92: E225 missing whitespace around operator
2555:25: E127 continuation line over-indented for visual indent
2555:37: E203 whitespace before ':'
2556:37: E203 whitespace before ':'
2557:37: E203 whitespace before ':'
2558:37: E203 whitespace before ':'
2559:37: E203 whitespace before ':'
2560:37: E203 whitespace before ':'
2565:24: E261 at least two spaces before inline comment
2570:16: E127 continuation line over-indented for visual indent
2597:52: E126 continuation line over-indented for hanging indent


1: D400 First line should end with '.', not 's'
25:1: I100 Imports statements are in the wrong order. from flask_login should be before from invenio.modules.alerts.models
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
28:1: E302 expected 2 blank lines, found 1
28: D101 Docstring missing
34: D102 Docstring missing
36:26: E261 at least two spaces before inline comment
36:27: E262 inline comment should start with '# '
42: D102 Docstring missing
73: D102 Docstring missing
75:16: E126 continuation line over-indented for hanging indent


3: L102 copyright year is outdated, expected 2015 but got 2014


1: D400 First line should end with '.', not 's'
23:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from flask_login should be before from invenio.ext.template
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
31: D101 Docstring missing
33: D102 Docstring missing
40: D102 Docstring missing
68: D102 Docstring missing
70:16: E126 continuation line over-indented for hanging indent


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


여기도 마찬가지. nested resource는 member 안 함


"desnity"


:shirt:


"capcity"


non-null이 되어야겠지?


Nah, neither me or Temasek is an expert an D2TW.
On Mar 24, 2015 10:50 PM, "jgcaap" <notifications@github.com> wrote:

> big thanks:) by any chance you guys were able to fix double tap wake? I
> cant find a proper fix which has been a pain :( lol
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/temasek/android_frameworks_base/commit/5ff0c1a2146bff7f1210c08127aec2f7f2dda789#commitcomment-10367310>
> .
>


Mes des screens ou même des gifs stp.


这个地方的处理考虑一下事件代理机制？

jQuery中的事件代理是这样用的：

```js
$(this.main).on('click', '[data-action]', $.proxy(this.onClick));
```

多出来的第二个参数是一个`selector`，也就是说，在`this.main`的满足`selector`的元素被点击时，调用`this.onClick`。

我们的`delegate`现在也支持`selector`，使用方法是类似这样：

```js
this.delegate(this.main, 'click', '[data-value]', this.onClick);
```

试试这种方案，可以简化在`onClick`中的逻辑。


"Capcity"


@erwan https://github.com/prismicio/scala-kit/compare/master...cchantep:fragments-pkg?expand=1 ?


28:1: I100 Imports statements are in the wrong order. from invenio.utils.shell should be before from invenio.version


28:1: I101 Imported names are in the wrong order. Should be BlueprintAutoDiscoveryRegistry, ConfigurationRegistry, ExtensionRegistry, PackageRegistry, Registry
31:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
34:1: I101 Imported names are in the wrong order. Should be unicodifier, with_app_context
273:9: B901 blind except: statement


1: D400 First line should end with '.', not 'l'
1: D205 Blank line missing between one-line summary and description
38:1: I100 Imports statements are in the wrong order. import gettext should be before import babel
38:1: I201 Missing newline before sections or imports.
39:1: I201 Missing newline before sections or imports.
39:1: F999 redefinition of unused 'gettext' from line 38
40:1: I201 Missing newline before sections or imports.
40:1: F401 'iteritems' imported but unused
46: D400 First line should end with '.', not 'n'
64: D209 Put multi-line docstring closing quotes on separate line
64: D400 First line should end with '.', not 's'
64: D205 Blank line missing between one-line summary and description
64: D208 Docstring is over-indented
82: D209 Put multi-line docstring closing quotes on separate line
82: D400 First line should end with '.', not 'e'
82: D205 Blank line missing between one-line summary and description
82: D208 Docstring is over-indented
97: D400 First line should end with '.', not ','
97: D205 Blank line missing between one-line summary and description
116: D401 First line should be imperative: 'Return', not 'Returns'
116: D400 First line should end with '.', not 's'
116: D205 Blank line missing between one-line summary and description


1: D100 Docstring missing


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
65:1: I201 Missing newline before sections or imports.
73: D101 Docstring missing
76: D102 Docstring missing
80: D102 Docstring missing
86: D400 First line should end with '.', not 'n'
86: D200 One-line docstring should not occupy 3 lines


1: D100 Docstring missing
20:1: I101 Imported names are in the wrong order. Should be abort, current_app
21:1: I101 Imported names are in the wrong order. Should be AdminIndexView, BaseView
21:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
27:1: I100 Imports statements are in the wrong order. from invenio.ext.principal should be before from invenio.ext.sslify
30: D400 First line should end with '.', not 's'
30: D200 One-line docstring should not occupy 3 lines
49: D203 Expected 1 blank line *before* class docstring, found 0
49: D204 Expected 1 blank line *after* class docstring, found 0
49: D400 First line should end with '.', not 's'
49: D200 One-line docstring should not occupy 3 lines
57: D290 White spaces around docstring should be trimmed.
57: D400 First line should end with '.', not 'n'
70: D401 First line should be imperative: 'Thi', not 'This'
70: D200 One-line docstring should not occupy 3 lines
80: D400 First line should end with '.', not 'r'
80: D200 One-line docstring should not occupy 3 lines
88: D200 One-line docstring should not occupy 3 lines
98: D203 Expected 1 blank line *before* class docstring, found 0
98: D204 Expected 1 blank line *after* class docstring, found 0
98: D400 First line should end with '.', not 's'
98: D200 One-line docstring should not occupy 3 lines
111: D203 Expected 1 blank line *before* class docstring, found 0
111: D204 Expected 1 blank line *after* class docstring, found 0
111: D200 One-line docstring should not occupy 3 lines


52:1: I101 Imported names are in the wrong order. Should be current_app, jsonify, request
52:1: I100 Imports statements are in the wrong order. from flask should be before import requests
53:1: I201 Missing newline before sections or imports.
54:1: I201 Missing newline before sections or imports.
56:1: I100 Imports statements are in the wrong order. from invenio.utils.xmlhelpers should be before from lxml.etree


44:1: I101 Imported names are in the wrong order. Should be Bundle, CleanCSSFilter, RequireJSFilter


23:1: I201 Missing newline before sections or imports.
24:1: I100 Imports statements are in the wrong order. import warnings should be before import pkg_resources
24:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
28:1: I201 Missing newline before sections or imports.


24:1: I201 Missing newline before sections or imports.
25:1: I101 Imported names are in the wrong order. Should be _request_ctx_stack, current_app
25:1: I100 Imports statements are in the wrong order. from flask should be before import six
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
29:1: I201 Missing newline before sections or imports.
235:9: B901 blind except: statement


24:1: I201 Missing newline before sections or imports.
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
28:1: I100 Imports statements are in the wrong order. from webassets.filter.requirejs should be before from werkzeug.utils
28:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. from webassets.filter should be before from webassets.filter.requirejs


23:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from babel should be before import six
27:1: I100 Imports statements are in the wrong order. from contextlib should be before from babel
27:1: I201 Missing newline before sections or imports.
28:1: I101 Imported names are in the wrong order. Should be _request_ctx_stack, current_app, g
28:1: I201 Missing newline before sections or imports.
29:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
33:1: I100 Imports statements are in the wrong order. from .errors should be before from .selectors
90:5: E266 too many leading '#' for block comment


22:1: I101 Imported names are in the wrong order. Should be current_app, request, session
23:1: I201 Missing newline before sections or imports.
32:9: E266 too many leading '#' for block comment
33:9: E266 too many leading '#' for block comment
36:13: E266 too many leading '#' for block comment
39:9: E266 too many leading '#' for block comment
42:13: E266 too many leading '#' for block comment
43:13: E266 too many leading '#' for block comment
46:13: E266 too many leading '#' for block comment
54:17: E266 too many leading '#' for block comment


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
33: D202 No blank lines allowed *after* function docstring, found 1


28:1: I201 Missing newline before sections or imports.


52:1: I100 Imports statements are in the wrong order. from urlparse should be before import requests
52:1: I201 Missing newline before sections or imports.
54:1: I101 Imported names are in the wrong order. Should be current_app, jsonify, request
55:1: I201 Missing newline before sections or imports.


1: D400 First line should end with '.', not 'n'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
34:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: F999 redefinition of unused 'MIMEMultipart' from line 35
36:1: E402 module level import not at top of file
37:1: F401 'MIMEText' imported but unused
37:1: E402 module level import not at top of file
38:1: E402 module level import not at top of file
39:1: I201 Missing newline before sections or imports.
39:1: E402 module level import not at top of file
40:1: I101 Imported names are in the wrong order. Should be EmailMessage, EmailMultiAlternatives
40:1: I201 Missing newline before sections or imports.
40:1: E402 module level import not at top of file
41:1: I101 Imported names are in the wrong order. Should be AbstractFormatter, DumbWriter
41:1: I100 Imports statements are in the wrong order. from formatter should be before from flask_email.message
41:1: I201 Missing newline before sections or imports.
41:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be StringIO, iteritems
42:1: I201 Missing newline before sections or imports.
42:1: E402 module level import not at top of file
43:1: I100 Imports statements are in the wrong order. from time should be before from six
43:1: I201 Missing newline before sections or imports.
43:1: E402 module level import not at top of file
45:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
51:1: E731 do not assign a lambda expression, use a def
86: D400 First line should end with '.', not 'd'
86: D205 Blank line missing between one-line summary and description
99:25: E124 closing bracket does not match visual indentation
140:8: E714 test for object identity should be 'is not'
142:8: E714 test for object identity should be 'is not'
158: D301 Use r""" if any backslashes in a docstring
158: D400 First line should end with '.', not 'y'
158: D205 Blank line missing between one-line summary and description
267:53: E502 the backslash is redundant between brackets
268:25: E128 continuation line under-indented for visual indent
268:50: E502 the backslash is redundant between brackets
268:28: E251 unexpected spaces around keyword / parameter equals
268:30: E251 unexpected spaces around keyword / parameter equals
269:25: E128 continuation line under-indented for visual indent
269:50: E502 the backslash is redundant between brackets
269:28: E251 unexpected spaces around keyword / parameter equals
269:30: E251 unexpected spaces around keyword / parameter equals
270:25: E128 continuation line under-indented for visual indent
270:44: E502 the backslash is redundant between brackets
270:31: E251 unexpected spaces around keyword / parameter equals
270:33: E251 unexpected spaces around keyword / parameter equals
271:25: E128 continuation line under-indented for visual indent
271:46: E502 the backslash is redundant between brackets
271:35: E251 unexpected spaces around keyword / parameter equals
271:37: E251 unexpected spaces around keyword / parameter equals
272:25: E128 continuation line under-indented for visual indent
272:35: E251 unexpected spaces around keyword / parameter equals
272:37: E251 unexpected spaces around keyword / parameter equals
301:24: F821 undefined name 'CFG_SITE_ADMIN_EMAIL'
301:46: F821 undefined name 'CFG_SITE_ADMIN_EMAIL'
314: D200 One-line docstring should not occupy 3 lines
325: D209 Put multi-line docstring closing quotes on separate line
325: D205 Blank line missing between one-line summary and description
428:21: E266 too many leading '#' for block comment
440:13: B901 blind except: statement
465: D401 First line should be imperative: 'Remove', not 'Removes'
465: D400 First line should end with '.', not 'n'
465: D205 Blank line missing between one-line summary and description
487: D400 First line should end with '.', not 's'
487: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from flask_email.backends.console should be before from .
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from flask_email.backends.smtp should be before from .
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file


1: D400 First line should end with '.', not 'r'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
4: L102 copyright year is outdated, expected 2015 but got 2013


24:1: I201 Missing newline before sections or imports.
25:1: I100 Imports statements are in the wrong order. from flask_registry should be before from werkzeug.utils
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.


I'm glad you like my contribution! I needed this for my own project that uses Composer. You will find that the library is also added to Packagist (look for `owasp/esapi`). If my fork is merged, it should point to the official repo.


Angry edit!


Sorry for my English.
My first problem is fixed in #916  (decoding to UTF-8 string).
The second problem is a wrong search, when I send request with Russian letters.

From: 无闻
Sent: Tuesday, March 24, 2015 3:35 PM
To: gogits/gogs
Cc: Andrey Smirnov
Subject: Re: [gogs] modules/ans1-ber: fix LDAP UTF8 string decoding for #916 (3a44143)

  I encountered a new problem.

What is the new problem?

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


如果内部没有调用这个方法，就把它移除掉吧。


90022444-FewReleasePrepThings (Myoldmopar) - i386-Windows-7-VisualStudio-12: Tests Failed

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


I'm going to revert this and replace the mammoth textures myself


That patch is not sufficient:
```
$ nix-instantiate -A clang_34
error: attribute ‘gcc’ missing, at /home/eelco/Dev/nixpkgs/pkgs/build-support/cc-wrapper/default.nix:174:38
(use ‘--show-trace’ to show detailed location information)
```
I guess older versions of Clang also need that passthru?


better use `~5.0`, to give more freedom. Or is there anything speaking against this?


Hi @svnsbck, could you try testing #189 and see if that fixes any issues you have?


@mickadoo - you can move the Check from Paul into a better location, probably the Slack Object itself

https://github.com/null9beta/random-quote-bot/blob/master/src/RandomQuoteBot/Library/Slack/Console/Command/RandomQuoteToSlackCommand.php#L71


I'm not sure to correctly understand the whole picture, but for me using a class property everywhere it was possible should be deprecated for now, and maybe asserted in the future. Are we agree with that ?


Yeah. Will ensure tarball builds by tonight.


Hello world


Bah, I meant New York Times.


NESSweb will not go down without a fight!


Ese fix se puede hacer directamente dentro de la función.  Por ejemplo:
<pre>
public function addButton(...)
{
     $navigator = $this->getNavigator();
     // Do something to fix ie6/ie7/etc
}
</pre>
De esta manera se resuelve el problema para todos los botones y no solo para 3 botones dentro de ejercicios... :smile:


Are all of them hashed with the sha512 algo now or do we have to check both hashes?


use readFileSync only during initial startup or for simple command line tool.
but otherwise, use async


woops haha


@simon-xia 这里我校对了一遍，基本没什么问题。


Hi @Caledfwlch1 , no problem, I've created an issue for this: https://github.com/gogits/gogs/issues/1139


Typo in generatior.


How exactly does this increase any parallelism?


这里我校对了一遍，还有些疑问用注释标了出来 @simon-xia


ce projet est un projet opensource, nous ne pouvons utiliser 'blease' comme dépendance


De acuerdo. Dejemoslo a Angel para que lo mande ahí.


Keep link on Mind4SE or on MIND-Tools?


@willhaynes I don't see mention of the 50 X 50 for sticky footer -- is it only mentioned in the pre-checklist?


Thanks a lot for this note.


Agree completely, I think it was highly fueled by Graham permissive stance "Not out fault, sorry". Things get dismissed very easily and it gives the impression 'we don't care' which I think that causes some upsets. I definitely don't think there was any kind of malice or intention to upset, it's just unfortunately how it came across.

With that said, we should see perspective that Taylor, Graham and the community have done an awesome job with Laravel. We know that occasionally things go sideways, let's just learn and move on folks. :smile:


Good thinking. I've already got a script that does detection and
appropriate installation of broadcom packages when necessary. Maybe we
could integrate this into the install script.
On Mar 24, 2015 8:50 AM, "James Slater" <notifications@github.com> wrote:

> We should be smarter about this.
>
>    - Practically, b43-fwcutter and drivers get close to 1 meg and we have
>    to pull it from the internet. This adds up quick.
>    - Philosophically, there's no reason to throw non-free firmware on a
>    system unless it needs it.
>
> Should take a look on Sat.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/freegeekchicago/fgc-installscript/commit/42fd0a349364dc5555cca152aa45bb7813a84688#commitcomment-10367295>
> .
>


That's because it's going to be nixed pretty soon in #437.


'A command-line client for the Hound source code search engine' instead of 'Lightweight search engine with a web frontend'


@meredithinn you mean the sticky header?


done


Nice one.


Make it E


remove []


I think all the pre-launch checklist needs to say is that the square image people upload should work at a small size (so, don't include text that's going to be unreadable, etc.)


@sly7-7 this is where using a class property is deprecated..

The assert you're commenting on is actually about instances not classes. The deprecation on this line here is deprecating the ability to use a class value


I am 100% fine with the decision. I just wanted to reason about it
together, that's all.

Thanks.

Ali

On Tue, Mar 24, 2015 at 8:51 AM, Antonio Scandurra <notifications@github.com
> wrote:

> @exalted <https://github.com/exalted> Initially I wanted to avoid
> mismatching between our command and Heroku's one, especially since the
> plugin would be downloaded when not installed.
>
> However, I think it's fine to keep a separate naming for our command: this
> way we're able to draw a line between what's ours and what's not. If we
> name it fork and someone else comes along, she may think that the
> original fork version allows HEROKU_API_KEY, or whatever (this someone
> else may be ourselves in two months [image: :smile:]).
>
> Are you strongly opposed to that? Shall we keep it as-is (or find a better
> name than da-fork maybe [image: :laughing:])?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/catchup/catchup-web/commit/a45d29c541442629206aa1ba40d4c24bd1c598b4#commitcomment-10361099>
> .
>


We have a focus directive. Maybe we should just use it


如果`value`是[1,2]，`boxType`是`radio`，`datasource`是[{name: 'a', value: 1}, {name: 'b', value: 2}]，是不是两个`label`都加上了`activeClass`了？


Ahh ok, I'll put a script in to make users go to https for that page. Thanks


trunk and 4.02+trunk


Indeed. I agree that it makes sense for that constructor _not_ to throw the exception, but the fact is that in `1.0.3`, a compatible constructor did. So the change that removes that thrown exception _did_, in practice, actually break the `SPIM_Registration`.


This is giving an eval error in the Nixpkgs tarball:
```
error: while querying the derivation named ‘krfb-14.12.3’:
while evaluating the attribute ‘nativeBuildInputs’ of the derivation ‘krfb-14.12.3’ at "/tmp/nix-build-nixpkgs-tarball-15.05pre1234.abcdef.drv-0/nixpkgs/lib/attrsets.nix":135:44:
attribute ‘telepathy.common_internals’ missing, at "/tmp/nix-build-nixpkgs-tarball-15.05pre1234.abcdef.drv-0/nixpkgs/pkgs/applications/kde-apps-14.12/default.nix":288:34
```
`nix-build -A kde5.krfb` also gives an eval error.


Well said @BrettLefty. Put it much better than me.


@aschweigert thinking about #430


Thanks taylor looks good! Would you be open to the idea of adding back in (maybe for 5.1) paths.php which we can configure all the different paths like public, storage, optimization paths, etc?


:+1: Thank you for listening to the community on this one


I am trying to add all the attributes in alphabetic sort... could you do the same please?


You can configure `storage` using `useStoragePath`... I'm open to adding additional similar methods for other paths. I don't really want a config file - prefer the chainable method approach.


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1132
success: http://build.servo.org/builders/linux2/builds/1132
success: http://build.servo.org/builders/android/builds/1166
success: http://build.servo.org/builders/mac1/builds/1345
success: http://build.servo.org/builders/mac2/builds/1348
success: http://build.servo.org/builders/gonk/builds/314


Can you inject the function instead of calling $parent


GA uses the client id to identify the same user across different sessions, to generate special statistics. In this case, since we only have 1 client reporting to GA (the backend), you could use the same UUID through a constant. I suggest using maybe something like `00000000-0000-0000-0000-000000000000`.


No, es para que ande en Rails 3.2 y 4.0.
Por alguna razón, en Rails 4.1 eso cambió a Rails.application que, si bien también existe en 3.2 y 4.0, se ve que es inicializado en otro momento y tira un error. Así anda en todas las versiones :)


could you do this as alphabetic sort as well?


Ryan... The genders for the Rex are all wrong...


Any chance of requesting a pull from source repository?


better use here and below instead
: ${debug_qa_crowbarsetup:=0}


big thanks ! :D lets see if i damage my framework alone xD

(i'm learning alot with your coding! you guys are smart! this isnt even my area, just a hobbie. in case you need a financial help i can exchange that since i am expert on that xD )


Well, now you'd resolve Node on armv6l to arm-pi.. which is obviously wrong, or at least not narrow enough.
io.js ships with armv6l (ELF) & armv7l (ELF) and they are designated as such: https://iojs.org/dist/v1.6.2/.


i need to understand how file streams work.
it's an already allocated array buffer, so that makes it faster?
that keeps getting replaced with new binary data from the file?
does it "open the file" and keep it open or something?


Fixed in https://github.com/Mind4SE/mindoc/commit/2d0c7a3a2a072f791cde40b671a33d2814d90e7a


Looks good


Fixed in https://github.com/Mind4SE/mindoc/commit/2d0c7a3a2a072f791cde40b671a33d2814d90e7a
The info is now repository-agnostic.


Must be:

```JS
controller: ["$scope", function($scope) {
}]
```
otherwise it will not work when minified


fast-forwarding master to auto = 8f452684


@tvsonar I could remove this without anything failing


pinLength: "@"??


This is a minor style issue, but for paragraphs in Javadoc we use just an opening `<p>` statement and no closing statement (I know it's not valid HTML, but it makes the text version more concise and does not cause any real issue in the HTML version).
And no need for a paragraph around the first sentence of the class/method.


To use `doit.cfg` or `.doit.cfg` is a matter of taste. We could support both to avoid the bikeshedding :)

`dodo.cfg` doesn't make sense to me. You are configuring doit. `dodo.py` is the file where you write tasks for doit, but this name is just a conventions. And soon using `doit.cfg` you will be able to change the default name for the file where you write tasks...


instead it could just pass the debug_qa_crowbarsetup variable to have a single place where it is applied


why do we log bundle throughput in the main section and in the catch?


Should be written with a small case.


`range` is outdated. The correct syntax is `0..count`


Va bene!

Il giorno 24 marzo 2015 14:49, Marco <notifications@github.com> ha scritto:

> Se la risposta é null il dizionario é null, OK!
> Ma se la risposta non é null e il risultato non contiene poll é meglio
> ritornare il dizionario vuoto, quindi semplicemente allocato e inizializzato
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mulasmarco/Panizzi-DePinto2015/commit/584b62544ae3affaea3f9075fc2957c8c09c85d3#commitcomment-10367268>
> .
>


Now, you are allowing a client to call the app when the remaining calls count equals 0, i.e. the limit has been reached. Are you accounting for this anywhere else?


why call clouseSourceIfNeeded here and outside of while?


For paid services. (We also have this for Hotels)


Out of interest where do you normally override your paths (if you do) maybe in bootstrap/app.php ? Sorry if that's in docs (can't see to find it), just wondered best practice for chainable way


Yes, `bootstrap/app.php`.


same method as in MapFeeder.  abstract class or new fancy Java8 interface with some util methods?


Thanks !


its the future!  good stuff


So, should I rewrite the code in a way it will display the hint(s) what method should be used instead?
It will facilitate the use of the library but unfortunately it will reduce the speed of deprecated methods execution (because decorator code will be looking for modern method name every time the method is called).
The reason why I declined to improve the decorator is reduced execution speed. So that, I decided that it would be better to avoid printing some annoying info (hints about method which should be used instead). For instance, Java notifies (notified) user about using deprecated method and do (did) not hint about new method name. As a result user have to look through the doc in order to find the modern method name.
If it is (speed) not a critical issue and you think It is an important issue I can handle this.
------------------------
@brifordwylie, could you have a look at my comment here: https://github.com/kbandla/dpkt/pull/8#issuecomment-82331395


int c=0;


```
multimedia: module deprecation

* INCOMPATIBLE Replaces multimedia module with Flask-IIIF extension.

Reviewed-by: Jiri Kuncar <jiri.kuncar@cern.ch>
Signed-off-by: Harris Tzovanakis <me@drjova.com>
```


The thread is interrupted when the max run time of the job has been exceeded. We want to close the current source and continue to process any remaining bundles in the source.


@KenanSulayman I don't really understand what you mean, all official available Node.js packages for ARMv6 are called "arm-pi" and the io.js ones "armv6l", which is exactly how the code searches for them. I tested both Node.js and io.js with this version of n on my Raspberry Pi 1 and everything worked, so I don't understand what your point is?


It is better if the analytics id is not in the repo, so others can't use it.


handleUncaughtThrowable stops the jvm


The singular form of Queries is Query.


@aem1269 I'm just really loving this table brah


In @ipython_magic2 I had to reverse cmd-line parsing to do the above.


done


MapFeeder will be deleted soon and MapFeederForkJoin will be renamed as MapFeeder.


Should we add `--user` each time?


Trying this as one line instead of 2


The best approach for this is to have an `appengine-web.xml.sample` with the structure of the file and the system properties with some place holders, and to have `appengine-web.xml` ignored in the repo. Then, in the deployment machine, you can create copy the sample file, change its name to `appengine-web.xml`, and set the appropriate values for it. See for example what Wordpress does: https://github.com/WordPress/WordPress/blob/master/wp-config-sample.php


@lukego @n-nikolaev Please vet this change for me. There are some `assert(self.socket, ..)` statements throughout the file which would not work for `self.socket == -1`. Additionally closing either -1 or nil didn't seem like a good idea.


Time [h00m10s00]


Done


We seem to have a regression, as hidden attributes are no longer hidden in popups.


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


24: D400 First line should end with '.', not 's'
24: D205 Blank line missing between one-line summary and description
61:5: B901 blind except: statement
94:5: B901 blind except: statement
106:5: E303 too many blank lines (2)
109: D400 First line should end with '.', not '2'
109: D205 Blank line missing between one-line summary and description
125: D101 Docstring missing
126: D102 Docstring missing
135: D203 Expected 1 blank line *before* class docstring, found 0
135: D204 Expected 1 blank line *after* class docstring, found 0
135: D400 First line should end with '.', not 's'
144: D102 Docstring missing


GREAT! :+1:


Indentation looks not right.


Of course this is right.


btw this guy: http://forum.xda-developers.com/oneplus-one/development/rom-frozenpop-lightly-customized-cm12-t2964040/post59635874#post59635874

seemes to have managed to have fix it, but i cannot find the commit. He says he received from CM directly. which is weird.... =[


I've found it best to edit in Blender. Even Notepad++ was doing actual Tab indentations instead of lots of spaces as python wants it -.-. The Python IDE was just one extra step more than needed; but that said I'm doing the UI where changes are obvious and nice to see instantly.


Do you know about http://vswebessentials.com/ ?
With this extension your css can be minified on saving css-files.
Minified files adding like childs to editing file in solution explorer


It feels like a bad idea to pass the DB result to the closure. The internal pointer is likely to change in the meantime. You should probably create a variable for the ID and pass that to the closure.


I think that this bit of code is sufficiently complicated that it deserves some comments.  However, I see that this code is gone by the end of this ticket.


Sus e joj vanno messi qua


the best!


Lol another reason for me to revert the changes


Shouldn't this have a `return false` somewhere?


Honestly I don't know as I haven't worked with the SDL IME code yet. I think you should check the return value of `SDL_IsTextInputActive` in your `HandleEvents` in `sdl_input.c` and ignore the event if it's `SDL_TRUE`.


Javadoc or even better : no comment.


Is this comment still valid? Do we need to check `job->opts.pty` or is a every child handled here?


Gittalo :)


the only reason we could leave it in keywords is to lighten access to "True"/"False" in the implementation of future rules. On this moment they are not used and i can easily remove them from keywords. What do you think?


@ahgittin This is breaking the build due to [RAT](https://builds.apache.org/job/incubator-brooklyn-pull-requests/ws/software/nosql/target/rat.txt) can you add a license header please?


Why parameters and not referers the constant directly from this method given that you always call it with the same parameters.


What do you mean?


yes, this was intentional. doing so after the discussion we had on irc. BUT I might just do remember it wrongly (did not search the irc logs).

@chrisseaton @enebo @headius please let me know if I shall add truffle back to jruby-complete ?

regarding the assembly/common.xml this is just not there anymore but in assembly/bin.xml, i.e. truffle is part of jruby-dist. and truffle is part of jruby-jars.gem

with the modular org.jruby:jruby artifact, if you want truffle you need to add org.jruby:jruby-truffle as well. and currently the same is true for jruby-complete


awesome


:beer:


I think we should remove them from keywords.


2号機は完成しないかもしれないし、この写真は貼らないほうがいいかな〜


Yes, let's make it private for now.
The only reason not to would be for extensibility, but right now you can't do anything very useful by extending the class. If someone comes up with a feature request in the future, we can expose some protected methods and open the constructor. But I prefer not doing that too early, to avoid committing to a protected API.


@mcollina where is pollErrCount declared?


ok


console.log


Did you check that this test is failing without your changes?


Parameters differ in visitMethodInvocation


You don't want the ```.only``` here. Otherwise, everything looks good to me. Thanks :-D


No idea, like you say I just used the previous value. It's there since early on: https://github.com/coreos/rocket/commit/50cda71331fda3e599d03a719a4672b83a4f2485


A comment about the intention would be better here. Maybe: just unblock the AsyncIO thread to leave its endless loop.


わかりました、削除しておきます！


Sounds OK to me.


Speed is definitely a critical requirement. I wonder how much overhead was introduced adding decorators. We need to do some tests against the pre-decorated code and see if/how much difference there is.


I don't understand why you cast it twice, or for that matters, why do you cast it at all? They should be ints.


IMHO, It would be must better if you could call this only once in `bindPathsInContainer()` and then set (as an example) `$this['path.compiled']` to either `$this->basePath().'/vendor'` or `$this['path.storage'].'/framework'`


oops!


can Reservations or Instances be empty arrays?


@ctrueden Ok, I see itnow


90022444-FewReleasePrepThings (Myoldmopar) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


こっちで消してmergeします！


Ah yeah, that would probably be better. This was more of a quick fix since people were pretty upset. We can refine it now.


Ta bort skiten för fan!
inte ok
GG i report u


Looking good so far!
Just out of curiosity and laziness, where are the custom rounding rules defined? x]


console.log?


well done


no idea. We have that code running in aws-ami-container, so I think it's a safe bet.


This is not thinking ahead, that's my point. As Node progresses on to v8 4.1 we will see armv6l, armv7l and probably even armv8l binaries — and then your code will still resolve armv6l to arm-pi.


Fair enough. What about getters and setters? Should I remove them from QueryLogger API as well?


This is great!


ok.


Hey Yoda, you mixed C3 and C4 coding style :D


We should check how this looks in the documentation, I think napoleon style comment would just add the kwargs to the end of Args.


哈哈，这个有意思


Removed it :+1:


@ArturKlajnerok this had the potential of operating on a nil pointer. I changed this function to operate on a non pointer value (makes no sense to calculate pass years on nil) and added the check where the function is invoked


for persistence there are 3 rst pages, one for java8 also


@ankostis sure, make a new PR whenever you want to submit some code.


Thank you very much, I'll wait for adjustments.

From: 无闻
Sent: Tuesday, March 24, 2015 3:56 PM
To: gogits/gogs
Cc: Andrey Smirnov
Subject: Re: [gogs] modules/ans1-ber: fix LDAP UTF8 string decoding for #916 (3a44143)

Hi @Caledfwlch1 , no problem, I've created an issue for this: #1139

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


this is definitely the one
Try left aligning the white dropdown box and the text inside it and connect the whole drop down to the button itself.
Note sure if background color should extend past the border on CSS.


Kut Jenkins gedoe. Wat een oplossing ook he...


>  Do we need to check job->opts.pty or is a every child handled here?

This is what caused a job test hang in clang/OSX. I can only guess how signals are delivered by libuv:  I know that `uv_spawn` adds its own `SIGCHLD` handler but it seem like other handlers can "compete" with it. In any case it should be save to call `process_close` here even if the job was created by uv_spawn.


@KenanSulayman Well I suggest you make your own pull request then, this one has been merged already anyway, then we don't need to discuss it here but rather also see how you would do it and merge it then.


@kbandla so you think that hint(s) should be implemented?


Also, there's a texture hole in the Rex's butt.


Doesn't it also need to expect "eval"? Otherwise it's not defined whether `wrap-cljs-repl` or `interruptible-eval` will handle a message with `{:op "eval"}`, right?


@tvsonar I think this can be rewritten into switchStatement.Sections.Take(currentSectionIndex).ToList();


I don't think we want to keep that.


Sorry commenting on my phone so I cannot check, is kwargs added to the docs for this method as well.


Thai you again for the PR.  Just a few minor things.


Can we just create an anonymous class that goes away?  `stub = Class.new {}`


> 28,664 additions and 128,607 deletions.

Holy commit batman!

At that point I'd think `public/` should be a submodule!


i am new plz help me how to send email using github


@tpietzsch The most proper fix would be to readd that checked exception, though I guess you could instead say that the constructor ever declaring that exception was a "bug" which is now "fixed"...


r+


Yes, that would solve it too, I think


I would use something like this:

```
static gint
slng_stats(int argc, char *argv[], const gchar *mode)
{
  GString *rsp = NULL;
  const gchar *command = _stats_command_builder();

  rsp = _run_cmd(command);

  if (rsp)
    {
       printf("%s\n", rsp->str);
       g_string_free(rsp, TRUE);
       return 0;
    }
  else
    return 1;
}
```


Hi,

I am a German and interested in some improvements for the German translations. How can we 'manage' this? Should I send you a patch?
Tomas


saw approval from jdm
at https://github.com/dmarcos/servo/commit/0ec5490c6683becbbd286b6caffb18b3bdf979b8


merging dmarcos/servo/issue4784 = 0ec5490c into auto


dmarcos/servo/issue4784 = 0ec5490c merged ok, testing candidate = 204be006


I suppose it should be fine with `~5.0`, but I am unsure.
For example, at 'bootstrap' we demand 3.1 or higher:
https://github.com/yiisoft/yii2-bootstrap/blob/master/composer.json#L22


This is true for native arrays. Not so true for HTMLCollections:

http://jsperf.com/array-length-in-loop-dom


Exactly. This is why I would want to make this a grunt task that you can either run during deployment or just manually (depending on your use case).


FYI: we also need to set `Concurrent build: 1` to avoid having parallel builds.

http://blog.travis-ci.com/2014-07-18-per-repository-concurrency-setting/


CyanogenMod has some several workarounds, which acts like a "fix".

So he does have a point there.
On Mar 24, 2015 11:12 PM, "jgcaap" <notifications@github.com> wrote:

> btw this guy:
> http://forum.xda-developers.com/oneplus-one/development/rom-frozenpop-lightly-customized-cm12-t2964040/post59635874#post59635874
>
> seemes to have managed to have fix it, but i cannot find the commit. He
> says he received from CM directly. which is weird.... =[
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/temasek/android_frameworks_base/commit/5ff0c1a2146bff7f1210c08127aec2f7f2dda789#commitcomment-10367900>
> .
>


revertti


Great point. I didn't think of that. We should probably namespace them in that case, you think?


Try to avoid using temporary variables when there is no intermediary steps which they are being used for:

```javascript
add: function(x, y) {
  return x+y;
}
```


Also, stylistically try not to use parens when they are not needed.


Thanks for the feedback, just don't look at my latest repo its more of the same. lol. But I will definitely keep that in mind!

Date: Mon, 23 Mar 2015 18:31:43 -0700
From: notifications@github.com
To: contact-list-3@noreply.github.com
CC: amarbir_151@hotmail.com
Subject: Re: [contact-list-3] active record (7bd65dd)

This isn't related to your code, but one benefit of github is that you don't really need to comment out old code since git keeps all your history - you can always go through the history of any file and bring back old code. It does however require a bit of a learning curve, since it's not always easy to do that in git.

But, perhaps another option you have aside from commenting old code or removing it entirely, is if you're working on a new feature or a new version of a file, you can create a new git branch, delete the code there, and add your new code. That way you'll still have the old code in the old branch, and the new branch will be much cleaner!

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


This is correct. But you can also do both together, won't do any harm.


Well, at the moment it is bikeshedding :-), but i came to this issue while i was trying to set the `--db-file` param on ipython (see @b6b10b6b7).  Obviously the `*cfg` file would need to be sourced from the same folder.

Anyway, it might be worthwhile to have a site-wide `~/.doit.cfg` and a project-wide `dodo.cfg`.
Unless a `setuptools` plugin architecture is used.


Che belo.


What happens when you send in:

```javascript
calculator.divide(2, 0);
```

Might need some error checking in there.


hello hello hihihohohohihihohoh


1: M111 unrecognized component name: assets


 throw new Exception("Could not find book by title: " + title,e);

do not throw exception without original exception. Layer who consumes this service must be informated or log all trace

 logger.error(e.getMessage(),e);


DO NOT GRADE.  PLEASE GRADE "lab11a"


Could you please add a comment above the line, which would explain why it's there? Your commit message seems to be just fine for that. Just for clarity and enabling others to quickly understand, what's going on.


yeah, but i have my source synced from theirs, and my builds dont have that working. I believe is on kernel side, they "force" to double tap work.


This looks reasonable.


If your decision is to assume parent coordinates for getFixedMomentsFlux, but switch to local coordinates for set_amom_bbox (and the like), it would probably be a good idea to put a big NOTE in the later routine, to warn readers that the coordinate system for this routine is local.


Good tests!

one additional:

```javascript
it("doesnt fail when divide by 0', function() {
  expect(calulcator.divide(2, 0)).toEqual('Nan');
});
```


@zhangxc11 干得漂亮


Nice work Natalia!


Good!


Done


Don't forget semicolons at the end of statements in JS!


Don't leave test/driver code in your final commits.


LGTM


Yes, this is the right change. I'm surprised the compiler did not warn you: both `g++` and `clang++` are very strict with `Warning: Taking/returning a reference to a temporary.`

(Btw, the first thing I do before `gdb` is re-compiling under `clang++`).