Update 17.0.4

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:138: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:224: missing_tests: output "libllvm-c17": No tests were found.
ERROR: clone/recipe/meta.yaml:227: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:227: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:257: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
ERROR: clone/recipe/meta.yaml:137: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:226: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:226: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:256: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
WARNING: clone/recipe/meta.yaml:49: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:136: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:193: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:193: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:223: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:99: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:111: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:159: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:159: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:185: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
WARNING: clone/recipe/meta.yaml:101: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:114: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:164: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:164: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:190: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:102: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:116: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:167: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:167: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:193: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:92: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:106: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:157: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:157: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:181: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:97: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:111: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:174: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:174: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:198: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:97: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:111: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:174: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:174: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:198: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
ERROR: clone/recipe/meta.yaml:74: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:92: missing_imports_or_run_test_py: output "llvmdev": Python packages require imports or a python test file in tests.
WARNING: clone/recipe/meta.yaml:112: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:116: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:126: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:126: missing_imports_or_run_test_py: output "libllvm17": Python packages require imports or a python test file in tests.
ERROR: clone/recipe/meta.yaml:140: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:169: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:179: missing_imports_or_run_test_py: output "llvm-tools": Python packages require imports or a python test file in tests.
ERROR: clone/recipe/meta.yaml:183: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:183: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:194: remove_python_pinning: On arch specific packages, python deps should not be constrained.
WARNING: clone/recipe/meta.yaml:211: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
ERROR: clone/recipe/meta.yaml:73: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:91: missing_imports_or_run_test_py: output "llvmdev": Python packages require imports or a python test file in tests.
WARNING: clone/recipe/meta.yaml:111: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:115: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:125: missing_imports_or_run_test_py: output "libllvm17": Python packages require imports or a python test file in tests.
ERROR: clone/recipe/meta.yaml:125: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:139: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:168: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: clone/recipe/meta.yaml:178: missing_imports_or_run_test_py: output "llvm-tools": Python packages require imports or a python test file in tests.
ERROR: clone/recipe/meta.yaml:182: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:182: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:193: remove_python_pinning: On arch specific packages, python deps should not be constrained.
WARNING: clone/recipe/meta.yaml:210: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:99: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:113: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:167: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:167: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:195: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:92: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:106: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:157: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:157: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:185: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:157: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:157: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:185: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
WARNING: clone/recipe/meta.yaml:93: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:107: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:158: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:158: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:186: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:94: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:108: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:159: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:159: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:187: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
ERROR: clone/recipe/meta.yaml:109: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:160: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:160: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:188: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
ERROR: clone/recipe/meta.yaml:109: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:160: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:160: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:188: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:108: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:159: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:159: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:187: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
ERROR: clone/recipe/meta.yaml:106: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:157: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:157: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:185: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:91: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:105: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:156: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:156: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:184: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:93: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:107: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:158: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:158: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:186: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:93: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:107: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:160: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:160: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:188: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "libllvm17": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "llvm": Output is missing script.
INFO: clone/recipe/meta.yaml:0: output_missing_script: output "lit": Output is missing script.
WARNING: clone/recipe/meta.yaml:98: host_section_needs_exact_pinnings: output "libllvm17": Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:112: missing_tests: output "libllvm17": No tests were found.
ERROR: clone/recipe/meta.yaml:168: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:168: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
WARNING: clone/recipe/meta.yaml:196: missing_description: The recipe is missing a description
Errors were found

@danpetry Can this PR be closed as llvmdev 17.0.6 is available on defaults?

sure


add refreezing calculation to Crevasse

This will move the refreezing (or blueband) calculation into Crevasse and out of ThermalModel
Note: This will require ThermalModel pass required values to IceBlock so they can be accessed by Crevasse for the refreezing calculation

