💅 Biome encountered an unexpected error when setting noExplicitAny=off in an override in CLI

Environment information
CLI:
  Version:                      1.4.1
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.18.2"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/9.8.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

Rule name
noExplicitAny, but seems to happens with other rules when includes is used
Playground link
Expected result
No errors when running the CLI.
I get this:
Biome encountered an unexpected error
This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:
Source Location: crates/biome_service/src/configuration/linter/mod.rs:167:18
Thread Name: biome::worker_6
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here
Biome encountered an unexpected error
This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:
Source Location: crates/biome_service/src/configuration/linter/mod.rs:167:18
Thread Name: biome::worker_1
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here
./test/dev/devChildTask/dev-child-task.test.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━
✖ processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here
⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

This should be fixed in the next release.

Still getting this error in 1.5.1. Other disables work, noExplicitAny errors.
  ✖ processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

Got the same issue withlint/performance/noDelete:
"overrides": [
    {
      "include": ["*.spec.ts", "*.spec.tsx"],
      "linter": {
        "rules": {
          "performance": {
            "noDelete": "off"
          }
        }
      }
    }
  ]

or even with an empty rules-object:
"overrides": [
    {
      "include": ["*.spec.ts", "*.spec.tsx"],
      "linter": {
        "rules": {}
      }
    }
  ]

We are using biome 1.5.2.

Use our Codesandbox template: https://codesandbox.io/p/sandbox/biome-starter-cbs-rky6zq

Use our Codesandbox template: https://codesandbox.io/p/sandbox/biome-starter-cbs-rky6zq

Thank you! Here it is: https://codesandbox.io/p/devbox/divine-waterfall-wqglgc Just run npm run check in terminal.
Output

➜  /workspace git:(master) npm run check

><EMAIL_ADDRESS>check
> biome check ./src

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates/biome_service/src/configuration/linter/mod.rs:186:18
Thread Name: biome::worker_0
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

./src/utils.spec.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

Checked 2 file(s) in 2ms

I ran into a similar issue, but instead I'm enabling a rule in an override. The rule is otherwise turned off.

