Update 1.13.1

Currently this is to determine how much effort this update might be (by seeing if it builds immediately or if there are weird errors to sort out).

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:116: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:128: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/clone/recipe/meta.yaml:135: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/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_ffcbnhoe8m/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:151: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_ffcbnhoe8m/clone/recipe/meta.yaml:158: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:169: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:118: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:128: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/clone/recipe/meta.yaml:135: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/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_1021m6iuwz/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:152: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_1021m6iuwz/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:169: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_16czp7do8y/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_16czp7do8y/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_16czp7do8y/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_16czp7do8y/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_16czp7do8y/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_16czp7do8y/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_16czp7do8y/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_16czp7do8y/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_16czp7do8y/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_16czp7do8y/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_16czp7do8y/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:172: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b4f3raqv7r/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_b4f3raqv7r/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_b4f3raqv7r/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_b4f3raqv7r/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_b4f3raqv7r/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_b4f3raqv7r/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_b4f3raqv7r/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_b4f3raqv7r/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_b4f3raqv7r/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_b4f3raqv7r/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_b4f3raqv7r/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:172: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3egptg4wzc/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_3egptg4wzc/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_3egptg4wzc/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_3egptg4wzc/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3egptg4wzc/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_3egptg4wzc/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_3egptg4wzc/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_3egptg4wzc/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_3egptg4wzc/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_3egptg4wzc/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3egptg4wzc/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:172: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3dbyqqhmdn/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_3dbyqqhmdn/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_3dbyqqhmdn/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_3dbyqqhmdn/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3dbyqqhmdn/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_3dbyqqhmdn/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_3dbyqqhmdn/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_3dbyqqhmdn/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_3dbyqqhmdn/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_3dbyqqhmdn/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3dbyqqhmdn/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:173: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_39oklvi1km/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_39oklvi1km/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_39oklvi1km/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_39oklvi1km/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_39oklvi1km/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_39oklvi1km/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_39oklvi1km/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_39oklvi1km/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_39oklvi1km/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_39oklvi1km/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_39oklvi1km/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:175: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_45m42_yrd1/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_45m42_yrd1/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_45m42_yrd1/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_45m42_yrd1/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_45m42_yrd1/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_45m42_yrd1/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_45m42_yrd1/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_45m42_yrd1/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_45m42_yrd1/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_45m42_yrd1/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_45m42_yrd1/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:173: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1c83b7gydv/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_1c83b7gydv/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_1c83b7gydv/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_1c83b7gydv/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1c83b7gydv/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_1c83b7gydv/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_1c83b7gydv/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_1c83b7gydv/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_1c83b7gydv/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_1c83b7gydv/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1c83b7gydv/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:173: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9efqokv85c/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_9efqokv85c/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_9efqokv85c/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_9efqokv85c/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_9efqokv85c/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_9efqokv85c/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_9efqokv85c/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_9efqokv85c/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_9efqokv85c/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_9efqokv85c/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_9efqokv85c/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:173: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_63je6d3l_6/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_63je6d3l_6/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_63je6d3l_6/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_63je6d3l_6/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_63je6d3l_6/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_63je6d3l_6/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_63je6d3l_6/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_63je6d3l_6/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_63je6d3l_6/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_63je6d3l_6/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_63je6d3l_6/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:173: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d1ztmtaenr/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_d1ztmtaenr/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_d1ztmtaenr/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_d1ztmtaenr/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_d1ztmtaenr/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_d1ztmtaenr/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_d1ztmtaenr/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_d1ztmtaenr/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_d1ztmtaenr/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_d1ztmtaenr/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_d1ztmtaenr/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:175: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1f2f5a_j5i/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_1f2f5a_j5i/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_1f2f5a_j5i/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1f2f5a_j5i/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_1f2f5a_j5i/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_1f2f5a_j5i/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_1f2f5a_j5i/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_1f2f5a_j5i/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_1f2f5a_j5i/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_1f2f5a_j5i/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1f2f5a_j5i/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:176: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_fb3_g5e3vq/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_fb3_g5e3vq/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_fb3_g5e3vq/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_fb3_g5e3vq/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_fb3_g5e3vq/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_fb3_g5e3vq/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_fb3_g5e3vq/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_fb3_g5e3vq/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_fb3_g5e3vq/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_fb3_g5e3vq/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_fb3_g5e3vq/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:177: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e1wvpex8df/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_e1wvpex8df/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_e1wvpex8df/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_e1wvpex8df/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_e1wvpex8df/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_e1wvpex8df/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_e1wvpex8df/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_e1wvpex8df/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_e1wvpex8df/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_e1wvpex8df/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_e1wvpex8df/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:178: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_733wxw4f07/clone/recipe/meta.yaml:43: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_733wxw4f07/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_733wxw4f07/clone/recipe/meta.yaml:120: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_733wxw4f07/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_733wxw4f07/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_733wxw4f07/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_733wxw4f07/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_733wxw4f07/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_733wxw4f07/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_733wxw4f07/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_733wxw4f07/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:178: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_84uvojcwkg/clone/recipe/meta.yaml:44: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
ERROR: /tmp/abs_84uvojcwkg/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_84uvojcwkg/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_84uvojcwkg/clone/recipe/meta.yaml:131: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_84uvojcwkg/clone/recipe/meta.yaml:131: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_84uvojcwkg/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_84uvojcwkg/clone/recipe/meta.yaml:135: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_84uvojcwkg/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_84uvojcwkg/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_84uvojcwkg/clone/recipe/meta.yaml:141: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_84uvojcwkg/clone/recipe/meta.yaml:160: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:178: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3cxyh0du64/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_3cxyh0du64/clone/recipe/meta.yaml:117: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3cxyh0du64/clone/recipe/meta.yaml:118: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3cxyh0du64/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_3cxyh0du64/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_3cxyh0du64/clone/recipe/meta.yaml:126: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3cxyh0du64/clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3cxyh0du64/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_3cxyh0du64/clone/recipe/meta.yaml:129: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3cxyh0du64/clone/recipe/meta.yaml:129: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_3cxyh0du64/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_3cxyh0du64/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_3cxyh0du64/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_3cxyh0du64/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_3cxyh0du64/clone/recipe/meta.yaml:135: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3cxyh0du64/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_3cxyh0du64/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_3cxyh0du64/clone/recipe/meta.yaml:139: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3cxyh0du64/clone/recipe/meta.yaml:151: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_3cxyh0du64/clone/recipe/meta.yaml:158: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:115: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:118: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/clone/recipe/meta.yaml:127: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:128: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5cg22cky4c/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_5cg22cky4c/clone/recipe/meta.yaml:130: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: /tmp/abs_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/clone/recipe/meta.yaml:135: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/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_5cg22cky4c/clone/recipe/meta.yaml:140: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:152: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_5cg22cky4c/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_81h5ut4b_m/clone/recipe/meta.yaml:89: no_git_on_windows: git should not be used as a dependency on Windows.
WARNING: /tmp/abs_81h5ut4b_m/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: /tmp/abs_81h5ut4b_m/clone/recipe/meta.yaml:152: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_81h5ut4b_m/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ab8ry6fvnd/clone/recipe/meta.yaml:89: no_git_on_windows: git should not be used as a dependency on Windows.
WARNING: /tmp/abs_ab8ry6fvnd/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: /tmp/abs_ab8ry6fvnd/clone/recipe/meta.yaml:152: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_ab8ry6fvnd/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_14xkqoe2w9/clone/recipe/meta.yaml:89: no_git_on_windows: git should not be used as a dependency on Windows.
WARNING: /tmp/abs_14xkqoe2w9/clone/recipe/meta.yaml:130: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: /tmp/abs_14xkqoe2w9/clone/recipe/meta.yaml:152: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_14xkqoe2w9/clone/recipe/meta.yaml:159: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

