Build with OpenSSL 1 and 3

Build with OpenSSL 1 and 3.
Depends on:

https://github.com/AnacondaRecipes/qt-main-feedstock/pull/5

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:17: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:26: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:110: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:111: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:119: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/clone/recipe/meta.yaml:129: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/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_e8sgxqgx5b/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_e8sgxqgx5b/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_e8sgxqgx5b/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e8sgxqgx5b/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_e8sgxqgx5b/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_e8sgxqgx5b/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_e8sgxqgx5b/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:17: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:26: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:110: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:111: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:119: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/clone/recipe/meta.yaml:129: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/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_cadqap730u/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_cadqap730u/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_cadqap730u/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cadqap730u/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_cadqap730u/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_cadqap730u/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_cadqap730u/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:17: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:26: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:111: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/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_8bg8aggp17/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_8bg8aggp17/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8bg8aggp17/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:17: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:26: missing_hash: The recipe is missing a sha256 checksum for a source file
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:111: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:137: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/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_eaqx3tfvcb/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_eaqx3tfvcb/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_eaqx3tfvcb/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/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_4f478i92uz/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_4f478i92uz/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_4f478i92uz/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4f478i92uz/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/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_40duhlq1qa/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_40duhlq1qa/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_40duhlq1qa/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_40duhlq1qa/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/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_28bwixk0pf/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_28bwixk0pf/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_28bwixk0pf/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_28bwixk0pf/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/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_1c4zuv1bac/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_1c4zuv1bac/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_1c4zuv1bac/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1c4zuv1bac/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/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_72e29zcmxb/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_72e29zcmxb/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_72e29zcmxb/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_72e29zcmxb/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/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_2dpll0_ef_/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_2dpll0_ef_/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_2dpll0_ef_/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_2dpll0_ef_/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/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_8eix_f_hv7/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_8eix_f_hv7/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_8eix_f_hv7/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8eix_f_hv7/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:114: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:122: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:125: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:132: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:134: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/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_1d9c_6_p9k/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_1d9c_6_p9k/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_1d9c_6_p9k/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1d9c_6_p9k/clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/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_95h4qitepy/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_95h4qitepy/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_95h4qitepy/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_95h4qitepy/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_95h4qitepy/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_95h4qitepy/clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/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_9dypojoi8s/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_9dypojoi8s/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_9dypojoi8s/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_9dypojoi8s/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_9dypojoi8s/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9dypojoi8s/clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/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_1f5kvf6qvd/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_1f5kvf6qvd/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_1f5kvf6qvd/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_1f5kvf6qvd/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_1f5kvf6qvd/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1f5kvf6qvd/clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/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_19syzkb47c/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_19syzkb47c/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_19syzkb47c/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_19syzkb47c/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_19syzkb47c/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_19syzkb47c/clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:113: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:121: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:123: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:124: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/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_aba2oc8_59/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_aba2oc8_59/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_aba2oc8_59/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_aba2oc8_59/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_aba2oc8_59/clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:143: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_aba2oc8_59/clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:116: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:126: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:148: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:116: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:126: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:148: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:116: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:126: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:142: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:145: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:148: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:116: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:126: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:136: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:144: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:146: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:148: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:148: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:150: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found


Add global query vector

Adding global query vector as mentioned in #4

@fisheggg thank you Arthur!


REST API Demo protected by SciTokens

Create a demo app with a simple REST API that uses SciTokens to authorize access to the API endpoints. Instead of using "scope": "read:/example" like in other SciTokens apps, this demo app does authorization based on the HTTP methods according to the REST approach. For example:

The holder of a token containing "scope": "get:/jsmith post:/jsmit put:/jsmith delete:/jsmith" can get, create, and delete "state" under /jsmith. For example, they could use put to create a /jsmith/example1 resource.
The holder of a token containing "scope": "get:/jsmith/example1 can only get the /jsmith/example1 resource.

The demo app itself could just store created resources in memory. No need for a back-end database. It's OK if everything gets reset when the app is restarted.
The end result should be a web app with code at https://github.com/SciAuth/rest-demo with a README that tells people how to use it.
The app could use the Python "decorator" example here:

