[Bulk] Validation: validation fixes JM 6/8b

This PR fixes __ issues.

Docs Build status updates of commit 9aa6735:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/filter-element-event.md
:warning:Warning
View
Details

docs/schema/filter-element-list.md
:warning:Warning
View
Details

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-association-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-query-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filter-element-event.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filter-element-list.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-association-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-query-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 02e3c37:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/filter-element-event.md
:warning:Warning
View
Details

docs/schema/filter-element-list.md
:warning:Warning
View
Details

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-association-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-query-subscription-schema.md
:warning:Warning
View
Details

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flows-element-workflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/folder-element-contenttype.md
:warning:Warning
View
Details

docs/schema/folder-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/folderviewdefinition-element.md
:warning:Warning
View
Details

docs/schema/foreach-element-view.md
:warning:Warning
View
Details

docs/schema/form-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/formregion-element.md
:warning:Warning
View
Details

docs/schema/formregions-element.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/filter-element-event.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filter-element-list.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-association-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-query-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flows-element-workflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-contenttype.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folderviewdefinition-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/foreach-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/form-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregion-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregions-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 04480e4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/filter-element-event.md
:warning:Warning
View
Details

docs/schema/filter-element-list.md
:warning:Warning
View
Details

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-association-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-query-subscription-schema.md
:warning:Warning
View
Details

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flows-element-workflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/folder-element-contenttype.md
:warning:Warning
View
Details

docs/schema/folder-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/folderviewdefinition-element.md
:warning:Warning
View
Details

docs/schema/foreach-element-view.md
:warning:Warning
View
Details

docs/schema/form-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/formregion-element.md
:warning:Warning
View
Details

docs/schema/formregions-element.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/filter-element-event.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filter-element-list.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-association-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-query-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flows-element-workflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-contenttype.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folderviewdefinition-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/foreach-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/form-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregion-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregions-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 8d796d2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/filter-element-event.md
:warning:Warning
View
Details

docs/schema/filter-element-list.md
:warning:Warning
View
Details

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-association-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-query-subscription-schema.md
:warning:Warning
View
Details

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flows-element-workflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/folder-element-contenttype.md
:warning:Warning
View
Details

docs/schema/folder-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/folderviewdefinition-element.md
:warning:Warning
View
Details

docs/schema/foreach-element-view.md
:warning:Warning
View
Details

docs/schema/form-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/formregion-element.md
:warning:Warning
View
Details

docs/schema/formregions-element.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/filter-element-event.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filter-element-list.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-association-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 39, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

docs/schema/filtervalues-element-in-query-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flows-element-workflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-contenttype.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folderviewdefinition-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/foreach-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/form-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregion-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregions-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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 0e52212:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/filter-element-event.md
:warning:Warning
View
Details

docs/schema/filter-element-list.md
:warning:Warning
View
Details

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-association-subscription-schema.md
:warning:Warning
View
Details

docs/schema/filtervalues-element-in-query-subscription-schema.md
:warning:Warning
View
Details

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flows-element-workflowinfo-elementaction4.md
:warning:Warning
View
Details

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/folder-element-contenttype.md
:warning:Warning
View
Details

docs/schema/folder-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/folderviewdefinition-element.md
:warning:Warning
View
Details

docs/schema/foreach-element-view.md
:warning:Warning
View
Details

docs/schema/form-element-deploymentmanifest.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspview.md
:warning:Warning
View
Details

docs/schema/formats-element-deploymentmanifestspwebpart.md
:warning:Warning
View
Details

docs/schema/formregion-element.md
:warning:Warning
View
Details

docs/schema/formregions-element.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/filter-element-event.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filter-element-list.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalue-element-in-filtervalues-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-association-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/filtervalues-element-in-query-subscription-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flow-element-flows-elementworkflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flows-element-workflowinfo-elementaction4.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/flyoutanchor-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-contenttype.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folder-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/folderviewdefinition-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/foreach-element-view.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/form-element-deploymentmanifest.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspview.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formats-element-deploymentmanifestspwebpart.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregion-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formregions-element.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/formsauthcredentials-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

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


Rename Update method to ProcessBundle

This generic name was bugging me

This generic name has been bothering me for a while as well. Great to see it gets changed!
/lgtm
/approve


Mount persistent is creating a directory instead of a file

Hi, I'm using linux and azk for a Laravel project.
In my Azkfile.js I used the persistent mount to save the composer.lock file. This file not exists until the system provision, and inspecting the azk persistent folder, the composer.lock was created as a folder.
This make the system doesn't start after a restart.
I'm using azk 0.16.2 and ubuntu 14.04.

Currently, there's no available way to inform to persistent mount if the target object is either a file or a directory.
In order to do this, I suggest the following solutions:

Add to persistent mount an option:
e.g.:

mounts: {
  '/azk/#{manifest.dir}/composer.lock': persistent('composer.lock', { file: true }),
},

Create a new kind of mount (same result as the above):
e.g.:

mounts: {
  '/azk/#{manifest.dir}/composer.lock': file('composer.lock'),
},


Allow for custom layouts

Hi. LOVE the plugin so far. Any chance you could allow for customised layouts? Using this in frameworks and existing grid structures could be much easier (and much more elegant) with other layout options (other than a simple list). The ability to create a custom template as a variable would be awesome. This has been done well on Instafeed.js, for example.

I hesitate to add a templating system, only because I want to keep this as lightweight as possible, but I do really like the concept. If I have some time, I may try out some kind of solution. Thanks for the suggestion!

Hi @michael-lynch. Totally know what you mean. The other day I was thinking about this and thought of a slightly lateral option. You could potentially target the first child of the div/list for repetition, that you are targeting in the JS. That way you would be allowing for any kind of (2 level) structure, which should cover list, flex and basic column structures.
Anyway... just an idea.

Eg:
`

$('.instagram-lite').instagramLite({
});`

Hello I have a simple solution to this problem
edit file instagramLite.js line 83
item = '

';
Inserted Bootstrap grid but you can insert your own grid and found perfect.
Hope this can help you! @Cam

@Yako75 good call! Simple enough for me :) Thanks!


Add selection option -sftp, -scp for pscp by sessions.

When the pscp to connect to dropbear (ssh server) we have the error:
"/usr/libexec/sftp-server: not found" This is correct answer because dropbear is not support sftp. For some reason pscp does not failback to scp protocol according documentation. pscp is working only adding option -scp.
Is it possible to add selection of scp and sftp?

Yes, it would be nice !


[rebase] Continuous Release 1.9.0

See this and this SO posts. Currently I don't have any plans why this is the case :(
Rebasing works (see commits below) but assigns new commit ids and updates the timestamps.

Closed in favor of #561


babble.tell does not generate a Block for decisions outside of evejs

It took me quite a while to figure this out. It seems only possible to use a babble.then on an agent.decision, when you require the babble package from within evejs.
I guess somehow the connection is handled inside of babble.
var babble = require('./../node_modules/evejs/node_modules/babble');
I was about to make a pull request to remove the babble package from the package.json, but I am not sure, if it is the best approach, since then some tests might not work.
Btw: That was the error log:

TypeError: Block expected as choice
at Decision.addChoice (c:\Thomas\Projects\eve\eve-agents\node_modules\evejs\node_modules\babble\lib\block\Decision.js:136:11)
at c:\Thomas\Projects\eve\eve-agents\node_modules\evejs\node_modules\babble\lib\block\Decision.js:84:10
at Array.forEach (native)

