[Doc Feature][Update integrate media capabilities]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 3bc6ba5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
15
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 6c18bc6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
14
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 88e5e1d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
14
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
14
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 90c1af5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
14
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
14
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 20fa5c8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 992495e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:warning:Warning
View
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md

Line 42, Column 1: [Warning: file-not-found - See documentation] Invalid file link: '~/assets/images/tabs/media-capability-mobile.png'.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 61f676c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 3b0d03a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
89
18
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
16
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 8fd062b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
91
15
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
91
15
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 9ca0e81:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
91
15
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
17
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 76a86d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 4e702ad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
35
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
36
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
36
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 24e7202:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
90
17
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
16
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
93
36
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
16
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/mstdd-landing.yml
:x:Error

Details

msteams-platform/mstdd-landing.yml

Line 27, Column 7: [Error: array-length-invalid] Array 'landingContent.linkLists.links' length should be <= 10.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
16
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
16
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/mstdd-landing.yml
:x:Error

Details

msteams-platform/mstdd-landing.yml

Line 27, Column 7: [Error: array-length-invalid] Array 'landingContent.linkLists.links' length should be <= 10.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
16
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 0ec9bfa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 4f3375c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 608a61f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
92
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
88
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
91
34
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
88
13
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
89
14
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
91
34
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 6da4e0d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
93
8
link
:white_check_mark:

msteams-platform/concepts/device-capabilities/native-device-permissions.md
94
10
link
:white_check_mark:

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/whats-new.md
91
34
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/mobile-camera-image-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/device-capabilities/native-device-permissions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/API-references.md
92
19
link
:white_check_mark:

msteams-platform/apps-in-teams-meetings/teams-live-share-capabilities.md
88
8
link
:white_check_mark:

msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md
96
2
link
:white_check_mark:

msteams-platform/bots/bot-basics.md
81
41
link
:white_check_mark:

msteams-platform/bots/bot-features.md
85
19
link
:white_check_mark:

msteams-platform/bots/calls-and-meetings/call-notifications.md
86
7
link
:white_check_mark:

msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md
85
18
link
:white_check_mark:

msteams-platform/bots/calls-and-meetings/debugging-local-testing-calling-meeting-bots.md
84
17
link
:white_check_mark:

msteams-platform/bots/calls-and-meetings/requirements-considerations-application-hosted-media-bots.md
83
15
link
:white_check_mark:

msteams-platform/bots/how-to/authentication/add-authentication.md
83
90
link
:white_check_mark:

msteams-platform/bots/how-to/authentication/auth-flow-bot.md
87
8
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/channel-and-group-conversations.md
84
18
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/request-headers-of-the-bot.md
88
10
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
80
34
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
88
17
link
:white_check_mark:

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
92
7
link
:white_check_mark:

msteams-platform/bots/how-to/debug/locally-with-an-ide.md
84
18
link
:white_check_mark:

msteams-platform/bots/how-to/get-teams-context.md
88
8
link
:white_check_mark:

msteams-platform/bots/how-to/rate-limit.md
89
8
link
:white_check_mark:

msteams-platform/concepts/authentication/authentication.md
86
8
link
:white_check_mark:

msteams-platform/concepts/authentication/configure-identity-provider.md
86
4
link
:white_check_mark:

msteams-platform/concepts/build-and-test/app-studio-overview.md
83
37
link
:white_check_mark:

msteams-platform/concepts/build-and-test/apps-localization.md
81
17
link
:white_check_mark:

msteams-platform/concepts/build-and-test/debug.md
87
13
link
:white_check_mark:

msteams-platform/concepts/build-and-test/deep-links.md
81
59
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-personal-app-or-tab.md
86
8
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
83
11
link
:white_check_mark:

msteams-platform/concepts/build-and-test/test-data.md
84
11
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/apps-upload.md
85
9
link
:white_check_mark:

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
88
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 3af2509:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/publish.md
:bulb:Suggestion
View
Details

msteams-platform/apps-in-teams-meetings/API-references.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-live-share-capabilities.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-live-share-overview.md
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/botdisable.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots_appid_botframework.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots_uploading.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/compose-extensions/ceexample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/publish-app/teams-app-detail.png
:white_check_mark:Succeeded

