Comment on 63a6a3759b75760627354121317c1a3c6f264784.

There are 613 results for the section checkstylebear. They have been shortened and will not be shown inline because they are more than 10.

| Message | File | Line |
|---|---|---|
| Abbreviation in name 'RAINBOWA' must contain no more than '1' capital letters. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 3 |
| 'method def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 5 |
| Missing a Javadoc comment. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 5 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 6 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 7 |
| Each variable declaration must be in its own statement. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 7 |
| Local variable name 'T' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 7 |
| Local variable name 'N' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 7 |
| Local variable name 'a' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 7 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 8 |
| Each variable declaration must be in its own statement. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 8 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 9 |
| 'for' have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 10 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 11 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 12 |
| 'for' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 13 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 14 |
| 'for rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 15 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 16 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 17 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 18 |
| 'for' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 19 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 20 |
| 'if' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 21 |
| 'if' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 22 |
| 'if rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 23 |
| '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 23 |
| 'else' construct must use '{}'s. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 24 |
| 'else' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 24 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 25 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 25 |
| 'if' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 26 |
| 'if' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 27 |
| 'if rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 28 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 29 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 30 |
| 'for rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 31 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 32 |
| 'for' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 33 |
| 'if' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 34 |
| 'if' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 35 |
| 'if' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 36 |
| 'if rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 37 |
| 'for rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 38 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 39 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 40 |
| 'if rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 41 |
| '}' at column 13 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 41 |
| 'else' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 42 |
| 'for' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 43 |
| 'if' have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 44 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 45 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 46 |
| 'if rcurly' have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 47 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 48 |
| 'if' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 49 |
| 'if' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 50 |
| 'if rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 51 |
| '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 51 |
| 'else' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 52 |
| 'else' child have incorrect indentation level 20, expected level should be 10. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 53 |
| 'else rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 54 |
| 'else rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 56 |
| 'for rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 57 |
| 'method def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/AUG/AUG17/RAINBOWA/RAINBOWA.java | 58 |
| The name of the outer type and the file do not match. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 8 |
| 'class def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 9 |
| 'class def lcurly' have incorrect indentation level 4, expected level should be 2. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 10 |
| '{' at column 5 should be on the previous line. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 10 |
| 'member def type' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 11 |
| 'member def type' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 12 |
| 'ctor def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 14 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 15 |
| 'ctor def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 17 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 19 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 20 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 21 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 23 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 24 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 25 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 27 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 28 |
| 'try' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 29 |
| 'try' child have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 30 |
| 'try rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 31 |
| Catch parameter name 'e' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 31 |
| 'catch' child have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 32 |
| 'catch rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 33 |
| 'while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 34 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 35 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 36 |
| 'class def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 38 |
| 'method def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 40 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 41 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 41 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 41 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 42 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 42 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 42 |
| 'while' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 43 |
| WhitespaceAround: '!=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 43 |
| WhitespaceAround: '!=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 43 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 44 |
| Local variable name 'n' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 44 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 44 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 44 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 45 |
| Local variable name 'q' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 45 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 45 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 45 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 46 |
| 'for' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 48 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 48 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 48 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 48 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 48 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 49 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 49 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 49 |
| 'for rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 50 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 51 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 51 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 51 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 52 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 52 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 52 |
| 'while' child have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 53 |
| 'for' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: 'for' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '>=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| WhitespaceAround: '>=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 54 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 55 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 55 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 55 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 56 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 56 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 56 |
| 'while' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 57 |
| WhitespaceAround: '==' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 57 |
| WhitespaceAround: '==' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 57 |
| 'while' child have incorrect indentation level 16, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 58 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 58 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 58 |
| 'while' child have incorrect indentation level 16, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 59 |
| 'while' child have incorrect indentation level 16, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 60 |
| 'if' construct must use '{}'s. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 61 |
| 'if' have incorrect indentation level 16, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 61 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 61 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 61 |
| 'while rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 63 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 64 |
| 'for rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 65 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 67 |
| WhitespaceAround: '!=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 67 |
| WhitespaceAround: '!=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 67 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 68 |
| Local variable name 'l' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 68 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 68 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 68 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 69 |
| Local variable name 'r' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 69 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 69 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 69 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 70 |
| Local variable name 'k' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 70 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 70 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 70 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 71 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 71 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 71 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 72 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 72 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 72 |
| 'for' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 73 |
| 'for' child have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 74 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 74 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 74 |
| 'if' have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 75 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 75 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 75 |
| WhitespaceAround: '>' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 75 |
| WhitespaceAround: '>' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 75 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 76 |
| 'if rcurly' have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 77 |
| 'if' have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 78 |
| WhitespaceAround: '>=' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 78 |
| WhitespaceAround: '>=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 78 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 79 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 80 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 80 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/APR/APRIL17/SMARKET/SMARKET.java | 80 |
| 'if rcurly' have incorrect indentation level 20, expected level should be 10. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 81 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 82 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 83 |
| 'while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 84 |
| 'while rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 85 |
| 'method def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/APR/APRIL17/SMARKET/SMARKET.java | 86 |
| Using the '.*' form of import should be avoided - java.io.*. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 2 |
| Using the '.*' form of import should be avoided - java.util.*. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 3 |
| 'CLASS_DEF' should be separated from previous statement. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 4 |
| The name of the outer type and the file do not match. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 4 |
| 'class def lcurly' have incorrect indentation level 8, expected level should be 0. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 5 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 5 |
| '{' at column 2 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 5 |
| 'class def modifier' have incorrect indentation level 8, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 6 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 6 |
| 'class def lcurly' have incorrect indentation level 4, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 7 |
| '{' at column 5 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 7 |
| 'member def type' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 8 |
| 'member def type' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 9 |
| 'ctor def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 11 |
| 'ctor def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 12 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 12 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 13 |
| 'ctor def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 15 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 17 |
| 'method def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 18 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 18 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 19 |
| 'while lcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 20 |
| '{' at column 13 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 20 |
| 'try' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 21 |
| 'try lcurly' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 22 |
| '{' at column 17 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 22 |
| 'try' child have incorrect indentation level 20, expected level should be 10. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 23 |
| 'try rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 24 |
| '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 24 |
| 'catch' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 25 |
| Catch parameter name 'e' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 25 |
| 'catch lcurly' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 26 |
| '{' at column 17 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 26 |
| 'catch' child have incorrect indentation level 20, expected level should be 10. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 27 |
| 'catch rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 28 |
| 'while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 29 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 30 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 31 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 33 |
| 'method def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 34 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 34 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 35 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 36 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 38 |
| 'method def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 39 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 39 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 40 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 41 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 43 |
| 'method def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 44 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 44 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 45 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 46 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 48 |
| 'method def lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 49 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 49 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 50 |
| 'try' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 51 |
| 'try lcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 52 |
| '{' at column 13 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 52 |
| 'try' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 53 |
| 'try rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 54 |
| '}' at column 13 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 54 |
| 'catch' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 55 |
| Catch parameter name 'e' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 55 |
| 'catch lcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 56 |
| '{' at column 13 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 56 |
| 'catch' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 57 |
| 'catch rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 58 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 59 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 60 |
| 'class def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 61 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 65 |
| 'method def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 66 |
| 'method def lcurly' have incorrect indentation level 4, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 67 |
| '{' at column 5 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 67 |
| 'method def' child have incorrect indentation level 3, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 69 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 69 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 69 |
| 'method def' child have incorrect indentation level 3, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 70 |
| Each variable declaration must be in its own statement. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 70 |
| Local variable name 'n' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 70 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 71 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 71 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 72 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 72 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 72 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 72 |
| 'method def' child have incorrect indentation level 0, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 73 |
| WhitespaceAround: 'while' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 74 |
| WhitespaceAround: '!=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 74 |
| WhitespaceAround: '!=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 74 |
| 'while lcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 75 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 75 |
| '{' at column 6 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 75 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 76 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 76 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 76 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 76 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 77 |
| 'while' child have incorrect indentation level 0, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 78 |
| 'for' construct must use '{}'s. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| 'for' have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: 'for' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 79 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 80 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 80 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 80 |
| 'for' have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: 'for' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '-' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| WhitespaceAround: '-' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 81 |
| 'for lcurly' have incorrect indentation level 16, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 82 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 82 |
| '{' at column 7 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 82 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 83 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 83 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 83 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 83 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 84 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 84 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 84 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 84 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 85 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 85 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 85 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 85 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 86 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 86 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 86 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 86 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 87 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 88 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 88 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 89 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 89 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 89 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 89 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 90 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 91 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 92 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 93 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 94 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 95 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 96 |
| 'for' have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: 'for' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 97 |
| 'for lcurly' have incorrect indentation level 16, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 98 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 98 |
| '{' at column 7 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 98 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 99 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 99 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 99 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 99 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 100 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 100 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 100 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 100 |
| 'for' have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: 'for' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '<' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '<' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 101 |
| 'for lcurly' have incorrect indentation level 24, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 102 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 102 |
| '{' at column 8 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 102 |
| 'if' have incorrect indentation level 24, expected level should be 10. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: 'if' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '==' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '==' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '&&' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '&&' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '>' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| WhitespaceAround: '>' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 103 |
| 'if lcurly' have incorrect indentation level 32, expected level should be 10. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 104 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 104 |
| '{' at column 9 should be on the previous line. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 104 |
| 'if' child have incorrect indentation level 32, expected level should be 12. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 105 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 105 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 105 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 105 |
| 'if' child have incorrect indentation level 32, expected level should be 12. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 106 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 106 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 106 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 106 |
| 'if rcurly' have incorrect indentation level 32, expected level should be 10. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 107 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 107 |
| 'for rcurly' have incorrect indentation level 24, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 108 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 108 |
| 'for' child have incorrect indentation level 16, expected level should be 8. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 109 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 109 |
| WhitespaceAround: '+' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 109 |
| WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 109 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 110 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 110 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 111 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 111 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 112 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 112 |
| 'while' child have incorrect indentation level 8, expected level should be 6. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 113 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 113 |
| WhitespaceAround: '=' is not preceded with whitespace. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 113 |
| WhitespaceAround: '=' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 113 |
| 'while rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 114 |
| Line contains a tab character. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 114 |
| 'method def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/JAN/JAN17/CAPIMOVE/CAPIMOVE.java | 115 |
| Wrong lexicographical order for 'java.io.DataInputStream' import. Should be before 'java.util.StringTokenizer'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 7 |
| Wrong lexicographical order for 'java.math.BigInteger' import. Should be before 'java.util.Vector'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 9 |
| The name of the outer type and the file do not match. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 11 |
| 'class def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 12 |
| 'member def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 13 |
| Abbreviation in name 'BUFFER_SIZE' must contain no more than '1' capital letters. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 13 |
| 'private' modifier out of order with the JLS suggestions. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 13 |
| Member name 'BUFFER_SIZE' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 13 |
| 'member def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 14 |
| 'member def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 15 |
| ',' should be separated from previous statement. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 16 |
| 'member def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 16 |
| Each variable declaration must be in its own statement. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 16 |
| 'ctor def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 18 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 19 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 20 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 21 |
| 'ctor def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 22 |
| 'ctor def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 24 |
| Parameter name 'file_name' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 24 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 25 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 26 |
| 'ctor def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 27 |
| 'ctor def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 28 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 30 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 31 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 32 |
| Each variable declaration must be in its own statement. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 32 |
| Local variable name 'c' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 32 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 33 |
| 'while lcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 34 |
| '{' at column 13 should be on the previous line. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 34 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 35 |
| 'if' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 35 |
| 'while' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 37 |
| 'while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 38 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 39 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 40 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 42 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 43 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 44 |
| Local variable name 'c' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 44 |
| 'while' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 45 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 45 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 47 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 48 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 48 |
| 'do..while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 50 |
| 'do..while' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 51 |
| 'do..while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 52 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 54 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 54 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 56 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 57 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 59 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 60 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 61 |
| Local variable name 'c' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 61 |
| 'while' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 62 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 62 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 64 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 65 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 65 |
| 'do..while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 67 |
| 'do..while' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 68 |
| 'do..while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 69 |
| 'do..while while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 70 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 71 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 71 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 73 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 74 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 76 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 77 |
| Each variable declaration must be in its own statement. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 77 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 78 |
| Local variable name 'c' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 78 |
| 'while' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 79 |
| 'while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 79 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 81 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 82 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 82 |
| 'do..while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 85 |
| 'do..while' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 86 |
| 'do..while rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 87 |
| 'do..while while' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 88 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 90 |
| 'while' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 91 |
| 'while' child have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 92 |
| 'while rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 93 |
| 'if rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 94 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 96 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 96 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 98 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 99 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 101 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 102 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 103 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 103 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 105 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 107 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 108 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 108 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 110 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 111 |
| 'method def modifier' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 113 |
| 'if' construct must use '{}'s. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 114 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 114 |
| 'method def' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 116 |
| 'method def rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 117 |
| 'class def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 118 |
| 'METHOD_DEF' should be separated from previous statement. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 119 |
| 'method def modifier' have incorrect indentation level 4, expected level should be 2. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 119 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 120 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 121 |
| Local variable name 'n' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 121 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 122 |
| Local variable name 'k' must match pattern '^[a-z][a-z0-9][a-zA-Z0-9]*$'. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 122 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 123 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 124 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 125 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 126 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 127 |
| GenericWhitespace '<' is preceded with whitespace. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 127 |
| GenericWhitespace '<' is preceded with whitespace. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 127 |
| '(' is preceded with whitespace. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 127 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 128 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 129 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 130 |
| 'for' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 131 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 132 |
| 'for' child have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 133 |
| 'if' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 134 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 135 |
| 'for' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 136 |
| 'if' have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 137 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 138 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 139 |
| 'if rcurly' have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 140 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 141 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 142 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 143 |
| 'if rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 144 |
| '}' at column 13 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 144 |
| 'else' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 145 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 146 |
| 'for' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 147 |
| 'for' child have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 148 |
| 'if' have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 149 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 150 |
| 'if' child have incorrect indentation level 24, expected level should be 12. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 151 |
| 'if rcurly' have incorrect indentation level 20, expected level should be 10. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 152 |
| 'for rcurly' have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 153 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 154 |
| 'if' child have incorrect indentation level 16, expected level should be 8. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 155 |
| 'if rcurly' have incorrect indentation level 12, expected level should be 6. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 156 |
| 'for rcurly' have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 157 |
| 'method def' child have incorrect indentation level 8, expected level should be 4. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 158 |
| 'method def rcurly' have incorrect indentation level 4, expected level should be 2. | 2017/MAY/MAY17/CHEFCODE/CHEFCODE.java | 159 |

