[bulk] Validations: fix duplicateH1Title issues and missing-description issues

This PR fixes 38 duplicateH1Title issues and 18 missing-description issues.

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

File
Status
Preview URL
Details

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/interface-architecture.md
:warning:Warning

Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/installing-sdn-interface.md
:bulb:Suggestion

Details

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:bulb:Suggestion

Details

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 7, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/interface-architecture.md

Line 8, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Skype for Business SDN Interface architecture' is duplicated with other articles: 'SDN/articles/interface-architecture.md(8,1), SDN/articles/skype-for-business-sdn-interface-architecture.md(11,1)'. First level headings must be unique within a docset.

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 7, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Identifier of the endpoint.' is duplicated in 'SDN/articles/id-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(7,14)', 'SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md(7,14)'.

Skype/SDN/articles/installing-sdn-interface.md

Line 7, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'You install Microsoft Skype for Business SDN Interface by running two installation packages. One is for the SDN Manager and the other is for the Dialog Listener.' is duplicated in 'SDN/articles/installing-sdn-interface.md(7,14)', 'SDN/articles/installing-skype-for-business-sdn-interface.md(7,14)'.

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md

Line 7, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'You install Microsoft Skype for Business SDN Interface by running two installation packages. One is for the SDN Manager and the other is for the Dialog Listener.' is duplicated in 'SDN/articles/installing-sdn-interface.md(7,14)', 'SDN/articles/installing-skype-for-business-sdn-interface.md(7,14)'.

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

File
Status
Preview URL
Details

Skype/SDN/articles/interface-architecture.md
:warning:Warning

Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md

Line 8, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Skype for Business SDN Interface architecture' is duplicated with other articles: 'SDN/articles/interface-architecture.md(8,1), SDN/articles/skype-for-business-sdn-interface-architecture.md(11,1)'. First level headings must be unique within a docset.

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 39025a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md
:bulb:Suggestion

Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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

Docs Build status updates of commit 6094807:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit fb92bf0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 7, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Whether the endpoint (Skype for Business client) is capable to send incall quality update messages. This flag does not indicate whether the client is configured to send incall QoE reports.' is duplicated in 'SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(7,14)', 'SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(7,14)'.

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 7, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'Whether the endpoint (Skype for Business client) is capable to send incall quality update messages. This flag does not indicate whether the client is configured to send incall QoE reports.' is duplicated in 'SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(7,14)', 'SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(7,14)'.

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

Docs Build status updates of commit 3b700ae:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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 ffe66b5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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

File
Status
Preview URL
Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-startorupdatetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-endedtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-errortype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-qualitytype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveport-element-qualityendpointtype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveport-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/reportMediaDiagnostics_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/myGroupMemberships2_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/removeContactFromAllGroups2_ref.md

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.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/groupMemberships_ref.md

Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

Skype/UCWA/group_ref.md

Line 55, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 b826ee1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-startorupdatetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-errortype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-qualitytype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-endedtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/pai-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/pai-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/group_ref.md

Line 55, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 67, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 107, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 143, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

Skype/UCWA/acceptWithAnswer_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 35, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/myGroupMemberships2_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/reportMediaDiagnostics_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 b826ee1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/SDN/articles/port-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:warning:Warning

Details

Skype/SDN/articles/port-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/acceptWithAnswer_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 35, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/myGroupMemberships2_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/ErrorSubcode_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/reportMediaDiagnostics_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 4d30ced:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/SDN/articles/port-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-qualitytype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-errortype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/acceptWithAnswer_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 35, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/groupMemberships_ref.md

Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

Skype/UCWA/message_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/group_ref.md

Line 55, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 67, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 107, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 4d30ced:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveport-element-qualityendpointtype-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveport-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveport-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-endedtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-startorupdatetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-errortype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/properties-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/acceptWithAnswer_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 35, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/ErrorSubcode_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/reportMediaDiagnostics_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/removeContactFromAllGroups2_ref.md

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.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/myGroupMemberships2_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 4d30ced:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/UCWA/mediaPolicies_ref.md
:warning:Warning