msteams-platform/assets/images/tabs/media-capability-desktop1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/media-capability-mobile2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/tabs/microphone-capability.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/azure-deployed-apptab.png
:white_check_mark:Succeeded

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/deploy-cloud.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/deploy-provision-successmsg.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/deploy-provision-successmsgext.png
:white_check_mark:Succeeded

msteams-platform/bots/bot-basics.md
:white_check_mark:Succeeded
View

msteams-platform/bots/bot-features.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/calls-meetings-bots-overview.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/debugging-local-testing-calling-meeting-bots.md
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/requirements-considerations-application-hosted-media-bots.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/add-authentication.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/authentication/auth-flow-bot.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/channel-and-group-conversations.md
:white_check_mark:Succeeded
View

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

msteams-platform/toolkit/publish.md

Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'yanjiang' is not a valid Microsoft alias.

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

Closing as outdated.

New PR is #6074 .


Integration stop working code 500

Hi,
many thanks for this integration!
some day ago this integration did stop working
2022-12-05 17:03:09.679 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.cz_energy_spot_prices.config_flow
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 728, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/loader.py", line 745, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/homeassistant/.homeassistant/custom_components/cz_energy_spot_prices/config_flow.py", line 59, in <module>
    class OptionsFlowHandler(config_entries.OptionsFlow):
  File "/home/homeassistant/.homeassistant/custom_components/cz_energy_spot_prices/config_flow.py", line 65, in OptionsFlowHandler
    self, user_input: dict[str, Any] | None = None
TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType'
2022-12-05 17:03:09.680 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration cz_energy_spot_prices: Exception importing
 custom_components.cz_energy_spot_prices.config_flow

2022-12-05 17:02:40.516 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/forwarded.py", line 222, in forwarded_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/config/config_entries.py", line 218, in post
    return await super().post(request)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/data_entry_flow.py", line 71, in post
    result = await self._flow_mgr.async_init(
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/data_entry_flow.py", line 225, in async_init
    flow, result = await task
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/data_entry_flow.py", line 243, in _async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/config_entries.py", line 1626, in async_create_flow
    return HANDLERS[entry.domain].async_get_options_flow(entry)
  File "/home/homeassistant/.homeassistant/custom_components/cz_energy_spot_prices/config_flow.py", line 42, in async_get_options_flow
    return OptionsFlowHandler(config_entry)
NameError: name 'OptionsFlowHandler' is not defined

TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType'

This sounds like python version problem, could you check what version are you using? What HomeAssistant installation method have you used?

NameError: name 'OptionsFlowHandler' is not defined

This is strange, that class is defined few lines below this problem. could you please make sure that all the files were correctly copied into HomeAssistant folder?

I did install via HACS.
version:
{
    "domain": "cz_energy_spot_prices",
    "name": "Czech Energy Spot Prices",
    "documentation": "https://github.com/rnovacek/homeassistant_cz_energy_spot_prices",
    "dependencies": [],
    "codeowners": ["@rnovacek"],
    "requirements": [],
    "iot_class": "cloud_polling",
    "version": "0.1.0",
    "config_flow": true
}

Let me try manual install via git

Please try pulling from git again, I've tried to fix it. Not quite certain it'll help.


How to deal with the problem about installing pysvmrank

Hi,gasse.
I am meeting some problem about   installing pysvmrank.
I follow your install instruction  as mention in https://github.com/ds4dm/PySVMRank
git clone https://github.com/ds4dm/PySVMRank.git
cd PySVMRank
wget http://download.joachims.org/svm_rank/current/svm_rank.tar.gz
mkdir src/c
tar -xzf svm_rank.tar.gz -C src/c
pip install .
the problem occurs after I  input the command :pip install .
error: command 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\cl.exe' failed with exit status 2
----------------------------------------
ERROR: Command errored out with exit status 1: 'C:\Users\P1\Anaconda3\envs\tensorflow-build\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\P1\AppData\Local\Temp\pip-req-build-4lil2te7\setup.py'"'"'; file='"'"'C:\Users\P1\AppData\Local\Temp\pip-req-build-4lil2te7\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users\P1\AppData\Local\Temp\pip-record-odmowkyg\install-record.txt' --single-version-externally-managed --compile --install-headers 'C:\Users\P1\Anaconda3\envs\tensorflow-build\Include\PySVMRank' Check the logs for full command output.
Could you give me some suggestion about how to deal with such problem ?
Thanks a lot

Hello,
I have never tried compiling the package under Windows, so I cannot help you with this issue. I hope you'll find a solution.
Best


Feature request: "wait x"

Thanks for a great piece of software!
I think a switch for adding a delay before exiting when playing a file would be nice. My usecase is I use durdraw -p to play a file when I log into my machine, and by default that waits for key input before proceeding (which is suboptimal), and -x 1 causes the file to display but immediately disappear again. Adding something like --delay  together with -p (which would wait either X seconds or until a key is pressed before continuing) would be pretty nice.

Thanks for the suggestion and kind feedback!
I like it. It makes a lot of sense to me for your use case.
I'll see what I can do about implementing this feature. I think it would be nice if it could not clear the screen (or give the illusion of not clearing the screen) when exiting from playback mode, too.

Ah yes, was going to say that, optional clear would also be great :)

