Build with OpenSSL 3

Build with OpenSSL 3.
Note that I removed nspr, nss, krb5 and ruby because they are not needed. They are needed for qt-webengine, so I'll add them there instead.
Depends on:

postgresql: https://github.com/AnacondaRecipes/postgresql-feedstock/pull/5
libcups: https://github.com/AnacondaRecipes/libcups-feedstock/pull/3
libevent: https://github.com/AnacondaRecipes/libevent-feedstock/pull/8

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:153: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:163: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_d7y_7k6h5u/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:153: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:163: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_77099yi5o0/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:153: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:163: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_c9jo0kth2u/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:153: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:163: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_ears9oy1xb/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:153: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:161: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:163: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_f4gcqljdmb/clone/recipe/meta.yaml:220: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:149: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:155: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:156: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_2bd2jbs1br/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:149: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:155: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:156: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_5d1qd8deba/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:149: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:155: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:156: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_7ebbz7bz0r/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:149: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:155: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:156: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_adzw1kev4h/clone/recipe/meta.yaml:221: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:133: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:151: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_93hannq1hl/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:133: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:151: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_fbfuewngqh/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:133: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:151: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_00rq0k3ifm/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:133: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:151: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_a16o74zipm/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:133: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:138: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:151: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:157: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:158: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:159: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:160: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:162: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
ERROR: /tmp/abs_ff_o9jvca_/clone/recipe/meta.yaml:223: has_run_test_and_commands: Test commands are not executed when run_test.sh (.bat...) is present.
Errors were found


I can't send mail on the server

Hello,
While working in the local, it doesn't work on the server.
Error: Invalid login: 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbtk 534-5.7.14 6YQOu2fx37epuJLJai4mSzLHzfrw87hFpUhNlcO6SgDJbubtLDDLORz17ibOi44w4MqmWm 534-5.7.14 cHamy1B54_C2p_L9KL0uhcu7dowd7e3pTYVA6I9CzIHIxybI2tAVGhufoulYLNITWkgMm0 534-5.7.14 wyNiTiewf-Fvwgq1yG4sCjnB3JTPatPyGucXv3ifCbOUBHpEIJu2OsA9usvoeMbNc1WKfe 534-5.7.14 cb8cfDAye4qb36vsEgHOKYdXt9BDc> Please log in via your web browser and 534-5.7.14 then try again. 534-5.7.14  Learn more at 534 5.7.14  https://support.google.com/mail/answer/78754 c18sm13481146wmd.13 - gsmtp
How can I solve this?
Regards.

Hey @yasinatesim! 👋
Could you please give us more information?

What's your mail configuration
What are you trying to do and how

It seems to be an issue in your configuration. You may find more help in the forum or Discord Server for this kind of question.

But this's also working on the local server.
Would you like to send a mail at the bottom?
https://yasinates.com/#contact-link