Thanks for reporting, I'm not yet sure what's going on here. How can I reproduce your issue?

I've released a new version of babble and evejs, which probably adresses the cause of your issue


Total connection loss

Hi,
Used this integration very good for long time. I guess since the last update to 2023.8 i cannot connect anymore.
Log saying:
`Logger: custom_components.senec.config_flow
Source: custom_components/senec/config_flow.py:63
Integration: senec (documentation, issues)
First occurred: 13:03:31 (4 occurrences)
Last logged: 13:04:33
Could not connect to Senec device at <IP_ADDRESS>, check host ip address`
This log is after a complete reinstall of the hacs integration.
What I've done so far:

deleting config of my senec through UI
reconfiger over add integration with "connection faild" as a result
rebooted the main router
perfectly reachable over web browser with that given IP adress.

what you missed to do is to search for similar issues ;-) - please see #47

what you missed to do is to search for similar issues ;-) - please see #47
Duplicate of #47

Search a couple of them.
Should it such major change isn't part of a in HACS available updates or even in the beta channel, shouldn't it? If i understand senec correct every battery received this update.
Problem solved with #47


Can't import component's exported types in a test

Version
5.0.0-rc.1
Reproduction link
github.com
Environment info
Environment Info:

  System:
    OS: Linux 5.10 NixOS 21.11 (Porcupine) 21.11 (Porcupine)
    CPU: (4) x64 Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
  Binaries:
    Node: 16.3.0 - /nix/store/dpn8hvlq7v703kz3x3npx6522x89kb57-nodejs-16.3.0/bin/node
    Yarn: Not Found
    npm: 7.18.1 - /nix/store/gjb90hapc9qz532c52gslv6p98nkhwj8-node_npm-7.18.1/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 93.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.0-rc.1
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.0-rc.1
    @vue/cli-plugin-babel: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-eslint: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-router:  5.0.0-rc.1
    @vue/cli-plugin-typescript: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-unit-jest: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-vuex:  5.0.0-rc.1
    @vue/cli-service: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-shared-utils:  5.0.0-rc.1
    @vue/compiler-core:  3.2.26
    @vue/compiler-dom:  3.2.26
    @vue/compiler-sfc:  3.2.26
    @vue/compiler-ssr:  3.2.26
    @vue/component-compiler-utils:  3.3.0
    @vue/eslint-config-typescript: ^9.1.0 => 9.1.0
    @vue/reactivity:  3.2.26
    @vue/reactivity-transform:  3.2.26
    @vue/runtime-core:  3.2.26
    @vue/runtime-dom:  3.2.26
    @vue/server-renderer:  3.2.26
    @vue/shared:  3.2.26
    @vue/test-utils: ^2.0.0-0 => 2.0.0-rc.18
    @vue/vue3-jest: ^27.0.0-alpha.1 => 27.0.0-alpha.4
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^8.0.3 => 8.2.0
    jest-serializer-vue:  2.0.2
    typescript: ~4.1.5 => 4.1.6
    vue: ^3.2.13 => 3.2.26
    vue-eslint-parser:  8.0.1
    vue-hot-reload-api:  2.3.4
    vue-loader:  16.8.3 (15.9.8)
    vue-style-loader:  4.1.3
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 5.0.0-rc.1

Steps to reproduce
Write a component that exports a type
<template>
<slot></slot>
</template>

<script setup lang="ts">

export interface TestProps {
  input: string;
}

const props = defineProps<TestProps>();

</script>

Then try to import it in a test
import { mount } from "@vue/test-utils";
import TestComponent, { TestProps } from "./TestComponent.vue";

describe("TestComponent.vue", () => {
  test("should compile", () => {
    const wrapper = mount(TestComponent, {
      props: { input: "test" },
    })
  })
});

See how it fails to compile with the following error:
    tests/unit/TestComponent.spec.ts:2:25 - error TS2614: Module '"*.vue"' has no exported member 'TestProps'. Did you mean to use 'import TestProps from "*.vue"' instead?

    2 import TestComponent, { TestProps } from "./TestComponent.vue";

What is expected?
The code compiles
What is actually happening?
It fails with
    tests/unit/TestComponent.spec.ts:2:25 - error TS2614: Module '"*.vue"' has no exported member 'TestProps'. Did you mean to use 'import TestProps from "*.vue"' instead?

    2 import TestComponent, { TestProps } from "./TestComponent.vue";

Note that these types of exports and imports work fine when running npm run serve

interface should be written in a separate .ts file  and then import *.ts
// ./types/index.ts
export interface TestProps {
  input: string;
}

<template></template>

<script setup lang="ts">
import { TestProps } from './types'

const props = defineProps<TestProps>();

</script>

Then import them in a test
import { mount } from "@vue/test-utils";
import TestComponent from "./TestComponent.vue";
import { TestProps } from './types'

describe("TestComponent.vue", () => {
  test("should compile", () => {
    const wrapper = mount(TestComponent, {
      props: { input: "test" },
    })
  })
});

Thanks for your answer. I tried this and got
    [@vue/compiler-sfc] type argument passed to defineProps() must be a literal type, or a reference to an interface or literal type.

Are you sure this is possible? I though this open issue prevented it. I've uploaded a branch external_props to my MCVE with your suggested changes and I'd be really grateful if you did a PR with whatever changes necessary to make it work


cast send fails to parse nested 2d struct arrays

Component
Cast
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (6d94a10 2022-11-04T00:17:05.450788Z)
What command(s) is the bug in?
cast send
Operating System
macOS (Apple Silicon)
Describe the bug
function signature: create(TempStruct memory temp) external;
struct StructA {
     uint16 cards;
     uint256 amount;
}
struct TempStruct {
   uint256 [] b;
   uint256 [][] c;
   StructA [][] d;
}

cast send 0x123 create((uint256[],uint256[][],(uint16,uint256)[][])) "([],[],[])"
Fails with this error:
Error:
Failed to parse tokens
Context:

Error #0: Hex parsing error: Invalid character '[' at position 0
Error #1: Invalid character '[' at position 0

cast send 0x123 create((uint256[],uint256[][],(uint16,uint256)[][])) "('[]','[]','[]')"
trying to wrap arrays in quotes results in this error
Error:
Failed to parse tokens
Context:

Error #0: Hex parsing error: Invalid character ''' at position 0
Error #1: Invalid character ''' at position 0

@biogin you have to wrap function signature in quotes
$ cast abi-encode 'create((uint256[],uint256[][],(uint16,uint256)[][]))' "([],[],[])"
0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

closing this issue, feel free to reopen if the issue persists or ask questions in this thread

let's also add this as an example


Magikarp times out

Requesting /pokemon/129/ or /pokemon-species/129/ times out because it's a very slow call. Caused by https://github.com/phalt/pokeapi/issues/178.

Could work around by bumping up the default timeout to greater than 30s.


Godot Window always steals focus on GNOME with PaperWM

