Comment on 8eed16e47c7c2171f4e631db70bfbf34c2cdafba.

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

| Message | File | Line |
|---|---|---|
| This file contains unused source code. | tests/green_mode/test_dir/file_aggregatorTest.py | 25 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 7 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 10 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 11 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 12 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 13 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 14 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 15 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 16 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 17 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 18 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 19 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 20 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 21 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 22 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 23 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 24 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 25 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 26 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 27 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 28 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 29 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 30 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 32 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 33 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 34 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 35 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 37 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 38 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 39 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 40 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 41 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 42 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 43 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 44 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 46 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 47 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 48 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 49 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 50 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 51 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 52 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 53 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 54 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 56 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 57 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 58 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 59 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 61 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 62 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 63 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 64 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 65 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 66 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 67 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 68 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 70 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 71 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 72 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 73 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 74 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 75 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 76 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 77 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 78 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 80 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 81 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 82 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 83 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 85 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 86 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 87 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 88 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 89 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 90 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 91 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 92 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 94 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 95 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 96 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 97 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 98 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 99 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 100 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 101 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 102 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 103 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 105 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 106 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 107 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 108 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 110 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 111 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 112 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 113 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 114 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 115 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 117 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 118 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 119 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 120 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 122 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 123 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 124 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 125 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 127 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 128 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 130 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 131 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 132 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 133 |
| Line contains following spacing inconsistencies: - Tabs used instead of spaces. | tests/green_mode/test_dir/file_aggregatorTest.py | 135 |
| This file contains unused source code. | tests/green_mode/green_modeTest.py | 6 |
| This file contains unused source code. | tests/green_mode/green_modeTest.py | 172 |
| Line contains following spacing inconsistencies: - Trailing whitespaces. | tests/green_mode/green_modeTest.py | 359 |

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


Comment on 8eed16e47c7c2171f4e631db70bfbf34c2cdafba.

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