config
{
  "$schema"<EMAIL_ADDRESS>  "files": {
    "ignore": [
      "./.cache/**/*",
      "./coverage/**/*",
      "./node_modules/**/*",
      "./translations/**/*"
    ]
  },
  "formatter": {
    "ignore": ["*.ts", "*.tsx"],
    "indentStyle": "space"
  },
  "json": {
    "parser": {
      "allowComments": true
    }
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "single",
      "trailingComma": "none"
    }
  },
  "linter": {
    "rules": {
      "recommended": false,
      "a11y": {
        "noAccessKey": "warn",
        "noAriaHiddenOnFocusable": "warn",
        "noAriaUnsupportedElements": "warn",
        "noAutofocus": "off",
        "noBlankTarget": "warn",
        "noDistractingElements": "warn",
        "noHeaderScope": "warn",
        "noInteractiveElementToNoninteractiveRole": "warn",
        "noNoninteractiveElementToInteractiveRole": "warn",
        "noNoninteractiveTabindex": "off",
        "noPositiveTabindex": "warn",
        "noRedundantAlt": "warn",
        "noRedundantRoles": "warn",
        "noSvgWithoutTitle": "off",
        "useAltText": "warn",
        "useAnchorContent": "warn",
        "useAriaActivedescendantWithTabindex": "warn",
        "useAriaPropsForRole": "warn",
        "useButtonType": "warn",
        "useHeadingContent": "warn",
        "useHtmlLang": "warn",
        "useIframeTitle": "off",
        "useKeyWithClickEvents": "off",
        "useKeyWithMouseEvents": "warn",
        "useMediaCaption": "off",
        "useValidAnchor": "off",
        "useValidAriaProps": "warn",
        "useValidAriaRole": "warn",
        "useValidAriaValues": "warn",
        "useValidLang": "warn"
      },
      "complexity": {
        "noBannedTypes": "warn",
        "noExcessiveCognitiveComplexity": "off",
        "noExtraBooleanCast": "warn",
        "noForEach": "off",
        "noMultipleSpacesInRegularExpressionLiterals": "warn",
        "noStaticOnlyClass": "warn",
        "noThisInStatic": "warn",
        "noUselessCatch": "warn",
        "noUselessConstructor": "warn",
        "noUselessEmptyExport": "warn",
        "noUselessFragments": "warn",
        "noUselessLabel": "warn",
        "noUselessRename": "warn",
        "noUselessSwitchCase": "warn",
        "noUselessThisAlias": "warn",
        "noUselessTypeConstraint": "warn",
        "noVoid": "warn",
        "noWith": "warn",
        "useArrowFunction": "warn",
        "useFlatMap": "warn",
        "useLiteralKeys": "warn",
        "useOptionalChain": "warn",
        "useRegexLiterals": "warn",
        "useSimpleNumberKeys": "warn",
        "useSimplifiedLogicExpression": "off"
      },
      "correctness": {
        "noChildrenProp": "off",
        "noConstAssign": "warn",
        "noConstantCondition": "warn",
        "noConstructorReturn": "warn",
        "noEmptyCharacterClassInRegex": "warn",
        "noEmptyPattern": "warn",
        "noGlobalObjectCalls": "warn",
        "noInnerDeclarations": "warn",
        "noInvalidConstructorSuper": "warn",
        "noInvalidNewBuiltin": "warn",
        "noNewSymbol": "warn",
        "noNonoctalDecimalEscape": "warn",
        "noPrecisionLoss": "warn",
        "noRenderReturnValue": "warn",
        "noSelfAssign": "warn",
        "noSetterReturn": "warn",
        "noStringCaseMismatch": "warn",
        "noSwitchDeclarations": "warn",
        "noUndeclaredVariables": "off",
        "noUnnecessaryContinue": "warn",
        "noUnreachable": "warn",
        "noUnreachableSuper": "warn",
        "noUnsafeFinally": "warn",
        "noUnsafeOptionalChaining": "warn",
        "noUnusedLabels": "warn",
        "noUnusedVariables": "off",
        "noVoidElementsWithChildren": "warn",
        "noVoidTypeReturn": "warn",
        "useExhaustiveDependencies": "warn",
        "useHookAtTopLevel": "warn",
        "useIsNan": "warn",
        "useValidForDirection": "warn",
        "useYield": "warn"
      },
      "performance": {
        "noAccumulatingSpread": "warn",
        "noDelete": "warn"
      },
      "security": {
        "noDangerouslySetInnerHtml": "warn",
        "noDangerouslySetInnerHtmlWithChildren": "warn"
      },
      "style": {
        "noArguments": "warn",
        "noCommaOperator": "warn",
        "noDefaultExport": "off",
        "noImplicitBoolean": "off",
        "noInferrableTypes": "warn",
        "noNamespace": "warn",
        "noNegationElse": "off",
        "noNonNullAssertion": "off",
        "noParameterAssign": "off",
        "noParameterProperties": "warn",
        "noRestrictedGlobals": "warn",
        "noShoutyConstants": "warn",
        "noUnusedTemplateLiteral": "warn",
        "noUselessElse": "warn",
        "noVar": "warn",
        "useAsConstAssertion": "warn",
        "useBlockStatements": "off",
        "useCollapsedElseIf": "warn",
        "useConst": "warn",
        "useDefaultParameterLast": "off",
        "useEnumInitializers": "warn",
        "useExponentiationOperator": "warn",
        "useFragmentSyntax": "warn",
        "useLiteralEnumMembers": "warn",
        "useNamingConvention": "off",
        "useNumericLiterals": "warn",
        "useSelfClosingElements": "warn",
        "useShorthandArrayType": "warn",
        "useShorthandAssign": "warn",
        "useSingleCaseStatement": "off",
        "useSingleVarDeclarator": "warn",
        "useTemplate": "warn",
        "useWhile": "warn"
      },
      "suspicious": {
        "noApproximativeNumericConstant": "warn",
        "noArrayIndexKey": "off",
        "noAssignInExpressions": "off",
        "noAsyncPromiseExecutor": "warn",
        "noCatchAssign": "warn",
        "noClassAssign": "warn",
        "noCommentText": "warn",
        "noCompareNegZero": "warn",
        "noConfusingLabels": "warn",
        "noConfusingVoidType": "warn",
        "noConsoleLog": "warn",
        "noConstEnum": "warn",
        "noControlCharactersInRegex": "warn",
        "noDebugger": "warn",
        "noDoubleEquals": "warn",
        "noDuplicateCase": "warn",
        "noDuplicateClassMembers": "warn",
        "noDuplicateJsxProps": "warn",
        "noDuplicateObjectKeys": "warn",
        "noDuplicateParameters": "warn",
        "noEmptyInterface": "warn",
        "noExplicitAny": "warn",
        "noExtraNonNullAssertion": "warn",
        "noFallthroughSwitchClause": "warn",
        "noFunctionAssign": "warn",
        "noGlobalIsFinite": "warn",
        "noGlobalIsNan": "warn",
        "noImplicitAnyLet": "off",
        "noImportAssign": "warn",
        "noLabelVar": "warn",
        "noMisleadingInstantiator": "warn",
        "noMisrefactoredShorthandAssign": "warn",
        "noPrototypeBuiltins": "warn",
        "noRedeclare": "warn",
        "noRedundantUseStrict": "warn",
        "noSelfCompare": "warn",
        "noShadowRestrictedNames": "warn",
        "noSparseArray": "warn",
        "noUnsafeDeclarationMerging": "warn",
        "noUnsafeNegation": "warn",
        "useDefaultSwitchClauseLast": "warn",
        "useGetterReturn": "warn",
        "useIsArray": "warn",
        "useNamespaceKeyword": "warn",
        "useValidTypeof": "warn"
      }
    }
  },
  "organizeImports": {
    "enabled": false
  },
  "overrides": [
    {
      "include": ["**/*.js"],
      "linter": {
        "rules": {
          "suspicious": {
            "noConsoleLog": "off"
          }
        }
      }
    },
    {
      "include": ["./src/MediaCampaign/**/*"],
      "linter": {
        "rules": {
          "complexity": {
            "noForEach": "warn"
          }
        }
      }
    }
  ]
}

