Debug Failure. Unhandled Diagnostic: 2626

Bug Report
Regression in v4.2.1-rc (EDIT: also an issue in v4.2.2), tsc fails to compile with an error Debug Failure. Unhandled Diagnostic: 2626. It worked fine in v4.2.0-beta

🔎 Search Terms

🕗 Version & Regression Information

This is a crash
This changed between versions v4.2.1-beta and v4.2.2-rc
This is the behaviour in every version I tried, and I reviewed the FAQ for entries about "Debug Failure. Unhandled Diagnostic: 2626"
I was unable to test this on prior versions because _______

⏯ Playground Link

Playground link with relevant code
💻 Code

// I don't have a simple reproduction, this occurs in our ~60,000 SLOC codebase which is 50% Javascript using checkJs mode

tsconfig:
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "es2020"],
    "allowJs": true,
    "checkJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "noFallthroughCasesInSwitch": true,

    "downlevelIteration": true,
    "importHelpers": true,
    "strictNullChecks": true,
    "noImplicitAny": false,
    "baseUrl": "src"
  },
  "include": ["src"],

  "exclude": ["cypress", "src/**/__tests__/*.test.*"],
  "typeAcquisition": {
    "include": ["jest"],
    "exclude": ["chai", "cypress"]
  }
}

🙁 Actual behaviour

TSC crashes and fails to compile
$ yarn tsc --extendedDiagnostics

...\node_modules\typescript\lib\tsc.js:88040
                throw e;
                ^

Error: Debug Failure. Unhandled Diagnostic: 2626
    at reportIncompatibleStack (...\node_modules\typescript\lib\tsc.js:49104:45)
    at checkTypeRelatedTo (...\node_modules\typescript\lib\tsc.js:48976:17)
    at checkTypeRelatedToAndOptionallyElaborate (...\node_modules\typescript\lib\tsc.js:48255:24)
    at checkTypeAssignableToAndOptionallyElaborate (...\node_modules\typescript\lib\tsc.js:48249:20)
    at checkVariableLikeDeclaration (...\node_modules\typescript\lib\tsc.js:62811:25)
    at checkVariableDeclaration (...\node_modules\typescript\lib\tsc.js:62876:13)
    at checkSourceElementWorker (...\node_modules\typescript\lib\tsc.js:65151:28)
    at checkSourceElement (...\node_modules\typescript\lib\tsc.js:64999:17)
    at Object.forEach (...\node_modules\typescript\lib\tsc.js:128:30)
    at checkVariableStatement (...\node_modules\typescript\lib\tsc.js:62886:16)

🙂 Expected behaviour

It should compile, which worked in v4.2 beta

@armanio123 looks like we're straightforwardly missing a case in reportIncompatibleStack. This might be difficult to construct a test for but we can write another case for code 2626 there.

I'm hitting this as well, in a large project with the following tsconfig.json:
{
  "compilerOptions": {
    "baseUrl": "./",
    "jsx": "preserve",
    "noEmit": true,
    "module": "esnext",
    "esModuleInterop": true,
    "strict": true,
    "alwaysStrict": true,
    "noImplicitThis": false,
    "resolveJsonModule": true,
    "moduleResolution": "node",
    "downlevelIteration": true,
    "allowSyntheticDefaultImports": true,
    "skipLibCheck": true,
    "paths": {
      "~/*": ["./src/*"],
      "test/*": ["./test/*"],
      "*": ["./typings/*"]
    },
    "lib": ["es2015", "es2016", "es2017", "es2018", "esnext", "dom"],
    "target": "ES2020"
  },
  "include": ["src", "typings"],
  "exclude": [
    "node_modules",
    "public",
    "lib",
    "./src/**/__tests__/*.legacy-unit-test.ts",
    "./src/**/__tests__/*-itest.ts"
  ]
}

$ tsc -p .
/app/node_modules/typescript/lib/tsc.js:88051
                throw e;
                ^

Error: Debug Failure. Unhandled Diagnostic: 2626
    at reportIncompatibleStack (/app/node_modules/typescript/lib/tsc.js:49104:45)
    at reportRelationError (/app/node_modules/typescript/lib/tsc.js:49145:21)
    at reportErrorResults (/app/node_modules/typescript/lib/tsc.js:49338:25)
    at isRelatedTo (/app/node_modules/typescript/lib/tsc.js:49299:17)
    at typeArgumentsRelatedTo (/app/node_modules/typescript/lib/tsc.js:49573:39)
    at relateVariances (/app/node_modules/typescript/lib/tsc.js:50032:34)
    at structuredTypeRelatedToWorker (/app/node_modules/typescript/lib/tsc.js:49982:46)
    at structuredTypeRelatedTo (/app/node_modules/typescript/lib/tsc.js:49689:30)
    at recursiveTypeRelatedTo (/app/node_modules/typescript/lib/tsc.js:49665:53)
    at isRelatedTo (/app/node_modules/typescript/lib/tsc.js:49279:34)

@stevehollaar any chance you could share code that reproduces the issue? That would help us out a ton

@stevehollaar any chance you could share code that reproduces the issue? That would help us out a ton

Unfortunately the codebase is proprietary and I wasn't able to isolate a small repro.
I ended up debugging this by adding a console.log line:
console.log({source, sourceType });

in tsc.js, just prior to this line:
reportIncompatibleError(ts.Diagnostics.Type_at_position_0_in_source_is_not_compatible_with_type_at_position_1_in_target, sourceIndex, i);

That gave me:
{
  source: Type {
    flags: 524288,
    id: 117489,
    symbol: undefined,
    objectFlags: 1114116,
    target: <ref *1> Type {
      flags: 524288,
      id: 1048,
      objectFlags: 12,
      symbol: undefined,
      members: undefined,
      properties: undefined,
      callSignatures: undefined,
      constructSignatures: undefined,
      stringIndexInfo: undefined,
      numberIndexInfo: undefined,
      typeParameters: [Array],
      outerTypeParameters: undefined,
      localTypeParameters: [Array],
      instantiations: [Map],
      target: [Circular *1],
      resolvedTypeArguments: [Array],
      thisType: [Type],
      declaredProperties: [Array],
      declaredCallSignatures: [],
      declaredConstructSignatures: [],
      declaredStringIndexInfo: undefined,
      declaredNumberIndexInfo: undefined,
      elementFlags: [Array],
      minLength: 2,
      fixedLength: 2,
      hasRestElement: false,
      combinedFlags: 1,
      readonly: false,
      labeledElementDeclarations: undefined,
      resolvedBaseTypes: [Array],
      baseTypesResolved: true
    },
    resolvedTypeArguments: [ [Type], [Type] ],
    members: Map(36) {
      '0' => [Symbol],
      '1' => [Symbol],
      'length' => [Symbol],
      'toString' => [Symbol],
      'toLocaleString' => [Symbol],
      'pop' => [Symbol],
      'push' => [Symbol],
      'concat' => [Symbol],
      'join' => [Symbol],
      'reverse' => [Symbol],
      'shift' => [Symbol],
      'slice' => [Symbol],
      'sort' => [Symbol],
      'splice' => [Symbol],
      'unshift' => [Symbol],
      'indexOf' => [Symbol],
      'lastIndexOf' => [Symbol],
      'every' => [Symbol],
      'some' => [Symbol],
      'forEach' => [Symbol],
      'map' => [Symbol],
      'filter' => [Symbol],
      'reduce' => [Symbol],
      'reduceRight' => [Symbol],
      'find' => [Symbol],
      'findIndex' => [Symbol],
      'fill' => [Symbol],
      'copyWithin' => [Symbol],
      '__@iterator' => [Symbol],
      'entries' => [Symbol],
      'keys' => [Symbol],
      'values' => [Symbol],
      '__@unscopables' => [Symbol],
      'includes' => [Symbol],
      'flatMap' => [Symbol],
      'flat' => [Symbol]
    },
    properties: [
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol],
      [Symbol], [Symbol], [Symbol], [Symbol]
    ],
    callSignatures: [],
    constructSignatures: [],
    stringIndexInfo: undefined,
    numberIndexInfo: { type: [Type], isReadonly: false, declaration: [Node] }
  },
  sourceType: Type {
    flags: 524288,
    id: 117487,
    objectFlags: 16,
    symbol: Symbol {
      flags: 4096,
      escapedName: '__object',
      declarations: [Array],
      valueDeclaration: [Node],
      id: undefined,
      mergeId: undefined,
      parent: undefined,
      members: [Map]
    },
    members: Map(3) {
      'notificationId' => [Symbol],
      'getTemplateData' => [Symbol],
      'generateStartEndDate' => [Symbol]
    },
    properties: [ [Symbol], [Symbol], [Symbol] ],
    callSignatures: [],
    constructSignatures: [],
    stringIndexInfo: undefined,
    numberIndexInfo: undefined
  }
}

just prior to the tsc error, and from there I was able to find the problematic code via the sourceType.members.
I think there must have been something funky about the way types were shared across module boundaries (possibly related to a circular reference?), as when I tried to repro in the playground, I could not. My "fix" was to explicitly type some exported objects with a shared interface, instead of leaving the type as implicit. I hope this helps!

I'm getting something very similar, but not exactly the same.  It compiles fine with 4.1.5 but fails with the error below in 4.2.2.  We are using webpack and I'm logging the ts file name as it's being processed, and unfortunately, it's not always happening on the same file.  I don't have an easy repro, this solution is proprietary and also contains thousands of typescript files.  At first I thought it was when exporting an enum where the enum's values were strings.  I noticed the ones that it was crashing on were strings using a single quote and not a double quote, so I changed it, and it seemed to no longer fail on that file.  However, I'm no longer certain that's the issue as it's now failing on a file with a large exported class.  This class has no members that are strings, although it does use strings in one method, and those strings have single quotes.  It's too much to change every file in the project as a test, but this seems like correlation but not necessarily causation anyway.  At this point, we are rolling back to 4.1.5.
Error: Debug Failure. Error: Debug Failure.     at Object.getModuleSpecifiers (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:111579:30)     at getSpecifierForModuleSymbol (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48852:62)     at C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48710:39     at Array.map (<anonymous>)     at getSymbolChain (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48708:58)     at getSymbolChain (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48718:51)     at lookupSymbolChainWorker (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48692:51)     at lookupSymbolChain (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48685:24)     at symbolToTypeNode (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48859:29)     at typeReferenceToTypeNode (C:\dev\Workspaces\Git\Project\node_modules\.pnpm\typescript@4.2.2\node_modules\typescript\lib\typescript.js:48272:40)

I had same problem. For me it was that I used string as an enum instead of using the actual enum as value.

