update to 1.5.11

libmambapy 1.5.11
Destination channel: main
Links

https://anaconda.atlassian.net/browse/PKG-6280
https://github.com/mamba-org/mamba/compare/libmambapy-1.5.8...libmambapy-1.5.11

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_9d9gp1a85a/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:159: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:99: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_16kzbutxtd/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:104: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:161: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:103: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_cf9gn2rg1j/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:103: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:104: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:163: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_26aj5z8n_e/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:104: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:103: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:163: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_ddwk88g704/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:163: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:103: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:104: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found

Linter check found the following problems:
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
WARNING:root:Failed to render using RecipeParserDeps
ERROR conda.cli.main_run:execute(125): conda run conda-lint /tmp/abs_4b4k3d2qfi/clone failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:100: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:163: invalid_url: https://mamba.readthedocs.io/ : Not reachable: 403
clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:104: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:52: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:48: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:103: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libmambapy": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: output "libmamba": Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:9: missing_package_version: The recipe is missing a package version
===== Final Report: =====
1 Error and 17 Warnings were found


Disable openj9 build for jdk18 until it is supported

openj9 extensions doesn't yet support jdk-18, disable until ready.
Signed-off-by: Andrew Leonard<EMAIL_ADDRESS>

run tests

FYI @AdamBrousseau

Why do you say jdk18 is not supported? It should build with https://github.com/eclipse-openj9/openj9/pull/12931.

Oh for the love of.... Grr GitHub updates are arriving out of order for me.  Sorry @keithc-ca  - I'll keep an eye on this and revert if need be.

@keithc-ca openj9 extensions repo is still jdk-17: https://github.com/ibmruntimes/openj9-openjdk-jdk/blob/openj9/closed/openjdk-tag.gmk
I suspect Jason needs to update the merge script/merge...?

There's ongoing work to adopt the method handle implementation from openjdk. Pending that, the openj9 branch of that repo is still at Java 17, so in that sense, I suppose jdk18 is 'not supported'. Hopefully that will be remedied soon.

Yes essentially at this point jdk17/openj9 and jdk/openj9 are the same so there's no point running both. We should have the 17 repo up today. Once the 292 work is functional and the openj9 branch of jdk can be moved past the split point for 18, then we can turn these back on.


App: Fixups for Holochat local run

Address minor Holochat issues encountered when running locally.
Fixes issues encountered on first HoloChat local run:
python3: can't open file '/workspace/holohub/build/holochat/build_holoscan_db.py': [Errno 2] No such file or directory

NameError: name 'SimpleNamespace' is not defined

With these fixes applied the DB build stage appears to complete. However, I can't fully confirm whether the local run is successful after that stage as my GPU does not meet hardware requirements.

Thank you for the catches. I deleted my local builds and am building from scratch to test this now.

The changes work from a clean build. However, I noticed --local is hardcoded in the metadata.json, could you remove this as well?

I noticed --local is hardcoded in the metadata.json

Huh, I thought we removed that in the last PR. Thanks for that fix and for verifying!


Make int32Ptr generic

Description
Make int32Ptr generic
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/lgtm
/approve

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/lgtm


current weather image

Need to find a way to render it hidden and then change the attribute after event listener is triggered.

tried hiding in CSS and changing display attribute in event listener function but got an undefined error.

added a starting img file to default when page loads


Links in the status modal dont work

In the above, the underlying link has two slashes after the domain which make them dysfunctional, like
https://my.domain.net//wiki/spaces/NC/pages/6767676767/

Would links to all pages published even if they haven't changed be helpful?

doubt it

Replacing this with https://github.com/markdown-confluence/markdown-confluence/issues/235


Add configuration options for consumer subscribing to a queue

When a worker subscribes to a queue only two configuration options were used :block (hardcoded) and :ack (configurable using :ack option). Setting other consumer configuration options such as consumer priorities or exclusive consumers was not possible.
Creating new consumer_options configuration options block resolves that and all configured consumer options are directly passed to queue.subscribe (in more general way than pull request for exclusive consumers) while original defaults are kept as new defaults. The approach is similar to exchange_options and queue_options which are already in codebase. Old :ack configuration option becomes deprecated, but is mapped via deprecated options mapping.

Sneakers now has a new home under https://github.com/ruby-amqp/kicks. May I ask you to re-submit this PR there? Thank you 🙏


(feat/actions): Add new action 'check if the given git tag exists in the repo or not'

This PR is addressing the issue #5554.
Please keep in mind that I'm a newbie in ruby so any improvements or suggestion are welcome =)

Thanks @Antondomashnev, I added 2 more comments before it's ready. We decided that this action is useful for many fastlane users and that it will be part of the fastlane main code base instead of providing it as an external plugin.
Let us know when you had the time to update the PR 👍 🚀

@KrauseFx thanks for accepting the action, the PR is ready 🚀

@KrauseFx any news about status of this PR? Thanks

This is great, thanks 👍  Sorry for the delay, this will be in the next release 🚀


Fixes facebook apk deconstruction

Fixes ApkTool can't deconstruct apk: https://apkpure.com/facebook/com.facebook.katana
Related to #1719

This to trick the handling of like styles# etc? What stops this from just becoming an infinite list of a res type a number suffix?
Perhaps I'll accept this, but I want to double check all the resource types in FB.


[backport] Fix dev info allocation

Backport of #4491

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit fa4176a12518786a02d6b07acda97f8df664bdd1, target branch v8) succeeded!

LGTM.