Details

Skype/UCWA/startVideo_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/docs/TenantAdminConsent.md
:warning:Warning

Details

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/reportMediaDiagnostics_ref.md
:warning:Warning

Details

Skype/AppSDK/Feedback.md
:warning:Warning

Details

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md
:warning:Warning

Details

Skype/UCWA/group_ref.md
:warning:Warning

Details

Skype/UCWA/groupMemberships_ref.md
:warning:Warning

Details

Skype/UCWA/acceptWithAnswer_ref.md
:warning:Warning

Details

Skype/UCWA/ErrorSubcode_ref.md
:warning:Warning

Details

Skype/UCWA/myGroupMemberships2_ref.md
:warning:Warning

Details

Skype/UCWA/message_ref.md
:warning:Warning

Details

Skype/Trusted-Application-API/samples/QuickStartSamples/README.md
:warning:Warning

Details

Skype/UCWA/removeContactFromAllGroups2_ref.md
:warning:Warning

Details

Skype/WebSDK/lib/webcomponentsjs/CONTRIBUTING.md
:warning:Warning

Details

Skype/WebSDK/docs/includes/P2PChromeWarning.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveip-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveip-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveip-element-qualityendpointtype-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/reflexiveip-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/port-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

Skype/SDN/articles/cpuinsufficienteventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 80: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/mediaPolicies_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCWA/startVideo_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/Trusted-Application-API/docs/TenantAdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4, Column 1: [Warning: yaml-header-syntax-error] While parsing a block mapping, did not find expected key.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/reportMediaDiagnostics_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/AppSDK/Feedback.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/ucma-2-0-core-applications-coexistence-migration-and-upgrade-scenarios.md

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

Skype/UCWA/group_ref.md

Line 55, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 67, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 107, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 143, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

Skype/UCWA/groupMemberships_ref.md

Line 46, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