Until GitMate provides an online UI to show a better overview, you can run [coala](https://coala.io/) locally for more details.


address #36


I think it's less error-prone to skip based on container type, rather than a specific container. Perhaps even a set of types if you wish to be more generic.


Got this here:
```
Exception in thread InvBroadcaster:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/home/glitch/test/PyBitmessage/pybitmessage/network/invthread.py", line 38, in run
    DandelionStems().add(data[1], None, self.dandelionRoutes)
  File "/home/glitch/test/PyBitmessage/pybitmessage/network/dandelion.py", line 20, in add
    self.stem[hashId] = choice(stems)
  File "/usr/lib64/python2.7/random.py", line 275, in choice
    return seq[int(self.random() * len(seq))]  # raises IndexError if seq is empty
IndexError: list index out of range
```


Oh yes of course, ill fix this the next commit. Thank you


So, this commit should have been called:

WaitingRoom GUI structure started


Victor's Branch


Ah, yeah. Sorry about that. I probably didn't notice because my next pr (https://github.com/jruby/activerecord-jdbc-adapter/pull/818) replaces this code and would fix the syntax error.


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/de742651-8462-4286-b78d-3e94ac013f9f "compromisos"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/0d0e8b6d-930b-40fc-ac1c-2a7d8ad5ef0b "compromisos") deployed [compromisos](https://github.com/eschuler7/compromisos/releases/tag/deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20171006-143839 "deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20171006-143839") to [dev](https://console.bluemix.net/apps/6f3a0e56-815a-41fc-aa5f-5ec09678068d?env_id=ibm:yp:us-south "ibm:yp:us-south:eschuler@pe.ibm.com:dev"), including this commit


Corrected a small typo in the example code


What is this data structure for? I see it's used on 51 and 58, just wondering what that's all about. I assume something to do with the dataset


Nice work 🎉


This should be `county` not `county_name`


@simo5 I'm not sure if we can just return a response, because still we need the attributes here for `AllowedSubjects`. See: https://github.com/abstractj/origin/commit/e4e509dc61fcf944805869c8dbd9ab63f2438d54#diff-2004baa088cb0f8c9950e3c41b695797R67


The idea of the context was not to pass special parameters to `getExtruderValue`, but to evaluate with a different context that has a different `getExtruderValue` function. As in, a `getExtruderValue` function that skips certain containers. The context parameter of `SettingFunction.__call__` is a dictionary. For example, you could have these two functions:

    def getExtruderValue(extruder_index, key):
        # Get the extruder value normally.

    def getExtruderDefaultValue(extruder_index, key):
        # Get the extruder value while skipping user containers.

When evaluating the setting, we pass a context, which is a dictionary. Normally it looks like so:

    context = {
        "layer_height": 0.1,
        "infill_sparse_density": 20,
        ...
        "getExtruderValue": ExtruderManager.getExtruderValue
    }

Instead, you would be passing a different context when you wish to evaluate for the default value:
    context = {
        "layer_height": 0.1,
        "infill_sparse_density": 20,
        ...
        "getExtruderValue": ExtruderManager.getExtruderDefaultValue
    }

That way, the definitions won't need to change for this detail.


aaa


Formatting gone wrong


delete some unnecessary things


Sorry for the confusion in the comments, this is fixed in https://github.com/jruby/activerecord-jdbc-adapter/pull/818 I apparently missed a bit while fixing a merge conflict.


The iRobot007 will serve as a waiter to help older people living lonely.


This commit introduces a regression: when you click on the Jenkins build number (e.g. http://192.168.98.94/jenkins/job/a-testlink-debug-job/34/) instead of seeing a table like before, you see the html with all tags exposed (e.g. `
TestLink build ID: 33

TestLink build name: go-34

Total of 3 tests. Where 3 passed, 0 failed, 0 were blocked and 0 were not executed.

List of test cases and execution result status

Test case ID	Test case external ID	Version	Name	Test project ID	Execution status

 57	MFP-1	1	First Test	55	Passed

 61	MFP-2	1	Second Test	55	Passed

 61	MFP-2	1	Second Test	55	Passed

)`


That's a chicken and egg problem. In order to return an `EvaluationError`, we need a `response`,  but to obtain a `response' we need to execute `ExpandSubjects`


@sergehould


I don't have problems with linux, macos and windows on AppVeyor, but I do have problems with local windows VM when I build my app having TDM-GCC installed (I followed the instructions form golang.org to install my Go environment, and it seems to be the preferred variant of MinGW).

```
$ go test github.com/thestk/rtaudio/contrib/go/rtaudio
# github.com/thestk/rtaudio/contrib/go/rtaudio
In file included from ..\..\thestk\rtaudio\contrib\go\rtaudio\rtaudio_stub.cpp:3:0:
C:/Users/Serge/go/src/github.com/thestk/rtaudio/RtAudio.cpp: In function 'void convertBufferWasapi(char*, const char*, const unsigned int&, const unsigned int&, const unsigned int&, const unsigned int&, unsigned int&, const RtAudioFormat&)':
C:/Users/Serge/go/src/github.com/thestk/rtaudio/RtAudio.cpp:3886:37: error: 'roundf' is not a member of 'std'
   outSampleCount = ( unsigned int ) std::roundf( inSampleCount * sampleRatio );
                                     ^
C:/Users/Serge/go/src/github.com/thestk/rtaudio/RtAudio.cpp:3886:37: note: suggested alternative:
In file included from C:/TDM-GCC-64/lib/gcc/x86_64-w64-mingw32/5.1.0/include/c++/cmath:44:0,
                 from C:/Users/Serge/go/src/github.com/thestk/rtaudio/RtAudio.cpp:48,
                 from ..\..\thestk\rtaudio\contrib\go\rtaudio\rtaudio_stub.cpp:3:
C:/TDM-GCC-64/x86_64-w64-mingw32/include/math.h:1051:24: note:   'roundf'
   extern float __cdecl roundf (float);
                        ^
FAIL    github.com/thestk/rtaudio/contrib/go/rtaudio [build failed]
```

Changing it to `std::round` doesn't help until I add `-std=c++0x` to my cgo build flags.


restaurando


This looks good to me


You are welcome. :100:


To prevent users of Factorio's stable release from being unable to use the most recent LTN build i reverted dependency to .34.


Please, move this file to a separated package


@sergehould

test


a


Duplicate!


This work was done in a day 💃


This is equally wrong if you were trying for proper English ;)