[BUG] Compatibility matrix Logstash OSS

Describe
The data ingest tool documentation shows a compatibility matrix with Beats OSS, but does not indicate what happens with later versions of Logstash OSS.

Is Beats OSS 7.0.0 to 7.11.x compatible with versions earlier than 7.12.x?
For example, using the image logstash-oss-with-opensearch-output-plugin:7.16.2.

I moved this to documentation-website.
Another user ran into a related problem, https://github.com/opensearch-project/OpenSearch/issues/6219#issuecomment-1424649688

Hi @dblock , the other issue you mention I have created too but it is to analyze the error when updating Opensearch. Here what I would like to confirm is if one of our possible solutions will be supported.
What is not clear in the compatibility matrix of Opensearch is if Logstash versions higher than 7.13.x with the Opensearch output plugin are compatible with Beats OSS or not.
In the Elastic documentation I see that it specifically states which versions are supported in each product:
In the case of Beats:

In the case of Logstash

Other than creating a pr to update the documentation, how can I confirm that this compatibility is maintained in Opensearch?


Refactor review publishing tests and add log output to checkruns

Add log output support to checkruns for https://stickler-ci.com to use. Update tests to use responses and test more fulsome parts of the code.

Codecov Report

Merging #319 into master will increase coverage by 0.57%.
The diff coverage is 97.18%.

@@            Coverage Diff             @@
##           master     #319      +/-   ##
==========================================
+ Coverage   90.50%   91.07%   +0.57%
==========================================
  Files          48       48
  Lines        2895     3047     +152
==========================================
+ Hits         2620     2775     +155
+ Misses        275      272       -3

Impacted Files
Coverage Δ

lintreview/tasks.py
29.16% <0.00%> (-2.21%)
:arrow_down:

lintreview/web.py
84.90% <0.00%> (ø)

lintreview/processor.py
91.04% <71.42%> (-0.14%)
:arrow_down:

lintreview/tools/__init__.py
83.24% <83.33%> (+<0.01%)
:arrow_up:

lintreview/__init__.py
100.00% <100.00%> (ø)

lintreview/diff.py
94.73% <100.00%> (+0.95%)
:arrow_up:

lintreview/docker.py
98.30% <100.00%> (+0.01%)
:arrow_up:

lintreview/git.py
85.18% <100.00%> (ø)

lintreview/review.py
96.91% <100.00%> (+0.52%)
:arrow_up:

lintreview/tools/ansible.py
90.00% <100.00%> (-6.00%)
:arrow_down:

... and 30 more

Continue to review full report at Codecov.

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


fix: increase e2e test suite timeout

Since we start to add more and more e2e tests, the 60m suite timeout is too short. Increase the timeout to 3h.

already addressed by #506


Failed to hibernate shoot clusters in creation phase

How to categorize this issue?

/area control-plane
/kind bug
/priority 3
What happened:
The hibernation of a shoot cluster failed because of the following reason:
"time=\"2021-08-03T05:58:49Z\" level=info msg=\"waiting until there are no running Pods in the shoot cluster... there is still at least one running Pod in the shoot cluster: kube-system/apiserver-proxy-kkrlb\" operation=reconcile shoot=garden-xxxxx\n"

Pods were still running in the cluster but:
 g k -n kube-system get po
NAME                          READY   STATUS    RESTARTS   AGE
apiserver-proxy-kkrlb         2/2     Running   0          116m
calico-node-bfjtf             1/1     Running   0          113m
csi-driver-node-bzkw6         3/3     Running   0          116m
kube-proxy-rvh8j              2/2     Running   0          116m
node-exporter-qtbsp           1/1     Running   0          116m
node-problem-detector-gchw6   1/1     Running   0          116m
g k -n kube-system get no
No resources found

--> Problem: KCM is already scaled to 0 and cannot clean up remaining pods.
What you expected to happen:
Hibernation operation to be successful.
How to reproduce it (as minimally and precisely as possible):

Create cluster and let it fail during creation
Trigger hibernation

Anything else we need to know?:
Shoot creation has never completed and when the shoot is hibernated during creation, KCM gets a replicas: 0. See this comment
Environment:

Gardener version: v1.28.1

/assign


sendToActiveChats('sendPhoto') only works once per call

Required Information

Operating system: Linux
PHP version: 7.1.22 (64bit)
PHP Telegram Bot version: 0.54.1
Using MySQL database: yes
Self-signed certificate: no

Expected behaviour
Photo should be sent to all active chats.
Actual behaviour
Photo seems to be sent to the first chat only.
This is the response I'm getting for the rest of the chats:
object(Longman\TelegramBot\Entities\ServerResponse)#192 (5) {
    ["ok"]=>
    bool(false)
    ["error_code"]=>
    int(400)
    ["description"]=>
    string(45) "Bad Request: there is no photo in the request"

Steps to reproduce
Request::sendToActiveChats(
    'sendPhoto',
    ['photo' => Longman\TelegramBot\Request::encodeFile($row['path'])],
    [true, true, true, null, null]
);

Extra details

