1823825 | Message fixes | Address validation issues | 8

This PR is for user story 1823825.
Fixed an issue with missing table headers.
If these changes are not appropriate, please let me know. I'm only trying to clean up validation issues in this repo. So I can easily close this PR or modify it in whatever way is best for the content.

Docs Build status updates of commit e30d356:
:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/accelerator-hl7/encoding-characters-using-free-text.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/upgrade-biztalk-accelerator-for-hl7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-rosettanet/install-configure-biztalk-accelerator-for-rosettanet.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/adding-an-mx-send-port.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/install-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/message-repair-and-new-submission-service-processing.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md

Line 46, Column 2: [Warning-alt-text-missing] Missing alternate text for image '../../adapters-and-accelerators/accelerator-hl7/media/protmethod.gif'. Alt text is required for accessibility.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 51387df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/encoding-characters-using-free-text.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/upgrade-biztalk-accelerator-for-hl7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-rosettanet/install-configure-biztalk-accelerator-for-rosettanet.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/adding-an-mx-send-port.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/install-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/message-repair-and-new-submission-service-processing.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 07807df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/encoding-characters-using-free-text.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/upgrade-biztalk-accelerator-for-hl7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-rosettanet/install-configure-biztalk-accelerator-for-rosettanet.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/adding-an-mx-send-port.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/install-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/message-repair-and-new-submission-service-processing.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/upgrade-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/connect-to-oracle-ebs-in-visual-studio-using-add-adapter-metadata-wizard.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7532345:
:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/install-configure-biztalk-adapters-enterprise-applications.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/consume-a-wcf-lob-adapter-sdk-adapter-in-a-biztalk-server-project.md
:bulb:Suggestion
View
Details

biztalk/adapters-and-accelerators/accelerator-hl7/encoding-characters-using-free-text.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/upgrade-biztalk-accelerator-for-hl7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-rosettanet/install-configure-biztalk-accelerator-for-rosettanet.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/adding-an-mx-send-port.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/install-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/message-repair-and-new-submission-service-processing.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/upgrade-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/connect-to-oracle-ebs-in-visual-studio-using-add-adapter-metadata-wizard.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/connect-to-oracle-ebs-in-visual-studio-using-add-adapter-service-reference.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/install-custom-rfcs-for-the-data-provider-for-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/install-microsoft-biztalk-adapter-for-sql-server-2016.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/consume-a-wcf-lob-adapter-sdk-adapter-in-a-net-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/install-the-wcf-lob-adapter-sdk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/what-is-the-windows-communication-foundation-line-of-business-adapter-sdk.md
:white_check_mark:Succeeded
View

biztalk/core/a-bitwiseand-comparison-cannot-be-done-for-this-xsd-type.md
:white_check_mark:Succeeded
View

biztalk/core/a-bts-mime-error-was-encountered-when-attempting-to-decode-an-as2-message.md
:white_check_mark:Succeeded
View

biztalk/core/a-failure-occurred-in-processing-x12-message-on-send-port-no-party-with-name.md
:white_check_mark:Succeeded
View

biztalk/core/a-file-not-found-exception-occurred-while-reflecting-a-biztalk-assembly.md
:white_check_mark:Succeeded
View

biztalk/core/action-errors.md
:white_check_mark:Succeeded
View

biztalk/core/agreement-found-for-the-protocol-is-in-disabled-or-expired-state.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/install-configure-biztalk-adapters-enterprise-applications.md

Line 872, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/consume-a-wcf-lob-adapter-sdk-adapter-in-a-biztalk-server-project.md

Line 45, Column 5: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 31f4197:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/encoding-characters-using-free-text.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/programming-guide-and-sdk-tools.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/upgrade-biztalk-accelerator-for-hl7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-rosettanet/install-configure-biztalk-accelerator-for-rosettanet.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/adding-an-mx-send-port.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/install-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/message-repair-and-new-submission-service-processing.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-swift/upgrade-biztalk-accelerator-for-swift.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/connect-to-oracle-ebs-in-visual-studio-using-add-adapter-metadata-wizard.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/connect-to-oracle-ebs-in-visual-studio-using-add-adapter-service-reference.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/install-custom-rfcs-for-the-data-provider-for-sap.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/install-microsoft-biztalk-adapter-for-sql-server-2016.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/install-configure-biztalk-adapters-enterprise-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/consume-a-wcf-lob-adapter-sdk-adapter-in-a-biztalk-server-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/consume-a-wcf-lob-adapter-sdk-adapter-in-a-net-project.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/install-the-wcf-lob-adapter-sdk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/wcf-lob-adapter-sdk/what-is-the-windows-communication-foundation-line-of-business-adapter-sdk.md
:white_check_mark:Succeeded
View

biztalk/core/a-bitwiseand-comparison-cannot-be-done-for-this-xsd-type.md
:white_check_mark:Succeeded
View

biztalk/core/a-bts-mime-error-was-encountered-when-attempting-to-decode-an-as2-message.md
:white_check_mark:Succeeded
View

biztalk/core/a-failure-occurred-in-processing-x12-message-on-send-port-no-party-with-name.md
:white_check_mark:Succeeded
View

biztalk/core/a-file-not-found-exception-occurred-while-reflecting-a-biztalk-assembly.md
:white_check_mark:Succeeded
View

biztalk/core/action-errors.md
:white_check_mark:Succeeded
View

biztalk/core/agreement-found-for-the-protocol-is-in-disabled-or-expired-state.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@damabe Hey Dan - Is this PR ready to be merged?

@MandiOhlinger - Yes, this PR is ready for merge.


[Bug] Cannot find module error for libs that ng-doc uses