Yes, I updated .env file in production.
.env file content at the bottom;
HOST=<IP_ADDRESS> PORT=3000 NODE_ENV=production APP_URL=http://${HOST}:${PORT} CACHE_VIEWS=false APP_KEY=myApiKey DB_CONNECTION=mysql DB_HOST=<IP_ADDRESS> DB_PORT=3306 DB_USER=MyUsername DB_PASSWORD=MyPassword DB_DATABASE=myDatabaseName SESSION_DRIVER=cookie MAIL_CONNECTION=smtp MAIL_HOST=smtp.gmail.com<EMAIL_ADDRESS>MAIL_PASSWORD=myPassword MAIL_PORT=587
While running this information locally, the server here (https://yasinates.com/#contact-link) gives an error.

What happens if you remove node_modules and package-lock.json file on your local and re install all dependencies

I tried Local, it works. I tried it on Server but it does not work

was was the solution? im getting error also. Pls share

Check your gmail account name and password.
Log in to your google account in your browser.
Try again.
If it does not work, check your gmail inbox to find a security alarm message from google.
Enable unsecured application. The google mail will show you how to do that.
Try again. It should work.
If not work, make sure you logged in to your google account and keep your browser open.


customize date

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
no
Describe the solution you'd like
I can only choose the date of the event or the days counted. The date is formatted to "DAY, DDMMMYYYY", but I want it in a shorter form, i.e.: DD/MM/YYYY or DD/MM.
Thanks!
Describe alternatives you've considered
No response
Additional context
No response

@purewhitedesign you can now choose between "counter" the predefined "default" date format and the new "custom" format option. After that there will a new text field where you can add a date format like 'yyyy/MM/dd' or 'dd/MM'
Available

day: d, dd
month: M, MM
year: y, yy, yyy, yyyy

This is awesome! Thank you so much! You will get a coffee for sure 💯

It's rock !

Thank you !
👍

Yes, now it fit's perfectly into my phone display!

Now, we could try to get another type of format, like "shortday, dd.MM." 😄
Mi, 13.03. for example.


[Debugger] Cannot evaluate object method and self inside method

Description:
Cannot evaluate object method and self inside method in VSCode. This happens in methods and init method

Sample code to reproduce
https://gist.github.com/keizer619/19e84eb3462f65ba6bd79a53ee865012#file-main-bal-L81

This is happening due to https://github.com/ballerina-platform/ballerina-lang/issues/27747 where we can not retrieved the value of self instance, as it does not get added into the variable table during the codegen.


fix for upstream/#116

Issue
#116
Description of changes:
Fix for #116
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hmm,
Fun fact, S3 URIs aren't strictly speaking URIs because they can contain characters that are illegal in URIs. For example in an S3 bucket you can create
"file with spaces.txt"
"file+with+spaces.txt"
"file%20with%20spaces.txt"
All of these will be unique files and their respective URIs are:
s3://bucket/file with spaces.txt
s3://bucket/file+with+spaces.txt
s3://bucket/file%20with%20spaces.txt
And S3 will not consider these to be the same URI (which is fun)
As you have spotted, implementations of the Path interface do need to return URI and that class will require URL encoding. URI is final (as it should be) so we cannot override this.
I need to  add a note into the README.md to explain the potential differences that people may see and advise that, where possible people should where possible avoid using characters that need to be URL encoded so they don't see these conflicts.

Fun fact, S3 URIs aren't strictly speaking URIs because they can contain characters that are illegal in URIs. For example in an S3 bucket you can create

ah interesting. we need to think a little bit more than. Paths.get(URI.create("s3://bucket/file with space")); breaks because URI.create() fails. We need to figure out then how Paths.get(uri) translates into a S3Path object and make sure it works if the urls is encoded.

I amended the javadoc, @markjschreiber does it work?
What I think we should be clear about is that a URI has a defined syntax, specified in one or more RFCs. It is somehow improper to say that "s3://something with space" is a S3 URI (of course we can use that expression for simplicity).
Anyway, like I tried to say in the comment, the current implementation is coherent:
S3Path p = (S3Path)Paths.get("s3://mybucket/with+blank+and+%25"); // -> s3://mybucket/with blank and %
String s = p.toString; // -> /mybucket/with blank and %
URI u = p.toUri(); --> // -> s3://mybucket/with+blank+and+%25
...
String s = p.getFileSystem().get("with space").toString(); // -> /with space


Client validation for AssertThat in EditorTemplate

I can't seem to get my client validation running correctly in my editor template with an AssertThat. Right now, this page just does a full postback and displays a blank ValidationSummary. I'm not sure if it works with EditorTemplate since my names are
<input name="ClassName[0].PropertyName1" />

etc.  When I look at the rendered HTML, all I see is "PropertyName1 <= PropertyName2".  I'll show details below:
    public class ViewData
    {
        public List<TakeOutOption> TakeOutOptions { get; set; }
        public decimal TotalAmountEligibleToTakeOut { get; set; }
    }

    public class TakeOutOption
    {
        public decimal CurrentValue { get; set; }
        [AssertThat("AmountToTakeOut <= CurrentValue", ErrorMessage = "Amount must not be more than the Current Value")]
        public decimal AmountToTakeOut { get; set; }
    }

Editor Template:
    @model Models.TakeOutOptions

        @Model.CurrentValue.ToString("C")@Html.HiddenFor(x => x.CurrentValue)
        @Html.Bootstrap().TextBoxFor(m => m.AmountToTakeOut).Value(Model.AmountToTakeOut > 0 ? Model.AmountToTakeOut.ToString("N2") : "").HtmlAttributes(new { data_calculate_total = true }).Prepend("$")

View:

                Current Value
                Amount To Take Out

            @Html.EditorFor(x => x.TakeOutOptions)

                @Model.TotalAmountEligibleToTakeOut.ToString("C")

                     @Html.Bootstrap().TextBoxFor(m => m.TotalAmountEligibleToTakeOut).Readonly().Prepend("$").Class("remove-disable-look")

The HTML Output ( I only pasted in the part where the validations are set ) :

            $45.00<input name="TakeOutOptions[0].CurrentValue" id="TakeOutOptions_0__CurrentValue" type="hidden" value="45" data-val-required="The CurrentValue field is required." data-val="true" data-val-number="The field CurrentValue must be a number.">

                $
                <input name="TakeOutOptions[0].AmountToTakeOut" class="form-control" id="TakeOutOptions_0__AmountToTakeOut" type="text" value="" data-val-required="The AmountToTakeOut field is required." data-val="true" data-val-number="The field AmountToTakeOut must be a number." data-val-assertthat-fieldsmap='{"AmountToTakeOut":"numeric","CurrentValue":"numeric"}' data-val-assertthat-expression="AmountToTakeOut <= CurrentValue" data-val-assertthat-constsmap="{}" data-val-assertthat="Amount must not be more than the Current Value" data-calculate-total="True">

            $55.00<input name="TakeOutOptions[1].CurrentValue" id="TakeOutOptions_1__CurrentValue" type="hidden" value="55" data-val-required="The CurrentValue field is required." data-val="true" data-val-number="The field CurrentValue must be a number.">

$
                <input name="TakeOutOptions[1].AmountToTakeOut" class="form-control" id="TakeOutOptions_1__AmountToTakeOut" type="text" value="" data-val-required="The AmountToTakeOut field is required." data-val="true" data-val-number="The field AmountToTakeOut must be a number." data-calculate-total="True" data-val-assertthata-fieldsmap='{"AmountToTakeOut":"numeric","CurrentValue":"numeric"}' data-val-assertthata-expression="AmountToTakeOut <= CurrentValue" data-val-assertthata-constsmap="{}" data-val-assertthata="Amount must not be more than the Current Value">

Is there a better way to do this to add validation to AssertThat the amount typed in is <= the amount allowed?

Hi. To be honest I don't know the answer right now. It can be an enhancement request (or bug) as well. This issue needs some investigation.

This was driving me crazy, so I moved it into its own project and removed all of my addons except Expressive Annotations and it seems to work as intended.  I type in an amount > my CurrentValue and I got the client side validation.  I'm guessing it's something else on my page that is not working.  Having said that though, the error messages are all generic so I am having to over-ride the erorr message property in the Editor Template otherwise, if there are 8 rows and you type in an invalid amount in all 8 rows, you get 8 of the same errors in the summary.
Thanks for looking.

Good to hear that.
I'd like to add that, if something is still not working as expected in some areas, you can always prepare sample project where such an issue can be reproduced (that project should compile and be as simple as possible), and attach it to this discussion. It would be easier to have it here.
Regards

In the next version (2.6.0), client script is going to have ea.settings.debug option (turned off by default). If activated, some messages will be displayed to the web console, about what expressions are going to execute right now, in which context, for which fields, also what dependency triggers are fired if any, and finally some warnings if detected. Maybe it will be helpful in such a cases.

This is great news.  Thanks!


License is 404

A License link at the bottom of your README.md returns 404.

Thanks, now fixed: https://raw.githubusercontent.com/crisp-im/crisp-sdk-web/master/LICENSE


fix blockchain defaults for config-less dapps (develop)

Additional fixes for config-less dapps such as the simple template
Cool Spaceship Picture

Please wait for #845 before merging this.


fs: open: fix zfp flags not set when calling truncate

Fixes #74218

I am sorry for this mess, I didn't switch branch before pushing. Reversing rn


force close

hi
when i click  cancel button , navigation app is close , i need when click cancel button  , go to another page

same issue

same issue

Stale issue message

Same issue, have you managed to fix it?

No i cant
On Sun, Jun 23, 2024, 13:00 Yoav Slama @.***> wrote:

Same issue, have you managed to fix it?
—
Reply to this email directly, view it on GitHub
https://github.com/eopeter/flutter_mapbox_navigation/issues/338#issuecomment-2184917776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK6FLNWN6YBARF6BR6O36B3ZI2ITNAVCNFSM6AAAAABJYGTUZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUHEYTONZXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Just search for CustomInfoPanelEndNavButtonBinder.kt
and delete activity.finish(), for example I did a new event called NAVIGATION_USER_CANCELLED and handle the actions with this event.

        return object : UIComponent() {
            override fun onAttached(mapboxNavigation: MapboxNavigation) {
                super.onAttached(mapboxNavigation)
                button.setOnClickListener {
                    //mapboxNavigation.stopTripSession()
                    PluginUtilities.sendEvent(MapBoxEvents.NAVIGATION_USER_CANCELLED)
                    //activity.finish() //--> this
                }
            }
        }


Vulnerability roundup 78: glibc-2.27: 1 advisory

search, files

[ ] CVE-2019-19126 CVSSv3=3.3 (nixos-19.09, nixos-unstable)

Scanned versions: nixos-19.09: 45ea6092203; nixos-unstable: 3140fa89c51. May contain false positives.

See also: #73638, #70093, #59155, #58263, #57143

nixos-unstable is at 2.31.
19.09 is EOL.
Closing.


Added user dirs

Added user dirs to search path. This allows users without admin rights to use the GTM plug-in.
Also did some cleanup (setting package private where appropriate, etc).

@dnedrow Looks good. Thank you!  I'll publish the updated plugin today.


Revalidate and modify league related actions

Check actions in

League manage list
league dashboard
club dashboard

Validate

is action allowed for role and in current state

Write Tests to verify this

redesign the league dashboard teams card:

use a datatable to show al l in one table
design like

button: CLUB, button: TEAM
or
Rbutton ASSIGN, button


Sampled Raytrace SIS gives twisted image on develop

All the models seem to work on master, so something has gone wrong with Sampled Raytrace on develop, and not in one of the most recent commits.

The problem was swapping the partial derivatives. Solved.


Its git user is persisted in the config (for the current job)

Since #7, if git config user.email is empty, the action will set user.email and user.name. This is persisted even after the step.
Ideally instead this should not happen.
I tried passing the git author via ENVs but I couldn't get exec/execFile to use them: #7@891d43e I don't know why this happens. The envs work correctly when git is run outside Node.
Any help would be appreciated.

If that does not happen, can you test by explicitly passing in the environment variables to execFile()?

Tried, no luck: https://github.com/fregante/daily-version-action/commit/72e74674d203b4c796fc775cf6a8e0027cbb15a5

How about inline environment variable declaration format?
Example: https://git-scm.com/docs/git-tag#_on_backdating_tags

I also tried setting the ENVs outside node, still no luck: https://github.com/fregante/daily-version-action/commit/4e39d6f6c742166d552de4091589eef9256cd278
It makes no sense. The only thing I can think of is to use a different way of calling the git command. Maybe spawn?

Semi-related side note: the awkward part is that git commit reads the ENVs but git config user.email does not.
I don't see any way to detect the user’s email other than doing this manually:
GIT_AUTHOR_EMAIL || GIT_COMMITTER_EMAIL || git config user.email


Please release a new version of azure-servicemanagement-legacy

Package Name: azure-servicemanagement-legacy
Package Version: 0.20.6
Operating System: Ubuntu 20.04
Python Version: 3.8

Describe the bug
0.20.6 of azure-servicemanagement-legacy in pypi contains code that uses the reserved keyword async. This has been fixed in recent versions of this repository, but the pypi package has not been updated, and is thus unusable with Python >= 3.7.
To Reproduce

Use python >= 3.7
pip install, import azure-servicemanagement-legacy
observe SyntaxError from use of reserved word async in azure/servicemanagement/servicemanagementclient.py (since fixed in this repo)

Expected behavior
The code that currently exists in this repo should be released in pypi as a new version of the azure-servicemanagement-legacy python package.
Additional context
This will enable users of Python >= 3.7 (e.g. anyone on Ubuntu 20.04, which uses 3.8 by default) to use the package.

Thanks @codyshepherd for reporting this, @nickzhums @RodgeFu can you take a look at this

The last SDK release is 3 years ago, add "service attention" label to involve service team to confirm whether their swagger is ready to release the new version Python SDK. thanks.

@RodgeFu this SDK is not really owned by a service team, this is the ASM old endpoint (before ARM). I indeed fixed some async keyword, but I thought it was impacting tests only, I will do pass to assess what's broken.
Being the deprecation of that SDK and the focus on ARM now, I don't think it worth me passing too much on passing the context, I will try to fix it myself for customer's sake. Please ping me if you have question

Exact stacktrace:
>>> from azure.servicemanagement import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\lmazuel\Documents\GitHub\asmtest\lib\site-packages\azure\servicemanagement\__init__.py", line 27, in <module>
    from .servicemanagementclient import parse_response_for_async_op
  File "C:\Users\lmazuel\Documents\GitHub\asmtest\lib\site-packages\azure\servicemanagement\servicemanagementclient.py", line 372
    def _perform_put(self, path, body, async=False, x_ms_version=None):
                                       ^
SyntaxError: invalid syntax

Released: https://pypi.org/project/azure-servicemanagement-legacy/0.20.7/


[EmbeddedAnsible] Add parameter support for jobs

Saves the params for each key/val as a OrchestrationStackParameter record, similar as to what was done in manageiq-providers-ansible_tower.
This was something that we didn't get to for the ivanchuk release.
Links

Similar work done in previous merged PR:

https://github.com/ManageIQ/manageiq/pull/19232
https://github.com/ManageIQ/manageiq/pull/19247

LGTM, overall...do we need to be concerned about any password fields?  Is there a way to tell those apart?

Is there a way to tell those apart?

I don't think there is, though I wrote this half a year ago now...

do we need to be concerned about any password fields?

I think we do, and I feel like we did have this conversation recently somewhere else... but I forgot where/when...


Part two

Pull Request Test Coverage Report for Build 37

167 of 257 (64.98%)  changed or added relevant lines in 12 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-23.9%) to 76.104%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/MoonWalkSpace.class.st
14
22
63.64%