I'd guess sendToActiveChats doesn't reset the stream to offset 0 (but I haven't looked into it yet).
This might also apply when sendToActiveChats is used with sendDocument and similar methods.

@0xEAB Thanks for reporting, was able find the cause.
You're on the right track. Guzzle internally converts resources into streams, making the existing one invalid after being posted once.
As a temporary fix, you can use this:
['photo' => \GuzzleHttp\Psr7\stream_for(Longman\TelegramBot\Request::encodeFile($row['path']))],

I'm not sure yet if changing this directly in the encodeFile method will break anything, as it will then return a Stream instead of just a simple resource. This could potentially break existing user code, if they rely on the returned resource :confused:
@php-telegram-bot/developers What is your view on this?

@0xEAB If you update to version 0.56.0 you can now simply pass the path as a string (which will internally automatically use a stream):
Request::sendToActiveChats(
    'sendPhoto',
    ['photo' => $row['path']],
    [true, true, true, null, null]
);


FrameBuffer may not always dispose texture

Hi,
Has discussed here, it is not possible to dispose framebuffer and use the texture later since dispose method dispose the texture as well.
It's not possible to change the colorTexture neither which is a big limitation for some use-cases :

use the same FBO to render multiple textures.
texture swap for multipass shader algorithm.

FBO and texture attached to it may not have the same lifecycle.
For now my "ugly" workaround is to extends FrameBuffer in that way :
public class RenderToTexture extends FrameBuffer
{
  ...
	public Texture swapColorTexture()
	{
		Texture result = colorTexture;
		setupTexture();

		bind();
		Gdx.gl20.glFramebufferTexture2D(GL20.GL_FRAMEBUFFER, GL20.GL_COLOR_ATTACHMENT0, GL20.GL_TEXTURE_2D,
				colorTexture.getTextureObjectHandle(), 0);
		unbind();

		return result;
	}

}

But it's not a perfect solution for many reasons :

This generate one texture more which is never used (just used to dispose it).
FrameBufferCubeMap needs to be extended in the same way.
this not cover all the use cases.

I could make a pull request with modifications on GLFrameBuffer class but i want to discuss about the solution before.
IMO, the color buffer may have to be controlled by user code.
The idea would be :

default behavior still unchanged, a color texture is always created, attached and disposed.
a new method to create and attach a new texture.
a new method to attach a texture created before.
a new method to detach the current texture (to not be automatically disposed when FBO is disposed).
when the "manual mode" is used, user code is responsible to dispose detached textures.

What do you think ?

Thanks! Should be fixed now, you can now override the disposeColorTexture method and take ownership from that point on. The general rule of thumb is: if you create it, you dispose it. I don't think that encouraging changing (attaching/detaching) ownership is a good idea.
It would be possible to accept a Texture in the constructor and thus move ownership completely out of the FrameBuffer. But that would get messy when the texture isn't managed (currently the texture is recreated on context loss).

Thanks for the very quick commit (less than 1 hour :-))
That's solve the first use case which is probably the most important.
For the others use cases, I understand your point, maybe frame buffer have to be implemented specifically for those.

I think a public Texture disposeAndTakeColorTexture() method would be appreciated, if that seems reasonable. Otherwise I think this is a code fragment most users are going to want:
class YieldingFrameBuffer extends FrameBuffer{// if you call disposeAndTakeColorTexture, colorBuffer is prevented from being disposed and given to you
	private boolean yielding = false;
	public YieldingFrameBuffer(Pixmap.Format format, int width, int height, boolean hasDepth){
		super(format, width, height, hasDepth);
	}
	@Override protected void disposeColorTexture(Texture t){
		if(!yielding) t.dispose();
	}
	public Texture disposeAndTakeColorTexture(){
		Texture r = getColorBufferTexture();
		yielding = true;
		dispose();
		return r;
	}
}


gphotos: back off, retry on download quota errors?

I just got this error from the gphotos importer:
2018/04/17 12:30:04 gphotos importer account, sha1-3241e8cbe169df2805cbaa456b2b7d57c47d8c38 error: gphotos importer: error getting permanode for photo "1hIij9bwxAHk8eD5QVIHR9_O3uVoY57fGKg": googleapi: got HTTP response code 403 with body: {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "downloadQuotaExceeded",
    "message": "The download quota for this file has been exceeded."
   }
  ],
  "code": 403,
  "message": "The download quota for this file has been exceeded."
 }
}

The error message makes it sound like it's about the download quota on a single file, but I suspect it's about my overall download rate of all photos.
Assuming the latter, we should we detect that and slow down & retry.
/cc @mpl

Also:
2018/04/18 12:48:48 gphotos importer account, sha1-3241e8cbe169df2805cbaa456b2b7d57c47d8c38 error: gphotos importer: error getting permanode for photo "1GGN3OgnTeJGwSnVRiCSCqpuueWSCSZ2tDQ": stream erro

and
2018/04/18 13:27:18 gphotos importer account, sha1-3241e8cbe169df2805cbaa456b2b7d57c47d8c38 error: gphotos importer: error getting permanode for photo "1rIbVcI0xHW3hMxkoq3uiNhl6xEGAFk7-9w": googleapi: got HTTP response code 503 with body: Service Unavailable

btw, it might be worth trying to re-review again the code that @tgulacsi had written in the first iteration. I think he had tried to address some of these issues, or at least he had some insight into what all the causes of errors were.

Another:
2018/04/18 23:01:34 gphotos importer: error getting permanode for photo "14zXnwsy9-rBg82UWlR4Ars1HW2AXF6P1jA": googleapi: got HTTP response code 500 with body: {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "backendError",
    "message": "Backend Error"
   }
  ],
  "code": 500,
  "message": "Backend Error"
 }
}


Input Number (helper) entities give an error