cli output
Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_4
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_15
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_8
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_44
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_2
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_41
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_31
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_35
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_28
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_2
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_30
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_50
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_15
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_45
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_6
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_52
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_13
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_30
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_20
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_15
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_40
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_39
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_2
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_32
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_14
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_28
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_8
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_18
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_0
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_27
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_37
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_26
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_29
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_25
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_32
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_18
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_6
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_22
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_42
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_2
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_11
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_46
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_30
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_16
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_18
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_60
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_25
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_58
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_32
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_59
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_20
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_40
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_9
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_4
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_10
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_13
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_33
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_18
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_35
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_26
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_62
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_14
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_11
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_3
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_61
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_44
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_20
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_17
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_46
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_2
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_54
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_22
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_39
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_40
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_10
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_47
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_0
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_12
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_36
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_49
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_59
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_31
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_42
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_5
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_34
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_26
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_13
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_48
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_21
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_24
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_53
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_38
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_23
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_1
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_35
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_18
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_43
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_45
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_41
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates\biome_service\src\configuration\linter\mod.rs:186:18
Thread Name: biome::worker_55
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

.\src\path\file.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━

  × processing panicked: internal error: entered unreachable code: the rule is turned off, it should not step in here

  ! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.

Checked 1575 file(s) in 90ms

I am working on a fix that will be released at the start of next week.
A temporary workaround is of setting every recommended to false in the overrides.
Foe example:
"overrides": [
    {
      "include": ["*.spec.ts", "*.spec.tsx"],
      "linter": {
        "rules": {
+         "recommended": false,
          "performance": {
+           "recommended": false,
            "noDelete": "off"
          }
        }
      }
    }
  ]

This should now be fixed by the last release: 1.5.3


django env to use pymemcache lib. es backward compatibility on search…

django.env: 'pymemcached://HOST:PORT' For use with the python-memcached library. https://github.com/ghickman/django-cache-url#supported-caches

make search api query builder work with es 1, 2 and 5. tests passes for ES v5.0.0-alpha feature/heatmap branch.

Thanks a lot @panchicore.


Unclear error message when job name or team are not passed correctly.

Describe the bug
When creating my job I used my own team name that was different from the original job’s team name. Then. When I was deploying the job I got an error and it took me a while to figure out what was going on. Vdk was insisting that I did a spelling mistake.
Steps To Reproduce
Steps to reproduce the behavior:

create new job vdk create -n foo -t my-team
configure different team name in config.ini
vdk deploy -p job-dir

We get very confusing error
Expected behavior
Be more explicit with user that team name is wrong
Screenshots

Version  (please complete the following information):
The latest as of 06. December 2021
Additional context
Likely need more granular error handling on "X is NotFound" error directly in teh control service. The user get the message from the control service directly usually so we need to be a bit more explicit.

Triaged. To be retested if it is still valid.


FR: Allow entering host name for ip field

Targets have helpful hostnames, can't enter them.

Targets have fulldeleite hostnames, can't enter them.


Symbol highlighting does not work properly

Hey :)
This is handled by VSCode itself and I think they using simple regular expression to find occurrences of highlighted word.


New release

Hi,
Can you release a new version for integrating latest bugs fixes.
Regards

Done. v0.2.13 is released

Thanks a lot

@PierreRambaud i added you as collaborator.

Thanks, I was planning to get back to my software ;)

