@mauritsvanrees Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.z3cform/9/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/converters.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:14:1: C901 'InlineValidationView.__call__' is too complex (12)
plone/app/z3cform/inline_validation.py:23:12: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:25:16: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:29:26: Q000 Remove bad quotes.
plone/app/z3cform/inline_validation.py:34:9: E265 block comment should start with '# '
plone/app/z3cform/inline_validation.py:41:17: E731 do not assign a lambda expression, use a def
plone/app/z3cform/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/interfaces.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/interfaces.py:6:80: E501 line too long (85 > 79 characters)
plone/app/z3cform/layout.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/layout.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/layout.py:2:1: F401 'FormWrapper' imported but unused
plone/app/z3cform/layout.py:2:1: F401 'wrap_form' imported but unused
plone/app/z3cform/object.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/object.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/templates.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/templates.py:13:1: E731 do not assign a lambda expression, use a def
plone/app/z3cform/utils.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/utils.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/widget.py:7:80: E501 line too long (83 > 79 characters)
plone/app/z3cform/widget.py:144:29: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:292:1: C901 'AjaxSelectWidget._base_args' is too complex (11)
plone/app/z3cform/widget.py:324:9: E303 too many blank lines (2)
plone/app/z3cform/widget.py:344:26: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:344:27: S001 found %s formatter
plone/app/z3cform/widget.py:425:30: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:425:31: S001 found %s formatter
plone/app/z3cform/widget.py:504:58: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:551:35: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:562:42: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:563:44: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:565:34: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:588:28: P101 format string does contain unindexed parameters
plone/app/z3cform/queryselect/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/queryselect/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/queryselect/__init__.py:17:21: Q000 Remove bad quotes.
plone/app/z3cform/queryselect/__init__.py:17:80: E501 line too long (97 > 79 characters)
plone/app/z3cform/queryselect/__init__.py:18:21: Q000 Remove bad quotes.
plone/app/z3cform/wysiwyg/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/__init__.py:2:1: F401 'WysiwygFieldWidget' imported but unused
plone/app/z3cform/wysiwyg/widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/wysiwyg/widget.py:43:17: Q000 Remove bad quotes.
plone/app/z3cform/wysiwyg/widget.py:43:80: E501 line too long (84 > 79 characters)
plone/app/z3cform/wysiwyg/widget.py:44:17: Q000 Remove bad quotes.
plone/app/z3cform/tests/example.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/example.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/example.py:16:16: Q000 Remove bad quotes.
plone/app/z3cform/tests/layer.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/layer.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/layer.py:33:10: Q000 Remove bad quotes.
plone/app/z3cform/tests/test_csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/test_objectsubform.py:34:35: S001 found %s formatter
plone/app/z3cform/tests/test_widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_widget.py:32:80: E501 line too long (126 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/test_widgets.py:549:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:552:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:769:36: D001 found directlyProvides replace it with zope.interface.provider
plone/app/z3cform/tests/test_widgets.py:771:9: D001 found directlyProvides replace it with zope.interface.provider
plone/app/z3cform/tests/test_widgets.py:893:80: E501 line too long (89 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:902:80: E501 line too long (90 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:982:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1020:80: E501 line too long (81 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:1043:80: E501 line too long (82 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:1129:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1144:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1152:39: Q000 Remove bad quotes.
plone/app/z3cform/tests/tests.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/tests.py:0:1: I001 isort found changes, run it on the file
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.z3cform/10/violations
```
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:15:1: C901 'InlineValidationView.__call__' is too complex (12)
plone/app/z3cform/inline_validation.py:24:12: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:26:16: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:30:26: Q000 Remove bad quotes.
plone/app/z3cform/inline_validation.py:42:17: E731 do not assign a lambda expression, use a def
plone/app/z3cform/layout.py:6:5: Q000 Remove bad quotes.
plone/app/z3cform/objectsubform.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/templates.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/utils.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/widget.py:147:29: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:351:26: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:351:27: S001 found %s formatter
plone/app/z3cform/widget.py:463:26: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:542:58: Q000 Remove bad quotes.
plone/app/z3cform/widget.py:591:35: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:602:42: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:603:44: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:605:34: P101 format string does contain unindexed parameters
plone/app/z3cform/widget.py:628:28: P101 format string does contain unindexed parameters
plone/app/z3cform/tests/example.py:22:16: Q000 Remove bad quotes.
plone/app/z3cform/tests/layer.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/layer.py:33:10: Q000 Remove bad quotes.
plone/app/z3cform/tests/test_objectsubform.py:37:35: S001 found %s formatter
plone/app/z3cform/tests/test_widgets.py:548:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:551:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:768:36: D001 found directlyProvides replace it with zope.interface.provider
plone/app/z3cform/tests/test_widgets.py:770:9: D001 found directlyProvides replace it with zope.interface.provider
plone/app/z3cform/tests/test_widgets.py:990:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1029:80: E501 line too long (81 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:1052:80: E501 line too long (82 > 79 characters)
plone/app/z3cform/tests/test_widgets.py:1138:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1153:14: D001 found assertEquals replace it with assertEqual
plone/app/z3cform/tests/test_widgets.py:1161:39: Q000 Remove bad quotes.
plone/app/z3cform/wysiwyg/__init__.py:3:1: F401 'WysiwygFieldWidget' imported but unused
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


I'll try to do it in this Saturday.
On Tue, 8 Mar 2016 at 19:22 James Turnbull <notifications@github.com> wrote:

> Sure! A PR would be great.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/riemann/riemann-tools/commit/575662d94d08bbeaac184be83ae487a29fa38789#commitcomment-16567454>
> .
>


@tisto Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.relationfield/1/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/behavior.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:25:23: E128 continuation line under-indented for visual indent
plone/app/relationfield/behavior.py:29:80: E501 line too long (90 > 79 characters)
plone/app/relationfield/demo.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/demo.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/demo.py:18:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:19:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:22: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:33: Q000 Remove bad quotes.
plone/app/relationfield/demo.py:22:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:23:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/event.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/event.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/event.py:10:1: C901 'extract_relations' is too complex (13)
plone/app/relationfield/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/marshaler.py:4:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/marshaler.py:8:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:10:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:15:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:16:80: E501 line too long (92 > 79 characters)
plone/app/relationfield/monkey.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/path.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:14:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:16:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:27:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:32:1: W293 blank line contains whitespace
plone/app/relationfield/setuphandlers.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/setuphandlers.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:8:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:12:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:20:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:25:12: Q000 Remove bad quotes.
plone/app/relationfield/source.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/source.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/source.py:10:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/source.py:35:42: S001 found %s formatter
plone/app/relationfield/source.py:44:21: W292 no newline at end of file
plone/app/relationfield/tests.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/tests.py:5:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:6:1: W293 blank line contains whitespace
plone/app/relationfield/tests.py:11:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:12:1: W293 blank line contains whitespace
plone/app/relationfield/tests.py:13:80: E501 line too long (83 > 79 characters)
plone/app/relationfield/tests.py:15:1: W293 blank line contains whitespace
plone/app/relationfield/widget.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/widget.py:15:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/widget.py:137:1: W391 blank line at end of file
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


@davisagli Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.z3cform/4/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:14:1: C901 'InlineValidationView.__call__' is too complex (12)
plone/app/z3cform/inline_validation.py:21:12: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:23:16: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:27:26: Q000 Remove bad quotes.
plone/app/z3cform/inline_validation.py:32:9: E265 block comment should start with '# '
plone/app/z3cform/inline_validation.py:39:17: E731 do not assign a lambda expression, use a def
plone/app/z3cform/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/layout.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/layout.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/layout.py:2:1: F401 'FormWrapper' imported but unused
plone/app/z3cform/layout.py:2:1: F401 'wrap_form' imported but unused
plone/app/z3cform/object.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/object.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/templates.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/templates.py:13:1: E731 do not assign a lambda expression, use a def
plone/app/z3cform/utils.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/utils.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/queryselect/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/queryselect/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/wysiwyg/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/__init__.py:2:1: F401 'WysiwygFieldWidget' imported but unused
plone/app/z3cform/wysiwyg/widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/example.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/example.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/example.py:16:16: Q000 Remove bad quotes.
plone/app/z3cform/tests/layer.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/layer.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/layer.py:34:10: Q000 Remove bad quotes.
plone/app/z3cform/tests/layer.py:38:10: Q000 Remove bad quotes.
plone/app/z3cform/tests/test_csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/test_objectsubform.py:34:35: S001 found %s formatter
plone/app/z3cform/tests/test_widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_widget.py:32:80: E501 line too long (126 > 79 characters)
plone/app/z3cform/tests/tests.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/tests.py:53:35: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


@esteele Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.z3cform/5/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/csrf.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/inline_validation.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/inline_validation.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/inline_validation.py:15:1: C901 'InlineValidationView.__call__' is too complex (12)
plone/app/z3cform/inline_validation.py:22:12: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:24:16: P002 found "hasattr", consider replacing it
plone/app/z3cform/inline_validation.py:27:1: W293 blank line contains whitespace
plone/app/z3cform/inline_validation.py:28:26: Q000 Remove bad quotes.
plone/app/z3cform/inline_validation.py:33:9: E265 block comment should start with '# '
plone/app/z3cform/inline_validation.py:38:32: F841 local variable 'TypeError' is assigned to but never used
plone/app/z3cform/inline_validation.py:40:17: E731 do not assign a lambda expression, use a def
plone/app/z3cform/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/interfaces.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/interfaces.py:3:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/layout.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/layout.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/layout.py:2:1: F401 'FormWrapper' imported but unused
plone/app/z3cform/layout.py:2:1: F401 'wrap_form' imported but unused
plone/app/z3cform/object.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/object.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/templates.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/templates.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/templates.py:16:1: E731 do not assign a lambda expression, use a def
plone/app/z3cform/templates.py:16:80: E501 line too long (90 > 79 characters)
plone/app/z3cform/utils.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/utils.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/utils.py:41:13: E129 visually indented line with same indent as next logical line
plone/app/z3cform/utils.py:41:13: W503 line break before binary operator
plone/app/z3cform/widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/widget.py:13:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/widget.py:18:1: E303 too many blank lines (3)
plone/app/z3cform/widget.py:21:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/widget.py:24:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/widget.py:29:1: E303 too many blank lines (3)
plone/app/z3cform/widget.py:32:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/widget.py:35:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/widget.py:38:1: W391 blank line at end of file
plone/app/z3cform/queryselect/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/queryselect/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/queryselect/__init__.py:11:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/queryselect/__init__.py:19:1: W293 blank line contains whitespace
plone/app/z3cform/queryselect/__init__.py:21:1: W293 blank line contains whitespace
plone/app/z3cform/queryselect/__init__.py:28:1: W293 blank line contains whitespace
plone/app/z3cform/queryselect/__init__.py:32:27: E701 multiple statements on one line (colon)
plone/app/z3cform/queryselect/__init__.py:38:27: E701 multiple statements on one line (colon)
plone/app/z3cform/queryselect/__init__.py:40:1: W293 blank line contains whitespace
plone/app/z3cform/queryselect/__init__.py:46:80: E501 line too long (83 > 79 characters)
plone/app/z3cform/queryselect/__init__.py:48:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/queryselect/__init__.py:54:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/wysiwyg/__init__.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/wysiwyg/__init__.py:3:1: F401 'WysiwygFieldWidget' imported but unused
plone/app/z3cform/wysiwyg/__init__.py:4:1: W391 blank line at end of file
plone/app/z3cform/wysiwyg/widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/wysiwyg/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/wysiwyg/widget.py:10:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/wysiwyg/widget.py:13:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/wysiwyg/widget.py:15:1: W293 blank line contains whitespace
plone/app/z3cform/wysiwyg/widget.py:31:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/tests/example.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/example.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/example.py:16:16: Q000 Remove bad quotes.
plone/app/z3cform/tests/example.py:64:1: E303 too many blank lines (3)
plone/app/z3cform/tests/layer.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/layer.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/layer.py:77:10: Q000 Remove bad quotes.
plone/app/z3cform/tests/test_csrf.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_objectsubform.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/test_objectsubform.py:34:35: S001 found %s formatter
plone/app/z3cform/tests/test_objectsubform.py:115:80: E501 line too long (81 > 79 characters)
plone/app/z3cform/tests/test_widget.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/test_widget.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/test_widget.py:11:1: E302 expected 2 blank lines, found 1
plone/app/z3cform/tests/test_widget.py:31:80: E501 line too long (85 > 79 characters)
plone/app/z3cform/tests/test_widget.py:32:80: E501 line too long (126 > 79 characters)
plone/app/z3cform/tests/test_widget.py:45:7: W292 no newline at end of file
plone/app/z3cform/tests/tests.py:0:1: C101 Coding magic comment not found
plone/app/z3cform/tests/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/z3cform/tests/tests.py:71:48: Q000 Remove bad quotes.
plone/app/z3cform/tests/tests.py:103:3: E122 continuation line missing indentation or outdented
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Any way this could use ImmutableTypeToInstanceMap? Eg., it could be a map from TypeToken<Evaluator<T>> to Evaluator<T>. Then the unsafe casts are hidden within that class.


isn't this the same with if else flipped?


Comment on why this is using rawtypes and why it is safe?


Ok. Now I'm agree with you. It's not whole the commit, only the radio part, etc. In this case you can back the cpuset part from this commit.


lines 110 and 111 can be collapsed


Ah, out of date comment.


This seems to be exccessively newlining. For instance, the new BoundedWindow() { ... } can fit on the same line. May also be worth either creating an IntervalWindow, or creating a TestBoundedWindow(...) that just takes a timestamp, rather than using anonymous classes here?


At least a single phrase/sentence telling me what the task does. I find this incredibly useful when I'm rooting around in the stack, to give me context for what I'm looking at. I think its a significant deficiency in the stack that having no module docstrings (even very short ones) is common practice.


Nice.:) am in 422 if u guys are in yet

Sent from my Windows Phone
________________________________
From: RichardJActon<mailto:notifications@github.com>
Sent: 08/03/2016 17:15
To: RichardJActon/Biocomp2Project<mailto:Biocomp2Project@noreply.github.com>
Cc: GabrieleNocchi<mailto:g.nocchi@hotmail.com>
Subject: Re: [Biocomp2Project] Removed another unused line. (e0a99ef)

Yes I think you have got the restriction site thing.
On 8 Mar 2016 3:01 pm, "GabrieleNocchi" <notifications@github.com> wrote:

> p.s. I mite have just understood what you mean with the restriciton site
> reverse transcription. Basically if a motif is for example 5-attcg-3 i need
> to search for that motif and also for its complementary, which is
> 5-cgaat-3, still in the DNA same strand right?
>
> Date: Tue, 8 Mar 2016 03:57:32 -0800
> From: notifications@github.com
> To: Biocomp2Project@noreply.github.com
> CC: g.nocchi@hotmail.com
> Subject: Re: [Biocomp2Project] Removed another unused line. (e0a99ef)
>
> Shouldn't this return an array of start positions and an array of end
> positions in the gene sequence to be given to @DolapoA 's layer where he
> adds the HTML?
>
>
> —
> Reply to this email directly or view it on GitHub.
>
>
>
>
>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/RichardJActon/Biocomp2Project/commit/e0a99efcbc78bbd8af4ff1552ff23972e415b579#commitcomment-16563602>
> .
>

---
Reply to this email directly or view it on GitHub:
https://github.com/RichardJActon/Biocomp2Project/commit/e0a99efcbc78bbd8af4ff1552ff23972e415b579#commitcomment-16567298


Dla mnie OK CR:+2


Is it functional yet? Can't wait to try! :smiley:


This is to just preserve the structure for future use?
Wonder what things that question will bring up.


Capital W


definitely not the best name/signature for a function ever, I won't fight it too hard as it is a "private" function.


Pulling it now.  I will test (again) this afternoon.


thanks


Forgot, you also need to add libcircle to your library path:
```sh
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/bhagwan/ExMatEx/CoEVP/serverize/circle/lib
```
/cc @louisvernon


same here


Yes, heart-alive sends a response, but it's kind of useless. It also won't send any state at all, which leaves me with the same problem. They really did a incredible bad job, but I guess it was never meant to be public..


Not quite, got all of the basic down, working on displaying the number of mines adjacent on each tile, then I will be practically done!


That is a question I have. Would we calculate the credits? I was thinking in delete it.


Q1. Can we move the package to something starting with com.moz.rogeros...?
On Mar 8, 2016 8:51 AM, "Vinit" <notifications@github.com> wrote:

> @jordmoz <https://github.com/jordmoz> Please review my primitive code in
> the most primitive construct that I know in Java, I am sure things can be
> done in much nicer, beautiful way but unfortunately I am not up to date on
> those.
>
> @ankanm <https://github.com/ankanm> @amitbose327
> <https://github.com/amitbose327> @04msambit <https://github.com/04msambit>
> Please review it and ask as many questions as possible.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vmahedia/marathon-example-plugins/commit/289abf558be4af4e0579cf432479aed0d44d2991#commitcomment-16566712>
> .
>


Feel free to test out my code though :P


Actually the z-score is calculated per sample individually. So for each sample we compose the normal distribution of their targets normalized coverages, we substract the mean and divide them by the stddev.


So is the right idea but in the wrong dimension.


相信是笔误，结尾写了两个分号，两个分号间是空语句，延迟的时间可以忽略


Suggestions?


LaTeXDummy (Myoldmopar) - 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.svg)


Domo arigato


Criar uma API (JSON+REST) que permita armazenar e consultar um catálogo de endereços (logradouros). Seu serviço deverá suportar cadastrar, consultar, alterar e excluir endereços. Para o procedimento de cadastro de logradouro deve ser informado somente o CEP do endereço e deve ser consultado no serviço web https://correiosapi.apphb.com/o endereço completo (logradouro, bairro, cidade, etc) e salvo em um banco de dados ou banco em memória.

Esclarecimentos:
1) Criar tanto uma interface web UI como uma API. Ambas com suporte a leitura, criação, alteração e remoção.

Obrigatório adotar Java como linguagem principal.

Para a web UI dê preferência a frameworks Model-View-Whatever e Single Page Application.

É obrigatório que o README.md do projeto contenha as instruções de como o projeto deve ser compilado, executado.

Desenvolver um script que realiza esse procedimento.


Oops, for got one more thing. `lctest` is not built by `Makefile`. Just compile by hand:
```sh
mpic++ -std=c++11 -g -O3 lctest.cc -o lctest -I ../serverize/circle/include -L ../serverize/circle/lib -lcircle
```

/cc @louisvernon


lambda funktionen sind so schön :heart_eyes:

für primzahlen geht das auch super
```python
factors  = lambda n: [x for x in range(1,n+1) if not n%x]
is_prime = lambda n: len(factors(n))==2
```


is this something you agreed upon? to my understanding the place to manage the log file configuration is probably chef, which deals with config files more gracefully than with database rows

cc/ @santisaez


New use case diagram and corresponding use case documents


Hey @MaxGhenis long time no see!

I was reading the source code of the Advanced R book and I saw that you were responsible for the last edit. Random!

How are you doing these days? Still playing phonez on plastic reeds? These days I'm playing bary and clarinet, but no plastic reeds, unfortunately.


PS: not big deal as long as we keep a low number of servers, but this can turn to be a bigger problem in the future. contained in a class/method FTM, which is good


Damn PHP 5.3! :stuck_out_tongue_winking_eye:


This is the format:

https://github.com/CartoDB/cartodb-platform/pull/1644#issuecomment-190180493

I agree with adding a differentiation field, that is why the service type is different. For API geocoder_here, for editor is heremaps. I could add other field like 'api'


MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT
======================================================
1. For what objective is the program MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT.exe?? .
   The program is used for automatic and very easy install MYSQL database
   and do its configuration automatically so that the user does not have to choose
   any parameter from the menu or need read help . Only must approve a few (3-4) button's  type
   NEXT. All parameters are stored in the config file setup.ini
   what can be edit and change by  programmer to adapt it , according to the needs .

2. The author of this project.
   The author of this project MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT
   is a Polish radio amateur SP9AUV. This callsign completely identifies a person
   in the whole world, as there are no other people in the worldwide of that
   callsign in Ham Radio.

3. The terms of the license.
   The project and the program is completely free without any fees. With the use of the
   entire project should, however, keep the features of copyright, ie callsign SP9AUV
   when displaying on the screen. When separate use  of the procedures program
   behavior callsign  SP9AUV is not necessary.

4. Objective of the development of this project    MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT.
   Initially, to the radio amateurs I provided all the files that are needed for installation
   MYSQL database and its configuration, along with a detailed description of what needs
   to be run consecutively and how to configure the database. However, the majority of
   people could not do this installation, or simply not want to read the extensive help.
   It became clear to me that this mechanism is too complicated.
   True, Microsoft provides software installation for  more
   components for MYSQL. However,  in this method is also too many elements
   to decide and choose to end the successful installation of MySQL.
   So I decided to develop a program
MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT,
   which automatically installs itself all the necessary components, without selecting
   any parameter from menu and also configure itself MYSQL ,  for the needs of a specific
   program, in my case AWARD_SECRETARY. If it will possible the steps installation are hidden from
   user. The program operatesin this way ,  that basically need is a couple of mouse clicks and it is

5. Files  accompanying the project:
   5.1. In the catalog MYSQL_INSTAL_WITH_SOURCE are placed following directories and files
          MYSQL_INSTAL and in directories
			V_5.1 files to install MySQL version 5.1
			V_5.5 files to install MySQL 5.5
			file MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT.exe
				- the same program to perform automatic installation and configuration of
                                  MySQL database MYSQL file of
                                   SHOW_CHM_HELP_IN_64BIT_WINDOWS.exe - Auxiliary program to
                                     remove the hassle of display help files .chm
			file Install_MYSQL_dla_informatykow_PL.chm - help for a Polish - extended only
                            for developer
			file Install_MYSQL_PL.chm - help Polish, reduced for non-technical users
			file Install_MYSQL_for_computer_science_EN.chm - help English - extended only for developer
			file Install_MYSQL_EN.chm - help English - shortened for non-technical users
			L_1045.dll files and L_1033.dll - dll files for the language English or  Polish
            configuration file setup.ini. This is a very important file which determines what components
               are to be installed. In it they are also stored configuration parameters needed for proper work then
               the program utility. It is possible to install and configure up to 6 six
               MYSQL components. At the present time , the configuration file may install MySQL : in version 5.1 or 5.5.
               Configuration file setup.ini is the file same commenting. Programmer after looking
               this file , will be knows what data must  change , to accommodate the setup.ini to your database system MySQL.
         SOURCE -  source in a Delphi for program  MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT

6. Using external programs to install and configure the database automatically.
   At this moment this program is used to automatic installation database:
		- Msiexec.exe - basic program for component installation MYSQL, he has options:
			-i install
			-q quite perform operations quietly, ie not-display
			-l create a log of operations was was do
		- MySQLInstanceConfig.exe - a collection is created only after the successful installation and MYSQL
		  It is used to configure the database
			- Setting up an account and password for the main root
			- Connection configuration for ODBC Driver
			- No port is usually 3306
			- Name server as domain = localhost
			- Name =           	Your choice
			- Pasword user = 	Your choice
			- DATABAE NAME = 	Your choice
		- Mysql.exe - a file is created after successful installation MYSQL
				and is used to create account and password for user for the application program, and
				setting privileges for that user
		- Net.exe - used to run networks to work with MYSQL

7. Use the program to automatic and very easy install MYSQL database.
   After designing MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT
   It became clear to me that the program can be used for very easy installation database
   MYSQL also by other than amateur radio users.
   Also, by "Mrs. Zosia from the accounting department what does not know anything
   about science."   The programmer must only edit file setup.ini
   the specific needs for  another company and another user.
   In this way there is no need to travel to another company, and the
   user group of our finanse applications can be extended to users around the world .
   The program works in English or Polish, depending on what is a Windows environment.
   If the parameters in setup.ini not enough, the programmer can make changes
   in the program MYSQL_INSTALL_AUTOMATIC_ALL_COMPONENT_AND_CONFIGURE_IT
   i.e. in a sources in Delphi .

8. Where can you get the project?
      http://sp9auv.com/EN/index.html?instalation_database_mysql_for_computer_science.php
    This is the full version with sources in Delphi
   	You can also have a look at the website discussion forum
			http://sp9auv.com/fudforum/


Bryan, the 3 changes above are identical. On top of that the block of code looks very similar. I would consider some refactoring with some abstract class handling common cases.


@santisaez has a row from the log file to check it it works fine with the aggregation process


98行有 一个小笔误


The linked list operation is good. But the space complexity in O(n) because you create another linked list while sorting. Actually the insertion sort can have O(1) space if you insert every node onto the L node (the dummy node to track head). There is no need to allocate a ListNode every time.

Also in your main function, remember to delete everything you newed otherwise there will be memory leak. You can try declare variable like this instead of new if you don't want to manage the memory by yourself.

`ListNode n1(6), n2(5), n3(3);`
`n1->next = n2;`
`n2->next = n3;``


do-while are not considered perl best practices.
They work entirely different than in other c based langauges.


@mauritsvanrees Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.relationfield/4/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/behavior.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:25:23: E128 continuation line under-indented for visual indent
plone/app/relationfield/behavior.py:29:80: E501 line too long (90 > 79 characters)
plone/app/relationfield/demo.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/demo.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/demo.py:18:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:19:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:22: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:33: Q000 Remove bad quotes.
plone/app/relationfield/demo.py:22:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:23:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/event.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/event.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/event.py:10:1: C901 'extract_relations' is too complex (13)
plone/app/relationfield/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/marshaler.py:4:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/marshaler.py:8:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:10:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:15:1: W293 blank line contains whitespace
plone/app/relationfield/marshaler.py:16:80: E501 line too long (92 > 79 characters)
plone/app/relationfield/monkey.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/path.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:14:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:16:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:27:1: W293 blank line contains whitespace
plone/app/relationfield/path.py:32:1: W293 blank line contains whitespace
plone/app/relationfield/setuphandlers.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/setuphandlers.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:8:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:12:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:20:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:25:12: Q000 Remove bad quotes.
plone/app/relationfield/source.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/source.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/source.py:10:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/source.py:35:42: S001 found %s formatter
plone/app/relationfield/source.py:44:21: W292 no newline at end of file
plone/app/relationfield/tests.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/tests.py:5:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:6:1: W293 blank line contains whitespace
plone/app/relationfield/tests.py:11:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:12:1: W293 blank line contains whitespace
plone/app/relationfield/tests.py:13:80: E501 line too long (83 > 79 characters)
plone/app/relationfield/tests.py:15:1: W293 blank line contains whitespace
plone/app/relationfield/widget.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/widget.py:15:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/widget.py:137:1: W391 blank line at end of file
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Nice! I think you should merge cpufreq_blu_active to your repo. It's very fast and smooth governor, maybe, the best for UI experience


rebased on master and merged some detail adjustments into the original commit


I don't think we should special-case ``DisallowedHost``. There's nothing particularly magic about that exception that would warrant that I'm afraid.


Preserved it in 215cd39c22d706c66d2cdcbfeb23c8919bc652f2.


This configuration is setted by chef using the geocoder-server cookbooj


Was just comparing to OCI. This should be in `Windows` rather `Spec` as `Spec` is the platform independent configuration.


I've built the runner against Beam (locally) with minimal code change. No need to change HadoopIO just set the appropriate coder when reading input using HadoopIO.
And I've used your "PLACEHOLDER" - Thanks!
Check it out: https://github.com/amitsela/spark-dataflow/commit/f8cf34db95bb2b581639aeec84e9cceabde4dd0a


@SergeyTravin
util is excluded in src/org/pentaho/agilebi/AgileBi.gwt.xml; this conflict seems to be the cause of recent failures in data-access-plugin and pentaho-enunciate


Ejecut `$ django-admin startproject mysite`


Can you explain what could go wrong in our current case as it does seem to be a perfect candidate for a do while


When declaring pointer data or a function that returns a pointer type, the
preferred use of '*' is adjacent to the data name or function name and not
adjacent to the type name.

http://lxr.free-electrons.com/source/Documentation/CodingStyle#L205


Not sure if it's worth it, but a couple suggestions for this:

* If you believe asString might be used in the future in the actual collections code, maybe a name like toString_() is less likely to have a conflict?

* Alternatively, consider calling a method that returns dynamic and hide the warning that way. For example, you might be able to call noSuchMethod by hand like this:
```dart
  toString() => noSuchMethod(TO_STRING_INVOCATION);
```


This change is [breaking the CI](https://ci.apache.org/waterfall?category=cordova&reload=15). Looks like there was a syntax error (missing comma), but I don't see the same error in #404


Minor: I think the indentation has gone wonky here.


In my opinion, we should expose some methods from handlers but not all of them.

As a ddf user (possibly a data scientist), function like getSummary(), getRandomSample(), etc. are quite often used. It's better to provide these interfaces in class for better usability. But functions such as transformPython(), transformMapReduceNative(), etc., are less often used and they can be hidden under the handlers.

But it's true the maintenance burden will remain.

/cc @zkidkid @sameerp @nhanitvn @mbbui


Эксепшенов у нас уже много всяких, как то локализовывать ошибки потом можно?)


Not needed


`Meteor.server.publish_handlers["Product"]()` is reporting that `this.stop()` does not exist and is throwing an error in the product tests. this.stop stops the publication from running, while this.ready should be used when we are done, but returning a cursor also sets this.ready().   The more I've been looking at how we've used this.stop, the more I think that this.stop is probably only appropriate when using observeChanges in the publication.


This shouldn't on branch laravel-5 because it uses L5.1 BladeCompiler. Method directive() does not exist on L5 and this gives this error

`Error Output: PHP Fatal error:  Call to undefined methodIlluminate\View\Compilers\BladeCompiler::directive() in /home/vagrant/Code/CLH/cpmapi/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 213`

Check it out here:
https://github.com/illuminate/view/blob/5.0/Compilers/BladeCompiler.php


You should just pass on the return value here - otherwise if someone comes along later and changes to_digit() so it can return OUT_OF_MEMORY or whatever it will get masked.

Normally we use something like
ret = to_digit(highnibble, &high_dec_nibble)
if (ret)
  return ret;


lgtm


use $self-> key_prefix


Done.


Yeah, but svgo for now works in node >= 0.10 and not everyone upgraded their infrastructure to latest versions of node. And array here is flattening because of grouping in [lib/svgo/config.js](/svg/svgo/blob/master/lib/svgo/config.js#L193).


Once you understand his notation for registers and the swapping charts, I find his docs much easier to use.


I only gave it a little bit of thought...but basically I figure this option will get used underneath Ansible wrappers and the like, people won't type it.


No code at all in this commit? just empty files with copyrights?


extra line


@spacediver I think @juacompe's point is that you didn't *close* the comment. :-) The comment is extending all the way until the next `*/}}`, so the template parser thinks you have an `else` in `define`'s context.


yep, see my note above. we do request and post


@mauritsvanrees Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.relationfield/5/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/behavior.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:25:23: E128 continuation line under-indented for visual indent
plone/app/relationfield/behavior.py:29:80: E501 line too long (90 > 79 characters)
plone/app/relationfield/demo.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/demo.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/demo.py:18:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:19:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:22: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:33: Q000 Remove bad quotes.
plone/app/relationfield/demo.py:22:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:23:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/event.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/event.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/event.py:10:1: C901 'extract_relations' is too complex (13)
plone/app/relationfield/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/marshaler.py:4:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/marshaler.py:16:80: E501 line too long (92 > 79 characters)
plone/app/relationfield/monkey.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/path.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/setuphandlers.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:8:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:12:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:20:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:25:12: Q000 Remove bad quotes.
plone/app/relationfield/source.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/source.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/source.py:10:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/source.py:35:42: S001 found %s formatter
plone/app/relationfield/source.py:44:21: W292 no newline at end of file
plone/app/relationfield/tests.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/tests.py:5:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:11:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:13:80: E501 line too long (83 > 79 characters)
plone/app/relationfield/widget.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/widget.py:15:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/widget.py:137:1: W391 blank line at end of file
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Good catch, thanks


This method should have `IProject` as a parameter and call `project.getFile("build.gradle").exists`


Thanks for sharing it.
I downloaded it and running it but background is not coming as black so things not visible.


This is not a valid object field definition!
this will break the code.


@Pafcholini I'm going to do a new build with just the cpuset portion of the commit enabled and see how it builds.  If so, I'll commit it here.


I think there's a space missing here and the line below


Create app -> `$ python manage.py startapp polls`


Done ! :P

Thank you for this plugin, it's lightweight and does just exactly what it's intended to !


@mauritsvanrees Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.relationfield/6/violations
```
plone/__init__.py:0:1: C101 Coding magic comment not found
plone/app/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/__init__.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/behavior.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/behavior.py:25:23: E128 continuation line under-indented for visual indent
plone/app/relationfield/behavior.py:29:80: E501 line too long (90 > 79 characters)
plone/app/relationfield/demo.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/demo.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/demo.py:18:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:19:28: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:22: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:20:33: Q000 Remove bad quotes.
plone/app/relationfield/demo.py:22:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/demo.py:23:24: E128 continuation line under-indented for visual indent
plone/app/relationfield/event.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/event.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/event.py:10:1: C901 'extract_relations' is too complex (13)
plone/app/relationfield/interfaces.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/marshaler.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/marshaler.py:4:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/marshaler.py:16:80: E501 line too long (92 > 79 characters)
plone/app/relationfield/monkey.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/path.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/path.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/setuphandlers.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/setuphandlers.py:8:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:12:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:20:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/setuphandlers.py:25:12: Q000 Remove bad quotes.
plone/app/relationfield/source.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/source.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/source.py:10:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/source.py:35:42: S001 found %s formatter
plone/app/relationfield/source.py:44:21: W292 no newline at end of file
plone/app/relationfield/tests.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/tests.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/tests.py:5:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:11:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/tests.py:13:80: E501 line too long (83 > 79 characters)
plone/app/relationfield/widget.py:0:1: C101 Coding magic comment not found
plone/app/relationfield/widget.py:0:1: I001 isort found changes, run it on the file
plone/app/relationfield/widget.py:15:1: E302 expected 2 blank lines, found 1
plone/app/relationfield/widget.py:137:1: W391 blank line at end of file
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


I like the idea of having a template function here, but if `T` is any type bigger than `int` and `__builtin_ffs` exists, then you'll have truncation I think.

Also, signed vs unsigned might expose interesting behavior here.


is this for the in-hand scanner?


Good idea


Or even, use the HexLib for your own project


@CMRemix At least for trltespr, there are folks on your XDA thread saying that GPS isn't working (only able to locate with WiFi/cellular).


"int" really took me very long time to figure out


A space? Where?
You mean an underscore? Like `XPCC__AVR_MAIN_HPP`?

We try not to do that anymore, since double underscores are reserved in the C++ standard for compiler and std lib.


Error message should be something meaningful like "Caught error during gradle execution." This makes it easier to grasp when the error occurred when reading the log.


Oops?


I like the whole `findMsg` thing.


You can probably hack around and use `__builtin_ffsl`. Or you could just have a loop and run builtin_ffs on each `int` of that bigger type `T`.

Have fun :laughing:


Grymt :)


This commit broken this ppa https://launchpad.net/~gwendal-lebihan-dev/+archive/ubuntu/cinnamon-nightly because it's impossible, almost to me, to find the gir1.2-cvc-1.0 lib over the entire internet


Russian language ini for IFME v6.1


1) model update (pdo binds added) !!!


no idea why but k


Think I added ${CMAKE_SOURCE_DIR} to make it easier to write the test/CMakeLists.txt here. But the library, as you suggest, would make it faster to compile the tests I think. By the way, what was your reason for adding add_library? Not to install it I guess, or?


Hi mate. This is not the proper commit to ask you about this but I want to ask you if ambient display (doze) works fine on this device? i mean in my Note 4 (trlte) doesn't work property. When I wake up the device the brightness it's at low brightness and doesn't up to normal state I have to lock and unlock again the device to fix the brightness.  i tried to logcat the issue but not luck for now.


Erm.... What exactly is this? Did you write this yourself? I didn't even know you knew what "Tort" means...


I don't know, it seems to happen on especially long lines where it's wrapping the content across multiple lines and it decides to break the line at `:` putting the checksum value on it's own line. So maybe it's related to that, indicating that it has another line.


Yeah, I finally found an example that includes depth that breaks this.

```swift
struct S<T> {
  struct R<U> {
    let x: T
    let y: U
  }
}

class Q<A, B> {
  let sr: S<A>.R<B>
}

let q = Q(sr: S.R(x: 1, y: true)) // q : Q<Int, Bool>
```

For `q`, I have a metadata with:
``````
q: Q<Int, Bool>
0: _TMSi
1: _TMSb
``````

Fetching the field typerefs for `q`'s `sr` field:

```
(bound-generic S
  (generic-type-parameter depth=0 index=0))
(bound-generic R
  (generic-type-parameter depth=1 index=0))
```

`q`'s substitution map `sub_q` starts out with:
```
(0, 0) -> Int
(0, 1) -> Bool
```

Following up to the parent, `S` is substituted:
```
(bound-generic S
  (nominal Int))  // Gotten from sub_q[(0, 0)]
(bound-generic R
  (generic-type-parameter depth=1 index=0))
```

Then, when we get back down to `R`, we need a substitution map that has a `(1, 0) -> Bool` but I don't see where I could've mapped `q`'s `(0, 1) -> Bool` to a `(1, 0) -> Bool`. Am I not serializing enough information?


1) database update
2) product item image list
3) abstract record improve
4) model improve


Still a lot of scaling problems.
Coord system is in bp space, thus, after navs and zooms, the coord space is transformed and individual objects don't need to be managed.  However, handling the coordinate space transform method is proving to be challenging.  It is necessary to scale the object properly to maintain approx dimensions in every zoom level driven by a scaling function.  This may be the Achilles heel of maintaining bp coord mapping.
I also noted base coordinate changes during horiz drag nav.  At higher zoom levels, sometimes the objects are not alligned to the coordinate system properly.  This is probably a computational problem.
![ice_screenshot_20160308-093125](https://cloud.githubusercontent.com/assets/10053377/13610035/9b54af74-e510-11e5-8c5b-a8772662ba3d.png)


Maybe value type here instead?


It seems odd that we have `options`, but aren't using the `UseHtml` flag in this case (but we do in the case below).


This now maps to current folder structure in alphabetical order. Added `js/` which was not documented. Not sure if the explanation is correct. Let me know and I can update.


It was moved to cinnamon-desktop: https://github.com/linuxmint/cinnamon-desktop/commit/65e05c22eddeba8ad14a32847f28a7548d8e91c6

You need to wait for cinnamon-desktop to build anew, then that package will be available.


I'll remove the unused variable in the next pull request
Is there a better way, a library, or a cleaner best practice, to handle these bit manipulations?
I'd like to keep the interface, so it mirrors the description in the product brief, but I hate that I have to reinvent these utility functions :)


`return self.base_dtype in (complex64, complex128)`


I think `jsartoolkit` is implied. Also the repository is now named `jsartoolkit5` so either we remove them or change to that.


Corrige a Issue #59


Looks like a pre-existing typo: "ellapsed" vs "elapsed".


move this to the validationMessage.properties too


    if self.is_quantized or self.base_dtype in (bool, string, complex64, complex128):

Possibly wrapped if that doesn't fit in 80 cols.


Should we also set_token_validation on store->auth_method ? It will be needed in get_policy()


Now the config gets reset and that way also McMMO breaks... damn


Same `in` trick as above.


We do that in OpenBSD to reduce reliance on `sys/param.h`. I guess it doesn't matter much here because htop will definitely always include `sys/param.h`. Still, it's nice to keep stuff from depending on miscellaneous helper macros that were meant to be internal to the kernel.


This would be useful for me as well.


Migrate apps ->
`$ python manage.py migrate`
`$ python manage.py makemigrations polls`
`$ python manage.py sqlmigrate polls 0001`
`$ python manage.py migrate`


I wouldn't have written this function in this way, but I like it. Your code should do less iterations.


Isn't the MetadataReader API already supposed to be deterministic? Should it be?


LaTeXDummy (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2155 of 2165 tests passed, 205 test warnings)

 * 214 tests had: AUD diffs.
 * 10 tests had: Table big diffs.

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


>`* = Removed Herobrine.`

no proof


Consider adding something like
`log.info(String.format("AUTHORIZED - user - %s, action - %s, path - %s", user, action, pathId));`
just before returning `true`.


```Publish functions can return a Collection.Cursor, in which case Meteor will publish that cursor's documents to each subscribed client. You can also return an array of Collection.Cursors, in which case Meteor will publish all of the cursors.```
```
If a publish function does not return a cursor or array of cursors, it is assumed to be using the low-level added/changed/removed interface, and it must also call ready once the initial record set is complete.
```
I am interpreting `and it must also call ready once the initial record set is complete.` to mean, `and not until the record is complete`.


Consider adding something like
`log.info(String.format("UNAUTHORIZED - user - %s, action - %s, path - %s", user, action, pathId));`
just before returning `false`.


Please code Spring Controller in the way Zavibor did. I mean passing Model as the method argument


>`# CodeTogetherOrganisation

is this a joke


This happens because of fact that `Meteor.server.publish_handlers["Product"]` we use `apply` on it and it doesn't have correct `this`, that's why we are completely mocking it while testing. To have `this.stop()` behavior while tests you'll probably need to add:
```js
const thisContext = {
  ready: function () { return "ready"; },
  stop: () => "stop"
};
```
Clean explanation of this you could find [here](https://forums.meteor.com/t/solved-instance-of-meteor-publish-is-object-while-testing/16106/9)
BTW, `this.ready()` returns not when we are done, but in situation like this (`shopId` undefined, `productId` undefined, etc)


How about the following -
* Move this project into its own dir in the roger-mesos repo.
* Add a more appropriate package name something starting with `com.moz.clusteros` (same as what alertd uses) - perhaps `com.moz.clusteros.authnz`?
* Add some info logs to enable audit.


in fact debugging was affected with this bug, same method with different parameters was disabling debug starting.


LaTeXDummy (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1019 of 1019 tests passed, 0 test warnings)

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


I think @strager was proposing something here instead of checking for the target architecture, checking the type of device we're targeting. Might be better to do it that way.

Also, it would be great if you could add a small comment explaining why these are disabled. Potentially a `TODO` to mark them as needing implementation.


it is not good practice to pass title or any other thing related to presentation from controller. It is better to pass some flag, ie isUpdate and based on that flag show appropriate message on the JSP


OMG, how silly, @tomxtobin, @juacompe, thanks a lot!


LaTeXDummy (Myoldmopar) - 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-passing-green.svg)


approved


`DS2BUG` is marked as `DS2_UNREACHABLE` so you don't need the `return` statements here.


This looks like it'll fail for `complex128` due to `scomplex_val` vs. `dcomplex_val`.


move this to the separate css file if this is used, becasue I saw the same for other pages.... Copy-Paste?


Ok, yes, your right about this.ready, but `this.stop` prevents further processing though.. when would we even want that?


LaTeXDummy (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (2117 of 2127 tests passed, 205 test warnings)

 * 214 tests had: AUD diffs.
 * 10 tests had: Table big diffs.

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


looks good


It is good practice to declare js at the top of the file, in the head section if any


Redundant


the same as for previous file


code wizardry at its best, m8s

learn from this


It is not obvious to me what is the distinct purpose of `AssemblyInfo` and `Chunk` types. I would have considered merging them and have the `AssemblyInfoBuilder` class simply build a single list of assembly chunks (or whatever name).
The only downside is carrying a little more baggage (the list of `TypeInfo`s) around purely for logging reasons.


@sariths Yes. It should work fine. I'm still writing the part to run the analysis but the base implementation is there.


We can remove this and all of the functions that calls these because for stat we are using the asm-generic version which is 32/64 bit agnostic.


EL PLUGINS PARA STREAMS UP QUE OS HABEIS PASADO SALE POPCORN TIME PERO ARROJA ERROR DE INICIO ,, DICE QUE NO TIENE LISTA DE INICIO.    PODREIS PASAR EL STREAMS UP?

MI OTRA DUDA ERA QUE EXactamente seria que acepta archivos con el caracter [
GRACIAS POR SU EXELENTE TRABAJO


Should I have removed "target" folder before commit?


Pour quelle raison ?
Attention aux types mime non reconnus par défaut dans IIS, risque d'erreur 404.

![2016-03-08 18_53_20-firebug - accueil](https://cloud.githubusercontent.com/assets/5129879/13610674/33c4b526-e55f-11e5-8d86-7e467e5defdd.png)


In this phrase 'we must build ensure', the word 'build' looks unnecessary.


what is the difference of this file and the previous one? Looks like they are for the same purpose or I missed sth?


Размещён


If `counts` are needed, the package using it should use counts, we don't generally need it.


delet


mmap is not supported (yet) so we can remove this as well. see arch/lkl/include/asm/syscalls.h.


needs to be added here and the line above as well...


Perhaps, this error message can be localised as `<MicrosoftBingAccesstokenError>` (or similar) ?


I think we can remove this comment, we always push the low and then hi part, regardless of endianess.


Why have 3 return values, instead of just 2 (return false for null case)?


Test 1, 2, 3


Hello


This last paragraph is a leftover from the previous text, I decided to leave it in since I didn't entirely understand it and wasn't sure how important it was for people on the Elixir/Erlang tracks.

If it's not applicable to Doubly-Linked Lists it can be removed, or should there be another explanation for Elixir/Erlang users in it's place?


good idea


I don't agree with that line


`This works`


Hello JXTG — good job!


Header


Wait, I'm confused by this. Why put the `Service_` bit here and not in `lib/vanagon/component/dsl.rb`? Is there ever going to be a time when we want to reference `MARIONETTECOLLECTIVE` but not `Service_MARIONETTECOLLECTIVE`?


hello to you too


WHAT THE HECK MAN!


no but I can split 1.8.8 off into its own branch


hi after hello


Hi :+1:


Gnarly. :alien:


Line level comment


Comment on line 1


Or not...


cc/ @McdonaldSeanp @jcoconnor


Nice Code!


A new comment for this file


Some robot does this for me


bad formatting. use 4 spaces instead of the tabs


@nouiz Could you please explain why ? Also, does this apply for all the GPUFromHost nodes ?


hmm, llok good :) +1:


Comment on #135


Hi everybody


tt


#156 Please review and comment on this.


commenting on heading 3


bad formatting


oh


I agree we don't need this functionality here (`this.stop()`). I more like to see `this.ready()` on it place.


heading 4 to issue#2


TDD is good approach.  We should start doing that. :100:


@Thierry123 definitely not! :ghost:


12 week fitness program blog template created!


so funny


Yes, it's necessary, because things in `processes.py` use `SynapseParam`. There would be other ways to do it of course, but something had to change.


Is `per_ctx_mode` now overloaded, it's just that I remember moving this into `gputop_perf_stream`, since we should now consider `gputop_perf_query` to be an immutable structure.


Because I am going to use that ID part in lieu of the long id bit I had in https://github.com/McdonaldSeanp/vanagon/blob/feature/RE-6455/dirlist/lib/vanagon/platform/windows.rb#L300


it's required


Hi manova,

A proofset with this commit has been created for triggermail_sublimetext_plugin. Just for you!

[View Proofset](https://www.bluecore.com/admin/email_proofs/triggermail_sublimetext_plugin/proof_set/5689413791121408)


great!


Thanks for pointing that out. Fixed the `cn` and `cc` list generation in https://github.com/turbinesFoam/turbinesFoam/commit/08230353608bcfb32509208ad58bb09829de1ed5


welcome back


Close #1 and #2


overall, it's working back!


I believe there is for the directory list ID identifiers.
I had originally gone with putting Service_ in the dsl.rb, but then noticed Sean was doing a similar gsub operation in his code.


Yes!

> On Mar 8, 2016, at 9:54 AM, sky2day <notifications@github.com> wrote:
>
> Should I have removed "target" folder before commit?
>
> —
> Reply to this email directly or view it on GitHub.
>


Ok @nouiz  fixed this.


CLOSES https://github.com/monsieur-x/server/issues/42


Ok. I stopped the test. In my local tests the penalty was applied correctly. But that was for white only in certain positions.


suggest:
... same email address as your Eclipse **account** ...


Where do we find that sync folder??
I dont find it in the app folder...


typo: Pleasure
typo: Missing . at end of sentence.


Ok, looks like I was wrong. Reverted.


Shouldn't this break compilation?


SADasdASDad


This is bad news. We've had problems with running off the top of stack before. Any chance we can just make this a call to error?


I still don't know how the comments work.


It is considered a bad practices in perl.
Mainly because it does not work like other do-while loops in other languages.
So if someone else comes along to modify that piece of code thinking it works like a c based do-while it can fail in strange ways.

To quote Damian Conway

> Like any other postfix looping construct, a do...while loop is intrinsically hard to read, because it places the controlling condition at the end of the loop, rather than at the beginning.
>
> More importantly, in Perl a do...while loop isn't a "first-class" loop at all. Specifically, you can't use the next, last, or redo commands within a do...while. Or, worse still, you can use those control directives; they just won't do what you expect.
>

http://perl.find-info.ru/perl/028/perlbp-chp-6-sect-18.html


De nada, gracias a ti por compartir tus conocimientos.
Prefiriria no aparecer en el encabezado del archivo, los meritos son del
otro user :)
Un saludo!
El 04/03/2016 12:08, "DaggerES" <notifications@github.com> escribió:

> Gracias por las correcciones, las he añadido a mi script :)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jograben/ReloadCam/commit/b0741ebd5db568a5b4e7ef8c76c7fac2062a9eac#commitcomment-16497286>
> .
>


@jimxj Good catch! I added it too: https://github.com/magnetsystems/message-ios/commit/57b1107fa2147ffaf700c15b0e61d837a8460b04


Gibt es einen Grund warum du "short" verwendest? Ich habe jetzt mit Byte experimentiert und die eignen sich auch.
Hier habe ich eine AES Implementation gefunden in Java
http://snipplr.com/view/67929/


commented use of $timeout


[R/util-test.R:357:1:](https://github.com/jackwasey/icd9/blob/f9127f6d8ab3255444bab9fe4830e89e15493ba7/R/util-test.R#L357) *style:* **lines should not be more than 150 characters.**
```r
  # covr runs tests in a completely different R process, so seem like options are not preserved.. An alternative might be to add an expression to be run.
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```


I don't personally find it that bad but I'll add it to my notes to change it at some point


Reviewed PR and good with merge without further comments.


Note that this commit does not include full PR-URL, it has:
```
PR-URL: #5546
```
while it's supposed to be:
```
PR-URL: https://github.com/nodejs/node/pull/5546
```


thanks :)


Super, danke! Das Adminpanel muss ich dringendst mal bereinigen (und vervollständigen).


Don’t mess with the Damian.

--
Louis Munro
lmunro@inverse.ca  ::  www.inverse.ca
+1.514.447.4918 x125  :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)

> On Mar 8, 2016, at 13:07 , James Rouzier <notifications@github.com> wrote:
>
> It is considered a bad practices in perl.
> Mainly because it does not work like other do-while loops in other languages.
> So if someone else comes along to modify that piece of code thinking it works like a c based do-while it can fail in strange ways.
>
> To quote Damian Conway
>
> Like any other postfix looping construct, a do...while loop is intrinsically hard to read, because it places the controlling condition at the end of the loop, rather than at the beginning.
>
> More importantly, in Perl a do...while loop isn't a "first-class" loop at all. Specifically, you can't use the next, last, or redo commands within a do...while. Or, worse still, you can use those control directives; they just won't do what you expect.
>
> http://perl.find-info.ru/perl/028/perlbp-chp-6-sect-18.html <http://perl.find-info.ru/perl/028/perlbp-chp-6-sect-18.html>
> —
> Reply to this email directly or view it on GitHub <https://github.com/inverse-inc/packetfence/commit/3abff6b5588af62cf501a706669a0accbaa4cf24#commitcomment-16568605>.
>


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 18644](https://teamcity.mesosphere.io/viewLog.html?buildId=156892&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:10:36


In this case, I've used `tiny-process-library` as a git submodule in a project that I'm working on. Then I can `add_subdirectory(tiny-process-library)` and link my executable with your library:
```
add_executable(myproject myproject.cpp)
target_link_libraries(myproject tiny-process-library)
```
Something similar could be done for tiny-process-library tests:
```
add_executable(open_close_test open_close_test.cpp)
target_link_libraries(open_close_test tiny-process-library ${CMAKE_THREAD_LIBS_INIT})

add_executable(multithread_test multithread_test.cpp)
target_link_libraries(multithread_test tiny-process-library ${CMAKE_THREAD_LIBS_INIT})
```
I'm not sure if the library will be installed when a `make install` is executed on Linux, but it's not the idea. (I think a cmake `install()` function call is needed to do that.)


"Deprecated since Chrome 33. Please use tabs.Tab.highlighted.": https://developer.chrome.com/extensions/tabs#type-Tab


Wanted to distinguish between the three cases: does inherit from object, does not inherit from object and can't tell.  Doing it this way lets the consumer decide how to handle the case.


P.S. I can create a PR for this.


nice derp m8, 10/10 would gs2 again


pozdrav, ova funkacija odradjuje upravo to
generateSignatureFromArray


Can you tag a new version?


Oops, typo! Thanks, I'll push a fix directly (since it's a trivial typo fix). Good catch! :+1:


Yes, I read it and understood it similarly. We do not provide `__ALL__` here, but we use the `_` notation to mark private functions. Then it should be according to the PEP to use it by importing the variable elsewhere. At least that's my interpretation.


please check code formatting


The only thing missing in the commit message is something like:

(From OE-Core rev: abc123567890ef)

With the right rev that introduced this version of cURL + CVE patch and so forth.


Nice, thank you Ben!


about titles, please use the same recomendation like i mentioned for Application


@jlabrecque please do not bump version in PR.


So the thought is to change that line to `services.map { |svc| directories.push({ :path => svc.service_file, :id => "#{svc.id}BINDIR" }) }`? That's fair.


hah, so that's why things break when I disable asserts...


Dodane funkcije su viska, ali svakako cu prihvatiti dokumentaciju, pa ako mozes izmjeniti commit @BojanKogoj


I fixed the issue as part of e740debffe6f83174126ba3c1711d017b3052d4f. Looks like the syntax error got introduced as part of the merge conflict.


@marshallswain really love feathers and how it welcome new people - just trying to send a bit back :)


Do you not need to 'location.reload(true)' ?


exactly


yea, but actually since it's ultracool i'll move it into basic node filtering, in the future


@jcouv The `AssemblyInfo` type describes a test and hence must be a part of the content file.  When new relevant data is added to the type the content file must also be updated.  Putting the list of `TypeInfo` here would add essentially duplicate data.  Hence it complicates the story for `AssemblyInfo`: some data needs to be in the content file, some doesn't.  This is why I kept it out.  Made the role and contents of `AssemblyInfo` easier to understand.


@jlabrecque could you you stronger assertions such as ```assert_equal({'Policy' => {'P1' => {}}, @cf_driver.stack_config('simple-production')[:stack_policy_body]``` instead of assert_not_nil


#TODO
 - add date calculation in 'will become compliant' message (if emb_length isn't set, date looks short).
 - tie this in with emb_length calculation from #27


The patch you add for fixing the cast issue needs a header as per:
http://openembedded.org/wiki/Commit_Patch_Message_Guidelines

and at that point, probably also submitting the change to upstream and seeing what they say.


c out is not necessary here for all fields


Well that's unfortunate ... I have mispelled that a lot.  In particular in my SQL definitions.  I will address this separately as I need to change a whole lot of places ... :(


removed..


Just extend and indent instead of SRC_URI +='ing each


No worries! I don't even (unfortunately) have a Sierra ILS, I was just curiously looking at what you were working on. :)


move this to the separate css file


Extra spaces here after open-"


- Delete the old api form

- Delete columns dictionary

- All the dictionary variables should be in the new api form, period = fields.Char(string='Period')


@tmat can state if it's deterministic or not.  Years of using reflection have me pegged to think that it's non-deterministic.  But maybe I can get past that now that I'm using `MetadataReader`.


nope. but has also been fixed. :)


Related PR: https://github.com/erming/shout/pull/493


@ #[](url)


:+1: #GoPacman


@jcouv yeah this could be clearer as to why this is necessary.  Let me update this.


This seems wrong.  Shouldn't we have the correct dbus-rs cargo installed into the sysroot and picked up?


i've modified but also ran on windows w/ Chakra, SM, V8 and OK; ran on Mac w/ SM/V8 it was OK.
`--engine-chakra`  & `--engine-mozilla`


FYI @irtimmer I'm working through issues with ENet stuff with some Moonlight Android users, so I'd wait to release until that stabilizes.


Just a few things to fix up / address, thanks!


@jlabrecque thank you for your contribution! The PR looks good. I put some suggestions for minor change on the code.


Me neither. I have no idea what your earlier message refers to.... Let me
look on github.

On Tue, Mar 8, 2016 at 1:06 PM, ron minnich <notifications@github.com>
wrote:

> I still don't know how the comments work.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dancrossnyc/akaros/commit/f4b19a33edc4cedc898d1d9896893c406b6d99a2#commitcomment-16568598>
> .
>


remove commented code


All good! Waiting for deployment into production servers


Move aaScheme_ earlier in classname. Introduce baseClassDEAfult typo.


Looks good to me


- Delete this unnecessary dictionary


@sayerh ?


Do you want to think about high speed roads that do not allow any connections to buildings? Or something like trains to connect parts of the Islands together?


This is all due to changing the imports from require to ES6.
I at least kept the change in this single commit but it is still pretty tough to see the changes.


I suggest that you implement this overload and the next one by calling this one prefixUrl(Utf8String).


I agree but we shouldn't over do it. It is definitely a good practice but
let's not get slowed down by TDD. I'll do my reviews tonight and finish the
merges.

I'd dropped an email before and I'm repasting that stuff here. I'm gonna
start with these basics and expect my checkins to address these things -

Quoting -

Coding basics -

1. Binary search
2. Quick sort
3 Skewed binary search -- find index and find element
4. DFS - all three ( inorder, preorder, postorder ) both recursive and non
 recursive
5. BFS - Zig zag print
6. Topological sort
7. Graph representation
8. Find a cycle in both cyclic and acyclic graph
9. LRU cache implementation
10. Coloring pattern in a graph
11. Sink and source in a graph
12. Eulerian circuit in a graph
13. Dynamic programming - 5 problems from geeks for geeks

Design basics -

1. Distributed system basics -- Fault tolerant, load balancing
2. Scale out for web application
3. Caching in web application

On Tue, Mar 8, 2016 at 10:00 AM, Ketan <notifications@github.com> wrote:

> TDD is good approach. We should start doing that. [image: :100:]
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/KetanA/Algorithms/commit/65be3a5fb24ccf18fc959a3d80fa5c80c52d7fa5#commitcomment-16568479>
> .
>


@ftonato ... Eu conversei com o Raphael sobre alterar a fota anterior por crianças sorrindo (pois parecia ser um pouco mais receptivo rsrs) ... Mas assim que eu subi a imagem ela ficou esticada para os lados ... você consegue ajustar isso?


We all have seen silly rook maneuvers by SF, and feel that "something could be done".
But I'm beginning to think that these rook motives does not occur often enough,
and probably even less often at LTC.


why is it 8000:80 here and in the pybossa-dev file 80:80?


It seems like a pretty special exception since that is what causes the error in the first place.

Regardless, don't you think it would be a good idea to give a user some information about what went wrong since with the current implementation they won't be able to differentiate why logging errors happened. Seems very counter intuitive to wrap an exception with explicit debugging information with a generic and unhelpful message.


b


Actually I may take that back. I came up with a smaller example that I thought would break but didn't:

```swift
class C<T> {
  let x: T
}

class Q<T, U> {
  let x: T
  let y: C<U>
}

let instance = Q(x: 1, y: C(x: true))
```
I just tried it, works fine, and apparently the unsubstituted typeref for `y` is:
```
(bound-generic C
  (generic-type-parameter index=1 depth=0))
```
The index was serialized with index == *1*, which means I can use `instance`'s substitution map. I thought that it would've been *0* for some reason. I assume that means that the depths will also line up?


:sunglasses: Nice !


I'm not sure what you mean; this is constructing the string that is passed to error(). Everything is spliced together using strlcpy() and strlcat(), which won't overflow the stack buffer.


@xpg934 Она уже там


Downgrading to a version that's more than one year old :fearful:
wait, that ccl version... does that even exist?


I would liked to not clutter code with additional functions, if possible.
Only if it's really enhances usage.
Now `AgSet <option>  <CR>` works to show value, like any other vim options do.


I picked part of another commit by accident. Everything after line 92 is part of this commit message.
Everything before should have been "create alertMessage and show onClick"


small inconsistencies make the world go round!


Heh, not on purpose. [Here you go.](https://github.com/django-ses/django-ses/pull/86)


The following doc(s) have been deployed to the [xmlsitemap](http://xmlsitemap-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/articles/sites/code/bots-and-indexing](http://xmlsitemap-static-docs.pantheonsite.io/docs/articles/sites/code/bots-and-indexing)


fixed


Did you test an `npm install` from nothing after making these changes? I actually had some issues at one point with ordering. Not sure exactly what NPM's behavior is for this.


I don't get why we need this parameter here.  It is not passed to any other function!


I'm not sure, but I don't think we can use `#[ignore]` and the --ignored switch of cargo to disable/enable these tests. There are some doctests that are marked `ignored` because doctests fail during cross-compilation.

Instead, there should be a feature flag that controls the use of these slow tests, named "slow_tests" or something.


Looks good. Though they might complain about the -1 initialization and we can address that with another patch.


Alright, I think reset isn't bad, however manually typing  `AgSet <option> []` is not much more of work either.
But are you sure there must be `... != type(...)` instead of `==`?


Actually it is just used as an error message so switch it to err.


Not really related to this PR, but is there any reason not include the OSF functions in MapUtils?


Is this just a UX preference @luciovilla?


FixCrashWithZoneAndSystemERV (JasonGlazer) - Win64-Windows-7-VisualStudio-12: OK (2137 of 2137 tests passed, 0 test warnings)

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


Maybe "start work on groups" There's no way that groups is a two week project.


What kind of commentary you're interested in?  The patch essentially covers up LLVM's lack of support for bitcasting between vectors and their isomorphic array equivalents.


space after comma


TeamCity Glyssen :: Glyssen-master Continuous [Build 0.2.6.9bddadcb9667e8ce0ba1a744a48645d1d209c588](http://build.palaso.org/viewLog.html?buildId=70021&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 1031, ignored: 12 Build time: 00:06:08


Also, I don't like this logs here. I think this is a waste of precious CPU time.


Create super user -> `$ python manage.py createsuperuser`


Actually I rewrote for lollipop. Kept kufis name there out of respect since it is based on his and a lot of code is his.


I think there's an off-by-one error here because `jt_entries` does not include the first `NOP` instruction (that gets added in `JumpTable.toString`, but `JUMP_TABLE_COUNT` is the count of all entries, including the initial `NOP`.


If you look at the implementation of MetadataReader.TypeDefinitions (https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/src/System/Reflection/Metadata/HandleCollections.cs#L1282) it's actually very simple - it enumerates thru a range of numbers [1..#typedefs]. So i'd say that's fairly deterministic :)


Those are some pimpin coding skills.


Oh god, that is really coming to back to annoy us. Good catch.


Eric,
I saw your typo. Noticed your correction now that I wrote that.
Thanks,
Sayer


Thank you for working on SLI and Multilang!
Here is the german cp:


I've tested your code but i'm still getting an error:
![img](https://i.imgur.com/eS84pib.png)


Triple L!


Pools of water, too? As I was trying to do with caves, just want to mix things up a little (:


Is this the method description? Or did you mean to do a @should?


Truly speaking append can also be superseeded by `AgSet option option+["value"]`
But alright, maybe append has it's right to exist, unlike others.
However I would instead complete functions did simple wrappers to `ag#set` interface.


As discussed over the call, Pls remove from AuditqueryLogSecured.xsd as well.


please provide more of a comment of what is getting fixed.


This comment was mostly a note to self. I think I will start a discussion about this in a separate issue tonight, since you are right, my concerns don't belong to your changeset but rather than to the exercise as a hole.


I'd suggest naming this `JT_MAX_ENTRIES`. Also, it seems to me it would be better to just put a constant number here, rather than computing it from things like the packet length. It's a quirk of the current communication protocol that the packet length and jump table length are the same; this may not be the case in the future. For example, we may be able to upload multiple jump tables in one sram write, or split a long jump table across multiple writes.


re the style guide, a multiline should be broken up on parens, like so:
```
_DEFAULT_DATE_BOUNDS_FILE = os.path.join(
    os.path.dirname(__file__), 'resources',
    'DQC_US_0006', 'dqc_06_date_bounds.csv'
)
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 18645](https://teamcity.mesosphere.io/viewLog.html?buildId=156940&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 250 Build time: 00:08:52


Title could be something like:

staging: unisys: visorbus: change vague variable name in visorbus_init()


Thank you for working on SLI and Multilang!
Here is the german cp:
![img](https://i.imgur.com/WIQ8xgy.png)


Duplication is not needed, right?


@spicyj Do you know why the `grantEvent` is before the `terminateEvent` here?


Number of _bytes_ in jump table SRAM write packet.


Please separate into multiple commits if you are doing mulitple things or at least comment on what you are doing in the commit.


let's call this `packet_len` since it is no longer a class-level constant.


nit: `test_too_many_entries`


Terminal is currently used in the Linux Process struct, which is a shared struct between Windows and Linux, so we can't remove Terminal, but we could either use it to indicate that we want to Emulate Console, or we could add EmulateConsole instead of tty.


This is not correct for nested types. ```type.Name``` for a nested type doesn't include the outer type names. Not sure how xunit handles tests in nested types though.


Minor style nit: Use a tuple here instead of a list for consistency.


1. RequestCollection it is not very good for user
2. all these validation messages need t be moved to the validationMessage.properties file


list -> tuple


In recent version build, task handeling catch the SayWhenError and the pool continue to run.
In older build, task handeling crash and we catch it. This raises some issues in the handeling of the cache.


Why you needed complete `ignore_list` instead of adding options to already existing `ignore`?
Is there some profoundness?
You can `AgSet ignore patt1|patt2|patt3` after all...


Oops, you already did this. Thanks! :)


Returns which allergy? Can you take a look at the existing openmrs services javadoc for an example of how we describe such methods?


@apaszke yes TX1 and Pascal both support FP16 processing. Maxwell (except TX1) supports only FP16 storage as @azaidy discovered. That is why I am puzzled as to why the TX1 FP16 batch 32 benchmark clocks in at 3x slower than FP32. It should be ~2x faster.


Same comment as above.


There's nothing particularly wrong with this, but does "~TC()" not work or something?


Can you also describe the uuid param?


Agreed. Fixed.


:metal: That's a lot of data :fearful:


All good with me.


Sounds good.


d851/proprietary/lib/libloc_ds_api.so was removed but it's still in d851/d851-vendor-blobs.mk


@vgokhale Oh, sorry. I misread your comment. I'm too tired today :confused: That's indeed weird.


Why silent? We assume there no errors in normal usecase. So when it throws, we need somehow to know about it.
With silent we will never know. You did something similar already in the past, and then I removed them after whole day of troubleshooting that hidden behaviour.


@djpate please do not bump gem version in PR, likely will conflict with other PR.


I imagine this should be translatable. In fact, you should probably make the string "Lvl $level" and use `vgettext()`.


TeamCity jonas-requests :: WindowsBuild [Build 19](https://build.neohq.net/viewLog.html?buildId=569151&buildTypeId=JonasHaRequests_WindowsBuild) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 31857, ignored: 117 Build time: 2:15:13
### Failed tests
```
org.neo4j.test.ha.ClusterTest.testClusterWithWildcardIP: <no details avaliable>

```


Well, RILD didn't even startup because it couldn't find this lib. I am not sure that commit would help this cause.


This function is basically a copy of [`elasticsearch.helpers.scan()`](https://github.com/elastic/elasticsearch-py/blob/879de7549e930c1580cb3a90f4551fea62717e0f/elasticsearch/helpers/__init__.py#L237). A simpler option would be to use `elasticsearch.helpers.scan()` and just get the total number of docs in a separate query. I was thinking it was best to reduce duplicate queries like that, but given that a scan could be multiple queries any ways, one more might not be such a big deal.


+1 for bash strict mode.


The list here has `JUMP_TABLE_COUNT + 2` entries. Let's make it `JUMP_TABLE_COUNT` to ensure that still fails (remember that there's an additional `NOP` added for the start operation, so if we have `JUMP_TABLE_COUNT` here there'll be `JUMP_TABLE_COUNT + 1` total, which should fail).


How does the end user change this value? Can you take a look at the bottom of this class for examples of how global properties are setup?


Again, why no translation mark?


`#[ignore]` works for me as expected. The [documentation chapter](https://doc.rust-lang.org/book/documentation.html#running-documentation-tests) from the book states that doctests marked with `ignore` are never executed.