Using a helper number entity in a call to the service gives an "Unknown Error".
Other entities work fine. Have tried with a helper number (and tried using a Jinja filter to convert to string). Text helpers work fine.
To Reproduce
Set up a number helper in Home Assistant
Call the service with the below data
service: open_epaper_link.lines4
data:
  mac: <mac>
  line1: "{{states('input_text.br2_guest_name') }}"
  line2: "{{states('input_number.tag_refresher') | string }}"
  format1: mwwr
  format2: mwwb

I have a work around. Append a string (must be alpha, not numeric) to the end of the number, inside the template.
Example:
'''
line2: {{ states('input_number.dry_rooms_min_temp') | string + 'C'  }}
'''
An empty string like the below does not work. It also does not work if you put a space inside the final quotes.
'''
line2:  {{ states('input_number.dry_rooms_min_temp') | string + ''  }}
'''

Pull request submitted to fix this.
And I've just realised that I'll have to re-do the README again once it's merged.


Allow passing a function name to the _fields() methods - for name_suffix(), states_list(), etc.

We can improve flexibility of our name_fields(), address_fields() etc. function by allowing a form author to pass a lambda in as a parameter to customize the various lists that we use.
E.g., people sometimes want to customize the list of suffixes.

There is another way to customize functions like name_suffix() already--using a language update function. But that may not provide the right level of customization. Worth thinking through.

Can you describe more about what you're thinking here? What would be the purpose in passing a lambda over just a list, or the parameter to use instead?

Mainly because name_suffix() is already a function and because the normal way to override name_suffix() is to use a language update function. But it's not critical, those other patterns would also be fine.
Another option would be a custom list like al_name_suffixes that can be overridden in the YAML file. Just need to figure out best option and go for it.

We had a SME suggest that some suffixes might be "Junior" or "Senior" rather than just the abbreviations. It looks like this issue was exploring ways to adjust the list of suffixes. Is this something we can revisit? Is the functionality handled elsewhere? Thanks!

It sounds like what the SME is suggesting is that we need both the long versions and the short versions together in one list. Am I misinterpreting that?

@plocket I think you're right. Ideally, the list of suffixes could be adjusted on a organization-wide or even program-by-program level. To address this specific concern, adding the full words "Junior" and "Senior" while keeping Jr, Sr, etc., would help. Thanks for asking.


Please add explanation in doc as to why INCLUDE+ was rejected

Please add explanation in doc as to why INCLUDE+ was rejected.
Was it even rejected?
I worry using this if there are drawbacks or open discussions regarding this. It seems so trivial, but I am a newbie to docker.

https://github.com/moby/moby/issues/735


PackageId:CPython39.Exe.x64;PackageAction:DownloadPackage;ReturnCode:0x80072ee2;

This issue has been moved from a ticket on Developer Community.

[regression] [worked-in:17.5.5]
it gives the error message when vs 2022 update to latest version.
===DO NOT EDIT BELOW THIS LINE===
PackageId:CPython39.Exe.x64; PackageAction:DownloadPackage; ReturnCode:0x80072ee2;

Original Comments
Feedback Bot on 5/3/2023, 11:03 PM:
(private comment, text removed)

Original Solutions
(no solutions)

It seems the problem occurs when the CPython installer fails. This could be due to network timeouts, corporate firewall policy, VPN configuration, anti-virus, or other problems. See if a retry helps, and if not, see if you can download the Python runtime directly from https://python.org/ and install it manually.
If that doesn't solve your issue, we could use more detailed logs to see what's really going on. Can you please collect more logs by running http://aka.ms/vscollect.exe and uploading %temp%\vslogs.zip and reopen the ticket if it persists? Thank you!😊


Security Vulnerability Disclosure

Hi,
I have found a high-risk security vulnerability which may result in remote code injection in this project. Who can I contact to responsibly disclose it?
Thanks,
Indiana Moreau

The project is dead and the service is discontinued by google so I wouldn't expect anybody to fix anything.

Closing as I've received no answer.


Update compile

@cwallsfdc I missed this. Also, active development is in https://github.com/wadewegner/salesforce-dx-buildpack/tree/v4-dev.


Build requires -Name option for Import-Module

For some reason I can not Import-Module AWSPowerShell, I must
Import-Module -Name "C:\Program Files (x86)\AWS Tools\PowerShell\AWSPowerShell\AWSPowerShell.dll"
I've also tried to remove the -noprofile from the build script and that didn't work either. Is this known, or would you happen to know why? When I run the same script from my local powershell, using -noprofile -file C:\foo.ps1 the script works as expected. When running the script via the CTRL+B from within sublime I get the following output:
Import-Module : The specified module 'AWSPowerShell' was not loaded because no
valid module file was found in any module directory.
Edit: I tried removing the -noprofile again and think that resolved it. I'm not totally sure what's going on but it appeared that my $env:psmodulepath was wrong.. again I think this was something on my end and this can likely be closed

Interesting. I didn't know about Ctrl+B at all.
@guillermooo , should we move all related effort to https://github.com/guillermooo/PowerShellConsole ?

Closing old issues, let's open a new one if it's still a problem.


Allow explicit optional labels

Using newest version of the Dart package (2.0.1) explicit optional fields are disallowed, even though they were re-introduced in protobuf 3.15 https://github.com/protocolbuffers/protobuf/releases/tag/v3.15.0
Explicit 'optional' labels are disallowed in the Proto3 syntax. To define 'optional' fields in Proto3, simply remove the 'optional' label, as fields are 'optional' by default.

I noticed this issue: https://github.com/google/protobuf.dart/issues/523
I am not sure if it covers it but if so, just close this as duplicate and I will comment and upvote 523


