autogluon 1.1.1 :snowflake:

autogluon 1.1.1 :snowflake:
Destination channel: Snowflake
Links

PKG-5331
dev_url:        https://github.com/autogluon/autogluon/tree/v1.1.1
conda_forge:    https://github.com/conda-forge/autogluon-feedstock
pypi:           https://pypi.org/project/autogluon/#files
pypi inspector: https://inspector.pypi.io/project/autogluon/1.1.1/

Explanation of changes:

new version number

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d1a4uuvupj/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:162: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:269: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:347: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:286: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:84: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:285: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:270: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:277: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:284: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:291: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:53: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:208: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:268: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:287: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:292: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:282: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:273: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:274: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:358: version_constraints_missing_whitespace: output "autogluon.timeseries": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:288: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:272: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:271: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:283: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:307: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:266: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:267: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:119: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:278: version_constraints_missing_whitespace: output "autogluon.multimodal": Packages and their version constraints must be space separated
===== Final Report: =====
29 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_7bnob75y9k/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:84: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:162: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:119: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:53: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:307: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:208: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:347: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
8 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e8_21ghra7/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:347: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:162: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:84: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:119: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:53: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:208: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:307: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
8 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_df_02nugf0/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:347: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:208: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:162: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:84: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:53: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:119: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:307: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
8 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_2eedj5yvzr/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:302: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:85: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:54: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:120: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:195: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:163: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:262: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_79qgtvajpq/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:262: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:54: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:163: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:303: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:195: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:85: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:120: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_73o1yglkjh/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:118: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:52: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:83: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:193: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:260: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:301: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:161: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_34ob93n7q8/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:301: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:83: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:118: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:52: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:161: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:260: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:193: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_81obmqamr1/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:260: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:52: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:193: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:118: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:161: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:301: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:83: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_abi0jdoz1h/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:56: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:264: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:197: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:122: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:165: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:305: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:87: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_7c0_ftohco/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:85: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:163: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:195: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:303: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:54: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:120: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:262: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_8eq383v9ut/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:195: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:262: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:163: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:120: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:85: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:303: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:54: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_51y9179f0r/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:120: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:291: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:85: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:54: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:189: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:252: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:159: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_79rtb8lgay/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:276: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f0jun1w8an/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:276: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_24e9v1ogu_/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:277: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_ee95abbrif/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:277: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_5clltpfmrw/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:276: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d7yktdsp75/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:276: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f88sawwy2s/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:75: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:276: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:240: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:44: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:149: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:110: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
clone/recipe/meta.yaml:179: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
7 Errors and 0 Warnings were found


Enable UI UT test framework (karma and jasmine) for UI lib

Enable UI UT test framework (karma and jasmine) for UI lib

Coverage increased (+0.05%) to 55.226% when pulling e31bab435b038e2984af3f7541cccc65155c8b8b on steven-zou:master into 6acf49581cd0863eb3df35c46cfaee1ff60a282f on vmware:master.

shouldn't it be triggered in travis.yml?

yes, it can be triggered in travis. But I suggest to enable it in travel a little later after  real components are implemented.


$videoDetails->getTitle() not working.

Has anyone else noticed this?
I assume YouTube must have changed something that the parsing logic can no longer find the title?

I don’t know what changed but it works again.


Cannot send files anymore (version 0.5.0)

Hello,
after the 0.5.0 release I'm not able to send files anymore.
bot.api.send_voice(chat_id: message.chat.id, voice: File.new(path), caption: caption)