Skype/UCWA/acceptWithAnswer_ref.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 35, Column 1: [Warning: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
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 4d30ced:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md
:white_check_mark:Succeeded

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

@lindalu-MSFT
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!
Sorry for all the problem builds above with wrong files etc. Build problems resolved now.

Docs Build status updates of commit 2fe53b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/id-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-errorendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-inviteendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/id-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-byeendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-endpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-errorendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallenabled-element-inviteendpointtype-complextype-skype-sdn-2-2-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/incallquality-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/inside-element-qualityendpointtype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/installing-skype-for-business-sdn-interface.md
:white_check_mark:Succeeded

Skype/SDN/articles/interface-architecture.md
:white_check_mark:Succeeded

Skype/SDN/articles/invite-element-messagetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:white_check_mark:Succeeded

Skype/SDN/articles/skype-for-business-sdn-interface-architecture.md
:white_check_mark:Succeeded

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


"ipelet set operations" needs exception handling

Many errors occur in spline operation.
We have to handle them.
Also, there is no readme.md for "ipelet set operations"

Error handling will be added at 2022.01.


Update de.json

had to fix a conflicting merge, therefore the file might be broken on my end (or it at least carries unnecessary data)

Thanks!
Everything seemed to merge fine, just 6 modified lines.


Rate limit

I am using your function to translate an .srt file (about 100 lines of text) with the free OpenAI API, and I often hit the limit right from the first translation. I wonder if there's any way to address this.

The free tier trial API is having a very restrictive rate limiting of 3 requests per minute and 200 requests per day  https://platform.openai.com/docs/guides/rate-limits/what-are-the-rate-limits-for-our-api
Set OPENAI_API_RPM to 3 in your .env file:
OPENAI_API_RPM=3

If you still hit rate limit, means you have exhausting request per day quota, wait for next day or upgrade your plan.

Thank you for your response.
I don't think this is a silly idea at all. I realize there is a more efficient way to use the rate limit.
The gpt-3.5-turbo model can send a maximum of 4097 tokens per request. My .srt file is calculated to be around 10,000 tokens. So, it should be possible to process the .srt file with just 2 requests.
is it work ?

You mentioned that your .srt file is around 100 text line count or timestamp entries? This application is already set to send 100 timestamp entries by default which should likely complete the run within 2 queries, unless the batch size is reduced due to mismatched output quantity (this cannot be easily fixed), though batch size can be increased to maybe 150 by setting:
--batch-sizes [150]
You can also try turn off moderator and line quantity matching:
--no-use-moderator --no-line-matching

Thank you for your response.
I don't think this is a silly idea at all. I realize there is a more efficient way to use the rate limit.
The gpt-3.5-turbo model can send a maximum of 4097 tokens per request. My .srt file is calculated to be around 10,000 tokens. So, it should be possible to process the .srt file with just 2 requests. is it work ?

Also to correct that,

The gpt-3.5-turbo model can send a maximum of 4097 tokens per request.

4097 tokens consists of both input and output tokens, not just input
https://help.openai.com/en/articles/4936856-what-are-tokens-and-how-to-count-them

Depending on the model used, requests can use up to 4097 tokens shared between prompt and completion. If your prompt is 4000 tokens, your completion can be 97 tokens at most.


How do you add a custom validator and error message?

Package version eg. v9, v10:
v10
It seems adding a custom validation rule is something that should be pretty common. I've been unable to find a complete example of adding a validation rule and the matching error message. Could someone explain how this is to be done?
The first step seems to be to define a custom function
https://github.com/go-playground/validator/blob/d6b17fd90bd4dd9d16a594c3035ceadc3de0193a/doc.go#L1273-L1282
Then it looks like you might have to add this non-intuitive block of code to mutate the translation handling. Is this correct?
https://github.com/go-playground/validator/blob/f6584a41c8acc5dfc0b62f7962811f5231c11530/_examples/translations/main.go#L105-L111
Related

https://github.com/go-playground/validator/issues/669

Yes, this is how it's done. For a more clarifying example , refer to this blog post https://medium.com/@apzuk3/input-validation-in-golang-bc24cdec1835

Yes, this is how it's done. For a more clarifying example , refer to this blog post https://medium.com/@apzuk3/input-validation-in-golang-bc24cdec1835


Json Variable Substitution and Arrays

In my appSettings.json file I have a section named "ItemList" which is in source control as "ItemList": [ ]
In my build definition I'm attempting to add two values to the array "One" and "Two" using variable substitution.  I've declared two variables "ItemList.0" with a value of "One" and "ItemList.1" with a value of "Two" but the values are not being added to the appSettings.json during the transformation process.
What is the supported method, if any, of setting the values for an empty array during the File Transformation and Variable Substitution phase of an Azure App Service Deploy step?

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

ID: 315ff823-9992-9f9b-62a1-42ce622ed41c
Version Independent ID: 72ec3ffc-1dc9-b2dc-e3d4-4f14deae3720
Content: File transforms and variable substitution
Content Source: docs/pipelines/tasks/transforms-variable-substitution.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

I am also quite interested in previous question: can we add items to an array (not only replace existing items)?

We are talking about adding a new value, not replacing an already existant one.
In following  json I would like to add a third user
{
“Users”: [“user1” , ”user2”]
}
I can replace user1 by defining a variable Users.0 and giving a value. However I was expecting to add a new user to array defining variable Users.2
Do you plan to support this scenario?

The code looks for the JSONPath matching the variable name and substitutes the value and doesn’t insert new.
Currently we are working on issues that impact broader set of customers and it will be a while before we can get to it. We do encourage contributions, if you are open, please feel free to raise a PR

@RoopeshNair , I see this was closed, but I have also been looking for a solution for a while. Is there somewhere separate to track this feature request?


Fail gracefully with a default return value when 0 keys are are provided to a command expecting at least 1 key

This is an alternative implementation to #941
Some commands like MGET, DEL, etc. accept 1 or more keys but fail if the user supplies 0 keys. From a user point of view, it would be nice if these commands simply returned an empty value when called with 0 keys. For example, MGET could return an empty list and DEL could return 0 indicating 0 keys were deleted. However, commands cannot simply return an empty value because of how they interact with pipelines.
This PR introduces a well named option EMPTY_ERROR. If a command detects one of these 0-key scenarios, it can pass the EMPTY_ERROR option with the default value that should be returned to the application. This includes the plumbing to work with pipelines.
Currently only MGET is implemented as an example. Other commands like DEL should also get this functionality if merged.
The question we need to answer is should we actually do this.

@andymccurdy I like this feature, but it gives me pause.
On one hand, I believe this is easier for the dev, perhaps even more pythonic.
It also matches the part of my brain that still works in SQL (select * from X where Y is in []).
On the other hand, this is a serious behaviour change from Redis.
I'm not that worried about backwards compatibility, though that also might be an issue.
I thought it would be nice to have two classes, one that is more pythonic, and easier to use, and one that strictly does what redis does. Then I noticed that we kind of already have that (Redis vs StrictRedis).
IMHO StrictRedis should be just that - strict, while features like this should be implemented elsewhere.
Maybe Redis class is a good fit for this, maybe not. If you think we need a new class for this, let's call it LiberalRedis or something.

@RoeyPrat
re: Backwards Compatibility: It seems like now is the time to get these kinds of changes in. There will be several compatibility issues with v3 and I'd prefer to get all this kind of stuff in at the same time.
re: StrictRedis vs. Redis: This is a longer discussion, but my hope is that we remove the StrictRedis/Redis distinction for v3. Some history: StrictRedis was created because I initially implemented some commands that deviated away from the server's expected syntax. This lead to lots of questions/bug reports, so I created StrictRedis to adhere to the server's command syntax and kept the Redis class for backwards compatibility. Sadly, this didn't really fix the bug report/question problem -- there's still quite a few bug reports about ZADD/SETEX/etc. because some people continue to use the Redis class.
The docs have encouraged the use of StrictRedis for years now. So I'd like to remove the Redis class, rename StrictRedis -> Redis, and create a StrictRedis alias of Redis. People using StrictRedis today will see no difference and continue to function as they do today without any changes. People using the Redis class will be affected if they use the small group of commands that it overrides. Providing better documentation on this stuff should help reduce the issues going forward.
All this is to say that my feeling has evolved into favoring user happiness and being "more pythonic" over strictly adhering to what the server expects, provided that we:

Have great documentation so users know what to expect
Provide enhancements over the server's behavior that are lossless, meaning these types of changes are only adding syntactic sugar or create an experience that's superior to the server without hiding any information that the user might need or want.

IMO, this change meets the lossless requirement. It's a better user experience and providing the default return value doesn't hide information or require the need for any special case code.

@andymccurdy Ok. that sounds like a good plan.

@RoeyPrat the constructor could also have another flag for throwing exceptions (like before) or silently handling this.
Also, might be time to start mapping which other commands like MGET need to be patched like this


v-model directive on

v-model directive can only be used on ,  or  elements for now.
It would be nice to use it on 'contenteditable' !
Best regards,
Benjamin

Hmm, did you mean to open an issue instead of a PR? This doesn't seem to contain anything and is merging the wrong branches.


Some blogs do not have HTTPS, allow them to use HTTP

Allow sites without SSL certificates to be loaded with http

Hilariously, even though I made the fix to set the protocol correctly, the ssl page still fails to load in an iframe:

[blocked] The page at https://blogofthe.day/? was not allowed to display insecure content from http://thisvictorianlife.com/.

But the RSS is correct. Might need a scheme to set a static image? Shades of #34 @capjamesg ? We could also attempt to pull an og:image or use something like https://github.com/simonw/shot-scraper to grab a shot and put it in as a background image.


FE: styling bugs due to em usage

I suspect there are more of these cases where em was used in the CSS and px is used elsewhere, causing render problems in some case.
MacOS

fixed

fixed


Add CLI for repo_entropy

Description
This PR introduces a CLI for tracking total software entropy from the first to the most recent commit, implemented in the cli.py module using the google fire library. The pyproject.toml file has been updated to include this CLI as a script.
The file structure has been reorganized, especially in the src/almanack folder, where the old process_repository function has been broken into smaller, more manageable components.
Additional test suites have been added.
Any and all feedback is appreciated, but I particularly would like suggestions on the testing cases and naming of functions/folders/CLI. I aimed for intuitive and simple names and welcome any suggestions!

What is the nature of your change?

[x] Content additions or updates (adds or updates content)
[ ] Bug fix (fixes an issue).
[ ] Enhancement (adds functionality).
[ ] Breaking change (these changes would cause existing functionality to not work as expected).

Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own contributions.
[X] I have commented my content, particularly in hard-to-understand areas.
[x] I have made corresponding changes to related documentation (outside of book content).
[x] My changes generate no new warnings.
[x] New and existing tests pass locally with my changes.
[x] I have added tests that prove my additions are effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

Thank you for the review @d33bs @falquaddoomi !! I have implemented most of your feedback with a couple comments on further clarity.
Main Changes:
1.) Added directories for src code organization
2.) Changed from writing to a .json file to dumping to a .json string, inside cli.py
3.) Added returns to functions referenced in cli.py