Is this a regression?
I don't know
Description
Hello,
I've just installed ng-doc v17.0.0 and couldn't run ng serve. I haven't user ng-doc before.
I used ng add @ng-doc/add and I had to fix some missing things by your manual guide.
Please provide the exception or error you saw
X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/boolean-control/boolean-control.component.d.ts:2:26:
      2 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2420: Class 'NgDocBooleanControlComponent' incorrectly implements interface 'NgDocTypeControl<boolean | undefined>'.
  Type 'NgDocBooleanControlComponent' is missing the following properties from type 'NgDocTypeControl<boolean | undefined>': writeValue, registerOnChange, registerOnTouched [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/boolean-control/boolean-control.component.d.ts:4:21:
      4 │ export declare class NgDocBooleanControlComponent extends DIControl...
        ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/number-control/number-control.component.d.ts:2:26:
      2 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2420: Class 'NgDocNumberControlComponent' incorrectly implements interface 'NgDocTypeControl<number>'.
  Type 'NgDocNumberControlComponent' is missing the following properties from type 'NgDocTypeControl<number>': writeValue, registerOnChange, registerOnTouched [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/number-control/number-control.component.d.ts:4:21:
      4 │ export declare class NgDocNumberControlComponent extends DIControl<...
        ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/string-control/string-control.component.d.ts:2:26:
      2 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2420: Class 'NgDocStringControlComponent' incorrectly implements interface 'NgDocTypeControl<string>'.
  Type 'NgDocStringControlComponent' is missing the following properties from type 'NgDocTypeControl<string>': registerOnChange, registerOnTouched [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/string-control/string-control.component.d.ts:4:21:
      4 │ export declare class NgDocStringControlComponent extends DIControl<...
        ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/type-alias-control/type-alias-control.component.d.ts:2:26:
      2 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2420: Class 'NgDocTypeAliasControlComponent<T>' incorrectly implements interface 'NgDocTypeControl<T>'.
  Type 'NgDocTypeAliasControlComponent<T>' is missing the following properties from type 'NgDocTypeControl<T>': writeValue, registerOnChange, registerOnTouched [plugin angular-compiler]

    node_modules/@ng-doc/app/type-controls/type-alias-control/type-alias-control.component.d.ts:4:21:
      4 │ ...rt declare class NgDocTypeAliasControlComponent<T> extends DICon...
        ╵                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/cdk/combobox-host/combobox-host.component.d.ts:5:60:
      5 │ ...{ DICompareFunction, DICompareHost, DIControl } from 'di-controls';
        ╵                                                         ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/classes/base-input/base-input.d.ts:2:26:
      2 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls/controls/control' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/classes/base-input/base-input.d.ts:3:32:
      3 │ import { DIControlConfig } from 'di-controls/controls/control';
        ╵                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/checkbox/checkbox.component.d.ts:2:31:
      2 │ import { DIStateControl } from 'di-controls';
        ╵                                ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/clear-control/clear-control.component.d.ts:3:26:
      3 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/combobox/combobox.component.d.ts:5:26:
      5 │ import { DIControl } from 'di-controls';
        ╵                           ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/option/option.component.d.ts:4:31:
      4 │ import { DIStateControl } from 'di-controls';
        ╵                                ~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module '@tinkoff/ng-polymorpheus' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/overlay-container/overlay-container.component.d.ts:6:44:
      6 │ ...rt { PolymorpheusOutletDirective } from '@tinkoff/ng-polymorpheus';
        ╵                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module 'di-controls' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/toggle/toggle.component.d.ts:3:31:
      3 │ import { DIStateControl } from 'di-controls';
        ╵                                ~~~~~~~~~~~~~

X [ERROR] TS2420: Class 'NgDocToggleComponent<T>' incorrectly implements interface 'ControlValueAccessor'.
  Type 'NgDocToggleComponent<T>' is missing the following properties from type 'ControlValueAccessor': writeValue, registerOnChange, registerOnTouched [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/components/toggle/toggle.component.d.ts:5:21:
      5 │ export declare class NgDocToggleComponent<T> extends DIStateControl...
        ╵                      ~~~~~~~~~~~~~~~~~~~~

X [ERROR] TS2307: Cannot find module '@tinkoff/ng-polymorpheus' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@ng-doc/ui-kit/types/content.d.ts:2:81:
      2 │ ...eusHandler, PolymorpheusTemplate } from '@tinkoff/ng-polymorpheus';

### OS

Windows

### Browser

Chrome

### Node version

20.9.0

### Anything else?

_No response_

Hi thanks for the issue! Looks like some packages were not installed, I'll fix it tomorrow!

I have fixed several issues with the automatic package installation caused by the latest update. However, I couldn't reproduce this particular issue. I suspect that, for some reason, the peerDependencies of the packages were not installed on your end. Please try deleting node_modules and package-lock.json, and then reinstall all packages, including the latest version of NgDoc (17.1.2).
Also, ensure that you are using the latest version of Angular, including the latest patch version of @angular-devkit/build-angular (the Angular team renamed one of the builder methods, so NgDoc won't work on version 17.0.0 but will work on version 17.0.2).

I had @angular-devkit/build-angular v17.0.0. Anyway, I updated all versions and install it again. Unfortunately, it didn't help.
One more thing which I forgot to say before. I have library and demo app with documentation. Demo app import styles from library and it doesn't work as well.
X [ERROR] Can't find stylesheet to import.
  ╷
5 │ @use "projects/mat-timepicker" as mat-timepicker;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  projects\demo-app\src\styles.scss 5:1  root stylesheet [plugin angular-sass]

    angular:styles/global:styles:2:8:
      2 │ @import 'projects/demo-app/src/styles.scss';

I had some warnings while installing dependencies
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@ng-doc/builder ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@ng-doc/builder ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>
package.json dependencies
  "dependencies": {
    "@angular/animations": "^17.0.2",
    "@angular/cdk": "^17.0.1",
    "@angular/common": "^17.0.2",
    "@angular/compiler": "^17.0.2",
    "@angular/core": "^17.0.2",
    "@angular/flex-layout": "^15.0.0-beta.42",
    "@angular/forms": "^17.0.2",
    "@angular/material": "^17.0.1",
    "@angular/platform-browser": "^17.0.2",
    "@angular/platform-browser-dynamic": "^17.0.2",
    "@angular/router": "^17.0.2",
    "@ng-doc/app": "^17.1.2",
    "@ng-doc/builder": "^17.1.2",
    "@ng-doc/core": "^17.1.2",
    "@ng-doc/ui-kit": "^17.1.2",
    "rxjs": "~7.5.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.14.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^17.0.2",
    "@angular/cli": "^17.0.2",
    "@angular/compiler-cli": "^17.0.2",
    "@types/jasmine": "~3.10.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~4.0.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.1.0",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "~1.7.0",
    "ng-packagr": "^17.0.0",
    "typescript": "5.2.2"
  }

@dhutaryan as I understand your project is open source can I have a branch to test these errors? because it's quite difficult to say what goes wrong. I can't reproduce it on a clear project or on existing ones.

I think you can fork it and add ng-doc for demo app. Here is the link https://github.com/dhutaryan/ngx-mat-timepicker

@dhutaryan great, thank you! I'll check it today!

@dhutaryan I looked at the repository, and here's what I found:
The @angular/cdk and @angular/material packages were not updated in the master branch. I updated all packages, fixing all issues, and obtained the following package.json.

👉 package.json
{
"name": "ngx-mat-timepicker",
"version": "0.0.0",
"scripts": {
  "ng": "ng",
  "start": "ng serve",
  "build": "ng build --configuration production --base-href=/ngx-mat-timepicker/",
  "watch": "ng build --watch --configuration development",
  "test": "ng test",
  "build:lib": "ng build mat-timepicker --configuration production",
  "test:lib": "ng test mat-timepicker --code-coverage"
},
"private": true,
"dependencies": {
  "@angular/animations": "^17.0.4",
  "@angular/cdk": "^17.0.1",
  "@angular/common": "^17.0.4",
  "@angular/compiler": "^17.0.4",
  "@angular/core": "^17.0.4",
  "@angular/flex-layout": "^15.0.0-beta.42",
  "@angular/forms": "^17.0.4",
  "@angular/material": "^17.0.1",
  "@angular/platform-browser": "^17.0.4",
  "@angular/platform-browser-dynamic": "^17.0.4",
  "@angular/router": "^17.0.4",
  "rxjs": "~7.5.0",
  "tslib": "^2.3.0",
  "zone.js": "~0.14.2"
},
"devDependencies": {
  "@angular-devkit/build-angular": "^17.0.2",
  "@angular/cli": "^17.0.2",
  "@angular/compiler-cli": "^17.0.4",
  "@types/jasmine": "~3.10.0",
  "@types/node": "^12.11.1",
  "jasmine-core": "~4.0.0",
  "karma": "~6.3.0",
  "karma-chrome-launcher": "~3.1.0",
  "karma-coverage": "~2.1.0",
  "karma-jasmine": "~4.0.0",
  "karma-jasmine-html-reporter": "~1.7.0",
  "ng-packagr": "^17.0.0",
  "typescript": "5.2.2"
}
}

Next, I installed NgDoc using the command ng add @ng-doc/add. The migrations were successful, but I noticed that the application was not created with Angular 17, so not everything worked right away. The issue is that in NgDoc version 17, all migrations were updated to support Angular version 17, so your angular.json wasn't migrated. There are a few possible solutions:

You could install NgDoc version 16.7 first and then migrate to NgDoc version 17 using ng update @ng-doc/builder. However, I think this might cause more problems with package installation since your project is already on Angular version 17.

You can use the updated angular.json below, in which I made all the necessary fixes:

👉 angular.json
{
"$schema"<EMAIL_ADDRESS>"version": 1,
"cli": {
  "packageManager": "yarn"
},
"newProjectRoot": "projects",
"projects": {
  "demo-app": {
    "projectType": "application",
    "schematics": {
      "@schematics/angular:component": {
        "style": "scss",
        "changeDetection": "OnPush"
      },
      "@schematics/angular:application": {
        "strict": true
      }
    },
    "root": "",
    "sourceRoot": "projects/demo-app/src",
    "prefix": "demo",
    "architect": {
      "build": {
        "builder": "@ng-doc/builder:application",
        "options": {
          "outputPath": "dist/demo-app",
          "index": "projects/demo-app/src/index.html",
          "browser": "projects/demo-app/src/main.ts",
          "polyfills": ["projects/demo-app/src/polyfills.ts"],
          "tsConfig": "projects/demo-app/tsconfig.app.json",
          "inlineStyleLanguage": "scss",
          "stylePreprocessorOptions": {
            "includePaths": [""]
          },
          "assets": [
            {
              "glob": "**/*",
              "input": "node_modules/@ng-doc/app/assets",
              "output": "assets/ng-doc/app"
            },
            {
              "glob": "**/*",
              "input": "node_modules/@ng-doc/ui-kit/assets",
              "output": "assets/ng-doc/ui-kit"
            },
            {
              "glob": "**/*",
              "input": "ng-doc/demo-app/assets",
              "output": "assets/ng-doc"
            },
            "projects/demo-app/src/favicon.ico",
            "projects/demo-app/src/assets"
          ],
          "styles": [
<EMAIL_ADDRESS>            "projects/demo-app/src/styles.scss"
          ],
          "scripts": [],
          "allowedCommonJsDependencies": [
            "@ng-doc/core"
          ]
        },
        "configurations": {
          "production": {
            "budgets": [
              {
                "type": "initial",
                "maximumWarning": "500kb",
                "maximumError": "1mb"
              },
              {
                "type": "anyComponentStyle",
                "maximumWarning": "2kb",
                "maximumError": "4kb"
              }
            ],
            "fileReplacements": [
              {
                "replace": "projects/demo-app/src/environments/environment.ts",
                "with": "projects/demo-app/src/environments/environment.prod.ts"
              }
            ],
            "outputHashing": "all"
          },
          "development": {
            "optimization": false,
            "extractLicenses": false,
            "sourceMap": true,
            "namedChunks": true
          }
        },
        "defaultConfiguration": "production"
      },
      "serve": {
        "builder": "@ng-doc/builder:dev-server",
        "configurations": {
          "production": {
            "buildTarget": "demo-app:build:production"
          },
          "development": {
            "buildTarget": "demo-app:build:development"
          }
        },
        "defaultConfiguration": "development"
      },
      "extract-i18n": {
        "builder": "@angular-devkit/build-angular:extract-i18n",
        "options": {
          "buildTarget": "demo-app:build"
        }
      },
      "test": {
        "builder": "@angular-devkit/build-angular:karma",
        "options": {
          "main": "projects/demo-app/src/test.ts",
          "polyfills": "projects/demo-app/src/polyfills.ts",
          "tsConfig": "projects/demo-app/tsconfig.spec.json",
          "karmaConfig": "projects/demo-app/karma.conf.js",
          "inlineStyleLanguage": "scss",
          "assets": [
            "projects/demo-app/src/favicon.ico",
            "projects/demo-app/src/assets"
          ],
          "styles": [
            "projects/demo-app/src/styles.scss"
          ],
          "scripts": []
        }
      }
    }
  },
  "mat-timepicker": {
    "projectType": "library",
    "schematics": {
      "@schematics/angular:component": {
        "style": "scss",
        "changeDetection": "OnPush"
      }
    },
    "root": "projects/mat-timepicker",
    "sourceRoot": "projects/mat-timepicker/src",
    "prefix": "mat",
    "architect": {
      "build": {
        "builder": "@angular-devkit/build-angular:ng-packagr",
        "options": {
          "project": "projects/mat-timepicker/ng-package.json"
        },
        "configurations": {
          "production": {
            "tsConfig": "projects/mat-timepicker/tsconfig.lib.prod.json"
          },
          "development": {
            "tsConfig": "projects/mat-timepicker/tsconfig.lib.json"
          }
        },
        "defaultConfiguration": "production"
      },
      "test": {
        "builder": "@angular-devkit/build-angular:karma",
        "options": {
          "main": "projects/mat-timepicker/src/test.ts",
          "tsConfig": "projects/mat-timepicker/tsconfig.spec.json",
          "karmaConfig": "projects/mat-timepicker/karma.conf.js"
        }
      }
    }
  }
}
}

Regarding styles
The issue with importing @use "projects/mat-timepicker" as mat-timepicker; can be resolved by adding additional configuration to angular.json:
"stylePreprocessorOptions": {
   "includePaths": [""]
},

I've already added it to the angular.json code above. Pls tell me if it works for you.

I've solved it. I was thinking about these warnings
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>
Because I felt something wrong here and I was right. has unmet peer dependency means I have to install these dependencies manually by myself. I reckon we so used to not doing it that I didn't expect that.
Installation page says nothing about it 😄 Probably it would be nice to bump versions in this case or use >=
Thank you for your work and quickly responses. I'm really appreciated it 👍

Well, all of these packages are peerDependencies of NgDoc, I saw that you are using yarn but I'm not sure how it works with it, but it works fine with npm. Anyways if the problem is solved then I'll close the issue :)

You are right. I did an experiment. I created 2 new projects (with npm and yarn) with the latest angular version. Everything works good with npm unlike yarn. It happens because npm@7 or more installs all peer dependencies automatically. Yarn team disagree with that approach and won't implement it (https://github.com/yarnpkg/berry/issues/3710). Another issue https://github.com/yarnpkg/berry/issues/5421
After some research I found a few solutions for that:

install all peer dependencies manually
The easiest solution. But if you use the same libraries you have to keep compatible versions.

use yarnrc.yml file
This works for yarn v4. Put the following code to yarnrc.yml

packageExtensions:
  "@ng-doc/app@*":
    dependencies:
      "@ng-web-apis/common": "*"
      "di-controls": "*"
  "@ng-doc/ui-kit@*":
    dependencies:
      "@ngneat/until-destroy": "*"
      "@tinkoff/ng-polymorpheus": "4.0.11" // this important because a newer version have another types
      "di-controls": "*"

@skoropadas don't you think to put packages into dependencies. First of all it will help people who use yarn, like me 😄 There is a technical explanation. Usually peer dependencies include package which you might not use in the project but you need it (hi babel) or their usage is not obvious. As I see ng-doc uses all these packages directly. So, it depends on them.


On demand testing for medic-bot

Two parts to this:

Getting the medic-bot plugins to be fired from the command line, on-demand, without depending on the schedule.
Getting that integrated with an outbound slack integration.

Closing. Stale issue.


🚀 [REQUEST] - Refactor MinhashLSH Dedup

Feature request
enhance minhashlsh dedup code with GraphFrame, add utils
reference - text-dedup
Context

In the current code of minhashdedup, the ConnectedComponent process is implemented using raw Python, but GraphFrames supports this functionality. It seems necessary to switch to this.
The results of minhashdedup can vary depending on how tokenization is performed, so it would be beneficial to accept a DataFrame of already tokenized data as List[str].
It would be advisable to fix the return of the SHA-1 hash as a long type (8 bytes).
It seems beneficial to optionally save documents that are removed due to duplication, allowing one to visually verify the degree of duplication.
In the optimal param function, fixing the false positive rate (FP) at
0.05 and the false negative rate (FN) at 0.95 seems advisable. Other libraries configure the number of bands and rows per band such that the probability p = (1-s^n)^b is approximately 0.9 ~ 0.95. (very low FP)
referenece

remove 5
It seems that the optimal param function is working well. From visual inspection, if I lower the false positives extremely, it also removes too many other things.


local html and baseUrl support

Description
This is an enhancement of the current implementation of flutter webview. This addresses the issue of loading static html in webview, alongwith baseUrl support. This works in both ios and android.
Related Issues
Earlier we used to do it through initialUrl, by converting it to base64 string and so on. React native has a proper support for static html and baseUrl.(https://github.com/fluttercommunity/flutter_webview_plugin/issues/23)
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] No, this is not a breaking change.

@googlebot I signed it!
On Sat, May 2, 2020 at 6:20 PM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fflutter%2Fplugins%2Fpull%2F2730
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/plugins/pull/2730#issuecomment-622948730, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGEY5CDQFCB4PC4BOCV2WR3RPQJH3ANCNFSM4MXVNM2Q
.

--
Thanks & Regards
Akshay Pauranik<EMAIL_ADDRESS>*uCertify *

This doesn't seems to be an issue of the code. I have futher investigated and found that there is some issue with the test setAndGetScrollPosition testcase. It produces random results and hence fails, this may be due to slow loading of webview or something else. But actually my PR is not related to it at all. Please help me. Below is the video of the issue.
Video


feat: add upload from url ui and merge main code before

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

We identified new issues on unchanged lines of code. Navigate to the Amazon CodeGuru Reviewer console to view the recommendations to fix them.


Skeleton code for S3 offload

Doesn't implement any of the logic for putting a ledger into an
object, but does contain code to configure a S3 client and create an
object, albeit empty.
Also adds a s3mock implementation to test against.
Master issue: #1511

@zhaijack @sijie @merlimat

retest this please


Gobblin metrics registers the base schemas instead of inferring them …

…from events.

@pcadabam can you review?

Coverage increased (+0.06%) to 46.577% when pulling 5694a62a0dfdaf902d66d523b1fb7e481bff28c4 on ibuenros:metrics-utf8-fix into 50ac294aa92d324ee18e9158ae6d63d43d99ee84 on linkedin:master.

LGTM


Debugging messages can be difficult to understand

Here are some examples  trying to save time-series data with an invalid identifier.  In some cases debugging required going into the oracle table AT_LOG_MESSAGE.   That is not practical for all users/developers.

Invalid ID attempted
API Response
Server Log
Oracle/AT_LOG_MESSAGE

Hartwell.Energy-Sched.Inst.0.1Hour.Raw-source1
status code: 404 {"message":"Not Found.","incidentIdentifier": "8589911861355292194", "details":{}}
INFO [http-nio-7000-exec-4]cwms.cda.ApiServlet.lambda$init$10<PHONE_NUMBER>355292194: Not Found.cwms-data-api-data-api-1cwms.cda.api.errors.NotFoundException: ORA-20998: ERROR: ORA-06512: at "CWMS_20.CWMS_TS", line 1999
ORA-20205: ERROR: Invalid Time Series Description: Hartwell.Energy-Sched.Inst.0.1Hour.Raw-source1 Inst/Cum parameter types cannot have non-zero duration

Hartwell.Storage.Inst.1Hour.0.Raw-source1
status code: 500 {"message":"Internal Error","incidentIdentifier": "-5846316739419111664","details":{}
ORA-20006: INVALID_PARAM_ID: "Storage" is not a valid CWMS timeseries Parameter
ORA-20006: INVALID_PARAM_ID: "Storage" is not a valid CWMS timeseries Parameter

How did you match the ServerLog to the AT_LOG_MESSAGE ?   Were those the only error messages or did they line up by time or was there another ID field that connected them?

I'm just looking at the last message in both places.  Since I'm running in my Docker environment with no other users, it should be accurate.

I believe its accurate - just curious if enough clues were there to automate what you manually did

It would be possible to automate that, but a royal pain. What's likely happening is that the database is logging a message but then a downstream query is looking for the data that would be saved and then gives a "NOT_FOUND" which is the PL/SQL error thrown when using select into.
The portion of the code that logs the AT_LOG_MESSAGE value should instead (or perhaps with a session setting we can set) raise the error immediately and shortcut further operations. I'll open a database ticket; not hard for any of us to make that change but Mike P might have some insight into doing it cleaning before we just barrel through everything.

If some automated tests were done from another language, such as python that would give a fresh, and realistic perspective for future scripting users,  and perhaps easier to automate.


libffi error

I've built the binary on Google Cloud shell and transferred the binary to my local machine but I get the following error.
 error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory

Sorry for the late reply :bow:
Please install libffi and try that again. This tool (strictly speaking used Haskell libraries) depends on libffi.
For example, if I use in Arch Linux, I install the library with
pacman -S libffi

I'm not famililar with Google Cloud Shell but if it provides apt, you can install with
apt install libffi-dev


feat: token-header override

  --token-header <TOKEN_HEADER>
      Token header to use for both edge authorization and communication with the upstream server [env: TOKEN_HEADER=] [default: Authorization]

This is useful in complex deployment scenarios where proxies are using the Authorization header.

cool!


infra: Integrate latest eco-goinfra

/cc @kononovn @klaskosk

@edcdavid There's a Github action that will automatically bump the eco-goinfra dependency every night now. Let me know if you need it before tomorrow and we can merge this then

@edcdavid There's a Github action that will automatically bump the eco-goinfra dependency every night now. Let me know if you need it before tomorrow and we can merge this then

@klaskosk tomorrow would be fine but is it going to work automatically? This PR modifies an existing interface so it will need manual input I believe

@edcdavid There's a Github action that will automatically bump the eco-goinfra dependency every night now. Let me know if you need it before tomorrow and we can merge this then

@klaskosk tomorrow would be fine but is it going to work automatically? This PR modifies an existing interface so it will need manual input I believe

Nevermind, it should merge automatically without issues. I'll rename and rebase this PR once the latest infra merges

/cc @mcornea @klaskosk @kononovn


feat: add fine grained async stack trace in Sink and Source

Do not find any sub-call of the SinkExecutor in the async stack trace, maybe we should add more information in that?

nit: May also add tracing spans as we'll switch to tracing-based instruments in the future.

cc @BugenZhao do we still need this?


add: distinction in results-db between run timestamp & data timestamp

Right now the results database only knows when a check was run - not what time period the check was run against.
Add another set of timestamps for the start & stop time the check was run against.  This is particularly important when incremental testing is being performed.
defines when process ran:

run_start_timestamp
run_stop_timestamp

defines period being checked:

if mode == 'full', then it's all data, up to the runtime, more or less

because they could have data for the future in the table
or because maybe there's no data for the past 3 weeks in the table

if mode == 'incremental', then it's the partitioning date used by the incremental checks

but there's a lot of different incremental date formats
maybe the setup should also provide a start & stop regular timestamp when it provides          incremental checks?

data_start_timestamp

data_stop_timestamp

Added in 0.1.5


Outdated cask: webarchiveplayer

Outdated cask: webarchiveplayer.
Info:

version: 1.4.1.
appcast url: https://github.com/ikreymer/webarchiveplayer/releases.atom.

Please do not run find_outdated_appcasts unless you are a maintainer.


docker: don’t run prometheus as root

Similar to https://github.com/prometheus/alertmanager/issues/39, I didn’t realize that prometheus itself was also running as root. Can we change that please to limit the attack surface?

I see that #2092 takes a stab at this. Should we run it as user prometheus or as user nobody?

Fixed in #2859


Bug: missing culture causes integertextbox crash

Hello,
Got the following error on step 3 of the onboarding on a new machine:

Really didn't do anything special.
Thanks !

A different, but similar, issue happens if I chose exit and then try to open the config from the main page:

That is weird! And I can't reproduce it.
Could you try the latest beta: https://github.com/LAB02-Research/HASS.Agent/releases/tag/b2022.2.17
If that doesn't work, what language is your OS?

I'll try the beta at home tonight, but I can already answer the question, my OS is in English (US). I do have other languages (french, japanese and korean) installed.
Also while my language is English US, my region and formats (time, numbers, ...) are all set to France. Weird, I know.
I'm French but mainly use English in my everyday life but I refuse to use their weird mm/dd/yyyy format :D

Pretty much the same setup here: EN instead of native, and without the weird date format - 100% agreed on that :p
I reproduced your config in a VM, but was unable to reproduce the bug. However, I made a test version that could help. So if the beta fails, could you please overwrite HASS.Agent.exe with this one:
https://shares.lab02-research.org/tests/33/hass.agent.zip
Thanks :)

Tried the new .exe, cannot start HASS.Agent at all anymore, even after rebooting. Should I wait for the new beta ?

Could you please install this beta:
https://github.com/LAB02-Research/HASS.Agent/releases/tag/b2022.2.17
And then copy the test exe into the installation directory, overwriting the existing one. Usually the directory is %appdata%\LAB02 Research\HASS.Agent.
Delete the config folder so you'll get the onboarding again. If it doesn't work, please check if there's anything in the logs subfolder and post it here.

Sadly, it's not better.
And the logs aren't helpful sadly:
2022-02-17 22:41:36.515 +01:00 [INF] [LOG] Coderr exception reporting disabled
2022-02-17 22:41:36.516 +01:00 [INF] [PROGRAM] Extended logging disabled
2022-02-17 22:41:36.650 +01:00 [INF] [SETTINGS] Config storage path: C:\Users\Growiel\AppData\Roaming\LAB02 Research\HASS.Agent\config
2022-02-17 22:41:36.652 +01:00 [INF] [SETTINGS] No config found, storing default settings

It's a brand new install, I do have installed .net maybe i'm missing something else ?

Alright, too bad. Let's enable extended logging. Could you please download this reg key:
https://shares.lab02-research.org/tests/33/hassagent_enable_extended_logging.zip
And doubleclick the .reg key to import. Afterwards, start HASS.Agent again and see if more info shows in the logs.

Longshot, but you could please download this zip, and again place the .exe in your HASS.Agent install folder (overwriting the current one):
https://shares.lab02-research.org/tests/33/hass.agent.zip
Then rename your config folder before launching, so you'll get the onboarding again.
If that doesn't work, and extended logging isn't giving additional info, I'll remove the control that's causing this and build it myself.
Thanks for helping :)

Hi
Sorry i wasn't home for a few days, i'll try it this evening (europe time) and let you know ! I appreciate your efforts in this.

The new .exe sadly doesn't help. Here are the extended logs though
[2022-02-22] HASS.Agent_20220222.log
!

I checked the log and using the error message, I went to everyone's favorite website: Stackoverflow.
Here's what I got: https://stackoverflow.com/questions/42554944/how-to-solve-this-exception-culture-is-not-supported
The first answer is the correct one. I had my region set as English (Europe) but my Keyboard set as English (US).
I switch my region back to English US and manually overrode all the time formats to not be totally stupid.
I know my case is fairly rare so if you don't want to waste time fixing, no problem for me, it now works.

Oh wow! Thanks for the extensive info, really helpful :)
I'm able to reproduce it now. It's the English (Europe) part that's messing things up, and looks like it's a .NET flaw which I can't circumvent without rebuilding the integer-textbox myself.
That wouldn't be too much of a problem, but I'm moving HASS.Agent to the newer .NET 6 in the coming months. So for now I'll leave it like this, and I'll add it to the documentation incase someone comes across it as well.


JRTB-0: create initial architecture of telegramBot with SpringBoot

Create initial architecture for telegramBot(JRTB - javarush telegrambot)
Acceptance criteria:

Spring Boot project started succeesfully.

Analysed, which components of Spring I will use in my project - SpringBoot, Spring Data, Flyway, PostgreSql, UniRest, Telegrambot StringBoot starter


Show and modify routing rules from the UI

Description

Adding a way to display routing rules and also modify them from the UI
Minor change to show a user icon with a gear if user is ADMIN or a regular user icon if its a regular USER on the top right corner of the UI

Additional context and related issues

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
(X) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:
*

This looks like a nice improvement, thank you! I reviewed the Java half, and will try to find someone for the typescript.
My biggest concern here is not with the code, but with allowing users to supply input that will be written to disk on the server, then executed by the jeasy rules engine. We should take a close look at jeasy and mvel to understand what security vulnerabilities we might be introducing. At minimum we should log all of the updates so that they can be audited. @wendigo and @ebyhr wdyt?

This functionality will be accessible only for users with ADMIN privileges. I also have a functionality implemented in our internal repo where we are auditing changes being made to the Clusters from the UI. I can raise a PR for that as well and will add functionality to audit routing rules as well. I was thinking of getting this reviewed first and then from comments and suggestions I will raise the Audit logs PR.

this is looking good, we're almost there. @mosabua and I discussed the need to support this for clustered deployments. We should also provide a way to disable this feature in case someone doesn't want to bother setting up a shared filesystem

So this means provide an option or a config to show/disable the Routing Rules option in the left panel of the UI right?

this is looking good, we're almost there. @mosabua and I discussed the need to support this for clustered deployments. We should also provide a way to disable this feature in case someone doesn't want to bother setting up a shared filesystem

So this means provide an option or a config to show/disable the Routing Rules option in the left panel of the UI right?

I think for now we can just say in the docs that you must provide shared storage for that feature to work and in terms of disabling it could be just a config option option .. I think over time we will need various config options for the UI anyway

@mosabua @willmostly  can you please review?

I assume that @prakhar10 and @willmostly are collaborating on this currently .. ping me if review or anything else is needed.

I need to make changes according to @ebyhr 's comments. So i will get that done by this weekend.

@ebyhr can you review now please?

@mosabua can you please review?

@ebyhr  can you take a look now?


merge to live

Docs Build status updates of commit 1bfed93:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/troubleshooting-the-office-365-management-activity-api.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Music Under The Mountain

So I was doing the quest, got close to the end and received the text attached below. Went to Cyril and nothing happened. Apparently the quest is marked as complete according to BlitzMentalist. Problem is, I got no rewards, not even a questpoint. I was 91qp before and after this quest.

This has since been fixed and should now work. If you are still concerned about this ask in #support for a refund of 1 QP and 5000$.

Closing since fixed.


GOTTY: error open terminal: unknow

When file a bug report (see below for feature requests)
Please answer these quesions for a bug report. Thanks!
What version of GoTTY are you using (gotty --version)?
gotty version unknown_version+unknown_commit (downloaded from Github)
What operating system and browser are you using?
Server on execute gotty (Ubuntu 18.04 LTS) under LXC on Proxmox
What did you do?
If possible, please provide the command you ran.
Hello everyone
I have installed and run without any type of GOTTY problem and I must admit that it really is a very successful solution to be able to see or access the console through the web.
My problem is that it works fantastic if I launch it from the console, but if I try to program it to auto-run in a cron (crontab -e) when the server restarts, the process is launched correctly, but on the page I get the error of:
error opening terminal: unknow
I am using this script:
#! / bin / bash
set -e
set .x
TERM = linux
/ usr / local / go_projects / bin / gotty --term xterm -c "user: password" dnstop -4 -6 -Q -R -l 3 eth0 &
Thank you
What did you expect to see?
Is there a way to run it automatically when restarting the server?
What did you see instead?
If possible, please provide the output of the command and your browser's console output.
error opening terminal: unknow
When file a new feature proposal
Please provide an actual usecase that requires your new feature.

maybe you should use systemd to control it

Hey @jacrespo64  did you find the solution for this? I am having the same problem when trying to start gotty from cron at startup!

same problem here!
I'm trying to run raspi-config using gotty, from a php exec call.
No problem running from command line, no problem running other commands from php exec call, but no way to run raspi-config.
I allways get the error:
tput: unknown terminal "unknown"
I also tried --term xterm and hterm, without results


Add hero image for /custom-analysis

If can have alternative to colored logo.
Need to maintain color identification on page though.

Also, maybe keep colored logo at small sizes if this helps avoid readability/scaling issues for a large image.

closing as future redesign will make this redundant


chore: remove jest types from typescript config

Jest was removed in https://github.com/vuepress/vuepress-next/pull/1030

Uh, thanks!


Cache options

Hi,
Is there a way to enable flexible caching? For example if I have a bug which affects only certain cases, I would like to use a list of the cases I want to recache, and not recache the whole dataset.
Thanks

We don't currently support this feature, and the recommended way is to re-cache all in such case (which is possibly the safest, depending on the case of course).
Feel free to:

Propose the API change, with usage examples (no actual implementation)
Create a PR with the desired change (only after 1 was discussed and agreed)

Thanks for the feature suggestion!

I think that cacher.delete(sample_ids) should do the trick. Do you agree?
It should be very easy to implement.


Remove unneeded code for messageParams (first-timers-only)

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.
How you can help
In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests, are simple readable tests.
There's a good opportunity to simplify one of our tests:
In src/Bid.test.ts when messageParams is defined we give it a value (a new MessageParams object). But that value is immediately overwritten in the beforeEach function. Change the code so that messageParams is just defined, and isn't immediately assigned a value. While we're at it, and since this is TypeScript, give it a type of MessageParams.

After making your changes, make sure the tests still pass by running npm run jest
Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

Can we hold this task for now?
It is a bad practice to use global scope in tests.
The code you are about to remove is what should remain.
The global code should be deleted.

So should i leave this task?

Closing for now. Will discuss with @srfrnk

@devkant
We had a discussion on this, and decided to go ahead with this one 👍
Are you still interested in doing it?

Can I take this?

@joseluisbsa Thank you, but these issues are created specifically for people who would like to try open source for the first time. It actually takes a lot of work to create these issues, and I would like to give a chance to someone who hasn't contributed yet to try them, and become hooked on open source like you have 😃
But please, feel free to take any of the other issues not marked as first-timers-only or better yet... if you find any additions to the codebase which you believe are worthwhile, suggest something new 👍

Hi @TalAter, I am a newbie and would love contributing to open source, can I solve this issue?


[3.13.1] Program type already present: okhttp3.EventListener$Factory

To replicate I went from okhttp 3.12.1-> 3.13.1
implementation 'com.squareup.okhttp3:okhttp:3.13.1'
on a multidex project, now when I try to build:
AGPBI: {"kind":"error","text":"Program type already present: okhttp3.EventListener$Factory","sources":[{}],"tool":"D8"}
> Task :transformDexArchiveWithDexMergerForBasicDebug FAILED
java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/0, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/1, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/2, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/3, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/4, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/5, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/6, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/7, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/8, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/9, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/10, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/11, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/12, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/13, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/14, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/15, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/16, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/17, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/18, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/19, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/20, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/21, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/22, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/23, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/24, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/25, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/26, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/27, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/28, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/29, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/30, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/31, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/32, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/33, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/34, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/35, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/36, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/37, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/38, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/39, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/40, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/41, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/42, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/43, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/44, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/45, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/46, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/47, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/48, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/49, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/50, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/51, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/52, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/53, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/54, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/55, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/56, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/57, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/58, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/59, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/60, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/61, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/62, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/63, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/64, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/65, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/66, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/67, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/68, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/69, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/70, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/71
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: okhttp3.EventListener$Factory
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:593)
	at java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
	at java.util.concurrent.ForkJoinTask.join(ForkJoinTask.java:720)
	at com.google.common.collect.ImmutableList.forEach(ImmutableList.java:406)
	at com.android.build.gradle.internal.transforms.DexMergerTransform.transform(DexMergerTransform.java:233)
	at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:239)
	at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:235)
	at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102)
	at com.android.build.gradle.internal.pipeline.TransformTask.transform(TransformTask.java:230)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
	at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:50)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:131)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:120)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:99)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
	at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
	at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
	at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
	at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
	at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
	at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
	at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)
	at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262)
	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135)
	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130)
	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200)
	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191)
	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:745)
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: okhttp3.EventListener$Factory
	at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1431)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