More accurate naming of steps

Pre-merge checklist
Performance:

[ ] Compare zig benchmark on linux before and after this pr.# benchmark results before
...

# benchmark results after
...

OR

[x] I am very sure this PR could not affect performance.

In @matklad 's comment I noticed that some of the seemingly duplicate steps were not named very accurately. This renames them to be clearer about the debug and non-debug Docker image steps and also about the native vs AMD+ARM steps.

bors r+


Updated  Mobile Ads SDK

I have updated  Mobile Ads SDK to newer version

iOS from v7.69.0 to v8.6.0
Android from v19.4.0 to v20.2.0

@spazfeed would love to see this merged.


Hot reloading not working

Bug Report
Describe the bug
Currently, with the latest version of Docz, hot reloading is not working at all.
To Reproduce
Create a new Docz project, load it up, make a file change and observe that the browser doesn't refresh with updated content.
Expected behavior
When one makes file changes, hot reloading causes the browser to refresh with new content.
Environment

docz version: 2.3.1
OS: Ubuntu
Node/npm version: node 14.15.3, npm 6.14.9

I believe I'm having the same issue with macOS, same Docz version, and 14.18.3.  From the browser console it appears that changes are detected, but the components aren't updating visually.  Sample console output:
[HMR] connected                                                           client.js:241
[HMR] bundle rebuilding                                                   client.js:250
[HMR] bundle rebuilt in 428ms                                             process-update.js:51
[HMR] Checking for updates on the server...                               process-update.js:125
[HMR] Updated modules:                                                    process-update.js:127
[HMR]  - ../src/component-docs/OpenApiForm.mdx                            process-update.js:127
[HMR]  - ./.cache/_this_is_virtual_fs_path_/$virtual/sync-requires.js     process-update.js:132
[HMR] App is up to date.


Add option to restore all projects in solution

In reference to : https://github.com/OmniSharp/omnisharp-vscode/issues/240
I propose the following change:
.NET: Restore All Projects : Restore all the projects in the workspace.
.NET Restore Project: Shows a command palette menu to select one of the projects to be restored.
How does that sound ?
Also we have a 'There are unresolved dependencies..' warning that pops up for every project that has an unresolved dependency. How do we change that? It is irritating especially when there are a number of projects in the solution. Should we modify that to come up when there is atleast one project that has an unresolved dependency
There are unresolved dependencies in the solution. Please execute the restore command to continue.
and then when the user clicks restore we perform the 'Restore all projects' as stated above ?

Please share your thoughts @rchande @TheRealPiotrP @DustinCampbell

@akshita31 I'm on board for having two commands for restoring projects. I don't have strong opinions about the names of those commands. I completely agree with your solution for the warning. It's annoying because we show one notification per project. The clear solution (as you said) is to only show one notification that offers to restore all projects. I'm having trouble imagining scenarios where users would want to only restore a subset of projects in response to the warning.

FYI that there's also this: https://github.com/OmniSharp/omnisharp-vscode/issues/240


Add GCS blob name and bucket name copy actions

fixes #1671
POC - still needs a little cleanup.
See the issues for rationale behind this.

blob name: an absolute path to the blob; e.g. folder1/folder2/myblob.zip
What do you think of this approach? I was also considering having a little bottom notification panel popup on clicking on one of the copy actions to acknowledge that the text was copied (and show its contents).

Updated: now in addition to the right-click menu shown in the PR description, there is a right click menu on the bucket listing panel for copying the bucket name (since this is a perhaps more natural place to find this):


Adopt Base's annotated types/functions as API

This opens the door to shuffling parts currently implemented in Base into this stdlib without breaking any public APIs.
To try to help avoid people using Base.Annot... anyway, I've exported these bindings. I think this is reasonable given unlike in Base this library needs to be deliberately imported.

This change has been discussed with other maintainers on Slack (the API shift, but not the exporting), so I'm inclined to merge this soon if I can figure out how to make doctests happy.

This is held up by difficulty figuring out the Documenter side of things.

It's hard to see how I can make this work before https://github.com/JuliaDocs/Documenter.jl/issues/1781 is resolved :grimacing:.
Perhaps @mortenpi might have an idea?

In light of https://github.com/JuliaLang/julia/pull/55845 and the change Kristoffer's just pushed it seems like neither of us can easily make Documenter do what we want here, so let's just leave the documentation of the Base-defined types there with an appropriate notice.
I think all that needs to be done now is the @ref StyledStrings.Annotated... changes to be reverted back to @ref Base.Annotated... in this PR (it currently produces 404 links), and then we can merge it and stop being a 1.11 blocker.


[pipelines] WIP: Iris Pipeline Example

/test rhoai-e2e pipelines pipeline_iris keep

/test rhoai-e2e pipelines pipeline_iris

iris pipeline now working with DSPv2

/test rhoai-e2e pipelines

hello-world default pipeline also passing now

/test rhoai-e2e pipelines pipeline_pi

@drewrip , please don't forget to check the linter, you have a yes to turn into true

/test rhoai-e2e pipelines pipeline_pi

/test rhoai-e2e pipelines pipeline_pi

/test rhoai-e2e pipelines pipeline_pi

pi pipeline is passing

/test rhoai-light pipelines light pipeline_hash

/test rhoai-light pipelines light pipeline_hash

/test rhoai-light pipelines light pipeline_hash

/test rhoai-light pipelines light pipeline_hash