Is it possible to have the permission to push gem on rubygems.org? (https://rubygems.org/profiles/PierreRambaud)
Regards

Sure, i can add you.

Pushed latest 0.2.14, also would need your email to add to owners.

here's my email used for rubygems<EMAIL_ADDRESS>

Added, you can now push to rubygems. Use rake release command.


Add external lib to parse date

Since Natty is approved, we can use it to parse deadline and duration.

After trying, found another more developer friendly library called prettytime.
Will look into this rather.


fix(@angular/cli): add '@angular/pwa' in the 'packageGroup'

When using ng update @angular/cli  to update from v6 to v7 with @angular/pwa and npm, even though the @angular/cli can be update to v7 correctly, but the dependencies like @schematics/angular cannot be updated correctly as the old @angular/pwa v0.8.6 still requires
"@angular-devkit/core": "0.8.6",
"@angular-devkit/schematics": "0.8.6",
"@schematics/angular": "0.8.6",

So here add @angular/pwa in the packageGroup to make sure the update is correctly when using with  @angular/pwa

The package actually has no code outside the schematic which only runs on ng add.  There’s no reason to update it and you can actually remove it from the project.

Good, so maybe when ng add should not add it to the package.json


Rshiny App blank screen after build

Hi,
I was using the default R script in the folder to test if it works. I've also installed all the R packages that are required ("shiny", "tidyverse", "plotly", "DT", "lubridate", "reshape2" as examples). However, after running "npm run package-win", and I opened electron-quick-start in ElectronShinyAppWindows folder, I only get a blank screen. I tried to force reload, but only the blank screen remained. I've searched everywhere for a possible solution, but could not find any. Could someone please help?
Thanks.
Best regards,
Hweeling

https://github.com/electron/electron-quick-start/issues/627#issue-1328322816


Update translations in strings.xml (French)

Fix wrong spelling of "Category" in French
Make sure you've done all the following (You can delete the checklist before submitting)

[ ] Apply the AndroidStyle.xml style template to your code in Android Studio.
[ ] Code is well documented
[ ] Include unit tests for new functionality
[ ] All user-visible strings are made translatable
[ ] Code passes Travis builds in your branch
[ ] If you have multiple commits please combine them into one commit by squashing them.
[ ] Read and understood the contribution guidelines .

@raphael0202 please use https://translate.openfoodfacts.org to fix mistakes in translations


Apmeken Wave Helper

I think it would be a good idea to change the wave helper to a infobox that shows the wave number and what monkeys show up in that wave. Fight caves has it aswell so I think it's allowed.

This would be fine now, but was not allowed when I created the feature. I am open to revisiting it.

If anyone can gather information about spawns by party size, I can implement this feature.
The chart I used for the side panel helper is only applicable to solos.

do you still need help with this?

Hey, I wrote a plugin that records which monkeys spawn on which wave, and left it running for about 400 raids, about half group and half solo. The amount of monkeys seems to be the same for all group sizes except solo
Here's the results:
Solo

Wave
Enemies

1
2x Brawler

2
1x Thrower, 1x Mage

3
2x Brawler, 1x Shaman

4
2x Thrower, 1x Volatile

5
2x Mage, 1x Cursed

6
2x Thrower, 1x Volatile, 1x Cursed, 1x Special

7
2x Mage, 1x Volatile, 1x Shaman, 1x Special

8
2x Brawler, 1x Shaman, 1x Cursed, 1x Special

9
1x Brawler, 1x Thrower, 1x Shaman, 2x Cursed

10
1x Shaman, 2x Volatile, 2x Special

Group

Wave
Enemies

1
3x Brawler

2
2x Thrower, 1x Mage

3
3x Brawler, 1x Shaman

4
3x Thrower, 1x Volatile

5
3x Mage, 1x Cursed

6
3x Thrower, 1x Volatile, 1x Cursed, 1x Special

7
3x Mage, 1x Volatile, 1x Shaman, 1x Special

8
3x Brawler, 1x Shaman, 1x Cursed, 1x Special

9
1x Brawler, 1x Thrower, 2x Shaman, 2x Cursed

10
1x Shaman, 3x Volatile, 2x Special

I dumped the wave data into a spreadsheet which you can view here:
https://docs.google.com/spreadsheets/d/1_15wFs_XqOw3AoMO-wjzKluNgbmFdtnHPehj18Gm3O8/edit?usp=sharing
The top table is the cumulative data, bottom table is average amount per raid. The waves that have non-integer averages are due to the specials. It seems that you can determine how many of the non-special monkeys spawn on each wave by the unit value, e.g. solo wave 8 spawns about 1.3 shamans, so there is a guaranteed of 1 shaman on that wave and the 0.3 is from specials, which are distributed by about a third over volatiles, curseds and shamans. I flicked through the data to make sure that this was accurate and seemed so, i.e. there are no wave 8s that didn't have at least one shaman. I checked this on every non-integer average


fix(subsys): getting back posix socket options

Settings POSIX socket options was accidentally removed. This commit brings it back.

bors merge


Replace full document with bson object

If we use mc_worker_api:update with the following way:
Database = <<"test">>.
{ok, Connection} = mc_worker_api:connect ([{database, Database}]).
Command =  {
<<"name">> , <<"Mets">>,
<<"quantity">>, 500,
<<"details">>, {<<"model">>, <<"14Q3">>, <<"make">>, <<"xyz">>},
<<"tags">>, [<<"coats">>, <<"outerwear">>, <<"clothing">>]
},
Collection= <<"test">>,
mc_worker_api:update(Connection, Collection, {<<"name">> , <<"Mets">>}, Command).

The returned of the execution will be:
{false,#{<<"code">> => 9,
         <<"errmsg">> => <<"wrong type for 'u' field, expected object, found u: [ { name: \"Mets\", quantity: 500, details: { mode"...>>}}

The solution here to convert the Document to map, the update done properly.

Just prefer using maps instead of bson tuples. Maps are supported and written in spec:
-spec update(pid(), collection(), selector(), map()) -> {boolean(), map()}.

the spec has been change Jan 21 in the commit :
5794fb46b028267666bf6ee0b98eb8ebb0027774
the type of the document from bson:document() to map()
the problem happened with any system used the old spec, So I think backward compatibility also preferred.

Closed, long time opened


typo: new-sqlcolumnencryptionkeysettings has "key"