@heikkis , We use them all over the place.  The language allows it: https://www.typescriptlang.org/docs/handbook/enums.html.

I'm having the same error as @ItWorksOnMyMachine.
And I have a small reproduction repo: https://github.com/flybayer/tsc-broken (boilerplate for a new Blitz app)

git clone git@github.com:flybayer/tsc-broken.git
cd tsc-broken
yarn
yarn tsc

In my case, I had code like this that crashed with a 2626 that was hard to debug:
import { defineMessages } from 'react-intl';

type UserSource = 'google' | 'slack' | 'microsoft'

type SourceInfo = {
  key: string;
  icon: ReactNode;
  label: { id: string; defaultMessage: string; description: string };
};

const messages = defineMessages({
  slackProvider: {
    id: 'fabric.elements.user-picker.slack.provider',
    defaultMessage: 'Slack',
    description: 'This external user is sourced from Slack provider',
  },
});

// @ts-ignore
const SourcesInfoMap = new Map<UserSource, SourceInfo>([
  ["slack", { key: "slack", icon: <SlackIcon />, label: messages.slackProvider }]
]);

The code doesn't run but I hope it gives you enough idea to tell what the issue is about.
The weird thing is that it crashed even with that // @ts-ignore in place. The fix was to change the declaration to <UserSource, any> instead of <UserSource, SourceInfo> although I know that's not particularly nice.
It's possible there was some issue in the original code that was uncovered by the update to TypeScript 4.2.

I ran across this with svelte-check, and I can share my code. This commit: https://github.com/rpavlik/openxr-changelog-maker/commit/7711de456285ef2f84c101fdd2337a5a865da97d
produces this:
❯ npm run check

><EMAIL_ADDRESS>check
> svelte-check

Loading svelte-check in workspace: e:\src-ssd\openxr-changelog-maker
Getting Svelte diagnostics...
====================================

Error: Debug Failure. Unhandled Diagnostic: 2626
    at reportIncompatibleStack (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59271:45)
    at reportRelationError (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59314:21)
    at reportErrorResults (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59580:25)
    at isRelatedTo (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59539:17)
    at typeArgumentsRelatedTo (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59842:39)
    at relateVariances (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:60394:34)
    at structuredTypeRelatedToWorker (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:60330:46)
    at structuredTypeRelatedTo (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59978:30)
    at recursiveTypeRelatedTo (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59950:64)
    at isRelatedTo (E:\src-ssd\openxr-changelog-maker\node_modules\typescript\lib\typescript.js:59490:34)
====================================
svelte-check found 0 errors, 0 warnings and 0 hints

This is still happening to me with 4.2.4. Same error: Error: Debug Failure. Unhandled Diagnostic: 2626

Just stumbled upon this too, looks like it was the same issue @bscaspar had: https://github.com/getsentry/sentry/pull/25744/commits/5b782112ce527872a0db18e2809fe7486d6ea124#diff-d8015cdd3c4c2b662a481d12aae7ff2f2a0bd8d48021a0a369cbd4f06229a2b8L4-R9

Version 4.2.4 same error.

Version 4.2.4 same error. Any idea how to debug it?

For me there was an actual typescript error which caused the crash, so I had to debug it the old fashioned way - add changes one at a time until the crash identified the problematic code. Of course there doesn't seem to be enough evidence ton confirm that TS errors are the only cause so it may be something that would compile completely fine normally. Good luck!

@bscaspar Thank you. Yes it was an error in TS but not sure where exactly. Maybe SWR lib typing. Sad the lib cant produce some kind of error trace.

fyi - I reverted to version "typescript": "4.0.2" (v. old, but was just what was mentioned in Google search results), and it spat our an error trace with line numbers! I can see that it is an issue with assigning types.

Just in case it's helpful, the following changes in the PR started generating this crash in our repository. https://github.com/roblox-ts/roblox-ts/runs/2613701799

The second commit in the PR has solved the crash.
Compiling with version 4.2.0 gave me this error:
src/TSTransformer/nodes/statements/transformStatement.ts:44:29 - error TS2769: No overload matches this call.
  Overload 1 of 3, '(iterable: Iterable<readonly [SyntaxKind, StatementTransformer]>): Map<SyntaxKind, StatementTransformer>', gave the following error.
    Argument of type '([SyntaxKind.InterfaceDeclaration, () => List<Statement<keyof StatementByKind>>] | [SyntaxKind.TypeAliasDeclaration, () => List<Statement<keyof StatementByKind>>] | ... 25 more ... |
[...])[]' is not assignable to parameter of type 'Iterable<readonly [SyntaxKind, StatementTransformer]>'.
      The types returned by '[Symbol.iterator]().next(...)' are incompatible between these types.
        Type 'IteratorResult<[SyntaxKind.InterfaceDeclaration, () => List<Statement<keyof StatementByKind>>] | [SyntaxKind.TypeAliasDeclaration, () => List<Statement<keyof StatementByKind>>] | ... 25 more
... | [...], any>' is not assignable to type 'IteratorResult<readonly [SyntaxKind, StatementTransformer], any>'.
          Type 'IteratorYieldResult<[SyntaxKind.InterfaceDeclaration, () => List<Statement<keyof StatementByKind>>] | [SyntaxKind.TypeAliasDeclaration, () => List<Statement<keyof StatementByKind>>] | ... 25 more ... | [...]>' is not assignable to type 'IteratorResult<readonly [SyntaxKind, StatementTransformer], any>'.
            Type 'IteratorYieldResult<[SyntaxKind.InterfaceDeclaration, () => List<Statement<keyof StatementByKind>>] | [SyntaxKind.TypeAliasDeclaration, () => List<Statement<keyof StatementByKind>>] | ... 25 more ... | [...]>' is not assignable to type 'IteratorYieldResult<readonly [SyntaxKind, StatementTransformer]>'.
              Type '[SyntaxKind.InterfaceDeclaration, () => List<Statement<keyof StatementByKind>>] | [SyntaxKind.TypeAliasDeclaration, () => List<Statement<keyof StatementByKind>>] | ... 25 more ... | [...]' is not assignable to type 'readonly [SyntaxKind, StatementTransformer]'.
                Type '[SyntaxKind.ForOfStatement, (state: TransformState, node: ForOfStatement) => List<Node<SyntaxKind>>]' is not assignable to type 'readonly [SyntaxKind, StatementTransformer]'.
                  Type at position 1 in source is not compatible with type at position 1 in target.
                    Type 'List<Node<SyntaxKind>>' is not assignable to type 'List<Statement<keyof StatementByKind>>'.
                      Type 'Node<SyntaxKind>' is not assignable to type 'Statement<keyof StatementByKind>'.
                        Types of property 'kind' are incompatible.
                          Type 'SyntaxKind' is not assignable to type 'keyof StatementByKind'.
  Overload 2 of 3, '(entries?: readonly (readonly [SyntaxKind, StatementTransformer])[] | null | undefined): Map<SyntaxKind, StatementTransformer>', gave the following error.
    Type '(state: TransformState, node: ForOfStatement) => List<Node<SyntaxKind>>' is not assignable to type 'StatementTransformer'.

 44 const TRANSFORMER_BY_KIND = new Map<ts.SyntaxKind, StatementTransformer>([
                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 45  // no emit
    ~~~~~~~~~~~
...
 77  [ts.SyntaxKind.WhileStatement, transformWhileStatement],
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 78 ]);

I had the same issue, in my case it was because of passing array to Map constructor. Consider this case:
interface UploadProgress {     progress: number }
createUpload(file: File, fileId: string): Observable<Map<string, UploadProgress>> {     ...     return fileUploader.startUpload(file).pipe(map((progress) => new Map<string, UploadProgress>([[fileId, { progress }]]))); }
here in return statement progress appears to be not a number as I expect, but and object UploadProgress.
As soon as I rewrite Map constructor without passing there an array, it rewards me with readable compiler exception that helps me figure this out.
return fileUploader.startUpload(file).pipe(map((progress) => new Map<string, UploadProgress>([[fileId, progress ]])));
{ progress } must be progress
I saw similar array assignment to Map array in previous comment, that gave me a hint.
Try
const map = new Map(); map.setValue(key, value);
instead of
new Map([[key, value]])

I had the same issue, in my case it was because of passing array to Map constructor. Consider this case:
`
interface UploadProgress {
progress: number;
}
createUpload(file: File, fileId: string): Observable<Map<string, UploadProgress>> {
...
return fileUploader.startUpload(file).pipe(map((progress) => new Map<string, UploadProgress>([[fileId, { progress }]])));
}
`
here in return statement progress appears to be not a number as I expect, but and object UploadProgress.
As soon as I rewrite Map constructor without passing there an array, it rewards me with readable compiler exception that helps me figure this out.
return fileUploader.startUpload(file).pipe(map((progress) => new Map<string, UploadProgress>([[fileId, progress ]])));
{ progress } must be progress
I saw similar array assignment to Map array in previous comment, that gave me a hint.
Try
const map = new Map();  map.setValue(key, value);
instead of
new Map([[key, value]])

I was on     "typescript": "^4.2.4" and it was throwing this error with no stack trace. I updated my project to use "typescript": "^4.5.5", and it handled the error properly and started throwing a stack trace which made it easy to find where the error was. In my case I was extending the global type the react navigation v6 export which caused this error.


Setup Bundling

We need setup deno bundler for all javascript files.
Official docs about Deno Bundler

I think #69 closes this issue, all .ts files transpile to a single bundle.js


Add section in the admin panel to manage "robot users" based on public keys

[x] New collection for public-key management is created
[x] New feature to register robot users (a normal user with a public key)
[x] New feature to link an existing user with a public key
[x] Create an admin panel to manage robot users (i.e., managing public keys)

This feature is associated with issue #293

[ ] New collection for public management is created
[ ] New feature to register robot users (a normal user with a public key)
[ ] New feature to link an existing user with a public key

Been done in the PR #315


Add a way to navigate back to the general landing page

Feedback from @nstewart: how do I get back to this screen after clicking any of the left hand navigation links? I can press the back button a lot, but I would have expected some direct home link. I kept clicking “quickstart” thinking I would go back to the docs home

@luciaaaaaaa, do we already have designs or thoughts about how to do this? This has been nagging at me as well when I use the docs. I also looked at pageviews, and the new main landing page isn't getting as much traffic as we might expect because one they're in other parts of the docs, users don't go back there until next time they enter the docs from the topnav.

Pain point: The current way to navigate back to the Docs Home page is through the primary nav ... Resources > Technical Resources > Docs. This is a UX pain point because we expect a lot of people to want to navigate back to the 'Docs' Home page, but once you are in the Docs site, the link is not visible at a glance.
Potential Solutions:

Proposal 1: Link to navigate to the Docs Home from the Docs side-nav
Proposal 2: Docs Home link surfaced as a top level nav item on primary nav, rather then as a sub-link of 'Resources'

Wireframes: https://www.figma.com/file/6XcxaUdad2RkjpEqnVHKAG/Education-docs-redesign?node-id=4018%3A8689
Open questions:

What was the marketing decision making around Docs presented in the ‘Resources’ tab rather than as a top-level nav item?
How many people access 'Docs' from the Primary Nav?
Is 'Home' well understood to users as the label for our Docs home page?
If we adopt option 1, should the page title match the side-nav label?


Response for preflight has invalid HTTP status code 401

When I try to access the webdav server using a script that runs from a different server (cross-origin requests known as CORS), I get this error : Response for preflight has invalid HTTP status code 401
Check the JS error console here : https://www.ajaxbrowser.com/?CrossDomainDemo
The problem is the same with Evert's DAVCLIENT.JS library
The problem seems related to the fact that sabredav requires authorization to answer to OPTIONS requests but this is non standard behaviour.
I tried adding these headers in my server.php file, but this doesn't change anything:
header("Access-Control-Allow-Origin: https://www.ajaxbrowser.com");
header("Access-Control-Allow-Credentials: true");
header("Access-Control-Allow-Methods: ACL, CANCELUPLOAD, CHECKIN, CHECKOUT, COPY, DELETE, GET, HEAD, LOCK, MKCALENDAR, MKCOL, MOVE, OPTIONS, POST, PROPFIND, PROPPATCH, PUT, REPORT, SEARCH, UNCHECKOUT, UNLOCK, UPDATE, VERSION-CONTROL");
header("Access-Control-Allow-Headers: Overwrite, Destination, Content-Type, Depth, User-Agent, Translate, Range, Content-Range, Timeout, X-File-Size, X-Requested-With, If-Modified-Since, X-File-Name, Cache-Control, Location, Lock-Token, If");
header("Access-Control-Expose-Headers: DAV, content-length, Allow");
Any idea ?

you can also check this site for more information on the subject : https://www.webdavsystem.com/ajaxfilebrowser/programming/cross_domain

This is not a bug and not non-standard. Responding to a 401 on a OPTIONS request is actually required by some DAV clients.
The right solution is to create a CORS plugin that returns the correct headers and does not return a 200 response, but only for CORS pre-flight requests and nothing else. It is possible to detect whether something was a CORS pre-flight or not.


Localtesttool: Automatic reload of dll

As an user, I want the localtesttool to reload my tests, directly before I start them. With this feature I can change stuff in the testdll and test these changes right after the build and I don't need to open the testdll again.

Implemented within Pullrequest #19


updated notebook to lab ...

notebook was not found when running command... switching to lab fixed this error
Signed-off-by: Gennaro Schiano<EMAIL_ADDRESS>

I took this for a spin locally and it worked. 👍🏼

@allcontributors please add @gschian0 for doc


jre requiring X11 on OSX

System:
darwin ; nix 1.11.2 ; channels/nixpkgs-unstable
Steps to reproduce:
$ nix-env -i groovy
$ groovysh

Expected:
groovy shell starts
Actual
This will open a dialogue telling me that I need to install X11 to run Java. If I build groovy with jre8 instead of jre it works.

@gilligan could you try building jre without X11 on darwin. if it works you can make it optional for darwin then.

triage: is this still a problem?


Maximum topology short CP /C++

💥 Proposal
It is an important Cp Topic that is very useful
For example, consider the tree below:
                      2
            1                  3

The sorted list of pairs is ((2,2),(1,3),(1,1)).
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign

#4392

#4654

Merged.


added rust-cookbook to "starters" and "impl"

Hi,
I've added the rust-cookbook to "starters" and "impl".
The cookbook itself is nominally part of the libs-blitz but I did not want to spam all of the tabs.
Any suggestions on how should we proceed with it?

Thanks!


[devops:bot] update deps in nix/sources.json (from: rhino-core@3da7915)

update nix refernces for rhino-core and|or nixpkgs to match https://github.com/rhinofi/rhino-core/blob/3da7915b720219763f5599c7b79682785a028a17/nix/sources.json (branch: dev)

superseded by #203


[Improvement request] Regex in Input machine

Ability to use regex in the mask (condition to valid entry) of the Input machine

Aded on July 2 by Guillain 32535de994e5b4372a8967f4ae514ca999b6268a


Errors found when running ./tests/run-system-tests.pl

Hi,
I installed cdec on my Mac as per the instructions here - https://github.com/redpony/cdec#building-the-software
But, when I run ./tests/run-system-tests.pl, one of the test fails. How do I debug what's wrong?  THERE WERE FAILURES - DECODER IS ACTING SUSPICIOUSLY !!!

save error, did you fix it?


HHH-9301 - Support select variable refs in group by for DBMS dialects that support it

While not strictly compliant with the SQL specification, the MySQL, PostgreSQL and H2 support the use of select aliases in the GROUP BY clause. An obvious benefit is that produced SQL queries will be easier to read, because complex select expressions from aggregrate queries will have to be included in the group by clause as well. These can now simply reference the aliases of the respective columns for the tuple element. However, there is also a functional difference. For function invocations that have parameterized arguments, the query optimizer can't guarantee the that the function result between the selection projection and grouping process are equal. This results in an error because a value is projected which is not grouped by. An example where this for example becomes relevant, is when parameterizing TimeScaleDB's time_bucket_gapfill() function.
For example, using time_bucket_gapfill() one might want to produce a criteria query that produces the following SQL:
SELECT
    time_bucket_gapfill(?, time, ?, ?) AS ts,
    avg(tg) as tg
FROM iaqmeasurement
GROUP BY ts
ORDER BY ts;

When the alias is not used as grouping value, the query will yield an error:
SELECT
    time_bucket_gapfill(?, time, ?, ?) AS ts,
    avg(tg) as tg
FROM iaqmeasurement
GROUP BY time_bucket_gapfill(?, time, ?, ?)
ORDER BY ts;