`"Only create a few attributes"`


I don't really get what problem this is trying to solve. Perhaps you can document it a bit better?


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/88956c79-c186-4d14-8384-592d9ff3fe0a "simple-toolchain-20170713170738545"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/e5a5f14e-14e7-4d4c-873f-59617367715d "simple-toolchain-20170713170738545") deployed [simple-toolchain-20170713170738545](https://github.com/sclymer/simple-toolchain-20170713170738545/releases/tag/deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-144750 "deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-144750") to [dev](https://console.stage1.bluemix.net/apps/0be740dc-83a2-4529-8ee1-aeb2e14d5932?env_id=ibm:ys1:us-south "ibm:ys1:us-south:sclymer@us.ibm.com:dev"), including this commit


Huge, wide `try: Except` block which catches exceptions of type `Exception`. This is prone to hide some very important bugs and make it hard to debug. Please remove!


@ryltar
Don't commit dev log!!!

When you want added debug log , you can use  it instead of `System.out.println` :
```
private log = Logger.getLogger(ReadTestDataLib.class.getName())
......
log.debug("ici");
log.warn("ici");
log.error("ici");
```


you need to add the paths to the buildDocumentation.bat script also


This is a comment to see if the comment option will work! 👍 💯


Unused variable `e`.


MSVC had some "run code analysis" or similar command that I'd never noticed before.


This is not thread-safe at all.


Bluemix [toolchain](https://console.stage1.bluemix.net/devops/toolchains/767c6bac-d7f3-49e9-bf3a-c9b3c9346cb8 "UI-ys1int-SimpleTC1006T104452"): [Delivery Pipeline](https://console.stage1.bluemix.net/devops/pipelines/b9e27d16-a36c-4e87-b15e-1667e95c7725 "UI-ys1int-SimpleTC1006T104452") deployed [UI-ys1int-SimpleTC1006T104452](https://github.com/idsb3t1/UI-ys1int-SimpleTC1006T104452/releases/tag/deploy-ibm-ys1-us-south-idsb3t3-us.ibm.com-dev-20171006-144931 "deploy-ibm-ys1-us-south-idsb3t3-us.ibm.com-dev-20171006-144931") to [dev](https://console.stage1.bluemix.net/apps/36efa5fb-a191-4ff5-8a6f-d77c686299d6?env_id=ibm:ys1:us-south "ibm:ys1:us-south:idsb3t3@us.ibm.com:dev"), including this commit


Avoid to commit console.log


[Harvest survey descriptions.pptx](https://github.com/thoufer/quhack_the_harvest/files/1363024/Harvest.survey.descriptions.pptx)

these are a few slides from a presentation Khristi and I put together for MF tech section.


no we don't, the response is built later and the contents are mostly nil already if ExpandSubjects (formerly GetAllowedSubjects) returns an error.


OK, I've finished my glut of work for this week - going to take a look at this uploader thing and what styling needs to be done.

The implementation seems to have changed quite a bit since I last looked. So we are not using Dropdown.js now and using [BlueIMP jQuery File Upload](https://github.com/blueimp/jQuery-File-Upload) instead, yes?

When it comes to the final implementation - you want this code to **only** appear with a theme's own files? Or are we going to build any functionality/code into core at all? And will we still put something in the `vendors` directory (currently it still have a folder for dropzone there but has bespoke JS which you have written).

Just want to get me head around how you want it to work before I write anything style-related.


See above, we already return a mostly empty response if the call to Getallowedsubjects/ExpandSubjects returns an error.


You're right. Feel free to PR xD


I dont't have an idea why this empty line is added. It also happens with smaller buffers of `length >= 2*Log_session::MAX_STRING_LEN - 8`.


remover binding.pry


Does this mean it can only return line items created through the service, not the autocreated ones?


que lindu


/!\, Don't commit this file with your own settings


Service


你学过汉语吗，这叫“使用已有虚拟硬盘新建虚拟机”


We'll use reflection instead to look up new stuff we added. The plan is to leave the version reference as is


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/88956c79-c186-4d14-8384-592d9ff3fe0a "simple-toolchain-20170713170738545"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/e5a5f14e-14e7-4d4c-873f-59617367715d "simple-toolchain-20170713170738545") deployed [simple-toolchain-20170713170738545](https://github.com/sclymer/simple-toolchain-20170713170738545/releases/tag/deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-145704 "deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-145704") to [dev](https://console.stage1.bluemix.net/apps/96a3ef21-9d75-4e88-ac87-3ae35b081cf7?env_id=ibm:ys1:us-south "ibm:ys1:us-south:sclymer@us.ibm.com:dev"), including this commit


I suggest adding `-std=c++0x` to your cgo build flags ;)
Actually now that I think about it we could probably fix this by removing `std::` and putting `using namespace std`...


このファイルは、リファクタリングとは別だけど同時に作っちゃった
理由は、UtilでCommandsだけじゃなくてCoverArtGetterもSuperviseするのが意味的に良いかと思ったため


You can probably write it as ` def before_closing_head_tag(_)`


gg ca


I would store it on the dist directory in ex_doc_makeup root and not in `priv`. Everything in priv is copied to _build but in this case we don't need to copy it because it is used only at compile time and not runtime. I did a similar change to ExDoc recently.


Avoid to use answer list to return list object. It is a bad practice we try to delete of Cerberus source.

Prefer return directly  List<AppService>


Bkit huhu


Travis installs version 2.17 (latest is v 2.26):
 https://travis-ci.org/dieterich-lab/dorina/jobs/284227718#L450

I also tested with a bioconda install (v 2.26) and it went fine. I think it should be ok as long pybedtools don't complain, but we can discuss this.


Bluemix [toolchain](https://dev-console.stage1.bluemix.net/devops/toolchains/d7a135c1-52ab-4749-ade7-9228894899cd "simple-toolchain-20171006141110076"): [Delivery Pipeline](https://dev-console.stage1.bluemix.net/devops/pipelines/cf48ed9e-df68-4ced-b0fc-08486edf6295 "simple-toolchain-20171006141110076") deployed [simple-toolchain-20171006141110076](https://github.com/sclymer/simple-toolchain-20171006141110076/releases/tag/deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-150054 "deploy-ibm-ys1-us-south-sclymer-us.ibm.com-dev-20171006-150054") to [dev](https://console.stage1.bluemix.net/apps/23a50f6a-0045-45c9-9edf-6764eefb47ac?env_id=ibm:ys1:us-south "ibm:ys1:us-south:sclymer@us.ibm.com:dev"), including this commit


Not deleted. Deprecated though as a wrapper for `create_table()` with a deprecation notice.


DEFERRED_CHECK sounds fine to me. I considered terms that reflected the worker's status (such as 'FRESH' or, keeping the hive theme 'LARVAL'), but think that might be confusing since it doesn't match a value that would appear in the DB.


Interesting, liking it :)


You can use [try with resources](https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html) to simplify open close connection


Typically code comments document intent, not function. `Load` was completely appropriate here. Only pointing out because changes for the sake of change just create noise ;)

This comment is applicable to many of these changes. Will add a comment to one of the changes that were improvements just to illustrate the differences.

Not trying to discourage, just pointing out details from my experience as a developer over the years. All help is certainly appreciated 👍


Also, since this seems like a really special circumstance, and your are in a position to provide build flags, a quick fix could be `-Droundf=round`


Check if the Title is given or not then assign it to the site title,
if($fixed_title){
$site_title = apply_filters( 'wpseo_title', wpseo_replace_vars( $fixed_title, get_post( $ID, ARRAY_A ) )  );
}
But test it with diff scenarios


This one, and the hexgrid comments are good examples of comments that were wrong.

`"Reset global counters"` and `"Create Hexgrid"` is how they would have been written at all of my jobs in the last 10 years.


The generation code is here: https://github.com/libpwquality/libpwquality/blob/master/src/generate.c

It appears to me that this is just a custom encoding of random bits in order to pass the quality check. Perhaps @t8m could comment as to whether or not there is a loss of security versus raw random bytes.


This is a minor point, but for code clarity it might be nicer to explicitly show all cases.

```
} elsif ($status eq 'DEFERRED_CHECK') {
    ; # do nothing now, wait until the next pass to check on this worker
} else {
    # RUN|PEND|xSUSP handling
}
```


Added in response to #13


what


Spacing is messed up on your import again.

```
find . -name \*.js | xargs sed -i.bak -e 's/^\*/ */'
```


Looks fine to me


Ah thank you sir :) I'll go run this in the whole thing


This may be a weird question, but where do you get code like
` <polyline id="Shape" fill="#A6784E" points="146.59 54 167.375 42 170.839 44 150.055 56 146.59 54"></polyline>`
from?
Is this generated somewhere?


W ten sposób możesz naruszyć limit. Czasami serwery mojangu mulą 😜


The problem is that between 2.17. and 2.26. the syntax e.g. for the intersection command changed by 180 degree. Given a few years of experience with bedtools and the connection with pybedtools old versions like 2.17 should be avoided whenever possible.


Thank you for the observation.  The primary developer @johnb30 has recently shifted to a new role: maintenance of this project is currently paused pending future developments.


Makes sense


XDDD


Don't use `MyLogger`. To simplify code, declare a Logger as a attribute of class :
```
private Logger log = Logger.getLogger(ReadTestDataLib.class.getName());
.....
log.error("text message");
```
Allways included Exception into log :
```
log.error("Unable to execute query : " + exception.toString(), exception);
```


This test would be obsolete with BAT. We will need to clear profile to test wallet creation


@ssozi91 you don't need to import fakeBookings.json here, as you already doing it here https://github.com/ssozi91/cyf-hotel-react/blob/c2c534029f6ef5560d3b1506625ae1ce9ee985f1/src/containers/Bookings.js#L5 and passing the data as a prop,


# hello


Называй переменые в блоке так, чтобы было понятно, что там лежит


You can also unpack a dict by using the double asterix. So if you use **options to pass the properties along, its a bit cleaner. So instead of:
`extruder.getRawProperty(key, "value", use_next = use_next, skip_until_container = skip_until_container, skip_user_container = skip_user_container)`
You can use
`extruder.getRawProperty(key, "value", **options)`


Yep, that should work just fine. You could always test your config on an example URL to see if everything works the way it should. (`gallery-dl -g test:deviantart` to get dA's unittest URLs)


А почему ты local_sum умножаешь, который равен 1, а не то кол-во, которое ввел пользователь?


Зачем тут each, просто обратись по ключам к хешу и перемножь значения.


No problem!


@nikita-leonov I see, have updated my fork. Thanks! I have a few new questions: Is there a way to find whether multiple keys are down at the same time? Is a keyboard down event only triggered when the key goes down, and not when it is held down continuously?


Вот это только усложняет все. кол-во дней в году - это константа, их не надо вычислять и гораздо проще и быстрее задать вручную в массиве. А для високосного года изменить одни элемент в нем


Sorry, define doesn't look so promising, because it redefines too much:

```
In file included from C:/TDM-GCC-64/lib/gcc/x86_64-w64-mingw32/5.1.0/include/c++/cmath:44:0,
                 from C:/Users/Serge/go/src/github.com/zserge/rtaudio/RtAudio.cpp:48,
                 from ..\..\zserge\rtaudio\contrib\go\rtaudio\rtaudio_stub.cpp:3:
C:/TDM-GCC-64/x86_64-w64-mingw32/include/math.h:1051:37: error: conflicting declaration of C function 'float round(float)'
   extern float __cdecl roundf (float);
                                     ^
C:/TDM-GCC-64/x86_64-w64-mingw32/include/math.h:1050:25: note: previous declaration 'double round(double)'
   extern double __cdecl round (double);
```

How about I change it to a ISO-compliant `std::round` and make a pull request with --std=c++0x and a few other Go-related things that fix the build?


hi! i cant try it tonight. it shouldn't be that much work


Hey @JonathanYiv, yeah thats the way the `svg` file is encoded. It's generated when the svg image is created.


I think you are likely running into the same issue I am (where the `rm platform` is un-setting the `engine spec`).

Take a look at https://github.com/bitrise-community/steps-ionic-archive/pull/15.  This is the same way we solved the problem with the `steps-cordova-archive` step.


Вот тут есть проблема, у тебя метод  fibonachi будет вычислять последовательно все элементы до n-го. В итоге, когдла ты вызовешь fibonachi(100), ты найдешь в 100й раз 1-й элемент, 99-й второй, и т.д. Т.е. ты каждый раз будешь заново все просчитывать, вместо того, чтобы сохранить уже полученные значения и считать только следующий элемент.

И у тебя получается 100 элементов последовательности, а нам надо найти все, меньше 100.


Are we again trying to enable boost?


Update: it seems that if you have the gist id you can view the contents even if the gist is secret. No changes are needed.


Используй постфиксную форму записи, если в if всего одна строка:


Не нужно задавать размерность массива, в руби они динамические. И пустой массив принято задавать как []


Oh I see. Thank you.


Revisa que se hayan añadido los archivos nuevos, porque no están.


I figured that if the '#' exists, then a tab must also exist. If I change it to look for '#' then it will need to remove the tab from the filename instead. I think both are equivalent solutions. Does Arena use '#' as the separator?


Тут не нужен `for`, лучш через `each` перебрать алфавит. И вообще в руби for практически не используется, потому что его всегда можно заменить на `each`.


Looking now, was traveling this week and unable to work on X-Tag


сделай  массив с гласными (или просто строку) и проверяй вхождение при помощи метода `include?`