Should be new-sqlcolumnencryptionsettings

@nschonni : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change.

@nschonni - thanks for the fix!
#sign-off


Not sure what happens here, but something really breaks

Describe the bug
I'm honestly not sure what happens and why it does that, but when I use the LazyOptimiser a few of the mesh renderes on my Avatar get deleted / merged together. This in it self is fine, but it results in some things looking extremely broken.
Without LazyOptimiser:

(the clipping is normal in editor)
With LazyOptimiser:

As you can see, the shirt looks really broken when using LazyOptimiser.

I suspect that the transform position of at least the shirt is offset compared to the other skinned meshes, during the merge it currently will ignore this potential offset and just pay attention to the first skinned mesh render.
The proper solution is to account for these offsets during the merge, I've actually started work on this a while ago, just didn't get it done. The temporary solution is to take the model into blender and apply the transform position (potentially also scale and rotation)

I've pushed a new version with changes which hopefully will resolve the issues seen here, do say if the issue remains. https://github.com/euan142/LazyOptimiser/releases/tag/0.2.1

I just tested it and it works perfectly fine now!


Support for Poetry build tool via JFrog CLI

Is your feature request related to a problem? Please describe.
At present, the JFrog CLI does not natively support attaching build metadata to Python packages built using Poetry in a manner similar to other build tools (consider the --build-name and --build-number options passed to the jfrog rt gradle command.)
Describe the solution you'd like to see
The addition of commands such as jfrog rt poetry and jfrog rt poetry-config isomorphic to those provided for other build tools (e.g. jfrog rt pip, jfrog rt gradle, jfrog rt npm) and subsequent recognition of those commands' by extant JFrog CLI commands (build-publish, build-scan, build-promote &c.)
Describe alternatives you've considered
We've considered converting our existing Poetry projects to Pip, however this is not feasible at this time.

We were informed by JFrog Support this is currently planned for 09/2022. Looking forward to being able to use poetry with artifactory/xray.

@sverdlov93 @talarian1 is this issue closed with release 2.27.0 ?

This still needs at least some documentation here, right?

@joergsesterhenn - although the code that supports Poetry is technically released, the documentation for it is still being worked on. It documentation will become available soon. We'll share an update here when it does.

@joergsesterhenn -
Unfortunately the new build-info functionality we built in JFrog CLI broke following the removal of a file which used to be generated by Poetry. We're trying to get the help of the Poetry Team as you can see in https://github.com/orgs/python-poetry/discussions/6869.

We are also facing this problem and would be happy about a solution.

I will add that using pip isn't viable, since pip doesn't respect the lock file. We really need to ensure that the dependency versions listed in the lock file are the ones used for the build-info.

What is the current state / stance on supporting poetry? We would like to use JFrog CLI with Poetry
After our initial look at it, it is quite confusing. Official documentation mentions support
for poetry and current version of cli seems to kind of work (we have not fully tested it), but on the other hand poetry example got removed mentioning that it is not supported


TcpEndpointTests.kt:27: Create adapter for kotlin.String...

The puzzle 2-20dd5b0a from #2 has to be resolved:
https://github.com/kerelape/reikai/blob/a4ea7f8cc2f9ec4cc99dd99ab225c96646a43735/src/test/kotlin/me/kerelape/reikai/io/network/TcpEndpointTests.kt#L27-L27
The puzzle was created by Киряев Кирилл on 20-Jul-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@Masynchin don't you want to fix this?

@kerelape I will try. My task is to add extension function for String same as for Integer?

@kerelape I will try. My task is to add extension function for String same as for Integer?

And String (: Entity) object. You escaped name collision of Integer and Number, what should I do in this case? Should I make EntityString or Text, or there is other name?

@Masynchin Text would be great, also add the extension

The puzzle 2-20dd5b0a has disappeared from the source code, that's why I closed this issue.


Reliably register routes

Register routes more reliably by trying multiple times and rolling back the content item if it eventually fails.
Trello Card

@bevanloon @steventux I believe I have addressed the issues you raised.
Regarding the revert, there isn't a chance of the content item being lost because it only calls .remove if there wasn't any existing item anyway, the only possibility is that we end up in the same inconsistent state, but now it happens a lot more rarely.

This looks good to me, just the minor comments. Happy to approve though.
@cbaines just wondering if you had any thoughts since you were working with this in the first place?

@cbaines just wondering if you had any thoughts since you were working with this in the first place?

I haven't looked at the code too closely, but I think the idea is good :) Making the update transactional will help reduce inconsistencies between the router and content-store.

@kevindew Thanks, I've addressed your comments. 😄


notifySuccess does not trigger for cross domains.

The notifySuccess() message was not replicated after we logged in or were redirected to the cross-domain. microsoftTeams.notifySuccess("") doesn't seem to work for cross domain. We verified the same from here.
Please mention the same in the documentation.

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