Of course the parameter values can just be stored in a CTE as well, but I think we should consider support for variable refs in group by for DBMS dialects that support it. This pull request implements the feature equivalently to how its currently done for order by clauses, and only enables the feature for known supported dialects (H2, PostgreSQL and MySQL - based on https://stackoverflow.com/a/3841804/2104280). I am not sure what we should do with dialects that do not support it. We could either throw an error, rely on the database to throw an error, or copy the expression from the select alias ourselves in an attempt to fix the query.
Jira: https://hibernate.atlassian.net/browse/HHH-9301

Thanks @JWGmeligMeyling !  This is very useful, I agree.

Perhaps something to integrate for 5.4 now we're integrating small non-breaking features again? @Sanne

@jwgmeligmeyling sure, go ahead and merge it in master? Looks like it was reviewed already.

rebased and applied upstream.
Thanks @jwgmeligmeyling


Optimal χ in modified Crank-Nicholson Adams-Bashforth time stepping is 1/8.

@jm-c's favorite value is 1/10. Probably won't make a huge difference.
See: https://epubs.siam.org/doi/abs/10.1137/0732037

Can you ref the place in the code this is defined?

https://github.com/climate-machine/Oceananigans.jl/blob/3b1518355df2f9bfcb81d702e3d5c55f52ab4757/src/time_steppers.jl#L7
https://github.com/climate-machine/Oceananigans.jl/blob/3b1518355df2f9bfcb81d702e3d5c55f52ab4757/src/time_steppers.jl#L203-L207
Might be good to double check with @jm-c before changing this.

@jm-c says we're just using AB2 so don't think this is relevant.

In AB2 there is no tunable parameter.

Yes it's not just AB2 but it's not Crank-Nicholson apparently (which is implicit-explicit).

In the language of the paper, the method we are using sets c = -2gamma to obtain a completely explicit scheme that resembles AB2, but still has a tunable parameter "gamma". The time-stepping method we are using is in the category of those presented in the paper.

Closed in #128 (which was merged into #118).


Old url

Since release is delayed for now, let's fix some more issues!
Fixes #103
cc @EPashkin @sdroege

:+1:


VSCode window not responsive on startup, even with extensions disabled

On startup the window is non-reponsive. After 30 seconds or so a popup dialog comes up:
The window is no longer responding
You can reopen or close the window or keep waiting.
[Reopen] [Keep Waiting] [Close]

What I have tried:

starting with code --verbose --disable-extensions
deleting my workspace file so that there's no open docs or folders

No change from either of those.
Here's the output from code --verbose --disable-extensions:
https://pastebin.com/mwzRjHbj

VSCode Version: 1.40.2
OS Version: Windows 10

I was able to get a responsive window by running code --disable-restore-windows
I've tested opening and closing a few times and it looks like this has fixed the issue.

Possibly related https://github.com/microsoft/vscode/issues/86633

I may have tracked down what causes this:
I did a search/replace in around 1500 small files (all svg, <20kb).
I then saw a spike in 'git for Windows' instances, and also 'console' instances nested under vscode in the windows task manager. These build over a couple is minutes until there was a combined total of >700 processes nested under vscode.
At this point the vscode window became unresponsive and I closed it from task manager. When I try to reopen I get the above error.
I have done this two times with this result.

@looeee so it does not reproduce anymore right? You once saw the git processes spike and then it was good?

@looeee so it does not reproduce anymore right?

No, I can reproduce. I have figured out the steps:

Go here https://fontawesome.com/download
Download "free for web package"
Extract SVG folder and open in VSCode
Do a search and replace on all SVG files.

I managed to snag this screenshot from the task manager. The processes here say 247, but it climbed slightly over 700. About half the processes are "console window host", the rest are "git for windows" (offscreen in this screenshot). Was kinda painful to capture this as my mouse was tracking at about 0.01 fps!

When I eventually managed to kill the VSCode process, about 200 of these windows popped up:

Ha!  I'm now on 1.41.
Going through the whole sorry process again, the slow death of my system still happens.
The only difference is that the console window hosts and git for window processes are no longer nested under VSCode:

However, the VSCode window is now responsive when I reopen 😁
So, this has morphed into a report of a different bug. Apologies for that. Do you want me to close this and open a new issue? Or is it just a case of "don't search and replace 1500 files at once"?

@looeee can you try to reproduce in a folder that is not under git control to see if these are all git processes?

Sure, I tested again by moving the svg folder to D:/downloads and running the same search/replace.
My downloads folder is not under source control. However, behavior is exactly the same - hundreds of git for windows and console hosts processes spawn and my computer gradually crashes.
Even after I kill VSCode stability doesn't really come back and I'm having to do a system restart nearly every time I test this.

Weird. I just tried to reproduce on my Windows and cannot. Can you share your settings?

Sure, here you go:
https://pastebin.com/mXRcgi7u
git version 2.21.0.windows.1
Code version:
1.41.0
9579eda04fdb3a9bba2750f15193e5fafe16b959
x64

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions

Hmm, that was the first thing I tested when I first had the original issue.
But it seems like this "secondary" issue is caused by an extension. code --disable-extensions fixes it.
I'll track down which extension tomorrow.
Thanks for your support @bpasero .


several code warnings related to deprecated funcs, truncation, and unused vars

Build results in 10+ warnings of code style, deprecation, truncation, etc. These can likely be resolved easily by minor code changes, or hiding the warnings with pragmas.
Setup

Microsoft Windows [Version 10.0.19042.804]
Visual Studio 2019 Community v16.8.6
Current develop branch 126f5fcf64bb127c3f5c7f069410b3e2754d20d7

Repro

clean git clone, configure, build

Result
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.exe" --build c:/njs/lux/depthai-core/build --config Debug --target all -- -j 15
[build] [3/43   2% :: 0.027] Generating depthai-resources resource loader
[build] [3/43   4% :: 0.846] Generating intermediate file for C:/njs/lux/depthai-core/build/resources/depthai-bootloader-0.0.11.cmd
[build] [3/43   6% :: 4.622] Generating intermediate file for C:/njs/lux/depthai-core/build/resources/depthai-device-fwp-5e4974e930f4ecbe1bf718463f6a5da664e68788.tar.xz
[build] [18/43   9% :: 7.446] Building CXX object CMakeFiles\depthai-core.dir\src\device\CallbackHandler.cpp.obj
[build] ..\src\device\CallbackHandler.cpp(40): warning C4101: 'ex': unreferenced local variable
[build] [19/43  11% :: 7.574] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\AssetManager.cpp.obj
[build] ..\src\pipeline\AssetManager.cpp(84): warning C4267: 'initializing': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\pipeline\AssetManager.cpp(93): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] [20/43  13% :: 7.579] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\XLinkIn.cpp.obj
[build] [21/43  16% :: 7.631] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\MyProducer.cpp.obj
[build] [22/43  18% :: 7.642] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\XLinkOut.cpp.obj
[build] [23/43  20% :: 7.646] Building C object CMakeFiles\depthai-core.dir\shared\depthai-bootloader-shared\src\SBR.c.obj
[build] ..\shared\depthai-bootloader-shared\src\SBR.c(169): warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] [24/43  23% :: 7.655] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\StereoDepth.cpp.obj
[build] [25/43  25% :: 8.391] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\ImageManip.cpp.obj
[build] [26/43  27% :: 8.439] Building CXX object CMakeFiles\depthai-core.dir\src\device\DataQueue.cpp.obj
[build] [27/43  30% :: 8.472] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\ColorCamera.cpp.obj
[build] ..\src\pipeline\node\ColorCamera.cpp(273): warning C4244: 'initializing': conversion from 'int' to 'float', possible loss of data
[build] ..\src\pipeline\node\ColorCamera.cpp(274): warning C4244: 'initializing': conversion from 'int' to 'float', possible loss of data
[build] [28/43  32% :: 8.491] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\MonoCamera.cpp.obj
[build] [29/43  34% :: 8.496] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\Node.cpp.obj
[build] [30/43  37% :: 8.517] Building CXX object CMakeFiles\depthai-core.dir\shared\depthai-shared\src\datatype\DatatypeEnum.cpp.obj
[build] [31/43  39% :: 8.639] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\NeuralNetwork.cpp.obj
[build] ..\src\pipeline\node\NeuralNetwork.cpp(69): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] [32/43  41% :: 9.182] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\Pipeline.cpp.obj
[build] [33/43  44% :: 9.934] Building CXX object CMakeFiles\depthai-core.dir\src\utility\Initialization.cpp.obj
[build] [34/43  46% :: 9.995] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\Buffer.cpp.obj
[build] [35/43  48% :: 10.502] Building CXX object CMakeFiles\depthai-core.dir\src\device\DeviceBootloader.cpp.obj
[build] ..\src\device\DeviceBootloader.cpp(101): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(102): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(107): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(108): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(113): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(114): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(119): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(120): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(130): warning C4267: 'argument': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(190): warning C4101: 'ex': unreferenced local variable
[build] ..\src\device\DeviceBootloader.cpp(202): warning C4101: 'error': unreferenced local variable
[build] ..\src\device\DeviceBootloader.cpp(287): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(288): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(336): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(337): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] ..\src\device\DeviceBootloader.cpp(380): warning C4996: 'sscanf': This function or variable may be unsafe. Consider using sscanf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] [36/43  51% :: 10.574] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\SystemLogger.cpp.obj
[build] [37/43  53% :: 10.633] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\VideoEncoder.cpp.obj
[build] ..\src\pipeline\node\VideoEncoder.cpp(93): warning C4244: '=': conversion from 'int' to 'float', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(137): warning C4244: 'return': conversion from 'const float' to 'int', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(145): warning C4244: 'argument': conversion from 'float' to 'int', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(157): warning C4244: '=': conversion from 'float' to 'int32_t', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(167): warning C4244: 'argument': conversion from 'float' to 'int', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(170): warning C4244: 'argument': conversion from 'float' to 'int', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(173): warning C4244: 'argument': conversion from 'float' to 'int', possible loss of data
[build] ..\src\pipeline\node\VideoEncoder.cpp(176): warning C4244: 'argument': conversion from 'float' to 'int', possible loss of data
[build] [38/43  55% :: 10.748] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\ImgFrame.cpp.obj
[build] [39/43  58% :: 10.826] Building CXX object CMakeFiles\depthai-core.dir\src\xlink\XLinkStream.cpp.obj
[build] ..\src\xlink\XLinkStream.cpp(25): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
[build] ..\src\xlink\XLinkStream.cpp(62): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
[build] ..\src\xlink\XLinkStream.cpp(115): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
[build] ..\src\xlink\XLinkStream.cpp(133): warning C4244: 'argument': conversion from '_Rep' to 'unsigned int', possible loss of data
[build]         with
[build]         [
[build]             _Rep=__int64
[build]         ]
[build] ..\src\xlink\XLinkStream.cpp(133): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
[build] ..\src\xlink\XLinkStream.cpp(153): warning C4244: 'argument': conversion from '_Rep' to 'unsigned int', possible loss of data
[build]         with
[build]         [
[build]             _Rep=__int64
[build]         ]
[build] ..\src\xlink\XLinkStream.cpp(167): warning C4244: 'argument': conversion from '_Rep' to 'unsigned int', possible loss of data
[build]         with
[build]         [
[build]             _Rep=__int64
[build]         ]
[build] [40/43  60% :: 11.212] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\node\DetectionNetwork.cpp.obj
[build] [41/43  62% :: 11.257] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\CameraControl.cpp.obj
[build] [41/43  65% :: 11.306] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\SystemInformation.cpp.obj
[build] [41/43  67% :: 11.591] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\ImgDetections.cpp.obj
[build] [41/43  69% :: 11.645] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\ImageManipConfig.cpp.obj
[build] ..\src\pipeline\datatype\ImageManipConfig.cpp(90): warning C4305: 'initializing': truncation from 'double' to 'const float'
[build] [41/43  72% :: 11.729] Building C object CMakeFiles\depthai-core.dir\src\bspatch\bspatch.c.obj
[build] ..\src\bspatch\bspatch.c(134): warning C4244: 'function': conversion from 'int64_t' to 'unsigned int', possible loss of data
[build] ..\src\bspatch\bspatch.c(129): warning C4244: 'initializing': conversion from 'int64_t' to 'unsigned int', possible loss of data
[build] [41/43  74% :: 11.978] Building CXX object CMakeFiles\depthai-core.dir\src\openvino\BlobReader.cpp.obj
[build] [41/43  76% :: 12.049] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\NNData.cpp.obj
[build] C:\.hunter\_Base\062a19a\8d58f30\2ddc225\Install\include\fp16/fp16.h(377): warning C4244: 'argument': conversion from 'float' to 'uint32_t', possible loss of data
[build] ..\src\pipeline\datatype\NNData.cpp(64): warning C4267: '=': conversion from 'size_t' to 'unsigned int', possible loss of data
[build] ..\src\pipeline\datatype\NNData.cpp(91): warning C4267: '=': conversion from 'size_t' to 'unsigned int', possible loss of data
[build] ..\src\pipeline\datatype\NNData.cpp(120): warning C4244: 'argument': conversion from '_Ty' to 'float', possible loss of data
[build]         with
[build]         [
[build]             _Ty=double
[build]         ]
[build] [41/43  79% :: 12.064] Building CXX object CMakeFiles\depthai-resources.dir\__cmrc_depthai-resources\lib.cpp.obj
[build] [41/43  81% :: 12.120] Building CXX object CMakeFiles\depthai-core.dir\src\xlink\XLinkConnection.cpp.obj
[build] ..\src\xlink\XLinkConnection.cpp(27): warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] ..\src\xlink\XLinkConnection.cpp(42): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data
[build] ..\src\xlink\XLinkConnection.cpp(92): warning C4267: 'argument': conversion from 'size_t' to 'const unsigned int', possible loss of data
[build] ..\src\xlink\XLinkConnection.cpp(205): warning C4267: 'argument': conversion from 'size_t' to 'unsigned long', possible loss of data
[build] ..\src\xlink\XLinkConnection.cpp(330): warning C4996: 'strncat': This function or variable may be unsafe. Consider using strncat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] ..\src\xlink\XLinkConnection.cpp(336): warning C4996: 'strncat': This function or variable may be unsafe. Consider using strncat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] ..\src\xlink\XLinkConnection.cpp(338): warning C4996: 'strncat': This function or variable may be unsafe. Consider using strncat_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
[build] [41/43  83% :: 12.147] Building CXX object CMakeFiles\depthai-core.dir\src\openvino\OpenVINO.cpp.obj
[build] [41/43  86% :: 12.281] Building CXX object CMakeFiles\depthai-resources.dir\__cmrc_depthai-resources\intermediate\depthai-bootloader-0.0.11.cmd.cpp.obj
[build] [41/43  88% :: 12.738] Building CXX object CMakeFiles\depthai-core.dir\src\device\Device.cpp.obj
[build] ..\src\device\Device.cpp(422): warning C4101: 'ex': unreferenced local variable
[build] ..\src\device\Device.cpp(567): warning C4101: 'ex': unreferenced local variable
[build] [41/43  90% :: 13.352] Building CXX object CMakeFiles\depthai-core.dir\src\utility\Resources.cpp.obj
[build] [41/43  93% :: 13.360] Building CXX object CMakeFiles\depthai-core.dir\src\pipeline\datatype\StreamPacketParser.cpp.obj
[build] ..\src\pipeline\datatype\StreamPacketParser.cpp(168): warning C4267: 'initializing': conversion from 'size_t' to 'uint32_t', possible loss of data
[build] [41/43  95% :: 15.210] Building CXX object CMakeFiles\depthai-resources.dir\__cmrc_depthai-resources\intermediate\depthai-device-fwp-5e4974e930f4ecbe1bf718463f6a5da664e68788.tar.xz.cpp.obj
[build] [42/43  97% :: 15.248] Linking CXX static library depthai-resourcesd.lib
[build] [43/43 100% :: 15.514] Linking CXX static library depthai-cored.lib
[build] Build finished with exit code 0