Tested versions
v4.2.1.stable.nixpkgs [b09f793f5]
System information
NixOS 23.11 - Godot v4.2.1 - GNOME 45.3 (X11) - PaperWM 45.6.0
Issue description
In the GNOME Desktop Environment with the PaperWM extension, the Godot Editor window always steals focus as soon as the user navigates to another window. This slides the view back to the Godot window, and makes it impossible to use any other window in the same workspace.
This bug was described by other users in the comments on #74378, and experienced by myself. That issue only refers to Xfce 4 and the latest comment implies that it's been fixed. But the issue with GNOME + PaperWM remains, so I have created a new issue for it here.
Steps to reproduce

Start the Godot Editor and open a project
Open another window in the same workspace
Navigate to the other window (<Super>+.)
PaperWM will immediately slide back to focus the Godot Editor

Minimal reproduction project (MRP)
Video evidence:
https://github.com/godotengine/godot/assets/19434374/76d28eb1-5d85-4406-aa86-96b91885e755

This bug was described by other users in the comments on https://github.com/godotengine/godot/issues/74378, and experienced by myself. That issue only refers to Xfce 4 and the https://github.com/godotengine/godot/issues/74378#issuecomment-1904690929 implies that it's been fixed.

These commits haven't been cherry-picked to the 4.2 branch yet (and no 4.2.2 release has been made yet either), so you need to build master from source to benefit from these fixes.

@Calinou Thank you for the quick response!
My mistake then, I misread what that comment was implying. I rebuilt from master (d335281) and I can confirm that it now works correctly in my GNOME/PaperWM setup. Thanks!


Feature/less frequent scheduled jobs

Dramatic cut back in frequency of scheduled jobs, to reduce the thrashing on stg*.
Bumped assessment cache to 2 hours.
Bumped reporting cache to 12 hours.
Eproms runs on the even hour:
:05 assessment cache update
:35 prepare communication
:55 send communication
9:00 (am & pm) reporting cache update
TrueNTH runs on the odd hour:
:05 assessment cache update
:35 prepare communication
:55 send communication
11:00 (am & pm) reporting cache update

Hello @pbugni! Thanks for submitting the PR.

In the file portal/config/config.py, following                are the PEP8 issues :

Line 138:80: E501 line too long (81 > 79 characters)

In the file portal/models/assessment_status.py, following                are the PEP8 issues :

Line 36:80: E501 line too long (80 > 79 characters)
Line 227:80: E501 line too long (80 > 79 characters)
Line 462:5: E722 do not use bare 'except'

There are no PEP8 issues in the file portal/models/reporting.py !


feat: handle cancel button on authWindow

i implemented this feature in another pr but it causes our Unit tests for login to fail, probably because i changed those 2  files, so i moved it in a separate branch/PR.

fixed


Make HMAC hashing algorythm configurable in Encrypter::encrypt()

https://github.com/laravel/framework/blob/69388c0a56cf833a205b4712507665682c63f01d/src/Illuminate/Encryption/Encrypter.php#L172

May I do it?

Maybe also support more ciphers

Actually there is no need in that for typical users, I guess.


Handle legacy contracts

Please look closely @cpacia

Coverage decreased (-0.04%) to 41.295% when pulling 182753597d7dbb599e39f39082d4a11ce1c3efc4 on brian.fixoldcontracts into 86ec0beb42755a1d94d47167a5bae16eccc67eaa on master.


CatCoding Webview tutorial broken

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.81.1 (system setup)
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:22:42.175Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

Steps to Reproduce:

Go here: https://code.visualstudio.com/api/extension-guides/webview
Follow directions to set up CatCoding webview
Open command palette to run webview

Error that appears:

I'm trying to follow the webview guide so I can add webview to my actual extension, and ran into the same error. Decided to just create a fresh extension and follow your guide. I think it's broken.

You can find the complete sample code here: https://github.com/microsoft/vscode-extension-samples/tree/main/webview-sample

You can find the complete sample code here: https://github.com/microsoft/vscode-extension-samples/tree/main/webview-sample

@mjbvz shocker, I cloned the repo and ran the extension without making a single modification, same error. But thanks for closing without confirming that the issue has been resolved or not.

My guess is that you didn't build the extension. If you did built it but it didn't run, then check for errors in the dev tools as well

My guess is that you didn't build the extension. If you did built it but it didn't run, then check for errors in the dev tools as well

https://github.com/microsoft/vscode-webview-ui-toolkit/blob/main/docs/getting-started.md#test-that-everything-works
I followed these instructions (listed in your docs) to test it and it's not working. Do you have some additional configurations in your VS Code not listed in the docs? Is that why it's working for you?


Setup CI (Devcontainer Flavor)

This PR enables Continuous Integration for Swifty-LLVM. It uses two distinct approaches:

Build Linux using the .devcontainer configuration
Build macOS using standard GitHub actions tasks

This fragmentation was chosen for the following benefits:

We now have a single configuration for Linux (defined in .devcontainer/Dockerfile), which models the ideal setup instructions for Linux users. Debugging Linux CI is now as simple as running a devcontainer in VSCode.
If we're willing to host our devcontainer image (say, on ghcr.io), the environment setup (dominated by downloading LLVM) will be nearly instantaneous.

I think that's a great setup. We can probably move forward with it. I guess we'll have to do the same for val-lang/val, right?


JsonParser ignores custom profiles resulting in validation issues

In version 3.1.0 the parse method in org.hl7.fhir.dstu3.elementmodel.JsonParser retrieves the structure definition for the resource being parsed via the getDefinition method (line 102).

This method looks for base definitions first, which means the custom profiles we have implemented to modify existing resources are never retrieved.

This manifests itself in the validateResource method of the class org.hl7.fhir.dstu3.validation.InstanceValidator on line 3411 where the structure definition is retrieved from an Element object created by calling the parse method in JsonParser.

The consequence of this is validation is occurring against base structure definitions rather than the custom profiles created.

I think of this as a feature, not an issue - it's enforcing the FHIR rules
On Tue, Mar 20, 2018 at 9:49 PM, sgtsaltandpepper<EMAIL_ADDRESS>wrote:

In version 3.1.0 the parse method in
org.hl7.fhir.dstu3.elementmodel.JsonParser retrieves the structure
definition for the resource being parsed via the getDefinition method
(line 102).
[image: 1]
https://user-images.githubusercontent.com/37578788/37650212-2f1effca-2c2c-11e8-8d33-7b8f465b2a5a.png
This method looks for base definitions first, which means the custom
profiles we have implemented to modify existing resources are never
retrieved.
[image: 2]
https://user-images.githubusercontent.com/37578788/37650218-342a5cb2-2c2c-11e8-8f36-c6c1fb794689.png
This manifests itself in the validateResource method of the class
org.hl7.fhir.dstu3.validation.InstanceValidator on line 3411 where the
structure definition is retrieved from an Element object created by calling
the parse method in JsonParser.
[image: 3]
https://user-images.githubusercontent.com/37578788/37650229-3d787f9c-2c2c-11e8-8214-45c274e1ec7e.png
The consequence of this is validation is occurring against base structure
definitions rather than the custom profiles created.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jamesagnew/hapi-fhir/issues/893, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFllFSa6AOEWgutdV06SnDheq2w0g2g3ks5tgN61gaJpZM4Sxq4h
.

--
http://www.healthintersections.com.au /<EMAIL_ADDRESS>/ +61 411 867 065