/test rhoai-light pipelines light pipeline_hash

/test rhoai-light pipelines light pipeline_hash

hash pipeline passed

/test rhoai-light pipelines light pipeline_timed_multistage

/test rhoai-light pipelines light pipeline_timed_multistage

timed multi stage pipeline passed, all pipelines are updated and passing!


Update Ledger Notes

Updates on

Side loading apps
Ledger Live Integration
Ledger Dapps

steps on connecting docker image with live devices.


replaced parse_raw_as with parse_obj_as, to work with pydantic v2

this pull request is a work in progress, please bear with me

I created #500, so if we don't want to proceed with this we can close it now.

I agree,  we can leave this in maintenance mode until there's cloud-sync support, or until we start implementing schemas+validations.


Fixing tests to work with python 3. Adding the colors.py file which w…

…as missing, but used by run.py.

Coverage remained the same at 96.978% when pulling 7c3f9bc59cec3eff0a628e9fea89ad4fa8841dae on gwendolyngoetz:fix-tests-for-v3 into f8ad756a7fe2c632fc044b9d56172445fce88533 on datascopeanalytics:master.

Thanks for highlighting this issue. It looks like this exact change is already in the codebase, so I'm going to close this MR. Thanks for the commit!


Create describe function for encoding an decoding

Like ISO8583 add the describe() function to create a human-readable output of the encoding inputs and outputs.

I see how pin and pan fields (that we calculate with the control char, length, padding, etc.) can be useful when you debug things e.g.:
PIN block:       441234AAAAAAAAAA911B9B36BC7CE94E
PAN block:<PHONE_NUMBER>4321098700000000000000

but in the #6 , we are not showing it. We are showing only two new data points into addition to what user already has: formatted name and padding.
What is the purpose of such output? I used examples from here to check if I'm doing it right. So, if our goal it to help people debug things, then I see two options for the implementation here:
Option 1 - use io.Writer as a debug output
By default, DebugOutput should be io.Discard, it can be set via constructor or by setting the field on the struct like this:
format := &formats.ISO0{
        DebugOutput: os.Stdout,
}

internally it can write any information that can be used for debugging - which can really be useful
My concern here is the security. It would be pretty bad if someone somehow will output real pins/pans somewhere without the intention to do so.
Option 2 - create methods that will show debug information so we can use them in Describe
It's similar to what we have in the #6 but we should agree on what exactly we want to see and how useful it is
For example, for iso4 we have many intermediate calculations, pin field, encrypted pin field, pan field, xor'ed encrypted pin and pan, encrypted pan (result). Which of them do we really want to show?
Here are two suboptions:
1
we can keep methods private, and move Describe into formats package so it will have access to them
2
agree on the Describable interface and use it instead of adding interface for the format (ISO) (because: define interface where you use it, not where you implement it).

@adamdecaf what do you think about Option 1? Do you think it's ok to allow setting DebugOutput?

I like Option 1 and the default io.Writer can be nil so that we only write when .DebitWriter != nil. Writing all of that unused debug information isn't great from a privacy/PCI point of view as those strings will reside in memory for a period of time.

option 1 is good for me too

Let's think about the API for this. I have following suggestions
Option 1 - separate method + without exporting the field
type ISO0 struct {
    Filler      string
    debugOutput io.Writer
}

/// usage
pinblock := &formats.NewISO0()
pinblock.SetDebugWriter(os.Stdout)

as I have a security concern, the first option seems to be a better choice. When the engineer explicitly calls a method like SetDebugWriter(), it's clear that they're enabling debug logging, which should make them more aware of what they're doing. Also, debugOutput is unexported, which means it cannot be directly accessed outside the package.
Option 2 - just set the field
type ISO0 struct {
    Filler      string
    DebugOutput io.Writer
}

// usage
pinblock := &formats.NewISO0()
pinblock.DebugOutput = os.Stdout

it's more straightforward, but I would prefer the Option 1
@mfdeveloper508 @adamdecaf what is your opinion?

Go usually avoids setters/getters. If someone calls pinblock.DebugOutput = os.Stdout they know what they are doing. To me that's the same as calling .SetDebugOutput(..).
Option 2 is more the Go standard way of writing this.


data_generator_task() in training.py does not honor model.evaluate_generator() val_samples argument properly

keras 1.2.2  using tensorflow-gpu 0.12.1.
When using the model.evaluate_generator(), val_samples is not honored by the threads queuing the generator even when nb_worker=1 and max_q_size=1.
For example, suppose my generator returns 32 samples per batch.  Calling model.evaluate_generator(myGenerator, 64,  max_q_size=1, nb_worker=1) should result in the next(myGenerator) being called 2 times.  However, it is called at least 3 times by data_generator_task() in training.py.  This is problematic for generators that loop through finite datasets.

Taking @fchollet for visibility per previous github conversations.


Copying and pasting large table into page results in table going off the page.

Describe the bug
Copying and pasting a large table from somewhere else into bookstack results in the table going off the page horizontally, across the edit, revision, etc buttons, and onwards until it reaches the edge of the table.
Steps To Reproduce
Steps to reproduce the behavior:

Create a large table in Word, Excel, Powerpoint, or even on another website.
Copy the entire table to clipboard
Edit a page
Paste the table into the editor
Save the page and view the results.

Expected behavior
I would expect the page to expand to fit the table.
Another option is to allow the user to set the page size for that specific page. Rather than making the page adjust itself, allow the user to increase the page size from A4, to A3 for example. Could also allow landscape orientations.
Screenshots
Screenshot in comments below.
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): 0.29.3
PHP Version: 7.3.17 (From Fedora 31 official repositories)
Hosting Method (Nginx/Apache/Docker): Apache