Expected
No warnings of unused vars, deprecated functions, potentially unsafe truncation, etc.

Thank you for the thorough report!

@diablodale if you are well versed on MSVC side of things, you can create a PR addressing some of those and I'll take a look at it.
Otherwise will check those out once I have more time on hands.

I can prob do some of these. I suspect many of them are related to 64-bit compile. GSL::narrow_cast<> is the modern way to do those truncations, e.g. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#es46-avoid-lossy-narrowing-truncating-arithmetic-conversions.
While the deprecated/unsafe functions like strncpy() are likely in the class of security/buffer protection and might need a holistic look. The latter you can do quickly while I might need significant time to grok the corpus of code.
I'll look either way. Gimme a week.

I'd like to bring in GSL as well - don't know about public usage though. I guess it would be okay if used only in private headers/sources. What do you think?
I already took a quick look at the strncpy() and the likes - will tackle those myself.
Thanks a lot!

@themarpe , to which branch should I do work and submit PRs?
develop, gen2_develop, or ...?

@diablodale to develop please.
I think I can add some defaults for this - will look into it

I have a PR ready, but ctest is failing on the unchanged develop branch https://github.com/luxonis/depthai-core/issues/77
When I get clarity on how to correct ctest so unit testing can be done, I can submit the PR.
I request your input and/or review on several topics -- they will be highlighted in the PR. I can always update the PR. 😄 I might have several commits in the PR as we work through it. I will gladly squash them all into one for the final.

Thank you!

@themarpe where does your team stand on the idea to use gsl? https://github.com/microsoft/GSL
I would recommend to first use its gsl::narrow_cast() for the noisy truncates/loss of data. Probably doing it in waves of commits and checking where it is applied that the trunc/loss is actually desired...or if a floor(), ceil(), etc. is more appropriate.

I'm in favor of it - also for the span instead of having to do std::vector& assuming that caller will have data managed by a vector.
GSL should be also available as is by Hunter although not sure if the latest.
We'd have to specify the version for it if we use it publically, as we did with nlohmann json the other day


use TextIOWrapper to read from bufferedreader instead

reading lines break whenever unicode character <U+2028> appears

Please advise if I need to make any changes for the python 3.4 test failure. It seems like an environment problem to me.

Thank you for your contribution. I will look into this during this week and give you a response. 👍

The issue with Python 3.4 is not something to be regarded in this PR as this PR is not breaking compatibility. We should pin the versions more exactly instead.
Thank you for your contribution!


HA Intergration not sending MQTT

Version of the custom_component
HACS 1.28.3
ThermIQ MQTT v1.3.5
Configuration
thermiq_mqtt:
mqtt_node: ThermIQ/ThermIQ-room2
language: 'en'   # Change friendly names of values. Implemented languages: en,se,fi,no,de
thermiq_dbg: False
Describe the bug
After updating to HA 2022.11 I am not able to change variables via the HA intergration (example change Indoor temperature target -> 21C). The intergration does not send a MQTT message when I change the value in Lovelace
The intergration does read the MQTT messages it gets from the ThermIQ-room2 and also via a HA automation to read in the indoor temperature sensor values also Node-Red messages are read by the intergration.
I have checked that I am able to send messages via the HA MQTT broker and HA automations can send MQTT messages.
I have been able to changes the variables before so the installation of ThermIQ MQTT intergration has been working.

Picture from MQTT Explorer, with data from the pump and 2 write one from Node-Red and the other from ThermIQ2 web

I have the same issue. Home Assistant 2022.11.1.

I will look into this the comming week together with the update for EVU function

I have the same issue as well.

This is most likely due to some other input_select/input_number not being properly/fully configured. See this post in HA forum

Unfortunately I still have problems. Have updated to v1.3.9 / core 2022.11.2 (in that order), and also uninstalled/reinstalled it from scratch. I see this in the logs:
2022-11-08 22:26:30.674 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/config/custom_components/thermiq_mqtt/__init__.py", line 177, in handle_home_assistant_started_event await create_entities_and_automations(hass) File "/config/custom_components/thermiq_mqtt/helper.py", line 293, in create_entities_and_automations await create_automations(hass) File "/config/custom_components/thermiq_mqtt/helper.py", line 308, in create_automations await add_automation(hass, OrderedDict(data), platform) File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 838, in _async_process_config automation_matches, config_matches = find_matches(automations, automation_configs) File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 826, in find_matches if automation_matches_config(automation, config): File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 805, in automation_matches_config return automation.name == name and automation.raw_config == config.raw_config AttributeError: 'str' object has no attribute 'name'

Do you have any other intergrations or things configured?
I have run on a fresh installed HA 2022.11.2, +MQTT, +HACS, + required lovelace plugins without seeing this making it hard to debug further.

I use several integrations. If I look at HACS i have Easee EV Charger, Blitzortung Lightning Detector, Xiaomi Cloud Map Extractor, Gardena Smart System, Node-RED Companion, Svensk Postutdelning, nordpool, and nordpool_diff. Kind of hard to know where to start...However I know that there were a Python version conflict between the Gardena and Easee a while ago, maybe this is a similar problem?
I'm not sure if I want to post my entire configuration.yaml, maybe it's enough with the TermIQ-specific config?
thermiq_mqtt:   mqtt_node: ThermIQ/ThermIQ-room-bb   language: 'se'   # Change friendly names of values. Implemented languages: en,se,fi,no,de   thermiq_dbg: False

I'm having the same issue. Out of the integrations DreamT80 mentioned nordpool is the only one we have in common.

Maybe try to disable them all and then enable one by one to see when it failing.
I will look into another way of implementing this in thermiq to make it more robust but I need help pinpointing on integration that fails so that I can debug myself

Hi
I also experince the same issue after update. I have also had the nordpool - tried to remove it but it dosen't help so even that this is a common thing between the posts it seems not to be the reason.

I have neither of those integrations and still experience the same issue.
Something must have happened with the 2022.11-update.

Then try to disable u till thermiq works. Ight be more than one other causing it

Hi, same issue - have nordpool:
"2022-11-09 13:43:40.303 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration thermiq_mqtt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-09 13:43:40.305 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-09 13:43:40.306 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nordpool which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-11-09 13:44:04.005 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform nordpool is taking over 10 seconds.
2022-11-09 13:44:11.326 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities input_number.thermiq_mqtt_indoor_requested_t or it is/they are currently not available" ... etc
BTW - if i remember right there were something Thermiq related automation(s) in /config/automation/dashboard before updates - now it/they seems  to disappeared..

The initial warnings can safely be ignored. It's commercial before the first mqqt message is received.

I am havin the exact same issue (as describes in issue 37) and reference to components/automation/init.py:805 The lines in the thermiq-mqtt component are slightly shiftet, perhaps due to the latest update?
Traceback (most recent call last):
File "/config/custom_components/thermiq_mqtt/init.py", line 177, in handle_home_assistant_started_event
await create_entities_and_automations(hass)
File "/config/custom_components/thermiq_mqtt/helper.py", line 293, in create_entities_and_automations
await create_automations(hass)
File "/config/custom_components/thermiq_mqtt/helper.py", line 308, in create_automations
await add_automation(hass, OrderedDict(data), platform)
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 838, in _async_process_config
automation_matches, config_matches = find_matches(automations, automation_configs)
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 826, in find_matches
if automation_matches_config(automation, config):
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 805, in automation_matches_config
return automation.name == name and automation.raw_config == config.raw_config
AttributeError: 'str' object has no attribute 'name'

I am havin the exact same issue (as describes in issue 37) and reference to components/automation/init.py:805 The lines in the thermiq-mqtt component are slightly shiftet, perhaps due to the latest update? I don't have the Nordpool integration installed. From HACS I only have "passive BLE monitor integration", "Deutscher Wetterdienst" and "ICS" installed.
Traceback (most recent call last): File "/config/custom_components/thermiq_mqtt/init.py", line 177, in handle_home_assistant_started_event await create_entities_and_automations(hass) File "/config/custom_components/thermiq_mqtt/helper.py", line 293, in create_entities_and_automations await create_automations(hass) File "/config/custom_components/thermiq_mqtt/helper.py", line 308, in create_automations await add_automation(hass, OrderedDict(data), platform) File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 838, in _async_process_config automation_matches, config_matches = find_matches(automations, automation_configs) File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 826, in find_matches if automation_matches_config(automation, config): File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 805, in automation_matches_config return automation.name == name and automation.raw_config == config.raw_config AttributeError: 'str' object has no attribute 'name'

Same issue here

I have same issue. Glad to see it is not only me and it's more global problem
I don't have any of the integrations mentioned above. It worked fine last time I tried to change something. But it was few weeks ago. Now everything I change via the integration and the dashboard is reverted. But if I change it on the heat pump it reads it fine. Basically it acts now as "read only"

Please revert back to 1.3.5 for a known working setup.

I need your help with the ha 2022.11 issue as I have a fully working setup.
In order to debug it I need your help to set up a configuration that fails  so please pinpoint to one specific config that fails.

Please revert back to 1.3.5 for a known working setup.

It actually didn't work from 1.3.5
When I noticed it doesn't work, I updated to latest version since I thought it would fix it. It didn't. I honestly cannot say when it appeared since only today I have noticed it. I am on HA 2022.11.1  . I was on 1.3.5 and it didn't work and then on latest.
Hope it helps to get to the bottom of this

Reverted to 1.3.5 scrip and love_lace. Same issue, same error message. Animations works in 1.3.5.

Then  help me figure out why it breaks for you and works for.me with plain 2022.11.2

I am sorry for the silly question or claim . But are you positive it works for you ? When you change the parameter in the dashboard. Does it change in the heat pump itself?
I honestly don't know how to recreate or trace back to a working state since it just appeared . The only changes I have done lately were updating HA. So I suspect it is related to that. I have now update to 2022.11.2 to see if it fixes it. But no. Still same issue. It changes, seems to be working but then changes back. Tried to restart already everything including the thermiq -mqtt module which connected to the heat-pump. Still works as "read only" , won't make changes in the heat pump.