feat: add IoT Class to integration manifest

Adds the IoT Class the the integration manifest.

@hellqvio86 can you please confirm that cloud_push is the correct state?

cloud_push: Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.

cloud_push is the best case classifier listed in https://www.home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/ . The addon is also doing periodically pulls, but events are pushed through the websocket soon as the new state is available:  Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.


error

NotPixel | 2024-11-27 14:59:21 | ERROR    | 13 - Error occurred: too many values to unpack (expected 3)
why? i try create json for session always get this

NotPixel | 2024-11-27 14:59:21 | ERROR    | 13 - Error occurred: too many values to unpack (expected 3)
why? i try create json for session always get this

Oh, so someone finally managed to explain when exactly this error happens? Shocking! 🫣 Thanks to that, I figured out what the problem was. Go ahead and install the latest update!

cant use proxy? i tried to use proxy from scrape, data impulse, bird all 407 error

I’m currently troubleshooting an issue with proxies. It seems to be a problem with SOCKS proxies again, as HTTP proxies are working fine for me.

cant use proxy? i tried to use proxy from scrape, data impulse, bird all 407 error

I’m currently troubleshooting an issue with proxies. It seems to be a problem with SOCKS proxies again, as HTTP proxies are working fine for me.

Yes, that's it. The issue occurred due to the update of the aiohttp-socks library; it needs to be rolled back to version 0.8.4. I'll fix the requirements.txt file and release an update.