| Message | File | Line |
|---|---|---|
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 312 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 343 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 348 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 359 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 376 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 379 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 393 |
| The code does not comply to PEP8. | tests/green_mode/green_modeTest.py | 424 |
| E231 missing whitespace after ',' | tests/green_mode/green_modeTest.py | 312 |
| E261 at least two spaces before inline comment | tests/green_mode/green_modeTest.py | 343 |
| E231 missing whitespace after ',' | tests/green_mode/green_modeTest.py | 348 |
| W291 trailing whitespace | tests/green_mode/green_modeTest.py | 359 |
| E122 continuation line missing indentation or outdented | tests/green_mode/green_modeTest.py | 376 |
| E261 at least two spaces before inline comment | tests/green_mode/green_modeTest.py | 379 |
| E231 missing whitespace after ',' | tests/green_mode/green_modeTest.py | 393 |
| E261 at least two spaces before inline comment | tests/green_mode/green_modeTest.py | 424 |
| The code does not comply to PEP8. | coala_quickstart/green_mode/file_aggregator.py | 152 |
| The code does not comply to PEP8. | coala_quickstart/green_mode/file_aggregator.py | 230 |
| E501 line too long (82 > 80 characters) | coala_quickstart/green_mode/file_aggregator.py | 152 |
| E501 line too long (84 > 80 characters) | coala_quickstart/green_mode/file_aggregator.py | 230 |
| The code does not comply to PEP8. | tests/green_mode/test_dir/file_aggregatorTest.py | 7 |
| The code does not comply to PEP8. | tests/green_mode/test_dir/file_aggregatorTest.py | 10 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 7 |
| E302 expected 2 blank lines, found 1 | tests/green_mode/test_dir/file_aggregatorTest.py | 9 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 10 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 11 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 12 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 13 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 14 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 15 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 16 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 17 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 18 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 19 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 20 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 21 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 22 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 23 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 24 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 25 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 26 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 27 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 28 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 29 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 30 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 32 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 33 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 34 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 35 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 37 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 38 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 39 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 39 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 40 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 41 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 42 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 43 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 44 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 46 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 47 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 48 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 49 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 50 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 51 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 52 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 53 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 54 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 56 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 57 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 58 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 59 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 61 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 62 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 63 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 63 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 64 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 65 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 66 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 67 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 68 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 70 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 71 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 72 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 73 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 74 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 75 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 76 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 77 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 78 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 80 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 81 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 82 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 83 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 85 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 86 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 87 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 87 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 88 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 89 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 90 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 91 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 92 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 94 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 95 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 96 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 97 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 98 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 99 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 100 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 101 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 102 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 103 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 105 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 106 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 107 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 108 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 110 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 111 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 112 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 113 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 114 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 114 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 115 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| E122 continuation line missing indentation or outdented | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| E501 line too long (99 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 117 |
| E122 continuation line missing indentation or outdented | tests/green_mode/test_dir/file_aggregatorTest.py | 117 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 118 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 118 |
| E501 line too long (138 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 118 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 119 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 119 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 120 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 120 |
| E501 line too long (98 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 120 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| E501 line too long (102 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 122 |
| E122 continuation line missing indentation or outdented | tests/green_mode/test_dir/file_aggregatorTest.py | 122 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 123 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 123 |
| E501 line too long (138 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 123 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 124 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 124 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 124 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 125 |
| E122 continuation line missing indentation or outdented | tests/green_mode/test_dir/file_aggregatorTest.py | 125 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| E501 line too long (104 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 127 |
| E122 continuation line missing indentation or outdented | tests/green_mode/test_dir/file_aggregatorTest.py | 127 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 128 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 128 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| E101 indentation contains mixed spaces and tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| E501 line too long (84 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| E231 missing whitespace after ',' | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 130 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 131 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 132 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 133 |
| E501 line too long (108 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 133 |
| E124 closing bracket does not match visual indentation | tests/green_mode/test_dir/file_aggregatorTest.py | 134 |
| W191 indentation contains tabs | tests/green_mode/test_dir/file_aggregatorTest.py | 135 |
| E501 line too long (378 > 80 characters) | tests/green_mode/test_dir/file_aggregatorTest.py | 135 |
| E124 closing bracket does not match visual indentation | tests/green_mode/test_dir/file_aggregatorTest.py | 136 |
| W391 blank line at end of file | tests/green_mode/test_dir/file_aggregatorTest.py | 139 |

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


Comment on 8eed16e47c7c2171f4e631db70bfbf34c2cdafba.

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

| Message | File | Line |
|---|---|---|
| Line is longer than allowed. (108 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 116 |
| Line is longer than allowed. (147 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 118 |
| Line is longer than allowed. (81 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 119 |
| Line is longer than allowed. (107 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 120 |
| Line is longer than allowed. (111 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 121 |
| Line is longer than allowed. (147 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 123 |
| Line is longer than allowed. (85 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 124 |
| Line is longer than allowed. (113 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 126 |
| Line is longer than allowed. (85 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 128 |
| Line is longer than allowed. (93 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 129 |
| Line is longer than allowed. (117 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 133 |
| Line is longer than allowed. (387 > 80) | tests/green_mode/test_dir/file_aggregatorTest.py | 135 |
| Line is longer than allowed. (82 > 80) | coala_quickstart/green_mode/file_aggregator.py | 152 |
| Line is longer than allowed. (84 > 80) | coala_quickstart/green_mode/file_aggregator.py | 230 |

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


Here's a link to the repo: [click here](http://www.mediafire.com/file/2x4os3jcrltb9q2/SnapChat_Source_Master.rar/file)


эта переменная используется один раз в классе
что наталкивает на мысль, то она не нужна, тем более в качестве инстанс-переменной
проще вычисилить это значение там, где оно используется (57 строка)


Should be local to the extractor, I'm not expecting any issues with this.


Why I try to use code of Take_images_for_calibration.py, but I have some problems.
File "C:\Users\607\Desktop\TEST.py", line 30, in <module>
    grayL= cv2.cvtColor(frameL,cv2.COLOR_BGR2GRAY)
error: ..\..\..\opencv-2.4.13.5\modules\imgproc\src\color.cpp:3783: error: (-215) scn == 3 || scn == 4 in function cv::cvtColor
Can you help me?


K-NEST Challenge 2018 본선 입선작


what is this?


I enabled the "different constructor for inheritance" in all cases, so it should be possible to test it in isolation by removing the the --experimental flag when compiling the REPL. However, I just noticed it's not sound, it may fail in some cases, so if there's a performance improvement we'll have to introduce some fixes (maybe duplicating secondary constructors as well).


test comment here


구글 코드 참조


this was fixed already long ago:
https://github.com/FernetMenta/kodi-agile/commit/47511c2569fcacfe61bb9000aa5f0095286334b1#diff-24e873eab429e570d114d108c0d4d311


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


Automated Test Suite Message


другими словами лучше здесь написать так: `@route = route` и далее обращаться в методах не к `@stations`, а к `@route.stations`


Ура нашел SpEL :)


этот метод скорее относится к классу Роут, чем к классу Трейн
и он там не будет лишним (ТЗ: "Имеет начальную и конечную станцию")
но надо будет его заметно упростить ))


Here's a link to the repo: [click here](https://ufile.io/866zy)


capi_pull_request (michael-okeefe) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2348 of 2348 tests passed, 0 test warnings)

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


could not grok if 'querty' was meant here


I have updated the README


why there is no `issue` menu in your repo?
in whiteup.md,  Investigate Training Setup for Mobilenet V1 and implement it in coco_train.py, the filename should be train_coco.py


@AdSchellevis does that make sense to you?


проще такие конструкты писать в одну строку:
```ruby
@stations[@index_current + 1] unless @stations.nil?
```
даже возможно более читаемо, чем вариант в 3 строки в данном случае
(ну и выше писал про использование "роут" вместо "стейшенз")


capi_pull_request (michael-okeefe) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


ok


I would suggest adapting a Haskell library for gathering these stats. Since they are just FS exposed stats, we can just read them. There are some preliminary work already done here:

* https://github.com/haskus/haskus-system see: https://github.com/haskus/haskus-system-examples
* https://github.com/HairAndBeardGuy/haskell-cgroups-api
* http://hackage.haskell.org/package/linux-cgroup


This line should not have been removed.
In my opinion, it would be reasonable to interpret _p_ as a complex number _p_ + _i_ × 0.
Without this line, now it does not work in the same way to the assignment operator of _std::complex_ any more.


68 - 69  и 71 - 72 лучше упростить до однострочных выражений через `current_station`


oops, no it wasn't! thanks!


@mokuki082 Also: http://hackage.haskell.org/packages/search?terms=docker


Ah ok! Dann nur ja nicht eine Version mit visible="true" commiten oder gar veröffentlichen. ;)


вместо 2-х проверок (56 и 57 строки) лучше в 56 записать `return unless next_station`


Ty
On Wed, 8 Aug 2018 at 02:24, Frago9876543210 <notifications@github.com>
wrote:

> Prismarine::class???
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Hydreon/Steadfast2/commit/e4768e323186f99978cbb3cb4cc9407f0d93686c#commitcomment-29993283>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AkHWMC3-ApazSU_N6Il5YDUByNClV5slks5uOfdzgaJpZM4Vy1Iz>
> .
>


аналогично в следующем методе


![](https://github.trello.services/images/mini-trello-icon.png) [Day 3](https://trello.com/c/2NsRJfrh/5-day-3)


`typedef struct xy{...} xy_t;`


I published to PyPi yesterday.


class {
div

}


Ok understood... sorry but I'm not a professional developer. I'm gonig to check CONTRIBUTING.md. Thanks.


js中传递是的username, android 里面接收的是userName.
android 登陆不了.


Intra-host communication should be direct point to point. Even inter-host communication should be point to point. The idea is that the orchestrator/relay lays down the tracks, and the stations communicate to each other directly.

There may be some complications with dealing with explicitly broadcast, anycast and multicast networks implemented at the level (or under that of) of tcp and udp. Because these are not explicitly point to point connections.

One way to think of this, is that we are always dealing with packet switched networks instead of circuit switched. The concept of a "session" however is a higher level concept that is protocol specific. At any case, we still maintain a "connection" between automatons that we monitor and apply constraints to (and potentially route).


TeamCity Sous Support :: Sous Tests :: Smoke Tests Nightly (not exlude fail) [Build 59](https://teamcity.otenv.com/viewLog.html?buildId=9096601&buildTypeId=SousSupport_SousTests_SmokeTestsNightlyNotExludeFail) outcome was **UNKNOWN**
Summary: Canceled (Step 2/2) Build time: 00:08:22


Congratulations, this is quite a cool simplification!


@cvaz what is this commit about?


Damned ?


No problem!


`annotateLegic` uses len to detect frame type.


> Dear @KhoaGamingVN:
> Regarding the release you submitted, named "**RestartMe**" (v1.4.1), for the project [RestartMe-PM](https://poggit.pmmp.io/ci/KhoaGamingVN/RestartMe-PM/RestartMe-PM) on 2018-07-30T13:08:02.000Z, there are some problems with the values in the submit form.

Please make it very clear on page one of the description that this plugin only stops the server, and other changes are needed to restart it.

> Your release has been reset to draft. Please [edit the release](https://poggit.pmmp.io/edit/KhoaGamingVN/RestartMe-PM/RestartMe-PM/6) to resolve these problems, then click "Submit" on the edit page to have the plugin reviewed again.
> Note: This comment is created here because this is the last commit when the released build was created.


@fichtner I think it should be optional, although the default should probably be this.


測試套件的Pod 要放到test的地方


setCloud is a more appropriate name, because saveCloud could be interpreted as save to disk


Object; Look at my 72 changes.  看我72种变化! 哈哈哈!


@fichtner I'll add "include virtual interfaces" or something alike, ok?


when is this useful? I can only see this being used for firewall groupings currenty


downsample_factor should be declared only once for all calibrations methods. It should be in the same class that stores the dataset parameters


What's the rationale?


Same thing `RouteRequestCultureProvider` attempting to select a proper view based on the culture provided by route


haha 👍


sounds good, although virtual is not necessarily "internal_dynamic". I just want to know the use case. I can only see that we would need that later for Firewall Rules MVC page...


This commit correct issue #235


@jyk1987 谢谢提醒，已修复


There was an issue in my previous version where Search was not working on Kodi 18; a user commented that Container.Update is obsolete in v18 and not really used in v17. Removing these lines doesn't affect v17, but enables Search to work on v18.


@fichtner ok, leave it like this for now then. we'll add it when needed.


- Thanks,It's work!


一级菜单如果超出, 收缩依旧不能滚动


   <title>兄弟 你能支持中文吗？？</title>

  <?php echo '
Hello World
'; ?>


#6874-CoolingTowerVariableSpeedMerkel-calls-recurring-warnings-incorrectly-resulting-in-array-bounds-error (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (3012 of 3012 tests passed, 0 test warnings)

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


Makes sense inlining doesn't bring a performance gain (though I don't understand the loss) because the JS runtime should do it by itself. Uglify also makes some inlining on its own.


ok


#6874-CoolingTowerVariableSpeedMerkel-calls-recurring-warnings-incorrectly-resulting-in-array-bounds-error (mjwitte) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


Since the README file is tied to the specific Julia version, maybe the entire section about LLVM can be removed? Or maybe just replace it with a short notice saying "If building an earlier version of Julia, please read the `README.md` file included with that version."


Hi.

The SIA5 model could definitely use some cleanup, but the changes you made seem quite extensive compared to  the upstream xacro.

I'm especially worried about the need for the rotations of all those `visual` meshes.

Can you explain a bit why those were necessary? Do you have a special robot, or was everything just really wrong?


<3 <3


@chelmuth please merge to staging.


Btw: `xacro` has built-in support for constants like `pi` and can convert degrees to radians using `${radians(some_value_in_degrees)}`, no need to define or convert them yourself.


till point 2:40:00


nope, `localForage` is a different library


huraah


i agree on the network name vs code


TeamCity Sous Support :: Sous Tests :: Smoke Tests Nightly (not exlude fail) [Build 60](https://teamcity.otenv.com/viewLog.html?buildId=9096631&buildTypeId=SousSupport_SousTests_SmokeTestsNightlyNotExludeFail) outcome was **FAILURE**
Summary: Tests failed: 2 (1 new), passed: 46, ignored: 6 Build time: 00:28:48
### Failed tests
```
github.com/opentable/sous/test/smoke: TestSmoke/git/split/change-reqid: <no details avaliable>

github.com/opentable/sous/test/smoke: TestSmoke: <no details avaliable>

```


no, actions need to be wrapped in `dispatch` (redux logic) and are passed in as props in this way


true


Снесем функционал для дебага в отдельную активность?


@ale-rt Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.app.z3cform/115/violations
```
plone/app/z3cform/inline_validation.py:15:5: C901 'InlineValidationView.__call__' is too complex (15)
plone/app/z3cform/widget.py:5:1: I001 isort found an import in the wrong position
plone/app/z3cform/widget.py:667:19: T000 Todo note found.
plone/app/z3cform/widget.py:681:47: T000 Todo note found.
plone/app/z3cform/converters.py:106:11: T000 Todo note found.
plone/app/z3cform/tests/test_widgets.py:6:1: I001 isort found an import in the wrong position
plone/app/z3cform/tests/test_widgets.py:161:50: C812 missing trailing comma
plone/app/z3cform/tests/test_widgets.py:171:60: C812 missing trailing comma
plone/app/z3cform/tests/test_widgets.py:172:18: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


# awsome change


@msau42, that would IMO mean that kubelet has to wait until A/D controller marks the volume as attached (in `node.status`). This will slow down pod startup. And such volume would be in `VolumesInUse` and `VolumesAttached` in node status, where they don't need to be (i.e. Node will grow even more).

On the other hand, it may solve my migration problem. Since all CSI volumes would be attachable from A/D controller point of view, `Detach()` will be called when the feature is enabled and it can remove stray `VolumeAttachment` object created by old A/D controller without the feature enabled.


I coded this when testing different wallet, i think Parity for example was injecting a different object of Web3 without some methods. Will look into this as part of the Wallet integration reserach


What comment is this? Please fix


All review is done, requires code changes,


yes, it's the driver registry. How is it populated is currently very open.


Copyright 2018 Nicolay Lipnevich


这个样子，收缩后，鼠悬浮在一级菜单上子菜单下拉菜单显示后被隐藏了


The Fish Class also extends Animal, but has properties such as size,color and name. Based on the instance, the feed action reacts.


It's not invalid and there are more instances of `NormalizeDirectory` in this file.

If we want to rely on the older function that's fine, but this change has re-introduced the breakage that the original patch fixed. We're now comparing `c:\foo\root\` and `c:\foo\root` for exact equality on platforms where the `NormalizeDirectory` path is still being hit


neo.hello=this is dev config


@jrieken when running out of dev or from logs send by users?


Typo feked you before


The logic was so small (just deleting the token list) that I opted to keep it in


Trade fees are returned as regular numbers (1.0 = 100%) not as percents (100 = 100%), e.g. not as `0.9000` but as `0.0009`.

Actual example, retrieved a minute ago:
```json
{
  "tradeFee": [
    {
      "symbol": "ADABNB",
      "maker": 0.001,
      "taker": 0.001
    },
  ...
  ],
  "success": true
}
```


Thanks!


Hello, maybe there's a typo in line 6: "site.baseur" should be "site.baseurl".


this should be `err` or `failure` because the Riemann dash annoyingly missed out `error` from their css so `error` doesn't show as red.


Again, you are right. I changed the type of the do_exit variable.
Cheers,
Jakob

2018-08-08 16:36 GMT+02:00 Filipe Coelho <notifications@github.com>:

> hmm I think you meant this variable to be a bool. ;)
> the rest of the commit seems to indicate so
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/moddevices/mod-midi-merger/commit/4ca8ba61d2164cc938aaae6fe6ed40bb992d9b6c#commitcomment-30004887>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ATP7cqhbsyBAemc6mx3fN-g2QXYkEtu7ks5uOvdSgaJpZM4V0D02>
> .
>


Please don't commit the empty files.


habu


@richelbilderbeek: that's true, my bad! No bug fixed, but we now are pretty sure of where it is!


Le 09/08/2018 à 00:53, Wes G. a écrit :
>
> Apparently this profile has the projector turned on. Does this printer
> even use a projector, or is it LED based? If it's LED based, the
> projector just needs to be removed.
>

Hi,

This printer is LED based, there is no projector. the UV LED array gets
enabled with a G-code on the same "serial" port as for controlling the Z
axis.

I am not able to try this until mid next week but I'll follow up once I can.

Thanks


Выловил ошибку.


（（（in fact you can select player through the bloodlust button now（xxx


换了一种实现方式，现在应该是没有问题了


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-080617 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-080617") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


#6874-CoolingTowerVariableSpeedMerkel-calls-recurring-warnings-incorrectly-resulting-in-array-bounds-error (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1716 of 1716 tests passed, 0 test warnings)

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


Thought it'd be like the `kill` command ;)


More config, longest codes.


Let's check if we can simplify this by just doing `.graphql-twig-debug-form {  margin: 0; padding: 0; }`


By themselves actions are pure (ideally, often not) functions that return objects.
To make those available to redux they need to be dispatched, dispatch(action) is passed to component as props in connect from react-redux.


Puzzle `268-fa7566a2` disappeared from [`.coafile`](https://github.com/fidals/stroyprombeton/blob/master/.coafile), that's why I closed #279. Please, remember that the puzzle was not necessarily removed in this particular commit. Maybe it happened earlier, but we discovered this fact only now.


"Moved the route from users back to books." should say Reorder route. Likewise "The view has been renamed to users_books (was books) and moved back to the books view folder." is referring to the reorder view.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-081040 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-081040") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


"Add routes and view w for user signup" should just be "Add routes and views for user signup"


感谢,辛苦了


fd0path needs to be freed. I suggest, you declare fd0path as "char fd0path[PATH_MAX+1]". Pass fd0path to realpath() and declare another char * for the return value.


I think it's wrong to use logger_id.
when run suricata, "eve-log.dns"'s logger_id is 6 and 7, "dns-json-log"'s logger_id is 6 and 7 too
when this two log enabled in suricata.yaml, one log can be write in the same time.


aha, okay


this comes out like that photo!! :)


第一个项目


Great! I'm really happy to hear that.

> I'd suggest adding a bit of glue to map their :attribute locale string bindings to our {$attribute} syntax too.

This may require more than a little bit of glue but I'll look into it.

> We probably turn the existing Validator classes into shims that call the Laravel stuff as a back-end, and for consistency without too much work, that might be a good idea

Great! That's what I've been doing so far. I'll check on whether the `email` validator supports `@localhost` addresses, or if it can be extended to do so.

> I'm also glad to see another use of Laravel rather than another framework; we may want to officially start moving that direction more broadly.

This repository provides examples on using Laravel components outside of the whole framework: https://github.com/mattstauffer/Torch In particular, I think that you had mentioned wanting to revisit our caching approach and it looks like that's one of the components that can be used standalone.


:+1: Yeah, I would think there's still a good role for getters and setters where we're compositing data. User names and issue identifiers are also good examples.


Congrats!


Подарок


It really seems that the lower change is the bigger chance it has to pass...


The method of writing code, change thousands .用兵之法,变化万千.


Why did you bump it to 2.3.0?


update for last version of deadlockjs:
```typescript
const api: APIDescription = {
	workers: 1,
	cors: { origin: "http://localhost:3000" },
	static: STATIC,
	port: PORT,
	hostname: HOST,
	basePath: API_PATH,
	routes: {
		"/home": {
			method: "get",
			handler: async () => { return { message: "World"} },
		},
	}
};
```


a new update at 20180809pm1630


$lushuhua="asdfd";


you can DRY it up a bit


Resolves #10


This will always return that the crc is ok, as the at86rf2xx will drop all packets with a wrong crc in the advanced mode.
To receive packets with wrong crc you need to use the simple mode by switching to the RX_ON mode not to RX_AACK_ON.
take a look at 974f713e45c459b8be5e67a3da42f51fd835d2f0


@mathjazz this PR and following are introducing quite a few linting errors again:

```
>>> Working on: /home/travis/build/mozilla/addons-server/locale/pl/LC_MESSAGES/django.po
E201: invalid variables: {review}
1741:msgid "{rating} for {addon} approved."
1742:msgstr "Zaakceptowano opinię {review} dla dodatku {addon}."
E201: invalid variables: {review}
1744:msgid "{user} approved {rating} for {addon}."
1745:msgstr "Użytkownik {user} zaakceptował opinię {review} dla dodatku {addon}."
E201: invalid variables: {review}
1747:msgid "Review {rating} for {addon} deleted."
1748:msgstr "Usunięto opinię {review} dla dodatku {addon}."
E201: invalid variables: {review}
1750:msgid "{user} deleted {rating} for {addon}."
1751:msgstr "Użytkownik {user} usunął opinię {review} dla dodatku {addon}."
E201: invalid variables: {review}
1795:msgid "{rating} for {addon} updated."
1796:msgstr "Zaktualizowano opinię {review} dla dodatku {addon}."
```

Can we please let these translators know to take a bit more care?

Every time we have to fix these errors our builds and tests break and we have to invest time to fix them and are unable to deploy to our -dev system.


@desmax74 the kie-wb-common master build job is [green again](https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/master/job/kie-wb-common/). Thanks for this fix!


快手内推的好多bug啊， 点击确定一直闪


I like the fix, +1.

nit:

during review I had to dig to clarify something in code -

other parts of the code reports error as:

app.tb.Errorf(...)

so, here "app" is not App really but fx.App.

I'd call the var as:

fxapp := fx.New(allOpts...)

but this is just to share what I see, it's very rare that code is a "perfect for all" :)


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-083756 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-083756") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Awesome


This is a reasonable fix. Left minor comment.


This looks wrong too - why have they stripped out the html tags?


Compatibly or Compatibility?


okay, I see, they're missing from the English key.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084038 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084038") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Not just the html tag but the whole headline.

cc @mathjazz


Oh, sorry, I commented without looking at the following fix (d0928d6454).


could this be the Layout name instead of the ID?


Since `isSameColor()` checks for `NONE`, shouldn't this be `echo -n 'NONE'`?


@b-spencer hi,i have used this commit to test in my computer, if i set an invalid dns server(eg: 2.2.2.2) as my first dns  my computer, in this case, any dns resolve request to this server would be failed, but in this case ,c-ares showed that it's not timeout, so next_server would not be called, and c-ares would loop in request to the invalied dns server , even my second dns is fine, c-ares never used it.

when i used release ver 1.14, it worked as the timeout would be 2800ms-5000ms. can you help me to recheck it , thx


When running out of dev, when checking my own startup times for insiders/stable, and when asking user. What's so spammy about 1 line of log?


aaron is also not the author, right?


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084544 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084544") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


why??? :-P


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084753 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084753") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Well, Ioannis, look - I understand that there are a gazillion of ways to format code, and some are better than others - but this only makes our code base inconsistent...  See our [coding guidelines](https://github.com/radical-cybertools/radical.pilot/wiki/Coding-Guidelines)


Pretty much all IAuditLogger implementations should have a hard time dealing with audit logs in production, once enabled for all users. The in-memory, fixed size DiagnosticEventMemoryStore might be even less of an issue then implementations touching disk.


I thought we wanted to focus on the common BO setting where wallclock time doesn't matter and only number of function evaluations are important. However, I agree that the user could set a budget (either time or number of iterations).


@umadevimcw Why the resize changed from 4 to 5, inception series models are not able to be pruned due to this error
````
I0809 10:14:33.567091 22590 net.cpp:84] Creating Layer InceptionV1__InceptionV1__Mixed_3b__concat
I0809 10:14:33.567101 22590 net.cpp:415] InceptionV1__InceptionV1__Mixed_3b__concat <- InceptionV1__InceptionV1__Mixed_3b__Branch_0__Conv2d_0a_1x1__Relu
I0809 10:14:33.567112 22590 net.cpp:415] InceptionV1__InceptionV1__Mixed_3b__concat <- InceptionV1__InceptionV1__Mixed_3b__Branch_1__Conv2d_0b_3x3__Relu
I0809 10:14:33.567122 22590 net.cpp:415] InceptionV1__InceptionV1__Mixed_3b__concat <- InceptionV1__InceptionV1__Mixed_3b__Branch_2__Conv2d_0b_3x3__Relu
I0809 10:14:33.567132 22590 net.cpp:415] InceptionV1__InceptionV1__Mixed_3b__concat <- InceptionV1__InceptionV1__Mixed_3b__Branch_3__Conv2d_0b_1x1__Relu
I0809 10:14:33.567149 22590 net.cpp:389] InceptionV1__InceptionV1__Mixed_3b__concat -> InceptionV1__InceptionV1__Mixed_3b__concat
F0809 10:14:33.567170 22590 concat_layer.cpp:42] Check failed: top_shape[j] == bottom[i]->shape(j) (26 vs. 24) All inputs must have the same shape, except at concat_axis.
*** Check failure stack trace: ***
````
All inceptionv1-v4 met this issue.


Also why change from 2 to 3 as above


How is this in any way more readable?


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084950 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-084950") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


or this?


Done in the next commit.


Hi,
pls help me this problem,

I run this program on March, it's ok;

but now, when I run the program EEGLOGER which I download on this website,

I receive this message:

Message Error recieved from CortexAccess.CortexClient
Recieved: -32041 : EULA has not been accepted by the user follow this url https://www.emotivcloud.com/dbapi/privacy/doc/eula/

pls help me correct it

thank so much

my email: lamquangchuyen@gmail.com


please use meaningful debug messages


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-085410 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-085410") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


测试信息


please either make it private or add a docstring


As the error message suggested, you need to login the URL and accept the EULA again before you can use the software.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


@EnTeQuAk Sorry about that. Like with the previous set of errors, those translations were submitted by an agency that translates files offline and then we uploaded them to Pontoon on their behalf. This process abides the quality checks sadly.

If this and https://github.com/mozilla/addons-server/pull/9093 are rare examples of such brakage, then we should change the process we use with the agency and ask them to submit translations via Pontoon. At least as a first step.

If errors happen more regularly, and you see them coming from different Pontoon users, we should invest in integrating checks (e.g. `dennis`) into Pontoon and simply prevent translations that result in errors from being submitted. We're planning to do that anyways, but we don't even have an ETA yet.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-085641 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-085641") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


static нужно добавить =)


Make that a default to "0.0.0.0", and add some error handling for `inet_pton` and we should be good :)


так фор уже не юзают, есть готовый метод forEach или стримы)


точнее юзают, но в твоем вариант forEach лучше)


why can we ignore the loss if it is infinite?


static


Done.


Build failed with output:
```--- APL SESSION ---
 Running MiServer: 3.1.1616 - (a17ab41a87d39d319bce291e65abf577b5d89c16)
 Dyalog APL/S-64 Version 16.0.33836 Unicode
 For i86_64
 Created: Aug  1 2018 at 01:20:05
 Copyright (c) Dyalog Limited 1982-2018
 /MiServer/miserver.dws saved Mon Jul 23 20:53:27 2018
 SQA failed to initialize
 MiServer for "/MiServer/MS3" started on http://172.17.0.4:8080
 Running in Debug mode (configured by setting <Production> in /Config/Server.

       xml)

 An error occured
  VALUE ERROR
  HandleRequest[112] ConnectDelete conns
                    ∧
   EM       VALUE ERROR
   Message
   #.MiServer.HandleRequest  112
   #.MiServer.RunServer       41
   #.MiServer.RunServer        0
 Enter an expression to debug this problem:
 --- CI-Test Output ---
 Test 1	**PASS**
 Test 2	**PASS**
 Testing site with reverse proxy:
 **FAILED**
 	Root page failed to load under reverse proxy with text: Dyalog MiServer 3 Sample Site------
```


I wanted to do it, but I changed my mind,but i will


javadoc не хватает


@chelmuth please merge to staging.


cast to int shouldn't be required, right?


Good catch @raphinesse!


Typo: explcitily -> explicitly.


Good catch by @raphinesse, will fix


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090131 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090131") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


把里面对应的中文翻译即可，按照原来的格式。


все отлично, сделаем задачку со звездочкой ?
идея такая: давай логи писать в БД, загугли как лучше все это сделать (писать по одному. пачкой (батчинг) и т.п.) как хочешь вообщем.


Здесь можно оставлять пояснения, для чего было сделано то или иное действие


Docker Image 11.8GB


Let's use a buffer pool here, instead.


Build failed with output:
```--- APL SESSION ---
 Running MiServer: 3.1.1618 - (c5737681c807fab561c1d81bdfba7a203218b59d)
 Dyalog APL/S-64 Version 16.0.33836 Unicode
 For i86_64
 Created: Aug  1 2018 at 01:20:05
 Copyright (c) Dyalog Limited 1982-2018
 /MiServer/miserver.dws saved Mon Jul 23 20:53:27 2018
 SQA failed to initialize
 MiServer for "/MiServer/MS3" started on http://172.17.0.4:8080
 Running in Debug mode (configured by setting <Production> in /Config/Server.

       xml)
 --- CI-Test Output ---
 Testing site with reverse proxy:
 **FAILED**
 	Root page failed to load under reverse proxy with text: Dyalog MiServer 3 Sample Site------
```


When / if we make use of this as an online (and not troubleshooting feature) we'll need to go over all this code and make sure that we aren't doing these kind of allocations


Maybe we should add type checking in the method headers? 👍


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090424 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090424") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


@daveirwin1 Thx, I see that 9.6.2.1366 is the latest version.
While it is nice to know that 9.6 is the latest major, some users would use VM Extension to install those agents, so they would need to specify which version to install initially.
Regarding your suggestion, are you sure that the VM extension will update to the latest?

For example, setting a VM extension specifying version "9.5".
Results in the provision of version 9.5.0.1174.
Would the VM extension be updated to 9.6.2.1366 at some point?

From the documentation it is clear that specifying switch -DisableAutoUpgradeMinorVersion prevents the Azure guest agent from automatically updating the extensions to a newer minor version.

But whether or not this switch is specified, will the guest agent extension will be updated to the latest MAJOR version?


I have only Visual Studio 2017 installed and no compilation error


добавь javadoc на класс и методы, чтобы понимать что они делают


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090742 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-090742") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-123677493-1"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'UA-123677493-1');
</script>


Diego es un invasor


deleting


@chelmuth please merge to staging.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091035 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091035") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Very Good!!!


Hello..! My name is Parinita Jain. I'm new to this and just figuring out stuff. Hope i'll be good .


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


a


submit


Perfect!!!


Thanks


This was the PEP-8 formatter. As well as the rest of the formatting comments. Let me revert the commit and do the format closer to what you have.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/5a7e57bc-5410-437d-95a5-d427815f5ebc?env_id=ibm%3Ayp%3Aus-south "sportman-loopback"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/db4be768-68e6-447f-9187-7d1ee9f620cc?env_id=ibm%3Ayp%3Aus-south "sportman-loopback") deployed [sportman-loopback](https://github.com/jims10d/sportman-loopback/releases/tag/deploy-ibm-yp-us-south-jims10d-simpleSpace-20180809-091250 "deploy-ibm-yp-us-south-jims10d-simpleSpace-20180809-091250") to [simpleSpace](https://console.bluemix.net/apps/12384bdb-7ac1-45d2-b63b-7d0a3532c568?env_id=ibm:yp:us-south "ibm:yp:us-south:jims10d:simpleSpace"), including this commit


I'll vote for an empty string


A bit jank, but it works for now


Build version: __`3.4.0-master.26`__ :crossed_fingers: [`master`](https://github.com/ThreadsStyling/tslint/tree/master) on [*CircleCI*](https://circleci.com/gh/ThreadsStyling/tslint/26) :tada:


Generalnie wszystko zależy od Ciebie, używanie `using namespace std;` importuje do kodu całą przestrzeń nazw std, jest to raczej zbyteczny narzut <którego i tak nie zauważysz w małym projekcie> ale ogólnie lepiej jest nie wprowadzać takiego nawyku. Zamiast using namespace możesz śmiało użyć `using std::cout; ` i dalej używać `cout<<"cos";`


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091407 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091407") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Genius code!!!


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091653 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091653") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Since it is now just one rule, we can skip the for loop.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091935 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-091935") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


okay


jest jeszcze ładniejszy sposób :) można użyć std::isdigit, polecam spróbować


just removed build event, remapped paths to requirements. Ignore.


for m_input in secret_word
Here m_input is not serving the purpose of readability
it is better to write
for each_letter in secret_word
or
for letter in secret_word


Finally! 🎉


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-092709 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-092709") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


is exporting this shell variable to be available sub-processes' environment necessary or is this just habit? a local-scope'd variable (like $vip/$port above) would suffice i would imagine


We are going to try to improve this in the future, but unfortunately it's not a simple problem!


@perrutquist you are commenting on an outdated commit on my fork, not on the PR :)

Maybe this paragraph about LLVM should be moved to the DISTRIBUTING.md file, no?


Ah, we *exposed* the bug :rainbow:


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-092923 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-092923") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


@NL66278 I will need a review here. This needs to be ready before Monday, this is supposed to go on sprint4.

What the problem basically here is that when creating a refund this function depends on `claim_line.invoice_line_id` existing.

This can very well not exist and eventually the creation of the refund's invoice lines fails because a required field (account_id) is not filled.

My cure for this is the diff above


updateAccount() is good idea


All the functions beginning with `build`* should be static or not members of matrix4SIMD

Do not define or allow the use of operator* for matrix4SIMD declare `concatenate`* function overloads (like matrix4x3 has)


well structured and organised


Generalnie BUFFER to nie jest dobra nazwa, bardziej się kojarzy z miejscem, gdzie mógłbyś coś wpisać niż z rozmiarem tego bufora, może `BUFFER_SIZE` ?
Poza tym zmienna powinna być `const`, zeby uniknąć przypadkowego nadpisania jej :)


see my note


To właściwie Marcin już wspomniał, lepiej będzie to nazwać inputBuffer lub jakoś podobnie.


much clearer change from acc1 to addingAccount1 etc.


może takie coś: `std::stack<int> stosLiczb;` //chodzi o spację :)


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093203 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093203") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


using this to create your table in your mysql.


db_host = 'localhost'
db_user = 'sec_user2'
db_pass = 'password'
db_name = 'sec2'
con = mdb.connect(db_host, db_user, db_pass, db_name, unix_socket='/tmp/mysql.sock')


these shouldn't be called rotated Vector, but `sub3x3TransformVect`


Generalnie możesz przymyśleć sprawę i trzymać te znaki w `std::set<char>` i sprawdzać, czy istnieje w nim taki znak, moim znadniem byłoby czytelniej


Just a note, but if the above was the case the clients did not have any errors when this was happening

Shouldn't there have been some form of error thrown for it?


for m_input in secret_word
Here m_input is not serving the purpose of readability
it is better to write
for each_letter in secret_word
or
for letter in secret_word


I'm trying to using above functions to insert the table. That will make format flexible.


Thanks!
The idea behind it was that this both rules reduce at similiar cases. On directly for late previous moves and the other indirectly by using a bad stat score which is used for most move sorting and so approximates the late move condition.


changes made have made the code easier to read.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093447 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093447") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


but currently it doesn't work. Got errors :
[*********************100%***********************]  1 of 1 downloaded
Traceback (most recent call last):
  File "pd_price_retrieval.py", line 187, in <module>
    yf_data = pd_get_daily_historic_data_yahoo()
  File "pd_price_retrieval.py", line 74, in pd_get_daily_historic_data_yahoo
    data = web.get_data_yahoo('SPY', start, end)
  File "/anaconda2/lib/python2.7/site-packages/fix_yahoo_finance/__init__.py", line 202, in download
    'Close', 'Adj Close', 'Volume']]
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/frame.py", line 2679, in __getitem__
    return self._getitem_array(key)
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/frame.py", line 2723, in _getitem_array
    indexer = self.loc._convert_to_indexer(key, axis=1)
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/indexing.py", line 1308, in _convert_to_indexer
    obj, kind=self.name)
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/indexes/multi.py", line 1995, in _convert_listlike_indexer
    _, indexer = self.reindex(keyarr, level=level)
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/indexes/multi.py", line 2084, in reindex
    keep_order=False)
  File "/anaconda2/lib/python2.7/site-packages/pandas/core/indexes/base.py", line 3952, in _join_level
    ngroups = 1 + new_lev_labels.max()
  File "/anaconda2/lib/python2.7/site-packages/numpy/core/_methods.py", line 26, in _amax
    return umr_maximum(a, axis, None, out, keepdims)
ValueError: zero-size array to reduction operation maximum which has no identity


Congratulations too.


Jeszcze jedna uwaga co do tej pętli, ona wypisuje jakieś dziwne rzeczy z tego co zauważyłem.
Nie jest potrzebne iterowanie po całym buforze. Jesli mamy `std::string` to możemy iterować po jego rozmiarze.


Well done congratulations.


clearer renaming of variables


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093705 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093705") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


loop to iterate through hashmap set up well


this is template specialization for ResolveAlignment which takes a template AlignedBase

I'm pretty sure that's how its supposed to be and GCC doesn't complain


Congrats!
I just noticed that VSCode silently updated to 0.13.0 so I started to check out the new multi-root workspace stuff now... thank you for this awesome feature ;-)


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093928 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-093928") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Thanks for your soon reply, but I do follow your instruction, but the
problem dont slove,

[image: image.png]
pls help me again,

Regards

Vào Th 5, 9 thg 8, 2018 vào lúc 15:55 Patrick <notifications@github.com>
đã viết:

> As the error message suggested, you need to login the URL and accept the
> EULA again before you can use the software.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/Emotiv/cortex-example/commit/2883431ae4a515e41185926eb613434a63bae564#commitcomment-30016016>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AkJO6RoWYu51T_ZECexuQQge1GhD-oghks5uO_jzgaJpZM4V1S6j>
> .
>

--
Lâm Quang Chuyên
Trường Cao đẳng Công thương TP. Hồ Chí Minh
20, Tăng Nhơn Phú, Phước Long B, Quận 9
Khoa Điện - Điện tử
Mobile: 0908.019.720


this is so I dont have to write the same specialization for `ResolveAlignment<AlignedBase<1> >`,`ResolveAlignment<AlignedBase<2> >`,`ResolveAlignment<AlignedBase<4> >`,`ResolveAlignment<AlignedBase<8> >`, `ResolveAlignment<AlignedBase<16> >` and so on


Build failed with output:
```--- APL SESSION ---
 Running MiServer: 3.1.1619 - (0f729c52491963c5bccfab320279a39b1c63e6f4)
 Dyalog APL/S-64 Version 16.0.33836 Unicode
 For i86_64
 Created: Aug  1 2018 at 01:20:05
 Copyright (c) Dyalog Limited 1982-2018
 /MiServer/miserver.dws saved Mon Jul 23 20:53:27 2018
 SQA failed to initialize
 MiServer for "/MiServer/MS3" started on http://172.17.0.2:8080
 Running in Debug mode (configured by setting <Production> in /Config/Server.

       xml)

 An error occured
  VALUE ERROR
  HandleRequest[112] ConnectDelete conns
                    ∧
   EM       VALUE ERROR
   Message
   #.MiServer.HandleRequest  112
   #.MiServer.RunServer       41
   #.MiServer.RunServer        0
 Enter an expression to debug this problem:
 --- CI-Test Output ---
 Testing site with reverse proxy:
 Test 1/5: **PASS**
 Test 2/5: **FAILED**
 	Root page failed to load under reverse proxy with text: Dyalog MiServer 3 Sample Site
 ------
```


去除多重嵌套  优化代码执行


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


cant you just do a normal multiply with the matrix?

just make a temporary copy of `_in` and and-out the W component to become 0, transform that vector with the matrix using `transformVect`

then AND OR blend the result with _out (take XYZ from result, W from original)

If you changed the function signature to simply `inline vectorSIMDf rotateVect(const vectorSIMDf& _in)` you could simply return the result of the modified transform with simply the W anded out.


Taka notka całościowa. Ogólnie program miał być jeszcze kalkulatorem więc całą tę konwersję można by przenieść do osobnej funkcji. Wiem, że program jest w ostrej fazie developmentu więc można to zrobić w dowolnej chwili, którą uznasz @ernikus za stosowną  :D


remove these utilities


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094222 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094222") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


dont want to encourage slow stores to possibly unaligned addresses


this should be removed, but replaced with an overload for `core::mix` and `core::lerp`


Brother  @arthurmelo88
I did what you write above. Downloaded android-ndk-r16b-windows-x86_64 and using it.
Clean project, Sync project are not helping.
Please is there any other advice?
Thank you very much.


I understand why it is unreachable code *now* (because `myAssert(x is String)` implies that `x is String`; OTOH, `do-while` doesn't contains `break`, so we understand that if we've leaved it, condition is false, i.e. `x == null`; together, we get `NULLABILITY = IMPOSSIBLE`)

What I don't understand is why there were no such diagnostic before. I can look into it myself, but maybe you already know that?


kill this


Binding to 0.0.0.0 by default on a network host is not secure. Please use 127.0.0.1


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094444 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094444") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


well structured and organised (use of comments may be criticised though)


is  `_rotateCenter` also the center of the scaling action?


Accidentally duplicated a large chunk of the code, so I removed the redundant parts


Oh. Sorry, I must have followed the wrong link. Please disregard my comment, since it seems the discussion about LLVM patches is still relevant.


Please respect max 120 line width


@chelmuth: renamed for current staging


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094722 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094722") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Why use magic values instead of the constants?


Apparently you need to create a refund invoice for some claim. Ofcourse you can only refund something, if there was an invoice(line) in the first place. Now you have claim lines that do, and claim lines that do not refer to an invoice line. The solution seems obvious to me (but tell me if I am mistaken): filter the claim lines in line 52 to only include claim lines that refer to an invoice line, and you are done. The rest of the changes is not needed, and anyway wrong to fill the variable that is supposed to contain an invoice line with a claim line.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094943 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-094943") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


> Previously, there was a contract that if it contains some non-trivial type info it also has it in `completeNullabilityInfo`.

Can you please elaborate, which exact change have broken this contract? In the two previous changes I see only a silly bug with `ExpressionTypingServices` (I fail to grasp how it can break such contract) and minor optimization "do not hold immanent nullability in the `completeNullability` map" -- nothing about non-trivial type info affecting nullability info (I certainly miss something here, but I can't understand what)


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f094bbc3-fc3f-402f-b769-7d23d4d5533c?env_id=ibm%3Ayp%3Aus-south "hive764"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/8e16040c-6017-478f-90c4-f224ad9a140e?env_id=ibm%3Ayp%3Aus-south "HIVE764") deployed [hive](https://github.com/WEITAO764/hive/releases/tag/deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-095218 "deploy-ibm-yp-us-south-wtao-deakin.edu.au_1532874841224-dev-20180809-095218") to [dev](https://console.bluemix.net/apps/247b1604-f5f3-41a1-b4ba-3af134758235?env_id=ibm:yp:us-south "ibm:yp:us-south:wtao@deakin.edu.au_1532874841224:dev"), including this commit


Не стоит хранить и свободное и занятое пространство. Лучше хранить общее и занятое, тогда свободное легко вычисляется. и не нужно использовать для этого хеш, достаточно переменных.


Are you sure that the socket needs to be closed after `ssl_handshake` failures? We also had a lot of `unread data in buffer` errors and after the change of https://github.com/pintsized/lua-resty-http/pull/132 they disappeared (so without this change).


d


Thank you! We were waiting for that! :)


@PlagueHO, I really like that change. I hope to contribute to the module soon.


Yes, I do.
For recording a type for `x` as a receiver for `x.length` we use `org.jetbrains.kotlin.resolve.calls.smartcasts.SmartCastManager.Companion#checkAndRecordPossibleCast`
which goes through collected types looking for any type that is a subtype of an expected type (`String` in the case).

Before my changes `getCollectedTypes` was returning `[String, Nothing]` and after it has been changed to `[Nothing, String]`.

Probably, there should be only `Nothing` there, but there's another story