Maybe we have gone about implementing this in the wrong way, but I am not convinced this is a feature.
We have attempted to implement validation using our custom profiles/structure definitions as described in the HAPI documentation (http://hapifhir.io/doc_validation.html#Supplying_your_own_StructureDefinitions) yet it seems as if HAPI only ever loads the default structure definitions and ignores our custom ones. The only difference between the documentation and our implementation is that we are using a RequestValidatingInterceptor rather than obtaining a FhirValidator instance via the ctx.newValidator() method call. This is the jist of what we have done:

The validate method in the FhirInstanceValidator class is eventually called and when debugging through the code it eventually reaches the code I have described above. This results in the default structure definition is being loaded by the JsonParser and so validation does not occur against our custom profiles.

After further investigation it seems as our custom profiles are indeed being loaded, I should have taken my debugging a bit further. Still having some issues with validation where we can define any of our custom extensions in a resource where our custom profile restricts the type of extension that can be used. Perhaps an issue with the profile?

Closing as not an issue.


[idea] Support command line params in Wren

Dome could provide some API to access command line params.
So games can change their behaviours depending on these params.
Some quick draft

import "dome" for Args
class Game {
    static init() {
           Args.dome // A Map that stores the argv with DOME specific params (like --debug)
          Args.app // A Map that stores the argv with all the other Not standard DOME params
         Args.all // Args.dome + Args.app params
    }
}

In general, the order of arguments is significant in command line tools, so
an array-style of access may be better.
On Mon, 28 Sep 2020, 17:09 Camilo<EMAIL_ADDRESS>wrote:

Dome could provide some API to access command line params.
So games can change their behaviours depending on these params.
Some quick draft
import "dome" for Argsclass Game {
static init() {
Args.dome // A Map that stores the argv with DOME specific params (like --debug)
Args.app // A Map that stores the argv with all the other Not standard DOME params
Args.all // Args.dome + Args.app params
}}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/avivbeeri/dome/issues/87, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALBBL5XMGJXA5UVHBFZ4STSICYL5ANCNFSM4R4WIDDQ
.

One thing that I would like to know if this lib should be on its own namespaces like
import "args" for Args

or its best to add to an available module like dome.
Its clearly that this module would need access to the C backend the same as the Version class.

Args processing should be considered part of the dome.Process class, as
it's a property of the running process.
On Tue, 29 Sep 2020, 22:20 Camilo<EMAIL_ADDRESS>wrote:

One thing that I would like to know if this lib should be on its own
namespaces like
import "args" for Args
or its best to add to an available module like dome.
Its clearly that this module would need access to the C backend the same
as the Version class.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/avivbeeri/dome/issues/87#issuecomment-700997045, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALBBL4CLFLCWKNHKJVJ4FLSIJFQ5ANCNFSM4R4WIDDQ
.


Duping a Lord/Lady uses up the discount from A Noble Cause

Title.

Will fix as part of the marshaling redo.


Update sim vs hw logic to be n'sync with the main MobileCoin repo

The MobileCoin repo uses the environment variable SGX_MODE to determine whether to build the crates in simulation vs hardware mode.
The environment variable usage was chosen as it lets one set up the development environment once and then they can call cargo build to build based on the environment, instead of having to remember to pass a flag cargo build --features sgx-sim
The downside of this approach is that there isn't a way to propagate features based on the environment variable down to dependencies:
sequenceDiagram
    cargo build->>+Top Level Crate: Build crate With features
    Top Level Crate->>Top Level Crate: Resolve features
    Top Level Crate->>+Dependency Crate: Build crate With features
    Dependency Crate->>-Top Level Crate: Propagate `CARGO_DEP` values
    Top Level Crate->>Top Level Crate: Invoke build.rs
    Note over Top Level Crate: build.rs adds rustc-cfg=feature="sgx-sim"
    Top Level Crate->>-Top Level Crate: Compile with rustc

From the above diagram one can see that the depency has already been built by the time that the top level crate updates the feature it's building with based on the environment variable.
In order to work collaboratively with the MobileCoin repo this repo should be updated to:

rename feature sim to sgx-sim
Key off of the environment variable of SGX_MODE with values of HW and SW

Probably pull in functionality from conf.rs and update the MobileCoin repo to use it from this repos mc-sgx-build crate.

This isn't needed at this time for the MobileCoin repo.
The MobileCoin implements the current sim logic it needs from this repo.
This may be needed if the MobileCoin repo uses more of this repos types and behavior.


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

http://github.com/aemoncannon/ensime
https://github.com/ensime/ensime-server

HTTPS Corrected URLs

Was
Now

http://en.wikipedia.org/wiki/Indent_style#Variant:_Stroustrup
https://en.wikipedia.org/wiki/Indent_style#Variant:_Stroustrup

http://github.com/StefanE/ScalaSidekick
https://github.com/StefanE/ScalaSidekick

http://github.com/mads379/scala.tmbundle
https://github.com/mads379/scala.tmbundle

Other Corrected URLs

Was
Now

http://aemon.com/file_dump/ensime_manual.html#tth_sEc4.8
http://www.aemon.com/file_dump/ensime_manual.html#tth_sEc4.8

http://www.opensource.org/licenses/mit-license.php
http://opensource.org/licenses/mit-license.php

fixed in upstream master

sweet


some Feat entries of impossible land

REVEAL HIDDEN SELF：lack of frequency
TOWERING PRESENCE：lack of frequency
DOMINION AURA；ASURA MAGIC；JALMERI RAKSHASA MAGIC；IDOL THREAT ：not even in the system

It looks like Reveal Hidden Self and Towering Presence are correctly set at once per day and once per hour respectively.


Excluding multiple path doesn't work

Describe the bug
When I try to exclude multiple file using the settings, only the first file is excluded.
Steps to reproduce
My settings :
00. Notes/02. Programmation/Git sheet.md, 00. Notes/02. Programmation/Ref snippet.md

I think trying with two or more file break, or maybe on some condition ? (Space ?)
Expected behavior
All file are excluded
Are you using the mobile app?
No
Obsidian debug info
SYSTEM INFO:
Obsidian version: v0.15.8
Installer version: v0.14.15
Operating system: Windows 10 Education 10.0.22622
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: light
Community theme: BRAT-ceciliamay----obsidianmd-theme-primary
Snippets enabled: 32
Restricted mode: off
Plugins installed: 76
Plugins enabled: 69
1: Style Settings v0.4.10
2: Supercharged Links v0.8.0
3: Format Hotkeys v0.1.7
4: Auto Card Link v1.1.1
5: Advanced Tables v0.17.3
6: Templater v1.12.0
7: Collapse All v1.5.2
8: Banners v1.3.3
9: Clear Unused Images v1.0.6
10: Copy as HTML v1.0.5
11: Customizable Menu v2.2.0
12: Footnote Shortcut v0.0.9
13: Homepage v2.2.1
14: Hotkey Helper v0.3.11
15: Obsidian42 - BRAT v0.6.34
16: Markdown Table Editor v0.3.1
17: List Callouts v1.0.5
18: Icon Shortcodes v0.9.6
19: AidenLx's Folder Note v0.16.4
20: Folder Note Core v1.3.5
21: Link Favicons v1.7.4
22: Bartender v0.5.7
23: Metadata Menu v0.1.2
24: Dataview v0.5.41
25: Folder Focus Mode v0.9.5-0
26: CodeMirror Options v0.9.5
27: Icon Folder v1.3.31
28: Simple Embeds v1.12.0
29: Notion-Like Tables v4.2.3
30: Table Generator v1.1.1
31: Commander v0.1.0
32: Hover Editor v0.11.4
33: Smart Typography v1.0.18
34: Settings Search v1.2.0
35: Smarter Markdown Hotkeys v1.16.2
36: Wrap with shortcuts v1.1.0
37: Admonition v9.0.3
38: Hider v1.1.1
39: Github Publisher v3.14.0-5
40: Editor Syntax Highlight v0.1.3
41: DB Folder v1.8.2
42: Markdown Attributes v1.1.1
43: MetaEdit v1.7.2
44: MySnippets v1.2.1
45: Another Quick Switcher v5.4.1
46: Auto Link Title v1.2.5
47: Contextual Typography v2.2.4
48: Dictionary v2.21.1
49: Doubleshift v2.1.2
50: Image Toolkit v1.3.1
51: Kanban v1.3.11
52: LanguageTool Integration v0.3.0
53: Obsidian Link Converter v0.1.4
54: Linter v1.3.6
55: Metacopy v1.2.2
56: Paste image rename v1.5.0
57: Sortable v0.2.5
58: Force note view mode v1.1.1
59: Waypoint v1.2.0
60: AidenLx's Folder Note - folderv component v1.0.0
61: Better footnote v1.0.1
62: Natural Language Dates v0.6.1
63: Excalidraw v1.7.8
64: Local File Interface v0.1.0
65: Meta Bind Plugin v0.2.0
66: Snippet Downloader v1.4.4
67: Stack Overflow Answers v1.0.1
68: Tidy Footnotes v0.1.1
69: QuickAdd v0.5.5
RECOMMENDATIONS:
Custom theme: for cosmetic issues, please first try updating your theme to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.
Relevant log output
No response

Hi @Mara-Li. Thank you for your bug report. Currently excluded files are found by splitting by commas. It looks like you have an extra space between the comma and your second file name. Could you remove that and see if it works?

If this is the issue, I can push out an easy fix today.


It's really nice to keep up with the times, isn't it?

NOTE: A similar issue may already be submitted! Please search among the issues before creating a new one.
NOTE: Each discrete (stand-alone) request should be in its own issue.
Types of Changes
What types of change are you thinking about? Put an x in all boxes that apply

[ ] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.

If you're adding something to the list, be sure to explain why it should be added.
If you're fixing a bug or resolving a feature request, be sure to link to that issue.

Issue Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the issue. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before responding to the issue.

[ ] I have checked for other similar issues
[ ] I have explained why this change is important
[ ] I have added necessary documentation (if appropriate)

Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

? @phonefixnicole


molot-lite: use fork with bugfix

The original only had the mone version working; the stereo one just
passed the sound.
https://github.com/magnetophon/molot-lite/commit/06c055a94709f06ebc2537eb45bdfd45cd9a5127

Motivation for this change
Things done

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

[x] NixOS
[ ] 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/)
[x] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123950 at 6e8bbb93 run on x86_64-linux 1