I'm getting error 400 from telegram's API, telling that the file_id is too long or contains not allowed chars (I don't specify a file_id).
Downgrading to version 0.4.2 fixes the issue.

Hi!
Use Faraday::UploadIO.new instead of File.new (see example here: https://github.com/atipugin/telegram-bot-ruby#file-upload)

👍 thanks!

On 18 Apr 2016, at 11:24, Alexander Tipugin<EMAIL_ADDRESS>wrote:
Hi!
Use Faraday::UploadIO.new instead of File.new (see example here: https://github.com/atipugin/telegram-bot-ruby#file-upload https://github.com/atipugin/telegram-bot-ruby#file-upload)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/atipugin/telegram-bot-ruby/issues/50#issuecomment-211293016


Pm 2.0 ga2 kim edits

Please review all files in this PR. One of the TS items is missing a 'cause' and I am working on it.

Fixes have been added to the GA doc.


Update MD file on new branch 2017-05-04_16-11-18

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature/healthcheck endpoint

@necrophonic - can you ok this for merge?

Should probably document the available endpoints (healthcheck) in the readme

@necrophonic done :+1:


Verifying requests

I've looked through the API a bit and it seems like it is designed around providing the capability to send a signed request but not necessarily verify an incoming OAuth request.
I was wondering if there is anyway to verify a incoming OAuth request using this library?

Unfortunately, you're right.  Of the three parties involved in an OAuth transaction: the service provider (e.g. twitter), the end-user, and the third-party application (aka the "Consumer"), this library is designed to implement the third part app / consumers.
After a brief look, I didn't see an obvious service provider for OAuth 1.0 in golang.   However, it looks like if you're willing to use OAuth 2.0, there is a service provider implementation here: https://github.com/RangelReale/osin
I'm going to close this for now, but feel free to re-open if you have more questions!


forever: command not found

Just installed tonight with out error but I did receive some warnings:
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.21"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.21"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.21"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.21"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x"} (current: {"node":"v0.10.24","npm":"1.3.21"})
To me I'm running a newer version than forever was looking for but I can only assume it will work…correct?
Here is the install command I used: sudo npm install forever -g
I did run the install a second time resulting in the same output.
I'm trying to set it to run Ghost using their suggested command line from the install directory: NODE_ENV=production forever start index.js
To me the command line seems wrong but the response I got with that command line is:
NODE_ENV=production: Command not found.
I expected an error but still i followed their direction.
So I tried: forever start index.js
OS Returned: forever: Command not found.
I'm on Mac OS 10.8.5

For some reason the forever command was not added to my path so I had to reference the forever executable in the node_modules like so node_modules/forever/bin/forever.


Fixed compile messages error

Hi there,
Thanks for writing this app. My patch fixes the following error when running "./manage.py compilemessages -l id"
./libraries/linguo/models.py:94: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.

Thank you very much for contributing this!


Is there a way to ensure PRs are not automaticalyl merged?

For my use case, I'm wanting to just keep an update to date PR of upstream changes, and when I merge, when there are new upstream changes, a new PR is made?

You could restrict a branch to require reviews, then a PR from Pull won't be merged until you review and approve it. After you do approve it, it's automatically merged (assuming the rest of the branch restrictions pass, such as CI), and a new PR is opened.

ah ok, so that'd be a github setting on the repo's default branch then. thanks!

Yeah, but doesn't have to be the default branch, just whatever branch Pull is merging to.

thanks!


Text: setting background color with multi-selection

Bug Description
When two texts are selected and one of these has "Fill" as the background mode and the other not, the background color setting is still displayed -- it is also changed for both text elements, however, it is only visible for the element which has "Fill" set.

Expected Behaviour
Not sure -- should the background color setting be hidden if not all the selected elements support it?
It should at least not change the default background color for the element that doesn't have "Fill" chosen.

Steps to Reproduce

Add two text elements
Set "Fill" as background mode for one
Select both elements.
Now change the background color/opacity
See only one element visibly changing
Now change the background mode to "Fill" for the other element, too
See the default background color had changed meanwhile.

Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

@o-fernandez Tagging you here since I'm not sure what should be the correct expected behavior from the product's perspective. Thoughts?

I think this is OK for Beta. We should wait to get user feedback before prioritizing a fix for this.

@miina  this feels relevant to the work on text prometheus is doing. I'm going to move it to prometheus but if that is wrong just pass it back.

@BrittanyIRL Yep, this is for Prometheus, thanks for tagging!


ASLR support

It only works with atlantiss's exe https://mega.nz/#!n4ghTJAR!VImp8xll_-v7F-oKuzPvr5b1unKGTHQ8QlafFe-RrOc

Thank you.  That is probably because they've disabled ASLR.  I may do another release with a fix to not require that.

List Of Servers Work ? For 3.3.5a and 4.3.4 cant find any server who works pls :D

Just go search and try yourself..

This should be resolved with version 0.4.  Release information here: https://github.com/namreeb/wowned/releases/tag/0.4

isn't working for me 0.4 in wow 4.3.4 with ASLR enabled

What do you mean by "isn't working"?  What happens when you try?

nothing, like the previous version
(Wow.exe never launch)


Simplify init_random() to remove QNX special-case

As it has both device entries and they provide the same functionality.
(I totally missed this when skimming the documentation, and it wasn't until today that I happened to notice the other device entry.)

Thanks for the cleanup.


Port changes from SIT.Manager

Decided to keep one source of this so it's a bit more organized in case there are more changes to the current manager before this is done.
The list of changes made to SIT.Manager and not ported to this version:

[x] https://github.com/stayintarkov/SIT.Manager/pull/32
[ ] https://github.com/stayintarkov/SIT.Manager/pull/31

I think my improvements already applied to the Avalonia project, because I do not see anymore bugs that I fixed before. There is only one thing to change is to make Window full screen.

I think my improvements already applied to the Avalonia project, because I do not see anymore bugs that I fixed before. There is only one thing to change is to make Window full screen.

Pretty much from the looks of it.


Connection Modal Styling

The connection modal styling is a bit basic. It could use some styling!
You can start by looking at the src -> renderer -> modals folder of new-dawn.

Related files: ConnectionConfigModal.tsx, ConnectionConfigModal.css


Model Weight

Hi, Do you intend to share model weight??
because we can do nothing !

Thank you for your interest. We are preparing an extended journal version of this work. As such, we are not releasing the model weights at this time. However, you can train the model yourself using the provided implementation.


CONTRIBUTING.md commit style convention link broken

The link to the angular style conventions in CONTRIBUTING.md returns 404.
Alternatives:

Angular's contributing.md, section git commit guidelines
Angular's google doc on the subject

Fixed it. Thanks for reporting!


Meeting expiration section has major problems

There are a few problems with this list:

There is no such thing as a "Regular" meeting. Would be better just to call it a Scheduled Meeting;
When you schedule a meeting, you can't create one with no end time.
Recurring meeting still have start and end TIME for each occurrence;
Recurring meeting can have no end "DATE"
On the extends of expiration, "each time you start" means you actually instantiate the meeting?
What is the meaning of "update a meeting" add/remove participants? Change meeting option? Change title/description?

There should be only three categories.

Scheduled meeting
Recurring meeting with no end date
Recurring meeting with end date

"Start time" on expiration should be anyone instantiate the meeting, i.e. the meeting is "STARTED"
I hope someone can clarify it if my understanding is wrong. But so far no one can create a "Regular with no end time" meeting.

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

ID: 905e2c09-ef3e-07cc-0809-6ff171157c47
Version Independent ID: c0d33162-183d-fff8-32e9-a999f391ea51
Content: Limits and specifications for Microsoft Teams - Microsoft Teams
Content Source: Teams/limits-specifications-teams.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@benjaminwchau Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@benjaminwchau thank you for reaching out. I see the article was updated yesterday with a few changes. I'm not seeing the instance of "update a meeting". Please can you provide clarity there.

I work for Microsoft, my office email is also bchau.
Do you want to talk about it? This is depressing to see one of our major document has so many problems. The relay section is still not changed at all. What is worse than giving customer bad information and doing in writing? Even worse, on the internet?
Regards,
Ben.

From: Lindsay @.>
Sent: Tuesday, April 6, 2021 12:19 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: benjaminwchau @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting expiration section has major problems (#6908)
@benjaminwchauhttps://github.com/benjaminwchau thank you for reaching out. I see the article was updated yesterday with a few changes. I'm not seeing the instance of "update a meeting". Please can you provide clarity there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6908#issuecomment-813888342, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJPG2M5Z2ZOLGVY5HG34MJ3THKYWRANCNFSM4ZWT3Y6A.

@benjaminwchau thank you. The team is continuously working to improve the Docs and we value your input.  I'm working through the article to see your recommendations for changing content and to see if anything has been changed so far to provide more clarity for users. The article was updated a few days ago. Please can you have a look again when you get a chance and let me know what you think and where more clarity can be provided.

A meeting URL will never stop working. The expiry only relates to any PSTN dial-in numbers and/or underlying meeting policies and settings.
This is a nice touch, not perfect, but at least pointing the right direction.
What is "Regular with no end time"?  What is regular, what is no end time?
Regular means what? Single occurrence meeting? Contrast to Recurring meeting?
Regards
Ben.

From: Lindsay @.>
Sent: Monday, May 24, 2021 1:32 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: benjaminwchau @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting expiration section has major problems (#6908)
@benjaminwchauhttps://github.com/benjaminwchau thank you. The team is continuously working to improve the Docs and we value your input. I'm working through the article to see your recommendations for changing content and to see if anything has been changed so far to provide more clarity for users. The article was updated a few days ago. Please can you have a look again when you get a chance and let me know what you think and where more clarity can be provided.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6908#issuecomment-846878303, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJPG2MZWMMGFGXY6GHO57RLTPIFIDANCNFSM4ZWT3Y6A.

@benjaminwchau Regular and recurring meetings with NO end time expire 60 days after the start time. Regular meetings with end time expire 60 days after the end time.  Recurring meetings with end time expire 60 days starting from the last occurrence. Hope this provides more clarity. Please let me know if you require further assistance or perhaps I should add this in a note in the article?  Let me know what you think.

The bottom line is there is no such thing as "Regular Meeting"! What is a Regular Meeting? Just a normal Teams Meeting created in Outlook or In Teams?
Try it yourself, can you create a meeting with no end time?
Why send me any email when you don't expect the return to get back? All these Noreply.github.com?
Regards,
Ben.

From: Lindsay @.>
Sent: Monday, May 31, 2021 2:15 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: benjaminwchau @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting expiration section has major problems (#6908)
@benjaminwchauhttps://github.com/benjaminwchau Regular and recurring meetings with NO end time expire 60 days after the start time. Regular meetings with end time expire 60 days after the end time. Recurring meetings with end time expire 60 days starting from the last occurrence. Hope this provides more clarity. Please let me know if you require further assistance or perhaps I should add this in a note in the article? Let me know what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6908#issuecomment-851348583, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJPG2M4AA56FVJN34CON7UTTQNHRVANCNFSM4ZWT3Y6A.

@SerdarSoysal please can you help provide clarity. Thanks so much.

[cid:de0a3356-45c4-4321-ab4f-7a806eb5106e]

The top note is a good touch. My suggestion should be "A meeting URL will never stop working. The expiry only related to any PSTN dial-in Number, CVI joining, and/or underlying meeting policies, settings, files uploaded to the meeting.
On Regular Meeting Type
*   Can someone clarify what on Regular Meeting? A simple meeting? There is no definition of "Regular Meeting" within Teams.
*   I can see the document have Regular with no end time and with end time. How can any (Regular or Recurring) meeting have no end time? The recurring can have no end time, but each occurence have to have Start time and End time.
I can only see the meeting type has
*   Meet Now
*   Single occurrence Meeting
*   Recurring meeting with no end time
*   Recurring meeting with end time

Please include my Microsoft email address too. And I am more than happy to join a call to discuss the detail. This is a very confusing section in our communication with the customer.
Regards
Ben.

From: Lindsay @.>
Sent: Tuesday, June 1, 2021 1:07 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: benjaminwchau @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting expiration section has major problems (#6908)
@SerdarSoysalhttps://github.com/SerdarSoysal please can you help provide clarity. Thanks so much.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6908#issuecomment-851920458, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJPG2M67HGC4G3I5X4DSTFLTQSIKTANCNFSM4ZWT3Y6A.

@benjaminwchau thanks for the response. I'm discussing with the team. Regarding the email addresses, all messages/comments here go directly to your email address by default, as well as anyone else who comments here, so the comments will appear here as well as in you Inbox.

@benjaminwchau Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


ACSE Won't Open Menu as Shown in Screenshots

Hello. I'm sorry if this is the wrong place to ask this question.
My SLN file opens in Visual Studio rather than in the separate program like it could a year ago. The icon also no longer shows, with no way for me to put in my GCI information. My Visual Studio version is 2019. I am mostly looking for a way to open this and have it run like normal, and get a screen that looks like the first image from the second. Thanks.

Yeah, I was also stuck with this problem but I figured it out
The main page shows the master build which is a visual studio file, you need the actual executable which is right here
Then download the first asset at the bottom of the page
Hope that helps!


bug:

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

Script Version
FUT AutoBuyer 1.3.5 And All previous versions
Platform
Android
Current Behavior
Not showing the price of Futbin or Futwiz
please fix this bug.....
Android - KIWI Browser / Alpha Browser
All previous versions have the same problem
Expected Behavior
...
Steps to Reproduce
...
Additional Information
....

No plan to support KIWI Browser / Alpha Browser.
Either use chrome in desktop or use FUT Market Alert app


The encoding of response from API is unicode

Response header:
Content-Type: text/html; charset=utf-8

Response body:
{"ret":0,"msg":"401 \u90ae\u7bb1\u6216\u8005\u5bc6\u7801\u9519\u8bef"}

这个 API ，还真没看过怎么用

uni2ascii package should be used.
Take Ubuntu & Debian for instance:
$ sudo apt-get install uni2ascii

Here is an example of uni2ascii:
$ echo 'Character 1: \u0144, Character 2: \u00f3' | ascii2uni -a U -q
Character 1: ń, Character 2: ó

It is a workaround.


sendTransaction() should accept only 1 private key

Description
Sending a transaction using sendTransaction function by the omg-js library currently takes an array of private keys causing Uncaught (in promise) Error: Number of non-empty inputs should match signatures count. Remove redundant signatures issue. This happens because a function doesn't know how many UTXOs it will use since it is calculated internally.
Changing the fromPrivateKeys property from an array into a single private key should make things work.

curious: was this initially in place for support of multisig wallets?


Add bigint serializer

Adds a serializer for BigInt values. It stores them as strings, so it should be lossless.

Uh, this is more a piece that needs to be core so we can serialize/deserialize bigints.

Oh. Do you concur @bdistin?


Settings validator related to detailed cycles input being raised incorrectly

It appears that anytime one uses the detailed cycles settings (see #637 ), a validator is raised:

This is raised even if your input does not actually contain any of the mentioned offending settings.
This incorrect validator should be either fixed, or possible removed. I am inclined to believe that it might not be possible to fix... We'll see.

Nah, I'll work on it today. Sounds like a good change of pace.
On Thu, Sep 22, 2022, 6:34 AM John Stilley @.***> wrote:

I can grab this one, if you need.
—
Reply to this email directly, view it on GitHub
https://github.com/terrapower/armi/issues/838#issuecomment-1255033961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFHRHMHEUHZMQLXWIGKXHO3V7RN45ANCNFSM56NHSA6Q
.
You are receiving this because you were assigned.Message ID:
@.***>


Make StackOrganiser extendable

Add virtual keyword to the Organise method  so the class can be extended with custom sorting of the items.
Provide mechanism to force reorganisation when items needs to be sorted. @ButchersBoy suggested calling InvalidateMeasure which I guess would work but it would be nice to have a solution that works with MVVM as well.
@ButchersBoy:

Override Organise and sort the items and pass to the base. Then you could InvalidateMeasure on the control itself....maybe i could add a routed event or something to "invalidate" the current sort which might make it easier in the future.

Extendable changes made.
I am considering enhancing the position monitor (mentioned in https://github.com/ButchersBoy/Dragablz/issues/82) to provide some bi direction communication.
This could become more of a PositionController, am currently weighing this up.


[A2-763] Hide "Access Management" on sidebar

:nut_and_bolt: Description
Previously, if logged in as an "Editor" on 2.0, we were seeing the "Access Management" title in the sidebar without any subcategories.
With this change, an Editor does not see the title on 2.0. However, on 2.1, the editor can see both the title and "Projects" underneath.
On 2.0:

On 2.1:

ℹ I'll rebase out of politeness and merge this when green.


How to alter horizontal and/or vertical spacing between facets in ggplot2?

This question was originally asked on SO here and here
ggplot2 has the ability to change the margins between a faceted plot using the argument panel.margin in opts. This seems to change both horizontal and vertical spacing. Is there a way to change the spacing of either horizontal or vertical without changing the other?
library(ggplot2)
# dummy data
mtcars[, c("cyl", "am", "gear")] <- lapply(mtcars[, c("cyl", "am", "gear")], as.factor)
# create the plot
example <- ggplot(mtcars, aes(mpg, wt, group = cyl)) +
  geom_line(aes(color=cyl)) +
  geom_point(aes(shape=cyl)) +
  facet_grid(gear ~ am) +
  theme_bw()
# visualize the plot
example + theme(panel.spacing.x=unit(2, "lines"))

See the Plot

Solution # 1
To expand both vertical and horizontal spacing in grid, use panel.spacing
example + theme(panel.spacing=unit(2, "lines"))
To expand ONLY the vertical spacing between columns in a grid, use panel.spacing.x()
example + theme(panel.spacing.x=unit(2, "lines"))
To expand ONLY the horizontal spacing between rows in a grid, use panel.spacing.y()
example + theme(panel.spacing.y=unit(2, "lines"))


feat: Trigger CEC onboot on Bluetooth device connection

Added a new udev rule which is triggered when a Bluetooth device is connected. It calls /usr/bin/cec-control onboot, same as cec-onboot.service, should set the TV's input source to Bazzite. Useful when you just grab the controller and turn it on to start gaming.

This is really cool, thank you


Option to bypass i18n question prefix.

I've found the i18n "question" format doesn't work when I'm not requesting a user input.  Say I want to step through the shared folder and ask the user whether or not it should be uploaded, you might have:
set :ask_upload, ask("Do you wish to upload folder x", 'y')
$ask = fetch(:ask_upload)
if ($ask == 'y') ...
Which gives you Please enter Do you wish to upload folder x (y):
For a better format and more flexibility with the question text (essentially getting rid of the prefix "Please enter " without modifying i18n.rb).  You can now use;
ask(:ask_upload, 'y', {text: "Do you want to upload x (y): "}
if (fetch(:ask_upload) == 'y') ...
I'm hope you understand what I'm trying to achieve, I did think about modify the i18n file but the impact would be too huge.

In principal I think I could live with this change.
Please have a look at the tests and ensure this behaviour is tested, and also review the contribution guidelines and see how to make this into a PR that we can accept, and we'd be more than glad to merge it.

Hi @simon-soak, this a good improvement. Thanks for the PR.
I want to suggest a few changes to your implementation:

Your test? method serves dual purpose as both a predicate and as an accessor. I think this is a little confusing.
Also, test? is never used outside the question method, so I think it is an unnecessary abstraction.
I assume that both nil and false values for the :text option should result in the default i18n behavior. If that's the case, then fetch(:text, false) is redundant and you can just use [:text].

How about this:
def question
  custom_text = (options || {})[:text]
  return custom_text if custom_text
  I18n.t(:question, key: key, default_value: default, scope: :capistrano)
end

Further, I think the (options || {}) check repeated in this class is a code smell. Maybe you can change the initialize method to fix the nil problem there instead? Then we won't need those repeated checks.
def initialize(key, default, options={})
  # ...
  @options = options || {}
end

Finally, I would appreciate it if you could also:

Add a test for this new behavior to question_spec.rb.
Update CHANGELOG.md with a bullet point describing this new feature.

Thanks!

Thank you both for the feedback.  I've actioned your points and amended my initial commit.
Ruby is not my principle language, so I have absolutely no idea where to start with question_spec.rb tests.  If you could advise or take off my hands that'll be grand.

My RSpec is also a bit rusty, but I think this will be a good test:
--- a/spec/lib/capistrano/configuration/question_spec.rb
+++ b/spec/lib/capistrano/configuration/question_spec.rb
@@ -15,6 +15,28 @@ module Capistrano
         end
       end

+      describe "prompt" do
+        before do
+          $stdin.expects(:gets).returns("")
+        end
+
+        context "without :text option" do
+          it "uses i18n" do
+            $stdout.expects(:print).with("Please enter branch (default): ")
+            question.call
+          end
+        end
+
+        context "with :text option" do
+          let(:options) { { text: "Custom prompt: " } }
+
+          it "uses :text value" do
+            $stdout.expects(:print).with("Custom prompt: ")
+            question.call
+          end
+        end
+      end
+
       describe "#call" do
         context "value is entered" do
           let(:branch) { "branch" }

@simon-soak If you're still interested in finishing this PR, and you need further assistance, let me know!

Morning @mattbrictson, apologies for the hold up.
I've managed to get some more time on this, and implemented (copy/pasted) the rubocop code into question_spec.
However; on running of rake rubocop it's thrown up some offenses "no-nested-conditiontals" on;

features/support/vagrant_helpers.rb:28:5:
lib/capistrano/configuration/validated_variables.rb:94:9:
lib/capistrano/version_validator.rb:8:7:

I'm pretty sure I didn't get this last time, so I imagine rubocop has been updated, anythoughts?

@simon-soak yeah, Rubocop is a moving target, you can safely ignore any errors that were there before your changes based on rubocop HEAD, and we'll eventually clean them up

@simon-soak RuboCop is working in master, so if you could rebase your PR against master and resolve any conflicts, that should clear up those RuboCop offenses and allow us to merge this PR. Thanks again!
If you'd like me to handle the rebase, let me know.

Awesome, I should be getting more time on this this Friday or next week.
Feel free to do your thing, if you'd rather, I've ticked the "Allow edits from..." box.

@simon-soak: Are you able to rebase this?

I just pushed a rebase. Is there still interest?


Promote Compiler2, Remove old compiler

This is the final push to replace our original AST-manipulating compiler with the new IR-based one.

When I started writing the src/*.rb files with the new compiler, some new bugs were exposed. :sweat_smile: I'll work on getting those fixed up in this PR and merge when all the tests pass...


Voting down against feature creep

Many users like simple apps and I wonder, if it'd make sense to add down voting.
Currently, if something doesn't get as many votes it's perhaps a less prioritized feature. But there's no way for users to express their concern that this adds too much complexity etc. Over time an unpopular feature still may collect enough votes by a minority of users even if the majority of the users would be strongly against it.
This would be a mechanism against feature creep.
Maybe it's better to use separate counts then to differentiate +10 -10 votes too see a controversial feature vs a 0 votes summed count (looks like nobody cares).
What do you think?

I'm curious about your reasons or what makes you concerned, if you don't mind sharing. It's good to get another perspective.

I prefer to have the votes represent an absolute number of users instead of an outcome calculation of minus and plus. If at all, I'd prefer to have upvotes and downvotes separated visible as a middle ground. Does that make sense?

I'd also have that separate. Just like YouTube has a likes count and dislikes count. Because a very controversial feature could just end up with something close to 0 then. It's better to keep it distinct. I agree on that.


[WIP] [api] Adding support for service reconfigure

- Adding resource action specific option :validate_action
- Added service model validate_reconfigure method
- Updated action spec rendering to support action validation on resources
- Adding the services resource reconfigure action
- Adding rspecs

Trello: https://trello.com/c/WRRgX50P

Marked as WIP

Needs more testing
Needs rspecs

@h-kataria could you please kick the tire.
The "reconfigure" action is not returned with services collection as it is resource specific.  For services that are reconfigurable, it will be a regular action returned as such:
{
  "href": "http://localhost:3000/api/services/2",
  "id": 2,
  "name": "SampleStaticServiceCatalogItem",
  "description": "Sample Static Service Catalog Item",
  "guid": "f61ab852-da6d-11e5-a890-000a27020067",
  "service_template_id": 2,
  "options": {
    "dialog": {
      "dialog_SampleTextName": "default",
      "dialog_SampleHostName": "sample.host.name",
      "dialog_SampleHostIp": "100.200.300.1"
    }
  },
  "display": false,
  "created_at": "2016-02-23T20:42:32Z",
  "updated_at": "2016-02-23T20:42:32Z",
  "evm_owner_id": 1,
  "miq_group_id": 2,
  "tenant_id": 1,
  "actions": [
    {
      "name": "edit",
      "method": "post",
      "href": "http://localhost:3000/api/services/2"
    },
    {
      "name": "retire",
      "method": "post",
      "href": "http://localhost:3000/api/services/2"
    },
    {
      "name": "set_ownership",
      "method": "post",
      "href": "http://localhost:3000/api/services/2"
    },
    {
      "name": "reconfigure",
      "method": "post",
      "href": "http://localhost:3000/api/services/2"
    },
    {
      "name": "delete",
      "method": "delete",
      "href": "http://localhost:3000/api/services/2"
    }
  ]
}

Reconfiguring a service is simply the post with the updated fields:
{
  "action" : "reconfigure",
  "resource" : {
     "SampleText" : "default_11",
     "SampleHostIp" : "100.200.300.11"
  }
}

Standard action signature returned, i.e.:
{
  "success": true,
  "message": "Invoked Service Reconfigure dialog for Service id:2 name:'SampleStaticServiceCatalogItem'",
  "href": "http://localhost:3000/api/services/2"
}

Let me know how this works for you and if you need any changes made.
Thanks,

@h-kataria fixed the validate_reconfigure method as discussed. Also, updated the app helper toolbar builder to use the model method instead. Let me if this works better.
@imtayadeway @gtanzillo please review, added specs, will un-wip once I know it works well for @h-kataria. Thanks.

@abellotti previously reported issue has been fixed by latest changes, PR looks good so far.

@abellotti LGTM. Minor/non-blocking comment above

LGTM :+1:


Can not set custom headers when post with form data

I found that when using:
request({
url: "xxxx",
method: "POST",
formData: xxxx,
headers: { "Content-Type": "application/json"},
}, function(error, response, body) {
// handle response here
});
The content type is still "multipart/form-data", can not be set.

Your either using formData that does mulltipart's, or your not.
If you don't need multipart, then use form instead, not formData.

When I am trying to do similar type of request, I am getting error as "The exception message is 'The incoming message has an unexpected message format 'Raw'. The expected message formats for the operation are 'Xml', 'Json'."
Please help me around...

request({
url: "xxxxx",
method: "POST",
body: formData,
json: true,
headers: { "Content-Type": "application/json"},
}, function(err, response, body) {
if (err)
resolve({"message": err});
else
resolve({"message": JSON.stringify(body)});
});
Worked for me, give a try...
May fix your issue also...

@KpjComp you didn't get the point of the problem. The header will change to 'application/x-www-form-urlencoded' if use key 'form'. My problem is when you make such request, you can not set custom headers

@HarshaVardhanPVK I use the key 'formBody' in request and finally set the custom header 'Content-Type' to value 'application/json'. Your solution bring exceptions for me. But thank you anyway.


refactor(generator): use new Options

This change is

FYI, as of https://github.com/googleapis/google-cloud-cpp/pull/6042 (merged) the Options are now public.


Update: Use autocomplete="new-password"

Description
Having some issues with Chrome trying to be helpful and trying to autocomplete on our multiselect
Proposed Changes

autocomplete="new-password" to really suggest that the browser does not try to autocomplete

License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

This won't cause chrome to suggest a password for our input fields will it?

I'm not seeing any weird behavior locally with new-password on chrome/firefox/safari


how to use modal in django-bootstrap3

I can't use bootstrap modal ,when i use django-bootstrap3

Did you include the Javascript?

Op 16 jan. 2017, om 06:16 heeft allen_code<EMAIL_ADDRESS>het volgende geschreven:
I can't use bootstrap modal ,when i use django-bootstrap3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/dyve/django-bootstrap3/issues/358, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFBi04Z15acw-xUrEiCKILku9JRbR9cks5rSv01gaJpZM4LkL81.


Expose public API for providing BackOffPolicies

As discussed here, we'd rather expose the BackOff generation logic we use for the RetryableTopics feature as an API  than duplicate it in Spring Boot for auto configuration.
I should have a PR for this soon if that's ok.
Thanks.

Closed in favor of Spring Retry #276.


feat: add an additional Caddyfile config template to the existing template

This could be a potential fix for #2 , not sure if you all would prefer to add to the existing template, or replace it altogether. There could be separate env var for each option. What do you think of these changes? (explanation in README changes)

I could also add a CADDY_FILE envvar that will replace the default Caddyfile.tmpl in a similar manner to how CADDY_SNIPPET is appended to the default Caddyfile. So there would be two options for custom templates: CADDY_FILE which will replace the default template, and CADDY_SNIPPET which will append to the existing template. Unfortunately, I do not think it's easy to support adding multiple snippets.

I'll think of a way to test, I'll updated the .travis.yml file

@sobolevn I rebased with master and added tests to the CI, any feedback is welcome.

Looks like I broke something 😢

Looks good I think we can merge, thank you for the feedback @sobolevn . I will update docs today for #52 demonstrating how to set up a file_server with the new options, then rebase, and add a feature to include snippets using container labels. We should be good to release after that.


MySQL error on syslog

Jun  5 08:35:06 Userver mysqld[23060]: 2017-06-05  8:35:06<PHONE_NUMBER>93120 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE queued_messagesSETqueued_messages.locked_by= 'host:Userver pid:6564 procname:worker.5 job:VU33AGB4HY',queued_messages.locked_at= '2017-06-05 08:35:06.648159' WHERE (retry_after IS NULL OR retry_after <= '2017-06-05 08:35:36.648221') ANDqueued_messages.batch_key= 'outgoing-domain.com' ANDqueued_messages.ip_address_idIS NULL ANDqueued_messages.locked_byIS NULL ANDqueued_messages.locked_at IS NULL LIMIT 100
I don't know if it's important, but I share just in case

Are you replicating your database?
You probably want to change your binlog format if so.

No, I just run the quick install. It installs MariaDB, I didn't touch
anything
2017-06-05 12:20 GMT+02:00 mattmartincouk<EMAIL_ADDRESS>
Are you replicating your database?
You probably want to change your binlog format if so.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/atech/postal/issues/213#issuecomment-306154456, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEf7wzmyO5FZQlvTLAM00aGAR_RgRuQGks5sA9Z-gaJpZM4Nvx-A
.

This is only important if you implement database replication. I don't think the installer touches the database configuration, so this is probably out of scope for now. Thanks for the note though, will consider it when writing any clustering documentation.

The thing is that you get one warning per email sent. not important, but not elegant either.


java.lang.NoClassDefFoundError: mcmultipart/block/BlockMultipartContainer

hi, i installed the correct versions of forge and mekanism, but still MC crashes. I've treid 1.7.10 first, that seemed to work at first, but crashed later. 1.9.4 crashes already when I attempt to launch.
I've attached the crash report.
crash-2016-08-13_20.41.32-client.txt

Install McMultipart.


Product Hunt icon

Can you please add this one? Thanks a bunch.
https://fontawesome.com/v6.0/icons/product-hunt?s=brands

This one's already in there (you can view the full icon list here—were you having trouble getting it to appear? I might need to tweak the domain setting, so let me know what's going on there.

Sorry, somehow missed it. I removed the "www" and it's now showing. Solved, thank you.

Ah, I need to make this work regardless of whether the www is there or not. Will tackle that soon!


Allow to set cache dir in config file

Use case:
I'm using pygments, so after every reboot, hugo re-runs pygments for every code snippet in any page of the blog, which takes quite some time.
Granted, I could set TPMDIR before running hugo, or use the command line flag, but I find it convenient to just have cacheDir = cache in the config file.
(And of course a matching entry in my blog's .gitignore)
Going further, maybe this could be the default?

This sounds like a rare problem.
Have you tried to set a value for CacheDir in your config (or as HUGO_CACHEDIR env var)?

Your implementation is buggy. Please correct it and I will merge.

Oups you're right. Using --cacheDir from the command line was no longer working.
Fixed :)


Add support for formatting currency rates (ex: $/km)

Currently, Intl.NumberFormat supports compound units formatting, like:
new Intl.NumberFormat('de-DE', { style: 'unit', unit: 'liter-per-kilometer' }).format(12);
//output: "12 l/km"

However, it misses support for formatting currency rates, like: $/mi, €/km, etc.

Hi, can you file this issue on https://github.com/tc39/ecma402/issues?
I do not believe there is CLDR data for currency rates.  That would need to be obtained first before it could be added to ECMA-402.


Latest lab helm chart not installing on rancher desktop

Of course this may be an issue with my environment but haven't seen this error before so thought I would document. I loaded latest helm charts and tried to install and got:
helm  install -f ./egeriaConnectors.yaml lab egeria/odpi-egeria-lab --set service.type=NodePortl --set jupyter.tokenSecret=jupyter-lab-secret
Error: INSTALLATION FAILED: cannot re-use a name that is still in use

Not sure what name is already in use or how to clear it...
I tried to install base with a simpler command and got a bit more output:
dwolfson@Lazurus egeriaConnectors % helm install base egeria/egeria-base --set service.type=NodePortl
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "strimzi-cluster-operator" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "base": current value is "lab"

Ok - the first error is because the name lab was still around - this seems to be a new behavior? I deleted it and reran - I also had to re-adjust the resource settings for rancher - seem to have gotten lost after I did an update.
Still getting a weird error..not sure why
dwolfson@Lazurus egeriaConnectors % kubectl logs lab-odpi-egeria-lab-core-0
Defaulted container "egeria" out of: egeria, init-connector (init)
Error from server: Get "https://<IP_ADDRESS>:10250/containerLogs/default/lab-odpi-egeria-lab-core-0/egeria": x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, fec0::5055:55ff:feba:e739, not <IP_ADDRESS>

Suspect that this is related to rancher - was able to get helm chart running on linux box.

The first error is caused by reusing the name of the 'release' - in your example it was 'lab'. In theory you can have multiple named releases in the namespace - but I can't promise I've tested that recently. I would recommend you do one 'release' (that's the helm name) per namespace
The second error is caused by trying to install a second instance within the cluster (whether same namespace or not) due to the way strimzi creates cluster wide resources. This is covered at https://egeria-project.org/guides/operations/kubernetes/charts/overview/?h=strimzi#strimzi-permissions-and-co-existance .
It is probably worth adding the example error in the docs as an example to help with search?

The final error you posted - from when you issue kubectl - indicates a problem with connectivity to the api server. That's going to be down to your chosen implementation of k8s and local configuration/networking. It's not anything to do with egeria, it's infra setup.

Thanks - I think I straightened out most of my network issues (does perfection exist?) and the base charts install properly as expected. With the labs charts (on my Mac) all pods start as expected except Jupyter - which gives the error:
dwolfson@Lazurus egeriaConnectors % kubectl logs lab-odpi-egeria-lab-jupyter-7ccddf9ccb-j7hzs Error from server (BadRequest): container "jupyter" in pod "lab-odpi-egeria-lab-jupyter-7ccddf9ccb-j7hzs" is waiting to start: CreateContainerConfigError
The labs charts start properly on my Linux box..

Can you do a kubectl describe pod lab-odpi-egeria-lab-jupyter-7ccddf9ccb-j7hzs or similar -- we need to find out what is the reason behind that error.
Most likely, you have configured jupyter to use a secret, but have not defined the secret. K8s is therefore going to tell you in the 'describe' that it's missing the secret it needs to run the pod........ ;-)


Cannot form nested join query, incorrect error rendered

Version: 0.13.4
Module: quill-jdbc
Database: postgres
Expected behavior
The following expression:
val fooWithLatestBar =
  quote {
    query[Foo]
      .filter(_.category == lift("some category"))
      .filter(_.active)
      .leftJoin {
        query[Bar]
          .map(logs => (logs.fooId, logs.createdTime))
          .groupBy(_._1)
          .map {
            case (id, history) =>
              (id, history.map(_._2).max)
          }
      }
      .on(_.id == _._1)
  }

Should generate the following query:
select foo.*, bar.update_time
   from foo
   left join (
      select foo_id, max(created_time) as update_time
      from bar
      group by foo_id
   ) as simplified_bar
   on foo.id = simplified_bar.foo_id
where
   foo.category = "some category"
   and foo.active

Actual behavior
java.lang.IllegalStateException: A 'groupBy' clause must be followed by 'map'.
Which is incorrect, because there is a call to map immediately following groupBy.
Steps to reproduce the behavior
The issue can be reproduced using a mirror context using this scastie snippet.
Workaround
Use .nested on the Bar sub-query, resolves the issue but the error message is misleading.
@getquill/maintainers

I think adding .nested resolved the issue, but the resulting query was incredibly slow anyhow.


os_info crate

Using the os_info create prevents to build docker images from scratch.
As far as I can see it is only for building a user_agent String. This can
be done in an other way, or make this via a feature configurable.

What os_info are you referring to?


lib_strftime: Fix %I to avoid printing 00:xx AM/PM

Summary
Currently strftime is printing 00:00 AM and 00:00 PM instead of 12:00 AM and 12:00 PM when using %I.
This commit fixes this issue
Impact
Users will get time format correct in USA (those Imperialist hehehe)
Testing
SIM

Fun thing: https://www.theverge.com/2019/6/25/18693533/metric-system-measurement-us-conversion-act-verge-science


[WIP] add timing for velox shuffle reader

What changes were proposed in this pull request?
Some jobs of ours consume most of their time for the operator of ColumnarExchange, and the metrics of VeloxShuffleReader don't contain IO(IPC read) and deserialize steps.
So I proposed this PR to complement these missing metrics.
(Please fill in changes proposed in this fix)
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@kecookier Could you finish this PR according to the comment of TODO zhaokuo, please!

@kecookier @zuochunwei Would you remove "WIP" from PR title?

@kecookier @zuochunwei Would you remove "WIP" from PR title?

Done

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_3254_time.csv
log/native_master_09_24_2023_e7152a05a_time.csv
difference
percentage

q1
43.56
43.08
-0.483
98.89%

q2
24.59
24.37
-0.222
99.10%

q3
38.30
36.77
-1.527
96.01%

q4
41.02
41.00
-0.020
99.95%

q5
67.98
70.15
2.173
103.20%

q6
6.25
5.11
-1.147
81.67%

q7
86.50
86.15
-0.349
99.60%

q8
80.44
78.81
-1.625
97.98%

q9
116.90
115.81
-1.087
99.07%

q10
47.54
46.15
-1.389
97.08%

q11
20.72
19.57
-1.146
94.47%

q12
26.15
25.39
-0.755
97.11%

q13
48.76
50.31
1.554
103.19%

q14
18.36
19.95
1.588
108.65%

q15
34.41
30.64
-3.765
89.06%

q16
15.76
16.03
0.269
101.71%

q17
120.04
120.09
0.050
100.04%

q18
160.83
164.22
3.390
102.11%

q19
12.13
12.51
0.381
103.14%

q20
27.15
30.33
3.183
111.73%

q21
233.77
238.20
4.436
101.90%

q22
15.80
15.33
-0.474
97.00%

total
1286.95
1289.98
3.035
100.24%


Folder template returns a map instead of an array

https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/blob/6f99a46c25d2343f440306385c9f802b3304207a/dm/templates/folder/folder.py.schema#L111
The schema states incorrectly the returned output. folders is a map, not an array.

vice versa, the schema incorrectly states it is an array, but it is a map


Description page does not load images

When I open Description in a pull request, the images don't load in VS code.

Extension version: 0.0.25
VSCode Version: 1.69
OS: Windows 10

Steps to Reproduce:

Launch the extension
Open a pull request
Navigate to the description tab
It appears like this:

same over here.

Anyone found a solution for this? :-)


Support Yarn v3

We can no longer use dependabot because it does not support yarn v3 (or v2).
Do you have any plans to support v3?
Can you suggest a workaround?
Thank you.

This is a duplicate of #1297.

Following instructions for Yarn's v2 upgrade, which I did shortly after https://github.com/dependabot/dependabot-core/issues/1297 was released, actually upgrades to the latest Yarn version, not v2 (specifically yarn set version berry, which currently installs v3.2.4). Further, when committing that, dependabot doesn't throw an appropriate error or warning. Instead, it silently stops creating PRs because every dependabot run times out ("timeout running job"). (@jurre, FYI it's easy to accidentally create this situation, since it seems like something that's very easy to run into and I suspect will be reported by others soon.
Also, it turns out yarn v2 only supports up to typescript 4.4[1] when linking to node_modules (that is, no PnP[2]), so this means that, in this situation, dependabot does not support typescript > 4.4. Yarn v3 has more patches[1] and, if the patch doesn't work, it at least doesn't block the install.
Personally, I only figured out I was on an unsupported Yarn v3 when I came to file an issue that Yarn v2 support was timing out dependabot. Now I'm trying to roll back to Yarn v2, and I'm having to downgrade Typescript to an older version, when the latest version of typescript is supported in both Yarn v1 and v3.
[1] Note that trunk yarn has patches for later versions; these just aren't backported, because (before this dependabot restriction) I imagine everyone could just upgrade to Yarn 3. https://github.com/yarnpkg/berry/blob/master/packages/plugin-compat/extra/typescript/gen-typescript-patch.js#L93
[2] And unfortunately, some tools, like Nuxt, don't yet support PnP.

Actually, Yarn v1 seems generally much better supported than v2, where everyone has moved to v3. So the current dependabot support requires several sacrifices.
Beyond typescript, above, yarn plugin import breaks on Yarn v2:
% yarn plugin import interactive-tools
➤ YN0000: Downloading https://github.com/yarnpkg/berry/raw/master/packages/plugin-interactive-tools/bin/%40yarnpkg/plugin-interactive-tools.js
➤ YN0001: HTTPError: Response code 404 (Not Found)
    at se.<anonymous> (.../.yarn/releases/yarn-2.4.3.cjs:23:10082)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
➤ YN0000: Failed with errors in 0s 624ms

Following instructions for Yarn's v2 upgrade, which I did shortly after #1297 was released, actually upgrades to the latest Yarn version, not v2 (specifically yarn set version berry, which currently installs v3.2.4). Further, when committing that, dependabot doesn't throw an appropriate error or warning. Instead, it silently stops creating PRs because every dependabot run times out ("timeout running job"). (@jurre, FYI it's easy to accidentally create this situation, and I suspect others will be reporting it soon.
Also, it turns out yarn v2 only supports up to typescript 4.4[1] when linking to node_modules (that is, no PnP[2]), so this means that, in this situation, dependabot does not support typescript > 4.4. Yarn v3 has more patches[1] and, if the patch doesn't work, it at least doesn't block the install.
Personally, I only figured out I was on an unsupported Yarn v3 when I came to file an issue that Yarn v2 support was timing out dependabot. Now I'm trying to roll back to Yarn v2, and I'm having to downgrade Typescript to an older version. Frustratingly, the latest version of typescript is supported in both Yarn v1 and v3.
[1] Note that trunk yarn has patches for later versions; these just aren't backported, because (before this dependabot restriction) I imagine everyone could just upgrade to Yarn 3. https://github.com/yarnpkg/berry/blob/master/packages/plugin-compat/extra/typescript/gen-typescript-patch.js#L93 [2] And unfortunately, some tools, like Nuxt, don't yet support PnP.

Dependabot support Yarn v3 (https://github.blog/changelog/2022-10-20-dependabot-can-now-generate-security-and-version-updates-for-yarn-v2-and-v3/), if you have any issues with it, it probably would be a good idea to make a separate issue for it.

Oh interesting, I thought it was only Yarn v2. Thanks!

Closing as we now support Yarn v3, as mentioned ☝.


⚠ Secret-Cinema has degraded performance

In fe63e75, Secret-Cinema ($SC) experienced degraded performance:

HTTP code: 502
Response time: 1247 ms

Resolved: Secret-Cinema performance has improved in cb195ee after 1 hour, 3 minutes.


Updating to 2.1.4 dotnet core sdk

This raises an interesting question - should those SDK upgrade be also automatically flagged and PRs created?


refactor(EMI-1691): rewrite Email PreferencesApp tests

The type of this PR is: refactor

@artsy/emerald-devs
This PR solves EMI-1691
Description
The existing tests in the Email Preference Center lack coverage and fail to test user opt in/out of email actions. I removed some tests and updated the spec with new tests that correctly cover user behavior.

Looks great! You may need to run yarn relay and commit the generated file changes, as well as remove the unused imports to get the CI tests to pass.

ah okay so I should commit the generated graphql query file into this PR as well?


Work remotely with PyCharm, TensorFlow and SSH

https://medium.com/@erikhallstrm/work-remotely-with-pycharm-tensorflow-and-ssh-c60564be862d

ssh端口转发
ssh -N -L


$db - Field Naming - Content

Just got caught, I created a new module and named a $db field 'Content' this sent the SS_Viewer templating engine into a tail spin.

Hi @mspacemedia, can you please provide the versions of SilverStripe and this module that you're using?

From what I've gathered on slack, this is an SS3 site. And since Widget has a Content method that renders the template, it'll render recursively, as soon as you put $Content into your block template.
So this is actually more of a framework issue with Widget and we can all agree that using Content as method-name was a poor choice.

Indeed bummzack I would have to agree that Widget should be shot for causing the recursion issue!


ld: framework not found FirebaseAnalytics

I am getting the following error while building in Xcode
ld: framework not found FirebaseAnalytics clang: error: linker command failed with exit code 1 (use -v to see invocation)
I am using Fuse .32, has something changed?
I remember being able to get it working.

+1. I can't even download the pods
$ [!] The Podfile does not contain any dependencies.

@LuisRodriguezLD Yes, definitely something in version <IP_ADDRESS> changed that affects it. I rolled back to 0.31.2 and it all works fine now.
@cbaggers Any idea when you'll have time to make and update?

grr Testing with latest internal code seems to work fine..that wasnt very illuminating. I'll install 0.32.0 and have another go

Ahah, yeah I get the same error with version 0.32. It sounds like it's fixed internally then. But the question of why this happened is still there.
When building with 0.32 I got.
[!] Please close any current Xcode sessions and use `AuthExample.xcworkspace` for this project from now on.
Sending stats
Pod installation complete! There are 7 dependencies from the Podfile and 16 total pods installed.

[!] The `AuthExample [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-AuthExample/Pods-AuthExample.debug.xcconfig'. This can lead to problems with the CocoaPods installation

[!] The `AuthExample [Release]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-AuthExample/Pods-AuthExample.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

The Please close any current Xcode one is perfectly normal for cocoapods, so no worries there.
However the next 2 warnings are likely the cause of the problem. Very strange. I'll go see what git says we have been changing recently

AHAH! we found it. The best news is you don't have to do anything to fix it except use the next release (when it's out).
The issue was that we had this section in the project.pbxproj

AHAH! we found it. The best news is you don't have to do anything to fix it except use the next release (when it's out).
The issue was that we had this section in the project.pbxproj
#if @(Pbxproj.FrameworkDirectories:IsSet)
                FRAMEWORK_SEARCH_PATHS = (
                    @(Pbxproj.FrameworkDirectories)
                );
#endif

So if a library was included during the uno build then the search paths would be set. CocoaPods was fine as usually this was false (and cocoapods runs after the uno build is finished).
However we now always include the jetfire framework (to enable websockets), which means @(Pbxproj.FrameworkDirectories:IsSet) was true and so we were overriding the FRAMEWORK_SEARCH_PATHS variable.
We noticed this internally (after 0.32 shipped) and changed the above section to
#if @(Pbxproj.FrameworkDirectories:IsSet)
                FRAMEWORK_SEARCH_PATHS = (
                    "$(inherited)",
                    @(Pbxproj.FrameworkDirectories)
                );
#endif

That $(inherited) bit keeps CocoaPods and Uno playing nice together.
This is in the next release, so now we wait (and use 0.31 until it's out)
Sorry for the inconvenience.

decided to reopen this until the new fuse release ships so others can see the issue

@cbaggers Thanks for having look at this and the update!

Closing as has been released for a while. Feel free to reopen if you run into the issue again


The old code did a linear scan of all the reflection info on each lookup, throwing away the information it got about the stuff it scanned over on its way to what it was looking for. When looking up lots of different things, this results in a lot of wasted time and bad performance.
This change stores the scanned info into a cache which can be used for subsequent lookups. It also scans to the end even when the target is found somewhere in the middle, to make it more likely that subsequent lookups will be cached.
rdar://problem/40705238

@swift-ci please test

LGTM