Program type already present: okhttp3.EventListener$Factory
	at com.android.builder.dexing.D8DexArchiveMerger.getExceptionToRethrow(D8DexArchiveMerger.java:132)
	at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:117)
	at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java:101)
	at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java:36)
	at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1424)
	... 4 more
	at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:65)
	at com.android.tools.r8.utils.ExceptionUtils.withD8CompilationHandler(ExceptionUtils.java:43)
	at com.android.tools.r8.D8.run(D8.java:90)
	at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:115)
	... 7 more
	at com.android.tools.r8.utils.Reporter.failIfPendingErrors(Reporter.java:116)
	at com.android.tools.r8.utils.Reporter.fatalError(Reporter.java:74)
	at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:59)
	... 10 more
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':transformDexArchiveWithDexMergerForBasicDebug'.
> com.android.build.api.transform.TransformException: java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/0, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/1, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/2, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/3, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/4, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/5, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/6, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/7, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/8, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/9, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/10, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/11, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/12, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/13, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/14, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/15, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/16, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/17, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/18, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/19, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/20, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/21, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/22, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/23, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/24, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/25, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/26, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/27, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/28, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/29, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/30, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/31, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/32, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/33, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/34, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/35, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/36, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/37, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/38, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/39, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/40, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/41, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/42, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/43, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/44, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/45, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/46, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/47, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/48, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/49, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/50, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/51, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/52, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/53, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/54, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/55, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/56, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/57, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/58, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/59, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/60, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/61, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/62, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/63, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/64, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/65, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/66, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/67, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/68, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/69, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/70, /Users/gubatron/workspace.frostwire/frostwire/android/build/intermediates/transforms/dexBuilder/basic/debug/71
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: okhttp3.EventListener$Factory