https://github.com/scitokens/scitokens-heroku/blob/master/app.py#L342
https://github.com/scitokens/scitokens-heroku/blob/master/scitokens_protect.py

If the demo app is based on existing code, be sure to include appropriate acknowledgements, licenses, etc.

https://auth0.com/blog/developing-restful-apis-with-python-and-flask/ looks like a useful reference for this.

Done: https://github.com/SciAuth/rest-demo/releases/tag/v1.0.0


nts/Tag entity at Setup domain

Closes: https://github.com/Not-Endurance/not-timing-system/issues/224

Planning to make RfidTagScanner visible based on the StaticOptions with the introduction of the StaticOptions functionality in the Controllers PR.

Set a fixed height for the RfidTagScanner content and its buttons to ensure that the CombinationForm's height is not changed when MudProgress appears while awaiting chip scan.


fix(buildenvs): Enable network user mode in QEMU build (via slirp)

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[x] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes

@nderjung I also tried the latest 8.X qemu in my attempts.
The problem in this PR is not solved by that, meaning that it won't have slirp compiled in or compilable-in, which results in two successive solutions:

Revert that specific commit in qemu that allows for slirp compiling
or
Compile non-statically and add all dependencies manually (will require extensive Dockerfile re-write)

If we are blocking on this, I say merge this PR and then work to make 2. happen. 1. needs too much maintaining and it's not worth it.

Compile non-statically and add all dependencies manually (will require extensive Dockerfile re-write)

Turns out, it was not so extensive after-all. This should now work and provide us with the latest qemu which can do what we want


Updated

@liul29

I think the table might have some problem since it should be a probability table.

@sfzhu

Problem 2. The distance actually follows the rayleigh distribution, and  it will give you d_5sigma = 5.489.


Add gruntjs

Gonna pass. Grunt is no longer properly maintained.

Gonna pass. Grunt is no longer properly maintained.

Nor does it seem much loved, see:

https://2017.stateofjs.com/2017/build-tools/results/


App crashes when calling youtubePlayer.currentTime()

Attempt to invoke interface method int com.google.android.youtube.player.YoutubePlayer.getCurrentTimeMillis()' on a null object reference
YoutubePlayerController : 152 line
Using versions :
"react": "~15.4.0-rc.4",
"react-native": "0.42.3",
"react-native-youtube": "^1.0.0-alpha.6",
Trying to access like this
<YouTube
        ref={(component) => {
          if (__DEV__) {
            if (component !== null) {
              component.currentTime().then((time) => {
                if (__DEV__) console.log('current Time in player :: >> ', time)
              })
            }
          }
          this.youTubePlayer = component
        }}
      />

@Dineshchitta seems like you are calling this method too soon. Of course it shouldn't cause a crash but anyway try calling methods after the onReady event

yes.Thank you @davidohayon669


About ble XMWXKG01YL is still abnormal after 3.1.0 fix

About ble XMWXKG01YL is still abnormal after 3.1.0 fix.
Only single key after repair
"Fix support XMWXKG01YL on Gateway fw 1.5.4 https://github.com/AlexxIT/XiaomiGateway3/issues/950"
Home Assistant 2023.1.7
Xiaomi Gateway 3 for Home Assistant v3.1.0
gateway ZNDMWG03LM 1.5.4_0090
debug logs ：
button_1_single
miio/report b'{"id":1893784138,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1012,"tid":83,"arguments":[{"piid":1,"value":1}]},"type":6}'
miio/report_ack b'{"id":1893784138,"result":"ok"}'

button_2_single
miio/report b'{"id":943065139,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1012,"tid":84,"arguments":[{"piid":1,"value":2}]},"type":6}'
miio/report_ack b'{"id":943065139,"result":"ok"}'

button_1_double
miio/report b'{"id":1247392140,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1013,"tid":85,"arguments":[{"piid":1,"value":1}]},"type":6}'
 miio/report_ack b'{"id":1247392140,"result":"ok"}'

button_2_double
miio/report b'{"id":1995923142,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1013,"tid":86,"arguments":[{"piid":1,"value":2}]},"type":6}'
miio/report_ack b'{"id":1995923142,"result":"ok"}'

button_1_hold
miio/report b'{"id":231842143,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1014,"tid":87,"arguments":[{"piid":1,"value":1}]},"type":6}'
miio/report_ack b'{"id":231842143,"result":"ok"}'