ID: 34dfca6e-abeb-9d03-0184-3cdc70ae7ffc
Version Independent ID: 96bc9c97-e4d5-e7c3-ed99-7937af2d35d9
Content: authentication module - Teams
Content Source<EMAIL_ADDRESS>Service: msteams
GitHub Login: @charlesprakash
Microsoft Alias: o365devx

@ChetanSharma-msft, we do not have access to this repo and will not be able to fix this issue from our end. Please reach out to Erika Doyle Navara or Joshua Partlow.
Removing this from our queue.

The PR mentioned above adds a remark to the reference docs calling out that the auth flow needs to start and end from the same domain.


Series access policy rules not disabled for viewers

Describe the bug
When a user with view-only permissions on a series or view-only permissions on series ACLs views a series access policy, they can still tick check boxes and get a message "The access rules have been saved".
To Reproduce
Steps to reproduce the behavior:

Create a user with VIEW ROLEs on all admin UI actions, notably ROLE_ADMIN_UI ROLE_UI_SERIES_DETAILS_ACL_VIEW ROLE_UI_SERIES_DETAILS_METADATA_VIEW ROLE_UI_SERIES_DETAILS_VIEW ROLE_UI_SERIES_VIEW ROLE_UI_EVENTS_VIEW
Create a new series, grant user created in step 1 view permissions in the access policy step
Log in as the new user, switch to "series", open the details of the created series and switch to "Access policy"
Tick the "write" checkbox for the role of your user and get the message "The access rules have been saved" in spite of a 400 error returned by the server

Environment Information

OS: n/a
Browser: Firefox
Opencast version with minor release 10.x (develop.opencast.org), 8.x (legacy.opencast.org)

N.b. trying to reproduce this on stable.opencast (9.x) caused the system to only report 500 errors after step 4 for events and series in admin UI. Sorry for breaking this system :-(

Resolved by #2793


Need better way to specify VMAF_MODEL_DIR.

Could we have a pre-defined set of directories to look for models, using the docker containers and brew directories as an example?

Addressed with fix #45


Added legrand-ecocompteur

Initial release of this adapter for test. Although it seems to work perfectly in my installation :)

RE-CHECK!

Automated adapter checker
ioBroker.legrand-ecocompteur

[ ] :heavy_exclamation_mark: [E301] Tests on Travis-ci.com are broken. Please fix.
[ ] :eyes: [W400] Cannot find "legrand-ecocompteur" in latest repository

Add comment "RE-CHECK!" to start check anew

I don't know what's going on here, but Travis builds are certainly passing:

Everything passes on adapter-check too (just waiting for this merge):

Seems to be a false positive ... sometimes that happens we don't know why ... so ok!

LGTM

Hi,
some review comments from me, all no real blockers

please check if there are roles matching for your states ... W, kWH and such :-) https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md
If you do not need to react on state/object changes please also not implement the methods (unneeded logic)
using Intervals can be dangerous when there are network problems - ok not that common for local network devices but still :-) more best practice is to use timeouts where next timeout is set after one call is done

Else also looking fine for me; the roles would be cool to get checked

Please give a short info if you want to check these or if I should merge into repo

some review comments from me, all no real blockers

If you want to critique the code for this adapter then you should really open an issue over in that repo:
https://github.com/raintonr/ioBroker.legrand-ecocompteur/issues
That said...

please check if there are roles matching for your states ... W, kWH and such :-) https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md

Yes, I looked at that list and there is nothing suitable. The adapter would need:

Instantaneous power measurement in Watts. Something like value.power or value.power.consumption.instantaneous.
Cumulative energy usage in kWh. Something like value.energy or value.energy.consumption.cumulative.

I notice there is value.power.consumption in kWh but this is incorrect nomenclature as kWh is a measure of energy and not power. If someone wants to correct that and create something more suitable happy to use those roles.

If you do not need to react on state/object changes please also not implement the methods (unneeded logic)

Good to know. You will notice I simply took the adapter template and did not touch anything I didn't need to. I left these methods because I didn't know if removing them would break the ioBroker world. If they can be safely removed I will do so.
May I suggest the template should be updated to mention in the comments where code can be safely removed.

using Intervals can be dangerous when there are network problems - ok not that common for local network devices but still :-) more best practice is to use timeouts where next timeout is set after one call is done

Yes, I thought about that. You will notice the minimum polling period is 1s whereas the HTTP request has a 750ms timeout. No problem as the request will always complete or error before the next is due.
Of course I tested this by pulling the cable out of my router and also pointing the IP address at an incorrect device that would throw errors. Works perfectly.

It is my fault with power.consumption. Just lost in translation. But it is a good opportunity to correct it.
What do you suggest? When I translate with google, I get "power consumption"...

What do you suggest? When I translate with google, I get "power consumption"...

Energy is the ability to do work. Measured in an amount of power spread over a period of time.
Power is the rate of doing work.
This is a good explanation: http://www.differencebetween.net/science/difference-between-energy-and-power/
Perhaps good roles would be:

value.power
value.power.consumption
value.power.production