cant use proxy? i tried to use proxy from scrape, data impulse, bird all 407 error

@WP1223
The proxy issue has been fixed. Everything is working properly for me now, both with HTTP and SOCKS proxies, which previously had issues. I’m looking forward to your feedback to confirm that everything is working correctly on your end as well.

@WP1223
A funny situation happened: I forgot to do a git push after fixing the "too many values to unpack" error. As a result, the update was only on my computer. I've fixed it now. 🥴


TokensAnalyzer - isBinaryOperator fix for intersection

closes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/6317

Coverage increased (+0.06%) to 93.194% when pulling 07861d4fdce501a53dfea276bc7148ac5f7c0e61 on SpacePossum:master_bug_BinaryOperatorSpaces_intersection into f45c5a08595b5d09b1aec3b284a5fc854fc9eeb2 on FriendsOfPHP:master.

current code (so not introduced here);
consider & in <?php function replace(?int &$count){} TokensAnalyzer considers this a isUnaryPredecessorOperator
for example
            [
                [3 => true],
                '<?php function &foo() {}',
            ],

            [
                [5 => true, 11 => true, 17 => true],
                '<?php function foo(&$a, array &$b, Bar &$c) {}',
            ],

I think this is wrong as these aren't operators, just references, requires bunch of work

Yeah, this is a mess, there is ReferenceAnalyzer which should detect is as well.


[QUESTION] possibility to use Publish-PerTenantExtensionApps on Dev End point?