repository/IngSoft2-Model/Board.class.st
43
53
81.13%

repository/IngSoft2-Model/Game.class.st
26
38
68.42%

repository/IngSoft2-Model/SpacesGenerator.class.st
0
60
0.0%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/Game.class.st
2
81.33%

Totals

Change from base Build 23:
-23.9%

Covered Lines:
293

Relevant Lines:
385

💛  - Coveralls


dnsmasq integration

This pull request fixes issue #182, #163 and #127.
The nginx resolver property specifies which DNS server nginx will use when resolving addresses.
The problem with the resolver is that by design nginx doesn't follow the system settings including the /etc/hosts file. In order to have a proper DNS resolution that respects the system DNS settings a new dependency needs to be introduces: dnsmasq.
dnsmasq is a DNS server that runs locally, can listen on a port (I decided to use 8053 for Kong), and can provide DNS resolution reading both /etc/hosts file and resolv.conf. It is the same dependency that we use for the official Kong Dockerfile (https://github.com/Mashape/docker-kong/blob/master/Dockerfile#L17).
I have been searching for another solution but everybody seems to be using dnsmasq for this use-case.
So this now works, and if in the future a better way to handle this issue will be found, I will be more than happy to remove the dependency to dnsmasq (which works very well by the way).
I will also update the distributions in a future commit to include dnsmasq as a dependency.

Do you think this may also fix #195?

@montanaflynn not sure, we need to replicate and test that separately after this pull request has been merged into master

I've been unable to replicate it, maybe he could build the new version from source and test for us.

The following lines could also be deleted: https://github.com/Mashape/kong/blob/master/kong/dao/cassandra/factory.lua#L27-L38

This pull request is not finalized, I still need to implement some fixes.

It looks ok so far, except minor things I'll probably update for the CLI.

I am very sad, we keep adding more and more dependencies to Kong, and they become more and more expansive (dnsmasq requires a port and runs as yet another process, sigh...)

I tried playing with lua-resty-dns with no success so far, so I see no other solution.

On a side note:
We should stop relying on the Faker, as it makes the test data very sparse. Some tests end up using the same APIs as others tests and we lose isolation.
We need to use the spec_helper to pass directly through the DAO, and insert only the needed for the current tests at setup. And the same APIs need to be dropped at teardown.

Coverage decreased (-0.12%) to 65.6% when pulling 9b49e446f81a0c6feaf30802955fc28a107fe599 on fix/dns into 0382513d1c87c1ecd014efbcc6a508b6302eb092 on master.

On a side note I will squash all this commits - basically locally it works, on Travis is failing for some reason.

Coverage increased (+0.04%) to 66.36% when pulling fb5d6ca07fd0409b9d0f7a5a78086c80ebc463f8 on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage increased (+0.04%) to 66.36% when pulling ed4f567e31412f28ff19cd72eebded4de515c525 on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage increased (+0.04%) to 66.36% when pulling 5911138cc87c991aaf62a377fe051006bc8a9404 on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage increased (+0.04%) to 66.36% when pulling 6cac000a54064210de6e8c0907afcb5757bc9bc9 on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage increased (+0.04%) to 66.36% when pulling 6cac000a54064210de6e8c0907afcb5757bc9bc9 on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage decreased (-0.01%) to 66.31% when pulling 845bf5986065a10ea48a1405b874a320836697aa on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Coverage decreased (-0.01%) to 66.31% when pulling 845bf5986065a10ea48a1405b874a320836697aa on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

@thibaultCha if it looks good I can merge

I'm having an error when I try to run it:
kong|fix/dns ⇒ bin/kong start
[WARN] No configuration at: /etc/kong/kong.yml using default config instead.
[INFO] Using configuration: /usr/local/lib/luarocks/rocks/kong/0.2.1-1/conf/kong.yml
[INFO] Proxy port.........8000
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=<IP_ADDRESS> port=9042 timeout=1000 keyspace=kong
[INFO] Connecting to the database...
[ERR] /bin/bash: /usr/local/sbin/dnsmasq: No such file or directory

@thibaultCha yes, I need to update the distributions but that is in another branch. The new distributions will include dnsmasq.
Also I will need to update the website to list the new requirement, and to document a new configuration property dnsmasq_port.

Yeah makes sense, it's kinda late here lol, ok nothing to say otherwise, sounds good

Adding some tests to increase the coverage, then I will merge.

Coverage increased (+0.2%) to 66.51% when pulling<PHONE_NUMBER>f35420caf0c35e12a5f9647eb3c77d on fix/dns into 8acfe1d1451ca5761057735cc89dd199732f28b6 on master.

Related to https://github.com/Mashape/getkong.org/commit/7c54540c179091c951191abfb1a3656b81570ccb and


Close issues to deprecated toolboxes

To clean out the Issues list for this repo we should be marking and closing the issues related to them.
Expected Behavior
Remove the following 20 Issues relating to deprecated toolboxes

[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/480
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/471
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/468
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/467
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/463
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/444
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/431
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/429
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/426
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/414
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/403
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/386
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/379
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/378
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/363
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/327
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/309
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/290
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/257
[x] - https://github.com/Esri/solutions-geoprocessing-toolbox/issues/105

Current Behavior

Possible Solution

Add a comment to the issue:

The tool/toolbox associated with this issue has been deprecated and is no longer actively supported. Earlier versions of this toolbox will still be available from previous Releases

Remove the any other process or bug labels and add the following:

4 - Done
B - Known Issue

Close the issue

Completed.


[Challenge] Ignoring predictions although they are in test cities + panorama images

Hiya,
Two more questions re challenge evaluation.

We receive the following message for ~60 query images (full list below): "Ignoring predictions for B55p4NnNAh1-Y8sOBha3NA at line 42. It is not in the selected cities". I checked and "B55p4NnNAh1-Y8sOBha3NA" is contained in the athens query images. Is the test set on the server diverging from the test set given out?
We also get "Some of your predictions are not in the database for the selected task [...]. This is probably because they are panorama images. They will be ignored in evaluation" -> Indeed I checked and the images are panoramas. Are the queries associated to these predictions completely removed from the evaluation process or what does "ignore" mean?

Ignoring predictions for B55p4NnNAh1-Y8sOBha3NA at line 42. It is not in the selected cities
Ignoring predictions for Qj0DPkWJUZV8tfPjKDAIhQ at line 183. It is not in the selected cities
Ignoring predictions for P-cjCsztzXwCRb2VwYONXQ at line 198. It is not in the selected cities
Ignoring predictions for 46Y2uYU_qHCbWRxjAbuZVw at line 394. It is not in the selected cities
Ignoring predictions for AC00dsAUt3p4-PlppbcCNA at line 558. It is not in the selected cities
Ignoring predictions for nLeBb_hgrQLilzWX_hn1Jw at line 678. It is not in the selected cities
Ignoring predictions for N6crkK6U_vTEMP9O2ZY9Qg at line 679. It is not in the selected cities
Ignoring predictions for 4km_uFuxPA-eIPTUSqrZIQ at line 685. It is not in the selected cities
Ignoring predictions for 74NTOmTmmnfkRJ2qlcLPCg at line 687. It is not in the selected cities
Ignoring predictions for QCLiybp5TS7HneAJfGMycg at line 689. It is not in the selected cities
Ignoring predictions for xqoli-E3rRgo-Hb81l7rT2 at line 690. It is not in the selected cities
Ignoring predictions for A1nsEM4NVTDSfAranGb3e_ at line 693. It is not in the selected cities
Ignoring predictions for YTkY36z6aysIGjf-XXw3QL at line 696. It is not in the selected cities
Ignoring predictions for VRTBJkkyq8LZw30lgJOYLQ at line 697. It is not in the selected cities
Ignoring predictions for aw9nP0itM_5E3e18z4l1Lw at line 698. It is not in the selected cities
Ignoring predictions for 5JzPKfo7VGQJgiAo47jM3g at line 699. It is not in the selected cities
Ignoring predictions for 9K4o7qUD6liUTi5tq9JCIw at line 700. It is not in the selected cities
Ignoring predictions for CQIf3WY6eFKA7nwR2xEL9Q at line 701. It is not in the selected cities
Ignoring predictions for RJ94yTIEtpOq5S3oMqYlUQ at line 703. It is not in the selected cities
Ignoring predictions for 3muZuCNoYLPq85AsK26Big at line 704. It is not in the selected cities
Ignoring predictions for Ml8AB7ONMrXyAf9OLBZJ-Q at line 706. It is not in the selected cities
Ignoring predictions for Hm9ah7EXyLYQwYqe_-SDmw at line 707. It is not in the selected cities
Ignoring predictions for 04jec_ilMrb8QfDp80G4dw at line 710. It is not in the selected cities
Ignoring predictions for Hv4AyQZ5G2FsyNyDaUhznQ at line 711. It is not in the selected cities
Ignoring predictions for OXdJ03v_cpf_sOvxpr99Bw at line 714. It is not in the selected cities
Ignoring predictions for d64mHbDDlhx4U3xxV3Nthg at line 715. It is not in the selected cities
Ignoring predictions for 0nBECBLVAgxy9rosfZP-Dg at line 717. It is not in the selected cities
Ignoring predictions for 9DTBAM0SeMxAMOn5433b2Q at line 718. It is not in the selected cities
Ignoring predictions for N2pAaPu47ryJWflWjhCpyQ at line 719. It is not in the selected cities
Ignoring predictions for u4pgo8LWD5nbLSO71YgrWA at line 720. It is not in the selected cities
Ignoring predictions for UCbwF47OVq7yMuzj2U0vgw at line 722. It is not in the selected cities
Ignoring predictions for pPQUNtR3yNp2ssnMdkqiIw at line 725. It is not in the selected cities
Ignoring predictions for liqAuW1u_vNa1ue9Td2Ltw at line 726. It is not in the selected cities
Ignoring predictions for as5UiJTaMGybf1PW7GS66g at line 727. It is not in the selected cities
Ignoring predictions for JOqViqeZ_Jsms84Ov5p40A at line 728. It is not in the selected cities
Ignoring predictions for fFYh5sPLc0cTBKubjL5Nnw at line 730. It is not in the selected cities
Ignoring predictions for Jdo5SyHJkeKfIvKRrL3u7g at line 732. It is not in the selected cities
Ignoring predictions for t8ajBUgabicusgtfZATv7Q at line 733. It is not in the selected cities
Ignoring predictions for 2IZYu_QoPDlHMM1NeKROuA at line 734. It is not in the selected cities
Ignoring predictions for 7UncugdfpZcmE0I5kaAnrQ at line 735. It is not in the selected cities
Ignoring predictions for wTJeqUgQNu3ncKFcQYoSOQ at line 736. It is not in the selected cities
Ignoring predictions for PNIu0dsY5GQLTJt2UdecTg at line 737. It is not in the selected cities
Ignoring predictions for ATu5gw5brpT0WuGPndRIQQ at line 738. It is not in the selected cities
Ignoring predictions for P9_JBSwBkYpJphg67IviPw at line 740. It is not in the selected cities
Ignoring predictions for KXxXtr0OiUcC8lxrztxQXA at line 741. It is not in the selected cities
Ignoring predictions for TRrVZQ-gI5SpuVngPWqWoA at line 747. It is not in the selected cities
Ignoring predictions for IrVCAePVHes4VoFteA5Epg at line 748. It is not in the selected cities
Ignoring predictions for CuS2xp-s4WNh9gwfPPP59w at line 749. It is not in the selected cities
Ignoring predictions for Y8TcQHaVeIQtA5bhoaAAwA at line 751. It is not in the selected cities
Ignoring predictions for dKmqPdm_908QQdVkTJ0yFQ at line 755. It is not in the selected cities
Ignoring predictions for NCS7bxeaz99oBV_RaMqKOQ at line 758. It is not in the selected cities
Ignoring predictions for HiATUbk6BWLVnHuYN2gBtQ at line 765. It is not in the selected cities
Ignoring predictions for y5XDC6bVZX0VWUEinJVEfM at line 767. It is not in the selected cities
Ignoring predictions for 0g_q2e68f_0RtBnb2EWIAJ at line 768. It is not in the selected cities
Ignoring predictions for 566X0ZIVNfbechJqbQ-4Ag at line 770. It is not in the selected cities
Ignoring predictions for uFVUTv-mgQdI-AaHx_pINA at line 773. It is not in the selected cities
Ignoring predictions for rhB2az2WAH6TsZi2ykZV88 at line 774. It is not in the selected cities
Ignoring predictions for oyl8jyAL10V91bGpFwIjQw at line 777. It is not in the selected cities
Ignoring predictions for 5OfWYXU5PyeEd4CNhvbTDg at line 778. It is not in the selected cities
Ignoring predictions for Dk0klQdCgLmGj3aN6_YE0P at line 780. It is not in the selected cities
Ignoring predictions for 0Wo8KBGc9Gn-rCmb2I2SYO at line 783. It is not in the selected cities
Ignoring predictions for kus39RdNaE_b00jhSuHedQ at line 784. It is not in the selected cities
Ignoring predictions for qX6ZYHxaAYSgV7tZst-lKQ at line 785. It is not in the selected cities
Ignoring predictions for l2V0e3Jg1sJOF8eUjjCgfw at line 786. It is not in the selected cities
Ignoring predictions for DY-Nsorqppy3EgLs2dWSRw at line 788. It is not in the selected cities
Ignoring predictions for oksKmhQaall1gj7exJNm_c at line 789. It is not in the selected cities
Ignoring predictions for InfVOLHXeJsr1LNK4TJuLw at line 1163. It is not in the selected cities

About panoramas: they will be ignored, meaning that if you submit e.g. 10 predictions and two of them are panoramas, they will be removed from the list of your predictions and won't affect the scores. We didn't properly document this so you might be at a disadvantage if you only submit 5 predictions (since we are scoring based on the top-5 recall). I will update the docs to inform about this. Thanks.
About the other errors: we're looking into it.

About the other error ("It is not in the selected cities"). The TL;DR is: don't worry about it.
It is either:

a panorama
an image in the query that has no positive match (at 25m) in the database

Sorry for the non-descriptive error message. We have updated the evaluation script in this repository to improve these, but we won't update the running challenge since we are close to the deadline - so you will still get the low-signal errors for now.

Thanks @mlopezantequera


Get Joint Name and its x,y,z position

Hey, when I do console.log(joint) I only see depth, color, camera position however I want the object to display JSON objects like:
Name: Head
x=-0.2126
y=0.523
z=0.2323
Currently, it's like this:

But I want it like (different code):

You're best bet would be to log the full body object so that you can see the array of joints rather than just logging the joint itself.


Feature Request: Add support for an image placeholder in chat - Reported by @mdneyazahmad

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Load big size image or any image on the slower network

Expected Result:
Image placeholder should display. Something like a loading spinner
Actual Result:
Blank square displayed
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.36-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/152626116-ec43cb1e-dd0e-4da9-92f5-ec8442b0aef6.mp4
Expensify/Expensify Issue URL:
Issue reported by: @mdneyazahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1643212660496300
View all open jobs on GitHub

Triggered auto assignment to @nkuoch (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @mallenexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Proposal
Proposing as I reported this issue
We need to add a loading state to track when the image is loaded. Image component accepts a prop onLoadEnd which is fired when the image is successfully loaded or it has failed. We set loading to false when it is fired. All changes are made in file src/components/ImageWithSizeCalculation.js.
+    constructor(props) {
+        super(props);
+
+        this.state = {
+            loading: true,
+        }
+    }

Now, conditionally display the loading indicator.
-import {Image} from 'react-native';
+import {Image, ActivityIndicator} from 'react-native';

+import themeColors from '../styles/themes/default'

     render() {
         return (
+            <>
                 <Image
                     style={[
                         styles.w100,
                         styles.h100,
+                        this.state.loading && styles.dNone,
                         this.props.style,
                     ]}
                     source={{uri: this.props.url}}
                     resizeMode="contain"
+                    onLoadEnd={() => this.setState({loading: false})}
+                />
+                {this.state.loading && (
+                    <ActivityIndicator
+                        size="large"
+                        color={themeColors.textSupporting}
+                        style={[styles.flex1]}
+                    />
+                )}
+            </>
         );
     }
 }

Result
https://user-images.githubusercontent.com/77761491/152679222-1fba78b9-6929-4785-accc-19a47ba3e196.mov

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (Exported)

Triggered auto assignment to @mountiny (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Job posted https://www.upwork.com/jobs/~018c2e439c0f0663e4
@rushatgabhane can you review @mdneyazahmad 's proposed solution above? (or.. if you're out, unassign yourself and ping @mountiny to ask to review)
https://github.com/Expensify/App/issues/7584#issuecomment-1030815511

@mdneyazahmad I was thinking of keeping the dimensions of loading box same as the image, so it doesn't resize. But I don't think we can do that before the image has loaded.

@mdneyazahmad what's  styles.dNone and why do we need it?

If we conditionally render the image then, Image will not be mounted and hence onLoadEnd will never be fired. styles.dNone will make it disappears but it will be there.

I understand. By styles.dNone you mean display: none?
Because I can't find dNone anywhere

Yes, It is display: none. Sorry, for misunderstanding.
https://github.com/Expensify/App/blob/78d6e68705ba5b986650cc93187f56f553d1bc23/src/styles/utilities/display.js#L11-L23

🎀👀🎀 C+ reviewed
@mountiny I like @mdneyazahmad's proposal.

📣 @mdneyazahmad You have been assigned to this job by @mountiny!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Great job guys! Nice feature! @rushatgabhane thank you for the review.
@mdneyazahmad please, feel free to submit a PR! Thank you!

Triggered auto assignment to @jboniface (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@jboniface  I'm out next week so auto-added you to keep 👀 on this til I'm back, then I'll take back over.

Bump @mdneyazahmad, can you please give an estimate of when you will be ready to submit the PR? Thanks and have a great day 😊

@mountiny  Sorry for not updating you about it. My pr is ready but I am unable to test it on desktop because of this issue https://expensify.slack.com/archives/C01GTK53T8Q/p1644514188692809.

@mdneyazahmad merging main into your branch should fix it
https://expensify.slack.com/archives/C01GTK53T8Q/p1644527403102189?thread_ts=1644527403.102189&cid=C01GTK53T8Q

Yes, as @rushatgabhane said, this should be fixed by this PR https://github.com/Expensify/App/pull/7719.
No worries, you can also just create the PR even if you can't test it on desktop and let us know in the PR :) Thank you! 🙇

It works adding .env with these content @rushatgabhane thanks.
USE_WEB_PROXY=true
USE_NRGOK=false

This is moving along

Merged just today! 🎉

@mdneyazahmad Following from https://github.com/Expensify/App/issues/7900, would you be able to look at the feedback there and implement the fix for the issue in new PR (after we revert the original PR)? Thank you very much
cc @rushatgabhane for your 👀

The PR for this issue (https://github.com/Expensify/App/pull/7723) caused a regression on staging and has been reverted.

@mdneyazahmad Feel free to submit a new PR, we dont need to rush on this as nothing is broken so lets test more thoroughly for this case. @kidroca had some suggestions here https://github.com/Expensify/App/issues/7900

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.40-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7723

If no regressions arise, payment will be issued on 2022-03-08. :confetti_ball:

Update the title, this is NOT ready for payment, there was a regression. @mdneyazahmad Would you be able to work on this and update the PR to fix the issue found on staging?

@mdneyazahmad Any update here? Otherwise, we will make this open for new contributors or in case @rushatgabhane would like to take it on.

@mountiny Sorry for the delay. Please, give me one more day.

Thank you for chiming in :)

I have found a library that does the same thing we want https://www.npmjs.com/package/react-native-image-progress. This is a very small library 243 loc only. We can install it or can do something similar. It has 1 more feature like when we load image from cache. We can provide a threshold default: 50ms value to wait before showing indicator so that it does not flash the indicator if loading from cache takes some milliseconds.

Image Component
// Made some minor changes
import React, {Component} from 'react';
import PropTypes from 'prop-types';
import {ActivityIndicator, Image, StyleSheet, View} from 'react-native';

const styles = StyleSheet.create({
  centered: {
    ...StyleSheet.absoluteFillObject,
    alignItems: 'center',
    justifyContent: 'center',
  },
});

const DefaultIndicator = ActivityIndicator;

const getSourceKey = (source) => (source && source.uri) || String(source);

const propTypes = {
    children: PropTypes.node,
    errorContainerStyle: PropTypes.any,
    indicator: PropTypes.func,
    indicatorContainerStyle: PropTypes.any,
    indicatorProps: PropTypes.object,
    renderIndicator: PropTypes.func,
    renderError: PropTypes.func,
    source: PropTypes.any,
    style: PropTypes.any,
    imageStyle: PropTypes.any,
    threshold: PropTypes.number,
};

const defaultProps = {
    indicatorContainerStyle: styles.centered,
    errorContainerStyle: styles.centered,
    threshold: 50,
};

class ImageProgress extends Component {

    static abortPrefetch = Image.abortPrefetch;
    static getSize = Image.getSize;
    static getSizeWithHeaders = Image.getSizeWithHeaders;
    static prefetch = Image.prefetch;
    static queryCache = Image.queryCache;
    static resolveAssetSource = Image.resolveAssetSource;

    static getDerivedStateFromProps(props, state) {
        let update = null;
        const sourceKey = getSourceKey(props.source);

        if (sourceKey !== state.sourceKey) {
            update = {
                sourceKey,
                error: null,
                loading: false,
                progress: 0,
            };
        }

        if (props.imageStyle !== state.imageStyle[1]) {
            update = {
                ...update,
                imageStyle: [StyleSheet.absoluteFill, props.imageStyle],
            };
        }

        return update;
    }

    constructor(props) {
        super(props);

            this.state = {
            sourceKey: getSourceKey(props.source),
            error: null,
            loading: false,
            progress: 0,
            thresholdReached: !props.threshold,
            imageStyle: [StyleSheet.absoluteFill, props.imageStyle],
        };
    }

    componentDidMount() {
        if (this.props.threshold) {
            this.thresholdTimer = setTimeout(() => {
                this.setState({ thresholdReached: true });
                this.thresholdTimer = null;
            }, this.props.threshold);
        }
    }

    componentWillUnmount() {
        if (this.thresholdTimer) {
            clearTimeout(this.thresholdTimer);
        }
    }

    setNativeProps(nativeProps) {
        if (this.ref) {
            this.ref.setNativeProps(nativeProps);
        }
    }

    measure(cb) {
        if (this.ref) {
            this.ref.measure(cb);
        }
    }

    ref = null;

    handleRef = (ref) => {
        this.ref = ref;
    };

    bubbleEvent(propertyName, event) {
        if (typeof this.props[propertyName] === 'function') {
        this.props[propertyName](event);
        }
    }

    handleLoadStart = () => {
        if (!this.state.loading && this.state.progress !== 1) {
            this.setState({
                error: null,
                loading: true,
                progress: 0,
            });
        }
        this.bubbleEvent('onLoadStart');
    };

    handleProgress = (event) => {
        const progress = event.nativeEvent.loaded / event.nativeEvent.total;
        // RN is a bit buggy with these events, sometimes a loaded event and then a few
        // 100% progress – sometimes in an infinite loop. So we just assume 100% progress
        // actually means the image is no longer loading
        if (progress !== this.state.progress && this.state.progress !== 1) {
            this.setState({
                loading: progress < 1,
                progress,
            });
        }
        this.bubbleEvent('onProgress', event);
    };

    handleError = (event) => {
        this.setState({
            loading: false,
            error: event.nativeEvent,
        });
        this.bubbleEvent('onError', event);
    };

    handleLoad = (event) => {
        if (this.state.progress !== 1) {
            this.setState({
                error: null,
                loading: false,
                progress: 1,
            });
        }
        this.bubbleEvent('onLoad', event);
    };

    handleLoadEnd = (event) => {
        this.setState({
            loading: false,
            progress: 1,
        });
        this.bubbleEvent('onLoadEnd', event);
    };

    render() {
        const {
            children,
            errorContainerStyle,
            indicator,
            indicatorContainerStyle,
            indicatorProps,
            renderError,
            renderIndicator,
            source,
            style,
            threshold,
            ...props
        } = this.props;

        const {imageStyle} = this.state;

        if (!source || !source.uri) {
            // This is not a networked asset so fallback to regular image
            return (
                <View style={style} ref={this.handleRef}>
                    <ImageComponent {...props} source={source} style={imageStyle} />
                    {children}
                </View>
            );
        }
        const {progress, sourceKey, thresholdReached, loading, error} = this.state;

        let indicatorElement;

        if (error) {
            if (renderError) {
                indicatorElement = <View style={errorContainerStyle}>{renderError(error)}</View>;
            }
        } else if ((loading || progress < 1) && thresholdReached) {
            if (renderIndicator) {
                indicatorElement = renderIndicator(progress, !loading || !progress);
            } else {
                const IndicatorComponent = typeof indicator === 'function' ? indicator : DefaultIndicator;
                indicatorElement = (
                    <IndicatorComponent
                        progress={progress}
                        indeterminate={!loading || !progress}
                        {...indicatorProps}
                    />
                );
            }

            indicatorElement = <View style={indicatorContainerStyle}>{indicatorElement}</View>;
        }

        return (
            <View style={style} ref={this.handleRef}>
                <Image
                    {...props}
                    key={sourceKey}
                    onLoadStart={this.handleLoadStart}
                    onProgress={this.handleProgress}
                    onError={this.handleError}
                    onLoad={this.handleLoad}
                    onLoadEnd={this.handleLoadEnd}
                    source={source}
                    style={imageStyle}
                />
                {indicatorElement}
                {children}
            </View>
        );
    }
}

ImageProgress.propTypes = propTypes;
ImageProgress.defaultProps = defaultProps;
ImageProgress.displayName = 'ImageProgress';

export default ImageProgress;

diff --git a/src/components/ImageWithSizeCalculation.js b/src/components/ImageWithSizeCalculation.js
index 698da27c6..12f50d20b 100644
--- a/src/components/ImageWithSizeCalculation.js
+++ b/src/components/ImageWithSizeCalculation.js
@@ -1,9 +1,11 @@
 import React, {PureComponent} from 'react';
-import {Image} from 'react-native';
+import {ActivityIndicator} from 'react-native';
 import PropTypes from 'prop-types';
 import Log from '../libs/Log';
 import styles from '../styles/styles';
+import themeColors from '../styles/themes/default';
 import makeCancellablePromise from '../libs/MakeCancellablePromise';
+import Image from './Image';

 const propTypes = {
     /** Url for image to display */
@@ -93,6 +95,9 @@ class ImageWithSizeCalculation extends PureComponent {
                 ]}
                 source={{uri: this.props.url}}
                 resizeMode="contain"
+                indicator={() => (
+                    <ActivityIndicator color={themeColors.spinner} size="large" />
+                )}
             />
         );
     }

cc: @mountiny @rushatgabhane

@mdneyazahmad Thank you for the comment. Would you be able to elaborate on the issue which was experienced on staging and maybe also why we did not see it in the PR itself?
Can we not solve the problem without adding a new library?

Couldn't we achieve the same with something simple as
                <Image
                    style={[
                        styles.w100,
                        styles.h100,
                        this.state.isLoading && styles.dNone,
                        this.props.style,
                    ]}
                    source={{uri: this.props.url}}
                    resizeMode="contain"
                    onLoadStart={() => this.setState({isLoading: true})}
                    onLoadEnd={() => this.setState({isLoading: false})}
                />

Initial state.loading would be false
As far as I saw, when something is loaded very quickly onLoadStart/End is not called (the indicator won't flash)

If for some reason (attachment uploads) initial state.loading need to be true we can remove styles.dNone which would trigger onLoadEnd
(For some reason Image without height is not triggering it's onLoad events)

Thank you @kidroca!
@mdneyazahmad would you be able to test out whether these changes would prevent the bug seen previously?

When I started to work on this issue I also consider to make it loading: false by default. But I have seen at many places in our repository we use loading: true by default so went forward with this pattern.
I am still unable to find the root cause. It seems to work fine from my side even with previous pr and also @kidroca findings

As far as I saw, when something is loaded very quickly onLoadStart/End is not called (the indicator won't flash)

I am testing with these changes and post my findings soon.

@mdneyazahmad How is it looking? It has been already a week since the regression so we might consider making this issue available for other contributors. You are currently assigned to this one, but it seems like there is not much progress being made.
Should we release to the pool so more contributors can help and potentially find the problem here?

@mountiny I am sorry for not being responsive here and thanks for you patience.  The culprit seems to be display: none it' behaviour is not consistent across all platform. it seems like onLoadEnd is not fired when display is none on ios other platforms works fine.
Solution
The reason I used display: none was it takes space equal to default width and height and ActivityIndicator was not there in the center. Now, we will overlay another View positioned absolute so that the Image Component will be hidden below the ActivityIndicator and When Image loads ends it will remove the overlay component.
-import {Image} from 'react-native';
+import {StyleSheet, View, Image, ActivityIndicator} from 'react-native';
+import themeColors from '../styles/themes/default'

    constructor(props) {
        super(props);

        this.state = {
            isLoading: true,
        }
    }

render() {
        return (
            <View
                style={[
                    styles.w100,
                    styles.h100,
                    this.props.style,
                ]}>
                <Image
                    style={[
                        styles.w100,
                        styles.h100,
                    ]}
                    source={{uri: this.props.url}}
                    resizeMode="contain"
                    onLoadEnd={() => this.setState({isLoading: false})}
                />
                {this.state.isLoading && (
                    <View style={{...StyleSheet.absoluteFillObject}}>
                        <ActivityIndicator
                            size="large"
                            color={themeColors.spinner}
                            style={[styles.flex1]}
                        />
                    </View>
                )}
            </View>
        );
    }

@mountiny this looks fine to me.

@rushatgabhane Thank you!
@mdneyazahmad Thanks! Since you are already assigned, feel free to create the PR and we will need to make sure to properly test the regression we experienced last time.

@mdneyazahmad can you apply to Upwork job here? https://www.upwork.com/jobs/~01c689e49c8567de30
I had to create a new job, the other one was expired

Hi @mdneyazahmad, just wanted to bump this one, I realize it has not been the easiest of problems to solve for you since you were unable to reproduce the regression, however, as you are active on other issues, I would like to point out that it is expected that once you are assigned to some issue to solve it, that issue should be your priority over making proposals to other jobs.
I hope all is good and that we can push this one along in the coming days 🙏 Let us know here if you have any problems or something time-sensitive going on. We understand we are not pedantic over here, but clear and frequent communication is key :)
Thank you very much!

@mountiny I am sorry for being late here. I was creating a pr and I got issue with mobile web (testing) in my machine. I just don't know why Safari (ios simulator) can not open localhost:8080 I can still open localhost:9000 but that is the old one. I also asked on Slack if somebody can help https://expensify.slack.com/archives/C01GTK53T8Q/p1647430519293939

Thanks for the message. That is alright and I am sorry you are having problems with your setup. Ideally, try to write as accurately as possible the steps you have taken to run it and what errors/logs you see in Slack so others can try to reproduce. Please, try to keep the communication more active.
Thank you for your efforts here!

@mountiny I posted the steps with a video.

Reverted the PR for precautionary measures as a performance issue has been found. Work will be continued in a new PR https://github.com/Expensify/App/pull/8238

Can someone provide an update on where we're at with this issue? What's the best PR link to be following/checking?

@mallenexpensify #8238 is the PR to follow

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.46-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/8203

If no regressions arise, payment will be issued on 2022-04-06. :confetti_ball:

Updated the title and everything, the PR we are following is linked fine but previous PR which was reverted triggered this update, we are about to merge the follow up

This is ready to be paid, right?
@rushatgabhane $250 for C+
@mdneyazahmad $500 - $250/each for reporting and fix.
Please apply here https://www.upwork.com/jobs/~01c689e49c8567de30

@mallenexpensify applied

Hired both in Upwork, let me know when you've accepted the offers. @mdneyazahmad let me know here if you're not "Neyaz A."  Also...the job price is $250, you'll be bonused the other $250 owed.

@mallenexpensify accepted the offer Thank you!

Paid @rushatgabhane and @mdneyazahmad one day early cuz I was paying another issue.  $250 each for C+ and fix


Updated theme.txt to make it more minecraft-y

Changed "The highlighted entry will be executed in x seconds" to "Joining world in x seconds"

Great idea!


Requirement could not be resolved

Getting the following error when running  composer require league/flysystem-aws-s3-v3:
 Your requirements could not be resolved to an installable set of packages.

   Problem 1
     - Can only install one of: league/flysystem[2.0.0, 1.1.3].
     - Can only install one of: league/flysystem[2.0.0, 1.1.3].
     - Can only install one of: league/flysystem[2.0.0, 1.1.3].
     - league/flysystem-aws-s3-v3 2.0.0 requires league/flysystem ^2.0.0 -> satisfiable by league/flysystem[2.0.0].
     - Installation request for league/flysystem-aws-s3-v3 ^2.0 -> satisfiable by league/flysystem-aws-s3-v3[2.0.0].
     - Installation request for league/flysystem (locked at 1.1.3) -> satisfiable by league/flysystem[1.1.3].

Before that I did run:
 composer require oneup/flysystem-bundle
 composer require aws/aws-sdk-php

So that my composer.json looks like:
  "require": {
    "php": "^7.1.3",
    "ext-ctype": "*",
    "ext-iconv": "*",
    "api-platform/api-pack": "^1.2",
    "aws/aws-sdk-php": "^3.168",
    "beberlei/doctrineextensions": "^1.3",
    "gesdinet/jwt-refresh-token-bundle": "^0.7.1",
    "google/apiclient": "^2.0",
    "lexik/jwt-authentication-bundle": "^2.6",
    "oneup/flysystem-bundle": "^3.6",
    "sensio/framework-extra-bundle": "^5.4",
    "stof/doctrine-extensions-bundle": "^1.3",
    "symfony/amazon-mailer": "4.4.*",
    "symfony/console": "^4.0",
    "symfony/dotenv": "^4.0",
    "symfony/flex": "^1.3.1",
    "symfony/framework-bundle": "^4.0",
    "symfony/google-mailer": "4.4.*",
    "symfony/http-client": "4.4.*",
    "symfony/mailer": "4.4.*",
    "symfony/monolog-bundle": "^3.6",
    "symfony/orm-pack": "^1.0",
    "symfony/serializer-pack": "^1.0",
    "symfony/translation": "4.4.*",
    "symfony/yaml": "^4.0",
    "vich/uploader-bundle": "^1.10",
    "webonyx/graphql-php": "^0.13.8"
},

Looking at composer.lock I see that the version of league/flysystem is 1.1.3' which I believe was put there for oneup/flysystem`
     "name": "league/flysystem",
        "version": "1.1.3",

I did try to force  update to<EMAIL_ADDRESS>running
composer update oneup/flysystem --with-dependencies
but that did not change anything.

The oneup bundle doesn't support flysystem 2 yet, so if you want to install flysystem, you need to use the previous major version.

Like so composer require league/flysystem-aws-s3-v3:1.0.29?
That seem to have worked.


regenerate result document test files

Description
The rule 'contain a resource (.rsrc) section': 'executable/pe/section/rsrc' is present in all json files in ./tests/data/rd. As the rule was deleted in PR https://github.com/mandiant/capa-rules/pull/761 . We might need to change or remove these test files

Steps to Reproduce
capa '.\tests\data\rd\al-khaser_x86.exe_.json'
capa '.\tests\data\rd\3f3bbcf8fd90bdcdcdc5494314ed4225.exe_.json'

Linked PR https://github.com/mandiant/capa-testfiles/pull/227


Scale for Action wrapper

Related Issue
https://github.com/BigThinkcode/AdaptiveCards/issues/127
Description
For all Pull Requests, please describe how the issue was fixed or how the feature was implemented from a summary level. This information will be used to help provide context to the reviewers of the pull request and should be additive to the issue being closed.
Sample Card
If appropriate, please include a link to a card in one of the samples directories that can be used to validate this change. This can be an existing card or a card added with this PR.
How Verified
How you verified the fix, including one or all of the following:
Attached videos:

Before
After

https://github.com/BigThinkcode/AdaptiveCards/assets/15324293/b6b178ff-4e27-4793-995b-5e2a7dc31b04
https://github.com/BigThinkcode/AdaptiveCards/assets/15324293/08842573-ae34-47f4-8387-e6cbd775c980

@pragadeeshk please take a look at this PR


include sources in error messages and don't overflow on invalid timestamps

For #111 and #112
This also includes some noise from formatting changes. There are 2 notable changes in here:

Don't panic when timestamps from GELF would overflow when converted into an Instant. This can happen if the number sent isn't at second-precision.
Include the messages from source errors, not just the top-level one, when GELF processing fails.

This needs https://github.com/datalust/seqcli/pull/257 released before it'll work.


Add bootstrap4 beta

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm closing this PR, since bootstrap 4 is available as a separate library. Thanks for your contribution and sorry that it wasn't used. If you're using bootstrap 4 I hope you can use the above library.


MalformedInputException on Locale C.UTF-8 on JDK 11

Coming from https://github.com/oshi/oshi/pull/2525#issuecomment-1838992663

My library prints output to stdout containing the degree sign, UTF-8 0xC2B0.
This output is printed as part of our CI testing.  One such CI is on a Solaris 11.4 x86 VM.  Important to this discussion, the locale is set to LANG=C.UTF-8.
While the CI test passes, the output catches the same error we saw in #95 on Windows

Full log: https://github.com/oshi/oshi/actions/runs/7089320523/job/19293798675
Excerpt:
  Caused by: java.lang.AssertionError: Unexpected exception caught!
  	at de.sormuras.junit.platform.maven.plugin.JUnitPlatformMojo.execute(JUnitPlatformMojo.java:433)
<snip>
  Caused by: java.io.UncheckedIOException: java.nio.charset.MalformedInputException: Input length = 1
  	at java.base/java.nio.file.FileChannelLinesSpliterator.readLine(FileChannelLinesSpliterator.java:176)
  	at java.base/java.nio.file.FileChannelLinesSpliterator.forEachRemaining(FileChannelLinesSpliterator.java:116)
  	at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658)
  	at de.sormuras.junit.platform.maven.plugin.JavaExecutor.evaluate(JavaExecutor.java:147)
<snip>
  Caused by: java.nio.charset.MalformedInputException: Input length = 1
  	at java.base/java.nio.charset.CoderResult.throwException(CoderResult.java:274)
  	at java.base/sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
  	at java.base/sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
  	at java.base/java.io.BufferedReader.fill(BufferedReader.java:161)
  	at java.base/java.io.BufferedReader.readLine(BufferedReader.java:326)
  	at java.base/java.io.BufferedReader.readLine(BufferedReader.java:392)
  	at java.base/java.nio.file.FileChannelLinesSpliterator.readLine(FileChannelLinesSpliterator.java:174)

The code involved (exception thrown in Files.lines()
if (captureIO) {
  String encoding = System.getProperty("native.encoding"); // Populated on Java 18 and later
  Charset charset = encoding != null ? Charset.forName(encoding) : Charset.defaultCharset();
  try (Stream<String> stdoutput = Files.lines(outputPath, charset);
      Stream<String> erroutput = Files.lines(errorPath, charset)) {

Since this is pre-JDK 18, the fix for #95 using the "native.encoding" doesn't apply, however, the symptom is the same. The charset being used doesn't understand one of the characters being processed.
This Stack Overflow answer suggests trying multiple charsets.  Another answer claims

ISO-8859-1 is an all-inclusive charset, in the sense that it's guaranteed not to throw MalformedInputException. So it's good for debugging

Not sure if this is something you want to handle here, but at a minimum I'd request that you at least catch the exception and provide a better error message indicating that the default charset (print it out) can't handle a line of output.

Happy to submit a PR. WDYT about adding a  option to specify an output charset? It would default to the JDK's default charset but would permit users to override that in the above code block, for example to ISO-8859-1.

Sure, sounds like a good fallback solution for such cases.


Variable Inlining [1/n]: Local variable inlining

This PR is part-1 of the Variable inlining PRs. This aims to solve the problem of local variable inlining. The tests written are only testing for local variable deletion and replacement. Integration tests for resolving the booleans in if else and other statements will be done in upcoming PRs.

Can be landed after Satyam's PR get's landed. Please review my commit only. Cherry picking my commit and opening a PR from a different branch can cause test failures as Satyam's PR is important for setting up the Function scope.


fixed definition of kinetic energy

Makes more sense this way. There should be no change in behaviour.

Pull Request Test Coverage Report for Build 704543941

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.196%

Totals

Change from base Build 699506928:
0.0%

Covered Lines:
1958

Relevant Lines:
2675

💛  - Coveralls


consensus plugin

We are return possibility to connect a consensus plugin, which was removed in the commit:
https://github.com/bigchaindb/bigchaindb/commit/50b0b3cef217bc412dba5a062de1db2d1adcd514
Possibility to extend basic consensus rules by custom logic.

Current coverage is 95.87% (diff: 76.19%)

Merging #1084 into master will decrease coverage by 0.66%

@@             master      #1084   diff @@
==========================================
  Files            49         44     -5
  Lines          2168       1964   -204
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           2093       1883   -210
- Misses           75         81     +6
  Partials          0          0

Powered by Codecov. Last update a7a163f...78bd1ec


refactor(katana-core): expose underlying StarknetWrapper in Sequencer trait

Stack:

#548
#547 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #548


adding production url in tailor registration verification url

Description
removed localhost and added updated hosting url in tailor registration verification url

Hello @Naresh-chandanbatve!
Thank you for submitting this pull request Your pull request will be reviewed by maintainers shortly. Meanwhile make sure you have referenced the respected issue in this pr Your pr will not be merged if it does not have reference to respected issue
please read our Contributing Guidelines https://github.com/UBA-GCOEN/StichHub/blob/main/CONTRIBUTING.md And Code of Conduct https://github.com/UBA-GCOEN/StichHub/blob/main/CODE_OF_CONDUCT.md


Collection sorting appears to be altered on v10.1.0

Laravel Version: 10.1.0
PHP Version: 8.2.2
Database Driver & Version: MySQL 8.0.32

Description:
After upgrading to Laravel 10.1.0, I was getting some test failures that appeared to be related to Collection sorting.  I reverted back to Laravel v10.0.3 and all tests passed again.
I haven't had time to deep dive in yet, but will soon and report back with more info.
Steps To Reproduce:
Possibly use the Collection sort() method. Will provide more details as I dig in.

If you're using Arr::random Arr::shuffle Collection::random Collection::shuffle, then the internal implementation changed with https://github.com/laravel/framework/pull/46105.

Are you using one of the following functions? If so, the #46105 may be affected

srand
rand
mt_srand
mt_rand
shuffle
str_shuffle
array_rand

It should be fixed on the 10.1.2 release. Thank you for reporting this.