All in W, kW, etc.
It's good to separate consumption and production because someone might have a Solar PV or other generation system for which they would require that latter one.
The 'instantaneous' part I mentioned before is probably redundant because thinking about it, by it's definition power is a constantly varying value so any reading only applies to that very instant in time it was taken. For example, with the device this adapter is polling, the best you can get is a reading every second so that is a 1 second sample.
And therefore for energy one would need:

value.energy
value.energy.consumption
value.energy.production

All in Wh, kWh, etc.
Maybe you want to include 'electrical' in there? Eg. value.power.electrical.consumption or something? I mention this because we have a heat pump for heating/hot water. There are sensors for water flow and leaving/return temperatures. From the flow and temperature difference it is possible to calculate the thermal power it is producing. Indeed, we measure those values, calculate the thermal power from them and divide by the electrical input power the unit is consuming which gives a COP value.
That said, further grouping these power/energy roles like that is probably overkill and unnecessary ;)

Noo ... do not invesnt new roles please ... if you think roles are missing please open a Issue at js-controller to discuss. But some energy roles are already defined, so if they match please use them. Was meaned that way

If you want to critique the code for this adapter then you should really open an issue over in that repo

Basically you rare right, we just did it inthe past so that for the "bring adapter in into latest the first time" we do this initial review here also to dicument that status in one place.

PS: Also reading https://github.com/ioBroker/ioBroker.repositories#development-and-coding-best-practices is always a good starting point :-) Should be as comment in new adaoter screated by adater creator or newest templates

So from all this... is there anything here that someone insists I must change in the adapter before merging this pull request?

No I merge it ...

That's good, thanks.
With regards to the state roles... are those defined anywhere? I mean, I see they are documented in the file you linked... but is there anywhere in the code that actually validates a role to one of these accepted options? Or is it just a string and it will literally store anything you give it?
Just if it's the latter I can simply update my code and it will work.

No roles are not validated right now.

Ps: but we think doing it ;-)


Downloading error.

Hi,
I get an error relating to a 'Job object' when I try to download a qgis project on my Android device.  The android device shows the error:
(Downloading error. Job(4ce74690-c0d8-423d-a850 etc...) finished with a failed status). Any idea what this may relate to?
QFieldCloud admin > Jobs Tab

Output pre:
job_output_pre.txt
Many thanks,

If you read the file that you have provided, you have an error that says:
Requested \"http://<IP_ADDRESS>/api/v1/packages/13848d10-1fa9-4ce6-8637-f9330ca07ccf/210e57c2-e2b0-4d28-8e89-e02b5d899261/files/sam_region.gpkg/\" and got \"413 Request Entity Too Large\":\n\r\n<title>413 Request Entity Too Large</title>\r\n\r\n
413 Request Entity Too Large
\r\n
nginx/1.26.2\r\n\r\n\r\n

You have to reduce the file size in your project or increase the limits in Django and nginx.


Custom operator for normalization in Collapse gate

As discussed in #262 this implements the state normalization required in the Collapse gate within the custom kernel instead of using Tensorflow primitives. Performance is very close to using the tf norm:

nqubits
Collapse with tf norm
Collapse with custom norm

27
0.56978
0.51419

28
1.06392
0.85471

29
2.01795
1.91229

30
4.01938
3.68727

31
7.89229
7.67427

32
15.8202
14.4606

however the custom norm is more stable in terms of RAM usage and uses the memory required for a single state copy. For example at 32 qubits double precision the custom norm uses 64GB, while the tf norm goes up to 120GB.
Currently the custom norm is implemented for CPU only and works with multi-threading. There are two issues to resolve (decide how to approach):

Regarding GPU, after a look at the reduction slides, it seems to me that we need a copy of the vector in order to calculate its sum using reduction methods. The reason is that half of the elements of the original array are modified in order to calculate the sum, so this operation cannot be done in-place. With this in mind, I am not sure if we would get over the current tf.reduce_sum implementation both in terms of memory and performance. In fact this may be one of the reasons that Tensorflow (which is GPU oriented) avoids in-place updates?

Regarding the distributed implementation, as I mentioned in #262, we cannot do the normalization in parallel in each device because the total norm is the sum of "norms" of each device piece. For this I have a normalize flag inside the Collapse gate which is always True except for the case that this gate is used in a distributed circuit where normalization is handled separately. Currently this normalization happens on CPU using tf.reduce_sum. There are various ways this could be improved, either by doing this on GPU (I am not sure about the communication overhead) or writing a separate custom norm operator for CPU, I am just not sure if this is sufficiently important to complicate at this stage to complicate our code-base with more custom operators.

@stavros11, thanks, the CPU performance and memory footprint are really great with this approach. For the distributed approach, I think the current behaviour is quite acceptable, it will consume more memory but that's an acceptable trade-off.
Concerning GPU, as you can see from the document, there are several approaches, but the simplest is when you consider a support array with size matching the blocks size (in our case 1024) and then use that object as shared array for the sums over threads.