1 package built successfully:

molot-lite

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/audio/molot-lite/default.nix:19:3:
   |
19 |   installPhase = ''
   |   ^


Update MD file on new branch 2017-12-13_23-34-02

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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


Created Brazilian Portuguese translation

Added the Brazilian translation, for this sentence is the same as the Spanish translation.

Thank you for the translation!  We'll have more to translate later today


Add config file option to set preferred language

This pull request enable users to write the following config:
[display]
language = "zh_CN"

to override the language.
Closes #251.

@cjwcommuny Do you want to continue working on this, or should we close this PR for now?


Fix CONTRIBUTING-pt_BR

What does this PR do?
Fixes CONTRIBUTING-pt_BR (comments at #6031)
For resources
Description
Fixes formatting and minor errors pointed at PR #6031.
Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

This should solve the problems pointed at #6031. As I commented in the previous PR, the symbol ¡ - known for its use in exclamations, such as ¡Error! - is not used in Brazilian Portuguese :brazil: :portugal:.
The main point was solved by #6168.
This should tick one of the items at #5762.


FIX: Fix mpl version check

This should hopefully fix CircleCI (again).

Codecov Report

Merging #4630 into master will increase coverage by <.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #4630      +/-   ##
==========================================
+ Coverage   87.68%   87.69%   +<.01%
==========================================
  Files         351      351
  Lines       66547    66554       +7
  Branches    10342    10343       +1
==========================================
+ Hits        58351    58362      +11
+ Misses       5235     5233       -2
+ Partials     2961     2959       -2

Successful with cache, rebuilding without cache. If it passes I'll merge so that hopefully master goes back to green.


Different sized cells.

I would like to contribute to the project by adding support for mixed size cells.
Originally thinking in multiples of the smalles view; as to not change the ordering or anything like that.
I am analyzing the code right now but do you have any heads up as to how to go about implementing this?
Is it in your plans to implement it (so we can work together)?
It would basically allow an item that is three columns high mixed with 1x1 cells.

The very first step would be to change the delegate method used for getting the size of cells by adding a cell index parameter. Then you'll have to find a way for the layoutStrategy to query the delegate to get the sizes for each index (via a block maybe?). And then comes the hard part: changing the entire algorithm in the layoutStrategy classes for the positioning of cells, detection of touches and the range of cells to load based on how many are visible. Furthermore, you'll also have to change the sorting code that allows sorting with a finger.
Good luck! It's a challenge.
No I dont intend on working on this as I dont think it's a feature a grid should support. It's more like a collage.

I'd also be interested in this getting in the grid view.
You could have the grid view ask the layout strategy for a frame rectangle for each cell index, rather than asking for position and assuming the size of the frame.


Customizable stage names

Description
Add short description
Changes

 add new file x.cs
 broken String in ...
...

@Joaquimmnetto you requested my review for this DRAFT PR. Its quite old. Do we still want to follow up on this?


Mobile app enhancement

Issue Description

[ ] Started on and Ends on for task are showing as nan-nan-nan on task details screen.
[ ] The link does not have an empty state.
[ ] The app takes a noticeable time to render task details data.

Expected Behavior
[Describe what should happen when this issue is resolved.]
Current Behavior
[Explain what currently happens when this issue is encountered.]
Screenshots
[If applicable, add screenshots or images that help illustrate the issue. You can use the following Markdown syntax to embed images:]
https://github.com/Real-Dev-Squad/mobile-app/assets/68867418/f445ca1f-2f7e-4c5b-b49a-8c721146da17
Environment

Operating System: [e.g., Windows, macOS, Linux]
Browser (if applicable): [e.g., Chrome, Firefox, Safari]
Version of Software/Project: [e.g., v1.0.0]

Additional Information
[Include any additional context, logs, or details that might be helpful in addressing the issue.]
Checklist

[ ] I have read and followed the project's code of conduct.
[ ] I have searched for similar issues before creating this one.
[ ] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.

Thank you for contributing to our project! We appreciate your help in improving it.
📚 See contributing instructions.

Add NA as an empty state for the link
Add empty state of DD/MM/YYYY
for dates
Remove compulsory API call for task/details/:id. Instead, use if the task is already present in the tasks array (fetched by  /task API) to render details.
Above changes will be done for only the Android app.

Removing the api calls  will not help.

Removing the api calls will not help.
It will surely save time when the user is coming from the task list screen.

Try some easy method, we don't have a loader on the task Detail screen, so why not start with that?


Saving as SVS file?

Thank you for your good work. We have achieved excellent registration results with Valis. I wanted to ask: could the registered images be saved as SVS format instead of ome.tiff? Thanks!

Hi @ciaobladoo,
So happy to hear that you're getting good results with Valis! Valis uses libvips to write the images, which unfortunately means it does not support writing SVS images. However, while the built in functions write an ome.tiff, it would be possible to write any format supported by libvips (TIFF, JPEG (JFIF), PPM/PGM/PBM/PFM, PNG, CSV, EXR, HDR (Radiance), Matlab, FITS, webp, Openslide and VIPS file formats, see the docs for more info). If one of those formats would be preferable, let me know and I could put together some example code on how to save in one of those formats. Also, if you don't mind my asking, are there any particular reasons that you'd prefer SVS (or some other format) over ome.tiff? Just wondering if there are issues with ome.tiff that I may not be aware of.
Best,
-Chandler

Hey Chandler,
Thank you for the swift response. I wanted '.svs' format because I thought some of my code for tiling WSI doesn't work for ome.tiff. But I tried today and it works. Not sure what was going on before but I no longer need help at the moment.
Cheers,
Chao


57 modify database schema

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f796197). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #62   +/-   ##
=========================================
  Coverage          ?   95.27%