button_2_hold
miio/report b'{"id":1265790144,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1014,"tid":88,"arguments":[{"piid":1,"value":2}]},"type":6}'
miio/report_ack b'{"id":1265790144,"result":"ok"}'

button_both_single
miio/report b'{"id":876460148,"method":"event_occured","params":{"did":"blt.3.1a2p4aiv05c01","siid":3,"eiid":1012,"tid":89,"arguments":[{"piid":1,"value":3}]},"type":6}'
miio/report_ack b'{"id":876460148,"result":"ok"}'

Thanks! Very helpful. Fixed in latest master version

It is still amiss after latest master version fix.
when button1 or 2 or both button are clicked, it returns
button: 1
action: single

when button1 or 2 is double-clicked, it returns
button: 2
action: double

when button1 or 2 is holded, it returns
button: 4
action: quadruple

It seems that button-type gets wrong value. And hold-action could not be recognized correctly.
I checked miot-spec and found some infomation maybe useful
#switch-sensor-for-ble
siid: 3
{"required-properties":[],"optional-properties":["urn:miot-spec-v2:property:button-type:0000011F","urn:miot-spec-v2:property:mode:00000008"],"required-actions":[],"optional-actions":[],"required-events":[],"optional-events":["urn:miot-spec-v2:event:double-click:00005008","urn:miot-spec-v2:event:click:00005007","urn:miot-spec-v2:event:long-press:00005009","urn:miot-spec-v2:event:device-be-reset:0000503C"],"type":"urn:miot-spec-v2:service:switch-sensor-for-ble:000078B0","description":"Switch Sensor For BLE"}

#button-type
piid: 1
value:
1 - Left Button
2 - Right Button
3 - Left And Right Button
{"format":"uint8","access":[],"value-list":[{"value":1,"description":"Left Button"},{"value":2,"description":"Right Button"},{"value":3,"description":"Middle Button"},{"value":4,"description":"Left And Right Button"}],"type":"urn:miot-spec-v2:property:button-type:0000011F","description":"Button Type"}

@rumianoesa what is your gateway model and firmware?

@rumianoesa what is your gateway model and firmware?
Home Assistant 2023.1.7
Xiaomi Gateway 3 for Home Assistant v3.1.0 latest master version
gateway ZNDMWG03LM 1.5.4_0090

Can you show logs and device diagnostics. You can't get this messages with this device model

@rumianoesa您的网关型号和固件是什么？家庭助理 2023.1.7 小米网关 3 家庭助理 v3.1.0 最新主版网关 ZNDMWG03LM 1.5.4_0090
It works fine with the latest fixes

Fix XMWXKG01YL on new firmwares

I download the master version again, it works fine now.
Thank you!


Figma Refactor: Counter

Features to Implement

[ ] Text
[ ] Variables
[ ] Simplify instances

No longer needed in the library as it was only used as part of DropdownInput component, so instead incorporated it into DropdownInput. Counter didn't exist as a component within the codebase, so no changes are needed on the code side


[DRAFT] Match the validation that exists in the current HL7 V2 GUI validation tool

User Story
As an HL7 V2 universal pipeline sender, I want to have validation that matches the IGs in the current GUI Validation tool.
Description/Use Case
We want to make sure that the validation tool for HL7 V2 will allow them to validate the same IGs and, if not out of the box, make it have them. We also want to make sure that we have profiles built into the validation that match those.
Risks/Impacts/Considerations
Dev Notes
Acceptance Criteria

[ ] The validation tool for HL7 V2 will allow them to validate the same IGs as the existing Validation tool
[ ] There are profiles built into the validation that match those in the existing Validation Tool.

Use the following template when creating new Acceptance Criteria:

We will determine which to use in the research ticket. Closing