Hi,
I'm trying to automatize extensions publication to BC tenants using DevOps release pipelines while working on "AppSource" extensions. Of course this intends for internal test sandboxes deployment only. (And it works fine for real PTE)
We previously tried using method found in older Hello World's Deploy-App.ps1 script and now try using Publish-PerTenantExtensionApps function (although its name is self-explanatory).
None of this methods were successful because of this expected error "An App with same app Id 'xxxx' is Already published
with Global scope"
The only possibility we discovered for now is to manually publish from VSCode, which works well, and I did not find yet how to reproduce it into release pipeline.
My question is: would it be possible to include a switch to Publish-PerTenantExtensionApps function to enable Dev End point publication to reproduce VSCode one and then allow easy automatized deployment, even related to AppSource already deployed extension?
Or maybe I simply missed some documentations somewhere to do that in another way?
Here is used script and result (expected results anyway)
Publish-PerTenantExtensionApps -useNewLine     -ClientID $PublisherAppClientID
-ClientSecret $PublisherAppClientSecret     -tenantId $TenantId
-environment $Environment     -companyName $CompanyName
-appFiles @("myFile.app")
Result
Invoke-WebRequest : {"error":{"code":"Unknown","message":"An App with same app Id 'xxxxxxx' is Already published
with Global scope with name 'xxxxxxx'. Please use the Extension market place to install the extension or use a new app id
for the current extension. CorrelationId: xxxxx."}}
Au caractère C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\1.0.14\AppHandling\Publish-PerTenantExtensionApps.ps1:119 : 17

...             Invoke-WebRequest -Headers ($authHeaders+(@{"If-Match" =  ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation : (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Hi,
Thanks' to your last bcContainerHelper modifications as described in your "Publishing apps to a Business Central Online Environment" blog post my "issue" is now solved.
I can use Publish-BcContainerApp with bcAuthContext and environment within my pipelines to publish AppSource apps to the Development scope in a Sandbox environment.
Thank you.

Yep, I ment to write this here, but I forgot.
Sorry, but good you found it yourself.


CRD schema object causing a panic

Threw a crazy long CRD at crd2pulumi and it error out like on https://github.com/pulumi/crd2pulumi/pull/135 Its a 5000 line CRD from https://github.com/element-hq/ess-starter-edition-core
 panic: fatal: error An assertion has failed: could not parse Pulumi package. source error: could not import spec: <nil>: #/types/kubernetes:matrix.element.io%2Fv1alpha1:ElementDeploymentSpecComponentsSynapseConfigMedia/properties/volume/default: type pulumi:pulumi:Any cannot have a constant value; only booleans, integers, numbers and strings may have constant values; , and 3 other diagnostic(s)

 properties:
                               volume:
                                 default:
                                   name: media
                                   size: 2048
                                 description: The volume holding media
                                 oneOf:
                                 - not:
                                     required:
                                     - name
                                   required:
                                   - size
                                 - required:
                                   - name
                                   - size
                                 properties:
                                   name:
                                     description: The volume name to use to store the
                                       media
                                     type: string
                                   size:
                                     anyOf:
                                     - type: integer
                                     - type: string
                                     description: The volume size to use to store the
                                       media
                                     pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[MGTPE])?$
                                     x-kubernetes-int-or-string: true
                                 type: object
                             type: object

Thanks for this example @hanthor!
We're currently working on some improvements to crd2pulumi which I expect will address this. Stay tuned!
cc @rquitales

Added to epic https://github.com/pulumi/home/issues/3431


Is there a tutorial of Pika + Codis？

I find that there isn't a tutorial to guide me setup Pika  + Codis.
There are always some incompatibilities.
Which Codis and Pika Release I should choose?
What't the configuration of both of them?

Also I saw pkcluster on wiki. But after I built v3.3.6 docker image. I can't find the binary pkcluster.

pika 与codis 官方原版不兼容的核心问题在于 codis dashboard 发送的一些命令使用事务的语义（获取状态信息）。但其实对于对于pika来说并不太重要。使用codis的兼容版本可以参考branch


buildbot: disable tests because of TimeoutErrors

Motivation for this change
buildbot does not build on aarch64 because of aborted tests
Closes https://github.com/NixOS/nixpkgs/issues/39819
Things done
Disabled tests by doCheck = false. Also removed patch-file skip_test_linux_distro.patch as it is not needed, when tests are disabled.

[x ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

buildbot does not build on aarch64 because of aborted tests.

Disabled tests by doCheck = false.

Then why not disable the tests just for aarch64 ?

There's also a version bump in #36964 .

changed the request to disable tests only on aarch64.


Update Jinja2 to address CVE-2019-10906

Fixes #1976 ,
Updates Jinja2 to mitigate CVE-2019-10906. Since it's a point release and only addresses the security fix (https://github.com/pallets/jinja/releases/tag/2.10.1), it should be a fairly safe upgrade.
PR Type

Bugfix Pull Request : Minor dependency update

Meanwhile, I've restarted two failing jobs in Travis CI.

Restarted https://travis-ci.com/ansible/molecule/jobs/193368152

@emkll thanks!


remove device while device trying to join insecurely

I have a problem related to cc2530 firmware.
when some devices trying to join many times they try to join with an insecure update device so the coordinator sending remove device and force the device to leave so I searched that issue in the TI forum and find it's problem is like below:
occurs if BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is set to TRUE and pre-Zigbee 3.0 Spec devices attempt to join without sending a TCLK update.
and I want to ask you could you please change cc230 firmware that has been used for zigbee2mqtt coordinator so it let's insecure joining.
regards.

I've checked but this is already set to FALSE:

As TP2_LEAGCY_ZC is defined (https://github.com/Koenkk/Z-Stack-firmware/blob/f2a7aa17fba716c72dd46d4821328f7daeb1e238/coordinator/Z-Stack_3.0.x/firmware_CC2531_CC2530.patch#L195)

ok, I will check this patch and I will let you know.
thank's

oooh, I'm not using z-stack3 I'm using zstack ha 1.2

1.2 does not have BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE


Increment version for eventhub releases

Increment version for eventhub releases

Can one of the admins verify this patch?


Stats/Stackdriver: export data using metrics API

Dependency on https://github.com/census-instrumentation/opencensus-java/pull/1499
This PR is part of https://github.com/census-instrumentation/opencensus-java/issues/1483

Codecov Report

Merging #1501 into master will decrease coverage by 0.1%.
The diff coverage is 94.56%.

@@             Coverage Diff              @@
##             master    #1501      +/-   ##
============================================
- Coverage     82.46%   82.36%   -0.11%
- Complexity     1626     1632       +6
============================================
  Files           248      248
  Lines          7648     7614      -34
  Branches        723      726       +3
============================================
- Hits           6307     6271      -36
- Misses         1120     1121       +1
- Partials        221      222       +1

Impacted Files
Coverage Δ
Complexity Δ

...er/stats/stackdriver/StackdriverStatsExporter.java
65.27% <100%> (ø)
11 <0> (ø)
:arrow_down:

...r/stats/stackdriver/StackdriverExporterWorker.java
72.5% <93.75%> (+0.46%)
19 <9> (ø)
:arrow_down:

...rter/stats/stackdriver/StackdriverExportUtils.java
77.64% <94.66%> (-5.37%)
37 <20> (+6)

...census/implcore/trace/export/SpanExporterImpl.java
93.15% <0%> (+1.36%)
8% <0%> (ø)
:arrow_down:

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 e56a976...c138295. Read the comment docs.

Comparison after and before change on same data set. Left side OC16 (SD using Stats API), Right side OC17(SD using Metrics API).


Quick dumb question

Which is the correct way to add multiple paths for unpackerr to monitor, in the config file?
Like this?:
paths = ["/Media/.downloads/.torrents/music","/Media/.downloads/.usenet/music"]

or like this?:
paths = ["/Media/.downloads/.torrents/music,/Media/.downloads/.usenet/music"]

(note the quotes  and comma separating the 2 paths).
I tried both, but the startup log seems to give no hint whether one is right or wrong.

Quote each path, separated by commas