=========================================
  Files             ?        6
  Lines             ?      275
  Branches          ?        0
=========================================
  Hits              ?      262
  Misses            ?       13
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f796197...f1ca42a. Read the comment docs.


Duplicated test targets in jcstress

Describe the bug
Noticed duplicated test targets in jcstress
00:18:08.402  autoGen.mk:2376: warning: overriding recipe for target 'jcstress_LongAtomicityTest_0'
00:18:08.402  autoGen.mk:1984: warning: ignoring old recipe for target 'jcstress_LongAtomicityTest_0'
00:18:08.402  autoGen.mk:2404: warning: overriding recipe for target 'jcstress_VolatileFloatAtomicityTest_0'
00:18:08.402  autoGen.mk:2012: warning: ignoring old recipe for target 'jcstress_VolatileFloatAtomicityTest_0'
00:18:08.402  autoGen.mk:2432: warning: overriding recipe for target 'jcstress_FloatAtomicityTest_0'
00:18:08.402  autoGen.mk:2040: warning: ignoring old recipe for target 'jcstress_FloatAtomicityTest_0'
00:18:08.402  autoGen.mk:2460: warning: overriding recipe for target 'jcstress_ByteAtomicityTest_0'
00:18:08.403  autoGen.mk:2068: warning: ignoring old recipe for target 'jcstress_ByteAtomicityTest_0'
00:18:08.403  autoGen.mk:2488: warning: overriding recipe for target 'jcstress_CharAtomicityTest_0'
00:18:08.403  autoGen.mk:2096: warning: ignoring old recipe for target 'jcstress_CharAtomicityTest_0'
00:18:08.403  autoGen.mk:2516: warning: overriding recipe for target 'jcstress_VolatileDoubleAtomicityTest_0'
00:18:08.403  autoGen.mk:2124: warning: ignoring old recipe for target 'jcstress_VolatileDoubleAtomicityTest_0'
00:18:08.403  autoGen.mk:2544: warning: overriding recipe for target 'jcstress_DoubleAtomicityTest_0'
00:18:08.403  autoGen.mk:2152: warning: ignoring old recipe for target 'jcstress_DoubleAtomicityTest_0'
00:18:08.403  autoGen.mk:2572: warning: overriding recipe for target 'jcstress_IntAtomicityTest_0'
00:18:08.403  autoGen.mk:2180: warning: ignoring old recipe for target 'jcstress_IntAtomicityTest_0'
00:18:08.403  autoGen.mk:2600: warning: overriding recipe for target 'jcstress_ShortAtomicityTest_0'
00:18:08.403  autoGen.mk:2208: warning: ignoring old recipe for target 'jcstress_ShortAtomicityTest_0'
00:18:08.403  autoGen.mk:2628: warning: overriding recipe for target 'jcstress_VolatileByteAtomicityTest_0'
00:18:08.403  autoGen.mk:2236: warning: ignoring old recipe for target 'jcstress_VolatileByteAtomicityTest_0'
00:18:08.403  autoGen.mk:2656: warning: overriding recipe for target 'jcstress_VolatileIntAtomicityTest_0'
00:18:08.403  autoGen.mk:2264: warning: ignoring old recipe for target 'jcstress_VolatileIntAtomicityTest_0'
00:18:08.403  autoGen.mk:2684: warning: overriding recipe for target 'jcstress_VolatileLongAtomicityTest_0'
00:18:08.403  autoGen.mk:2292: warning: ignoring old recipe for target 'jcstress_VolatileLongAtomicityTest_0'
00:18:08.403  autoGen.mk:2712: warning: overriding recipe for target 'jcstress_VolatileShortAtomicityTest_0'
00:18:08.403  autoGen.mk:2320: warning: ignoring old recipe for target 'jcstress_VolatileShortAtomicityTest_0'
00:18:08.403  autoGen.mk:2740: warning: overriding recipe for target 'jcstress_VolatileCharAtomicityTest_0'
00:18:08.403  autoGen.mk:2348: warning: ignoring old recipe for target 'jcstress_VolatileCharAtomicityTest_0'
00:18:08.403  autoGen.mk:4448: warning: overriding recipe for target 'jcstress_BoundedSingleTest_0'
00:18:08.403  autoGen.mk:4280: warning: ignoring old recipe for target 'jcstress_BoundedSingleTest_0'
00:18:08.403  autoGen.mk:4532: warning: overriding recipe for target 'jcstress_UnboundedSingleTest_0'
00:18:08.403  autoGen.mk:4308: warning: ignoring old recipe for target 'jcstress_UnboundedSingleTest_0'

https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_dev.system_x86-32_windows/6/consoleFull
We should remove the duplicate test targets in playlist
https://github.com/adoptium/aqa-tests/blob/master/system/jcstress/playlist.xml

For example, search jcstress_LongAtomicityTest in jcstress/playlist.xml, it should have 2 matches and remove one of them.
https://github.com/adoptium/aqa-tests/blob/6c74b567b07c7d776d1ea414ef8b3902961d0a3b/system/jcstress/playlist.xml#L822-L831

Hi! Can I work on this issue?

Please do @ArkaprabhaChakraborty, thanks!


Using import.meta.glob keeps relative paths in the build output

Describe the bug
I believe that this is a bug, but it could also be related to what the docs point to as only using relative paths with the glob function.
I am importing a list of png files from a directory using ../assets/image_*.png.  All of the images are found and everything works during vite and vite build && vite serve.  However, when trying to take the files from the build and use them with a different web server, they are not found because of the relative path being used still.
Reproduction
https://github.com/nrayburn-tech/asset-issue

Clone repo
npm install && npm run build && npx vite serve. See that the globbed image is being loaded with a relative path, whereas the first uses an absolute.
npm run serve to use a different web server, notice the missing image.

System Info

vite version: 2.0.0-beta.49
Operating System: macOS Big Sur
Node version: 14.13.1
Package manager (npm/yarn/pnpm) and version: 6.14.10

Asset imports expose the resolved URL as the default export of the imported module.
With glob imports, the globbed object contains a Record<relativePath, importedModule> map.