a switch for adding a delay before exiting when playing a file would be nice.
-x 1 causes the file to display but immediately disappear again.

I just wanted to add, you can set a frame delay (esc-D) to hold the last frame for a few seconds, inside of the invidiaul drawing. If I'm understanding correctly, this should simulate the behavior you're describing.

That's doable ofc, and I should have remembered from my old TheDraw days, but having the option in the viewer would be much easier of course :) Thanks!

having the option in the viewer would be much easier of course :)

It's now in the beta now for 0.27. You can get the "Dev" branch to try it, or wait for the release. The option is "-d" or "--delayexit" and it waits X seconds before exiting, after playing the last file in --play mode.
Thanks!

optional clear would also be great :)

This one will take a bit more work to implement, since, as mentioned, it must be "simulated" to work around the joys of ncurses. :)

Excellent, thanks! And heh, yeah, ncurses is powerful but "slightly" challenging ;) Will check out the dev bracnh


Fix: Azure avoid duplicates (316)

Possible fix for 316

I close this PR as the issue was not related to the connector, and the proposed fix will change nothing.


Include the #cause when formatting exception backtraces

Since Ruby 2.1, Exception has a #cause method which shows the underlying cause of the exception. (When running on MRI, if you raise an exception from a rescue block, it sets the cause automatically. When running on JRuby, if the underlying exception came from Java, it exposes Throwable#getCause(). The similar naming is not a coincidence - I believe it was JRuby's devs who convinced Ruby to add the feature.)
Often this contains the most useful information about the failure - the actual underlying stack which caused the test to fail, rather than a wrapped exception some higher label provided to format a nice error message.
We're currently using a trick like this to enhance ExceptionPresenter to print this extra info:
RSpec::Core::Formatters::ExceptionPresenter.class_eval do

  # Overridden to print nested causes as well as the top-level exception.
  def formatted_backtrace

    # Caught exception
    exception = @exception
    str = backtrace_formatter.format_backtrace(exception.backtrace, example.metadata)

    # Cause chain
    while exception.respond_to?(:cause)
      exception = exception.cause
      str += "--- Caused by: ---\n"
      str += backtrace_formatter.format_backtrace(exception.backtrace, example.metadata)
    end

    str
  end

end

Something like this baked into core would probably be better, but I am not sure if it makes sense in general to return it from formatted_backtrace itself, because now it formats more than one backtrace. Maybe there should be another method which calls formatted_backtrace once for each exception.

I think this makes more sense as an external formatter, most people don't want the underlying stack frames from an exception when writing tests

I'd be happy to help you write this in so you could release it as a gem to provide this for others who do want the detail though

You think that most people don't want to know why their test actually failed? Why show the stack at all then, if the only one you're showing is the wrong one?