I just realized that the AbsSquare method is hardcoded as double which may explain why VectorXd is faster than VectorXf (I guess the latter does more conversions between floats and doubles). I will do a few more checks with that in mind and if the situation is similar to what I wrote above I will change to VectorXd as you propose. I am not sure if there exists a way to do the variable type without slowing it down.

Concerning GPU, as you can see from the document, there are several approaches, but the simplest is when you consider a support array with size matching the blocks size (in our case 1024) and then use that object as shared array for the sums over threads.

I think I managed to do the sum on GPU following what you write here. Thanks for the explanation! I do it with two calls, the first creates a vector of size 1024 with the norms of each thread and the second does the reduction of this vector using the code from the slides. I have done a few checks and it seems to calculate the correct norm, but I still need to fix a few issues in the code before pushing. I also plan to do some benchmarks to see how this compares to the native tf solution and whether we finally gain a qubit in terms of memory. I will push the code here once I have all this.

I am not sure if there exists a way to do the variable type without slowing it down.

Probably if you write explicitly the template for each case complex64 and complex128, so you can hardcode and precompile both approaches before execution.

I think I managed to do the sum on GPU following what you write here.

Perfect.

I pushed the CUDA kernel that does the normalization and changed to Eigen::VectorXd for the CPU. The CUDA kernel works, performance for single runs is similar to what we had before and as expected we gain one qubit in memory, so we can do 30 qubits in double precision instead of 29 which was the limit when using tf.reduce_sum for the norm.
Regarding performance, notice that I wrote for single run. I noticed that if I run a circuit repeatedly as
circuit = models.Circuit(nqubits)
circuit.add(gates.Collapse(0, result=0))

for _ in range(nreps):
    state = circuit()
    del(state) # have to do this deletion otherwise GPU will run OOM

time does not increase linearly with nreps as I would expect. For example for 28 qubits I get the following times:

nreps
simulation time (sec)

50
0.02346062660217285

100
0.03359484672546387

200
9.528245449066162

300
42.064990520477295

I will try to pinpoint this issue but I suspect it has to do with the memory allocation, because I am using cudaMalloc to create the norm vectors on GPU and I suspect that Tensorflow doesn't like this. As commented in the code, normally one would do cudaFree in the end however if I do that then repeated execution of Collapse does not work properly and tests don't pass.
TODO summary to keep track of this PR's progress:

[ ] Fix the issue with repeated execution on GPU.
[ ] Attempt to parallelize the GPU norm calculation to multiple blocks (currently I use one block). This may increase performance.
[ ] Use a template variable for the norm vector types both on CPU and GPU.
[ ] Benchmark the final version on both CPU and GPU.

Probably if you write explicitly the template for each case complex64 and complex128, so you can hardcode and precompile both approaches before execution.

I implemented the norm type with a template in the last set of commits, both for CPU and GPU. Here is a comparison of the latest version of this PR (custom norm for both CPU and GPU) and the version from #262 that uses tf.reduce_sum for the norm:
CPU (40-threads)

nqubits
Collapse tf norm
Collapse custom norm

28
1.09692
0.7224

29
2.08101
1.46323

30
4.06606
2.76722

31
8.12420
5.40362

32
15.79736
11.29282

GPU

nqubits
Collapse tf norm
Collapse custom norm

27
0.00956
0.00971

28
0.01592
0.01468

29
0.02778
0.02933

30
OOM
0.05553

I believe performance and memory is acceptable in both cases, however (mostly out of curiosity) I will try to play a little with the block number for the GPU case because currently the computation is using only one block.

I pushed some small modifications in the GPU kernel, particularly used numBlocks to parallelize the state normalization kernel and moved the norm square root in the sum kernel so that it only happens once (instead of applying the square root repeatedly when normalizing each component). There is no significant change in performance from these changes.
I could not find a way to use numBlocks > 1 in the kernels that calculate the sum. If I understand the mechanism correctly, in order to do this we would need to add more components to the norm vector and I guess eventually we would just need to fine tune the number and size of blocks to get the best performance. However I would expect the differences to be tiny for our particular application, so I am not sure if it is worth going through that.
Since normalization works in both CPU and GPU and I believe that performance (tables in previous post) is acceptable, I would suggest to merge this to #262 and have a final review of the collapse gate.

Thanks, I agree. Do you still observe the memory increase on CPU/GPU?

Thanks, I agree. Do you still observe the memory increase on CPU/GPU?

The custom operators for the Collapse gate take the expected memory on both CPU and GPU, same as all other gates. The 32GB GPU can run up to 30 qubits in double precision. This is one qubit more compared to using the native Tensorflow Collapse gate. On CPU memory usage is similar, for example 32 qubits take 64GB.

OK, and what about the for _ loop you have quoted some time ago?

OK, and what about the for _ loop you have quoted some time ago?

If you mean the repeated circuit executions on a single script I have actually been doing some more benchmarks about this right now and was planning to open an issue quoting the exact script and numbers. I prefer to keep it separate from this PR because it is not related to the Collapse gate, I can reproduce the same behavior using other gates and the master branch. I am not sure if it is really an issue or it is expected but we can discuss this once I have all numbers.