So your line 8 of App.tsx should be changed to:
images[fileName] = microdotImages[path].default;

Asset imports expose the resolved URL as the default export of the imported module.
With glob imports, the globbed object contains a Record<relativePath, importedModule> map.

So your line 8 of App.tsx should be changed to:
images[fileName] = microdotImages[path].default;


add the possibility to set the gc_grace_seconds property on the journal table

Awesome, thanks a lot!

Awesome ! Waiting for your next version !


Allow plugin to contract and invoice view

Changes to be committed:
modified:   src/netbox_contract/api/serializers.py
modified:   src/netbox_contract/templates/netbox_contract/contract.html
modified:   src/netbox_contract/templates/netbox_contract/invoice.html

Will be part of v2.0.8


docs: example lambda retry with queues

I thought it would be nice to have a retry example which uses similar logic to how sst v2 did retries for EventBus subscribers.
I have seen it asked a few times on discord and just thought it would be a nice challenge for me to try. I was able to get things working so I figured an PR to add an example might be helpful to others.
Let me know if you want me to change anything.

Awesome. Thanks the comment block, it'll get added to the docs as well.


Bump to bundletool 0.13.4+

Hey guys,
Bundletool 0.13.4 fixes a pretty important issue for us:
https://github.com/google/bundletool/releases/tag/0.13.4
Could you update this step to either use 0.13.4 or 0.14.0?
Thanks!

Fixed in #122 I guess haha

This can also be closed


have a way to mark elements as consumed

eg in some cases a property has a list price and a closing price.
The naive thing that seeks out prices anywhere will discover two prices and vomit.
It would be better if we could put very specific selectors up first, and have them blacklist a given element. Ideally we'd blacklist a selection, I guess, to handle the case where things aren't segregated by element.
We could make this a flag you can pass in a rule - optional 3rd param to indicate it should consume the element?

Fixed in https://github.com/cldellow/real-estate-prices-cc/commit/4d59bae008d81abba510fbf9baa24afda0da237a


Ruby, Rust and Swift support

Hi guys! Do you have plans about ruby, rust and swift support? This extension is so helpful, thank u!

Hi guys! Do you have plans about ruby, rust and swift support? This extension is so helpful, thank u!

Rust has been supported. Ruby and Swift will take a second


bleu score computation

Thanks for the great one-stop resource !!
bleu_score() function in bleu.py takes candidate_corpus as first argument and reference corpus as second argument. But the order is reversed in the calculate_bleu() function in 6 - Attention is All You Need.ipynb, 5 - Convolutional Sequence to Sequence Learning.ipynb and 4 - Packed Padded Sequences, Masking, Inference and BLEU.ipynb.
In general, BLEU_SCORE(prediction, reference) != BLEU_SCORE(reference, prediction)
The calculate_bleu()  function after correction is:
def calculate_bleu(data, src_field, trg_field, model, device, max_len = 50):

    trgs = []
    pred_trgs = []

    for datum in data:

        src = vars(datum)['src']
        trg = vars(datum)['trg']

        pred_trg, _ = translate_sentence(src, src_field, trg_field, model, device, max_len)

        #cut off <eos> token
        pred_trg = pred_trg[:-1]

        trgs.append([trg])
        pred_trgs.append(pred_trg)

    return bleu.bleu_score(pred_trgs, trgs)

Good catch - will correct this now.


chore(package): add homepage

to add https://ui.nuxt.com here : https://www.npmjs.com/package/@nuxt/ui
🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks 😊


EnableUnobtrusiveAjaxReplacing

hi,
how to use this with EnableUnobtrusiveAjaxReplacing?

currently that is not implement yet
maybe you can send a pull request?

hi,
i did as you suggested but it ajax capability is not working.
after reading source code of x.pagedlist, i noticed that it checkes that option object is of type PagedListRenderOptions and if so then it proceeds to apply ajaxoptions.
I had to implement it like this:
 @Html.PagedListPager(Model.List, page => Url.Action("IndexPage", new { userId = Model.UserId,fromDate = Model.FromDate,toDate= Model.ToDate, pageIndex = page - 1, pageSize = ViewBag.PageSize }),                 PagedListRenderOptions.EnableUnobtrusiveAjaxReplacing(new PagedListRenderOptions                 {                     LiElementClasses = new List<string> { "page-item" },                     PageClasses = new List<string> { "page-link" },                     UlElementClasses = new List<string> { "pagination justify-content-center" },                     DisplayLinkToPreviousPage = PagedListDisplayMode.Never,                     DisplayLinkToNextPage = PagedListDisplayMode.Never                 }, new AjaxOptions { HttpMethod = "GET", UpdateTargetId = "logContainer" }))


SignalXY-add-support-for-markers-#3602

If I understood correctly, then the solution you propose looks like this. But I'm not sure what's in Drawing.DrawMarkers should be passed pixels, but I haven't quite figured out how I can get the points I need.

Hi @Giviruk, thanks so much for opening this pull request! I have the code open right now so now that you got the ball rolling, I think I can refine this and merge it in shortly. Thanks again!

Looks fantastic! This will be in the next release 🚀
var sig = myPlot.Add.SignalXY(xs, ys);
sig.MarkerStyle.Shape = MarkerShape.FilledCircle;


Detect Manifoldjs

Is possible to detect that my site are being accessed with manifoldjs?
I want to make some modification on this case but the js injection work after the page is loaded, but I need it to be before.
There is any workaround on this?

yea, this is still a gap, because on some platforms (like windows 10) the user agent is different when it is a PWA, but most of the time it is the same.  you may be able to do some feature detection for APIs, anyone else know?

I went back and looked at the issues in the manifest spec, and found a solution for you.  the official recommendation is to add a query string parameter to the start URL on the manifest.  For example, your site is https://www.mysite.com/  and you make the start url https://www.mysite.com/?inApp=true.  This way you can do a detect for this in your URL and know you are in the app.  Should work for all platfroms and polyfills.