Yes, it works in both read and write.
The "connection " btw input_number (what you can get Iin the ui) and the service of sending an mqtt message is broken by some other integration not being complete in its definition of input_number or input_select
Again, if you disable all integrations except thermiq  will it work?
Give me ONE integration that makes thermiq fail so that I can debug why......

Ok I will try and see if I can find out something

I haven't tried disabling the other integrations (I'm afraid it will mess upp a lot in my HA install), but instead i did a clean install of HassOS 9.3/core 2022.11.2 (a virtual machine), installed ThermIQ (v1.3.5, v1.3.9 didn't seem available right now?)  and added the integrations one after another. This didn't break the the ThermIQ installation.
Could this be an upgrade related issue, where a configuration is created in a certain way, and gets broken when doing updates? Due to changes made in the HA core? I think that maybe HA is changed regarding how to match/add automations, which maybe affects automations that were added earlier.
Maybe the problem can be recreated in the following way?

Install HA with an older core (2022.10.5, but preferably older).
Install ThermIQ (v1.3.5 or older). Automations gets added by the integration.
Upgrade the HA core to 2022.11.2 (does it still work?)
Upgrade ThermIQ to v1.3.9 (does it still work?)

Thanks, I'll try that

So this i what i got so far.
Tried to downgrade both MQTT addon and Thermiq = No luck.
Tried to downgrade HA Core without luck all the way down to -> 2022.10.0 = this version seams to work fine for me.

@tgmos : Do you have aný other automations? The error message above comes when init:ing an automation.
I will try to run a Dev Container of 2022.10.0 and upgrade it to 2022.11.2 and see if that breaks stuff.
The debug in a virtual machine on a pc is actually quite good even for a beginner like me

I have a lot of automations and addons. So i upgraded from 22.10 to 22.11.2 and it broke. Downgraded to 22.10 and still broken. So im not sure its version related. What i did to fix the issue now was to delete the mqtt thermiq information in mqtt explorer.

"What i did to fix the issue now was to delete the mqtt thermiq information in mqtt explorer."
Can you elaborate, i.e what steps where taken to brake, and fix, and what has MQTT Eplorer to do with it?

Looking at the error message:
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 805, in automation_matches_config return automation.name == name and automation.raw_config == config.raw_config AttributeError: 'str' object has no attribute 'name'
This is now functionality added to HA during autumn

In HA, i tried to change targeted indoor temp and/or setting heatpump mode to off or auto. It looks like it works but reverts back to old state after some time. There is no mqtt write produced then changing. So after i confirmed that its not working i deleted the topics "ThermIQ -> ThermIQ-room-bb" and the announce topic in MQTT Explorer, then tried changing mode/temp again and it produces a write command, and iv confirmed it on the heatpump.

HA:
When changing an input_number it displays it's new value trigger an automation that sends an MQTT wite message. The heatpump changes it's value and confirms back with a complete register log which is used, again with an automation, to update the input_number.
When the write automation fails (or isn't installed or ...) you get the behaviour you describe
MQTT Explorer
I don't understand how this can affect HA all

You are right, disregard the above. The only thing i can say for sure is that 2022.10.5 works for me without disabling any addons or automations, but in 11.0 ThermIQ is broken for some reason.

I have now been able to reproduce the issue:

Clean install HA 2022.11.02, +MQTT, +HACS, +ThermIQ (inc lovelace)
This works fine

Add an automation through the GUI, i.e "at Sunrise create event"

Restart and ThermIQ will now fail. I need to review the whole concept of "built in automations"

Is it possible to manually adjust the value for the indoor room temperature?
I mean - it's never possible to adjust that value directly on the heat pump manually - you have to go through the ThermIQ-module and it "sends" a value for the temperature, just as it was a real temperature sensor attached to the heat pump.
Is there a way to temporarily do this manually from HA or through MQTT Explorer for example?

Is it possible to manually adjust the value for the indoor room temperature?
I mean - it's never possible to adjust that value directly on the heat pump manually - you have to go through the ThermIQ-module and it "sends" a value for the temperature, just as it was a real temperature sensor attached to the heat pump.
Is there a way to temporarily do this manually from HA or through MQTT Explorer for example?
As it is now, the indoor temperature defaults to 20.5 degrees.

@Dauzzen , you can publish MQTT messages directly in HA, for example via an automation (the action MQTT: Publish is a way to go). I haven't used it myself (yet), but in theory this could work. There is also possible to publish MQTT commands in Node-Red if you're using that.

@ThermIQ Anders, are you making any progress in this? I don't want to stress you or anything ("no cow on the ice" as we say in Sweden ;) ), but it would be nice to know if you see a solution in the near future? Else I might upgrade anyway and set values via home built automations instead.

I believe the services are still working:
thermiq_mqtt.write_id
thermiq_mqtt.write_reg
thermiq_mqtt.write_mode
thermiq_mqtt.set_indr_t
thermiq_mqtt.set_evu
You could give that a try. Then of course sending "raw" mqtt messages are possible with ha, nodeRed, MQTT-Explorer etc

I'm halfway through a major restruct of the code to remove the need for manual entry into configuration.yaml and to alllow more than on heatpump. And of course, finding a way through for updating inputs and sending mqtt messages  that is now broken.
It won't happen this week but likely ready in November (Year is intentionally left out)

I believe the services are still working: thermiq_mqtt.write_id thermiq_mqtt.write_reg thermiq_mqtt.write_mode thermiq_mqtt.set_indr_t thermiq_mqtt.set_evu
You could give that a try. Then of course sending "raw" mqtt messages are possible with ha, nodeRed, MQTT-Explorer etc

Great! Can you give examples on how to use the services? Couldn't find it in the documentation. For the moment i'd like to set the requested indoor temp (which i guess I use thermiq_mqtt.set_indr_t with a value of 1?), and I'd also want to set the hotter starting temperature (.thermiq_mqtt_hotwater_start_t).

@DreamT80 sending messages with Node-RED extension at least works nicely. To test setting indoor target temperature (d50) to 20 C, you could create an inject node with msg.payload = {"d50":20}
And then have MQTT out node with your MQTT broker selected and with write topic: ThermIQ/ThermIQ-room2/write

Hotwater start temp would be d58, you can find the register list from the install guide: https://thermiq.net/ThermIQ_MQTT_Installation.pdf
@ThermIQ while restructing the code, may I propose to include also HA entity for 'rssi' (wifi signal strength)?

@DreamT80 sending messages with Node-RED extension at least works nicely. To test setting indoor target temperature (d50) to 20 C, you could create an inject node with msg.payload = {"d50":20} And then have MQTT out node with your MQTT broker selected and with write topic: ThermIQ/ThermIQ-room2/write  Hotwater start temp would be d58, you can find the register list from the install guide: https://thermiq.net/ThermIQ_MQTT_Installation.pdf
@ThermIQ while restructuring the code, may I propose to include also HA entity for 'rssi' (wifi signal strength)?

Thanks, @kheikola! I think I will use HA for sending messages, but the principle should the same when using MQTT.
It would however be nice to know how to use the thermiq_mqtt-service. The data should be the same (sending data to dXX), but I guess the payload should be formatted differently.

Isn't there some info if you go to developer tools services and select it?

Isn't there some info if you go to developer tools services and select it?

Yes, as soon as I understood how it worked.. :). Works fine. Thank you!

I have some trouble setting a dynamic value, i.e. from a HA entity.
A static value works fine
service: thermiq_mqtt.write_id
data: {"register_id":"sensor.thermiq_mqtt_indoor_requested_t", "value":21.0}

But, I can't manage it to work with a dynamic value:
service: thermiq_mqtt.write_id
data: {"register_id":"sensor.thermiq_mqtt_indoor_requested_t", "value":{{ states('sensor.heat_capacitor_evaluated_heat') | float }} }

I get
No MQTT message sent due to missing value:[21.0]
in the log, hinting that the syntax probably isn't correct. But I don't know how to correct it..

The brave can now try out the v2.0.0 release where this should be solved. Please note that the setup is now done through a graphical flow when adding the integration. Please remove all entries from configuration.yaml

hmm I was brave :)
Updated, removed the entries in configuration.yaml.  restarted. added integration. double checked correct node-name. then restarted again.
the Lovelace is broken thought. do I need to reconfigure it too?

First, check with HA Developer Tools to see if you have the input instances and there are values in them. If you have instancess but no values you are likely not having the correct mqtt node name. Mine is ThermIQ/ThermIQ-room2, note that there is no slash in the beginning nor end....
If not, do you have anything in the log to help?
Remove the integration, restart and add (and restart?) to update settings

Yes I have the same  ThermIQ/ThermIQ-room2 . I have copied it from the configuration and double checked in mqtt explorer
checked in HA developer.  value unavailable
tried to remove - restart - add - restart.
or maybe you meant to remove it completly from HACS ? I have only removed from the integration panel

It's not needed to completely remove it.
Update to v2.0.2 and check the logs, there should be some info there to post here

Ok, done it. this is what I found in the logs about ThermIQ. 3 different errors:
This error originated from a custom integration.
Logger: custom_components.thermiq_mqtt
Source: custom_components/thermiq_mqtt/init.py:52
Integration: ThermIQ MQTT Integration (documentation, issues)
First occurred: 23:15:29 (1 occurrences)
Last logged: 23:15:29
Set up ThermIQ-MQTT integration entry vp1
This error originated from a custom integration.
Logger: custom_components.thermiq_mqtt
Source: custom_components/thermiq_mqtt/init.py:38
Integration: ThermIQ MQTT Integration (documentation, issues)
First occurred: 23:15:29 (1 occurrences)
Last logged: 23:15:29
Set up ThermIQ-MQTT integration
This error originated from a custom integration.
Logger: custom_components.thermiq_mqtt.heatpump
Source: custom_components/thermiq_mqtt/heatpump/init.py:221
Integration: ThermIQ MQTT Integration (documentation, issues)
First occurred: 23:15:29 (1 occurrences)
Last logged: 23:15:29
thermiq_mqtt_vp1 mqtt_node: [ThermIQ/ThermIQ-room2]

None of them are errors but but i wanted the message to come through.
Any sensorn, inputs etc in the developer tool?

ok I check now. yes sensors appear in the HA developer. I see I have still the old entities helpers which are unavailable but new entities show values.
just not sure why the Lovelace card is broken?

Make sure you have latest Lovelace.
You can clean out the old in settings/integration/devices

I did copy the latest one. it must be that new since the sensor names now are "sensor.thermiq_mqtt2_vp1_" instead of the previous "sensor.thermiq_mqtt2"