@dholth Seems that the error on win-64  caused by conda_package_handling:
conda_package_handling.exceptions.ArchiveCreationError: info/test/test/functorch: Cannot stat while writing file: info\test\test\functorch
@danpetry Or do we have issues with CI specifically?

I think we may have introduced a bug in the conda-build release (from about 16 days ago) that keeps a file open. Then we see the same problem in conda-package-handling < 2 and > 2.

@dholth thanks for the investigation on this
@varlackc please see above discussion and description. PO has cleared us to go ahead without Windows for the time being, and build it out later

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_dc9ght12_m/clone/recipe/meta.yaml:93: no_git_on_windows: git should not be used as a dependency on Windows.
WARNING: /tmp/abs_dc9ght12_m/clone/recipe/meta.yaml:134: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: /tmp/abs_dc9ght12_m/clone/recipe/meta.yaml:156: build_tools_must_be_in_build: The build tool ninja is not in the build section.
WARNING: /tmp/abs_dc9ght12_m/clone/recipe/meta.yaml:163: build_tools_must_be_in_build: The build tool ninja is not in the build section.
ERROR: build.sh:166: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found


git: optionally build gnome-keyring and libsecret credential helpers

Some very minor cleanup of the build/install phase too.
Motivation for this change
Encrypted storage for git secret credentials.
There is no change to the default git derivation.
This adds ~200mb to the transitive closure of gitFull because of the new dependencies on libgnome-keyring and libsecret.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: git
Partial log (click to expand)
All tests successful.
Files=802, Tests=18597, 199 wallclock secs (85.12 usr 17.62 sys + 2748.74 cusr 7085.20 csys = 9936.68 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.17.1/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.17.1/t'
make[1]: Leaving directory '/build/git-2.17.1/t'
/nix/store/q7mvbajifj0imyvmvk38ij53bq3lkc4i-git-2.17.1

Success on x86_64-linux (full log)
Attempted: git
Partial log (click to expand)
All tests successful.
Files=802, Tests=18597, 1700 wallclock secs (11.08 usr  2.23 sys + 670.09 cusr 855.41 csys = 1538.81 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.17.1/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.17.1/t'
make[1]: Leaving directory '/build/git-2.17.1/t'
/nix/store/yp4yarn6kwr4m79kvlk7f83ic2zrj3z3-git-2.17.1

Success on x86_64-linux (full log)
Attempted: gitFull
Partial log (click to expand)
All tests successful.
Files=816, Tests=19219, 218 wallclock secs ( 5.11 usr  0.95 sys + 287.14 cusr 277.36 csys = 570.56 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.18.0/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.18.0/t'
make[1]: Leaving directory '/build/git-2.18.0/t'
/nix/store/402f8v55m63n0qnxj58m4imbvc0z5xqs-git-2.18.0

Success on aarch64-linux (full log)
Attempted: gitFull
Partial log (click to expand)
All tests successful.
Files=816, Tests=19219, 277 wallclock secs (90.65 usr 17.67 sys + 3055.00 cusr 7830.16 csys = 10993.48 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.18.0/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.18.0/t'
make[1]: Leaving directory '/build/git-2.18.0/t'
/nix/store/bvj35zx9jmi9wwxcl3ckl4xb8kr9kpw1-git-2.18.0

@jtojnar take another look?

When I install it, I see the following:
warning: skipping dangling symlink '/nix/store/1kj7d2ch4kg3ym0yy5kz02ilnb2dn1pd-user-environment/bin/lgit-credential-libsecret'

When I install it using nix-env, I see the following:
warning: skipping dangling symlink '/nix/store/1kj7d2ch4kg3ym0yy5kz02ilnb2dn1pd-user-environment/bin/lgit-credential-libsecret'

Grah, that's because I made a dumb typo.  Fixed, sorry.

Success on aarch64-linux (full log)
Attempted: gitFull
Partial log (click to expand)
All tests successful.
Files=816, Tests=19219, 277 wallclock secs (90.56 usr 17.60 sys + 3071.82 cusr 7853.25 csys = 11033.23 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.18.0/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.18.0/t'
make[1]: Leaving directory '/build/git-2.18.0/t'
/nix/store/0kjzqvh05ll90iq61gmxlc3prvny845c-git-2.18.0

Success on x86_64-linux (full log)
Attempted: gitFull
Partial log (click to expand)
All tests successful.
Files=816, Tests=19219, 1870 wallclock secs (11.41 usr  2.40 sys + 765.68 cusr 927.53 csys = 1707.02 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory '/build/git-2.18.0/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory '/build/git-2.18.0/t'
make[1]: Leaving directory '/build/git-2.18.0/t'
/nix/store/5is7rb9cki1yjcarribcjr0vbmql9k70-git-2.18.0

thanks for reviewing!

Are you able to use it? I have the helper set
$ git config --system --get credential.helper
libsecret

but git send-email still uses $SSH_ASKPASS for prompt.
So does
echo "protocol=https
host=example.com
path=foo.git
" | git credential fill

and neither action seems to add the key to secret agent.


[BUG] Token used too early

I didn't see this bug before, it has happened last week until now. You could try it at my live demo page: http://m.raphay.com/user/sign_in
Token used too early,<PHONE_NUMBER> <<PHONE_NUMBER>:
{
   "iss":"https://identitytoolkit.google.com/",
   "aud":"176327357454-tv700agv82ggdlujldn205m2i3eprqp8.apps.googleusercontent.com",
   "iat":1442488106,
   "exp":1443697706,
   "user_id":"04296657315607463607",
<EMAIL_ADDRESS>   "provider_id":"yahoo.com",
   "verified":true,
   "display_name":"Tùng Nguyễn",
   "photo_url":"https://s.yimg.com/dh/ap/social/profile/profile_b48.png"
}

Below is the main source code of /user/sign_in:
$gitkitClient = Gitkit_Client::createFromConfig($config);
$user = null;

try {
    $user = $gitkitClient->getUserInRequest();
} catch (Exception $e) {
    die($e->getMessage());
}

if ($user) {
    echo 'Email: ' . $user->getEmail() . '
';
    echo 'Name: ' . $user->getDisplayName() . '
';
    echo 'Provider ID: ' . $user->getProviderId() . '
';
    echo 'User ID: ' . $user->getUserId() . '
';
    echo 'Password Hash: ' . $user->getPasswordHash() . '
';
    echo 'Photo URL: ' . $user->getPhotoUrl() . '
';
    echo 'Salt: ' . $user->getSalt() . '
';
    echo 'Email Verified: ' . $user->isEmailVerified() . '
';
    echo 'Delete account' . '
';
} else {
    echo 'Not logged in.';
}

I have checked again, and detected that my server's time had a little lag behind the world's time. After re-sync the time, everything works fine again.


Minimal changes to resolve #38

Change from RIPEMD160 to SHA256
resolves #38
If #53 is merged we can additionally remove ripemd160 from the glide file (or dep file if #52 get's merged first)

Maybe it would be better if we have a sha256truncated utility function that we can just call with the buf, instead of having to create and write to the hasher and then slice it every time. At least that way if we change it again we just change it in one place

Good point. It's a bit messy with all the [:20] right. My intention was to submit this PR as is (with the least changes possible) and further improve this in a followup PR shortly after (see https://github.com/tendermint/iavl/issues/38#issuecomment-386290979 and https://github.com/tendermint/iavl/issues/11). Will do as you suggested and submit another PR later.

Maybe it would be better if we have a sha256truncated utility function that we can just call with the buf, instead of having to create and write to the hasher and then slice it every time.

I took a slightly different approach and added a tiny package for the hasher. It makes the hasher a bit more visible in generated godoc and adds a bit more flexibility if we switched to another hasher.
PTAL @ebuchman.


How to get column editing to work

I am able to use Alt+Mouse to select a column of text, but when I start typing it only starts typing on the bottom of the selection instead of all of the lines. Am I missing something?

Could Scintilla.AdditionalSelectionTyping be what you're looking for? Some more information is available on the wiki.

Thanks alot!


Fix test failures

These changes look good to me. Lets merge and then just double check that all the tests do in fact work.

@ekmartin can you rebase on top of master? For Cargo.lock, just remove the file, run cargo update, and commit the resulting one.

@jonhoo: rebased 👍

:tada:
@ms705 can you take a look at the hotsoup failures? Maybe we should just delete that binary from master?


improve hyperparameters documentation

@jbueltemeier you can look at the built documentation by clicking on "Details" for the readthedocs.org check below.

I basically split the changes into two categories:

behavioral changes and
hyper parameter changes.

The former includes "unreasonable" changes (score_correction_factors, loss_reductions other than "mean", ...), while the latter includes "reasonable" changes (score_weight, num_steps, ...).
All behavioral changes are listed in the Implementation Parameters section. In this category I think we should only give the user the ability to use it with or without impl_params. Thus, these parameters are not part of the hyper_parameters().
On the other hand, functionality that has no behavioral changes (for example image_pyramid) is not listed in the Implementation Parameters section.

Okay, I wasn't aware of that, but this is a very good solution. So you can forget my comments above, they only refer to the behavioral changes.

@jbueltemeier you can look at the built documentation by clicking on "Details" for the readthedocs.org check below.

:wink:


refactor LadderView

Thanks for pointing out for me.
About the problem with constructor, I tried to replace constructor with initialize before with UserView and MainUserView but failed. Is there any differences between this View and these 2 Views?

There shouldn't be, but the code base is a bit of a mess, so sometimes weird things happen... Possibly it's because UserView is a subclass of CocoView, the others are subclasses of RootView. So they can be handled differently.

👍 Thanks for continuing to move our codebase in the right direction!


Feature/training camp api

Practice for Api creation on on-http
Create following APIs
-GET /api/2.0/config/logcolor : Return whether the log color configuration
{logColorEnable: true} or {logColorEnable: false}
https://github.com/RackHD/on-core/blob/master/lib/services/argument-handler.js#L56
https://github.com/RackHD/on-core/blob/master/lib/services/configuration.js#L81
-POST /api/2.0/config/logcolor { logColorEnable: true/false }: To enable or disable the log color.
https://github.com/RackHD/on-core/blob/master/lib/services/configuration.js#L73
https://github.com/RackHD/on-core/blob/master/lib/serializables/log-event.js#L129
Check items:
-Make sure the swagger UI shows the new APIs.
-Make sure your API works as expected.
-Run on-http on foreground through node index.js, and check setting is available or not.

:+1:  btw, you may squash some commits into one in formal PR, if you decide that they are not critical and you would like to keep them in the official repo.


Istio component

What does this PR do?
Add Istio support for kubernetes
deploying via helm charts and optional setup of testing application and gateway routing example
Which scenarios this will impact?
Motivation
Additional Notes

/merge


Error: container's runAsUser breaks non-root policy , container: k8tz)

Hi,
I do have this error on a pod, probably due to a Security Context.
The pod is longhorn-driver-deployer from the longhorn storage system.
Is there a way to make it work without hacking Longhorn?
Thank you.

Thanks for the quick fix @yonatankahana! Is there any chance that you could create a release / Docker tag that contains this fix?


create github page for Homepage

create homepage page from prod branch

people not must see this ,but okay


Support for adding a prefix to branch name created by NuKeeper.

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Feature.
:arrow_heading_down: What is the current behavior?
NuKeeper is currently responsible for creating branch names. There aren't any options for users to influence the branch naming. This resulted for us in this:

We would like to organize these branches in a nukeeper/ directory.
:new: What is the new behavior (if this is a feature change)?
Added functionality for providing a prefix that gets added in front of the branch name that NuKeeper creates.
:boom: Does this PR introduce a breaking change?
It shouldn't.
:bug: Recommendations for testing
No recommendations for testing. Mostly interested on feedback on code.
:memo: Links to relevant issues/docs
There isn't an existing issue yet.
:thinking: Checklist before submitting

[x] All projects build
[x] Relevant documentation was updated

LGTM


How limit/remove related post in change?

Hi, I have a problem regarding the related posts part on the post edit page.
Due to the large amount of posts I'm having a very big slowdown on the page, it would be necessary to limit or even remove the "related posts" field.
Edit:
BLOG_USE_RELATED = False
Not working.

Have you also changed this in the apphock config? On the admin panel there is are settings for djangocms blog, one for each apphook. In the setting, disable related posts.


Create a new pull request by comparing changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 95.735%

Files with Coverage Reduction
New Missed Lines
%

js/src/dom/event-handler.js
1
92.27%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1981

Relevant Lines:
2030

💛  - Coveralls


Fix python building to include hashlib's c helper function

I submitted PR #36 through #39 for this already, but am creating an issue here just for completeness.
The basic idea is hashlib uses a C helper function to query openssl lib for the hash functions provided by it (such as ripemd160).  The 1-line change PR I submitted adds the compilation of the C function to the final built libPython.a, so that hashlib can do its magic and provide all hash functions.
Without it, only a very basic set of hash functions are compiled in to libPython.a's modules.  With it, you get more hash functions.  It's a win/win as far as I can tell. ;)

Thanks - the build and release process takes a while, so these should start trickling into new support binaries over the next day or so.

I've just finished releasing 3.4-b6, 3.5-b7 and 3.6-b5, integrating the _hashlib changes.

That was fast.  👍
Thank you for providing this great support lib and for briefcase and for everything else!


[Feature request]Option to unlock inventory slots bottom up.

Right now, the slots are unlocked in the following order

slots on the hotbar
slots top row - down in the inventory.

I would love it if there were a option that would allow the first row of the inventory to be unlocked(step 2) to be the one closest to the hotbar(so unlocking down-up, instead of the current behavior)

Right now, slots are unlocked in the same order that they're indexed in the inventory, which in turn is tied to things like item pickup slots or item shift-clicking. To change the order in which slots are unlocked would most likely cause some unwanted behaviors if done in isolation. While I'm sure that such unwanted can be circumvented or worked around, I don't think this feature would be important enough to try implementing that.
I'll leave this issue open for a bit of time in case someone else comes across this and want to try implementing it.


AttributeError: module 'torchvision.transforms' has no attribute 'Resize'

I'm running the srgan.py implementation and receive the following error:
Namespace(b1=0.5, b2=0.999, batch_size=1, channels=3, checkpoint_interval=-1, dataset_name='img_align_celeba', decay_epoch=100, epoch=0, hr_height=256, hr_width=256, lr=0.0002, n_cpu=8, n_epochs=200, sample_interval=100)
Downloading: "https://download.pytorch.org/models/vgg19-dcbb9e9d.pth" to /Users/Username/.torch/models/vgg19-dcbb9e9d.pth
100%|███████████████████████████████████████████| 574673361/574673361 [00:34<00:00, 16895858.86it/s]
Traceback (most recent call last):
  File "srgan.py", line 104, in <module>
    lr_transforms = [   transforms.Resize((opt.hr_height//4, opt.hr_height//4), Image.BICUBIC),
AttributeError: module 'torchvision.transforms' has no attribute 'Resize'

If you need any additional information let me know...

What version of torchvision are you using? Since torchvision.transforms.Resize is visible in their docs updating you package should solve your issue.

It seems torchvision 0.1.9 was what got installed when using sudo pip3 install -r requirements.txt. I ran sudo pip3 install torchvision --upgrade which installed version 0.2.1 which did resolve the issue — thank you!

I was having the error: "AttributeError: 'module' object has no attribute 'Resize' ". I installed torchvision-0.2.0-py2.py3-none-any.whl from the wheel file available at https://download.pytorch.org/whl/cu90/torch_stable.html and it solved my problem. I was previously using torchvision==0.1.6 when the error occured.


Make getting a PCE App easy

Context
Currently, when you want to build your privacy portal using blindnet devkit, you are supposed to make a webpage, include the PRCI web component and give to it a URL of the PCE. See example here:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <title>Privacy Components for the Web - Minimal Static Demo</title>

Privacy Components for the Web - Minimal Static Demo

Assert Your Privacy Rights

    <bldn-priv-request computation-base-url="http://localhost:9000/v0"></bldn-priv-request>

Intended outcome
I want to make the integration, for clients using our PCE instance, as quick as possible. So I want them to get (from us, or maybe later through an interface) a URL* to provide in the computation-base-url argument, so that they can really have an easy quick-start.
It should also be possible (independently of this web page and the example code given above) to provide configuration meta-data/settings to configure the PCE App.
*several clients get to use the same URL, but must specify particular app id and other ifnromation used to identify them.

If no url is provided, staging one is used.

It should also be possible (independently of this web page and the example code given above) to provide configuration meta-data/settings to configure the PCE App.

PCE configuration settings shouldn't be set here since it's a data subject facing component. Do you have some particular setting in mind?

*several clients get to use the same URL, but must specify particular app id and other ifnromation used to identify them.

App information is extracted from the token, so no need to specify it in this component.

I am fine with all you wrote. My issue description is slightly outdated.


es https curl

Hi dear,
I config application.conf  for  es invite,but the password “admin”  is no encryption。please help me，how can i config encryped password。
thanks！

closed: i don,t config cluster info , user self  input user and password in welcome page.


Add support for flag enum

As followup #205 I have checked that we do not have a test for another enum base class. So I prevent future failures, I added tests and spotted that flag support was not fully functional as it does not support element combinations.
Also add StrEnum test.

Summary by CodeRabbit

New Feature: Enhanced the QEnumComboBox class to support Flag enums in addition to regular enums. This allows users to select multiple options from a combo box.
Refactor: Improved the internal handling of enum classes in QEnumComboBox by introducing helper functions for retrieving enum member names and values.
Test: Added comprehensive test cases for the new Flag enum support in QEnumComboBox, ensuring robust functionality and error handling.

Thanks @Czaki
Looks like it needs updating for everything below 3.11

Looks like it needs updating for everything below 3.11

Yes. I also hit problems as there was a bug in the new name mechanism in Python 3.11(.3).
As it is fixed in 3.11.5 then I left only the workaround code with a docstring explanation.


informative message on docker pull fail

Can one of the admins verify this patch?

This fixes #1020

@jenkins-droid test this please

Can one of the admins verify this patch?

@jenkins-droid test this please

Can one of the admins verify this patch?

@jenkins-droid test this please

Jenkins Linux s390x Build #2864 [push] informative message on d... started at 10:00

Jenkins Linux ppc64le Build #1982 [push] informative message on d... started at 10:04

Jenkins Linux amd64 Build #2875 [push] informative message on d... started at 09:01

Jenkins Linux s390x Build #2864 [push] informative message on d... passed after 39 min

Jenkins Linux amd64 Build #2875 [push] informative message on d... passed after 51 min

Jenkins Linux ppc64le Build #1982 [push] informative message on d... passed after 52 min


[CI][Packaging][RPM][CentOS] Could not resolve host: mirrorlist.centos.org

Describe the bug, including details regarding any error messages, version, and platform.
The centos-7-amd64 job:
https://github.com/ursacomputing/crossbow/actions/runs/9757626828/job/26930405868#step:8:621
#8 17.58 Could not retrieve mirrorlist [http://mirrorlist.centos.org?arch=x86_64&release=7&repo=sclo-rh](http://mirrorlist.centos.org/?arch=x86_64&release=7&repo=sclo-rh) error was
#8 17.58 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
#8 17.58
#8 17.58
#8 17.58  One of the configured repositories failed (Unknown),
#8 17.58  and yum doesn't have enough cached data to continue. At this point the only
#8 17.58  safe thing yum can do is fail. There are a few ways to work "fix" this:
#8 17.58
#8 17.58      1. Contact the upstream for the repository and get them to fix the problem.
#8 17.58
#8 17.58      2. Reconfigure the baseurl/etc. for the repository, to point to a working
#8 17.58         upstream. This is most often useful if you are using a newer
#8 17.58         distribution release than is supported by the repository (and the
#8 17.58         packages for the previous distribution release still work).
#8 17.58
#8 17.58      3. Run the command with the repository temporarily disabled
#8 17.58             yum --disablerepo=<repoid> ...
#8 17.58
#8 17.58      4. Disable the repository permanently, so yum won't use it by default. Yum
#8 17.58         will then just ignore the repository until you permanently enable it
#8 17.58         again or use --enablerepo for temporary usage:
#8 17.58
#8 17.58             yum-config-manager --disable <repoid>
#8 17.58         or
#8 17.58             subscription-manager repos --disable=<repoid>
#8 17.58
#8 17.58      5. Configure the failing repository to be skipped, if it is unavailable.
#8 17.58         Note that yum will try to contact the repo. when it runs most commands,
#8 17.58         so will have to try and fail each time (and thus. yum will be be much
#8 17.58         slower). If it is a very temporary problem though, this is often a nice
#8 17.58         compromise:
#8 17.58
#8 17.58             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
#8 17.58
#8 17.58 Cannot find a valid baseurl for repo: centos-sclo-rh/x86_64

Component(s)
Continuous Integration, Packaging

Issue resolved by pull request 43127
https://github.com/apache/arrow/pull/43127


[Run] Word not first search result

Microsoft PowerToys version
0.41.4
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

✔ Expected Behavior
word is displayed as first result
❌ Actual Behavior
word is displayed as third result
Other Software
No response

Can reproduce it. We should probably tweak the scoring system.
@floh96
Take into account that by default Include in global result is unchecked for Windows settings. So in default settings, you don't experience this issue.


Move CustomerInfo to non-expect classes and use new mappings and models modules

Description
This PR moves the CustomerInfo, EntitlementInfos, EntitlementInfo and Transaction models to the models module, converts them to classes without expect/actual and moves their mapping to the mappings module.

Tests are not passing in these branches it seems (only on PRs pointing to main). Tests are passing locally for me now though, so going to merge this.


SmoothControls should take devicePixelRatio into account

Description
We should take window.devicePixelRatio into account when processing the user's input. Translation, rotation and zoom amounts will otherwise depend on the device pixel density and will be inconsistent between devices.
Live Demo
https://model-viewer.glitch.me/
Browser Affected

[x] Chrome
[x] Edge
[x] Firefox
[x] Helios
[x] IE
[x] Safari

OS

[x] Android
[x] iOS
[x] Linux
[x] MacOS
[x] Windows

Versions

model-viewer: v0.7.0

The natural thing to me would be to normalize based on width and height (so that dragging all the way across the canvas gave the same amount of motion). But I'm not totally sure that's right either. Is there some UX person we could ask who's studied this?


Typo in Zipalign section?

The section states

The follow command will use the signed APK and produce a signed, zipaligned APK called helloworld.apk that is ready for distribution.

It then goes on to provide the following command:

$ zipalign -f -v 4 mono.samples.helloworld-unsigned.apk helloworld.apk

The text stating that the file is initially signed but the command having unsigned in the name is confusing. Also, from reading the top of the page I was initially under the impression that zipalign must be performed before signing. However, from reading this section I wasn't so sure anymore.
Turns out, the correct way to do it depends on whether you are signing with apksigner or jarsigner. If you're signing with apksigner, zipalign must only be performed before signing. If you're signing with jarsigner, zipalign must only be performed after signing.
Since the page is recommending that users sign with apksigner, it would be nice to see the zipalign section follow the apksigner method of performing zipalign before signing. In other words, just change the text before the sample command by replacing both of the signed values to unsigned. It would also be nice to have a note in the jarsigner section that if a user chooses to sign with jarsigner, signing must happen before performing zipalign (and, perhaps, link to the zipalign documentation) .

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

ID: d6c53ae1-252f-3869-b8c4-4ffb2e927444
Version Independent ID: d2343aa0-f82b-d2fe-c6a2-b9b47a93df7b
Content: Manually Signing the APK - Xamarin
Content Source: docs/android/deploy-test/signing/manually-signing-the-apk.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @davidortinau
Microsoft Alias: daortin

Thanks for submitting an issue and we apologize for the delayed response. The requested updates haven't been made since the creation of the issue, and the timeline for resolution may vary based on resourcing, so the issue is being moved to an internal repo to better track it.


Ignoring squash option in native representation

Could you add a test to prove that this change is working.
I think that hcl:squash is the same as json:inline. Possible to confirm?

Seems to work


Select input needs option for "nothing" selected / validation bug when option value is "space" char.

I was trying to quickly set up a select input and wanted it to have an empty option - no visible placeholder/label, value would be something that would be easy to filter out as "not selected". It's important that if the field is required - nothing would be preselected for user. If nothing would be chosen - it would show an error.
Not sure how to add a custom validation rule for this - could you give an example how to do it?
If I tried to use a "space" character as value for option - at first submit it shows a good error. But if I still don't choose anything again and click submit button - it throws this error (option value is a "space" character:

TypeError: FrontendForms\Form::encryptDecrypt(): Argument #1 ($string) must be of type string, null given, called in .../FrontendForms/Formelements/FormValidation.php on line 93

How the option is set:
$input->addOption(' ', ' ');
How the option is output:
<option value=" " selected> </option>

Hello Donatas
I am not sure if I understand what you want to achive and why the empty option should not have a label.
If you want to add an empty option, there is an inbuild method. Take a look at the following example:
$php = new \FrontendForms\Select('php'); $php->setLabel('My preferred PHP version is'); $php->addEmptyOption(); $php->addOption('PHP 6', 'PHP 6'); $php->addOption('PHP 7', 'PHP 7'); $php->addOption('PHP 8', 'PHP 8'); $php->setRule('required'); $form->add($php);
The addEmptyOption() method works with validation.


fix broken version selector on mobile due to merge skew

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b60668fd56e3410049cef1acabf365e072a87d39/


Problem using tigerbeetle image: error: permissiondenied

Describe the bug
From TigerBeetle docs, tried running the docker commands and they fail. Using docker works correctly, but not with orbstack.
To Reproduce

Run

docker run -v $(pwd)/data:/data ghcr.io/tigerbeetle/tigerbeetle \
    format --cluster=0 --replica=0 --replica-count=1 /data/0_0.tigerbeetle

Will end up unexpectedly with a error: PermissionDenied error.

Expected behavior
Should end correctly.
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)
System info:
macOS: 14.4.1 (23E224)
CPU: arm64, 10 cores
CPU model: Apple M1 Max
Model: MacBookPro18,2
Memory: 32 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-04-16T09-52-03.218795Z.zip

Screenshots and additional context (optional)
No response

TigerBeetle requires io_uring. Docker 25.0.0 blocks io_uring by default: https://github.com/moby/moby/pull/46762
I've submitted a PR to fix the command in TigerBettle's docs: https://github.com/tigerbeetle/tigerbeetle/pull/1995
Please add --security-opt seccomp=unconfined to the docker run command. This keeps most security features intact, as opposed to --privileged.


change docs/writing_plugins adds exec method implementation

Adds exec method implementation
Fixes #789

Thanks @ankurjain00 !


fix(slides): deprecation notice typo's

Short description of what this resolves:
Small typo's in the deprecation notice for getSlider().

Thanks!


[WFLY-7514] XTS graceful shutdown

https://issues.jboss.org/browse/WFLY-7514
https://issues.jboss.org/browse/JBEAP-7421
TODO add EAP pull request

Stuart and Alessio provided functionality which is needed to implement XTS graceful shutdown. Is it OK to have all these commits in this pull request?

@gytis yes, no problem

@kabir , thanks. I'll raise an EAP pull request then.

+1 on the ws part of the changes


plainButtonWithNormalImageName method not found

First, I download the code, and then I run the code, the error say the EasyLayout.h not found. so I download the EasyLayout Code, and add it to the Xcode project. And I run again, the error say plainButtonWithNormalImageName not found.I have to annotate the code in order to run successfully. where is the method?

So, any update about "plainButtonWithNormalImageName"? since there's no where to find it~

The plainButtonWithNormalImageName is in the EasyLayout project.
https://github.com/bentford/EasyLayout/blob/master/EasyLayoutLibrary/ButtonMaker.h
Make sure to checkout submodules using command listed above.

Yes, but I only saw "plainButtonWithNormalImage", not "plainButtonWithNormalImageName"; Is that right?
Sorry for I'm new in iOS, please let me know if I'm wrong, thanks.

To fix, in FindDeviceViewController.m, change to this line:
modeButton = [ButtonMaker plainButtonWithNormalImage:
                                [UIImage<EMAIL_ADDRESS>                                selectedImage:[UIImage<EMAIL_ADDRESS>


Change the workflow

Hello world ! :wave:

This is a multi-line test comment

With GitHub Markdown :sparkles:
Created by create-or-update-comment

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

approve

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

Please review the pull request.
If approved please comment "approve".
Otherwise make comments on the code, or to close the pull request comment "abort".

approve

approve


Target [Psr\Container\ContainerInterface] is not instantiable while building [RoachPHP\Core\Runner]

If I run php artisan roach:run MySpider I get:
Target [Psr\Container\ContainerInterface] is not instantiable while building [RoachPHP\Core\Runner].

Adding the following to \RoachPHP\Laravel\RoachServiceProvider::registeringPackage() seems to fix it.
$this->app->bind(\Psr\Container\ContainerInterface::class, \RoachPHP\Core\DefaultContainer::class);

Is it possible to get this updated please (assuming that's the correct fix)?

I'm unable to reproduce this issue on a fresh Laravel installation. Can you provide a repository that reproduces this error?

Hmm. I'm using October CMS v3 which is built on Laravel 9. I guess there's a difference in the application config or something compared to the Laravel default. I'm no expert on this part of Laravel tbh.
No worries, I can add the binding in my own code and that seems to work too. Thanks for your time.


documentation for get_details functions for dockets, documents, and comments

Below are the fields returned when we query details on a specific document ID using

https://api.regulations.gov/v4/dockets/?[id]&[api_key]
https://api.regulations.gov/v4/documents/?[id]&[api_key]
https://api.regulations.gov/v4/comments/?[id]&[api_key]

Note that the API does not return the originally supplied id, so get_details functions need to add it back in after extracting the data frame from the json.
Also, note that the API does not always return the same fields for different documents of the same type.
> names(docket_details)
[1] "displayProperties"
[2] "modifyDate"
[3] "dkAbstract"
[4] "agencyId"
[5] "title"
[6] "docketType"
[7] "objectId"

> names(document_details)
[1] "allowLateComments"
 [2] "paperLength"
 [3] "paperWidth"
 [4] "agencyId"
 [5] "comment"
 [6] "displayProperties"
 [7] "docketId"
 [8] "documentType"
 [9] "firstName"
[10] "objectId"
[11] "lastName"
[12] "modifyDate"
[13] "pageCount"
[14] "postedDate"
[15] "receiveDate"
[16] "title"
[17] "trackingNbr"
[18] "withdrawn"
[19] "openForComment"

> names(comment_deatils)
[1] "commentOn"
 [2] "commentOnDocumentId"
 [3] "duplicateComments"
 [4] "agencyId"
 [5] "comment"
 [6] "displayProperties"
 [7] "docketId"
 [8] "documentType"
 [9] "firstName"
[10] "objectId"
[11] "lastName"
[12] "modifyDate"
[13] "pageCount"
[14] "postedDate"
[15] "receiveDate"
[16] "title"
[17] "trackingNbr"
[18] "withdrawn"
[19] "openForComment"

The API does not return the same fields for all documents; for document "OMB-2023-0001-0001", it returned 20 fields rather than 19:
> names(document_details)
 [1] "allowLateComments"
 [2] "commentEndDate"
 [3] "commentStartDate"
 [4] "frDocNum"
 [5] "paperLength"
 [6] "paperWidth"
 [7] "agencyId"
 [8] "displayProperties"
 [9] "docketId"
[10] "documentType"
[11] "fileFormats"
[12] "objectId"
[13] "modifyDate"
[14] "originalDocumentId"
[15] "pageCount"
[16] "postedDate"
[17] "receiveDate"
[18] "title"
[19] "withdrawn"
[20] "openForComment"

For document "OMB-2023-0001-12471", it returned 15:
> names(document_details)
 [1] "duplicateComments"
 [2] "agencyId"
 [3] "displayProperties"
 [4] "docketId"
 [5] "documentType"
 [6] "fileFormats"
 [7] "objectId"
 [8] "modifyDate"
 [9] "originalDocumentId"
[10] "pageCount"
[11] "postedDate"
[12] "receiveDate"
[13] "title"
[14] "withdrawn"
[15] "openForComment"

Note that paths for docket details cannot contain  "include=attachments&"

Interstingly, paths for comments and other documents appear to work with /comments/ or /documents/ in the path (i.e., the API returns document details when a document id is supplied, even when the path says /comments/


Live server stop working after 1.31 update

Issue Type: Bug
dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/.../.vscode/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
Expected in: flat namespace
dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/.../.vscode/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
Expected in: flat namespace
Extension version: 5.3.1
VS Code version: Code 1.31.0 (7c66f58312b48ed8ca4e387ebd9ffe9605332caa, 2019-02-05T22:32:14.164Z)
OS version: Darwin x64 18.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (4 x 2000)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 3

Memory (System)
8.00GB (0.08GB free)

Process Argv

Screen Reader
no

VM
0%

After the most recent VS update I'm also getting the following error: "Extension Host Terminated" and restarting it won't work. I had to disable Live Server in order to get VS to work at all.
Extension version: 5.3.1
VS Code version: Version 1.31.0 (1.31.0)

Same error as above.
5.3.1
1.31.0

Yes same here.
Live Server 5.3.1
VS Code <IP_ADDRESS>
I had to go all the way back to 4.1.0 to get it working again. (on Mojave)Just go to extension settings/ live server/ settings and and "install another version"

Hello, this help me to solve the problem:
https://github.com/ritwickdey/vscode-live-server/issues/273#issuecomment-461185641
Update Live server to version 5.4.0 via vsix file
https://github.com/ritwickdey/vscode-live-server/releases

Same issue after update to vscode version 1.31

Please try the 5.4.0 in the Releases tab.
We are awaiting feedback before publishing it to the Visual Studio Marketplace.

Please download 5.4.0 from this repo (under Releases), and try installing that manually.
View -> Command Pallete... -> Extensions Install from VSIX...

Please install v5.4.0 from marketplace. This issue has been fixed!
// Duplicate of #273


Add a quick "Copy to Clipboard" context menu.

This PR adds a simple "Copy Photo" context menu which put the current generated photo into the clipboard.
Allowing the users to copy the photo to the clipboard makes it faster to quick share the photo to any app they want.
Example:

+1


[Bug]

Commands that require a players name do not work.
like /class exp Dimrok 1 class does not work, but I do /class exp 1, it will give me 1 exp.
See this image: https://i.imgur.com/U1N7dYC.png
For some reason the command breaks when you try to use the players name in the command

same for me, this has something to do with the server software as well. I am on paper-465 here is everything fine but after that (this is not exaclty, next version i tested was 500) this error is comming. please fix, I want to update my paper Version xD thx for taking over this project ^^

same for me, this has something to do with the server software as well. I am on paper-465 here is everything fine but after that (this is not exaclty, next version i tested was 500) this error is comming. please fix, I want to update my paper Version xD thx for taking over this project ^^

we're going to fix it, thanks for the report.


when is this actually defined?

I am getting warning C4013: "alignof" undefined.  Your page gives no suggestion as to when it would be undefined, except if language extensions have been disabled which I am not doing.
Also, forcing me to create an account, log in, type in a further emailed verification code is putting too many barriers in the way of me simply giving you valuable feedback.  It lessens my interest in bothering to do so in the future.  Given all the effort you're putting me through to improve your offering, what do I get out of it?

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

ID: e2bb3ebf-3916-1509-086d-091e938dd15b
Version Independent ID: a1aad343-6b13-622e-0e7b-c80041455f2e
Content: alignof Operator
Content Source: docs/cpp/alignof-operator.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@SwissFrank
I'm sorry it's giving you trouble. Thanks for taking the time to register. You now have a GitHub account, which might be useful in other contexts, too.
The alignof keyword is available in all C++ /std modes, including the default. It's available in C as an alias for _Alignof under /std:c11 and /std:c17 if you have #include <stdalign.h> in your source code. (C didn't adopt the _Alignof keyword until C11. The __alignof form is available in the default C compiler as a Microsoft extension to C89. That's what might be turned off by /Za.)
Generally speaking, keywords aren't defined anywhere, they're built into the parser. The error message indicates that the parser doesn't expect the alignof keyword to appear where you're using it, because it decided it was an identifier, not a keyword. That suggests to me you're compiling your code as C in the default mode.
So first, I'd verify that you're compiling as C++, if your code is in fact C++. Code compiled as C doesn't support the alignof keyword by default.
If you're compiling C, make sure you're using at least the /std:c11 switch, and verify that you've included <stdalign.h> to define the alignof alias. And it would probably help to look at the C documentation for alignment instead of the C++ documentation.
In general, we don't provide troubleshooting for every possible way you can get an error in the docs, because it's not practical. I'm working on updates for the C11/C17 docs, and I'll include a link from the C++ docs for people who aren't getting the right documentation when they search.


CASSANDRA-13391 Added --all to ClearSnapshot command

Added --all to ClearSnapshot command, so entering the command without a parameter will now throw an exception instead of deleting all the snapshots.

what the hell - it's the wrong branch. My mistake, clearly.


Sync history and Sync diff don't work : Cannot read properties of null (reading 'listHistory')

Hello
Show Git Diff view for active file works well without an issue. However, Show Sync history for active file and Show Sync diff view for active file don't work at all showing an empty window. (BTW, I don't exactly know what they do actually)
The developer's console shows the following error:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'listHistory')
    at t.<anonymous> (app.js:1:1970557)
    at app.js:1:235078
    at Object.next (app.js:1:235183)
    at s (app.js:1:233922)

Obsidian Git version : 1.28.0
Version History Diff version : 2.0.5
Obsidian App version : 0.15.9
OS : Windows 10 21H2

I am answering myself. Sync history and Sync diff seem to be related to the core plugin Sync, and if you don't use it, the result being empty is right -- however, it would be better to display some message instead, something like "Sync is not enabled" or so.


vid2seq installation error:  No matching distribution found for t5x

I was trying to install vid2seq.
I created a fresh conda virtual environment with Python=3.9.
Then, according to documentation when I am running this following command
pip install -r scenic/projects/vid2seq/requirements.txt

It throws this error
Collecting dmvr@ git+https://github.com/deepmind/dmvr.git
  Cloning https://github.com/deepmind/dmvr.git to /tmp/pip-install-g5bw7bnk/dmvr_2884f2053dd747c6b11a633bad9e9ef8
  Running command git clone --filter=blob:none --quiet https://github.com/deepmind/dmvr.git /tmp/pip-install-g5bw7bnk/dmvr_2884f2053dd747c6b11a633bad9e9ef8
  Resolved https://github.com/deepmind/dmvr.git to commit 77ccedaa084d29239eaeafddb0b2e83843b613a1
  Preparing metadata (setup.py) ... done
Collecting gin-config
  Using cached gin_config-0.5.0-py3-none-any.whl (61 kB)
Collecting t5
  Using cached t5-0.9.3-py3-none-any.whl (153 kB)
ERROR: Could not find a version that satisfies the requirement t5x (from versions: 0.0.0)
ERROR: No matching distribution found for t5x

Am I missing something, or is the requirements.txt incorrect?

It seems the t5x installation fails. You may try to follow the t5x installation instructions from https://github.com/google-research/t5x.

It seems the t5x installation fails. You may try to follow the t5x installation instructions from https://github.com/google-research/t5x.

The t5x gpu is so hard to use. After pip install -r pile_requirements.txt, there is still no t5x in the conda environment. Is there anything wrong?
One more thing, Could you give the T5.1.1 Base model link directly? I cannot found the link in the t5x Readme.

The t5x gpu is so hard to use. After pip install -r pile_requirements.txt, there is still no t5x in the conda environment. Is there anything wrong?

I was able to install t5x using the following steps :
git clone https://github.com/google-research/t5x.git  # Clone repo if not done already
cd t5x
python3 -m pip install -e .[gpu]

The t5x gpu is so hard to use. After pip install -r pile_requirements.txt, there is still no t5x in the conda environment. Is there anything wrong?

I was able to install t5x using the following steps :
git clone https://github.com/google-research/t5x.git  # Clone repo if not done already
cd t5x
python3 -m pip install -e .[gpu]

Above worked for me on Mac. I still ran 'pip install t5x' (no errors now). thx

@antoyang Could you let me know which revision you used to run the vid2seq model?

@toshohirasawa I used Google's internal environment which I cannot access now as this was an internship work, so I am not sure which t5x version was used.
If you are struggling with the installation, you may have a look at the updated PyTorch implementation (with a few differences explained in the readme) here: https://github.com/antoyang/VidChapters.


wrong error reporting

when you dynamically open a dialog that is a part of a child lazy-loaded module, you will get a wrong error message
ERROR
Error: NgxFormly: missing `forRoot()` call. use `forRoot()` when registering the `FormlyModule`.

for this minimal reproduction, when you click on openDialog it calls the openDialog() method which opens the dialog dynamically
  openDialog() {
    console.log('opening lazyDialog');
    import('./lazy-load/lazy.module')
      .then((mod) => console.log({ mod: mod.LazyModule }))
      .then(() => this.dialog.open(LazyComponent, { data: {} }));
  }

I fixed this issue by adding FormlyModule to app.module.ts but don't know why it solved my issue.
another solution is to replace FormlyModule.forChild() in the lazy-loaded module with FormlyModule.forRoot()
anyway the fix is differ than the error message by formly

The message indicate that Formly needs to be imported, either using forRoot or forChild which depend on the the use-case.
PR welcomed to improve the message!

I know what the error message tells us, but this is NOT the exact issue, FormlyModule.forChild() already imported correctly
and works as expected when you navigate to '/lazy'
the problem appears when you open the same component as a dialog (instead of navigating to it), one must add FormlyModule again in app.module which is not expected by the consumer of app.module (other modules that imported in lazyModule don't need to be imported again in appModule but FormlyModule)
also, this message doesn't guide to the exact issue

Ok I see, will check further


[Federation] Joining cluster service accounts roles created by kubefed join are very broad

 Issue by perotinus
Wednesday Mar 01, 2017 at 20:25 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/42355

This is a follow-up to #41267.
Currently, the service account created in a joining cluster by kubefed join has role-based access to all APIs and all resources in all namespaces. We should determine if there is a tighter reasonable subset, or decide that this is conceptually OK. Making a tighter subset will be a small maintenance burden, and will potentially cause issues if people are trying to use older versions of kubefed with newer versions of the control plane.

 Comment by fejta-bot
Monday Jan 08, 2018 at 17:25 GMT

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

cc @perotinus


Update notebook v6.x and remove traitlets v5.9.0 from required notebook dependencies

Once a new notebook 6.x package version is released with this fix, remove traitlets v5.9.0 from required dependencies.
PR pinning traitlets v5.9.0: https://github.com/microsoft/azuredatastudio/pull/24444

We should probably have the requirement be traitlets > 5.10.0 if that's possible - otherwise someone could have 5.10.0 installed and it would fail for them.

Once we pin the new notebook package with the fix, traitlets 5.10.0 should work as expected right?

I was thinking we wouldn't be pinning the notebook version, but good point - I think that would be better (although same applies there - it should be > 6.5.5)


Add prefixes to kotlintest system properties

Esp. the excludeTags / includeTags should be renamed to either kotlintestExcludeTags / kotlintestIncludeTags or kotlintest.tags.exclude / kotlintest.tags.include to be able to filter out kotlintest-specific properies by name. Being able to do so is esp. useful as Gradle requires to forward system properties from the JVM running Gradle itself to the JVM running the tests, and you'd probably only want to forward properties related to kotlintest to avoid side-effects, see
https://discuss.gradle.org/t/how-should-i-be-handling-passing-system-properties-from-gradle-to-my-tests/7171/3

Now implemented on master.

This is changed in 3.0.0 RC1.
If you have the time, please give it a try. There are some breaking changes that should be aware of by reading the changelog here: https://github.com/kotlintest/kotlintest/blob/master/CHANGELOG.md


Link does not work

The link https://learn.microsoft.com/en-us/concepts/tutorial-applications-basics.md#lock-sensitive-properties-for-service-principals
does not work, gives a 404 error.

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

ID: c4fd55a1-43b5-843e-6fc5-4b12c2441346
Version Independent ID: 454259b0-d853-ae51-7724-92d6e77b9926
Content: servicePrincipalLockConfiguration resource type - Microsoft Graph v1.0
Content Source: api-reference/v1.0/resources/serviceprincipallockconfiguration.md
Product: applications
Technology: microsoft-graph
GitHub Login: @madansr7
Microsoft Alias: MSGraphDocsVteam

Thank you @cropland-bv for catching this error. I've raised a PR to fix the broken link.