Not clear what action we can take here. Seems like you’ve got duplicate classes.

after applying an Android SDK platform tools update this morning the problem went away.
Thanks @swankjesse


Monitoring static pods in k8s

This is essentially a follow-up to an issue we had before, namely #1447
Long story short, the kubelet will always show static pods as status Pending. This was causing issues for the agent as seen on the ticket above, so as far as I can tell the decision was made to make the agent ignore Pending pods altogether.
However, we use static pods to run k8s master components (API server, scheduler, etc.) that we'd like to monitor with Datadog through autodiscovery annotations. Right now the annotations are completely ignored, I assume because all Pending pods are ignored.
Of course in an ideal scenario this bug would be fixed upstream so that even static pods are correctly reported as Running the kubelet's local pod list but that issue has been standing still for more than 6 months. Would you consider special-casing static pods so even if they're Pending checks will be ran against them? You can tell static pods apart from regular pods because the kubelet automatically puts a "kubernetes.io/config.source": "file" annotation on them.

Yes please! We specifically run into this issue on our kubernetes clusters provisioned with Kops. Kops launches etcd, kube-controller-manager, kube-apiserver, and kube-proxy as static pods. This means that we cant use autodiscovery for etcd or kube-proxy. I've talked to Datadog support a few times about this and the recommendation is to run "dummy pods" on the same nodes as the static pods:
      containers:
      - name: dummy
        image: k8s.gcr.io/etcd:3.2.18
        command: ["/bin/sh"]
        args:
        - -c
        - while :; do sleep 2073600; done