[ ] Write refreezing method in Crevasse
[x] Determine what values need to be extracted from ThermalModel for the refreezing calc.
[ ] store and track refreezing for each crevasse (refreezing/blueband grows through time as refreezing continues (but it can melt as well).

#71 virtualblue/refreezing values now calculated by ThermalModel properly and are now able to be passed back to IceBlock.
To hook ThermalModel and Crevasses
#70  IceBlock._get_virtualblue() method created, populate with functionality to:

[ ] resample virtual blue to IceBlock's z-resolution
[ ] divide by thermal_freq to adjust refreezing rates to the timestep used by the crevasse model. Currently by default refreezing rates will be 2x greater than they should be if this is not fixed.


Add spin lock to Flux materialization in Lazy Collections

Currently if a race exists the colleciton can be materialized twice on separate threads, this could cause problems if the lazy queued operators include functions that apply side effects. A better alternative is to spin wait on the loosing thread until the winning thread has completed.
Also add a materialize operator so races can be easily avoided entirely.

Merged


LSP[rust_analyzer] recieved end message with no corresponding begin

Description
I'm getting errors stated in the title when I open any Rust file/project. Idk if it some way affects how rust files are processed yet but this only happens with Rust
Neovim version
NVIM v0.7.2
Build type: Release
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
No response
Operating system and version
manjaro
Affected language servers
rust_analyzer
Steps to reproduce
nvim main.rs
Actual behavior
small delay at loading file and then I get error stated in the title
Expected behavior
No response
Minimal config
I'm using the standard config provided in this repo

LSP log
na

This repo isn't a support channel, it's just a collection of quickstart configs.
Your particular issue is/was a bug in rust_analyzer: https://github.com/neovim/neovim/issues/19158

Had the same issue - updated rust-analyzer to latest version and error gone.
Clone rust-analyzer repo, cd to it and do 'cargo xtask install --server'


Precise Interprocedural Dataflow Analysis via Graph Reachability

IFDS
14pages

Nanjing University's Static Program Analysis course,  Interprocedural Analysis part


Lost USB Connectivity with Repacked 242

Hey team,
Seems like I've lost USB connectivity with repacking firmware 242. I've used the repacker tool with no problems for over a year now, yet for some reason this time around this happened. I've tried different cables as well as different devices to connect it to, to no avail. I understand that the risk was on me, but just wanted to let you know in case you've seen it happen before or have any advice. No worries if not. Thanks.

(FWIW it's working fine for me)

Sorry to hear you have issues. I haven't heard of that before. Which mods did you use (although none of them should affect usb)? It's probably more likely that the usb port has gotten worn out somehow or clogged with dust. You could try to clean it and see if that helps.

Not sure if the OP responded on this one, but i’m going to repack with all mods enabled this evening on an original OP-1. I’ll update if any issues

He responded on the op-forum but it's still unclear what the cause of the problem was. I'm also running latest FW with all mods without any issues. Everything works just like before including the USB connection. I'm pretty sure the cause is unrelated to custom FW but I'll keep this issue open for now for any future follow ups.

Right on. I’ll give it a read through. Also no issues on my end with custom 242 FW


Clean up Stellar secret keys

We currently have some secrets for Stellar accounts lingering around in this repository. These are required for the successful execution of many integration tests. However it's not ideal to have these secrets available in this public repository and we need to clean this up.
TODO

Create a config that holds the required Stellar account secrets required by all tests. We need at least 4 different account secrets for both public and test network in total because we need to have a source account and a destination account on each network. These are used when testing transfers.
Pass the necessary account secrets as environment variables instead. It's very easy to add a configuration that is populated with env variables using clap, see here.
Replace all occurrences of hard-coded Stellar secret keys with keys passed to the config.

@pendulum-chain/product this doesn't add a new feature but removes technical debt and improves the security of our Stellar keys by not publishing them publicly. I'd give it a higher priority.

Hey team! Please add your planning poker estimate with Zenhub @b-yap @bogdanS98 @ebma @gianfra-t @TorstenStueber

@ebma do you agree? I would think that this does not interfere with the public launch.
Since these are all testnet secrets (?), I think it is merely more of annoyance if someone would steel them as we would have to recreate new accounts.

We don't have to fix this issue before the public launch. The secret keys that are exposed here are used on neither Foucoco, Amplitude nor Pendulum so there is no risk for Spacewalk on our production networks.

Moving this to icebox as it is low priority

Can I veto moving this to the icebox? In theory, I agree it's a good candidate for the icebox because it's not relevant to the security of the bridge itself. But it's kind of important for our internal security because we might forget about those keys being exposed and we'd end up wondering what's going on when people start messing with the accounts. So IMO it would still be nice to fix it soon.

@zoveress we are now very close to merging the respective changes for this. Going forward, the CI running the Spacewalk tests needs to have access to some Stellar account secrets. We already configured the credentials on Github but not yet on Gitlab. You can find the required secrets in the 'Spacewalk Testing Stellar accounts' item. You will need to supply them somehow to the pipeline running the cargo test command. The environment variable names are here.

@ebma can you please specify the entire command or I just have to define the envars and thats it?

Yes, they just have to be available in the environment. Alternatively, you can pass them directly when running the cargo test command, ie.  SOURCE_STELLAR_SECRET_MAINNET=... SOURCE_STELLAR_SECRET_TESTNET=... DEST_xxx= cargo test --all --all-featuresLast but not least you could also put them into a.envfile in theclients` directory, similar to this. The tests would pick that up automatically


Add more examples

Our examples are limited to Movielens (because it's handy), but it is clearly not the most "typical" implicit feedback data.
We clearly need more examples with

different datasets
reproducing recent papers

Added NeuMF type evaluation example.


jsp hook template

Just started reviewing :) :octocat: Sent from GH.

Pull request submitted to https://github.com/AndyWu2015/liferay-blade-tools/pull/1. See changes here. :octocat: Sent from GH.


return an empty node set when xpath expression doesn't match

Could you show me any examples that will cause a problem?

For example, the following example does not fail even though there is no matching nodes for a query:
julia> doc = parsexml("""<root/>""")
EzXML.Document(EzXML.Node(<DOCUMENT_NODE@0x00007fc53d7e9b10>))

julia> find(doc, "//notexit")
0-element Array{EzXML.Node,1}

Thank you. I've quickly checked libxml2 and found the following macro in xpath.h:
/**
 * xmlXPathNodeSetIsEmpty:
 * @ns: a node-set
 *
 * Checks whether @ns is empty or not.
 *
 * Returns %TRUE if @ns is an empty node-set.
 */
#define xmlXPathNodeSetIsEmpty(ns)                                      \
    (((ns) == NULL) || ((ns)->nodeNr == 0) || ((ns)->nodeTab == NULL))

So, your patch looks good to me 👍 .

👌


my dev container

still this issue:
/usr/local/bin/docker-entrypoint.sh: line 9: /root/scripts/cardano_node/run_cardano_node_testnet.sh: No such file or directory
[INFO  tini (1)] Spawned child process '/usr/local/bin/docker-entrypoint.sh' with pid '7'
[INFO  tini (1)] Main child exited normally (with status '127')


Consistently use std::exchange and use 2 phase swap for to support fancy pointers

Thanks for this.


Release Google.Cloud.Compute.V1 version 2.4.0

Changes in this release:
New features

Update Compute Engine API to revision 20221101 (issue 751) (commit 83e6c11)

Created release for Google.Cloud.Compute.V1-2.4.0


4.x: Add metrics for concurrency limits and fault tolerance

Currently we do not have metrics in fault tolerance components, and we did not introduce them to concurrency limits (https://github.com/helidon-io/helidon/issues/8897).
We should find a good way to be able to expose information from these components that can be seen in metrics.
We should honor the name of the component, to allow differentiation between instances (i.e. we can have a fixed metric for a client and a server, and these should not be seen in metrics as the same instance) - this can be achieved through name, which can be specified by user in configuration, or when explicitly setting an instance.

Watching.
Do we have a potential helidon version we expect this change to be available?

Watching.
Thanks,
David.

Hi team,
Could you clarify what specific types of metrics will be emitted by this enhancement? Additionally, in which version of Helidon will these new metrics features be available for users?
Thanks,
David

Yes,  Having metrics is critical for uptake of concurrency limit in production.
For Fixed Limit with queueing ,  we feel the following metrics  would be  very useful

Queue usage :  actual requests queued,    %queue full
Histogram for time spent by requests in a queue

For AIMD :

A metric that shows how the dynamic concurrency  goes up and down based on user concurrency and  requests breaching KPI

Do we know which Helidon version is expected to have this fix?

Hi @m0mus - Do you have a rough ETA for Milestone 4.3.0? We are trying to plan some HPA work around the concurrency rate limits.
Thanks in advance.
-David

Created specific issue for SE fault tolerance metrics. Note that MP fault tolerance metrics are already supported as part of the MicroProfile spec.


ci: require content of description and brief_description in classes doc

inspired by @KoBeWi's comment in #68948

tbh it's irritating when someone adds a feature, but doesn't bother to fill the description.

This PR changes type of <description> and <brief_description>to string with a min length of 10, which is then checked via xmllint in CI pipeline. Error looks like this:

doc/classes/WorkerThreadPool.xml:3: element brief_description: Schemas validity error : Element 'brief_description': [facet 'minLength'] The value has a length of '2'; this underruns the allowed minimum length of '10'.

Unfortunately there is over 600 empty <description> in the existing code already, so to make the pipeline pass I had to either regularly fill them (which feels quite overwhelming) or fill them up with just blank spaces. Not the best solution, but this could help to stop the problem getting worse over time.

okay so the blank spaces filling is not passing in other places in the CI...

Maybe you can post the list of files/classes so that people start filling them. Might speed up the process.
Filling with blank spaces might further obscure the issue so I would suggest against it.

We also don't need to require both of them, but at the same time we don't have a rule which one should be required. In any case, adding a warning and then faking content to suppress it doesn't look like a solution to the presented problem.

Yeah having more tooling to identify what's missing in a PR is good, but filling the docs with non-documentation for this purpose is not good.
We have a good tool to keep track of what is missing for each class: https://godotengine.github.io/doc-status/
For CI, what could be useful is a check that applies only to the PR's changes. So it could check for empty descriptions in the diff.
Still, as described in https://github.com/godotengine/godot/pull/68948#issuecomment-1321984073, there have been good reasons why some PRs have been merged without filling the documentation for the WIP API they were adding. So automated checks can be useful, but they should not be blocking - it could e.g. be a bot posting a reminder on the issue when a PR is approved by a maintainer but its diff still has empty documentation.
For the time being I think we're better off having PR reviewers point out the need to fill documentation when it's not done (and make it clear that it's required in our guidelines), so we can still make exceptions when relevant without blocking merges or requiring artificial content filling like here.

btw for finding missing descriptions etc. there is also https://github.com/KoBeWi/Godot-Documentation-Editor


Wrong usage of useEffect

As Dan Abramov said many times the useEffect hook is not for data fetching,  react don't have a hook for that. You can use SWR, React Query or your own fetcher around suspense but useEffect is not for that.
react has a hook "use effect" -- but this is primarily for data

Dan Abramov links to the same article in his example of how to fetch data with useEffect: https://overreacted.io/a-complete-guide-to-useeffect/#moving-functions-inside-effects -- I believe his concern is not that this is possible, but rather that people may do it in a way that hides dependencies from react.
This is the modified example that he gives:
function SearchResults() {
  const [query, setQuery] = useState('react');

  useEffect(() => {
    function getFetchUrl() {
      return 'https://hn.algolia.com/api/v1/search?query=' + query;    }

    async function fetchData() {
      const result = await axios(getFetchUrl());
      setData(result.data);
    }

    fetchData();
  }, [query]); // ✅ Deps are OK
  // ...
}

He also cites the same article that I have here, but we can update to his "complete guide for react". Pull requests welcome. Also, recently he said the following:

one way to think about it is that useEffect is a way to synchronize React with some external system (network, subscription, DOM). if you don’t have any external system and just try to manage your data flow with useEffect, you’re gonna have all these problems.

Emphasis added, citation: https://twitter.com/dan_abramov/status/1501737272999301121
So, it appears that fetching data is still one of the valid use cases for useEffect. The outcome, in relation to this proposal, is the same though. The point of this section is to show how async behavior is sometimes hidden by frameworks. Unlike other frameworks, react seems to only do this for data, and not for modules themselves.


Unable to predict for dict and set while optimizing "any" built-in

As discussed in #246 : Unable to predict dict and set datatypes while optimizing "any" built-in because those datatypes are not indexable.
I suspect this is primarly because this line while optimization
https://github.com/Nuitka/Nuitka/blob/efd876c1e02fa9a420d39100356e0bbffccde7b1/nuitka/nodes/ExpressionBases.py#L397
Reproducer
1. Script:  set.py
print(any(set([0, 1, 2, 3, 3])))

Executed:
$ ~/Nuitka/bin/nuitka3-run --verbose set.py
Output:
Nuitka:DEBUG:set.py:1 : new_expression : Using original '__file__' value.
Nuitka:DEBUG:set.py:1 : new_builtin_ref : Module variable 'print' found to be built-in reference.
Nuitka:DEBUG:set.py:1 : new_builtin_ref : Module variable 'any' found to be built-in reference.
Nuitka:DEBUG:set.py:1 : new_builtin_ref : Module variable 'set' found to be built-in reference.
Nuitka:DEBUG:set.py:1 : new_builtin : Replaced call to built-in 'set' with built-in call 'EXPRESSION_BUILTIN_SET'.
Nuitka:DEBUG:set.py:1 : new_builtin : Replaced call to built-in 'any' with built-in call 'EXPRESSION_BUILTIN_ANY'.
Nuitka:DEBUG:set.py:1 : new_constant : Built-in call to 'set' pre-computed. Predicted constant result.
Problem with statement at set.py:1:
-> print(any(set([0, 1, 2, 3, 3])))

Nuitka:INFO:Interrupted while working on '<Node 'PYTHON_MAIN_MODULE' with {'filename': 'set.py', 'main_added': False, 'mode': 'compiled'}>'.
Traceback (most recent call last):
  File "/home/bksahu/Nuitka/nuitka/__main__.py", line 184, in <module>
    main()
  File "/home/bksahu/Nuitka/nuitka/__main__.py", line 177, in main
    MainControl.main()
  File "/home/bksahu/Nuitka/nuitka/MainControl.py", line 745, in main
    main_module = createNodeTree(filename=filename)
  File "/home/bksahu/Nuitka/nuitka/MainControl.py", line 139, in createNodeTree
    Optimization.optimize(main_module.getOutputFilename())
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 545, in optimize
    finished = makeOptimizationPass(initial_pass=False)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 456, in makeOptimizationPass
    changed = optimizeModule(current_module)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 167, in optimizeModule
    changed = optimizeCompiledPythonModule(module)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 100, in optimizeCompiledPythonModule
    module.computeModule()
  File "/home/bksahu/Nuitka/nuitka/nodes/ModuleNodes.py", line 461, in computeModule
    trace_collection=self.trace_collection
  File "/home/bksahu/Nuitka/nuitka/nodes/StatementNodes.py", line 165, in computeStatementsSequence
    new_statement = statement.computeStatementsSequence(trace_collection)
  File "/home/bksahu/Nuitka/nuitka/nodes/FrameNodes.py", line 182, in computeStatementsSequence
    new_statement = trace_collection.onStatement(statement=statement)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 550, in onStatement
    new_statement, change_tags, change_desc = statement.computeStatement(self)
  File "/home/bksahu/Nuitka/nuitka/nodes/StatementNodes.py", line 229, in computeStatement
    trace_collection.onExpression(expression=self.getExpression())
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1038, in computeExpressionRaw
    expression = trace_collection.onExpression(sub_expression)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1038, in computeExpressionRaw
    expression = trace_collection.onExpression(sub_expression)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1057, in computeExpressionRaw
    return self.computeExpression(trace_collection=trace_collection)
  File "/home/bksahu/Nuitka/nuitka/nodes/BuiltinAnyNodes.py", line 46, in computeExpression
    any_node=self, trace_collection=trace_collection
  File "/home/bksahu/Nuitka/nuitka/nodes/ConstantRefNodes.py", line 383, in computeExpressionAny
    truth_value = value.getIterationValue(i).getTruthValue()
  File "/home/bksahu/Nuitka/nuitka/nodes/ConstantRefNodes.py", line 208, in getIterationValue
    constant=self.constant[count], source_ref=self.source_ref
TypeError: 'set' object does not support indexing

2. Script: dict.py
print(any({1:"One", 2:"Two"}))

Executed:
$ ~/Nuitka/bin/nuitka3-run --verbose dict.py
Output:
Nuitka:DEBUG:dict.py:1 : new_expression : Using original '__file__' value.
Nuitka:DEBUG:dict.py:1 : new_builtin_ref : Module variable 'print' found to be built-in reference.
Nuitka:DEBUG:dict.py:1 : new_builtin_ref : Module variable 'any' found to be built-in reference.
Nuitka:DEBUG:dict.py:1 : new_builtin : Replaced call to built-in 'any' with built-in call 'EXPRESSION_BUILTIN_ANY'.
Problem with statement at dict.py:1:
-> print(any({1:"One", 2:"Two"}))

Nuitka:INFO:Interrupted while working on '<Node 'PYTHON_MAIN_MODULE' with {'filename': 'dict.py', 'main_added': False, 'mode': 'compiled'}>'.
Traceback (most recent call last):
  File "/home/bksahu/Nuitka/nuitka/__main__.py", line 184, in <module>
    main()
  File "/home/bksahu/Nuitka/nuitka/__main__.py", line 177, in main
    MainControl.main()
  File "/home/bksahu/Nuitka/nuitka/MainControl.py", line 745, in main
    main_module = createNodeTree(filename=filename)
  File "/home/bksahu/Nuitka/nuitka/MainControl.py", line 139, in createNodeTree
    Optimization.optimize(main_module.getOutputFilename())
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 545, in optimize
    finished = makeOptimizationPass(initial_pass=False)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 456, in makeOptimizationPass
    changed = optimizeModule(current_module)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 167, in optimizeModule
    changed = optimizeCompiledPythonModule(module)
  File "/home/bksahu/Nuitka/nuitka/optimizations/Optimization.py", line 100, in optimizeCompiledPythonModule
    module.computeModule()
  File "/home/bksahu/Nuitka/nuitka/nodes/ModuleNodes.py", line 461, in computeModule
    trace_collection=self.trace_collection
  File "/home/bksahu/Nuitka/nuitka/nodes/StatementNodes.py", line 165, in computeStatementsSequence
    new_statement = statement.computeStatementsSequence(trace_collection)
  File "/home/bksahu/Nuitka/nuitka/nodes/FrameNodes.py", line 182, in computeStatementsSequence
    new_statement = trace_collection.onStatement(statement=statement)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 550, in onStatement
    new_statement, change_tags, change_desc = statement.computeStatement(self)
  File "/home/bksahu/Nuitka/nuitka/nodes/StatementNodes.py", line 229, in computeStatement
    trace_collection.onExpression(expression=self.getExpression())
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1038, in computeExpressionRaw
    expression = trace_collection.onExpression(sub_expression)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1038, in computeExpressionRaw
    expression = trace_collection.onExpression(sub_expression)
  File "/home/bksahu/Nuitka/nuitka/optimizations/TraceCollections.py", line 531, in onExpression
    r = expression.computeExpressionRaw(trace_collection=self)
  File "/home/bksahu/Nuitka/nuitka/nodes/ExpressionBases.py", line 1057, in computeExpressionRaw
    return self.computeExpression(trace_collection=trace_collection)
  File "/home/bksahu/Nuitka/nuitka/nodes/BuiltinAnyNodes.py", line 46, in computeExpression
    any_node=self, trace_collection=trace_collection
  File "/home/bksahu/Nuitka/nuitka/nodes/ConstantRefNodes.py", line 383, in computeExpressionAny
    truth_value = value.getIterationValue(i).getTruthValue()
  File "/home/bksahu/Nuitka/nuitka/nodes/ConstantRefNodes.py", line 208, in getIterationValue
    constant=self.constant[count], source_ref=self.source_ref
KeyError: 0

python -m nuitka --version
0.6.3rc3 (Branch: optimize_buildin_any  #246)
Python: 3.6.8 |Anaconda, Inc.| (default, Dec 30 2018, 01:22:34)
Executable: ~/anaconda3/envs/nuitka/bin/python3
OS: Linux
Arch: x86_64

Thanks for reporting this, great find.
A few things I want to highlight @bksahu about optimization in Nuitka. First of all, I have adopted a method, where I give each level of optimization its own spin, and your finding is evidence of it being useful. So, what I would do, is first:
a) Run all world test without the optimization (done already)
b) Run all world test with only the C code replaced, basically using your C code only, and see what this finds. This is the point in time, where this has the best exposure. The node would return self, None, None and be good, i.e. definitely not do anything wrong.
c) Run all world test with the generic implementation (the one you got right now in your PR), and see what it does (any it finds bugs).
d) Look at cases to specialize and do that, again run all world test with that.
On each stage, there is a tendency to find bugs. Right now, you can't really run the "all world test", but it has to be done on my infrastructure, as it needs really a lot of CPU and time. If you have a machine that might heat up and become not as responsive, you can try running the CPython test suite for one version at least. But I think I have to make an arrangement for you. It's a shame we don't have public CPU in large quantity yet. I will try and push for donated resources soon though. Nothing like Travis will allow us to use much CPU by default.
So, this is the general approach, and as you can see, had you headed my additional request to specialize any for constant nodes (computing any(self.constant) would be much faster than manual iteration, however at least for any not by much, due to most of the constants containing only stuff with positive truth value). That would would break going in baby steps. Ideally it's also why the built-in task is done in parallel, i.e. start other built-ins and e.g. bring the to the C only level, etc.
This testing approach deserves to be formalized with a table I guess. I am really happy about the opportunity to remember this, and why I have done it like above normally.

Also, another experience with optimization is, that when we add new one, we increase the burden on it being correct. Nuitka has historically been incorrect on many things with these kind of things, and then when new optimization gets added, old errors get exposed, because now we depend on it being correct more deeply.
The compile whole world test is going to crash in places you don't expect, and this could well have happened to us, had you not sought good enough test coverage yourself. For example, it could have gone unnoticed, and a for loop over constant values in the CPython test suite, would not hit the code now. But the day we start to unroll such loops, then it would crash, unrelated to the optimization being done there.
So there is a tendency to uncover existing bugs that is far more widespread in Nuitka than you would normally encounter, because easily everything can affect everything. Every new optimization adds new requirements, or makes new test cases. For example, previously nothing was known about any expressions, but with your addition, more constants, more bool shapes enter the world, and that can affect code generation, and expose bugs there.

As for your bug, I would suggest you would question this code in ConstantRefNodes.py
    def canPredictIterationValues(self):
        return self.isKnownToBeIterable(None)

Being iterable at all, doesn't mean you can predict the values, and definitely not this way:
def getIterationValue(self, count):
    assert count < len(self.constant)

        return makeConstantRefNode(
            constant=self.constant[count], source_ref=self.source_ref
        )

So, this could be done with next() calls on a iter(self.constant), but do we really want to go there? I doubt, we should do this. Maybe instead a node, needs to provide something that is a like a handle on iteration, so that we don't get called by the index, but rather with an expression that we want to go next. Can you propose an API from the perspective of your any node? One where you could ask to get a iteration handle, and then only use that, to predict the values. I know I am asking much here, but I think you ought to try thinking of that.
Then I think, random access, and sequential access, could be differentiated. Right now your any code is using an interface that is for random access in a sequential fashion. And even then, emulating the random interface on 3.6 dicts would be extremely costly.
If you search for .getIterationValue you barely find uses. So replacing it with your API will be relative easily possible.

@kayhayen I have a doubt. While debugging I have noticed that for example print(any[0] * 20000)  the control flows through ExpressionBases.py (I mean it is computed there) whereas for  print(any({1:"One", 2:"Two"})) the control flows through ConstantRefNodes.py. So could you please explain me this behaviour? When should I expect that control will flow though ConstantRefNodes.py and when from ExpressionBases.py ?

@bksahu The first expression of yours is going to raise an exception, because any is not indexable. Is it a typo, or what you actually looked at?

Sorry that was a typo.

Where do we stand with this one?

Sorry, I haven't been able to work on it due to my exams which will end in next two weeks.

Maybe instead of a node needs to provide something that is a like a handle on iteration, so that we don't get called by the index, but rather with an expression that we want to go next. Can you propose an API from the perspective of your any node? One where you could ask to get an iteration handle, and then only use that, to predict the values.

I don't what exactly understand what do you mean by the handle and how it is going to return an expression instead of index. Could you give me some pointers?
Do you mean something like this:
truth_value = value.getIterationValueExpression(i).getTruthValue()

def getIterationValueExpression(self, index):
    return makeConstantRefNode(
            constant=next(iter(self.constant)), source_ref=self.source_ref
     )

@bksahu I was thinking that a node, like range, constant value, etc. should be able to return a new kind of object, one with methods, that will be used instead of itself. So instead of calling getIterationValue(3) as in the old API (spelling might be off), we first call a method that can be called getIterationHandle() which then has methods and internally obviously a reference to the node that produced it, but will then have an interface that is most suitable to us.
This would then offer ways do get the next value and/or its value shape, the length and so, and these would be used in generic algorithms like your any default implementation.
The problem of your method is that the iterator gets lost. That is something I would expect the handle to store, and re-use.
This is a rought sketch up:
class ConstantInterationHandle:
   def __init__(self, constant):
       self.constant = cons
       self.iter = iter
   def getNextValueExpression(self):
       return makeConstantRefNode(constant=next(self.iter), ...)

Obviously, this needs to have its way of saying `StopIteration` as well.

For some constants, or ranges, or list multiplications, we will have better knowledge, and random access will be possible.

There are remnants of very weak iterator tracing in Nuitka. These handles, I would assume, could become value traces of the `iter()` and later become mergeable between branches.

Basically you need to think of these objects as intermediates. They address the need of generic algorithms to have more or less random access, as well as the difficulty of the producing side, to have its own state. We cannot well track a `self.iter` inside the nodes, imagine the memory usage of every constant in the node tree had that. Plus a node shouldn't contain state related to the abstract execution.

From this, pretty immediately the need for an object between the node and the using algorithm comes into play, and that is pretty much immediately the only way to really do it.

Yours,
Kay


is it possible to set perpagesize into [10, 25, 50, 100, ALL]

Hello sir Andre, first of all this is not an issue this is just a question.
I just want to ask if it is possible to set perpagesize into [10, 25, 50, 100, ALL]
because i have a dynamic data and sometimes it exceeds the given size per page.
i am using the export to csv but it limits the row of data that i wanna export.
right now i am using perpagesize =  [10, 25, 50, 100, 10000] since i my data doesn't exceed 10000.
Hope you can help me again. thank you :)

Hello!
Yes, this is indeed possible!
Just pass a dynamic value for perPageSizes, like as follows:
<template>

Dashboard

        <data-table v-bind="bindings"/>

</template>

I think this solves your problem

Now, I recognize my proposed solution is not good.
Indeed, it is better to have a "SHOW ALL" option instead of setting the perpages sizes.
I will add it.

@paul-cylix this feature has been added to the latest branch and will be available soon in the next release. I'll just add some more tests before publishing a new release. Thanks for helping improving the project. I hope this plugin has been helpful!


Gradients are asymmetrical

When creating a gradient with minimessage the produced colors are asymmetrical
When creating the following gradient <gradient:red:green:blue>123 It would be reasonably assumed that 1, 2 and 3 are red, green and blue respectively.
In reality however 1 is red 2 is green and 3 is a slightly darker green as shown below:

I have also tested this in the webui with the same results.
When using a larger string it is also observable:

seems like the last color is basically exclusive, not inclusive

Seems to be fine now.


go get github.com/dolthub/go-mysql-server got the wrong path?

I tried to import the dependency using go get github.com/dolthub/go-mysql-server, but i got err msg:
$ go get github.com/dolthub/go-mysql-server
go: github.com/dolthub/go-mysql-server upgrade => v0.6.0
go get<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/liquidata-inc/go-mysql-server
                but was required as: github.com/dolthub/go-mysql-server

If you use go mod tidy to import the dependencies in the example, you can also encounter this problem!
So, i'm wondering if you can solve this problem?

Think the problem is that the most recent release had tag '0.7.0' instead of 'v0.7.0', so it went for v0.6.0 instead.
In any case I've now release v0.8.0 off master but, I'm not sure it's working right. I see:
go get github.com/dolthub/go-mysql-server
# github.com/dolthub/go-mysql-server/sql/expression/function/aggregation
C:\Users\Zach Musgrave\go\src\github.com\dolthub\go-mysql-server\sql\expression\function\aggregation\count.go:165:33: no
t enough arguments in call to hashstructure.Hash
        have (interface {}, nil)
        want (interface {}, hashstructure.Format, *hashstructure.HashOptions)

It probably depends what version of github.com/mitchellh/hashstructure you have installed. The project uses 1.0.0.

The v0.8.0 works fine with me. Thx!!! ♥


How do we support VS Code Insiders in winget?

Related: https://github.com/microsoft/winget-pkgs/issues/277
code-insiders is published approximately daily, while we could automate a PR for stable I don't think it makes sense to do this for Insiders. We have a web endpoint that points to the latest version, can we just not include a Version in the manifest?
@KevinLaMS

As the Visual Studio Code release version and the insiders can be installed "side-by-side" we are looking at generating a manifest and having the submission as part of their release process. We would have the standard package and manifests for the release version. As well as the daily insiders build.

Couldn't you fetch the hash for comparison if you don't want to ignore it? You should be able to get this from Github at the very least.


Refactor mixins

Flat is better than nested.

Ready for review @nobodxbodon @kaguillera @mattbk et al. I'd like to get this in master and then rebase https://github.com/gratipay/gratipay.com/pull/4305 to build on this.

Redone to fix a test.

LGTM

Don't wait for me.

@kaguillera Merge? :-)

Rebased, was 2d2b580127e03f8dfbfd7d8c37cd20d0e00908f6.


Fix indexing and pdf splitting

A collection of fixes discovered during Adventist testing.
Should be thoroughly tested on base Hyku before merging.

Test list:

[ ] PDF splitting works in UI upload
[ ] PDF splitting in Bulkrax CSV - same row
[ ] PDF splitting in Bulkrax CSV - separate fileset row
[ ] PDF splitting in Bulkrax CSV - remote URL
[ ] is_child gets set on solr for child works
[ ] is_child does not get set on solr for if not a child work
[ ] derivatives are generated
[ ] OCR text is indexed
[ ] Searching PDF text in Catalog search
[ ] Searching PDF text in Parent's UV
[ ] Searching PDF text in Child's UV


Add Slider and toggle components

I was wondering since bootstrap has been built with "mobile first" in mind, why there is no slider and toggle (which are key components in the mobile world)!
Shouldn't be new features to add to the new v4?

Should be one of the top priorities, it's so basic.

+1 its an essential component for a lot of websites

Angular Material too has these components. Its a basic need in mobile.

I migrated to material for several reasons: slider, RTL and pagination support out of the box, I don't understand how this is not implemented already in bootstrap, especially the RTL - this is a requirement as old as bootstrap...

@HarelM The only problem I have with material is that it is too style heavy. I guess we would need more designers to make sure that custom elements gel well with material elements.

@HarelM Don't forget that nobody at bootstrap is paid for this project (AFAIK) while material is backed by Google... so yeah, it's a must have but be patient!

True, I can't argue about it, although I don't think it's a matter of payment but priorities - bootstrap 4 has a lot of code changes but still doesn't have RTL and slider - which means it's not highly prioritized, it's not like this project doesn't have contributors and maintainers...

Totally agree, I clearly miss sliders and toggle components.
If I had the skills, I would do it !

@mdo Any chance this can be implemented in the next release?

slider has allready been added, the switch is still in progress i guess. although i couldn't find it on any project board

Exactly slider has already being added. The toggle-switch, seems that they are reviewing it.
Man I really hope it becomes part of this release.

Custom switch was added for v4.2 (launching soon), and the custom range was added in v4.1. Closing out!

Is the "Feature Idea" project still used? If so this issue should be removed from there to keep it clean and up to date


Fix OS X build

Not sure what the reason was to have an Apple-specific path to UnitTest++.h with repeated occurrences of UnitTest++, but that Apple-specific path causes the build to fail for me under OS X. (I think I set up the UnitTest library following the instructions in the Wiki, but it's been a while so I'm not 100% sure anymore.)

@cinquin see https://github.com/RichardWarburton/honest-profiler/pull/114. Now I don't use Mac OS X, so for me I've been trusting other contributors comments on Mac OS X builds and stability. Consequently I'd like to solicit some feedback for this PR.
@kylesm - does this PR work for you?
@nitsanw - I've seen you using a Mac ;) Does this PR work for you and have you had similar build problems to @cinquin ?
Sorry for not just merging immediately, I just want to make sure we aren't going to have a "whack a mole" type situation with Mac OS builds where a fix for some people then causes the build to break on other machines.

@cinquin see #114.

Ah I see. This ifdef looks like it may be a Homebrew-specific adjustment (I don't use Homebrew). It's easy enough to fix by hand. I guess whether it makes sense to have this Apple-specific code depends on whether it is expected that the majority of OS X users use Homebrew and will have a need for the adjustment. I don't have the answer to that. Feel free to just close this PR if there's a majority in favor of the Homebrew version...

Perhaps a better solution would be something that detects the UnitTest++ path at compile time?

Perhaps a better solution would be something that detects the UnitTest++ path at compile time?

Absolutely. I imagine it would be easy to adjust the CMake configuration to do just that.

@cinquin did you have a chance to look into the cmake approach? If so, would it be an extension of this PR or another one?

@RichardWarburton I haven't had time to look into this, and probably won't for a while.
I think adjusting the CMake configuration is definitely the way to go, and should be pretty straightforward.
The CMake adjustment would come in addition to the change I've submitted in this PR, which is necessary in any case to fix the build for OS X users who do not use Homebrew (and the ad hoc, Homebrew-specific changes that this PR removes will be made obsolete by the CMake adjustment).

Thanks for clarifying. In that case I'll leave this PR open and if you get some time to finish off the cmake things then I'll get it merged. Thanks again for your work here - its most appreciated.

Sorry. I didn't see this pull request, but I made a CMake adjustment in this Pull Request that works with the head of the unittest-cpp/unitest-cpp project's master branch.  That branch was recently updated in unittest-unittest-cpp/unittest-cpp@e88121f to provide cmake files to make it easier to consume after it is installed from sources.
I haven't yet confirmed whether that pull request breaks the CMake config on a non Mac OS X system, but it definitely allows a build to happen on Mac OS X.

Yes your fork of honest-profiler builds fine for me as such.
Thanks for having taking care of this; I'll close this pull request.

Thanks @cinquin - just following up on this thread - I've merged #172 - so everything should be fixed now anyway.
Thanks for your contribution gents.


migrate rational API to use the new error handling mechanism instead of Result

…of Result

Pull Request Test Coverage Report for Build 2122
Details

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

Totals

Change from base Build 2118:
0.0%

Covered Lines:
3578

Relevant Lines:
3916

💛  - Coveralls


Add configmaps and pod rules.

Signed off by @jnpacker

The leader election rules were lost when making a change 4 days ago. They were:

configmaps: create, get
pods:           get

Issue reference:
https://github.com/open-cluster-management/backlog/issues/10674
Original errors:
Create configmaps:
E0319 13:27:15.074157       1 controller.go:128] configmaps is forbidden: User "system:serviceaccount:open-cluster-management:cluster-curator" cannot create resource "configmaps" in API group "" in the namespace "open-cluster-management": RBAC: clusterrole.rbac.authorization.k8s.io "open-cluster-management.cluster-lifecycle.cluster-curator" not foundDid not obtain leader cluster-curator-controller-lock

Get configmaps:
E0319 13:25:15.583227       1 controller.go:128] configmaps "cluster-curator-controller-lock" is forbidden: User "system:serviceaccount:open-cluster-management:cluster-curator" cannot get resource "configmaps" in API group "" in the namespace "open-cluster-management": RBAC: clusterrole.rbac.authorization.k8s.io "open-cluster-management.cluster-lifecycle.cluster-curator" not foundDid not obtain leader cluster-curator-controller-lock

Get pods:
E0319 13:23:32.483700       1 controller.go:128] pods "cluster-curator-controller-7fdd56984b-8fhtc" is forbidden: User "system:serviceaccount:open-cluster-management:cluster-curator" cannot get resource "pods" in API group "" in the namespace "open-cluster-management": RBAC: clusterrole.rbac.authorization.k8s.io "open-cluster-management.cluster-lifecycle.cluster-curator" not foundDid not obtain leader cluster-curator-controller-lock

/cc @chrisahl
Testing results:
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm get pods --watch | grep curator
cluster-curator-controller-7fdd56984b-shll4                       0/1     ContainerCreating   0          23s
cluster-curator-controller-7fdd56984b-tq2px                       0/1     ContainerCreating   0          23s
cluster-curator-controller-7fdd56984b-shll4                       1/1     Running             0          42s
cluster-curator-controller-7fdd56984b-tq2px                       1/1     Running             0          43s
^C
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm logs cluster-curator-controller-7fdd56984b-shll4
I0319 13:28:54.281191       1 request.go:645] Throttling request took 1.099400757s, request: GET:https://<IP_ADDRESS>:443/apis/hiveinternal.openshift.io/v1alpha1?timeout=32s
I0319 13:28:55.281223       1 request.go:645] Throttling request took 2.099262284s, request: GET:https://<IP_ADDRESS>:443/apis/autoscaling/v2beta2?timeout=32s
I0319 13:28:56.282345       1 request.go:645] Throttling request took 3.100276532s, request: GET:https://<IP_ADDRESS>:443/apis/admission.work.open-cluster-management.io/v1?timeout=32s
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm logs cluster-curator-controller-7fdd56984b-tq2px
I0319 13:28:54.173961       1 request.go:645] Throttling request took 1.099550598s, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1beta1?timeout=32s
I0319 13:28:55.374204       1 request.go:645] Throttling request took 2.09949598s, request: GET:https://<IP_ADDRESS>:443/apis/metal3.io/v1alpha1?timeout=32s
I0319 13:28:56.391689       1 request.go:645] Throttling request took 3.317158197s, request: GET:https://<IP_ADDRESS>:443/apis/search.open-cluster-management.io/v1alpha1?timeout=32s
I0319 13:28:58.974434       1 reflector.go:207] Starting reflector *v1.ManagedCluster (0s) from github.com/open-cluster-management/cluster-curator-controller/cmd/controller/controller.go:100
I0319 13:28:59.274401       1 controller.go:61] > Investigate Cluster local-cluster
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$

Testing results:
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm get pods --watch | grep curator
cluster-curator-controller-7fdd56984b-shll4                       0/1     ContainerCreating   0          23s
cluster-curator-controller-7fdd56984b-tq2px                       0/1     ContainerCreating   0          23s
cluster-curator-controller-7fdd56984b-shll4                       1/1     Running             0          42s
cluster-curator-controller-7fdd56984b-tq2px                       1/1     Running             0          43s
^C
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm logs cluster-curator-controller-7fdd56984b-shll4
I0319 13:28:54.281191       1 request.go:645] Throttling request took 1.099400757s, request: GET:https://<IP_ADDRESS>:443/apis/hiveinternal.openshift.io/v1alpha1?timeout=32s
I0319 13:28:55.281223       1 request.go:645] Throttling request took 2.099262284s, request: GET:https://<IP_ADDRESS>:443/apis/autoscaling/v2beta2?timeout=32s
I0319 13:28:56.282345       1 request.go:645] Throttling request took 3.100276532s, request: GET:https://<IP_ADDRESS>:443/apis/admission.work.open-cluster-management.io/v1?timeout=32s
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$ ocm logs cluster-curator-controller-7fdd56984b-tq2px
I0319 13:28:54.173961       1 request.go:645] Throttling request took 1.099550598s, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1beta1?timeout=32s
I0319 13:28:55.374204       1 request.go:645] Throttling request took 2.09949598s, request: GET:https://<IP_ADDRESS>:443/apis/metal3.io/v1alpha1?timeout=32s
I0319 13:28:56.391689       1 request.go:645] Throttling request took 3.317158197s, request: GET:https://<IP_ADDRESS>:443/apis/search.open-cluster-management.io/v1alpha1?timeout=32s
I0319 13:28:58.974434       1 reflector.go:207] Starting reflector *v1.ManagedCluster (0s) from github.com/open-cluster-management/cluster-curator-controller/cmd/controller/controller.go:100
I0319 13:28:59.274401       1 controller.go:61] > Investigate Cluster local-cluster
wsl2@jnp-rh:[🔱main]:🏡/workspace_git/cluster-curator-controller$


fix cartpole argument examples formating

previously:
https://gymnasium.farama.org/main/environments/classic_control/cart_pole/

Complete in #898


Add detekt

Codecov Report

Merging #9 (638527b) into main (c56411d) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   13.74%   13.74%
=======================================
  Files          17       17
  Lines         604      604
  Branches       79       79
=======================================
  Hits           83       83
  Misses        515      515
  Partials        6        6

Impacted Files
Coverage Δ

...xvanyo/composelife/data/TemporalGameOfLifeState.kt
0.00% <ø> (ø)

.../kotlin/com/alexvanyo/composelife/ui/CellWindow.kt
0.00% <0.00%> (ø)

...lin/com/alexvanyo/composelife/ui/ComposeLifeApp.kt
0.00% <ø> (ø)

...n/com/alexvanyo/composelife/ui/InteractableCell.kt
47.61% <ø> (ø)

.../com/alexvanyo/composelife/ui/InteractableCells.kt
59.67% <ø> (ø)

...kotlin/com/alexvanyo/composelife/ui/theme/Shape.kt
0.00% <ø> (ø)

...kotlin/com/alexvanyo/composelife/ui/theme/Theme.kt
0.00% <ø> (ø)

.../kotlin/com/alexvanyo/composelife/ui/theme/Type.kt
0.00% <ø> (ø)

...poselife/ui/util/CustomTransformGestureDetector.kt
0.00% <ø> (ø)

... and 2 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 c56411d...638527b. Read the comment docs.


Prevent model server crash if data is missing in metadata file during callHome

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report
Attention: 1375 lines in your changes are missing coverage. Please review.

Comparison is base (bb5073f) 72.08% compared to head (36d5af0) 72.15%.
Report is 889 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2799      +/-   ##
============================================
+ Coverage     72.08%   72.15%   +0.06%
- Complexity     5126     7110    +1984
============================================
  Files           473      702     +229
  Lines         21970    31680    +9710
  Branches       2351     3285     +934
============================================
+ Hits          15838    22860    +7022
- Misses         4925     7261    +2336
- Partials       1207     1559     +352

Files
Coverage Δ

...ava/ai/djl/inference/streaming/StreamingBlock.java
100.00% <100.00%> (ø)

api/src/main/java/ai/djl/metric/Dimension.java
100.00% <100.00%> (ø)

api/src/main/java/ai/djl/metric/Unit.java
100.00% <100.00%> (ø)

api/src/main/java/ai/djl/modality/audio/Audio.java
100.00% <100.00%> (ø)

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...ava/ai/djl/modality/cv/output/DetectedObjects.java
96.29% <100.00%> (+1.29%)
:arrow_up:

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <100.00%> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...i/djl/modality/cv/transform/RandomResizedCrop.java
94.11% <100.00%> (+5.22%)
:arrow_up:

... and 226 more

... and 372 files with indirect coverage changes

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


on user opening PT while it is already running, open settings

if a user launches PowerToys multiple times, we should open up the settings dialog.
They may not realize it is open and think something has gone wrong.  (i've done this multiple times :) )

Note: UWP apps by default won't create a second instance, need to verify if this is also true for centennial apps. In case, figure out if the app receives a notification that the user has tried to launch it again, so that PT can show the settings.

Currently we show

And this is really useful during development, what if we add a button to offer to open the settings?

I think we should figure out how we can support development scenarios but end user is top priority.
I don't think this prompt is helpful / useful.

Fixed in v.0.17 https://github.com/microsoft/PowerToys/releases


config.json: update house

add topics and change difficulty

Don't we need to reorder exercises according to difficulty ?

We will need to re-order at some point, yes. We can either re-order as we go along or when the config.json file is complete. If we order as we go there might be quite a bit of churn as we continue to update config.json, though if we wait for config.json to be completed we may be waiting a while.
Also, is it generally accepted to order according to difficulty, rather than interspersing a run of difficult exercises with something slightly easier, to keep morale up as it were, or taking into consideration the topics as well so that similar exercises are not too closely grouped?


[WFLY-13489] Reduce some debug logging from tests. Change some tests …

…that log info messages to debug. Clean up the test logging configuration files.
https://issues.redhat.com/browse/WFLY-13489
There are some other log messages that could likely be removed. For now these are just the ones I did.
I've also contemplated removing the duplicate logging.properties files. If anyone else feels we should do that let me know and I'll create a single one in the base test suite.

@pferraro and @rhusar clustering had fairly verbose logging enabled which I reduced quite a bit here. Does this seem okay to you guys?


Fix 3784 issue

Description
This PR fixes #3784 . It appears the DiffTime used for checking opportunities aren't ignored for too long is not correctly tuned. The solution consists in slightly increasing the time window considered.
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

I put the description ahead of Checklist (anything after #Checklist will be removed by bors).

bors merge

bors merge


[REQUEST] Why not support charts in terminal~?

Consider posting in https://github.com/willmcgugan/rich/discussions for feedback before raising a feature request.
Have you checked the issues for a similar suggestions? 1
How would you improve Rich?
Support some basic charts, like what diagram lib did.
Example for line chart:
    def __str__(self):
        """
        绘图并返回字符串

        Draw and return a string

        :return: 折线图的字符串
        """
        opt = diagram.DOption()
        opt.size = diagram.Point([self.height, self.width])
        opt.mode = 'g'
        stream = io.BytesIO()
        gram = diagram.DGWrapper(
            data=[self.values, range(len(self.values))],
            dg_option=opt,
            ostream=stream
        )
        gram.show()
        return str(stream.getvalue(), encoding="utf-8")

What problem does it solved for you?
I can do more things using rich, it's exciting that draw a beautifule chart in rich's containers like table or tree

It may happen. But ideally diagram or a library like it could add support for Rich.

It may happen. But ideally diagram or a library like it could add support for Rich.


Fix warnings

Current dependencies on/for this PR:

main

PR #162   👈

This stack of pull requests is managed by Graphite.