Maybe I'm miss understanding what you mean, what does cause return? From what you're saying I'm expecting the stack which isn't trivially understandable (as it'd show memory locations and the like), where as we currently show the backtrace, which is?

Can you provide some demo output?

Given that you have a broken class:
class BrokenCode
  def self.shallow_method
    begin
      deep_method
    rescue
      raise "Something happened and I'm hiding that from the message 'because usability'."
    end
  end

  def self.deep_method
    raise 'The real cause for the failure is here!'
  end
end

And you have a spec which triggers the exception:
RSpec.describe 'some broken code' do
  it 'works' do
    BrokenCode.shallow_method
  end
end

The current output from RSpec will be:
  1) some broken code works
     Failure/Error: raise "Something happened and I'm hiding that from the message 'because usability'."
     RuntimeError:
       Something happened and I'm hiding that from the message 'because usability'.
     # ./my_spec.rb:32:in `rescue in shallow_method'
     # ./my_spec.rb:29:in `shallow_method'
     # ./my_spec.rb:43:in `block (2 levels) in <top (required)>'

The code I posted is broken for this particular case (in our real system, it somehow works for the failures I have seen to date, but it isn't very well tested.)
But the ideal output (IMO) is something like this:
  1) some broken code works
     Failure/Error: raise "Something happened and I'm hiding that from the message 'because usability'."
     RuntimeError:
       Something happened and I'm hiding that from the message 'because usability'.
     # ./my_spec.rb:32:in `rescue in shallow_method'
     # ./my_spec.rb:29:in `shallow_method'
     # ./my_spec.rb:43:in `block (2 levels) in <top (required)>'
     --- Caused by: ---
     RuntimeError:
       The real cause for the failure is here!
     # ./my_spec.rb:37:in `deep_method'
     # ./my_spec.rb:30:in `shallow_method'
     # ./my_spec.rb:43:in `block (2 levels) in <top (required)>'

I managed to fix the code I wrote not to fail in this situation, but it formats the wrong result, so I am probably going to change it to override the next method along instead (format_message_and_backtrace?)
  def formatted_backtrace

    # Caught exception
    exception = @exception
    str = backtrace_formatter.format_backtrace(exception.backtrace, example.metadata)

    # Cause chain
    while exception.respond_to?(:cause) && exception.cause
      exception = exception.cause
      str << ["--- Caused by: ---\n"]
      str << backtrace_formatter.format_backtrace(exception.backtrace, example.metadata)
    end

    str
  end

My quick attempt at improving the output in the last 5 minutes of the work week:
RSpec::Core::Formatters::ExceptionPresenter.class_eval do

  # Overridden to print nested causes as well as the top-level exception.
  # Trying to get something like this into rspec-core: https://github.com/rspec/rspec-core/issues/2044
  def formatted_backtrace(exception = @exception)

    # Caught exception
    lines = backtrace_formatter.format_backtrace(exception.backtrace, example.metadata)

    # Cause chain (recursive)
    cause = exception.respond_to?(:cause) ? exception.cause : nil
    if cause
      lines << ''
      lines << '--- Caused by: ---'

      # Replicating stuff that happens in another method.
      lines << "#{exception_class_name}:" unless exception_class_name =~ /RSpec/
      encoded_string(cause.message.to_s).split("\n").each do |line|
        lines << "  #{line}"
      end

      lines += formatted_backtrace(cause).map { |line| "  #{line}" }
    end

    lines
  end

end

This gives:

some broken code works
Failure/Error: raise "Something happened and I'm hiding that from the message 'because usability'."
RuntimeError:
Something happened and I'm hiding that from the message 'because usability'.
./my_spec.rb:46:in `rescue in shallow_method'
./my_spec.rb:43:in `shallow_method'
./my_spec.rb:57:in `block (2 levels) in <top (required)>'

--- Caused by: ---
RuntimeError:
The real cause for the failure is here!
./my_spec.rb:51:in `deep_method'
./my_spec.rb:44:in `shallow_method'
./my_spec.rb:57:in `block (2 levels) in <top (required)>'

There might be too many lines prefixed with hashes, but maybe I'm just being too picky. The way the hack is shoehorned in still feels wrong though anyway.

Not sure if this could help: https://gist.github.com/stanio/13d74294ca1868fed7fb

Monkey patching Exception certainly works too, but I thought people decided that monkey patching was evil.