This way the agent will discover that etcd is running on the same node and perform the checks. It requires hardcoding the hostname and port in the check definition so that the agent doesn't try to reach the dummy pod's IP and instead connects to the real etcd.
I believe the fix on the agent side would either be here or here.
Please let me get rid of all these dummy pods!

#2970 makes the podwatcher aware of static pods, but we won't be able to enable autodiscovery on them because the pod IP is part of the status that's not updated in the pod list.
There are several ways forward:

we can add static pods in autodiscovery, but you won't be able to use %%host%% in config templates as we won't can't get the pod IP. It can still be useful if your pod has a service name/domain name you can hardcode in the URL, if it exposes a hostPort (and use hostIP:hostPort in the config template), or if everything runs with hostNetwork:true in which case you can hardcode localhost in the template
we watch the pod list from the apiserver, except it's not scalable to do it from every agent, so we'll have to do it in the cluster agent and proxy the info to agents. This would add a dependency for this feature on the cluster agent, and would also make it use a lot of RAM
we try revisiting fixing the pod list upstream

If the first solution still sounds useful we can implement that quickly, but I don't think it's very valuable.
Curious to hear your thoughts on this @andor44 @rifelpet

Just posted on https://github.com/kubernetes/kubernetes/issues/61717 if you want to track solution 3

