10.0.0-beta1: $simpleNodeFinder in __construct() not found

just in case you want early feedback.
when running > phpstan analyse -c phpstan.neon.dist --no-progress I get
In Resolver.php line 447:

  Service of type Symplify\PHPStanRules\NodeAnalyzer\Doctrine\EntityClassDetector: Service of type Symplify\Astral\NodeFinder\SimpleNodeFinder needed by
   $simpleNodeFinder in __construct() not found. Did you add it to configurat
  ion file?

if not feel free to close.

Yes, thank you :+1:
What happens when you run composer install? These PHPStan extension need exactly install command

not sure this is what you ask for but hier ist my composer install log (copied out of a github action)
2021-11-02T15:49:42.9817048Z [command]/usr/local/bin/composer install --no-interaction --no-progress --ansi --prefer-dist --no-progress --no-suggest
2021-11-02T15:49:43.1039918Z You are using the deprecated option "--no-suggest". It has no effect and will break in Composer 3.
2021-11-02T15:49:43.1056537Z No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
2021-11-02T15:49:43.1059757Z Loading composer repositories with package information
2021-11-02T15:49:43.3264314Z Cache not found for input keys: linux-php-8.0.11-locked-a272ef2974412d52eae3e86e2efa4e26f43ec821d1cd5164371b9575ee207f1f---prefer-dist --no-progress --no-suggest, linux-php-8.0.11-locked-a272ef2974412d52eae3e86e2efa4e26f43ec821d1cd5164371b9575ee207f1f-, linux-php-8.0.11-locked-
2021-11-02T15:49:47.7971239Z Warning from https://repo.packagist.com/complex-gmbh:
2021-11-02T15:49:47.7974108Z You are using a read-only authentication token, if you're running composer update, composer require, or composer install without a lock file, no new packages will be mirrored.
2021-11-02T15:49:49.2970863Z Updating dependencies
2021-11-02T15:49:50.5746811Z Lock file operations: 68 installs, 0 updates, 0 removals
2021-11-02T15:49:50.5748200Z   - Locking bamarni/composer-bin-plugin (1.4.1)
2021-11-02T15:49:50.5749177Z   - Locking danielstjules/stringy (3.1.0)
2021-11-02T15:49:50.5750123Z   - Locking doctrine/instantiator (1.4.0)
2021-11-02T15:49:50.5750989Z   - Locking myclabs/deep-copy (1.10.2)
2021-11-02T15:49:50.5751771Z   - Locking nette/neon (v3.3.0)
2021-11-02T15:49:50.5752524Z   - Locking nette/utils (v3.2.5)
2021-11-02T15:49:50.5753311Z   - Locking nikic/php-parser (v4.13.0)
2021-11-02T15:49:50.5754126Z   - Locking phar-io/manifest (2.0.3)
2021-11-02T15:49:50.5754930Z   - Locking phar-io/version (3.1.0)
2021-11-02T15:49:50.5755877Z   - Locking phpdocumentor/reflection-common (2.2.0)
2021-11-02T15:49:50.5756983Z   - Locking phpdocumentor/reflection-docblock (5.3.0)
2021-11-02T15:49:50.5758210Z   - Locking phpdocumentor/type-resolver (1.5.1)
2021-11-02T15:49:50.5759142Z   - Locking phpspec/prophecy (1.14.0)
2021-11-02T15:49:50.5760026Z   - Locking phpstan/phpdoc-parser (1.2.0)
2021-11-02T15:49:50.5760875Z   - Locking phpstan/phpstan (1.0.1)
2021-11-02T15:49:50.5761885Z   - Locking phpstan/phpstan-deprecation-rules (1.0.0)
2021-11-02T15:49:50.5763010Z   - Locking phpstan/phpstan-strict-rules (1.0.0)
2021-11-02T15:49:50.5764019Z   - Locking phpunit/php-code-coverage (9.2.8)
2021-11-02T15:49:50.5764998Z   - Locking phpunit/php-file-iterator (3.0.5)
2021-11-02T15:49:50.5766228Z   - Locking phpunit/php-invoker (3.1.1)
2021-11-02T15:49:50.5767184Z   - Locking phpunit/php-text-template (2.0.4)
2021-11-02T15:49:50.5768073Z   - Locking phpunit/php-timer (5.0.3)
2021-11-02T15:49:50.5768897Z   - Locking phpunit/phpunit (9.5.10)
2021-11-02T15:49:50.5769682Z   - Locking psr/container (1.1.1)
2021-11-02T15:49:50.5770508Z   - Locking sebastian/cli-parser (1.0.1)
2021-11-02T15:49:50.5771490Z   - Locking sebastian/code-unit (1.0.8)
2021-11-02T15:49:50.5772501Z   - Locking sebastian/code-unit-reverse-lookup (2.0.3)
2021-11-02T15:49:50.5773391Z   - Locking sebastian/comparator (4.0.6)
2021-11-02T15:49:50.5774149Z   - Locking sebastian/complexity (2.0.2)
2021-11-02T15:49:50.5774870Z   - Locking sebastian/diff (4.0.4)
2021-11-02T15:49:50.5775597Z   - Locking sebastian/environment (5.1.3)
2021-11-02T15:49:50.5776352Z   - Locking sebastian/exporter (4.0.3)
2021-11-02T15:49:50.5777115Z   - Locking sebastian/global-state (5.0.3)
2021-11-02T15:49:50.5777895Z   - Locking sebastian/lines-of-code (1.0.3)
2021-11-02T15:49:50.5778731Z   - Locking sebastian/object-enumerator (4.0.4)
2021-11-02T15:49:50.5779598Z   - Locking sebastian/object-reflector (2.0.4)
2021-11-02T15:49:50.5780474Z   - Locking sebastian/recursion-context (4.0.4)
2021-11-02T15:49:50.5781358Z   - Locking sebastian/resource-operations (3.0.3)
2021-11-02T15:49:50.5782155Z   - Locking sebastian/type (2.3.4)
2021-11-02T15:49:50.5782862Z   - Locking sebastian/version (3.0.2)
2021-11-02T15:49:50.5783559Z   - Locking symfony/config (v5.3.10)
2021-11-02T15:49:50.5784247Z   - Locking symfony/console (v5.3.10)
2021-11-02T15:49:50.5785069Z   - Locking symfony/dependency-injection (v5.3.10)
2021-11-02T15:49:50.5786011Z   - Locking symfony/deprecation-contracts (v2.4.0)
2021-11-02T15:49:50.5786835Z   - Locking symfony/filesystem (v5.3.4)
2021-11-02T15:49:50.5787541Z   - Locking symfony/finder (v5.3.7)
2021-11-02T15:49:50.5788315Z   - Locking symfony/polyfill-ctype (v1.23.0)
2021-11-02T15:49:50.5789220Z   - Locking symfony/polyfill-intl-grapheme (v1.23.1)
2021-11-02T15:49:50.5790206Z   - Locking symfony/polyfill-intl-normalizer (v1.23.0)
2021-11-02T15:49:50.5791139Z   - Locking symfony/polyfill-mbstring (v1.23.1)
2021-11-02T15:49:50.5791976Z   - Locking symfony/polyfill-php73 (v1.23.0)
2021-11-02T15:49:50.5792794Z   - Locking symfony/polyfill-php80 (v1.23.1)
2021-11-02T15:49:50.5793600Z   - Locking symfony/polyfill-php81 (v1.23.0)
2021-11-02T15:49:50.5794440Z   - Locking symfony/service-contracts (v2.4.0)
2021-11-02T15:49:50.5795208Z   - Locking symfony/string (v5.3.10)
2021-11-02T15:49:50.5795932Z   - Locking symplify/astral (10.0.0-beta1)
2021-11-02T15:49:50.5796834Z   - Locking symplify/autowire-array-parameter (10.0.0-beta1)
2021-11-02T15:49:50.5797920Z   - Locking symplify/composer-json-manipulator (10.0.0-beta1)
2021-11-02T15:49:50.5799036Z   - Locking symplify/easy-testing (10.0.0-beta1)
2021-11-02T15:49:50.5799903Z   - Locking symplify/package-builder (10.0.0-beta1)
2021-11-02T15:49:50.5800812Z   - Locking symplify/phpstan-extensions (10.0.0-beta1)
2021-11-02T15:49:50.5801710Z   - Locking symplify/phpstan-rules (10.0.0-beta1)
2021-11-02T15:49:50.5802861Z   - Locking symplify/rule-doc-generator-contracts (10.0.0-beta1)
2021-11-02T15:49:50.5803970Z   - Locking symplify/simple-php-doc-parser (10.0.0-beta1)
2021-11-02T15:49:50.5804918Z   - Locking symplify/smart-file-system (10.0.0-beta1)
2021-11-02T15:49:50.5805819Z   - Locking symplify/symplify-kernel (10.0.0-beta1)
2021-11-02T15:49:50.5806620Z   - Locking theseer/tokenizer (1.2.1)
2021-11-02T15:49:50.5807339Z   - Locking webmozart/assert (1.10.0)
2021-11-02T15:49:50.5808032Z Writing lock file
2021-11-02T15:49:50.5808813Z Installing dependencies from lock file (including require-dev)
2021-11-02T15:49:50.5809734Z Package operations: 68 installs, 0 updates, 0 removals
2021-11-02T15:49:50.5810630Z   - Downloading bamarni/composer-bin-plugin (1.4.1)
2021-11-02T15:49:50.5811448Z   - Downloading nette/neon (v3.3.0)
2021-11-02T15:49:50.5812257Z   - Downloading symfony/polyfill-ctype (v1.23.0)
2021-11-02T15:49:50.5813078Z   - Downloading webmozart/assert (1.10.0)
2021-11-02T15:49:50.5813948Z   - Downloading phpdocumentor/reflection-common (2.2.0)
2021-11-02T15:49:50.5814909Z   - Downloading phpdocumentor/type-resolver (1.5.1)
2021-11-02T15:49:50.5815897Z   - Downloading phpdocumentor/reflection-docblock (5.3.0)
2021-11-02T15:49:50.5816780Z   - Downloading phpstan/phpstan (1.0.1)
2021-11-02T15:49:50.5817705Z   - Downloading phpstan/phpstan-deprecation-rules (1.0.0)
2021-11-02T15:49:50.5818731Z   - Downloading phpstan/phpstan-strict-rules (1.0.0)
2021-11-02T15:49:50.5819594Z   - Downloading sebastian/version (3.0.2)
2021-11-02T15:49:50.5820348Z   - Downloading sebastian/type (2.3.4)
2021-11-02T15:49:50.5821199Z   - Downloading sebastian/resource-operations (3.0.3)
2021-11-02T15:49:50.5822147Z   - Downloading sebastian/recursion-context (4.0.4)
2021-11-02T15:49:50.5823063Z   - Downloading sebastian/object-reflector (2.0.4)
2021-11-02T15:49:50.5823964Z   - Downloading sebastian/object-enumerator (4.0.4)
2021-11-02T15:49:50.5824844Z   - Downloading sebastian/global-state (5.0.3)
2021-11-02T15:49:50.5825650Z   - Downloading sebastian/exporter (4.0.3)
2021-11-02T15:49:50.5826471Z   - Downloading sebastian/environment (5.1.3)
2021-11-02T15:49:50.5827229Z   - Downloading sebastian/diff (4.0.4)
2021-11-02T15:49:50.5828000Z   - Downloading sebastian/comparator (4.0.6)
2021-11-02T15:49:50.5828801Z   - Downloading sebastian/code-unit (1.0.8)
2021-11-02T15:49:50.5829598Z   - Downloading sebastian/cli-parser (1.0.1)
2021-11-02T15:49:50.5830377Z   - Downloading phpunit/php-timer (5.0.3)
2021-11-02T15:49:50.5831219Z   - Downloading phpunit/php-text-template (2.0.4)
2021-11-02T15:49:50.5832073Z   - Downloading phpunit/php-invoker (3.1.1)
2021-11-02T15:49:50.5832928Z   - Downloading phpunit/php-file-iterator (3.0.5)
2021-11-02T15:49:50.5833749Z   - Downloading theseer/tokenizer (1.2.1)
2021-11-02T15:49:50.5834525Z   - Downloading nikic/php-parser (v4.13.0)
2021-11-02T15:49:50.5835342Z   - Downloading sebastian/lines-of-code (1.0.3)
2021-11-02T15:49:50.5836157Z   - Downloading sebastian/complexity (2.0.2)
2021-11-02T15:49:50.5837109Z   - Downloading sebastian/code-unit-reverse-lookup (2.0.3)
2021-11-02T15:49:50.5838206Z   - Downloading phpunit/php-code-coverage (9.2.8)
2021-11-02T15:49:50.5839086Z   - Downloading doctrine/instantiator (1.4.0)
2021-11-02T15:49:50.5839980Z   - Downloading phpspec/prophecy (1.14.0)
2021-11-02T15:49:50.5840757Z   - Downloading phar-io/version (3.1.0)
2021-11-02T15:49:50.5841506Z   - Downloading phar-io/manifest (2.0.3)
2021-11-02T15:49:50.5842276Z   - Downloading myclabs/deep-copy (1.10.2)
2021-11-02T15:49:50.5843023Z   - Downloading phpunit/phpunit (9.5.10)
2021-11-02T15:49:50.5843907Z   - Downloading symfony/deprecation-contracts (v2.4.0)
2021-11-02T15:49:50.5844930Z   - Downloading symfony/polyfill-php80 (v1.23.1)
2021-11-02T15:49:50.5845767Z   - Downloading symfony/filesystem (v5.3.4)
2021-11-02T15:49:50.5846576Z   - Downloading symfony/polyfill-php73 (v1.23.0)
2021-11-02T15:49:50.5847442Z   - Downloading symfony/polyfill-php81 (v1.23.0)
2021-11-02T15:49:50.5848271Z   - Downloading psr/container (1.1.1)
2021-11-02T15:49:50.5849084Z   - Downloading symfony/service-contracts (v2.4.0)
2021-11-02T15:49:50.5850001Z   - Downloading symfony/polyfill-mbstring (v1.23.1)
2021-11-02T15:49:50.5851005Z   - Downloading symfony/polyfill-intl-normalizer (v1.23.0)
2021-11-02T15:49:50.5852061Z   - Downloading symfony/polyfill-intl-grapheme (v1.23.1)
2021-11-02T15:49:50.5852940Z   - Downloading symfony/string (v5.3.10)
2021-11-02T15:49:50.5853793Z   - Downloading symplify/symplify-kernel (10.0.0-beta1)
2021-11-02T15:49:50.5854624Z   - Downloading symfony/finder (v5.3.7)
2021-11-02T15:49:50.5855345Z   - Downloading nette/utils (v3.2.5)
2021-11-02T15:49:50.5856181Z   - Downloading symplify/smart-file-system (10.0.0-beta1)
2021-11-02T15:49:50.5857101Z   - Downloading symplify/easy-testing (10.0.0-beta1)
2021-11-02T15:49:50.5858041Z   - Downloading symfony/dependency-injection (v5.3.10)
2021-11-02T15:49:50.5858918Z   - Downloading symfony/console (v5.3.10)
2021-11-02T15:49:50.5859791Z   - Downloading symfony/config (v5.3.10)
2021-11-02T15:49:50.5860649Z   - Downloading symplify/package-builder (10.0.0-beta1)
2021-11-02T15:49:50.5861687Z   - Downloading symplify/composer-json-manipulator (10.0.0-beta1)
2021-11-02T15:49:50.5862832Z   - Downloading symplify/autowire-array-parameter (10.0.0-beta1)
2021-11-02T15:49:50.5863804Z   - Downloading symplify/astral (10.0.0-beta1)
2021-11-02T15:49:50.5864711Z   - Downloading symplify/phpstan-extensions (10.0.0-beta1)
2021-11-02T15:49:50.5865614Z   - Downloading phpstan/phpdoc-parser (1.2.0)
2021-11-02T15:49:50.5866586Z   - Downloading symplify/simple-php-doc-parser (10.0.0-beta1)
2021-11-02T15:49:50.5867533Z   - Downloading danielstjules/stringy (3.1.0)
2021-11-02T15:49:50.5868564Z   - Downloading symplify/rule-doc-generator-contracts (10.0.0-beta1)
2021-11-02T15:49:50.5869602Z   - Downloading symplify/phpstan-rules (10.0.0-beta1)
2021-11-02T15:49:54.8686043Z   - Installing bamarni/composer-bin-plugin (1.4.1): Extracting archive
2021-11-02T15:49:54.8970804Z   - Installing nette/neon (v3.3.0): Extracting archive
2021-11-02T15:49:54.9020533Z   - Installing symfony/polyfill-ctype (v1.23.0): Extracting archive
2021-11-02T15:49:54.9052735Z   - Installing webmozart/assert (1.10.0): Extracting archive
2021-11-02T15:49:54.9087377Z   - Installing phpdocumentor/reflection-common (2.2.0): Extracting archive
2021-11-02T15:49:54.9126827Z   - Installing phpdocumentor/type-resolver (1.5.1): Extracting archive
2021-11-02T15:49:54.9154842Z   - Installing phpdocumentor/reflection-docblock (5.3.0): Extracting archive
2021-11-02T15:49:54.9200212Z   - Installing phpstan/phpstan (1.0.1): Extracting archive
2021-11-02T15:49:54.9240078Z   - Installing phpstan/phpstan-deprecation-rules (1.0.0): Extracting archive
2021-11-02T15:49:54.9301528Z   - Installing phpstan/phpstan-strict-rules (1.0.0): Extracting archive
2021-11-02T15:49:54.9375311Z   - Installing sebastian/version (3.0.2): Extracting archive
2021-11-02T15:49:54.9432071Z   - Installing sebastian/type (2.3.4): Extracting archive
2021-11-02T15:49:54.9487413Z   - Installing sebastian/resource-operations (3.0.3): Extracting archive
2021-11-02T15:49:54.9598867Z   - Installing sebastian/recursion-context (4.0.4): Extracting archive
2021-11-02T15:49:54.9600415Z   - Installing sebastian/object-reflector (2.0.4): Extracting archive
2021-11-02T15:49:54.9601753Z   - Installing sebastian/object-enumerator (4.0.4): Extracting archive
2021-11-02T15:49:54.9602943Z   - Installing sebastian/global-state (5.0.3): Extracting archive
2021-11-02T15:49:54.9604063Z   - Installing sebastian/exporter (4.0.3): Extracting archive
2021-11-02T15:49:54.9605217Z   - Installing sebastian/environment (5.1.3): Extracting archive
2021-11-02T15:49:54.9606272Z   - Installing sebastian/diff (4.0.4): Extracting archive
2021-11-02T15:49:54.9607355Z   - Installing sebastian/comparator (4.0.6): Extracting archive
2021-11-02T15:49:54.9722456Z   - Installing sebastian/code-unit (1.0.8): Extracting archive
2021-11-02T15:49:54.9723959Z   - Installing sebastian/cli-parser (1.0.1): Extracting archive
2021-11-02T15:49:54.9725335Z   - Installing phpunit/php-timer (5.0.3): Extracting archive
2021-11-02T15:49:54.9727084Z   - Installing phpunit/php-text-template (2.0.4): Extracting archive
2021-11-02T15:49:54.9728415Z   - Installing phpunit/php-invoker (3.1.1): Extracting archive
2021-11-02T15:49:54.9729627Z   - Installing phpunit/php-file-iterator (3.0.5): Extracting archive
2021-11-02T15:49:54.9730853Z   - Installing theseer/tokenizer (1.2.1): Extracting archive
2021-11-02T15:49:54.9731996Z   - Installing nikic/php-parser (v4.13.0): Extracting archive
2021-11-02T15:49:54.9733197Z   - Installing sebastian/lines-of-code (1.0.3): Extracting archive
2021-11-02T15:49:54.9734412Z   - Installing sebastian/complexity (2.0.2): Extracting archive
2021-11-02T15:49:54.9735726Z   - Installing sebastian/code-unit-reverse-lookup (2.0.3): Extracting archive
2021-11-02T15:49:54.9737066Z   - Installing phpunit/php-code-coverage (9.2.8): Extracting archive
2021-11-02T15:49:54.9738318Z   - Installing doctrine/instantiator (1.4.0): Extracting archive
2021-11-02T15:49:54.9739474Z   - Installing phpspec/prophecy (1.14.0): Extracting archive
2021-11-02T15:49:54.9740594Z   - Installing phar-io/version (3.1.0): Extracting archive
2021-11-02T15:49:54.9741739Z   - Installing phar-io/manifest (2.0.3): Extracting archive
2021-11-02T15:49:54.9742848Z   - Installing myclabs/deep-copy (1.10.2): Extracting archive
2021-11-02T15:49:54.9745018Z   - Installing phpunit/phpunit (9.5.10): Extracting archive
2021-11-02T15:49:54.9746539Z   - Installing symfony/deprecation-contracts (v2.4.0): Extracting archive
2021-11-02T15:49:54.9799548Z   - Installing symfony/polyfill-php80 (v1.23.1): Extracting archive
2021-11-02T15:49:54.9803587Z   - Installing symfony/filesystem (v5.3.4): Extracting archive
2021-11-02T15:49:54.9808238Z   - Installing symfony/polyfill-php73 (v1.23.0): Extracting archive
2021-11-02T15:49:54.9812556Z   - Installing symfony/polyfill-php81 (v1.23.0): Extracting archive
2021-11-02T15:49:54.9817260Z   - Installing psr/container (1.1.1): Extracting archive
2021-11-02T15:49:54.9822363Z   - Installing symfony/service-contracts (v2.4.0): Extracting archive
2021-11-02T15:49:54.9827227Z   - Installing symfony/polyfill-mbstring (v1.23.1): Extracting archive
2021-11-02T15:49:54.9833760Z   - Installing symfony/polyfill-intl-normalizer (v1.23.0): Extracting archive
2021-11-02T15:49:54.9840401Z   - Installing symfony/polyfill-intl-grapheme (v1.23.1): Extracting archive
2021-11-02T15:49:54.9846192Z   - Installing symfony/string (v5.3.10): Extracting archive
2021-11-02T15:49:54.9852265Z   - Installing symplify/symplify-kernel (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9858352Z   - Installing symfony/finder (v5.3.7): Extracting archive
2021-11-02T15:49:54.9864070Z   - Installing nette/utils (v3.2.5): Extracting archive
2021-11-02T15:49:54.9870141Z   - Installing symplify/smart-file-system (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9880355Z   - Installing symplify/easy-testing (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9881762Z   - Installing symfony/dependency-injection (v5.3.10): Extracting archive
2021-11-02T15:49:54.9883982Z   - Installing symfony/console (v5.3.10): Extracting archive
2021-11-02T15:49:54.9887945Z   - Installing symfony/config (v5.3.10): Extracting archive
2021-11-02T15:49:54.9891858Z   - Installing symplify/package-builder (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9895762Z   - Installing symplify/composer-json-manipulator (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9899553Z   - Installing symplify/autowire-array-parameter (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9903720Z   - Installing symplify/astral (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9908304Z   - Installing symplify/phpstan-extensions (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9952550Z   - Installing phpstan/phpdoc-parser (1.2.0): Extracting archive
2021-11-02T15:49:54.9958603Z   - Installing symplify/simple-php-doc-parser (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9965712Z   - Installing danielstjules/stringy (3.1.0): Extracting archive
2021-11-02T15:49:54.9972044Z   - Installing symplify/rule-doc-generator-contracts (10.0.0-beta1): Extracting archive
2021-11-02T15:49:54.9978341Z   - Installing symplify/phpstan-rules (10.0.0-beta1): Extracting archive
2021-11-02T15:49:56.3255871Z 12 package suggestions were added by new dependencies, use `composer suggest` to see details.
2021-11-02T15:49:56.3272032Z Generating optimized autoload files
2021-11-02T15:49:56.4358672Z Class clxSymplify\PHPStan\Rules\Tests\ForbiddenMathRuleTest located in ./packages/phpstan-rules/tests/Rules/ForbiddenMathRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.4361759Z Class clxSymplify\PHPStan\Rules\Tests\SqlPlaceholderRuleTest located in ./packages/phpstan-rules/tests/Rules/SqlPlaceholderRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.4365233Z Class clxSymplify\PHPStan\Rules\Tests\NoJavascriptInStringRuleTest located in ./packages/phpstan-rules/tests/Rules/NoJavascriptInStringRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.4371624Z Class clxSymplify\PHPStan\Rules\Tests\ActiveRecordArrayRuleTest located in ./packages/phpstan-rules/tests/Rules/ActiveRecordArrayRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.4375613Z Class clxSymplify\PHPStan\Rules\Tests\ModelAbstractArrayRuleTest located in ./packages/phpstan-rules/tests/Rules/ModelAbstractArrayRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.4388268Z Class clxSymplify\PHPStan\Rules\Tests\EchoDeprecatedToStringRuleTest located in ./packages/phpstan-rules/tests/Rules/EchoDeprecatedToStringRuleTest.php does not comply with psr-4 autoloading standard. Skipping.
2021-11-02T15:49:56.6734323Z 51 packages you are using are looking for funding.
2021-11-02T15:49:56.6739236Z Use the `composer fund` command to find out more!
2021-11-02T15:49:56.9046193Z Loading composer repositories with package information
2021-11-02T15:49:58.3736450Z Updating dependencies
2021-11-02T15:49:58.4232504Z Lock file operations: 17 installs, 0 updates, 0 removals
2021-11-02T15:49:58.4234093Z   - Locking bmitch/churn-php (1.5.0)
2021-11-02T15:49:58.4235367Z   - Locking composer/package-versions-deprecated (<IP_ADDRESS>)
2021-11-02T15:49:58.4236550Z   - Locking psr/container (1.1.1)
2021-11-02T15:49:58.4237439Z   - Locking symfony/console (v5.3.10)
2021-11-02T15:49:58.4238686Z   - Locking symfony/deprecation-contracts (v2.4.0)
2021-11-02T15:49:58.4239791Z   - Locking symfony/filesystem (v5.3.4)
2021-11-02T15:49:58.4240783Z   - Locking symfony/polyfill-ctype (v1.23.0)
2021-11-02T15:49:58.4241858Z   - Locking symfony/polyfill-intl-grapheme (v1.23.1)
2021-11-02T15:49:58.4243122Z   - Locking symfony/polyfill-intl-normalizer (v1.23.0)
2021-11-02T15:49:58.4244315Z   - Locking symfony/polyfill-mbstring (v1.23.1)
2021-11-02T15:49:58.4245369Z   - Locking symfony/polyfill-php73 (v1.23.0)
2021-11-02T15:49:58.4246411Z   - Locking symfony/polyfill-php80 (v1.23.1)
2021-11-02T15:49:58.4247331Z   - Locking symfony/process (v5.3.7)
2021-11-02T15:49:58.4248350Z   - Locking symfony/service-contracts (v2.4.0)
2021-11-02T15:49:58.4249343Z   - Locking symfony/string (v5.3.10)
2021-11-02T15:49:58.4250240Z   - Locking symfony/yaml (v5.3.6)
2021-11-02T15:49:58.4251094Z   - Locking webmozart/assert (1.10.0)
2021-11-02T15:49:58.4252014Z Writing lock file
2021-11-02T15:49:58.4253053Z Installing dependencies from lock file (including require-dev)
2021-11-02T15:49:58.4260402Z Package operations: 17 installs, 0 updates, 0 removals
2021-11-02T15:49:58.4268053Z   - Downloading composer/package-versions-deprecated (<IP_ADDRESS>)
2021-11-02T15:49:58.4273279Z   - Downloading symfony/polyfill-ctype (v1.23.0)
2021-11-02T15:49:58.4277398Z   - Downloading webmozart/assert (1.10.0)
2021-11-02T15:49:58.4282345Z   - Downloading symfony/deprecation-contracts (v2.4.0)
2021-11-02T15:49:58.4285646Z   - Downloading symfony/yaml (v5.3.6)
2021-11-02T15:49:58.4289976Z   - Downloading symfony/polyfill-php80 (v1.23.1)
2021-11-02T15:49:58.4293530Z   - Downloading symfony/process (v5.3.7)
2021-11-02T15:49:58.4297151Z   - Downloading symfony/filesystem (v5.3.4)
2021-11-02T15:49:58.4300922Z   - Downloading symfony/polyfill-mbstring (v1.23.1)
2021-11-02T15:49:58.4309530Z   - Downloading symfony/polyfill-intl-normalizer (v1.23.0)
2021-11-02T15:49:58.4310824Z   - Downloading symfony/polyfill-intl-grapheme (v1.23.1)
2021-11-02T15:49:58.4313046Z   - Downloading symfony/string (v5.3.10)
2021-11-02T15:49:58.4323542Z   - Downloading psr/container (1.1.1)
2021-11-02T15:49:58.4324444Z   - Downloading symfony/service-contracts (v2.4.0)
2021-11-02T15:49:58.4325429Z   - Downloading symfony/polyfill-php73 (v1.23.0)
2021-11-02T15:49:58.4326416Z   - Downloading symfony/console (v5.3.10)
2021-11-02T15:49:58.4327798Z   - Downloading bmitch/churn-php (1.5.0)
2021-11-02T15:49:58.9864262Z   - Installing composer/package-versions-deprecated (<IP_ADDRESS>): Extracting archive
2021-11-02T15:49:59.0070810Z   - Installing symfony/polyfill-ctype (v1.23.0): Extracting archive
2021-11-02T15:49:59.0102783Z   - Installing webmozart/assert (1.10.0): Extracting archive
2021-11-02T15:49:59.0130543Z   - Installing symfony/deprecation-contracts (v2.4.0): Extracting archive
2021-11-02T15:49:59.0156503Z   - Installing symfony/yaml (v5.3.6): Extracting archive
2021-11-02T15:49:59.0186371Z   - Installing symfony/polyfill-php80 (v1.23.1): Extracting archive
2021-11-02T15:49:59.0214080Z   - Installing symfony/process (v5.3.7): Extracting archive
2021-11-02T15:49:59.0239578Z   - Installing symfony/filesystem (v5.3.4): Extracting archive
2021-11-02T15:49:59.0265992Z   - Installing symfony/polyfill-mbstring (v1.23.1): Extracting archive
2021-11-02T15:49:59.0294796Z   - Installing symfony/polyfill-intl-normalizer (v1.23.0): Extracting archive
2021-11-02T15:49:59.0320416Z   - Installing symfony/polyfill-intl-grapheme (v1.23.1): Extracting archive
2021-11-02T15:49:59.0344355Z   - Installing symfony/string (v5.3.10): Extracting archive
2021-11-02T15:49:59.0353745Z   - Installing psr/container (1.1.1): Extracting archive
2021-11-02T15:49:59.0361209Z   - Installing symfony/service-contracts (v2.4.0): Extracting archive
2021-11-02T15:49:59.0368536Z   - Installing symfony/polyfill-php73 (v1.23.0): Extracting archive
2021-11-02T15:49:59.0375664Z   - Installing symfony/console (v5.3.10): Extracting archive
2021-11-02T15:49:59.0382911Z   - Installing bmitch/churn-php (1.5.0): Extracting archive
2021-11-02T15:49:59.4850938Z 4 package suggestions were added by new dependencies, use `composer suggest` to see details.
2021-11-02T15:49:59.4856536Z Generating autoload files
2021-11-02T15:49:59.4905976Z composer/package-versions-deprecated: Generating version class...
2021-11-02T15:49:59.4907717Z composer/package-versions-deprecated: ...done generating version class
2021-11-02T15:49:59.4908964Z 14 packages you are using are looking for funding.
2021-11-02T15:49:59.4909765Z Use the `composer fund` command to find out more!
2021-11-02T15:49:59.5341672Z Loading composer repositories with package information
2021-11-02T15:50:00.2665159Z Updating dependencies
2021-11-02T15:50:00.2835097Z Lock file operations: 29 installs, 0 updates, 0 removals
2021-11-02T15:50:00.2836147Z   - Locking composer/semver (3.2.6)
2021-11-02T15:50:00.2837165Z   - Locking composer/xdebug-handler (2.0.2)
2021-11-02T15:50:00.2838282Z   - Locking doctrine/annotations (1.13.2)
2021-11-02T15:50:00.2839075Z   - Locking doctrine/lexer (1.2.1)
2021-11-02T15:50:00.2839936Z   - Locking friendsofphp/php-cs-fixer (v3.2.1)
2021-11-02T15:50:00.2840869Z   - Locking php-cs-fixer/diff (v2.0.2)
2021-11-02T15:50:00.2841586Z   - Locking psr/cache (1.0.1)
2021-11-02T15:50:00.2842304Z   - Locking psr/container (1.1.1)
2021-11-02T15:50:00.2843113Z   - Locking psr/event-dispatcher (1.0.0)
2021-11-02T15:50:00.2844175Z   - Locking psr/log (1.1.4)
2021-11-02T15:50:00.2844910Z   - Locking symfony/console (v5.3.10)
2021-11-02T15:50:00.2845815Z   - Locking symfony/deprecation-contracts (v2.4.0)
2021-11-02T15:50:00.2846793Z   - Locking symfony/event-dispatcher (v5.3.7)
2021-11-02T15:50:00.2847842Z   - Locking symfony/event-dispatcher-contracts (v2.4.0)
2021-11-02T15:50:00.2848770Z   - Locking symfony/filesystem (v5.3.4)
2021-11-02T15:50:00.2849706Z   - Locking symfony/finder (v5.3.7)
2021-11-02T15:50:00.2850560Z   - Locking symfony/options-resolver (v5.3.7)
2021-11-02T15:50:00.2851441Z   - Locking symfony/polyfill-ctype (v1.23.0)
2021-11-02T15:50:00.2852439Z   - Locking symfony/polyfill-intl-grapheme (v1.23.1)
2021-11-02T15:50:00.2853546Z   - Locking symfony/polyfill-intl-normalizer (v1.23.0)
2021-11-02T15:50:00.2854562Z   - Locking symfony/polyfill-mbstring (v1.23.1)
2021-11-02T15:50:00.2855549Z   - Locking symfony/polyfill-php72 (v1.23.0)
2021-11-02T15:50:00.2856392Z   - Locking symfony/polyfill-php73 (v1.23.0)
2021-11-02T15:50:00.2857274Z   - Locking symfony/polyfill-php80 (v1.23.1)
2021-11-02T15:50:00.2858186Z   - Locking symfony/polyfill-php81 (v1.23.0)
2021-11-02T15:50:00.2858964Z   - Locking symfony/process (v5.3.7)
2021-11-02T15:50:00.2859849Z   - Locking symfony/service-contracts (v2.4.0)
2021-11-02T15:50:00.2860707Z   - Locking symfony/stopwatch (v5.3.4)
2021-11-02T15:50:00.2861505Z   - Locking symfony/string (v5.3.10)
2021-11-02T15:50:00.2862128Z Writing lock file
2021-11-02T15:50:00.2862995Z Installing dependencies from lock file (including require-dev)
2021-11-02T15:50:00.2871563Z Package operations: 29 installs, 0 updates, 0 removals
2021-11-02T15:50:00.2875515Z   - Downloading doctrine/lexer (1.2.1)
2021-11-02T15:50:00.2885666Z   - Downloading symfony/stopwatch (v5.3.4)
2021-11-02T15:50:00.2894014Z   - Downloading symfony/polyfill-php81 (v1.23.0)
2021-11-02T15:50:00.2897980Z   - Downloading symfony/polyfill-php72 (v1.23.0)
2021-11-02T15:50:00.2905442Z   - Downloading symfony/options-resolver (v5.3.7)
2021-11-02T15:50:00.2909246Z   - Downloading symfony/finder (v5.3.7)
2021-11-02T15:50:00.2917116Z   - Downloading psr/event-dispatcher (1.0.0)
2021-11-02T15:50:00.2921272Z   - Downloading symfony/event-dispatcher-contracts (v2.4.0)
2021-11-02T15:50:00.2924328Z   - Downloading symfony/event-dispatcher (v5.3.7)
2021-11-02T15:50:00.2941155Z   - Downloading php-cs-fixer/diff (v2.0.2)
2021-11-02T15:50:00.2944427Z   - Downloading psr/cache (1.0.1)
2021-11-02T15:50:00.2948696Z   - Downloading doctrine/annotations (1.13.2)
2021-11-02T15:50:00.2952872Z   - Downloading psr/log (1.1.4)
2021-11-02T15:50:00.2956315Z   - Downloading composer/xdebug-handler (2.0.2)
2021-11-02T15:50:00.2959801Z   - Downloading composer/semver (3.2.6)
2021-11-02T15:50:00.2963179Z   - Downloading friendsofphp/php-cs-fixer (v3.2.1)
2021-11-02T15:50:00.8794953Z   - Installing doctrine/lexer (1.2.1): Extracting archive
2021-11-02T15:50:00.8831048Z   - Installing psr/container (1.1.1): Extracting archive
2021-11-02T15:50:00.8860286Z   - Installing symfony/service-contracts (v2.4.0): Extracting archive
2021-11-02T15:50:00.8890521Z   - Installing symfony/stopwatch (v5.3.4): Extracting archive
2021-11-02T15:50:00.8918310Z   - Installing symfony/polyfill-php80 (v1.23.1): Extracting archive
2021-11-02T15:50:00.8944405Z   - Installing symfony/process (v5.3.7): Extracting archive
2021-11-02T15:50:00.8971640Z   - Installing symfony/polyfill-php81 (v1.23.0): Extracting archive
2021-11-02T15:50:00.8998431Z   - Installing symfony/polyfill-php72 (v1.23.0): Extracting archive
2021-11-02T15:50:00.9025024Z   - Installing symfony/polyfill-php73 (v1.23.0): Extracting archive
2021-11-02T15:50:00.9051344Z   - Installing symfony/deprecation-contracts (v2.4.0): Extracting archive
2021-11-02T15:50:00.9076683Z   - Installing symfony/options-resolver (v5.3.7): Extracting archive
2021-11-02T15:50:00.9086646Z   - Installing symfony/finder (v5.3.7): Extracting archive
2021-11-02T15:50:00.9095143Z   - Installing symfony/polyfill-ctype (v1.23.0): Extracting archive
2021-11-02T15:50:00.9104050Z   - Installing symfony/filesystem (v5.3.4): Extracting archive
2021-11-02T15:50:00.9112355Z   - Installing psr/event-dispatcher (1.0.0): Extracting archive
2021-11-02T15:50:00.9120266Z   - Installing symfony/event-dispatcher-contracts (v2.4.0): Extracting archive
2021-11-02T15:50:00.9128028Z   - Installing symfony/event-dispatcher (v5.3.7): Extracting archive
2021-11-02T15:50:00.9153404Z   - Installing symfony/polyfill-mbstring (v1.23.1): Extracting archive
2021-11-02T15:50:00.9163943Z   - Installing symfony/polyfill-intl-normalizer (v1.23.0): Extracting archive
2021-11-02T15:50:00.9182475Z   - Installing symfony/polyfill-intl-grapheme (v1.23.1): Extracting archive
2021-11-02T15:50:00.9186990Z   - Installing symfony/string (v5.3.10): Extracting archive
2021-11-02T15:50:00.9191456Z   - Installing symfony/console (v5.3.10): Extracting archive
2021-11-02T15:50:00.9195819Z   - Installing php-cs-fixer/diff (v2.0.2): Extracting archive
2021-11-02T15:50:00.9200222Z   - Installing psr/cache (1.0.1): Extracting archive
2021-11-02T15:50:00.9204375Z   - Installing doctrine/annotations (1.13.2): Extracting archive
2021-11-02T15:50:00.9208216Z   - Installing psr/log (1.1.4): Extracting archive
2021-11-02T15:50:00.9212630Z   - Installing composer/xdebug-handler (2.0.2): Extracting archive
2021-11-02T15:50:00.9216615Z   - Installing composer/semver (3.2.6): Extracting archive
2021-11-02T15:50:00.9221154Z   - Installing friendsofphp/php-cs-fixer (v3.2.1): Extracting archive
2021-11-02T15:50:01.4583095Z 4 package suggestions were added by new dependencies, use `composer suggest` to see details.
2021-11-02T15:50:01.4592021Z Generating autoload files
2021-11-02T15:50:01.4642871Z 23 packages you are using are looking for funding.
2021-11-02T15:50:01.4644251Z Use the `composer fund` command to find out more!
2021-11-02T15:50:01.5121143Z Loading composer repositories with package information
2021-11-02T15:50:01.9066376Z Updating dependencies
2021-11-02T15:50:01.9088662Z Lock file operations: 3 installs, 0 updates, 0 removals
2021-11-02T15:50:01.9090443Z   - Locking phpstan/extension-installer (1.1.0)
2021-11-02T15:50:01.9091544Z   - Locking phpstan/phpstan (0.12.99)
2021-11-02T15:50:01.9092662Z   - Locking phpstan/phpstan-deprecation-rules (0.12.6)
2021-11-02T15:50:01.9095361Z Writing lock file
2021-11-02T15:50:01.9096314Z Installing dependencies from lock file (including require-dev)
2021-11-02T15:50:01.9097876Z Package operations: 3 installs, 0 updates, 0 removals
2021-11-02T15:50:01.9100623Z   - Downloading phpstan/phpstan (0.12.99)
2021-11-02T15:50:01.9104001Z   - Downloading phpstan/extension-installer (1.1.0)
2021-11-02T15:50:01.9105369Z   - Downloading phpstan/phpstan-deprecation-rules (0.12.6)
2021-11-02T15:50:02.4539560Z   - Installing phpstan/phpstan (0.12.99): Extracting archive
2021-11-02T15:50:02.5835880Z     Skipped installation of bin phpstan for package phpstan/phpstan: name conflicts with an existing file
2021-11-02T15:50:02.5837474Z     Skipped installation of bin phpstan.phar for package phpstan/phpstan: name conflicts with an existing file
2021-11-02T15:50:02.5849020Z   - Installing phpstan/extension-installer (1.1.0): Extracting archive
2021-11-02T15:50:02.5963057Z   - Installing phpstan/phpstan-deprecation-rules (0.12.6): Extracting archive
2021-11-02T15:50:02.9626894Z Generating autoload files
2021-11-02T15:50:02.9646456Z 1 package you are using is looking for funding.
2021-11-02T15:50:02.9647873Z Use the `composer fund` command to find out more!
2021-11-02T15:50:02.9650385Z phpstan/extension-installer: Extensions installed
2021-11-02T15:50:02.9651811Z > phpstan/phpstan-deprecation-rules: installed
2021-11-02T15:50:03.0326635Z ##[group]Run composer bin phpstan install --no-progress
2021-11-02T15:50:03.0327373Z composer bin phpstan install --no-progress
2021-11-02T15:50:03.0375967Z shell: /usr/bin/bash -e {0}
2021-11-02T15:50:03.0376369Z ##[endgroup]

The composer update would not be enought, I meanted to run composer install instead. Which you already did :+1:
I see this package is missing https://github.com/phpstan/extension-installer
Try to add it, should be enought to solve. Otherwise you have to include various configs manually with correct absolute paths: https://github.com/symplify/astral/blob/ae79b4f8a8ad417760da934b6d66d50f05f9ef07/composer.json#L34-L38

hm I see. I used the previous version also without the extension installer, since I am only cherry picking certain rules and don't want everything.
it seems I need to adjust the config. would be great for DX to get a more explicit error

I recommend using installer, as all other packages like Twig/Latte rules depend on it. You'll save yourself lot of copy paste work and config maintenance.

The rules are not included, so you can still cherry pick them:
https://github.com/symplify/phpstan-rules/blob/main/composer.json#L57


Update engine_warmup.py

fix [issue #2170]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


class tables not working

attempting to insert a half or full class table from the menu does not insert the table.
.Additional Details
Share Link :
or
Brew code to reproduce : Click to expand
PASTE BREW CODE HERE

I'm also having the same problem.

Same issue

Same issue as well

Fixed in v2.6.2


Service generator for other languages

This is a bit of a niche request - I'm building an app with a custom RPC implementation, defined by Protobuf services. So prost-build's ServiceGenerator is extremely convenient (great job!). However the frontend of my app is in another language that already has Protobuf support, but obviously doesn't support my custom RPC.
The "proper" solution is of course to write a proper protoc plugin, but I am lazy and prost-build has already done most of the work. It would be great if I could write a ServiceGenerator to output my other-language RPC code.
This is sort of almost possible via this massive hack:
fn main() {
	...
	let mut typescript_build = prost_build::Config::new();

	typescript_build.service_generator(
		Box::new(TypescriptRpcGenerator{clear_file: true})
	);

	typescript_build.out_dir("../protocol");

	typescript_build.compile_protos(
		&["../protocol/foo.proto"],
		&["../protocol"],
	).expect("Typescript Protobuf compilation failed");
}

struct TypescriptRpcGenerator {
	// Massive HACK!
	clear_file: bool,
}

impl ServiceGenerator for TypescriptRpcGenerator {
	fn generate(&mut self, service: Service, buf: &mut String) {
		if self.clear_file {
			buf.clear();
			self.clear_file = false;
		}
		buf.push_str("\nFoo\n");
	}
}

Obviously that sucks, but it could be made nice with two extra options:

Allow for changing the filename extension from .rs (default) to something else. It's set here.
Add a flag to disable generation of the protobuf type code. I guess add an if() around these loops?

Would you accept a pull request for these?

Actually haven't used it more I don't think this will work. And writing a proper plugin isn't that hard.


wsl.exe Wrong Default Display Langauge

Version
Microsoft Windows [Version 10.0.22621.900]
WSL Version

[ ] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
Install Windows 11 with the romanian language pack, maybe other languages affected.
Run wsl --install
Do wsl --help the help language wont be in english as expected

Expected Behavior
Default to english
Actual Behavior
PS C:\Users\marin> wsl -v
Verze WSL: <IP_ADDRESS>
Verze jádra: <IP_ADDRESS>
Verze WSLg: 1.0.47
Verze MSRDC: 1.2.3575
Verze Direct3D: 1.606.4
Verze DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
verze Windows: 10.0.22621.900
PS C:\Users\marin>

Diagnostic Logs
No response
Solution
https://github.com/microsoft/WSL/issues/9242#issuecomment-1406138325

Could you try powershell Get-WinSystemLocale?

Could you try powershell Get-WinSystemLocale?

LCID             Name             DisplayName

1048             ro-RO            Romanian (Romania)

I have a similar problem, although it goes to Dutch. My display language is English:
LCID             Name             DisplayName
----             ----             -----------
1033             en-US            English (United States)

I don't even have Dutch installed.

Had a similar issue, where WSL display language was in Czech.
In language settings:
Windows display language: English (United States)
Under Preferred languages: Only Estonian (language pack not even downloaded), which also set Apps & websites language to Estonian.
Solution:
Installed English (United States) language pack under Preferred languages. Left the order remain (Estonian first, English second), so the Apps & websites language remained Estonian, but WSL diaplay language turned to English (as desired).
Hope it is helpful for others dealing with similar issue.

Same issue here, only the system locale is en-US. However, I do have the country and region set to Romania and the default input method set as Romanian (Programmers).

Had a similar issue, where WSL display language was in Czech.
In language settings: Windows display language: English (United States) Under Preferred languages: Only Estonian (language pack not even downloaded), which also set Apps & websites language to Estonian.
Solution: Installed English (United States) language pack under Preferred languages. Left the order remain (Estonian first, English second), so the Apps & websites language remained Estonian, but WSL diaplay language turned to English (as desired).
Hope it is helpful for others dealing with similar issue.

Can confirm your solution works works

Same issue here, only the system locale is en-US. However, I do have the country and region set to Romania and the default input method set as Romanian (Programmers).

Add English United States as additional language and it should display

Still, it's a problem that should be clarified - is the Romanian language package filled with Czech localization strings, or is there a bug in wsl?

@dorinlazar In my case there was nothing to do with Romanian language. I myself suspect WSL, but being not familiar in detail, how languages and locales work, can't really confirm my suspicions.

Bug in WSL

My Windows is set to English and there is no language pack installed:

The CLI output for commands is in English
The clie output for the update command is in German
which leads me to believe it uses some sort of GEO IP or the region settings? Either way, pretty weird, would love to have everything in English.

It's been almost a year and it's still broken. @benhillis Can we expect a solution anytime soon?

Same problem here since the upgrade from WSL <IP_ADDRESS> to <IP_ADDRESS>
My Windows 11 is setup to use English for the Language and French for the Region.
PS> systeminfo | findstr Locale
System Locale:             en-gb;English (United Kingdom)
Input Locale:              en-gb;English (United Kingdom)

PS> Get-WinSystemLocale

LCID             Name             DisplayName
----             ----             -----------
2057             en-GB            English (United Kingdom)

PS> xyz
xyz : The term 'xyz' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.

It looks like that  sometime WSL.EXE uses the Region, and sometime it uses the Language.
For some options WLS.EXE displays result in French (my Windows Region):
PS> wsl.exe --version
Version WSL : <IP_ADDRESS>
Version du noyau : <IP_ADDRESS>-1
Version WSLg : 1.0.59
Version MSRDC : 1.2.4677
Version direct3D : 1.611.1-81528511
Version de DXCore : 10.0.25880.1000-230602-1350.main
Version de Windows : 10.0.22621.2428

For other options it displays result in English (my Windows Language):
PS> wsl -l -v
  NAME                      STATE           VERSION
* Alpine                    Running         2
  docker-desktop            Stopped         2
  docker-desktop-data       Stopped         2
  OracleLinux_7_9           Stopped         2
  podman-machine-default    Stopped         2

I guess everyone expect an output in the same language as the Language selected in the 'Language & Region' settings.

This just suddenbly happend for me today:

Single command - two languages.

It's a widespread problem across Microsoft products where Culture and UI Culture are mixed.
Region/Regional format/Location should never affect the language. Either Windows display language or the first one on preferred language list should be used (these are both en-US for me).

Why on earth is my WSL German? I installed Windows in English (United States).

I have the same problem right after doing the wsl --update from 1.x.x.x to <IP_ADDRESS>. WSL output language has changed to Russian.

Should've been English - the chosen Windows display language and the topmost preferred language:

Mentioned solutions don't work. Chosen regional date/time format should NOT affect the WSL output language.

After some experimentation, it is clear that the language WSL uses for localization is taken from the "reginal format" setting, as several people have pointed out above, which is 100% a bug. People can and do use other contries formats without knowing the language, and not being able to even read the help without changing system settings to something inconvenient is awful. Please fix.

Can confirm that wsl.exe 2.0.14 is switching its display language when you change the Windows Region and Regional Format.
What part of "Windows Display Language = English (US)" does wsl.exe not understand??? Does it need more AI or maybe just more common sense?

Changing Regional format does indeed change the wsl language:

WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3930

Can this please be labeled as a bug?

Please, know, that advanced users and especially developers and administrators usually never want a translated version.

I disagree.  If applications are translated, they should come in the language the user expects. You're using a generalisation to express your personal opinion. That does not help the quality of the application and only shifts the issue to a different group of people - namely the ones who want localised apps. If you want your system and apps to be in English, then you can do that via the system language settings.
The problem here is that the application does not follow the system language, but rather the region. These are two different settings. A user can be located in Germany, Poland, France or any other place in the world and would prefer to see content from that region. This is why you can set the region in Windows to wherever you are at the moment. All the while you can still have your system language in the language you are comfortable with. And then there are date, time and number formats, which can also be configured independent of region and language.
I'm frankly tired of seeing these issues in Microsoft applications, as these settings things have been in Windows for at least 20 years and I'm shocked that Microsoft developers still don't understand how these work.

https://github.com/microsoft/WSL/releases/tag/2.1.3

Use the display language for localization instead of the default locale (solves #11087,#11051)

The problem here is that the application does not follow the system language, but rather the region. These are two different settings. A user can be located in Germany, Poland, France or any other place in the world and would prefer to see content from that region. This is why you can set the region in Windows to wherever you are at the moment. All the while you can still have your system language in the language you are comfortable with. And then there are date, time and number formats, which can also be configured independent of region and language.
And applications should follow system language. It's that simple.
I'm frankly tired of seeing these issues in Microsoft applications, as these settings have been in Windows for at least 20 years and I'm shocked that Microsoft developers still don't grasp this concept.

Yes, that is the bug here and must be fixed.
Furthermore there are not only the region and the display language but also the input method (keyboard layout) and the formatting options for currency, date and so on as well as the time zone. All of these settings must be changeable completely independently and must be respected by every application.

I disagree. If applications are translated, they should come in the language the user expects. You're using a generalisation to express your personal opinion. That does not help the quality of the application and only shifts the issue to a different group of people - namely the ones who want localised apps. If you want your system and apps to be in English, then you can do that via the system language settings.

Sure, that is one way.
But I claim that there are different kind of applications. There are those which main target audience are developers and administrators. And for those I claim, that there is only one working way for avoid misunderstandings and errors: English language. It does not make sense to translate technical keywords or phrases into some other language. It will only lead to subtle differences in the meaning and a lost in some details (best case) or even to big errors (worst case).
For example, to program VBA in Excel in any other language than English is just a pain. English is the common language for interchange. Imagine, everybody would program an API of a library, the source and all the comments in his/her native spoken language. The IT world would collapse entirely.
So, again, I claim, that for tools which are targeted for developers and administrators are best available only in English.
It will lead to global interchangeable results automatically.
This is not only my personal opinion but backed with reasonable points.
When it comes to personal opinion, I can add the following:
I not only want that application will follow the set system language. I want set the display language for each application individually.
As I said, tools for developing shall be in English for me, but my Word shall be in German as well as any movie app. Also, for movies, I don't want English or English subtitles but German for default, and so on.

https://github.com/microsoft/WSL/releases/tag/2.1.3

Use the display language for localization instead of the default locale (solves #11087,#11051)

That sounds promising. Thank you!

Solved with 2.1.3


Teff and bp_rp are now optional inputs

At least one must be provided though.
The missing parameters are just replaced by the mean of the prior and a very wide std before it gets fed to KDE.
Also added unit tests for these parts.

@grd349 ready to merge

At 2 sigma, what I put in covers the 16500 targets in Teff by a margin of
800K, the margin might be a bit narrower for bp_rp.
It seems to work on RGs though. Haven't run it on an F-star yet.
For now I don't really have an issue with asking people to supply both if
they can. Soon PBjam will automatically get bp_rp anyway, so Teff will be
the only thing they have to worry about.
On Mon, 8 Jun 2020 at 07:38, Guy Davies<EMAIL_ADDRESS>wrote:

@grd349 commented on this pull request.
Looks fine to me. Is this really the functionality we want? What happens
when someone runs on a bloody F-star - The new prior will prefer lower
temperatures. If we force people to supply values then they must think
about what they are doing. The prior on Teff for a main sequence star with
seismic detection is probably more like 6000 \pm 1000.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grd349/PBjam/pull/241#pullrequestreview-425947782,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJWO37HMIOZKCKAWKEWAZTRVSBPVANCNFSM4NTOE3ZA
.


Issue with authentivation token manipulation in last commit b228791

Hello,
it seems that the latest version ( b228791 ) of Tileboard has an issue with the auth token manipulation with the following message :
TypeError: Cannot read property 'then' of undefined
The error seems to come from the models/api.js fil here when calling this.getToken().then(....).
I am far from a JS expert, but i may try to have a look into it soon.
Currently I took an older commit and it works great.
Grm

Will have a look at the code soon (currently in transit). What platform/browser/version?

Can you point out the exact code line where this happens for you? There is no this.getToken().then line, there is _getToken but the code there looks fine to me.

My bad, as i have typed the ticket after reverting, i forgot about the underscore.
Here are the screens from the developer tools.

I am on Mac using chrome (Version 78.0.3904.70 (Official Build) (64-bit)) and on android using also chrome !
I had a quick look into it (trying to have a new one tomorrow) and it seemed also fine ...  Maybe i need to adapt my config.js (which was working fine before and works with the previous version) ?
Grm

And are you sure you don't have any local modifications in your api.js?
I can see how it would fail if any code path in _getToken would not return a promise but as far as I can tell it doesn't.
If you would be willing to debug it, you could place a breakpoint on that line and once it breaks, step into and over the code to see how it returns something that it shouldn't.

Never mind, I see that it returns undefined in a case when using long-lived token (I think). I will look into it.

Working like a charm now.
Thanks,
Grm


Revert "[ownership] Convert OME into a function pass"

Reverts apple/swift#33205
This maybe causing failures on Linux. Reverting it until I can repro and fix.

I can start testing only once #34081 is merged

Closing in favor of #34084


Remove unnecessary output related to duplicate region checking

Saw this mentioned in the Discord and had a moment, so figured I'd go ahead and PR this quick fix.
The duplicate region checking that RE3R does outputs a message when it's skipping a region, but this might look like an error to users. So this PR removes the unnecessary message.


feat(workflows): Remove the option of updating the workflow name

This PR eliminates the ability for users to update the name of a workflow, as we are transitioning to a declarative approach where names are immutable.
Refs #683

This PR contains unrelated changes that we'll be remove once this PR is merged: https://github.com/chainloop-dev/chainloop/pull/920

I've mad the column immutable and did a migration to update possible null values + setting it required on the DB.


Cow: Watch +8613520320431

Cow requests the watch of the watch_number +8613520320431. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Rejected by cocomac in Charcoal HQ. No rejection reason was provided.

This was duplicated by a watch tripleee made after this was created, so I'm rejecting it. SD was not cooperating with a rejection reason.


Allow skipping more than one hostname

Skipping more than one hostname does seem to work correctly.
However, the skipping is specific to a particular host and not subdomains of that host.
e.g. -s google.com will not skip the url www.google.com


Unable to close the dropdown after double selection

Describe the bug
When using a custom ItemRenderer, double selecting a single item will remove the capability to  close the dropdown when clicking outside.
Sandbox / Git Repo
https://codesandbox.io/s/naughty-dewdney-wn7v74?file=/src/App.js
To Reproduce
Steps to reproduce the behavior:

Check out the repo
Select a single item
Deselect the item
click outside of the dropdown
It won't close

Expected behavior
It closes when clicked outside
Screenshots

Desktop (please complete the following information):

OS: Win 11
Chrome
Latest

Additional context
Maybe I use the Default Item renderer wrong, but there is no working example in the docs and this was the only thing I found in the soruce code.

Hi, I have the same issue. Any update on this one?

Checkout this : https://codesandbox.io/p/sandbox/react-multi-select-example-uqtgs?file=%2Fsrc%2FApp.js%3A1%2C1-34%2C1

I work around this by using the useClickAway hook in @uidotdev/usehooks
Put the MultiSelect component in div with ref from useClickAway
When clicked outside, trigger function to find to class .dropdown-heading, then trigger click event.
Worked!

@Uni2K Please check the focus of the dropdown. When you use a ItemRender after first click, the Dropdown loses focus and cannot be closed clicking outside.


Reorganize and format the code

I found that some code fragments do not conform to the format of pep8, which is not beautiful and easy to read. I hope I can reformat the code.

Thanks for doing this. And all redundant outputs are now removed. New version on PyPI has been published.


[Server] [Discovery] dutyfree backend

Background:

As the wise man says, for every frontend there is a backend to serve its needs.
This is discovery into how will the backend of dutyfree look like. The current ideas that I have on mind are:

API backend with a small db (might be an overkill)
API backend with a yml file (might not be the best architecture)
Same as the current way: rendering static pages based on a yaml file.

Acceptance Criteria:

[ ] we should define the way the backend will look like.

so had a bit of a discussion with @YoussB earlier, and we talked about a couple of things regarding the backend discovery:

first it just needs to serve up resource names, versions, and descriptions (IIRC)
when it comes to figuring out the contributor workflow, ie how to add a resource, how we check whether a resource is acceptable or not, how that resource gets updated when a new version comes out, etc etc, will be decided somewhat later, but we should probably keep those questions in the back of our mind when we are deciding on how we want our backend to be set up
i think that having the backend with a db is the easiest and most futureproof way of doing things, since the most we'll have to do data wise is a migration, BUT even that will affect the contributor workflow (i think)
so long story short, we're still discussing 😅

working out of the branch go-backdend
the current plan is to have a Golang api in the backend, but still unsure about the persistence layer.
we're building a working skeleton for the api.

We now have our basic backend serving api and static files, this replaces the need to have a separate way to serve static files.
The current code is experimental, but sets a base for the backend.


Passing querystring parameters to collection components (via route request??)

When a collection component needs to be filtered on SSR loading we need to be able to pass the querystring to the collection. Need to think about how to handle this where it will be able to support multiple collections on a page so we know which filter parameters we want to pass to each collection component.

This may need to be done with HTTP headers and implementation with vulcain and fetching resources in a granular manner must be considered


Fix: Typo

This PR

[x] fixes a small typo

Thanks. This is unbelievable btw: this typo happened because the "N" key on my fancy new macbook keyboard sometimes is stuck or types double..

Thank you, @brendt!
Good luck with the keyboard, hehe!


Streaming encoder

Supersedes #56.
cc @brianm @nox

Wait, no DecodeWriter?

Well, this PR is entitled "Streaming encoder"... ;) One thing at a time. Most of this logic can eventually be shared with a Write that encodes, and there will also eventually be Read impls as well.

@nox does this suit your use case?

Yes!

Codecov Report

Merging #74 into master will decrease coverage by 0.68%.
The diff coverage is 94.44%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   97.31%   96.63%   -0.69%
==========================================
  Files          10       12       +2
  Lines        1044     1368     +324
==========================================
+ Hits         1016     1322     +306
- Misses         28       46      +18

Impacted Files
Coverage Δ

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/write/encoder.rs
86.41% <86.41%> (ø)

src/write/encoder_tests.rs
97.11% <97.11%> (ø)

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 0794fc6...37e8402. Read the comment docs.

Yea!

This may be broken.
https://github.com/servo/servo/pull/22147#issuecomment-437341675

Looking into it

@marshallpierce found out that the problem is probably in the png crate, which uses io::Write::write without checking how many bytes were actually written.
I've opened https://github.com/PistonDevelopers/image-png/pull/94. There is no issue with the base64 crate AFAICT.


How to open document reference directly from VStudio!

Hi!
When typing a function name, I need more information about that function. How to open document about current function on mouse cursor by shortcut key.
Example: Ctrl + ' in Unity Editor

Check out the Visual Studio documentation at https://docs.microsoft.com/visualstudio/


Unicode problems in Windows (3.4)

Editor content is not saved properly. Unicode characters are misinterpreted.

Zřřsxááá - ok
Zář => ZáY
Hypothesis (confirmed): if western special char (á, í,...) come before the first central-european one (ř, č, ň), it fails. Otherwise, it works.
It is not dependent on the editor widget being used, standard qt and pyqode do the same thing.

Unfortunately, str and QString are automatically converted :-(

Anaconda 2.4.1 fixes this.


Update autofill to 11.0.0

Task/Issue URL: https://app.asana.com/0/1207036666985255/1207036666985255
Autofill Release: https://github.com/duckduckgo/duckduckgo-autofill/releases/tag/11.0.0
Description
Updates Autofill to version 11.0.0.
Autofill 11.0.0 release notes
What's Changed

It's a major version change, but the API change is only affecting Android.
Android: enable iframe support by @GioSensation in https://github.com/duckduckgo/duckduckgo-autofill/pull/536

Full Changelog: https://github.com/duckduckgo/duckduckgo-autofill/compare/10.3.0...11.0.0
Steps to test
This release has been tested during autofill development. For smoke test steps see this task.

Superseded.


Markdown content with custom slug fails to resolve relative links ("error Docusaurus found broken links!")

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
yarn build fails with error Docusaurus found broken links! if a markdown docs page with custom slug has a relative link in it.
Steps to reproduce

Add classic preset with docs enabled, like so:  docs: {
    routeBasePath: '/',
    path: 'content'
}

Add two  docs:

content/01-ch1/01-sec1.mdx:---
slug: '/'
---

hi - this is the landing page!

More good stuff in [sec2](./sec2).

content/01-ch1/02-sec2.mdx:This is chapter1 -> section2.

Expected behavior
Relative paths should not error out, even in case of custom slug.
Actual behavior

Run yarn build:error Docusaurus found broken links!
Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.
Exhaustive list of all broken links found:
- On source page path = /ch1:
  -> linking to ./sec2 (resolved as: /sec2)

NOTE1: This does not seem to be a problem with a slug referring to a different path. It still errors out if slug: /ch1/
NOTE2: It stops complaining, if I use the absolute path /ch1/sec2.
Your environment

Public source code: https://github.com/Domiii/dbux/blob/docs/docs/content/04-tools-and-configuration/00-architecture-overview.mdx
Public site URL: (not deployed yet)
Docusaurus version used: 2.0.0-beta.13
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node@16+
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows 10

Reproducible demo
No response
Self-service

[X] I'd be willing to fix this bug myself.

Relative links are only file paths when they end in .md or .mdx—we don't try to guess if you mean file paths or URL paths if the extension is not present because ./sec2 is also a valid URL. You should use full Markdown path: ./02-sec2.md

@Josh-Cena If this is not supposed to work at all, why does it work if slug is not present on the file?

If you don't have a custom slug, then the two files are served with the same base path: /ch1/sec1 and /ch1/sec2. When you write a URL like ./sec2 your browser resolves that to /ch1/sec2. This is not a file path.

I am not sure I understand what you are saying. The /ch1/sec2 path exists and works fine. In fact, all paths work just fine.
The problem is only with sec1's complaining about the path not existing, even though I can link to it from any other file just fine.

Sorry, was having dinner, didn't explain it clear enough.
In Docusaurus, there are two types of paths: file paths and URL paths. File paths are what exist on your system; URL paths are what your site's visitors see in their browser.
Without extra configuration, they usually map very intuitively:

docs/ch1/sec1.md => /docs/ch1/sec1
docs/ch1/sec2.md => /docs/ch1/sec2

What slug does is that it manually sets the URL.

docs/ch1/sec1.md (slug: /) => /docs
docs/ch1/sec2.md => /docs/ch1/sec2

A key observation is that these two path systems are idempotent: .. goes one level above, . stays on the current level, ./slug goes to a slug subpath. If you are given a path, you have no way to tell if it's a file path or URL path.
So, how should you link pages? As implied in my previous response in #6208, Docusaurus wants to prioritize using file paths over URLs in general, because editors can help you update file references during refactoring, but URLs are a downstream feature. Therefore, in ch1/01-sec1.md, if you write [link](./02-sec2.md), Docusaurus understands that this is a file path, and automatically converts that to a URL path for you.
However, if you write [link](./sec2), does Docusaurus know that this is a file path? No, because link is, in fact, a common pattern to link to another page, compared to link which is very unlikely to happen (.md files aren't present in the build output; they are converted to .html files). Therefore, Docusaurus sees this as a URL and leaves it as-is.
So, what page does link link to? We go back to your page's URL. Because you have set slug: /, docs/ch1/sec1.md is now mapped to http://example.com/docs. By the argument that URL paths are idempotent in behavior, ./sec2 will be resolved as http://example.com/docs/sec2 by the browser (remember: all this happens on the client side!), which is, well, a non-existent path.
How should you solve it? If you want to use file paths, explicitly tell Docusaurus that it's a file path by adding the extension: [link](./02-sec2.md). If you want to use URL paths, make sure it resolves correctly: [link](./ch1/sec2).
Does that clear up some doubts?

Also, you could ask in our Discord server first if there's anything not working: https://discord.com/invite/docusaurus
We can help you figure out if it's a bug first, so we don't clog the GitHub issue tracker.

Again, @Josh-Cena. Your help has been much appreciated!
I will heed your advice and take further issues to Discord first. Thanks for the invite!

@Josh-Cena Again, thanks for the elaborate answer!
I guess, explaining how files and URL resolution works was not necessary. The main piece of information I was missing seems to be this:

What slug does is that it manually sets the URL.

docs/ch1/sec1.md (slug: /) => /docs

That implies that the slug config override just wipes default URL resolution.
In order to fix my problems, I had to change all relative paths of the folder, to be relative to the root instead. Meaning that ./sec2 needs to be changed to ./ch1/sec1.
Some final thoughts:
To my mind, relative URL resolution should be relative to the file, not relative to the slug override. This current approach is somewhat non-intuitive.
I understand that file and URL resolution is different from another, and what I'm asking for is basically partially mixing the two.
Maybe, as a middleground, slug changing relative link behavior should be mentioned on https://docusaurus.io/docs/docs-introduction?

URLs will never be relative to the file. When your file has been turned to HTML pages, how does the browser know what the original path is like? You are missing the key part here: file path is server-side, URL path is client-side. The server knows about the client because it builds the client, but the client is ignorant about the server. That's what I mean by saying that "URL is downstream".
And that's exactly the reason why I said you should use MD links instead of URL links. Changing the routes can lead to unexpected broken links.

As I said: I agree, that fixing the behavior is not an easy feat. My argument does not go against the difficulty of the technical implementation. As I said: I agree that this is not easy to change.
But from a documentation editor perspective, it is odd:
[a](b/c/d) behaves one way if slug is set, and another if it is not set.
I still think, It would be best if it would at least be mentioned in the slug documentation, no?
I guess, your argument is that, in general, relative urls should not be used. I can now agree with that. Using file-based linking also has the advantage that VSCode (or other IDEs) can easily track and fix them when files change.

I hope you understand what I had been emphasizing above. b/c/d is not a file path, it's a URL path and it's up to the browser to decide what it resolves to. You should expect it to behave differently when slug is set because the routing has been changed.
URL links, relative or absolute, can still be useful in many cases because file links currently only work when you link files within one plugin. This might be fixed in the future.

I still think, It would be best if it would at least be mentioned in the slug documentation, no?

Mmm, we can. I've actually explained to multiple people about how routing works. I kind of added some details here: https://docusaurus.io/docs/next/docs-introduction#docs-only-mode but ultimately I think it would be useful to have a centralized place where we talk about all things related to routing: routeBasePath, conflicting routes, slugs, file path => URL path, relative / absolute URLs... If you want to take the first step, PR welcome

Agree that users generally struggle with our routing system. The docs-only mode also makes it even more confusing as you have to combine routeBasePath + slug to set a doc as your homepage. I've seen recently a live stream where a user struggled, also encountered the "onBrokenLinks" error after changing a slug, and wasn't sure how to fix it.
In this case, however, we didn't invent anything, and relative links are relative to the current page they appear in, it's just how the web works. Just write 2 HTML files locally in different folders and test for yourself.
That's also why we tend to recommend using relative file paths:
https://docusaurus.io/docs/next/docs-markdown-features

@slorber  About my "togglable warning" recommendation - the idea is to pop up a warning if it is a relative link under "certain circumstances". E.g., in my case I should not try to link to my docs content pages. But I can see that there might be a lot more obscure cases that would not be easily detected automatically.
Maybe just a more blanket warning in case of any links that the server-side URL parser fails to be able to link to a file?
I am not quite sure I understand the entire system. My guess is that the server parses all URLs and tries to convert them if they match certain patterns, e.g. they don't directly map to a file. I am referring to the "conversion" process that @Josh-Cena mentioned:

in ch1/01-sec1.md, if you write link, Docusaurus understands that this is a file path, and automatically converts that to a URL path for you.

I guess, it would be an extension of onBrokenLinks: but instead of triggering for broken links, it would trigger, if the link is relative and cannot be directly mapped to a file.... maybe?

We already emit a warning for all links ending with .md or .mdx that we couldn't resolve. All other links are left untouched and added as is to the final HTML, so it's your responsibility to be sure your own links work.
We can't add warnings everywhere, because in the end, using relative links is something legit to do, that some users currently use in production. Do we really want to show them new unwanted warnings while their system is working? I don't know, but if you have a warning in mind, please give a very concrete example of what to display to the user, under which circomstances

@slorber I agree. My last comment was not sufficiently concise, and also tried to over-engineer things.
Ultimately, it is probably easiest to go with Josh's idea:

I think it would be useful to have a centralized place where we talk about all things related to routing: routeBasePath, conflicting routes, slugs, file path => URL path, relative / absolute URLs

And then, crucially, add a link to the onBroken*Links warning/error message, and it would probably fix the problem of people (like myself) not knowing what they did wrong :)


Readme recommends TypeScript Vue Plugin (Volar) and take over mode seems already discarded.

The readme recommends
TypeScript Vue Plugin (Volar) and take over mode already discarded, Nowadays the Vue recommends is Vue - Official plugin.
Could you update it, thanks!

Updated recommendations

Please leave me a star


feat!: Encapsulation

Description

Makes encapsulation the default pattern for handling data in all Substation applications and public APIs (see changes in /config/)

Adds backwards compatible functions for handling non-encapsulated data

Adds AWS Firehose sink support
Adds AWS SQS source and sink support
Adds context support condition API
Updates code style of public APIs

This is a non-breaking change for ITL applications and a breaking change for the public APIs.
Motivation and Context
The motivation for adding encapsulation was the need to let users simultaneously handle both data (structured or unstructured) and metadata. This has two advantages:

sources can add metadata when data is ingested
metadata can be tracked alongside unstructured (e.g., binary) data

This change means that users can now access and interpret information only the source application knows; for example:

substation/file: the filename and file size of the source file that data is read from
substation/aws/kinesis: the Kinesis stream data is delivered by and approximate arrival time of data
substation/aws/s3: the S3 bucket and object that data is read from

It also provides total separation of metadata from data, which is most useful in sink applications; for example:

http: storing HTTP headers as metadata instead of in the data object
s3: storing the S3 prefix as metadata instead of in the data object
sumologic: storing the category as metadata instead of in the data object

This gives us some flexibility for growth in the future. For example, instead of relying on configured settings for Kinesis streams and S3 buckets, we can add features to let users dynamically apply these from metadata.

How Has This Been Tested?

All public APIs had their unit tests updated
Firehose and SQS features were tested in a development AWS account

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Go lint is failing due to an unavoidable issue mocking an SQS API call for a unit test. The fix for this is to stop using golint (it's deprecated) and switch to staticcheck (recommended replacement), we'll handle that in a different PR.


SFC tests for mount + more

This PR should complete the task of duplicating all relevant class-based component tests to also include stateless function components.
Happy to squash commits if everything looks good.
Related to issue #261

Pending my one comment, this LGTM. Thanks for doing this work!

This looks great @gm758 👍

@ljharb How's that look? pretest gets rid of the need for npm run lint in test, check already runs the linter, so no need to run it in test:all

@gm758 looks great, thanks! It'll just need a fresh rebase on top of master :-)

Should be good to go

Thanks for the great work @gm758!


The latest version of az cli (2.30.0) break while running az commands

azure-cli 2.30.0 throws ERROR: {'Error': TypeError("init() got an unexpected keyword argument 'async_persist'",)} while running the pipeline: dstoolkit-mlops-base/invoke-aml-pipeline.template.yml at main · microsoft/dstoolkit-mlops-base (github.com)
As a workaround, we found that the az cli 2.30.0 will install azure-cli-ml version 1.5.0 as default
{
"experimental": false,
"extensionType": "whl",
"name": "azure-cli-ml",
"path": "/opt/az/azcliextensions/azure-cli-ml",
"preview": false,
"version": "1.5.0"
}
We need to downgrade the azure-cli 2.29.2 and the azure-cli-ml version 1.33.1 is installed correctly.

Original issue for reference: https://github.com/Azure/azure-cli/issues/20297

Change pool version from ubuntu-latest to ubuntu-18.04 because of this error:
File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/dotnetcore2/runtime.py", line 279, in attempt_get_deps

raise NotImplementedError(err_msg + '\n' + _unsupported_help_msg)

NotImplementedError: Linux distribution ubuntu 20.04 does not have automatic support.

.NET Core 2.1 can still be used via dotnetcore2 if the required dependencies are installed.

Visit https://aka.ms/dotnet-install-linux for Linux distro specific .NET Core install instructions.

Follow your distro specific instructions to install `dotnet-runtime-*` and replace `*` with `2.1`.

Downgrade the azure-devops 0.21.0 due to this error:
The 'azure-devops' extension version 0.22.0 is not compatible with your current CLI core version 2.29.2.

This extension requires a min of 2.30.0 CLI core.

The most recent SDK version (1.43.0) fixes this:

ADAL authentication is now deprecated and all authentication classes now use MSAL authentication. Please install azure-cli>=2.30.0 to utilize MSAL based authentication when using AzureCliAuthentication class.

We can now try reverting back to unpinned versions


Source code link doesn't work

The source code link on http://www.beanshell.org/developer.html to file http://www.beanshell.org/bsh-2.0b4-src.zip does not work. The response is a 404 (not found).
Reported by: jaydunning
Original Ticket: "beanshell/bugs/281":https://sourceforge.net/p/beanshell/bugs/281

This has been fixed now. Thanks!


Remove "today's date" next to birthdate field in child and family records

this is an update to the Keystone.js codebase, and while it's not a correct implementation, there's a pull request that attempted to do this already: https://github.com/keystonejs/keystone/pull/4499


support polygonbound

use this algorithm to determining whether a point is inside a complex polygon

Thanks for the PR!
Would you mind filling out the CLA? http://druid.io/community/cla.html
(The CLA for Druid is a Metamarkets one)

Please use the style mentioned in https://github.com/druid-io/druid/blob/master/CONTRIBUTING.md

The link to the algorithm in the master comment seems broken, can you please fix the link?

sorry i put an error link. i have fixed it.

@scusjs Radius and Rectangular bounds both count boundary points as part of the Bound. But http://alienryderflex.com/polygon/ notes

If the test point is on the border of the polygon, this algorithm will deliver unpredictable results; i.e. the result may be “inside” or “outside” depending on arbitrary factors such as how the polygon is oriented with respect to the coordinate system

This change in behavior from the existing Bound rules is not documented.
com.metamx.collections.spatial.search.Bound notably lacks an explicit contract on what the expected behavior is in such a case, but in this scenario I would expect implementations to behave in a similar fashion.

https://groups.google.com/d/msg/druid-development/cHi-1TDJ4iQ/d4lku-yhBQAJ As per that discussion, and barring other feedback on the matter, I think its ok to have implementation defined boundary conditions.

👍  Needs cache key fix (see https://github.com/metamx/bytebuffer-collections/pull/34 for related) but I can add that in

Thanks!


Fix/2122 create connection in merlin should NOT be Code for IBM i dialog

Instead the action on the Project Explorer view title should take you to the Connection Browser
Fixes issue 272

@edmundreinhardt The version in types/package.json should also always be updated when updating the root package.json

@edmundreinhardt The version in types/package.json should also always be updated when updating the root package.json

Yes, I forgot last time, so I am catching up this time.


Consider increasing styling width when we render MigMigration phase statuses

You can see here how there is more room to expand but the
'e' from 'Stage'
'd' from EnsureAnnotationsDeleted
are wrapped to next line

Another view
Looks like there is some more room for MigrationTable we could expand into?

Notice how Failed is displayed one character per line in below

Fixed in #434, Derek bumped width from 6->9. Should fit much cleaner.


Ban rate?

The title explain all (a friend told me this question... i use in my first acc since 3 month ago and i never get banned THANKS R3zn)

Riot already stated they dont ban Skin Changers. They dont bother with it since it doesnt give the player any advantages.
They ban custom skins though. Skin Mods that messes with League's files are likely to get you banned, but a simple Skin Changer isn't.
Been using Skin Changers since 2018 and never had a ban.
https://support-leagueoflegends.riotgames.com/hc/en-us/articles/225266848-Third-Party-Applications

Riot already stated they dont ban Skin Changers. They dont bother with it since it doesnt give the player any advantages.
They ban custom skins though. Skin Mods that messes with League's files are likely to get you banned, but a simple Skin Changer isn't.
Been using Skin Changers since 2018 and never had a ban.
https://support-leagueoflegends.riotgames.com/hc/en-us/articles/225266848-Third-Party-Applications

Thanks for solving my issue. I'll send it to my friend

Thanks for solving my issue. I'll send it to my friend


NWTC_Lib: Adding Yaml and VTK to library (moved from SD and AD)

This pull request is ready to be merged
Feature or improvement description
This pull request moves the VTK.f90 and Yaml.f90 files which were respectively stored in AeroDyn and SubDyn.
I believe these modules fit within the "NWTC library" as they deal with generic IO operations.
Both AeroDyn and WakeDynamics have dependencies on VTK.f90.
Only SubDyn depends on Yaml.f90 for now, but I think it would be valuable to write the BeamDyn summary file in Yaml format, and the HydroDyn linearized matrices in that format too, so that their output can more easily be parsed (it's human and machine readable).
I'm happy to hear from @bjonkman as well if these changes are fine.
Impacted areas of the software
NWTC lib
Test results, if applicable
No change of tests
Example usage
Typical usage of the YAML library:
   call yaml_write_var  (UnSum, 'Mass', 10      , 'ES15.6E2', ErrStat2, ErrMsg2, comment='Total Mass')
   call yaml_write_list (UnSum, 'ID'  ,(/1,2,5/), 'I3'      , ErrStat2, ErrMsg2)
   call yaml_write_array(UnSum, 'Rib' , eye(3)  , 'ES15.6E2', ErrStat2, ErrMsg2, comment='Transformation matrix')

Should produce the following output:
Mass:    1.000000E+01 # Total Mass
ID: [  1,  2,  5]
Rib: # 3 x 3 Transformation matrix
  - [   1.000000E+00,   0.000000E+00,   0.000000E+00]
  - [   0.000000E+00,   1.000000E+00,   0.000000E+00]
  - [   0.000000E+00,   0.000000E+00,   1.000000E+06]

Typical usage of the VTK libray:
    call vtk_misc_init(mvtk) ! initialize vtk options
    ! Open VTK file write data for points and cells
    if ( vtk_new_ascii_file(filename, '', mvtk)) then
        call vtk_dataset_polydata(Points, mvtk) ! Points
        call vtk_quad(Connectivity, mvtk)       ! Connectivity table
        call vtk_cell_data_init(mvtk)           ! Initialize cell data (defined by connectivity)
        call vtk_cell_data_scalar(CellValues, 'Gamma', mvtk) ! Scalar value per cell
        call vtk_point_data_init(mvtk)           ! Initialize point data
        call vtk_point_data_vector(PointDataVec, 'Vel', mvtk) ! Vector data per point
     endif
     ! Open VTK file write data for structured points (e.g. plane, 3d grids)
    if ( vtk_new_ascii_file(filename2, '', mvtk)) then
        call vtk_dataset_structured_points((x0, y0, z0/), (/dx, dy, dz/), (/nx,ny,nz/), mvtk)
        call vtk_point_data_init(mvtk) ! Initialize point data
        call vtk_point_data_scalar(Vx, 'Vx', mvtk)  ! Scalar data on grid points
     endif

Do we need to include use vtk and use yaml statements in the NWTC_Library.f90 file, or do we just want to lump these module into the library and require explicit use statements in the code for them?

So far I've put the modules outside of the "library module", but inside the library.
I'm fine putting it into the module as well. I will just have to update of couple of vfproj and remove the "use VTK" and "use YAML" statements.

@bjonkman do you have an opinion on whether these should be integrated into the library module?

I like having these routines contained in the NWTC_Library directory.
I could go either way on having them in the NWTC_Library module. If they were linking with or using other (external) modules, I would say to just keep them separated. Do you have plans to link with any other standard yaml or vtk libraries in the future? (I haven't looked what kind of standard libraries there are, though I've used C/C++ versions in other projects.) What about the existing ReadVTK_* and WrVTK_* subroutines that are in NWTC_IO.f90?
One comment about the YAML Write Array 2D routines: it seems like they have optional arguments to output as json format. I'd be inclined to make separate subroutines for the json formats so that the routines always write yaml format, as their names indicate.

Thanks Bonnie for the feedback.
I think it will make sense to add the ReadVTK_ and WriteVTK routines to VTK.f90.
I agree that it's nice to put the JSON routines separately. I think it might make sense to put this into JSON.f90 (comparing the YAML.f90 and JSON.f90 would then be easy, as I expect some similar code between the two.
I'll try to do that this afternoon.

@ebranlard: FYI, it is possible that the ModMesh.f90 routines that write meshes to VTK may use those routines, so moving them into VTK.f90 might require putting module VTK in module NWTC_Library.

Hi @bjonkman , yes, I'm currently noticing that.
We could:

put the header and footer VTK writer to modmesh
or have modmesh depend on VTK.

I've put the WrWTK_* and ReadVTK* routines into VTK.
Now ModMesh requires VTK, which means VTK is part of the NWTC_Library somehow. I personally don't mind explicit imports (like use VTK instead of use NWTC_Library).
YAML, JSON, and VTK depends on NWTC_IO.
I've done explicit imports at the beginning of these modules, let me know if you don't like that. I like it because it makes it clearer what the module relies on, see here:
https://github.com/ebranlard/openfast/blob/f/nwtc-io-libs/modules/nwtc-library/src/JSON.f90#L21
https://github.com/ebranlard/openfast/blob/f/nwtc-io-libs/modules/nwtc-library/src/VTK.f90#L7
https://github.com/ebranlard/openfast/blob/f/nwtc-io-libs/modules/nwtc-library/src/YAML.f90#L21
If you have some quick feedback, I'm happy to include it. Otherwise, I'll like to move on, and let you free to rearrange this in future pull requests.


Improve ockam enroll —-help text by adding doc comment for identity flag (clap command)

Context
When a user types ockam enroll —-help in their terminal, they are presented with long help text. You can improve this text content by adding the help information for --identity, which is currently missing.

To install Ockam command from a prebuilt binary or from source, please take a look at this README.md.

Current behavior

When you run ockam enroll --help in your terminal you will see the following help text.

Suggested fix
A doc comment needs to be added to the EnrollCommand::identity field.
/// Existing identity identifier to enroll

File that needs to be modified: /src/enroll/command.rs#L39.
Once the fix is applied, it should look like the following.

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

Hi @nazmulidris is this issue still opened?

@Lumexralph That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.gg/RAbjRr3kds

@Lumexralph Hi 👋 Just checking to see if you are still interesting in working on this issue.

A PR has been made already, I think it was merged, not sure


Build Postgres 9.6 images in addition to 13.4

This PR https://github.com/CircleCI-Public/cimg-postgres/pull/20 made some changes and as part of it, rebuilt 9.6 images. But then the changes were backed out in this PR https://github.com/CircleCI-Public/cimg-postgres/pull/22 due to issues. The back out change also removed the build commands for postgres 9.6 which resulted in just 13.4 getting rebuilt which undid the changes whereas 9.6 stuck with broken builds.
I am seeing error saying Postgres can't connect to Postgres Unix socket, same as here https://github.com/CircleCI-Public/cimg-postgres/issues/17#issuecomment-970113236
This PR adds those commands to rebuilt 9.6 images as well so users of Postgres 9.6 also have a working image.

Hi. I wish I saw this sooner. #24 has been merged which will hopefully fix this issue.
JUST IN CASE there's still a problem and/or another revert is needed, I'm going to leave this PR open.

Also, this PR didn't run because you are "not authorized". So I just ran the branch manually so we can see what the status will be.

@felicianotech This PR was supposed to be a temporary fix to ensure a 9.6 image was built after the changes were reverted.
To fix test pipelines that were failing due to postgres image, we built the image ourselves using the reverted 9.6 Dockerfile and hosted it in our docker hub account.
Just did a quick test, and it fails with same error message as before. Full log
********************************************************************************
WARNING: POSTGRES_HOST_AUTH_METHOD has been set to "trust". This will allow
         anyone with access to the Postgres port to access your database without
         a password, even if POSTGRES_PASSWORD is set. See PostgreSQL
         documentation about "trust":
         https://www.postgresql.org/docs/current/auth-trust.html
         In Docker's default configuration, this is effectively any other
         container on the same system.

         It is not recommended to use POSTGRES_HOST_AUTH_METHOD=trust. Replace
         it with "-e POSTGRES_PASSWORD=password" instead to set a password in
         "docker run".
********************************************************************************
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... Etc/UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....LOG:  database system was shut down at 2021-11-23 13:07:24 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
 done
server started
psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
LOG:  received SIGHUP, reloading configuration files
LOG:  parameter "listen_addresses" cannot be changed without restarting the server
LOG:  configuration file "/var/lib/postgresql/data/postgresql.conf" contains errors; unaffected changes were applied

Exited with code 2

CircleCI received exit code 2

The image circle pulled at the start of the job
cimg/postgres:9.6.23:
  using image cimg/postgres@sha256:7084fe94f492a9519553d17eabe3cd6ed6de3ee9b3a22032070d1f0f8861cd85
  pull stats: Image was already available so the image was not pulled
  time to create container: 124ms

This is the image that was built about 14 hours ago https://hub.docker.com/layers/cimg/postgres/9.6.23/images/sha256-7084fe94f492a9519553d17eabe3cd6ed6de3ee9b3a22032070d1f0f8861cd85?context=explore by this job https://app.circleci.com/pipelines/github/CircleCI-Public/cimg-postgres/62/workflows/e6323b1f-9944-4f5b-80ff-2220d97ea705/jobs/58
I was able to reproduce the same error with just docker run command as well
docker run cimg/postgres:9.6.23

Closing in favor or recent PRs.
@nirojan Can you confirm that with a fresh build, your pipeline works now?
v9.6.22 should be ready and v9.6.23 will be updated within an hour or so.


Render the specific component via blazor service

Is your feature request related to a problem? Please describe.
I want to render the specific component via the services. Is this possible in blazor? please suggest me on this.
Describe the solution you'd like
Actual requirement,
I have two components, namely 'Index.razor' and 'Comp1.razor'.
In default the blazor render the 'Index.razor' at initial load. But in that initial load, i want to show the 'Comp1.razor' component over the 'Index.razor'.
Need 'Comp1.razor' component overlayed on the 'Index.razor'.
How can i implement this ?
Additional context
I have used latest Core SDK 3.1 preview3 and blazor server application

@kmuthukumar23 thanks for contacting us.
We are not sure we understand your scenario. Could you provide more details on what you are trying to accomplish and how? A sketch of the code you would write and what you would like/expect to happen would help us understand your scenario.

Hi @javiercn thanks for your update.
I will create the sample regarding this and update you.
i have an one doubt regerding blazor component rendering.
is possible to render the component from .cs file.
exact need is render the razor component from .cs file.
Thanks


access member

[Enter feedback here]

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

ID: 8121f526-cfe4-091d-d031-2cdc274cd8ee
Version Independent ID: 76a389f6-b568-3568-6483-6df440f96f0c
Content: Access Modifiers - C# Programming Guide
Content Source: docs/csharp/programming-guide/classes-and-structs/access-modifiers.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Hi @Sothyrak99
Do you have a question about this content? If so, can you elaborate here?


V0.20.84 dev

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This was just a test to check the builds for the next data release. I am closing this merge request now.