Well first i installed MoltenGamepad and after starting it with the command ./moltengamepad --mimic-xpad i realized that the games i tried recognize the gamepad as Mouse (horray for progress!).
But back to the Problem: after pressing a button i get the following message:
No moltengamepad.cfg found.
driver: wiimote driver initialized.
plug: wm1 added
device hiding: changing permissions of /dev/input/event25 failed.
device hiding: changing permissions of /dev/input/js4 failed.
stdin: ready to read commands from standard input. Try "help" for more info.
slot: wm1 assigned to slot virtpad1
then i typed print devices wm1
and got the following output:
wm1
"Wii U Pro Controller"
type: gamepad
uniq: "------" (i removed it)
phys: "-----"  (i removed it too)
events:
btn   cc_a:   Classic Controller A button
btn   cc_b:   Classic Controller B button
btn   cc_x:   Classic Controller X button
btn   cc_y:   Classic Controller Y button
btn   cc_plus:    Classic Controller + button
btn   cc_minus:   Classic Controller - button
btn   cc_home:    Classic Controller Home button
btn   cc_left:    Classic Controller Dpad left
btn   cc_right:   Classic Controller Dpad right
btn   cc_up:  Classic Controller Dpad up
btn   cc_down:    Classic Controller Dpad down
btn   cc_l:   Classic Controller L button
btn   cc_zl:  Classic Controller ZL button
btn   cc_r:   Classic Controller R button
btn   cc_zr:  Classic Controller ZR button
btn   cc_thumbl:  Classic Controller Left Stick Click (Wii U Pro only)
btn   cc_thumbr:  Classic Controller Right Stick Click  (Wii U Pro only)
axis  cc_left_x:  Classic Controller Left Stick X
axis  cc_left_y:  Classic Controller Left Stick Y
axis  cc_right_x: Classic Controller Right Stick X
axis  cc_right_y: Classic Controller Right Stick Y
options:
?grab_exclusive = true
Grab device events via ioctl EVIOCGRAB
?grab_permissions = true
Grab device via blocking all read permissions`
well... now is the problem: i don't know what to do now? The main goal is to get the wiiU Pro pad recognized as xbox360 controller (or something simliar) but i don't know what to do next.

ok i've think i've finally managed everything but now i don't really understand to add the device to this config.
after putting in: print drivers wiiu-pro
i've got
(wiiu-pro)
  no devices

as output and cant find a option to set my controller from
(wiimote)
wm1:	Wii U Pro Controller

to
(wiiu-pro)
  no devices

Sorry for the delay.
The wiimote driver has built in support for the Wii U Pro, and it appears to be working as intended. It is being assigned to virtpad1, the first virtual output device. With --mimic-xpad, this should be functioning as a 360 controller, and the default mapping should be reasonable.
My Wii U Pro controller is actually the one I use most often with MG.

You do have some permissions issues, so the original Wii U Pro device node (/dev/input/event25) isn't being hidden. This means your games are going to see both the original node and the new fake 360 controller node.
Let me know what udev rules you installed and I can try to figure this out.

Your mouse issues are likely your desktop environment's fault. For some reason many popular distros default to treating gamepads/joysticks as a mouse input device.

If you wish to use your wiiu-pro config rather than the support in the wiimote driver, you'll have to remove the wiimote plugin. This can be done by changing the Makefile before compiling.
MG currently does not have support for rebinding devices to different MG drivers.

Hey No Problem at least i could use the days to learn something new, also i hopped from Antergos to pure Arch Linux.
So if i understood you correctly the main problem is my arch linux itself.

For testing i tried for testing purpose moltengamepad as root:
$ sudo ./moltengamepad --mimic-xpad
warning: Running MoltenGamepad as root is not recommended. Instead, please run as a non-superuser that has been granted the appropriate permissions.
No moltengamepad.cfg found.
driver: wiimote driver initialized.
plug: wm1 added
stdin: ready to read commands from standard input. Try "help" for more info.
slot: wm1 assigned to slot virtpad1
so hiding is possible as root.

i am still try to figure out why my arch still thinking my Controler is a mouse even with --mimic-xpad
and i didn't changed anything from your main configuration, i am more likely a "mainstrem Linux user" than somebody who really understands the most stuff (makepkg is still a little bit a hassle for me)
if i don't find any solutions why Arch is thinking my Controller is a mouse i try to use my wiiu-pro cfg.

For the mouse issue, see the Arch Wiki. Create the needed file and reboot.

For the permissions, for auto-hiding to work, the device nodes /dev/input/eventX need to have MG's user as the owner. Running as root of course gives the needed permissions also.
udev rules can be created in order to automatically assign ownership of the device nodes when they are created. The installation directory in this repo has a couple suggested udev rules files (along with scripts to install them).

For the permissions, for auto-hiding to work, the device nodes /dev/input/eventX need to have MG's user as the owner. Running as root of course gives the needed permissions also.

got now 3 configs:
Section "InputClass"         Identifier "joystick catchall"         MatchIsJoystick "on"         MatchDevicePath "/dev/input/event*"         Driver "joystick"         Option "StartKeysEnabled" "False"       #Disable mouse         Option "StartMouseEnabled" "False"      #support EndSection
Section "InputClass"         Identifier "joystick catchall"         MatchIsJoystick "on"         MatchDevicePath "/dev/input/js*"         Driver "joystick"         Option "StartKeysEnabled" "False"       #Disable mouse         Option "StartMouseEnabled" "False"      #support EndSection
and:
Section "InputClass"         Identifier "Nintendo Wii Remote Raw Input Blacklist"         MatchProduct "Nintendo Wii Remote"         MatchDevicePath "/dev/input/event*"         Option "Ignore" "on" EndSection
it seems like something i should ask in the arch forum because when i connect via bluetoothctl i've got still the same issue.

``

If you are still seeing it move the mouse, I don't know what is up. X11 config files like those given on the Arch Wiki are still a little bit of arcane magic to me.
However, there is still a remaining option if all else fails. Run xinput to list all the current mouse/keyboard devices your desktop is seeing.
If the configs above are failing, you'll see the virtual gamepads in the list. You can then use xinput --disable [##], which will tell X to ignore the mouse movements from these devices. This should work, but it'll need to be done whenever you restart MG. The config files above are supposed to do this disabling automatically.

hey, first of al, i think we can close this topic, because it was all about config files and not my personal "why doesn't it work on arch" problems.. overall i asked also in the arch forums and hope for an answere.
secondly, xinput --disable doesn't seemed to help. but overall i realized, that the only thing that helped was to start FIRST moltengamepad and THEN start bluetooth and activate the controller. it still doen't work on games wich are mouse based (like 12 is better than 6) but now i can at least play all controller based games like risk of rain or guacamelee. funny thing is only that it don't really map it as a xbox controller. when i press the b button on the wii u pro pad, it doesnt realize "ok this is the a button on the xbox" it trys to tell me that is the B button on the xbox, but at least i can play more than before :)

About that last thing:
MG's default mapping is to match by meaning, so the "B button" on the Wii U pro becomes the virtual "B button" of the xbox. This was an intentional decision.
Since the layouts are different, it isn't clear whether one might care more about the button labels (a,b,x,y) or the button positions.
If you choose to delve deeper into MG configuration, you can change the mappings, if you want the Wii U pro's button layout to match the 360 one. This is handy for games that focus on the physical layout, like Oxenfree.


Censorship?

greetings,
SD vanilla have censorship enabled by default. What is the censorship status with this repo?
Thank you,

Also, is there any hidden watermarks?

The safety checker and watermark lines don’t exist in the files, which presumably indicates they’ve been removed in this fork.

No censorship and no watermarks at present. However, I think watermarks will be added as an optional feature in the next release.

It's not quite the same, but the prompts are embedded as plain text into the PNG, so if you distributed the raw output, it's theoretically possible to extract what prompts you used (this is generally considered a good thing especially when you forgot what you were doing to create an image!)

So is the feature request to install the NSFW filter and watermarking? I'm happy to do that.

I think he was confirming they weren’t present, since it wasn’t explicitly called out in the readme one way or the other.

Good point. Is the lack of censorship/watermarking something people would consider a "feature" that should be called out in the feature list, or is it something that the less said about the better?

(Solely my personal opinion, but) I think "censorship" is a tricky term as it evokes different things in different groups of people. I think things are OK as they are given the experimental nature of the project, but if it's a FAQ it could warrant a "privacy" section in the README to state the facts around what the code does or does not do. For example: no watermarking, no filtering of output, no "phoning home", metadata is written, etc.

Is the lack of censorship/watermarking something people would consider a "feature"

At a minimum, it should be noted.
As a semi-aside, my understanding (possibly incorrect) is that the watermark (which consists entirely of the text "Stable Diffusion") is there so that future models aren't contaminated (overwhelmed, even?) by ML-generated images.

As a semi-aside, my understanding (possibly incorrect) is that the watermark (which consists entirely of the text "Stable Diffusion") is there so that future models aren't contaminated (overwhelmed, even?) by ML-generated images.

I hadn't thought of that. I'd better bring the watermarking code in.

Do we know what is encoded in the watermark? Privacy (as noted above) may be the better way to view this, and I imagine an "opaque" watermarking process might be seen as imposing on that.
From what I can see suggested (anecdotally), it is indeed just a "Stable Diffusion" flag. However, I imagine folks might still be wary.

The code doesn't lie, and upstream simply has the string "StableDiffusionV1" (converted to pixel data, of course)
wm = "StableDiffusionV1"
wm_encoder = WatermarkEncoder()
wm_encoder.set_watermark('bytes', wm.encode('utf-8'))
.
.
.
# Here, 'img' is the generated image
def put_watermark(img, wm_encoder=None):
    if wm_encoder is not None:
        img = cv2.cvtColor(np.array(img), cv2.COLOR_RGB2BGR)
        img = wm_encoder.encode(img, 'dwtDct')
        img = Image.fromarray(img[:, :, ::-1])
    return img

which is then called as img = put_watermark(img, wm_encoder)

@lstein - Proposal for some readme text, if helpful - yours to edit and change as you see fit. I am assuming that only the code setting these flags has been removed (e.g., safety_cheker_input  and image, has_nsfw_concept).
This seems to implement a "Safety Checker" flag, which may be interesting to implement as a feature if users find it useful. https://github.com/huggingface/diffusers/pull/254/files
Privacy & Safety
As a principle, the contributors to this fork strive to ensure the ethical development and use of this emerging technology. Decisions have been made regarding the safety checking & watermarking implementations in Stable Diffusion.
Safety Checking -
Safety Checking has been disabled by default from this fork as is common among other forks looking to access the full range of model output. This may result in outputs uninhibited by filters that would remove things commonly seen as "NSFW". If you are using this for any use cases which this output may be inappropriate, it is advised to re-implement this checking manually by updating txt2img.py with
safety_cheker_input = self.feature_extractor(self.numpy_to_pil(image), return_tensors="pt").to(self.device)         image, has_nsfw_concept = self.safety_checker(images=image, clip_input=safety_cheker_input.pixel_values)
Watermarking
Watermarking allows for the encoding of information into images which can then be decoded through observing pixel-level data in the image. This can be used for various purposes and reasons, depending on the party implementing the watermark. With any kind of watermarking implementation, privacy can be a concern, if any personally identifiable information is encoded. The code invoking the watermark encoder is accessible within this repo, and is used primarily to identify ML generated content to prevent future model iterations of Stable Diffusion from training on its own outputs. A simple "StableDiffusionV1" watermark is added to output images for this purpose, and there are absolutely no privacy implications associated with the encoding of this information. It helps ensure that the Stable Diffusion ecosystem will continue to compete in quality model development against other closed-source and centralized offerings, but if you have any objections, the code for the Watermark Encoder can be removed manually.
The purpose of this repo is to offer a sophisticated and fully featured toolset, combining the latest developments in the space, while working towards common goals as a broader community. We appreciate your help!

@hipsterusername That seems a really good idea, though on the 'Safety Checking' - I believe users will need similar in ldm/generate.py otherwise dream.py, etc. would still be unfiltered?

The flag would seemingly be useful to some to be able to control as a "Default", and more easily controlled by end-user than directly modifying multiple .py files. I know that there has been discussion around other "default" settings users would like to be able to control - e.g., resolutions, samplers, etc.
I just don't know how much of a priority it is. Most are probably fine with the checker off, by default - The readme is more of a helpful FYI for the corner cases.

So is the feature request to install the NSFW filter

IMO giving users freedom to create by default is one of the strengths of the fork.
If such limitations are ever implemented, there should be an option to override the same. A flag, as others have suggested, and/or an environment variable would be good UX.

No censorship and no watermarks at present.

The code doesn't lie, and upstream simply has the string "StableDiffusionV1" (converted to pixel data, of course)

getting mixed messages here, is there watermarks embed in generated image or not? If yes, how it is being decode/visualized?

The watermark code is NOT in this repo. I was referring to the original watermark code, which is still upstream (in CompVis/stable-diffusion).

If yes, how it is being decoded/visualized?

The same library which writes the watermarks can read them, though it's been weeks since I looked into it (briefly), so I don't remember the details.

Filtering is not censorship when it's optional at the user's discretion. There are number of comments that mention there are cultural and personal differences in what's considered explicit or triggering. Therefore I think it's worthwhile pursuing a customizable filter that's available from the web interface.
Filtering could go a number of ways but categorically

NSFW content

Generating explicit images unintentionally is a possibility and not always desirable.

Keywords or associations used in generation

For example a fear of spiders eg arachnophobia.

This can be made into a new issue if deemed appropriate.

We can include the Hugging Face NSFW filter, although I'm not sure how much
work this will require since we are not using their Diffusers library at
present. As far as keyword filtering goes, I think this is up to the writer
of the prompts to avoid. For example, it is not clear that the word
"skyscraper" would generate imagery that could trigger someone with a fear
of heights.
On Wed, Oct 19, 2022 at 4:11 PM LexiconCode @.***>
wrote:

Filtering is not censorship when it's optional at the user's discretion.
There are number of comments that mention there are cultural and personal
differences in what's considered explicit or triggering. Therefore I think
it's worthwhile pursuing a customizable filter that's available from the
web interface.
Filtering could go a number of ways but categorically

NSFW content

Generating explicit images unintentionally is a possibility and
not always desirable.

Keywords or associations used in generation

For example a fear of spiders eg arachnophobia.

This can be made into a new issue if deemed appropriate.
—
Reply to this email directly, view it on GitHub
https://github.com/invoke-ai/InvokeAI/issues/502#issuecomment-1284519806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVNAAQJFJLOHQFLHJRTWEBIYFANCNFSM6AAAAAAQJ2NULY
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

The code doesn't lie, and upstream simply has the string "StableDiffusionV1" (converted to pixel data, of course)
wm = "StableDiffusionV1"
wm_encoder = WatermarkEncoder()
wm_encoder.set_watermark('bytes', wm.encode('utf-8'))
.
.
.
# Here, 'img' is the generated image
def put_watermark(img, wm_encoder=None):
    if wm_encoder is not None:
        img = cv2.cvtColor(np.array(img), cv2.COLOR_RGB2BGR)
        img = wm_encoder.encode(img, 'dwtDct')
        img = Image.fromarray(img[:, :, ::-1])
    return img

which is then called as img = put_watermark(img, wm_encoder)

I hope someone will volunteer to bring the watermarking code in. It is benign and useful.


nuxt generate SPA mode not working for dynamic routes when reloading/going to route directly

Versions

nuxt: 2.14.12
node: n/a

Reproduction

Additional Details

nuxt.config.js settings:

ssr: false

target: 'static'

### Steps to reproduce
-Run 'npm nuxt generate'

-Deploy to firebase hosting

-Dynamic routes are accessible when clicking on the links, but getting a 404 when accessing the URL directly or reloading the page.

-Cannot run nuxt generate everytime a new dynamic route gets created because these routes are user generated.

What is Expected?
Should be able to access dynamic route directly in SPA mode or reload the dynamic route page
What is actually happening?
Getting a Firebase 404 error, since the routes weren't generated during build. (this is not a possibility since users will create content and they will get a new route to access the new content)

@aphavichitr With static file hosting, you will need to configure your host to serve fallback HTML in the case of a 404.
From https://firebase.google.com/docs/hosting/full-config#404, it looks like you just need to set generate. fallback to true. (More information.)

Thank you so much!!!! This worked!!! Been looking for this answer for a very long time haha


Change: Generate test and code issues badges as SVG

This setup enables the use of local SVG badges directly from the repository, eliminating the dependency on shields.io. The key advantage is that the displayed counts for passed tests and code issues in the README will automatically reflect the state of the code in the specific branch or commit currently being viewed.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 56.75676% with 16 lines in your changes missing coverage. Please review.

Project coverage is 44.61%. Comparing base (3f40e7c) to head (210dde5).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

code/+matbox/+utility/createBadgeSvg.m
66.66%
9 Missing :warning:

code/+matbox/+py/pipUninstall.m
0.00%
4 Missing :warning:

code/+matbox/+py/pipInstall.m
0.00%
2 Missing :warning:

code/+matbox/+tasks/testToolbox.m
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
- Coverage   46.25%   44.61%   -1.64%
==========================================
  Files          45       49       +4
  Lines         988     1022      +34
==========================================
- Hits          457      456       -1
- Misses        531      566      +35

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


New release for python3 soon?

Many dists are removing py2.7 support now

It's worked with python3 for a few releases now. What is it you're looking for?
On Fri, Jul 3, 2020, at 7:02 AM, joakim-tjernlund wrote:

Many dists are removing py2.7 support now

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/davidjamesca/ctypesgen/issues/89, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI4MSYC2OFRR3GSRWC3RZXCERANCNFSM4OPX6WSA.

--
Alan Robertson
<EMAIL_ADDRESS>

It's worked with python3 for a few releases now. What is it you're looking for?
…
On Fri, Jul 3, 2020, at 7:02 AM, joakim-tjernlund wrote: Many dists are removing py2.7 support now — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#89>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI4MSYC2OFRR3GSRWC3RZXCERANCNFSM4OPX6WSA.
-- Alan Robertson<EMAIL_ADDRESS>
Gentoo is at version 0_p72-r1 and it just support py2_7
Maybe Gentoo is a bit behind?

That's quite old. From before the two of us took this over - many months ago. Try installing it with pip.
On Fri, Jul 3, 2020, at 8:58 AM, joakim-tjernlund wrote:

It's worked with python3 for a few releases now. What is it you're looking for?
… https://www.fastmail.com/mail/compose/M18e0a7b8ab8514afd1bd2ae6?u=c40940ab&theme=light#
On Fri, Jul 3, 2020, at 7:02 AM, joakim-tjernlund wrote: Many dists are removing py2.7 support now — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#89 https://github.com/davidjamesca/ctypesgen/issues/89>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI4MSYC2OFRR3GSRWC3RZXCERANCNFSM4OPX6WSA.
-- Alan Robertson<EMAIL_ADDRESS>

Gentoo is at version 0_p72-r1 and it just support py2_7
Maybe Gentoo is a bit behind?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/davidjamesca/ctypesgen/issues/89#issuecomment-653561248, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI5GW63BXJQ36ZENG4DRZXPXJANCNFSM4OPX6WSA.

--
Alan Robertson
<EMAIL_ADDRESS>

That's quite old. From before the two of us took this over - many months ago. Try installing it with pip.
…
On Fri, Jul 3, 2020, at 8:58 AM, joakim-tjernlund wrote: > It's worked with python3 for a few releases now. What is it you're looking for? > … https://www.fastmail.com/mail/compose/M18e0a7b8ab8514afd1bd2ae6?u=c40940ab&theme=light# > On Fri, Jul 3, 2020, at 7:02 AM, joakim-tjernlund wrote: Many dists are removing py2.7 support now — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#89 <#89>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI4MSYC2OFRR3GSRWC3RZXCERANCNFSM4OPX6WSA. > -- Alan Robertson @.*** Gentoo is at version 0_p72-r1 and it just support py2_7 Maybe Gentoo is a bit behind? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJTJI5GW63BXJQ36ZENG4DRZXPXJANCNFSM4OPX6WSA.
-- Alan Robertson<EMAIL_ADDRESS>
I see a bug from yesterday req an update of the package in Gentoo, I can wait a few days. Thanks


Fix security concern on getting javascript from the outside

@jasonblais I'll do it right away :)

@jasonblais done

Codecov Report

Merging #107 into master will decrease coverage by 1.35%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #107      +/-   ##
==========================================
- Coverage   45.93%   44.58%   -1.36%
==========================================
  Files           8        8
  Lines         788      812      +24
==========================================
  Hits          362      362
- Misses        399      423      +24
  Partials       27       27

Impacted Files
Coverage Δ

server/api.go
0.00% <0.00%> (ø)

server/configuration.go
17.07% <ø> (ø)

server/manifest.go
100.00% <ø> (ø)

Continue to review full report at Codecov.

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