Additional context
None.

Ok I have finally had some time to get an image of what this looks like (apologies, university exams are royally painful), and so here it is:

It's worth noting that this can happen even with tables that you make yourself. If you put pictures or other wide items in the cells of the table, then it can easily take the table off the edge of the content section. But the only real alternative I suppose would be to make elements that are too wide horizontally scrollable, which would be tricky I imagine
I suppose the biggest question I have is why is the content section so relatively narrow even in on wide screens?

Maybe allowing to place control panel at left side (or even at bottom) could address this issue with not so much of effort, what do you think?


Allow emoji aliases to be created from emojipacks

Reopening #52 with refreshed patch. Might conflict with #105, but I'm happy to rebase against it again.
Aliases can be defined using a list of names under the aliases key of an
emoji definition. See the updated README.md for more details.
New errors added to image-checker.py:

Error: Emoji named ___ already defined elsewhere.
For when the emoji being tested has been defined as an emoji or alias
already.
Error: Alias named ___ already defined elsewhere.
For when the alias being tested has been defined as an emoji or alias
already.
Warning: ___ should be an alias for ___.
For when two emoji definitions share the same URL.

Existing emojipacks have been aliased and de-duplicated as appropriate.

This contains new code that you just squashed right? Just making sure!

Ah yes, that's just reusing the previous timestamp from #52. I should probably bump it to today.

Rebased and updated timestamp.

Cool looks good.


Objective-C for Swift

How can I implement the api for Swift??? i did not found nothing about it!.

++++ need swift, i can pay for it)


Initial creation of the standalone Project Reunion Installer

See issue #443.
This PR introduces the starting project for a standalone Project Reunion installer. It produces an executable with embedded packages and when run attempts to install and provision those packages. Provisioning is best-effort since users may not be admin and that is not an actionable error by developers and does not prevent the packages from being deployed for the current user.
It builds using the 0.1 released framework packages, which are not included in this PR, and provides an override mechanism for providing packages at build time (see project_reuion_definitions.h for details).
This is intended to be consumed by build pipelines to produce installers for just-built packages.
More changes are expected based on feedback, and tests are planned for a later PR to build and deploy test packages to verify the installer.

Can we avoid committing in the .msix files?  Git doesn't like binaries.


Re-implement Twitter Service

We removed the Twitter service temporarily in #85 to fix a bug where the bot crashed on deployment.
We need this feature added back, but obviously do not want it to crash the bot.

@LamboCreeper could I get a bit more detail on this one please?

@LamboCreeper could I get a bit more detail on this one please?

This feature is currently on hold until Twitter Streaming API becomes more easily accessible via a Node SDK again. Sorry, should have made more clear.

No longer required due to the use of Webhooks for this functionality.


Correction for raw affiliation EESP, Lausanne<EMAIL_ADDRESS>

Correction needed for raw affiliation EESP, Lausanne<EMAIL_ADDRESS>raw_affiliation_name: EESP, Lausanne<EMAIL_ADDRESS>new_rors: 0278ff426
previous_rors:
works_examples: W2469856183
contact: a8f4643d54690cb5046bb2b08f86451a:ef41f6b1d885f622137dba1676259410d1 @ hetsl.ch

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Don't work. Please fix your install script.

Please go to Stack Overflow for help and support. http://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or feature request.
The form below must be filled out.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g. fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
System Information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow)?:
OS Platform and Distribution (i.e. Linux Ubuntu 16.0):
TensorFlow installed from (source or binary)?:
TensorFlow version (use command below):
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU Model and Memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script https://github.com/tensorflow/tensorflow/blob/master/tools/
You can collect the TensorFlow version with
python -c "import tensorflow as tf; print (tf.GIT_VERSION, tf.VERSION)"

Describe the problem clearly
Source Code / Logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full-traceback. Large logs and files should be attached. Try to reproducible test-case code the bare-minimum necessary to generate the problem

Please fix your install script. Make it work.


Terminal as tab

Hi
It would be great to have ability to open terminal as code editing tab. Or to be able to open several terminals (actually only one open terminal it is rare case ;) )

Multiple terminals is planned for the June release https://github.com/Microsoft/vscode/issues/6458
I don't see terminals being made as actual tabs due to the way that vscode is, full screening or making panels more convenient to expand is definitely an option in the future though.


Added random alphanumeric sequence to the temp FDF file name

Using just the timestamp to generate a temporary file name on a multi-threaded environment can be risky. This MR is just adding a random alphanumeric sequence in order to improve the "uniqueness" of the file name and to avoid threads clashing when generating FDF files.

Hi guys, any feedback on this, please? :)

@johntayl , could you please release this change to NPM?
BTW. issue #2 referenced this change coincidentally a year ago or @whitef0x0 is a time traveller...


[Feature] Enhance the footer UI

Description
in your website the footer is missing i want to add a footer to your website to make more professional your website

Screenshots
i will be make footer like this in your website:

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a KWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Status of your PR pls @biswajit-sarkar-007

@Rakesh9100 , hey now I'm busy with my exam preparation when i have time  I will sure work on this  within 25 dec

@Rakesh9100  hey sorry bro now days I'm so much busy with my college exam and partical , so I would not able to doing this !

@Rakesh9100  I would like to take on this issue and contribute to its resolution.