now I got this. made new dashboard put the code in raw configuration

What does the MQTT message look like when you try to change the value?
What is the option MQTT Debug Write set to?
MQTT Explorer is a great tool

I have enabled debug in the integration setup
This is what it looks like in mqtt explorer after I change the value

Hint. Disable "MQTT Debug Write" if you want to actual write to the HP. As you can see the end-point whit Debug enable is not correct. Great for debug, not so great if you want the heatpump to take action.

Hint. Disable "MQTT Debug Write" if you want to actual write to the HP. As you can see the end-point with Debug enable is not correct. Great for debug, not so great if you want the heatpump to take action.

Thanks for the hint. didnt know that. I have done it though and restarted home assistant but it still not working :(

Ok, so now on version 2.0.2 after I have removed, restarted , installed , restarted , have the debug disabled . it WORKS ! :)
thank you very much! I hope others can confirm!

Great, I've focused on getting basic functionality back, and less on config flow and documentation. As mentioned "For the brave" and now also lucky :-)

Thank You, Version 2.02 works fine for me!

I got it also working. Steps taken:

Remove current integration in HACS and Lovelace YAML
Restart
Install 2.0.2 in HACS
Restart
Install integration under settings Devices & Services
Restart
Add new Lovelace Card

Now MQTT messages are being sent to the HeatPump.
Still to do is to clean out the old Entities (Sensors) just need to find out where :/

I have cleaned them out in the "helpers" section. nearly all entites are created by helpers. If you go to the helpers section you will see a huge list. sort them by name and remove all these that dont have "vp1" the the name.

I'm now on 2.0.3 and the lovelace control works again!
However I'm now missing all the thermiq_mqtt services. Without those I'm not able to set my automations up again.
Is there any way to get theese back? I've tried reinstalling the Thermiq stuff but made no difference.

Therese are no services (yet). But As this integration builds on vanilla input_number I  think you can use the default services of these

Hi guys, I followed this thread and fixed occured problem by installing 2.0.3. Everything seems to be working now. I set the language to Finnish (fi) in the initial setup and some of the sensors aren't translated perfectly. I would like to fix sensor translations, could you just point me to right direction? How can I fix sensor "friendly name" and icon?

I would happily accept changes to any translations or new languages. All translation tables are in heatpunp/thermiq_regs.py.
Either check out your own github version, update, and make a pull request or mail me an updated version to add.

Therese are no services (yet). But As this integration builds on vanilla input_number I think you can use the default services of these

Yep, this worked fine (thank you):
service: input_number.set_value
data: {"entity_id": "input_number.thermiq_mqtt_vp1_indoor_requested_t", "value":20}

I would happily accept changes to any translations or new languages. All translation tables are in heatpunp/thermiq_regs.py.
Either check out your own github version, update, and make a pull request or mail me an updated version to add.

Thanks for pointing me to the right direction. I will not open any new issues for this. I'll just create a branch and edit the file there. I will make a pull request as I have it done. Might take some time to go forward with this when I have time to do it. I'll use Thermia Heatpump manual to match the translations to the manual and Heatpump menu terminology. Also if manual or menus have unnatural Finnish impressions I'll fix them to be more natural. (teacher's occupational hazards :D )

I would greatly appreciate that! I've had some finnish support doing it but I have no way to check. Neither are the swedish names 100%
The settings displayed in the lovelace "fold"-panels is based on the value of the field "panel" and in each panel the "panel_order". If you also find a more natural way of organizing the different settings in the lovelace "fold"-panels you can change these but it will not take effect directly but I will then regenerate the lovelace file accordingly.

I will close this one now as I have received positive feedback from several brave testers, thank you!
There are still things to fix but the general crash from HA 2022.11 is now considered resolved in v2.x


params with upper-case characters

Looks like the parameters with upper-case characters don't recognition with 'isset' function.
For example, config.toml has parameter
googleAnalytics = "UA-12345678-123"
But I get the message 'You must set a googleAnalytics UA-Code within the global config.toml Params.' on the page.
I've made a changes in the file themes\gohugo-amp\layouts\partials\amp\google-analytics.html:
from
{{ if isset $.Site.Params "googleAnalytics" }}
to
{{ if isset $.Site.Params "googleanalytics" }}
and everything is working now.
But the strings:
{{ printf "%s" $.Site.Params.googleAnalytics }}
{{ printf "%s" $.Site.Params.googleanalytics }}
work both.
The same problem in the file 'app-banner-header.html' and others.

@Intelligent2013 thanks for reporting this issue.
It should be fixed in the current branch develop. I'll make a versioned update in master as soon as its tested.
Related PR: https://github.com/wildhaber/gohugo-amp/pull/23/


Not able to connect to the chef server URL.

PyChef Version : 0.2.3
{
  "stackTrace": [
    [
      "/var/task/main.py",
      77,
      "my_handler",
      "if len(search) != 0:"
    ],
    [
      "/var/task/chef/search.py",
      82,
      "**len**",
      "return len(self.data['rows'])"
    ],
    [
      "/var/task/chef/search.py",
      59,
      "data",
      "self._data = self.api[self.url]"
    ],
    [
      "/var/task/chef/api.py",
      229,
      "__getitem__",
      "return self.api_request('GET', path)"
    ],
    [
      "/var/task/chef/api.py",
      225,
      "api_request",
      "response = self.request(method, path, headers, data)"
    ],
    [
      "/var/task/chef/api.py",
      208,
      "request",
      "response = self._request(method, self.url+path, data, dict((k.capitalize(), v) for k, v in request_headers.iteritems()))"
    ],
    [
      "/var/task/chef/api.py",
      195,
      "_request",
      "return urllib2.urlopen(request).read()"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      154,
      "urlopen",
      "return opener.open(url, data, timeout)"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      431,
      "open",
      "response = self._open(req, data)"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      449,
      "_open",
      "'_open', req)"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      409,
      "_call_chain",
      "result = func(*args)"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      1242,
      "https_open",
      "context=self._context)"
    ],
    [
      "/usr/lib64/python2.7/urllib2.py",
      1199,
      "do_open",
      "raise URLError(err)"
    ]
  ],
  "errorType": "URLError",
  "errorMessage": "urlopen error [Errno -2] Name or service not known"
}

"errorMessage": "<urlopen error [Errno -2] Name or service not known>"

I can run the lambda main.py on my local machine and it connects to chef server and cleans up the URL. In my local setup, I can just pass the instance id value. But it fails to run the same code in the AWS. I tried both the VPC setup for lambda and non VPC. It fails in both the setups. Checked security groups etc for the chef server running in AWS , thats seems ok too. I even launched the lambda function in the same VPC as chef server but that didn't help also.

I am seeing this behavior also... when I am trying to connect to the VPC region
"errorMessage": "[Errno -2] Name or service not known"