Ha, good catch on that one.
What I can say is that in our case (so I guess in @rifelpet's too) solution 1 works as we're using static pods to run master components and kube-proxy, all of which need to be hostNetwork: true by their nature. I'd be happy with that, that already fixes our immediate problem. Though that's also side-stepping the issue a bit.
I'm also fine with option two, though for example there's also #1853, which is also trying to shift heavy-lifting to DCA. Can the DCA take all this extra load? Is it worth adding all this extra complexity for an admittedly somewhat niche use-case? 🤷♂
If you guys can push a fix upstream that'd be the bees knees 😄

Agreed, all of Kops' default static pods use host networking:

etcd
kube-proxy
kube-scheduler
kube-controller-manager

Additionally, the current workaround of using dummy pods doesn't support %%host%% since it would use the dummy pod's IP rather than the real pod's IP.
I'm fine with the hostNetwork: true requirement but obviously if we can get this fixed upstream that would be ideal.

Update: we're working on the upstream solution, 6.10 doesn't make autodiscovery work with static pods. We'll keep this issue open for tracking.

Hey,
good new everyone 🎉  the fix for the static pods update on the kublet pod list has been merged https://github.com/kubernetes/kubernetes/pull/77661 and should be shipped with kubernetes 1.15
We have opened cherry-pick PRs for kubernetes 1.12, 1.13, 1.14 but they're not merged yet 🤞
https://github.com/kubernetes/kubernetes/pull/77939
https://github.com/kubernetes/kubernetes/pull/77934
https://github.com/kubernetes/kubernetes/pull/77941
We have effectively tested this on a manually setup cluster with a modified kubelet and were able  monitor static pods with some AD annotations 👍

we are on kubernetes 1.17 + datadog 7.19.1 and this seems to not be working
the pod on the node with the static pod does not seem to be found by the datadog pod on that node
agent status shows other pods with annotations but not the static  :(


GPG Import fails for seemingly unknown reasons

Expected behaviour
The GPG should be imported
Actual behaviour
The GPG Import throws incorrect email (I've confirmed it's correct), and if I don't set the email and uses the one in the private key, it fails to sign the commits, using semantic-release.
Configuration

Repository URL (if public): https://github.com/Colonise/Config
Build URL (if public): https://github.com/Colonise/Config/actions

name: Node.js CI

on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

env:
  CI: true
  CC_TEST_REPORTER_ID: ${{ secrets.CC_TEST_REPORTER_ID }}
  COLONISE_PACKAGE_NAME: ${{ secrets.COLONISE_PACKAGE_NAME }}
  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
  GIT_AUTHOR_NAME: ${{ secrets.GIT_NAME }}
  GIT_AUTHOR_EMAIL: ${{ secrets.GIT_EMAIL }}
  GIT_COMMITTER_NAME: ${{ secrets.GIT_NAME }}
  GIT_COMMITTER_EMAIL: ${{ secrets.GIT_EMAIL }}

jobs:
  lint:
    name: Lint
    runs-on: ubuntu-latest

    steps:
    - name: Checkout Repository
      uses<EMAIL_ADDRESS>
    - name: Setup Node.js
      uses<EMAIL_ADDRESS>      with:
        node-version: 14

    - name: Install dependencies
      run: |
        # Run NPM Clean Install
        npm ci

    - name: Run Linters
      run: |
        # Run NPM lint script
        npm run lint

  build:
    name: Build
    needs: [lint]
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [12.x, 13.x, 14.x]

    steps:
    - name: Checkout Repository
      uses<EMAIL_ADDRESS>
    - name: Setup Node.js
      uses<EMAIL_ADDRESS>      with:
        node-version: ${{ matrix.node-version }}

    - name: Install dependencies
      run: |
        # Run NPM Clean Install
        npm ci

    - name: Run Build
      run: |
        # Run NPM build script
        npm run build

  test:
    name: Test
    needs: [lint, build]
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [12.x, 13.x, 14.x]

    steps:
    - name: Checkout Repository
      uses<EMAIL_ADDRESS>
    - name: Setup Node.js with ${{ matrix.node-version }}
      uses<EMAIL_ADDRESS>      with:
        node-version: ${{ matrix.node-version }}

    - name: Install dependencies
      run: |
        # Run NPM Clean Install
        npm ci

    - name: Run Unit Tests
      run: |
        # Run NPM test script
        npm run test

  coverage:
    name: Test Coverage
    needs: [lint, build, test]
    runs-on: ubuntu-latest

    steps:
    - name: Checkout Repository
      uses<EMAIL_ADDRESS>
    - name: Setup Node.js
      uses<EMAIL_ADDRESS>      with:
        node-version: 14

    - name: Install dependencies
      run: |
        # Run NPM Clean Install
        npm ci

    - name: Run Test Coverage and Code Climate
      uses<EMAIL_ADDRESS>      with:
        coverageCommand: npm run coverage
        debug: true

  release:
    name: Release
    needs: [lint, build, test]
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses<EMAIL_ADDRESS>
      - name: Setup Node.js
        uses<EMAIL_ADDRESS>        with:
          node-version: 14

      - name: Install dependencies
        run: npm ci

      - name: Run Build
        run: npm run distribute

      - name: Zip Build
        run: zip -r build.zip ./distribute/

      - name: Import GPG key
        uses<EMAIL_ADDRESS>        with:
          gpg-private-key: ${{ secrets.GPG_PRIVATE_KEY }}
          passphrase: ${{ secrets.GPG_PASSPHRASE }}
          git-committer-name: ${{ secrets.GIT_NAME }}
          git-committer-email: ${{ secrets.GIT_EMAIL }}
          git-user-signingkey: true
          git-commit-gpgsign: true
          git-tag-gpgsign: true
          git-push-gpgsign: true

      - name: Run Semantic Release
        run: npx semantic-release

Logs
logs_180.zip

I've solved the GPG problems (incorrect passphrase, silly me), but the email mismatch still baffles me.

@pathurs

but the email mismatch still baffles me.

Looks like email matches, otherwise the action would failed.

@crazy-max Sorry for the confusion, I had been committing a few times to try and resolve the issue.
You can see in this run it has the git-committer stuff set, but it then complains about the mismatch. You can also see that my email is correct, since github is removing the email from the logs.

@pathurs Did you ever find a solution? I am getting

Error: Committer email does not match GPG key user address

But this was all working fine on v2. I know the email has to be correct. Here is the diff of my upgrade

@razor-x No, I just ended up trusting the automatically retrieved email. I assume there must me a a bug.
@crazy-max

@razor-x @pathurs I will take a look thanks for your feedback

I also encountered this issue and found the problem. PR fix incoming 🚀
Verified working in my pipelines using uses<EMAIL_ADDRESS>instead of uses: crazy-max/ghaction-import-gpg@v3


rbw: 0.5.0 -> 0.5.2

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107247 run on x86_64-darwin 1

1 package built:

rbw