Go ahead @pragna7


Question: how to scale up vcf2fhir

Hi I just had a quick question - I'm trying to run vcf2fhir on large vcfs, and the process is taking many hours - is there a way to scale up? I'm working on GCP so I can use whatever resources I need.
Thanks,
Camille

Camille, have you tried using a bgzipped VCF with a tabix index? Also, are you converting the entire file, and have you considered just converting key regions of interest?

I would love to convert just key regions on interest - is there a streamlined process for picking those regions out and making a smaller VCF?
Thanks,
Camille

Hi Camille,
We provide some additional documentation here (https://vcf2fhir.readthedocs.io/en/latest/). You won't be making a smaller VCF, but rather, you'll selectively convert specified regions from the larger VCF.
You can limit the conversion region using a conversion region dictionary (e.g. conv_region_dict={"Chromosome": ["X", "X", "M"],"Start": [50000, 55000, 50000],"End": [52000, 60600, 60025]}) or a conversion region BED file (e.g. conv_region_filename="WGS_b37_convert_everything.bed").
Values for Chromosome must align with values in VCF #CHROM field. Ranges must be 0-based and based on GRCh37 or GRCh38 reference sequences.
You'll find some sample BED files here https://github.com/elimuinformatics/vcf2fhir/tree/master/vcf2fhir/test
Either way, for very large files, I suspect the process will be more efficient with zipped and indexed VCF files.


fix(csr): add support virtual interrupt for hvictl csr injection

Format check failed.
Please run pip install --user clang-format==18.1.4 and make format locally.


Your code does not return time

You can easily measure time by using the function time.time()
https://www.tutorialspoint.com/python/time_time.htm

the code runs time in the unit test section and it is available in my repo
I'll merge it to the main repo soon

can't we use %%timeit and %timeit??

@yasmensarhan27 yes you can if you want to edit the code.

I'll merge unit test using colab, quantum lab and Jupyter notebook using the original code
Moreover, I'll add a new unit test file containing time it
Once I finish I'll request to merge them

Sounds perfect!

Great


Stop copying truss server code over for "trussless"

:rocket: What
https://basetenlabs.slack.com/archives/C037X7HFAE4/p1728672357619419?thread_ts=1728574438.184139&cid=C037X7HFAE4

:computer: How

:microscope: Testing
Passed integration test
https://github.com/basetenlabs/truss/actions/runs/11301752384

lgtm.
Might also be worth trying out dhruv's config before merging

@dsingal0 can you try context image "v0.9.44-rc" to verify it can resolve the issue?

@tianshuc0731 I also think that we might need to merge https://github.com/basetenlabs/truss/pull/1187 to properly test dhruv's changes. it lgtm

@tianshuc0731 I also think that we might need to merge #1187 to properly test dhruv's changes. it lgtm

Merged the change, @dsingal0  please test this new image "v0.9.44-rc2"


NVM status in status bar

Hey @vlad-shatskyi
Would you please describe the feature details? I like to develop it.

@sorousht It's about a button in the status bar showing current node version, similar to git branch we have now. But I'd like to do it myself first because there is no status bar API at the moment.

@vlad-shatskyi What feature do you suggest me to start with?

@sorousht I can't find anything small. Would you be willing to work on a bug, like this one? https://github.com/railsware/upterm/issues/1163 ?


[track2] should we publish tsdoc-metadata.json

The conversation that started it all:
https://github.com/Azure/azure-sdk-for-js/pull/8654/#discussion_r418762086
It looks like tsdoc-metadata.json allows api-extractor to know what dialect of tsdoc (if any) your package speaks. This can be useful for example when you're running api-extractor on package A, which in turn depends on package B that has types. If api-extractor finds tsdoc-metadata.json in package B, it should be able to respect the TSDoc comments...at least that's how I understand it:
https://github.com/microsoft/tsdoc/issues/7
Currently many of our packages don't publish this file, since they include just the rolled-up types in the package.json files field. This package is to investigate (and potentially track efforts) whether we should be publishing this file.

cc @jeremymeng, @xirzec

Ok it looks like that the API extractor generating tsdoc-metadata.json is now undesirable as explained here: https://github.com/microsoft/rushstack/pull/1628#issuecomment-553665782 (the origin of the design is here: https://github.com/microsoft/rushstack/issues/959). Furthermore, in the same issue you are linking to, the idea of using a human-authored tsdoc.json was born and which I already introduced using in our repo across our packages to support the @hidden tag and the API extractor tool is already working on support for it here: https://github.com/microsoft/rushstack/pull/1950.
Unfortunately, we are stuck with an older version of the api extractor for now for reasons I do not remember on top of my head so I do not think we will have access to that support anytime soon. Based on this I am gonna go ahead and close this issue and I recommend to take no action at this time.

Ok it looks like that the API extractor generating tsdoc-metadata.json is now undesirable as explained here: https://github.com/microsoft/rushstack/pull/1628#issuecomment-553665782 (the origin of the design is here: https://github.com/microsoft/rushstack/issues/959). Furthermore, in the same issue you are linking to, the idea of using a human-authored tsdoc.json was born and which I already introduced using in our repo across our packages to support the @hidden tag and the API extractor tool is already working on support for it here: https://github.com/microsoft/rushstack/pull/1950.
Unfortunately, we are stuck with an older version of the api extractor for now for reasons I do not remember on top of my head so I do not think we will have access to that support anytime soon. Based on this I am gonna go ahead and close this issue and I recommend to take no action at this time.