Hi, i am also trying to access the git hub url , it fails , however i tried to access google.com
Still it fails with same error.
{
"stackTrace": [
[
"/var/task/lambda_function.py",
16,
"lambda_handler",
"ami = getLatestAMI(os.environ['ACCOUNT_NAME'],os.environ['AWS_REGION'])"
],
[
"/var/task/lambda_function.py",
24,
"getLatestAMI",
"response2 = urllib2.urlopen('http://www.google.com')"
],
[
"/usr/lib64/python2.7/urllib2.py",
154,
"urlopen",
"return opener.open(url, data, timeout)"
],
[
"/usr/lib64/python2.7/urllib2.py",
429,
"open",
"response = self._open(req, data)"
],
[
"/usr/lib64/python2.7/urllib2.py",
447,
"_open",
"'_open', req)"
],
[
"/usr/lib64/python2.7/urllib2.py",
407,
"_call_chain",
"result = func(*args)"
],
[
"/usr/lib64/python2.7/urllib2.py",
1230,
"http_open",
"return self.do_open(httplib.HTTPConnection, req)"
],
[
"/usr/lib64/python2.7/urllib2.py",
1200,
"do_open",
"raise URLError(err)"
]
],
"errorType": "URLError",
"errorMessage": "<urlopen error [Errno -2] Name or service not known>"


[MM-47256] Notifications native module

Summary
Use node-notifier for displaying native notifications.
Add support for sending test notification under Desktop Settings page
Ticket Link

https://mattermost.atlassian.net/browse/MM-47617
https://mattermost.atlassian.net/browse/MM-47256

Screenshots

Release Note
Use native module for notifications

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/24578
https://circleci.com/gh/mattermost/desktop/24577
https://circleci.com/gh/mattermost/desktop/24576

Artifact links:
https://output.circle-artifacts.com/output/job/d7e60b3c-7dd4-459c-8d1a-f473cf769008/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-ia32.zip
https://output.circle-artifacts.com/output/job/d7e60b3c-7dd4-459c-8d1a-f473cf769008/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-x64.zip
https://output.circle-artifacts.com/output/job/a4ded704-f691-4bbb-a677-433b975bb322/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-linux-x64.tar.gz
https://output.circle-artifacts.com/output/job/67f0ce92-8ba0-4c9e-8b38-78ec898c3006/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-m1.dmg
https://output.circle-artifacts.com/output/job/67f0ce92-8ba0-4c9e-8b38-78ec898c3006/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-x64.dmg

Thanks @tboulis
Seeing one issue on Windows 10, I can hear the notification sound, but no notification popup for messages or when I test "send notification"  in settings.
I did get "session expired" notifications, both sound and popup.
On macOS and Ubuntu this works as expected (sound and popup) for both new messages and testing the setting.


Error in BFloat16 extension

As spotted on CUDA.jl CI:
      From worker 2:	ERROR: LoadError: UndefVarError: `typetree_inner` not defined
      From worker 2:	Stacktrace:
      From worker 2:	 [1] getproperty(x::Module, f::Symbol)
      From worker 2:	   @ Base ./Base.jl:31
      From worker 2:	 [2] top-level scope
      From worker 2:	   @ ~/.cache/julia-buildkite-plugin/depots/3cc01fab-3357-4a7a-9294-cde2d3115a97/dev/Enzyme/ext/EnzymeBFloat16sExt.jl:6
      From worker 2:	 [3] include
      From worker 2:	   @ ./Base.jl:495 [inlined]
      From worker 2:	 [4] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
      From worker 2:	   @ Base ./loading.jl:2222
      From worker 2:	 [5] top-level scope
      From worker 2:	   @ stdin:3
      From worker 2:	in expression starting at /root/.cache/julia-buildkite-plugin/depots/3cc01fab-3357-4a7a-9294-cde2d3115a97/dev/Enzyme/ext/EnzymeBFloat16sExt.jl:1
      From worker 2:	in expression starting at stdin:3

Ought to be fixed in the newest release.


(FACT-3425) Remove logic for older Rubies

Previously, the dir_children method accounted for versions of Ruby older than 2.5. Facter currently only supports Ruby >= 2.5, so we no longer need to account for older versions.
This commit removes logic for older Rubies from the dir_children method.

I've updated this PR to keep the dir_children method, but simplify it.


⚠ Bofrost.at has degraded performance

In 8fb71ad, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2165 ms

Resolved: Bofrost.at performance has improved in 8114603 after 16 minutes.


Advanced pane collapse

There's no need for additional space between these two rows of buttons:

The Close button is basically always on the bottom, independend from the window hight. Maybe I can improve it by increase the hight of the editor dynamically.
I also thought to place PolicyExceptions in this window somehow but no clear idea yet.


SpreadSheet

can you make it so it will create a spreadsheet in that folder
thankyou

Dear Micheal,
I am pretty inexperienced with these things. I can possibly make a hex.
folder, for you, in the future, if it can help you.
But, in my beginning stages, of learning of these sorts of things, can you
reply with, ' a teacher's explanation ',
in why are you asking, this question of myself.
sincerely,
blair beekman

On Sat, Aug 18, 2018 at 1:24 PM, Michaelmeissner1997 <
<EMAIL_ADDRESS>wrote:
can you make it so it will create a spreadsheet in that folder

thankyou
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yasirkula/DownloadLinkGeneratorForGoogleDrive/issues/5,
or mute the thread
https://github.com/notifications/unsubscribe-auth/An1fTfZ9d1CHkIp96fvrJoDTMVMHp5Ikks5uSHgBgaJpZM4WCtVH
.

For now, here's a workaround for this issue:

create a new Google Sheet in your Drive
copy&paste the output of Download Link Generator to the A1 cell (it will automatically put each line to a different row)
select C1 and insert =LEFT(A1,FIND("~~~~~",SUBSTITUTE(A1," ","~~~~~",LEN(A1)-LEN(SUBSTITUTE(A1," ",""))))) next to the fx line above (credit)
select D1 and insert =MID(A1,FIND("~~~~~",SUBSTITUTE(A1," ","~~~~~",LEN(A1)-LEN(SUBSTITUTE(A1," ",""))))+1,LEN(A1)) next to the fx line above (credit)
select C1 and D1 cells, drag the blue square at the bottom right corner of the selection and drop it at the row the download links end
now select the populated C and D columns, copy them, right click a blank cell in your sheet and select Paste special-Paste values only
enjoy the results!


write an implementation that uses Deno

No sure exactly what this comment means. We are pretty happy with our current stack at the moment 🙂


problem after reboot, SSL Verification

Hello
I followed all steps and installed the chia blockchain pools-2021.may-25 and then the pool-reference.
I got the pool to run and everything looked like it worked well.
However i rebooted the computer and when i tried to start the pool again i get a SSL verification problem, and i have tried to reinstall on a new virtual machine just to make sure i did not mess anything up and it is the same thing after reboot.
I have not made any changes to any files exept the steps on how to start.
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host localhost:85
55 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verif
y failed: certificate signature failure (_ssl.c:1123)')]

Maby someone here have an idea on how i messed up?

Port 8555 is a default port used by a full_node RPC server.
I guess CA certificates between full_node and farmer(or something like that) does not match.

DId you find a solution for this?

I have not found any solution yet. Will do more testing today.
As ChiaMineJP said there is probably something with the CA certificates that get messed up?

I did solve it now. Looks like the i had to copy my CA cert from testnet7 folder to mainnet(that by some reason is the folder for testnet7) and everything worked. Don't know why it behaves like this. But it is running again.


Test for Add function and delele function

Tests with jest
We implemented the tests for the add function and for the remove function.
https://github.com/Alejandro-Bernal-M/To-do-list/blob/ddf7c21bd5a47e3d89fbd4bdb76b8017f805a8c4/src/addAndDelete.test.js#L4-L18

Thank you


Dynamic loading not supported when trying to require("module.so")

Hello @aarzilli
Thanks a lot for your work to create a go binding for lua C APIs.
Environment:

Golang: 1.20
Lua: 5.4.6
golua: last version

I am building a static go binary with the following command:
go build  -ldflags '-extldflags "-static"' -tags "luaa lua54 yara_static" -o app main.go

Compilation works fine, except that when my Lua file try to require a module (require 'rapidjson' that I installed via luarocks, it fails with: `error loading module 'rapidjson' from file '/where/lib/was/built/rapidjson.so':\n\tDynamic loading not supported".
Do you know why this is failing ?
Cheers.

Try removing the -static flag.

That actually worked, thank you @aarzilli .


Rebaseline ParallelDownloadsPerformanceTest

To accept a 0.5% regression

@bot-gradle test and merge

OK, I've already triggered a build for you.


during onboarding all the administrators have to sign in to open the …

…compound session and not only the quorum

Don't merge please, actually it seems only the quorum need to login.


PyWavelets error when calling methods

Hi, there's an error show up when i tried to import PHash
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-794d9086a39e> in <module>
----> 1 from imagededup.methods import PHash
      2 phasher = PHash()

~/miniconda3/envs/imagededup/lib/python3.8/site-packages/imagededup/methods/__init__.py in <module>
----> 1 from .hashing import PHash, AHash, DHash, WHash
      2 from .cnn import CNN

~/miniconda3/envs/imagededup/lib/python3.8/site-packages/imagededup/methods/hashing.py in <module>
      4 from typing import Dict, List, Optional
      5
----> 6 import pywt
      7 import numpy as np
      8 from scipy.fftpack import dct

~/miniconda3/envs/imagededup/lib/python3.8/site-packages/pywt/__init__.py in <module>
     14 from distutils.version import LooseVersion
     15
---> 16 from ._extensions._pywt import *
     17 from ._functions import *
     18 from ._multilevel import *

pywt/_extensions/_pywt.pyx in init pywt._extensions._pywt()

AttributeError: type object 'pywt._extensions._pywt.Wavelet' has no attribute '__reduce_cython__'

Can anyone help me with this?

You could create a new Conda environment to have consistent versions of packages.
conda create -n dedupEnv python=3.6
conda activate dedupEnv
pip install imagededup

It has helped me.

Hi @SinedYuk, thanks for the tip. I tried that method before and sadly resulted in the same error. I fixed it by building the package from source.


Used programatic settings panel

New version of the Run configuration settings editor  for IC 2021+. Old editor kept for IC <2021 due to lots of missing stuff for the programmatic editor.
New version of the editor also supports package and spec class selection using browsers 🤓

Doesn't work on <=203, same error as before I think:
2022-06-20 03:46:23,097 [  74368]  ERROR - llij.ide.plugins.PluginManager - lateinit property module has not been initialized
kotlin.UninitializedPropertyAccessException: lateinit property module has not been initialized
	at io.kotest.plugin.intellij.SettingsEditorPanel.<init>(SettingsEditorPanel.kt:36)
	at io.kotest.plugin.intellij.KotestConfiguration.getConfigurationEditor(KotestConfiguration.kt:8)
	at io.kotest.plugin.intellij.KotestConfiguration.getConfigurationEditor(KotestConfiguration.kt:6)
	at com.intellij.execution.impl.ConfigurationSettingsEditor.<init>(ConfigurationSettingsEditor.java:193)
	at com.intellij.execution.impl.ConfigurationSettingsEditorWrapper.<init>(ConfigurationSettingsEditorWrapper.java:58)
	at com.intellij.execution.impl.SingleConfigurationConfigurable.<init>(SingleConfigurationConfigurable.java:103)
	at com.intellij.execution.impl.SingleConfigurationConfigurable.editSettings(SingleConfigurationConfigurable.java:140)

I'm probably ok with just dropping support for these versions - who is using a 2/3 year old version of intellij that can't live with the current kotest plugin ?


Added --ask-tower-pass

This option will use click to prompt for a tower password if present. No more typing passwords on command line for your shell history to remember.

Coverage increased (+0.01%) to 63.981% when pulling 28e3dd76274753396d887b8c654d6a522efe2d3c on john-westcott-iv:ask-pass into a3bad1e117e35a056d36c9f8f3a6bad40781b900 on ansible:master.

what if, instead of a new option, we used your callback in the event that the string value of the existing password option was "ASK"? That will avoid lengthening the help text volume, and it's an approach that Tower/AWX itself has used for password prompting.

It would be very easy to allow prompting for all of the runtime variables. Is that something we want to do? I thought of it because I could see someone saying that want to be prompted for the username as well as the password.

I would stick to password for now, it's hard to imagine a good use case for prompting for those other things.


Add support for Base64url encoding (#1348)

This small and dirty change adds support for Base64url encoding & decoding.
I had only one concern though, when I intentionally broke the test, npm test was still returning successfully, so not really sure what's going on with that...

@gschier do you have any tips, why npm test doesn't fail when I intentionally break the tests I've added?

Never mind, I figured it out.

The review comments have been addressed, let me know if any other changes are needed. Thanks!

Awesome, thanks!

For some reason, this broke all of my existing encoding Tags. I had to remove and re-add them to get them to work. First it through a 400 and errored about attribute value. When I realized it was this tag, I went in and tried to fix it, but the preview constantly failed. Removing and re-adding caused it to work fine again.


bugfix(transform): Disable handlebars transform pre-Ember-1.13

Followup to #149, this disables all handlebars transforms in pre-1.13 Ember. The transforms break otherwise, so this is a way to allow users to still get the benefits of test selectors, even if they won't be stripped.

Can you enable CI testing for 1.12?

Hmm, I assumed that tests would have had to be rewritten for older Ember but it looks like everything just works! 😄 updated

@pzuraq: unfortunately that's only because we're currently missing an acceptance test for that functionality. I'm adding on in #152. I guess we should merge that first, rebase this and make whatever changes are necessary (which is probably not running that particular test for Ember < 1.13).

@pzuraq: #152 was merged

So I rebased and reran the tests locally. I thought it was weird because I expected some of the tests to fail, upon closer inspection several of them should have. It appears that because this addon may be triggering a bug in ember-cli-version-checker/ember-try where it reports the wrong Ember version. I'm not sure exactly what's going on here, but running ember try:one ember-1.11.4 --skip-cleanup locally resulted in ember-source not being removed from package.json.
I manually removed it and verified that tests failed without the changes from ember-compatibility-helpers.

Also worth noting, with the minimal examples in tests 1.11 actually does work. Dug into this locally and it seems like only certain block statements will trigger the bug, specifically link-tos but others could exist.
For our purposes, I'd still prefer outright disabling the transforms. We'll be finishing the update to 1.13 soon, so this is just a temp fix to get us over the finish line