A module for modifying relevant MESSAGE parameters after changing lifetime

Please confirm that this PR has done the following:

[ ] Tests Added
[x] Documentation Added
[x] Description in RELEASE_NOTES.md Added

Adding to RELEASE_NOTES.md
Please add a single line in the release notes similar to the following:
- (#XX)[http://link-to-pr.com] Added feature which does something

There are 100 errors:

message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 3 - E501 line too long (95 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 5 - E501 line too long (135 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 6 - E501 line too long (134 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 32 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 34 - E501 line too long (107 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 36 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 40 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 42 - E501 line too long (108 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 44 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 46 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 47 - E501 line too long (125 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 56 - E128 continuation line under-indented for visual indent
E501 line too long (86 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 64 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 73 - E501 line too long (89 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 98 - E126 continuation line over-indented for hanging indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 102 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 103 - E501 line too long (111 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 104 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 132 - E501 line too long (91 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 158 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 166 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 188 - E501 line too long (88 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 190 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 199 - E114 indentation is not a multiple of four (comment)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 202 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 204 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 207 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 228 - E501 line too long (163 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 229 - E501 line too long (115 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 243 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 245 - E501 line too long (92 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 259 - E501 line too long (90 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 278 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 282 - W293 blank line contains whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 283 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 284 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 291 - E501 line too long (98 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 296 - E704 multiple statements on one line (def)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 313 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 325 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 326 - E501 line too long (100 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 327 - E501 line too long (119 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 335 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 357 - E501 line too long (109 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 359 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 367 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 369 - E501 line too long (142 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 370 - E501 line too long (141 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 372 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 376 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 377 - E126 continuation line over-indented for hanging indent
E501 line too long (101 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 379 - E231 missing whitespace after ','
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 380 - E126 continuation line over-indented for hanging indent
E501 line too long (97 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 383 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 384 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 399 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 401 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 403 - E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 404 - E127 continuation line over-indented for visual indent
E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 417 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 419 - E265 block comment should start with '# '
E501 line too long (122 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 443 - E265 block comment should start with '# '
E501 line too long (83 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 456 - E501 line too long (87 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 459 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 460 - E265 block comment should start with '# '
tests/test_lifetime.py, line 11 - E501 line too long (82 > 79 characters)
tests/test_lifetime.py, line 18 - E231 missing whitespace after ','
tests/test_lifetime.py, line 21 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (94 > 79 characters)
tests/test_lifetime.py, line 24 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 25 - E231 missing whitespace after ':'
E501 line too long (104 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 26 - W293 blank line contains whitespace
tests/test_lifetime.py, line 28 - E231 missing whitespace after ','
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E501 line too long (88 > 79 characters)
tests/test_lifetime.py, line 29 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (107 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 30 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 31 - E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (81 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 32 - E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (92 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 41 - E501 line too long (92 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 42 - E128 continuation line under-indented for visual indent
E501 line too long (89 > 79 characters)
tests/test_lifetime.py, line 45 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 46 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E501 line too long (104 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 50 - E231 missing whitespace after ','
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E501 line too long (97 > 79 characters)
tests/test_lifetime.py, line 51 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (112 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 52 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 53 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (82 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 54 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (106 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 55 - E126 continuation line over-indented for hanging indent
E231 missing whitespace after ','
tests/test_lifetime.py, line 57 - E231 missing whitespace after ','
E501 line too long (87 > 79 characters)
tests/test_lifetime.py, line 66 - E501 line too long (87 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 67 - E128 continuation line under-indented for visual indent
E501 line too long (88 > 79 characters)
tests/test_lifetime.py, line 70 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 71 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E501 line too long (88 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 72 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
tests/test_lifetime.py, line 77 - E225 missing whitespace around operator
E501 line too long (106 > 79 characters)
E226 missing whitespace around arithmetic operator
tests/test_lifetime.py, line 78 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (112 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 79 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 80 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 81 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (86 > 79 characters)
tests/test_lifetime.py, line 82 - E126 continuation line over-indented for hanging indent
E231 missing whitespace after ','
tests/test_lifetime.py, line 84 - E231 missing whitespace after ','
E501 line too long (87 > 79 characters)
tests/test_lifetime.py, line 85 - W292 no newline at end of file

There are 100 errors:

message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 3 - E501 line too long (95 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 5 - E501 line too long (135 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 6 - E501 line too long (134 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 32 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 34 - E501 line too long (107 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 36 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 40 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 42 - E501 line too long (108 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 44 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 46 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 47 - E501 line too long (125 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 56 - E128 continuation line under-indented for visual indent
E501 line too long (86 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 64 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 73 - E501 line too long (89 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 98 - E126 continuation line over-indented for hanging indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 102 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 103 - E501 line too long (111 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 104 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 132 - E501 line too long (91 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 158 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 166 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 188 - E501 line too long (88 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 190 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 199 - E114 indentation is not a multiple of four (comment)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 202 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 204 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 207 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 228 - E501 line too long (163 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 229 - E501 line too long (115 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 243 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 245 - E501 line too long (92 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 259 - E501 line too long (90 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 278 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 282 - W293 blank line contains whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 283 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 284 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 291 - E501 line too long (98 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 296 - E704 multiple statements on one line (def)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 313 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 325 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 326 - E501 line too long (100 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 327 - E501 line too long (119 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 335 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 357 - E501 line too long (109 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 359 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 367 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 369 - E501 line too long (142 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 370 - E501 line too long (141 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 372 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 376 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 377 - E126 continuation line over-indented for hanging indent
E501 line too long (101 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 379 - E231 missing whitespace after ','
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 380 - E126 continuation line over-indented for hanging indent
E501 line too long (97 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 383 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 384 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 399 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 401 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 403 - E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 404 - E127 continuation line over-indented for visual indent
E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 417 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 419 - E265 block comment should start with '# '
E501 line too long (122 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 443 - E265 block comment should start with '# '
E501 line too long (83 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 456 - E501 line too long (87 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 459 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 460 - E265 block comment should start with '# '
tests/test_lifetime.py, line 11 - E501 line too long (82 > 79 characters)
tests/test_lifetime.py, line 18 - E231 missing whitespace after ','
tests/test_lifetime.py, line 21 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (94 > 79 characters)
tests/test_lifetime.py, line 24 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 25 - E231 missing whitespace after ':'
E501 line too long (104 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 26 - W293 blank line contains whitespace
tests/test_lifetime.py, line 28 - E231 missing whitespace after ','
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E501 line too long (88 > 79 characters)
tests/test_lifetime.py, line 29 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (107 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 30 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 31 - E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (81 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 32 - E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (92 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 41 - E501 line too long (92 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 42 - E128 continuation line under-indented for visual indent
E501 line too long (89 > 79 characters)
tests/test_lifetime.py, line 45 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 46 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E501 line too long (104 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 50 - E231 missing whitespace after ','
E225 missing whitespace around operator
E226 missing whitespace around arithmetic operator
E501 line too long (97 > 79 characters)
tests/test_lifetime.py, line 51 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (112 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 52 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 53 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (82 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 54 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E225 missing whitespace around operator
E501 line too long (106 > 79 characters)
E231 missing whitespace after ','
tests/test_lifetime.py, line 55 - E126 continuation line over-indented for hanging indent
E231 missing whitespace after ','
tests/test_lifetime.py, line 57 - E231 missing whitespace after ','
E501 line too long (87 > 79 characters)
tests/test_lifetime.py, line 66 - E501 line too long (87 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 67 - E128 continuation line under-indented for visual indent
E501 line too long (88 > 79 characters)
tests/test_lifetime.py, line 70 - E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 71 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E501 line too long (88 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 72 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
tests/test_lifetime.py, line 77 - E225 missing whitespace around operator
E501 line too long (106 > 79 characters)
E226 missing whitespace around arithmetic operator
tests/test_lifetime.py, line 78 - E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (112 > 79 characters)
W291 trailing whitespace
tests/test_lifetime.py, line 79 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (111 > 79 characters)
tests/test_lifetime.py, line 80 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
W291 trailing whitespace
tests/test_lifetime.py, line 81 - E128 continuation line under-indented for visual indent
E231 missing whitespace after ':'
E231 missing whitespace after ','
E501 line too long (86 > 79 characters)
tests/test_lifetime.py, line 82 - E126 continuation line over-indented for hanging indent
E231 missing whitespace after ','
tests/test_lifetime.py, line 84 - E231 missing whitespace after ','
E501 line too long (87 > 79 characters)
tests/test_lifetime.py, line 85 - W292 no newline at end of file

There are 111 errors:

message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 3 - E501 line too long (95 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 5 - E501 line too long (135 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 6 - E501 line too long (134 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 32 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 34 - E501 line too long (107 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 36 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 40 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 42 - E501 line too long (108 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 44 - E501 line too long (105 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 46 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 47 - E501 line too long (125 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 56 - E128 continuation line under-indented for visual indent
E501 line too long (86 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 64 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 73 - E501 line too long (89 > 79 characters)
W291 trailing whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 98 - E126 continuation line over-indented for hanging indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 102 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 103 - E501 line too long (111 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 104 - E501 line too long (80 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 132 - E501 line too long (91 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 158 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 166 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 188 - E501 line too long (88 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 190 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 199 - E114 indentation is not a multiple of four (comment)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 202 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 204 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 207 - E501 line too long (95 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 228 - E501 line too long (163 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 229 - E501 line too long (115 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 243 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 245 - E501 line too long (92 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 259 - E501 line too long (90 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 278 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 282 - W293 blank line contains whitespace
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 283 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 284 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 291 - E501 line too long (98 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 296 - E704 multiple statements on one line (def)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 313 - E501 line too long (93 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 325 - E501 line too long (99 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 326 - E501 line too long (100 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 327 - E501 line too long (119 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 335 - E501 line too long (124 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 357 - E501 line too long (109 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 359 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 367 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 369 - E501 line too long (142 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 370 - E501 line too long (141 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 372 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 376 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 377 - E126 continuation line over-indented for hanging indent
E501 line too long (101 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 379 - E231 missing whitespace after ','
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 380 - E126 continuation line over-indented for hanging indent
E501 line too long (97 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 383 - E501 line too long (112 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 384 - E501 line too long (103 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 399 - E501 line too long (82 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 401 - E501 line too long (81 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 403 - E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 404 - E127 continuation line over-indented for visual indent
E501 line too long (113 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 417 - E128 continuation line under-indented for visual indent
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 419 - E265 block comment should start with '# '
E501 line too long (122 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 443 - E265 block comment should start with '# '
E501 line too long (83 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 456 - E501 line too long (87 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 459 - E501 line too long (85 > 79 characters)
message_ix/toolbox/lifetime_changer/f_lifetimeChanger.py, line 460 - E265 block comment should start with '# '
tests/test_lifetime.py, line 29 - E501 line too long (84 > 79 characters)
tests/test_lifetime.py, line 30 - E501 line too long (94 > 79 characters)
tests/test_lifetime.py, line 47 - E501 line too long (84 > 79 characters)
tests/test_lifetime.py, line 48 - E501 line too long (84 > 79 characters)
tests/test_lifetime.py, line 93 - E501 line too long (90 > 79 characters)
tests/test_lifetime.py, line 94 - E501 line too long (90 > 79 characters)
tests/test_lifetime.py, line 96 - E501 line too long (85 > 79 characters)
tests/test_lifetime.py, line 122 - E501 line too long (94 > 79 characters)
tests/test_lifetime.py, line 145 - E501 line too long (85 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 3 - E501 line too long (92 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 4 - E501 line too long (140 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 39 - E501 line too long (121 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 41 - E501 line too long (134 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 43 - E501 line too long (101 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 45 - E501 line too long (118 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 46 - E501 line too long (115 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 56 - E501 line too long (86 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 104 - E501 line too long (80 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 105 - E501 line too long (111 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 106 - E501 line too long (80 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 198 - E501 line too long (88 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 209 - E114 indentation is not a multiple of four (comment)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 212 - E501 line too long (95 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 214 - E501 line too long (93 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 217 - E501 line too long (95 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 238 - E501 line too long (163 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 239 - E501 line too long (115 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 276 - E501 line too long (90 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 295 - E501 line too long (82 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 300 - E501 line too long (112 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 310 - E501 line too long (98 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 315 - E704 multiple statements on one line (def)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 332 - E501 line too long (93 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 369 - E501 line too long (124 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 391 - E501 line too long (109 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 393 - E501 line too long (85 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 401 - E501 line too long (103 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 403 - E501 line too long (142 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 404 - E501 line too long (141 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 410 - E501 line too long (89 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 412 - E501 line too long (85 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 415 - E501 line too long (112 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 416 - E501 line too long (103 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 431 - E501 line too long (97 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 433 - E501 line too long (81 > 79 characters)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 464 - E265 block comment should start with '# '
E501 line too long (122 > 79 characters)

I couldn't find a .stickler.yml file in this repository. I can make one for you, or you can create one by following the documentation.

I couldn't find a .stickler.yml file in this repository. I can make one for you, or you can create one by following the documentation.

There are 101 errors:

tests/test_lifetime.py, line 18 - E402 module level import not at top of file
tests/test_lifetime.py, line 94 - E501 line too long (80 > 79 characters)
tests/test_lifetime.py, line 95 - E501 line too long (104 > 79 characters)
tests/test_lifetime.py, line 99 - W391 blank line at end of file
toolbox/lifetime_changer/f_lifetimeChanger.py, line 13 - E302 expected 2 blank lines, found 1
toolbox/lifetime_changer/f_lifetimeChanger.py, line 28 - W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 41 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 42 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 46 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 47 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 49 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 50 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 52 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 53 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 55 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 56 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 57 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 58 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 110 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E116 unexpected indentation (comment)
W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 111 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 112 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 113 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 114 - W191 indentation contains tabs
E116 unexpected indentation (comment)
W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 115 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 116 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 118 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 148 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E116 unexpected indentation (comment)
W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 149 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 150 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
W503 line break before binary operator
toolbox/lifetime_changer/f_lifetimeChanger.py, line 151 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 152 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 220 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 222 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 234 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 235 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 237 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 238 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 239 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 241 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 242 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 244 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 262 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E116 unexpected indentation (comment)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 263 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 264 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 265 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 266 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 267 - E101 indentation contains mixed spaces and tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 268 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E131 continuation line unaligned for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 269 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 270 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 271 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 308 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 309 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 328 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 329 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 330 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E131 continuation line unaligned for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 331 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 332 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 334 - W293 blank line contains whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 340 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 341 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 342 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 352 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 354 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 357 - E704 multiple statements on one line (def)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 365 - W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 377 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 378 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 385 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 386 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 387 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 414 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 415 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 427 - W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 442 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E116 unexpected indentation (comment)
W291 trailing whitespace
toolbox/lifetime_changer/f_lifetimeChanger.py, line 443 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 451 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E999 IndentationError: unexpected indent
E113 unexpected indentation
toolbox/lifetime_changer/f_lifetimeChanger.py, line 452 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 454 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 456 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 457 - W191 indentation contains tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 459 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 476 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E126 continuation line over-indented for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 477 - W191 indentation contains tabs
E101 indentation contains mixed spaces and tabs
E131 continuation line unaligned for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 478 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 480 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E131 continuation line unaligned for hanging indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 482 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 483 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 484 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 485 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 486 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 487 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 488 - W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 490 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 502 - W293 blank line contains whitespace
E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 503 - W191 indentation contains tabs
E116 unexpected indentation (comment)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 504 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 506 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E128 continuation line under-indented for visual indent
toolbox/lifetime_changer/f_lifetimeChanger.py, line 508 - E101 indentation contains mixed spaces and tabs
toolbox/lifetime_changer/f_lifetimeChanger.py, line 538 - E101 indentation contains mixed spaces and tabs
W191 indentation contains tabs
E116 unexpected indentation (comment)
toolbox/lifetime_changer/f_lifetimeChanger.py, line 539 - E101 indentation contains mixed spaces and tabs

Okay, looks like we've satisfied the @stickler-ci, finally!
An initial checklist of changes that should be addressed:

[ ] move toolbox/lifetime_changer/f_lifetimeChanger.py → message_ix/tools/lifetime_changer/__init__.py

[ ] adjust the import in test_lifetime.py accordingly.

[ ] move toolbox/lifetime_changer/readme → message_ix/tools/lifetime_changer/README.rst

[ ] add a page doc/source/api/tools.rst with this content:
.. include:: ../../../message_ix/tools/lifetime_changer/README.rst

.. automodule:: message_ix.tools.lifetime_changer
   :members:

[ ] address the conflict in RELEASE_NOTES.md

Thank you Paul reviewing the style and for improving it. I will follow your guide for the documentation and readme.


how to reinitilize slick

So, I have slick carousel for my images.
I want the carousel to go fullscreen when i click a button.
I am doing it in fullscreen by adding class
position:fixed; width:100%; height:100%;left:0;top:0
but i images are partially shown.
how do I reinitialize slick in this case so that it takes up the new width and height and adjusts accordingly?

anyone? anything?

use ng-if to reinit

Thank you for your reply.
Can you tell me the code. :|

Got it. Thanks. :)

example: https://github.com/devmark/angular-slick-carousel#slide-data

For change slide content, you have to set ng-if to destroy and init it
If works, although not very obvious!


RuleSet generation in Connection Manager

This PR introduce the RuleSet generation in Connection Manager.

This change is

Added RuleSet creation functions and field for distribute serialized ruleset in packet.


fix: version of the package

Description
The version doesn't exist
Related Issue
None
Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[ ] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[ ] I've read the CODE_OF_CONDUCT.md document.
[ ] I've read the CONTRIBUTING.md guide.
[ ] I've updated the code style using make codestyle.
[ ] I've written tests for all new methods and classes that I created.
[ ] I've written the docstring in Google format for all the methods and classes that I used.

Ask me anything if you need help. Have a good day!


feat(chocolatey): improved choco packages installation task

Added an option to select the version of the installation package.
Added an option to update or delete the package via the state argument.
Added an option to provide additional parameters for the choco package manager via choco_args parameter.

This PR is included in version 1.11.0 :tada:


Change site root

I found that the rewrite rule listed under the "Change site root" heading did not work. I found this rule did:
RewriteCond %{REQUEST_URI} ^(.*)
Hope this helps someone else.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a3209bb1-99cd-9e32-ae48-2605831aee02
Version Independent ID: 743bc03e-d0d1-1e9e-acb1-52ae01daa0cc
Content: Configure PHP apps - Azure App Service
Content Source: articles/app-service/configure-language-php.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@robert-t-taylor Thanks for the feedback. Our team is looking into this and will update the document as required.

Thanks for taking time to share your valuable feedback and suggestion.
To test this out, just to confirm, are you leveraging Laravel? it uses the public/ subdirectory as the site root.
The .htaccess file to your repository root to have both lines:
 `<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REQUEST_URI} ^(.*)
RewriteRule ^(.*)$ /public/$1 [NC,L,QSA]
 </IfModule>
    `

Actually, I am using Drupal 9, and the /web is the new, recommended site
root. I have confirmed that this works.
BTW, the only issue I had was the following line:
RewriteCond %{REQUEST_URI} ^/$
I had to change it to RewriteCond %{REQUEST_URI} ^(.*) to get the
redirect to work.
On Mon, Sep 14, 2020 at 5:12 PM AjayKumar-MSFT<EMAIL_ADDRESS>wrote:

Thanks for taking time to share your valuable feedback and suggestion.
To test this out, just to confirm, are you leveraging Laravel? it uses the
public/ subdirectory as the site root.
The .htaccess file to your repository root to have both lines:
<IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{REQUEST_URI} ^(.*) RewriteRule ^(.*)$ /public/$1 [NC,L,QSA]  </IfModule>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/62505#issuecomment-692317091,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWE6ZYUN5CPCKYNDXABBK3SF2BLFANCNFSM4RIKKEVA
.

--
Bob Taylor
Elliance, Inc. http://elliance.com
600 River Avenue, Suite 201
Pittsburgh, PA 15212
Toll Free:<PHONE_NUMBER>
Local:<PHONE_NUMBER> x347

Robert, Thanks for sharing additional details.
My apologies if I'm missing understanding anything.
You have mentioned "I had to change it to RewriteCond %{REQUEST_URI} ^(.*) to get the redirect to work."
I see that in the referenced document , the exact same line is mentioned.
And, I don't see this line -'RewriteCond %{REQUEST_URI} ^/$'

If you could share a screenshot of what you observe would be helpful (please conceal any private information).
The tutorial is meant to show something more involved, but still allow customers to learn things beyond a specific framework (Laravel). For example, here you learn how to set environment variables and access them, connect with Azure MySQL securely, run Composer (or a custom deployment script). It's not meant to teach Laravel but just uses Laravel to demonstrate the concepts. So in a sense the article uses Laravel but isn't merely for Laravel developers, but hopefully demonstrates certain concepts for all PHP developers. Hope this explanation helps.
Once again, apologies for any confusion, we really appreciate you taking time to share good feedback.
We will close this out, but if you feel you need more information please just let us know we will continue the discussion.

Sorry, I had this backwards: I had to change the condition to  RewriteCond
%{REQUEST_URI} ^/$  to get it to work.
On Wed, Sep 16, 2020 at 4:15 PM AjayKumar-MSFT<EMAIL_ADDRESS>wrote:

Robert, Thanks for sharing additional details.
My apologies if I'm missing understanding anything.
You have mentioned "I had to change it to RewriteCond %{REQUEST_URI} ^(.*)
to get the redirect to work."
I see that in the referenced document
https://docs.microsoft.com/azure/app-service/configure-language-php?pivots=platform-linux#change-site-root,
the exact same line is mentioned.
And, I don't see this line -'RewriteCond %{REQUEST_URI} ^/$'
[image: image]
https://user-images.githubusercontent.com/44606227/93385784-585bbc80-f884-11ea-9711-c7d524673911.png
If you could share a screenshot of what you observe would be helpful
(please conceal any private information).
The tutorial is meant to show something more involved, but still allow
customers to learn things beyond a specific framework (Laravel). For
example, here you learn how to set environment variables and access them,
connect with Azure MySQL securely, run Composer (or a custom deployment
script). It's not meant to teach Laravel but just uses Laravel to
demonstrate the concepts. So in a sense the article uses Laravel but isn't
merely for Laravel developers, but hopefully demonstrates certain concepts
for all PHP developers. Hope this
https://github.com/MicrosoftDocs/azure-docs/issues/34265#issuecomment-522056070
explanation helps.
Once again, apologies for any confusion, we really appreciate you taking
time to share good feedback.
We will close this out, but if you feel you need more information please
just let us know we will continue the discussion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/62505#issuecomment-693641248,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWE6Z2AYOVYQ4BB5JHWB33SGEMF5ANCNFSM4RIKKEVA
.

--
Bob Taylor
Elliance, Inc. http://elliance.com
600 River Avenue, Suite 201
Pittsburgh, PA 15212
Toll Free:<PHONE_NUMBER>
Local:<PHONE_NUMBER> x347

Please ignore and close this ticket. Thanks.
On Wed, Oct 14, 2020 at 3:28 PM Bob Taylor<EMAIL_ADDRESS>wrote:

Sorry, I had this backwards: I had to change the condition to  RewriteCond
%{REQUEST_URI} ^/$  to get it to work.
On Wed, Sep 16, 2020 at 4:15 PM AjayKumar-MSFT<EMAIL_ADDRESS>wrote:

Robert, Thanks for sharing additional details.
My apologies if I'm missing understanding anything.
You have mentioned "I had to change it to RewriteCond %{REQUEST_URI}
^(.*) to get the redirect to work."
I see that in the referenced document
https://docs.microsoft.com/azure/app-service/configure-language-php?pivots=platform-linux#change-site-root,
the exact same line is mentioned.
And, I don't see this line -'RewriteCond %{REQUEST_URI} ^/$'
[image: image]
https://user-images.githubusercontent.com/44606227/93385784-585bbc80-f884-11ea-9711-c7d524673911.png
If you could share a screenshot of what you observe would be helpful
(please conceal any private information).
The tutorial is meant to show something more involved, but still allow
customers to learn things beyond a specific framework (Laravel). For
example, here you learn how to set environment variables and access them,
connect with Azure MySQL securely, run Composer (or a custom deployment
script). It's not meant to teach Laravel but just uses Laravel to
demonstrate the concepts. So in a sense the article uses Laravel but isn't
merely for Laravel developers, but hopefully demonstrates certain concepts
for all PHP developers. Hope this
https://github.com/MicrosoftDocs/azure-docs/issues/34265#issuecomment-522056070
explanation helps.
Once again, apologies for any confusion, we really appreciate you taking
time to share good feedback.
We will close this out, but if you feel you need more information please
just let us know we will continue the discussion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/62505#issuecomment-693641248,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWE6Z2AYOVYQ4BB5JHWB33SGEMF5ANCNFSM4RIKKEVA
.

--
Bob Taylor
Elliance, Inc. http://elliance.com
600 River Avenue, Suite 201
Pittsburgh, PA 15212
Toll Free:<PHONE_NUMBER>
Local:<PHONE_NUMBER> x347

--
Bob Taylor
Elliance, Inc. http://elliance.com
600 River Avenue, Suite 201
Pittsburgh, PA 15212
Toll Free:<PHONE_NUMBER>
Local:<PHONE_NUMBER> x347


feat(discord): add more detail to pledge embed

Description

Makes Discord embed for pledge events prettier

Closes

Closes #2864

Note

Feel free to close, just had a wild hair on lunch.
I tested locally but I'd like to be able to test with the pulled values from the database and others, if someone can do that?

UI

Before

After

Thanks, I've tested this with real data and it looks fantastic! Thanks a lot!


FR:Disable opening an empty buffer when clicked on buffer line

Hi
I have been trying to find a solution to this, sometimes not clicking the proper place on the bufferline ends up creating new empty buffers. I think because adding a newtab means adding also a new buffer. So in that respect it would be nice if there is a way to disable this functionality.
thanks

Unfortunately, this is a builtin feature of vim's tabline. Showing buffer names via the tabline is really just a hack with the tab labels.
From the vim docs:
A double click with the mouse in the non-GUI tab pages line opens a new, empty
tab page.  It is placed left of the position of the click.  The first click
may select another tab page first, causing an extra screen update.

So I guess you should just avoid double-clicking the tabline.

thanks


Use core version of listagg macro

Describe the feature
Remove the need to roll our own version of listagg to force integration tests to pass.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
Who will this benefit?
What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
Are you interested in contributing this feature?

yeah! thought it would have closed with benoit's PR 🤔


No context menus in latest Insiders?

Version: 1.85.0-insider
Commit: 1ef160d5bc6aab85b74e34c98d7861c7727a37ec
Date: 2023-11-03T11:39:32.113Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.85.0-insider Chrome/114.0.5735.289 Electron/25.9.2 Safari/537.36

Is it only me, or did today's Insiders break all context menus?

Duplicate of #197370

/duplicate

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


add registration amount and download button

here remove showing adminid field and add number of registration and download action button for download registered participants details. I'll give you the API for get the registered users details

Add number of registration and download action button.

when click the download button, we can download the event registration details as a excel sheet.
committed these changes to the test


Prompt for password interactively

Currently, it seems to be required to store the password in plaintext in the config file when using tower-cli. My AWX installation uses LDAP accounts for user access, and hence the passwords supplied to AWX are valuable account passwords, and we do not want them stored on disk. It should be possible to prompt for account details when required, and then cache the session token without storing the password.

Yes, tower-cli should do this, also see #402


Add configuration options to skip missing report generation

Description
Showing missing movies and shows from a collection can be useful, but can also take a lot of time when those collections are large (ex: streaming collections contain 100s of movies and shows, but I would assume most people don't want to see every piece of media missing from a streaming platform).
To solve this problem, skip_missing_report and skip_<<key>>_missing_report template variables have been added to allow users to disable the generation of the missing report for specific collections.
Type of Change

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code was submitted to the nightly branch of the repository.

If this feature is deemed useful, I'll edit the documentation to add these new template variables and add the changes to this PR.

you can turn the report on and off globally using save_report
but the report isnt the actually the issue. the issue is pmm looking up each missing items which can be turned off globally using show_missing
I dont think this is needed on a per definition basis.


@damassi => link to sale on artwork partner line

For artworks that are in sales, we want to link to the sale on the partner byline (but still show the partner name, which will be something like "Phillips Auctions" once we do the migration).

👍


Launching component commands directly

I'm wondering if it'd be better if there wasn't a command type optionally returned on updates, but instead a mechanism for sending commands as futures.
sender.command(|out, shutdown| async move { });

Which would be combined with https://github.com/AaronErhardt/Relm4/pull/147 and https://github.com/AaronErhardt/Relm4/issues/148

I don't see any disadvantage. In fact, this should make things even more flexible because you can then send multiple commands.


Remove the non-functioning sanity check, add e2e test

Signed-off-by: Ville Aikas<EMAIL_ADDRESS>
Summary
Remove a non-functioning sanity check. Add an e2e test for validating creation of
an attestation and then validating it against a cue policy that will work and one that
doesn't work. Now, This is the example that we use in our documentation, and it does
now pass, but I'm not sure what all else this change might break. I reckon with these
tests we can add few more of these test cases with different payload types and keep
validating them by adding them in the test/testdata/policies. Just a beginning.
Ticket Link

Fixes
Release Note

Remove non-functioning sanity check that prevents cue policies from being evaluated.

Codecov Report

Merging #1685 (42f97af) into main (ba50ee0) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1685   +/-   ##
=======================================
  Coverage   29.29%   29.30%
=======================================
  Files         140      140
  Lines        8370     8358   -12
=======================================
- Hits         2452     2449    -3
+ Misses       5652     5642   -10
- Partials      266      267    +1

Impacted Files
Coverage Δ

cmd/cosign/cli/verify/verify_attestation.go
0.00% <ø> (ø)

pkg/cosign/tuf/client.go
62.34% <0.00%> (-0.95%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba50ee0...42f97af. Read the comment docs.


Fix Basic Types' table of contents and adds object usage note

This fixes the Basic Types' table of contents (randomly stumbled upon this while fixing the original issue).
Moreover, it adds a note to the Any section to avoid using Object in favor of object. I think it's fine to leave the example as is since you can obviously use it like this, but you shouldn't.
Fixes https://github.com/microsoft/TypeScript-Handbook/issues/1025, https://github.com/microsoft/TypeScript/issues/19908

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ndresx sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Good catch @ndresx! Just noticed this myself in the docs and was going to open a PR, just beat me to it 🙂


Solved compiler warnings C5026 and C5027 for VS2015.

Possibly solves #387

IMO these two warnings are silly. If anything, they should be disabled.

I agree that a compiler should only warn if something is done wrong; not when something could go wrong when used inappropriately. In general though, one should strive to satisfy the rule of five.

This was solved a bit differently -- if CATCH_CONFIG_CPP11_GENERATED_METHODS is defined, it also deletes its move constructor and move assignment -- so I am going to cloes this soon unless someone still has the problem.


Add linting and formatting check to CI pipeline

From @coruscating
What is the feature being requested?
As per group meeting discussion, we should add pylint and yapf google style checks to our current CI pipeline.
What are use cases for this feature?
Code will be checked for lint and format violations by CI automatically

The work by @ismirlia in Pull Request #787 closes this issue.


imagenet sample run much slower use the engine cache file

Hi,
I build this project in my NVIDIA Jetson Xavier NX device,when i run the imagenet sample with
./imagenet --network=resnet-18 images/jellyfish.jpg images/test/output_jellyfish.jpg for the first time, the cost time is about 4ms
[TRT]    ------------------------------------------------
[TRT]    Timing Report networks/ResNet-18/ResNet-18.caffemodel
[TRT]    ------------------------------------------------
[TRT]    Pre-Process   CPU   0.08611ms  CUDA   0.04842ms
[TRT]    Network       CPU   4.09130ms  CUDA   3.91024ms
[TRT]    Post-Process  CPU   0.11168ms  CUDA   0.11120ms
[TRT]    Total         CPU   4.28910ms  CUDA   4.06986ms
[TRT]    ------------------------------------------------

but after that each time i run the same command ,the total cost time is over 22ms
[TRT]    ------------------------------------------------
[TRT]    Timing Report networks/ResNet-18/ResNet-18.caffemodel
[TRT]    ------------------------------------------------
[TRT]    Pre-Process   CPU   0.09654ms  CUDA   0.19050ms
[TRT]    Network       CPU  24.41387ms  CUDA  23.46602ms
[TRT]    Post-Process  CPU   0.10746ms  CUDA   0.10650ms
[TRT]    Total         CPU  24.61787ms  CUDA  23.76301ms
[TRT]    ------------------------------------------------

after i read the code, i found that difference between the first time and the latter ones : the sample will generate a engine cache file networks/ResNet-18/ResNet-18.caffemodel.1.1.7100.GPU.FP16.engine, and after that the sample will load the .engine file instead of build engine from caffemodel;
when i delete the networks/ResNet-18/ResNet-18.caffemodel.1.1.7100.GPU.FP16.engine file, and run the command again, the cost time comes back to 4ms.
so i concerned that which cost time is the real one of the resnet-18 sample and why this appended?
environment of the  NVIDIA Jetson Xavier NX  detected by jetsonUtilities is
NVIDIA Jetson Xavier NX (Developer Kit Version)
 L4T 32.4.2 [ JetPack 4.4 DP ]
   Ubuntu 18.04.4 LTS
   Kernel Version: 4.9.140-tegra
 CUDA 10.2.89
   CUDA Architecture: 7.2
 OpenCV version: 4.1.1
   OpenCV Cuda: NO
 CUDNN: <IP_ADDRESS>
 TensorRT: <IP_ADDRESS>
 Vision Works: <IP_ADDRESS>1
 VPI: 0.3.7

Hi @sky-fun, I think it has to do with the dynamic clock rates.  On the first run when the TensorRT engine is created, the CPU/GPU clocks are already spun up, because TensorRT was running optimizations.   But on the second run when the TensorRT engine is simply loaded from disk, the CPU/GPU clocks are still low or idle.
You can try running sudo jetson_clocks beforehand, and the processor clocks will stay at their maximums.
Also processing a single image one time isn't great way to measure sustained performance.   Instead, I recommend you run it on a camera feed or a video file to get the realtime performance.

@dusty-nv , thanks, after i run sudo jetson_clocks, the cost times of using caffemodel and engine file are barely the same;
i will close this issue.
Ps.
By saying that i need to run it on a camera feed or a video file get the realtime performance,do you meaning decode the video will affect the performance， or performance of different images can be very different？


Hide specific relationships or add option to remove not defined relationships inside the Resource

Description
Hello,
we encountered an error that led back to the documentation. It isn't a bug from this package it was more a misunderstanding of how this package will handle relationships.
In the first implementation, we got only models and relationships that would be shipped with the model/API call. After some more work on the project, we got to the point where we had some models that would not be exposed to any api but had relationships with models that were exposed. Like a company that has several settings that don't affect any frontend/API but are a needed relationship. So company <-> settings. This Relation should not be exposed to the API yet.
It affects lines 76 to 116 in the file src/Http/Response.php it would be nice if there was an option to hide all relations that could not be mapped to a Rest Resource. The default behavior could be still that it would throw an exception that the given resource() is null on line 92 and with the option set to true the relation would be removed from it until it is defined in the Rest-Resource.
At the moment those lines work well with relations that return null and the collection will get { key: null } but not with not defined relationships inside the Resource which are defined in the model. Calling the delete route will trigger an exception with not missing defined relationships like that but it will deleted the entry successfully.

Hello @Nowocyn,
Could you give me an example to reproduce this ? I'm not quite sure what you mean, this might be kind of a bug if the package is misleading


fix(condition) do not execute target if a condition fails

Fix #526
This PR revamps what I broke in #470:

No more updating the pipeline configuration (as it's only required after source execution: there is no point in rendering the template after each condition as for today)

Test
To test this pull request, you can run the following commands:
cp <to_package_directory>
go test

Additional Information
Tradeoff

Potential improvement

@dduportal  it's still in draft mode, are you waiting for something?

@dduportal it's still in draft mode, are you waiting for something?

Yep, my fix does not correct the issue + there is a edge case that I want to test manually.
I wanted to add an e2e test to cover this case but it's not mandatory (I would prefer to delay the e2e).

Added an E2E "basic suite"
Took your feedback in account + removed the "config.update" as it is not needed

Very nice for the e2e test


src/./zmq_van.h:122: there is no socket to node 9

For bugs or installation issues, please provide the following information.
The more information you provide, the more likely people will be able to help you.
Environment info
Operating System:Ubuntu 14.04
Compiler: gcc 4.9.4
Package used (Python/R/Scala/Julia):python  python2.7
MXNet commit hash (git rev-parse HEAD):e036c24632fa6ed66b0f152df8902e3e2d997293
Error Message:
Please paste the full error message, including stack trace.
spark@sparkMachine1:~/mxnet/example/HCL2000$ ../../tools/launch.py -n 3 -H hosts python train_hcl.py --kv-store dist_sync
[20:57:18] src/./zmq_van.h:122: there is no socket to node 9
[20:57:18] /home/spark/mxnet/dmlc-core/include/dmlc/logging.h:235: [20:57:18] src/van.cc:126: Check failed: (send_bytes) != (-1)
terminate called after throwing an instance of 'dmlc::Error'
  what():  [20:57:18] src/van.cc:126: Check failed: (send_bytes) != (-1)
Aborted (core dumped)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/spark/mxnet/tools/../dmlc-core/tracker/dmlc_tracker/tracker.py", line 363, in <lambda>
    target=(lambda: subprocess.check_call(self.cmd, env=env, shell=True)), args=())
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'python train_hcl.py --kv-store dist_sync' returned non-zero exit status 134

Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.
I use 3 computer to train my example. I reboot the 3 computer and train it again , the error occur.
What have you tried to solve it?

I make clean_all the mxnet.
cd into the ps-lite and use the command make.
I try the standard example, the error message is the same.

it happens sometimes, probably due to zmq bug?
one easy fix is restarting the job again.

@mli
I run the command on another node which is listed in the hosts file, the message didn't show up...


[TESTED] Macos

I have tested the theme in macos, and everthing seems to be good. You can update the readme.
App: <IP_ADDRESS>8675 AppStore

Hi. Thanks for reporting the status, I'm going to update the README asap. :+1:

Hi. Thanks for reporting the status, I'm going to update the README asap. 👍

It's okay. But there is a problem with android. The input for gifs and stickers has a white background

Oh, that's bad, definitely needs to be fixed. I'm going to slightly adjust the issue title and reopen it.


Add PhpUnitDedicateAssertInternalTypeFixer

Closes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4144

[x] Update RuleSet
[x] Add integration test with PhpUnitDedicateAssertInternalTypeFixer

I intentionally created a new fixer instead of updating PhpUnitDedicateAssertInternalTypeFixer because the codes need too different logics.
I don't really like the names, they may confuse the users, any suggestion is welcome, but I would like to keep the two fixers in two different classes.

Thank you @Slamdunk.


apiKey undefined for Amplitude

For some reason, the apiKey prop isn't being passed through to the amplitude script properly.
I'm using TypeScript, so I'm wondering if the transpile step is losing context.
<!-- Layout.astro -->
<!-- ... -->
<!doctype html>
<html
	lang="en"
	transition:animate={fade({ duration: '1s' })}
>
	<head>
		<meta charset="UTF-8" />
		<meta name="image" property="og:image" content={ SHARE_IMAGE }>
		<meta name="description" content={ DESCRIPTION } />
		<meta name="viewport" content="width=device-width" />
		<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
		<meta name="generator" content={Astro.generator} />
		<title>{ pageTitle }</title>
		<Amplitude apiKey="MY_REAL_KEY_OBVIOUSLY" />
		<ViewTransitions />
	</head>
	<body>
	<!-- ... -->

I think it also has to do with this issue that me and others spotted as well.
https://github.com/Destiner/astro-analytics/issues/25
It seems like the code from Amplitude always loads, regardless and I think that implementation is just broken.

I have the same issue


Support Whatsapp message with Media

I'm using then the Twilio WhatsApp API to notify users with messages. I want to send images too. I noticed that the actual API does not support this.

Should I fork and implement this?

Created a pull request #72 with the implementation and WhatsApp testing.

Thanks for the PR. I just merged it.


"test_index_file_endianness_compatibility" isn't really about endianness

I'm not sure how you would get access to a big-endian computer, unless you have IBM Power machines somewhere? A better name is more "golden master"/"approval test" or something like that, if I understand this correctly.

I'm not sure how you would get access to a big-endian computer, unless you have IBM Power machines somewhere? A better name is more "golden master"/"approval test" or something like that, if I understand this correctly.

I agree wit your suggestions. FYI, I almost got the test working (see https://github.com/marcin-krystianc/PalletJack/blob/dev-20240104-bigendian/.github/workflows/python-ci.yml#L16-L44) but had some troubles installing pyarrow from source.
I think with some more effort it is actually doable, but I decided to abandon the idea for now.


add notice about processing time CDS

Change proposed in this Pull Request
Added a notice about the  CDS side processing time in the create_cutout example including a link where to
check the status of CDS request. To inform about why it might take a while before the download starts.

Motivation and Context
Motivated by #175

Thanks, that's a helpful link!
I've just restored the original output from the code cell, such that the output stays displayed in the documentation.


added hasRole and hasRoleAtLeast method for checking of user roles

In Laravel 5.1, this method will be useful for checking roles via Middleware parameters like below:
<?php

namespace App\Http\Middleware;

use Closure;

class RoleMiddleware
{
    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @param  string $role
     * @return mixed
     */
    public function handle($request, Closure $next, $role)
    {
        if (! $request->user() || ! $request->user()->hasRole($role)) {
            if ($request->ajax()) {
                return response('Unauthorized.', 401);
            } else {
                return redirect()->guest('auth/login');
            }
        }

        return $next($request);
    }
}

Route::get('test', ['middleware' => 'role:administrator', function() {
	return 'success';
}]);

Hmm, I'm unsure about this one as I believe that you should be simply checking for permissions within your application. Roles are more like dynamic "containers" to hold a set of permissions for a user - they can change. Permissions are concrete hooks that your application can confidently rely on.

Good point on roles and permissions. I just got this idea in relations to your menu filters.  I basically passed a set of ACL on values (permissions & roles) and check if the user can access it.
<?php

namespace App\Http\Middleware;

use Closure;
use Menu;

class AdminMenuGenerator
{
    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next)
    {
        Menu::make('main', function ($menu) {
            $menu->add('Home', 'home')->icon('home');
            $menu->add('Dashboard', 'admin/dashboard')->icon('dashboard');

            $menu->add('Menu Manager', 'admin/menus')
                ->data('acl', ['manage-menus', 'administrator'])->icon('list');

            $menu->add('Logout', 'auth/logout')->icon('power-off');
        })->filter(function ($item) {
            if (! $item->data('acl')) {
                return true;
            }

            return auth()->check() && $this->canAccess($item->data('acl')) ?: false;
        });

        return $next($request);
    }

    /**
     * Check if user can access the menu
     *
     * @param  string|array $acl
     * @return boolean
     */
    public function canAccess($acl)
    {
        return auth()->user()->canAtLeast($acl) || auth()->user()->hasRoleAtLeast($acl);
    }
}

On the other hand, I think hasRole is redundant to is function. What I basically need is a way to check if a user has at least one role. Will remove hasRoleAtLeast and put the implementation on hasRole if you would consider it. Thanks!

:+1:


Create a session using the JWTs from the hosted sign in

I'm building an Angular 5 application and would like to use aws-amplify since it's recommended over amazon-cognito-identity-js.
Given that there doesn't seem to be any pre-built components for Angular in the same way there is for React, I'd prefer to use the Hosted UI rather than handling sign up / sign up / change password, etc within my application.
When I sign in with Angular 5, I get an identity token and a refresh token. Is there any way to pass these to AWS Amplify to create a session?

In the next sprint we will have available components for angular. I will let you know when we publish those.

@NRaf Angular components have been launched, see
https://aws.github.io/aws-amplify/media/angular_guide


[FEAT] Separate movement/action locking

The current implementation of action locking leaves a lot of spells/features undefined, with no combat phase that they can actually be used in. As a result we've had to disable action locking for the time being.
While, long term, fixing each one is clearly the right solution, in the short term it might be better to separate action locking from movement locking, as movement locking already works perfectly.

Which ones are undefined? What do you have that can't be used in any phase?
If you want to disable Action Locking for a phase you can just change it's name slightly and the module will no longer recognize it (although changing the name of the Attacks phase will affect the HUD feature).
I'm not sure if I'm interested in allowing parts of Action Locking not to be used, since changing the phase names is a more efficient solution.

Hmm. I like that. I can just set the magic phase to be a magic/misc phase, then, and keep movement/attacking phases distinct.
We had enough things (4-5?) that seemed to fall outside existing phases that it didn't occur to me to take notes. I'll keep an eye out for them in the future and do an update when I run across them.
Sorry for the long delay, I only jump back to D&D stuff every few days.


expose all public FunctionHandle methods on Function

Continues work in #675 and #685:

[X] Queue
[X] Dict
[X] Volume (commit, reload, ...)
[X] NetworkFileSystem (write_file, read_file, ...)
[X] Function (all the function calling)

At this point every handle method is now exposed on the provider classes too. This means that after this PR is merged, we can swap out handle classes for providers, so that the handle classes are internal only. Off the top of my head this is roughly:

Any function created in global scope
All objects created on the app object locally
All objects created on the app object in the container

Once that's done, we should move all docs and implementation from the handle to the provider classes too

@prbot approve

Nice!


Update restricted admin

https://github.com/rancher/docs/issues/3005 and https://github.com/rancher/docs/issues/3144
Sheilagh also mentioned there's another upcoming use case to account for.

Hello @btat. Restricted admin permissions have changed since Prachi's table was created (rancher-security # 769):
Pod security policies

Restricted admin is able to manage pod security policies. They will have the same privilege as global admin for PSPs.

Node templates

Restricted admin can only manage their own node templates. Not templates created by other users.

Cloud credentials

Restricted admin can only manage their own cloud credentials. Not templates created by other users.

Could we change the documentations so these changes are reflected, please?

Hello @btat. Restricted admin permissions have changed since Prachi's table was created (rancher-security # 769):
Pod security policies
* Restricted admin is able to manage pod security policies. They will have the same privilege as global admin for PSPs.

Node templates
* Restricted admin can only manage their own node templates. Not templates created by other users.

Cloud credentials
* Restricted admin can only manage their own cloud credentials. Not templates created by other users.

Could we change the documentations so these changes are reflected, please?

Will do


Add a map search view and search utilities section to the venues search

LIIKUNTA-335:

Migrate the map view from the old Liikunta-Helsinki production version
Update the Leaflet plugins.
Split the form part from the Simple Venue Search component, so that the map search can reuse it.
Create a new search utilities section to the Venues Search page.
The search mode can be switched between the list and the map mode.

LIIKUNTA-362:

Fix the return path issues where the venue id was given as undefined.

Codecov Report

Merging #120 (d34ecdb) into main (4e6ef0f) will increase coverage by 6.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
+ Coverage   61.26%   67.53%   +6.27%
==========================================
  Files         362      200     -162
  Lines        8552     4833    -3719
  Branches     1947     1089     -858
==========================================
- Hits         5239     3264    -1975
+ Misses       3109     1436    -1673
+ Partials      204      133      -71

Impacted Files
Coverage Δ

apps/sports-helsinki/src/constants.ts

...-helsinki/src/domain/event/eventHero/EventHero.tsx

...helsinki/src/domain/event/eventQueryString.util.ts

...sinki/src/domain/search/eventSearch/SearchPage.tsx

...sinki/src/domain/search/venueSearch/SearchPage.tsx

...inki/src/domain/search/venueSearch/VenueSearch.tsx

.../domain/unifiedSearch/useUnifiedSearchVariables.ts

...-helsinki/src/domain/venue/venueHero/VenueHero.tsx

apps/sports-helsinki/src/pages/search/index.tsx

apps/sports-helsinki/src/utils/routerUtils.ts

... and 152 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr120.dev.hel.ninja :rocket::rocket::rocket:

Hobbies-Helsinki branch is deployed to platta: https://harrastukset-pr120.dev.hel.ninja :rocket::rocket::rocket:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr120.dev.hel.ninja :rocket::rocket::rocket:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr120.dev.hel.ninja :rocket::rocket::rocket:

Sports-Helsinki branch is deployed to platta: https://liikunta-pr120.dev.hel.ninja :rocket::rocket::rocket:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr120.dev.hel.ninja :rocket::rocket::rocket:

Events-Helsinki branch is deployed to platta: https://tapahtumat-pr120.dev.hel.ninja :rocket::rocket::rocket:


Please update byte-buddy to newest version

Current version comes with old version of byte-buddy which makes problems with Mockito under Java 21:
Caused by: java.lang.IllegalArgumentException: Java 21 (65) is not supported by the current version of Byte Buddy which officially supports Java 20 (64) - update Byte Buddy or set net.bytebuddy.experimental as a VM property

I just released version 2.15.0 which bumps the ByteBuddy dependency.

Thank you!


FIX #159 enum hash auto correct for % arrays

update code and tests so autocorrect for enum hash handle % array notations such as
%w[done todo archived] are well corrected

This looks good to me. Could you squash your commits into one?

👍 My bad, though it was during the merge / squash.

Thanks!


Document process for changing a Mac minion's ID and regenerating the key

@aneeshusa, this seems like the best way of getting ahold of you at the moment. I've tried just removing the old key and restarting Salt, but that doesn't cause the minion to show up in the master's unaccepted keys list. Will we have to generate keys on the master and transfer them to the minion as suggested in https://docs.saltstack.com/en/2017.7/topics/tutorials/preseed_key.html?
If you don't have time to sort this out, I can continue through trial and error, but I suspect you may already know the best practices.

Changing the ID should be sufficient; IIRC Salt will generate a new key once it sees a new minion id.
I don't remember how our install process sets the minion id, but there are two places to look:

It can be explicitly set in /etc/salt/minion (or an included file); update or add the new minion id here
Salt will cache it in the /etc/salt/minion_id file; you can delete this file.

That plus a minion restart should be sufficient, let me know if it's not working. Emailing me directly is another good way to get a hold of me. (I filter GH emails into a separate folder which I check occasionally as well.)


add support for left hand coordinate system for POI feature

Description
POI feature is not working properly if the babylon scene is not set to use right hand coordinate system.
GLTF is in right hand coordinate system while babylon scene by default is using left hand coordinate system so that babylon GLTF importer is applying some transform to the root node of imported character which breaks our POI feature angle calculation.
This change invert one of the angle calculation in POI feature if the babylon scene is using left hand coordinate system to mitigate the transform impact brought by babylon GLTF importer
Testing
Manually go through all babylon examples to verify POI feature is working properly.
Submission Checklist
I confirm that I have...

[x] removed hard-coded Cognito IDs
[x] manually smoke-tested the BabylonJS integration tests
[x] manually smoke-tested the BabylonJS demos
[x] manually smoke-tested the Three.js integration tests
[x] manually smoke-tested the Three.js demo

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It's too bad we don't have any unit tests or integration tests that target the POI feature -- in their absence, would it be worth removing the useRightHandedSystem from one of the demos (perhaps the Hello World one)?
At the very least, those demos should be updated in the sense that there's a comment in the .js files' createScene() function that says // IMPORTANT for Sumerian Hosts! (or something along those lines) that should be removed

It's too bad we don't have any unit tests or integration tests that target the POI feature -- in their absence, would it be worth removing the useRightHandedSystem from one of the demos (perhaps the Hello World one)?
At the very least, those demos should be updated in the sense that there's a comment in the .js files' createScene() function that says // IMPORTANT for Sumerian Hosts! (or something along those lines) that should be removed

Removed the useRightHandedSystem setting from Hello World demo and updated comments


Create 3 gun Illustration for 26th Event

illustrate 3 guns based on the generated pixel art by Shah

Issue moved to fragcolor-xyz/rhythm-run #65 via Zenhub