Hello again.
I tried this solution url/?variable=value :
It open the hosted site correctly, but after some seconds (10-15 secs) it crashes with this message(i´m on Android):
Application Error
The connection to the server was unsuccessful. (https://myurl.com.br/?manifold=1)
My site uses Angular 1.5 not sure if this can be related.
I opened the url with the browser and everything works ok.

Nvm. It is happening with any link regardless.
Yet still did´nt know whats happening since the app open and the hosted site are showed properly, just to crash some seconds later.


Add pthread_set/get schedparam functions to FreeBSD.

FreeBSD has these functions and this provides an interface to use them.
In particular, the thread-priority crate can't be built without those.

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 1d5136a6bb25090d3db6e439228ec7889f3039fd has been approved by Amanieu

:hourglass: Testing commit 1d5136a6bb25090d3db6e439228ec7889f3039fd with merge a29988a5fb3c1b050a8f30844606086ac93a7c87...

:broken_heart: Test failed - checks-actions

I am not sure I understand what this error is about. Can you help me with it, please?

I think it's just a spurious failure, let's try again.
@bors retry

:hourglass: Testing commit 1d5136a6bb25090d3db6e439228ec7889f3039fd with merge c25369946c6dd0db4052dfeec8add37c1015236d...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing c25369946c6dd0db4052dfeec8add37c1015236d to master...


Sample Github TensorFlow Issue Renamed

Please go to Stack Overflow for help and support:
http://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or a feature request.
The form below must be filled out.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Testing comments API.

Testing comments API.

Testing comments API.

Testing comments API.

Testing comments API.

Testing comments.

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Testing delete comment.

I am commenting on this issue.

Testing deleted comments with @av8ramit tagged.

Hi @destinedtobedeleted testing comment.

Delete this comment again.


🎁 1718 Use device requests API

Use the device requests API for:

execute_resource
set_resource_value

I left the now-unused fix_path parameter in to keep the same signature for backwards compatibility.

Be aware, if fixed path does what I think it does, it removes the leading / for old endpoints. However DeviceRequests requires a leading / to work.

@alexl0gan Ah, so that's a breaking change: someone could currently be passing URIs like 100/1/1 to one of these functions. So I need to check if the path starts with "/" and if not prepend it.
However, I can't make the fix_path parameter control this behaviour since that's also a breaking change.

Looks like the base64 encoding is broken in python 2. I'll try and find a version-independent way of doing it.

Fixed base64 encoding in Python 2.


Considered incorporating d3 tree into new webui

regaining interest in this.  especially considering the strong performance under 0.4.x (https://github.com/ipfs/dataviz/issues/20#issuecomment-224171063).
@dignifiedquire just a heads up, I'm getting into react, and may be interested in working on integrating this or another dataviz into webui sometime soon-ish...


Reformat LICENSE so e.g. GitHub can recognize it

This should remove this warning:

Please review.

Thanks for the review.


add parallel actor critic algorithm

There is something wrong with symbol definition and gradients calculation in A3C,  here is the parallel actor critic algorithm transplanted from Minpy#parallel_actor_critic. This implementation can get relatively good results for Pong in about 30 minutes of training.

Could you be more specific on whats wrong with the A3C implementation?

Hi @piiswrong,

A3C is actually parallel actor critic, since it uses batch learning instead of asynchronous learning.

As noeted in "Policy Gradient Theorem", in policy gradient, the loss is: , which just considers the action taken, so the policy output should be SoftmaxActivation(with advantage as out_gradient) instead of SoftmaxOutput.

I think the entropy loss in A3C is not right, please refer to parallel_actor_critic/model.py#L30

@loofahcus It's really great if we can get the A3C implementation correct! Have you tried it on other games like BreakOut? Also, I think that SoftmaxActivation with advantage as the out_grad should be the same as SoftmaxOutput with the advantage as the label. And A3C in the original paper should be asynchronous, which uses different exploring ratio for the agents.

@sxjscience Sorry, I didn't make it clear. When I said "so the policy output should be SoftmaxActivation(with advantage as out_gradient) instead of SoftmaxOutput.", I actually meant log(SoftmaxActivation), you can see here, that's why I said SoftmaxOutput is not proper.
I myself didn't try other games like BreakOut, but I refered to other A3C implementation like async-rl and quit sure the implementation is right. The shared net uses MLP instead of CNN, since Atari8080Preprocessor simplifies the observation into “binary image”, which leads to fast learning, and so it may not fit other games. Since this implementation focuses on right implementation of network structure of actor-critic, it's not a big deal.
By the way, in my opinion, the biggest difference between A3C and Parallel Actor Critic may lie in the rate of convergence, A3C may benefit from its hogwild learning schema.

I think it's a good example for parallel actor critic.

Hi, I have run this algorithm on my server(28  Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz), with the default parameter setting(num-envs = 16). It takes too much time to solve this problem, more than 10 hours.  I use the latest version of mxnet. I would like to know what cause this algorithm to be solved so slowly. Thansk.


mkcloud_reserve_pool: use arithmetic with seconds

allows to specify notification delays longer than a day
and crossing midnight

+1 (if tested)

:+1:


adds datetime folder containing DatetimeFeatures nb

@solegalli
related to main repo's issue#67
I couldn't really find great datetime datasets on UCI. This one has only one datetime variable which works for most purpose I guess but I can't really show the timezone related functionality for example (which is in the docs examples with the toy dataset though)
Let me know if it would be best to introduce similar toy examples in this notebook too or maybe find a more suitable real dataset looking into other sources. Or if there's something else important I forgot to put in here of course

Hi @dodoarg
Thank you for creating the notebook. Looks really good. I have 3 minor suggestions:
After cell 3, you mention that the transformer does not support missing data, but it does, in fact, we have an attribute to control this behavior. Could you change the wording?
In cell 8, the link to the docs (which do not exist already) is not going to be correct. I would remove it, and users can search for the class themselves. We can always add it later after the package is released.
Would you be able to showcase a bit more the attributes of the transformer? in particular the features_to_extract_ when setting the initial param to None or 'all'?
And maybe also show how the variable datetime was captured and stored automatically in variables_ when setting variables=None?
That's all I would say. Then it is pretty much ready to merge.

After cell 3, you mention that the transformer does not support missing data, but it does

!! 🤔 yea I removed that

In cell 8, the link to the docs is not going to be correct.

It was meant to be some kind of placeholder, I removed it now

the features_to_extract_ when setting the initial param to None or 'all'

The "all" option was already there, I now added the None/default case in a similar way

show how the variable datetime was captured and stored automatically in variables_ when setting variables = None

This was actually in the notebook before I decided to remove it - I thought attributes named with a trailing underscore are not meant to be accessed by the user. But that's not how it works, right?
Anyhow, I put it back in

Attributes with a preceding underscore are private. Those will not be visible to the users.
Hi @dodoarg
Attributes with a trailing underscore, by sklearn convention, contain the values that are learned during fit. In, fact, the function to check that the transformer has been fit (which we use in the tests), checks for the existence of trailing underscores added during fit.
If you have a look at the sklearn classes, you will see that all learned parameters have a trailing underscore, like coef_, feature_importance_, classes_, etc.
Thank you for the great work. I am merging this now.


Update for latest macOS

On macOS Catalina 10.15.3 you will need to change the home-brew installed conan's ~/.conan/settings.yml to add clang version "11" to be able to build.
And you will have to specify this as the version.
ERROR: Invalid setting '11' is not a valid 'settings.compiler.version' value.
You may want to reference this page in your description along with the "you may have to change these settings...."
https://docs.conan.io/en/latest/faq/troubleshooting.html#error-invalid-setting
libstdc++ is also now deprecated, so libc++ needs to be used.

Never mind, i was not able to tweet it to work , i'm giving up.


Add to onboarding reproduction logs

System Setup:
Operating System: Arch Linux, Kernel 6.8.1
Memory: 16GB
CPU: Intel i5-8350U (8) @ 3.600GHz
Python Version: 3.11.8
Java Version: 21.0.3
Maven: 3.9.6
When running the command
bin/run.sh io.anserini.index.IndexCollection \
  -collection JsonCollection \
  -input collections/msmarco-passage/collection_jsonl \
  -index indexes/msmarco-passage/lucene-index-msmarco \
  -generator DefaultLuceneDocumentGenerator \
  -threads 9 -storePositions -storeDocvectors -storeRaw

to index the documents, I had to add the flag -memory-buffer 128 as the process would get killed for what I suspect to be high memory usage.
The documentation for the onboarding path had not yet reflected the change from maven-appassembler-plugin to a custom run script. I have updated the documentation to reflect this change.
Besides this, everything worked as expected

Hi @DanielKohn1208 thanks for catching the doc fixes!