I disagree with @JonRowe here -- I think that if there is a cause, it makes sense to include it in the output.  We wouldn't implement it using monkey patching, of course, but @stanio's gist is useful.  Anyone want to take a stab at a PR?

Yes, I haven't meant mine as a complete solution for the given use case, but probably demonstrate some details like omitting duplicate stack for the nested cause(s).

I think we should implement this too, @stanio are you volunteering to make a PR, or is this free for others to take a look at?

@samphippen Sorry, I wouldn't be able to help with the RSpec task.  It happens I just came across this issue while searching if there's anything like this already done I could reuse.

@trejkaz My patch for this just got merged into master, maybe we can close this issue now?

Closed by #2074


Preprocessing an impedance spectrum where all frequencies are below high_freq_threshold raises an exception

Brief description and conditions for reproducing
Note that this bug is present in the latest commit on the main branch as I installed AutoEIS by cloning this repository instead of installing the latest release (0.0.29) that is available on PyPI.
I found a bug in the preprocess_impedance_data function while testing out AutoEIS. The high_freq variable (a boolean array) that is defined on the following line
https://github.com/AUTODIAL/AutoEIS/blob/603378b0e72e74dfac552a8154cbfbbe3c9e62e4/src/autoeis/core.py#L170
will not contain any True values when freq does not contain any values greater than the value of high_freq_threshold.
So, if one attempts to preprocess an impedance spectrum that spans, e.g., a frequency range from 100 mHz to 500 Hz while high_freq_threshold=1000, then a ValueError: attempt to get argmin of an empty sequency exception will be raised by the next line
https://github.com/AUTODIAL/AutoEIS/blob/603378b0e72e74dfac552a8154cbfbbe3c9e62e4/src/autoeis/core.py#L171
since Z.imag[high_freq] will be an array with a length equal to zero (since high_freq will be an array that only contains False values).
Suggested fix
This bug can be fixed by simply adding an if high_freq.any(): after line 170 and indenting the lines that are currently lines 171-174. So the following lines of code would go from this
https://github.com/AUTODIAL/AutoEIS/blob/603378b0e72e74dfac552a8154cbfbbe3c9e62e4/src/autoeis/core.py#L170-L174
to this
high_freq = freq > high_freq_threshold
if high_freq.any():
    idx_highest_valid_freq = np.argmin(np.abs(Z.imag[high_freq]))
    # Filter out frequencies above the highest valid frequency (only works if freq is sorted)
    freq = freq[idx_highest_valid_freq:]
    Z = Z[idx_highest_valid_freq:]

I checked out the 0.0.29 tag, deleted the old Python virtual environment, created a new virtual environment (Python 3.12.4 on Linux), and installed version 0.0.29. This version is also affected by this bug.
However, after fixing that bug I then ran into KeyError: 'MCMC' exceptions upon reaching this line both when using my own impedance spectrum and when using the one returned by io.load_test_dataset.
I noticed that pyproject.toml does not limit the versions of most of the dependencies. So, I decided to try to run the included tests locally and all except one of them passed. The one that didn't pass was the one for perform_full_analysis that was set to be skipped.
I also tried switching back to the latest commit and got the same KeyError: 'MCMC' exceptions upon reaching this line.
Have you by any chance been using the same Python (virtual) environment for a while now? Could one of the updated dependencies have made a breaking change between the release of version 0.0.29 and now? If the perform_full_analysis function has been working all this time within your development environment, then this second issue might simply have gone unnoticed due to the function never being tested in the GitHub CI in a fresh environment.

Sorry for the late reply. For some reason, this completely dropped off my radar!
Anyway, thanks for the bug report. This is now fixed in #124, and merged into main. There are other fixes/minor improvements on main, so I'll issue a new release in a few hours.
RE the missing key issue: We've been rethinking the API a little bit, so there might be some more breaking changes pushed in the near future, but we'll try to settle on a stable API soon. The main branch should be functioning okay now.
RE perform_full_analysis, that's always been a pain to maintain as it does too much, although that's ultimately what many users want. We've deprecated the function for now (not sure if that's the right word, but basically calling it raises a NotImplementedException with a proper message), but we'll get back to it once we're happy with the API.
If you have any suggestions/feature requests, feel free to share in the issue tracker/discussion forum :)