address sensitive language

[x] removed term 'slave' - the underlying Jenkins product has also removed the term.

[ ] could not remove the term 'whitelist' the underlying Cordova product still uses it. See Cordova whitelist plugin docs. Not sure how to address this.

Docs Build status updates of commit 7bc7ea6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

cordovadocs/2017/build-deploy/get-started-with-ci.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/jenkins.md
:warning:Warning

Details

cordovadocs/2015/index.md
:warning:Warning

Details

cordovadocs/2017/index.md
:warning:Warning

Details

cordovadocs/2017/first-steps/get-started-with-ionic2.md
:warning:Warning

Details

cordovadocs/docfx.json
:warning:Warning

Details

cordovadocs/2017/first-steps/installation.md
:warning:Warning

Details

cordovadocs/2015/release-notes/release-update-9.md
:warning:Warning

Details

cordovadocs/2017/first-steps/develop-with-typescript.md
:warning:Warning

Details

cordovadocs/2015/release-notes/release-update-10.md
:warning:Warning

Details

cordovadocs/2017/take-further/add-azure-mobile-app.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/access-native-cordova-project.md
:warning:Warning

Details

cordovadocs/2017/publishing/publish-to-a-store.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/android-tips.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/windows-tips.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/configuration-tips.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/visual-studio-team-services.md
:warning:Warning

Details

cordovadocs/2017/samples/cordova-samples.md
:warning:Warning

Details

cordovadocs/2017/first-steps/simulate-in-browser.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/measuring-performance.md
:warning:Warning

Details

cordovadocs/2017/run-your-app/deploy-and-run-app.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/host-a-mac-in-the-cloud.md
:warning:Warning

Details

cordovadocs/2017/first-steps/ios-guide.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/ci-guide.md
:warning:Warning

Details

cordovadocs/2017/debug-test/debug-using-visual-studio.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/using-gulp-build-tasks.md
:warning:Warning

Details

cordovadocs/2017/run-your-app/run-app-windows.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/performance-tips.md
:warning:Warning

Details

cordovadocs/2017/first-steps/migrate-from-visual-studio-2015.md
:warning:Warning

Details

cordovadocs/2017/first-steps/build-your-first-app.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/general-tips.md
:warning:Warning

Details

cordovadocs/2017/run-your-app/run-app-ios.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/run-windows-in-mac-vm.md
:warning:Warning

Details

cordovadocs/2017/first-steps/toolsets.md
:warning:Warning

Details

cordovadocs/2017/take-further/add-analytics.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/ios-tips.md
:warning:Warning

Details

cordovadocs/2017/take-further/add-platform-specific-content.md
:warning:Warning

Details

cordovadocs/2017/tips-workarounds/run-web-app-in-cordova.md
:warning:Warning

Details

cordovadocs/2017/take-further/core-plugins.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/app-lifecycle-management.md
:warning:Warning

Details

cordovadocs/2017/run-your-app/run-app-android.md
:warning:Warning

Details

cordovadocs/2017/build-deploy/tfs2015.md
:warning:Warning

Details

cordovadocs/2017/take-further/using-plugins.md
:warning:Warning

Details

cordovadocs/2017/run-your-app/simulate-in-browser.md
:warning:Warning

Details

cordovadocs/2015/access-device-capabilities/use-cordova-plugins.md
:bulb:Suggestion

Details

cordovadocs/2015/build-deploy/get-started-with-ci.md
:bulb:Suggestion

Details

cordovadocs/2015/build-deploy/jenkins.md
:bulb:Suggestion

Details

cordovadocs/2017/build-deploy/get-started-with-ci.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/build-deploy/jenkins.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 58, Column 7: [Suggestion-duplicate-alt-text] Alt text 'NodeJS Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 73, Column 7: [Suggestion-duplicate-alt-text] Alt text 'NodeJS Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 125, Column 7: [Suggestion-duplicate-alt-text] Alt text 'Agent Config' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 139, Column 7: [Suggestion-duplicate-alt-text] Alt text 'Agent Config' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 242, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 256, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 270, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 287, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2015/index.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Visual Studio Tools for Apache Cordova' is duplicated in '2015/index.md(3,14)', '2017/index.md(4,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/index.md

Line 7, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Visual Studio Tools for Apache Cordova' is duplicated in '2015/index.md(3,14)', '2017/index.md(4,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/first-steps/get-started-with-ionic2.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 18, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Finished Weather application' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 459, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Weather App: Current Weather conditions' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 521, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Weather App: Current Weather conditions' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 719, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Finished Weather application' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 723, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Finished Weather application' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/docfx.json

Line 55, Column 32: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/first-steps/installation.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2015/release-notes/release-update-9.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/first-steps/develop-with-typescript.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 43, Column 1: [Suggestion-duplicate-alt-text] Alt text 'TypeScript Project Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 121, Column 1: [Suggestion-duplicate-alt-text] Alt text 'TypeScript Project Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 148, Column 1: [Suggestion-duplicate-alt-text] Alt text 'TypeScript Project Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2015/release-notes/release-update-10.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/take-further/add-azure-mobile-app.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/tips-workarounds/access-native-cordova-project.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/publishing/publish-to-a-store.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 169, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Platform selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 173, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Release Build Configuration' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 177, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 264, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/visualstudio/cross-platform/tools-for-cordova/first-steps/ios-guide?view=toolsforcordova-2017 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 318, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/visualstudio/cross-platform/tools-for-cordova/first-steps/ios-guide?view=toolsforcordova-2017 NOTE: This Suggestion will become a Warning in early December, 2020.
Line 322, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Platform selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 326, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Release Build Configuration' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 330, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/tips-workarounds/android-tips.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Tips and workarounds for building Windows apps using Visual Studio Tools for Apache Cordova.' is duplicated in '2017/tips-workarounds/android-tips.md(3,14)', '2017/tips-workarounds/windows-tips.md(3,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/tips-workarounds/windows-tips.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Tips and workarounds for building Windows apps using Visual Studio Tools for Apache Cordova.' is duplicated in '2017/tips-workarounds/android-tips.md(3,14)', '2017/tips-workarounds/windows-tips.md(3,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/tips-workarounds/configuration-tips.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 174, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 189, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 198, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 215, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 219, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 223, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 229, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 235, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 241, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 254, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 263, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 267, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 271, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 297, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 318, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 324, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 328, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 340, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 345, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/build-deploy/visual-studio-team-services.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/samples/cordova-samples.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/first-steps/simulate-in-browser.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Run Your App Using Cordova Simulate - Cordova' is duplicated in: '2017/first-steps/simulate-in-browser.md(2,8), 2017/run-your-app/simulate-in-browser.md(2,8)'. Titles must be unique within a docset.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Run Your App Using Cordova Simulate' is duplicated with other articles: '2017/first-steps/simulate-in-browser.md(15,1), 2017/run-your-app/simulate-in-browser.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 108, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate: Accelerometer pane' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 115, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate: Accelerometer pane' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/tips-workarounds/measuring-performance.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 77, Column 1: [Suggestion-duplicate-alt-text] Alt text 'layout and rendering profiler' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 81, Column 1: [Suggestion-duplicate-alt-text] Alt text 'layout and rendering profiler' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/run-your-app/deploy-and-run-app.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Cordova build process in Visual Studio' is duplicated with other articles: '2015/build-deploy/deploy-and-run-app.md(9,1), 2017/run-your-app/deploy-and-run-app.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/tips-workarounds/host-a-mac-in-the-cloud.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 32, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/first-steps/ios-guide.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 91, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - step 1' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 95, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - step 2' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 108, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - complete' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 112, Column 1: [Suggestion-duplicate-alt-text] Alt text 'remotebuild server process' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 131, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - step 1' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 135, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - step 2' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 148, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Initial remotebuild configuration - complete' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 152, Column 1: [Suggestion-duplicate-alt-text] Alt text 'remotebuild server process' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 205, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Settings for non-secure mode' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 213, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Settings for non-secure mode' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 235, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 287, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 291, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 374, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 378, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Target selector' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 480, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Settings for non-secure mode' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/build-deploy/ci-guide.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/debug-test/debug-using-visual-studio.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Debug your app built with Visual Studio Tools for Apache Cordova' is duplicated with other articles: '2015/build-deploy/debug-using-visual-studio.md(9,1), 2017/debug-test/debug-using-visual-studio.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/build-deploy/using-gulp-build-tasks.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/run-your-app/run-app-windows.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Run your Apache Cordova app on Windows' is duplicated with other articles: '2015/build-deploy/run-app-windows.md(9,1), 2017/run-your-app/run-app-windows.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/tips-workarounds/performance-tips.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/first-steps/migrate-from-visual-studio-2015.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 28, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Select the source project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 32, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Select the source project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 42, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Select the source project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 56, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Select the source project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 60, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Select the source project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/first-steps/build-your-first-app.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 52, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Cordova Project Structure' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 72, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Cordova Project Structure' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 106, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate Options' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 110, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate Options' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 532, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Configuration Editor: Plugins' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 536, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Configuration Editor: Plugins' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 636, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Platform-Specific Javascript File' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 646, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Platform-Specific Javascript File' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/tips-workarounds/general-tips.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 25, Column 1: [Suggestion-alt-text-bad-value] Alt text 'CORS' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 40, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio notifications' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 45, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio notifications' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 181, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Custom Local Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 194, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Custom Local Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 196, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Custom Local Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/run-your-app/run-app-ios.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 14, Column 1: [Suggestion-duplicate-h1s] H1 'Run your Apache Cordova app on iOS' is duplicated with other articles: '2015/build-deploy/run-app-ios.md(10,1), 2017/run-your-app/run-app-ios.md(14,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/tips-workarounds/run-windows-in-mac-vm.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 46, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 55, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 73, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 114, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/first-steps/toolsets.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/take-further/add-analytics.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/tips-workarounds/ios-tips.md

Line 4, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 13, Column 1: [Suggestion-duplicate-h1s] H1 'iOS and OSX Tips and Workarounds' is duplicated with other articles: '2015/tips-workarounds/ios-readme.md(10,1), 2017/tips-workarounds/ios-tips.md(13,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/take-further/add-platform-specific-content.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Add platform-specific content to your Cordova project' is duplicated with other articles: '2015/take-further/configure-app.md(10,1), 2017/take-further/add-platform-specific-content.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/tips-workarounds/run-web-app-in-cordova.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 66, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 70, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 74, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 90, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Select a Publish Target' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 97, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Select a Publish Target' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 107, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 125, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Solution Explorer' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 227, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/visualstudio/cross-platform/tools-for-cordova/?view=toolsforcordova-2017#the-w3c-content-security-policy-csp NOTE: This Suggestion will become a Warning in early December, 2020.
Line 242, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Run the Hosted Web App' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 348, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Run the Hosted Web App' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 364, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Plugin files in the ASP.NET project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 376, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Plugin files in the ASP.NET project' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/take-further/core-plugins.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Visual Studio Core Plugins' is duplicated with other articles: '2015/access-device-capabilities/use-cordova-plugins.md(9,1), 2017/take-further/core-plugins.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 35, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 51, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 68, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 84, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 100, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 116, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/build-deploy/app-lifecycle-management.md

Line 7, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/run-your-app/run-app-android.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 79, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Standard Toolbar' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 83, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Standard Toolbar' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 95, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio: Install Android Emulators' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 99, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio: Install Android Emulators' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 107, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Standard Toolbar' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 117, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Standard Toolbar' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 189, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Visual Studio Standard Toolbar' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2017/build-deploy/tfs2015.md

Line 5, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.

cordovadocs/2017/take-further/using-plugins.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Manage plugins for apps built with Visual Studio Tools for Apache Cordova' is duplicated with other articles: '2015/access-device-capabilities/manage-plugins.md(9,1), 2017/take-further/using-plugins.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2017/run-your-app/simulate-in-browser.md

Line 6, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'.
Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Run Your App Using Cordova Simulate - Cordova' is duplicated in: '2017/first-steps/simulate-in-browser.md(2,8), 2017/run-your-app/simulate-in-browser.md(2,8)'. Titles must be unique within a docset.
Line 15, Column 1: [Suggestion-duplicate-h1s] H1 'Run Your App Using Cordova Simulate' is duplicated with other articles: '2017/first-steps/simulate-in-browser.md(15,1), 2017/run-your-app/simulate-in-browser.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 108, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate: Accelerometer pane' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 115, Column 1: [Suggestion-duplicate-alt-text] Alt text 'Cordova Simulate: Accelerometer pane' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2015/access-device-capabilities/use-cordova-plugins.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 9, Column 1: [Suggestion-duplicate-h1s] H1 'Visual Studio Core Plugins' is duplicated with other articles: '2015/access-device-capabilities/use-cordova-plugins.md(9,1), 2017/take-further/core-plugins.md(15,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.
Line 29, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 45, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 62, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 78, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 94, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 110, Column 1: [Suggestion-duplicate-alt-text] Alt text 'scan-for-devices' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

cordovadocs/2015/build-deploy/get-started-with-ci.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 16, Column 57: [Suggestion-alt-text-missing] Missing alternate text for image 'https://raw.githubusercontent.com/Microsoft/vsts-cordova-tasks/master/docs/media/misc/cordova_logo_white_purple.png'. Alt text is required for accessibility. NOTE: This Suggestion will become a Warning in late September, 2020.

cordovadocs/2015/build-deploy/jenkins.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 48, Column 7: [Suggestion-duplicate-alt-text] Alt text 'NodeJS Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 59, Column 7: [Suggestion-duplicate-alt-text] Alt text 'NodeJS Plugin' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 109, Column 7: [Suggestion-duplicate-alt-text] Alt text 'Agent Config' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 123, Column 7: [Suggestion-duplicate-alt-text] Alt text 'Agent Config' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 228, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 247, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 257, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.
Line 274, Column 5: [Suggestion-duplicate-alt-text] Alt text 'Build script' is duplicated. Within an article, alt text must be unique. NOTE: This Suggestion will become a Warning in late October, 2020.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


productionSourceMap not built

Client-source maps are never built in production mode:
https://github.com/Akryum/vue-cli-plugin-ssr/blob/2037d18a76999dd849101f42d60c2a6319549ac2/lib/webpack.js#L65
vue.config.js includes a productionSourceMap option, that is true by default.:
https://cli.vuejs.org/config/#productionsourcemap
IMHO it should be considered as in
https://github.com/vuejs/vue-cli/blob/2cf5849222db24ce5c3b5607513f32ac79a476a7/packages/%40vue/cli-service/lib/config/prod.js#L13
version<EMAIL_ADDRESS>

I can confirm this still doesnt work. But you can at least easily workaround it by setting devtool manually in your vue.config.js:
module.exports = {
  // productionSourceMap: true, // doesnt work currently
  chainWebpack: (config) => {
    config
      .devtool('source-map')
  }
}


Develop nilesh raster clone bug

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

No, I haven't read it.

Is this PR related to a JIRA ticket?

Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format [SEDONA-XXX] my subject.

No, this is a documentation update. The PR name follows the format [DOCS] my subject.

What changes were proposed in this PR?
How was this patch tested?
Did this PR include necessary documentation updates?

Yes, I am adding a new API. I am using the current SNAPSHOT version number in since vX.Y.Z format.
Yes, I have updated the documentation update.
No, this PR does not affect any public API so no need to change the docs.

@iGN5117 Do we also need to update other related functions such as copyRasterAndAppendBand and copyRasterAndReplaceBand since they also clone the rasters?

@iGN5117 Do we also need to update other related functions such as copyRasterAndAppendBand and copyRasterAndReplaceBand since they also clone the rasters?

Yes @jiayuasu I will do that once the new rasterUtils functions are approved, This PR will finally replace all places where rasters are cloned


AttributeError: 'LandslideProbability' object has no attribute 'landslide_factor_of_safety_histogram' (landslide_driver)

core_nodes = LS_prob.grid.core_nodes
LS_prob.landslide__factor_of_safety_histogram[core_nodes[10]]
results in the following error

AttributeError: 'LandslideProbability' object has no attribute 'landslide_factor_of_safety_histogram'

@itaher1995 Please close and move to https://github.com/hydroshare/hydroshare-jupyterhub


exportcert command: Export only if total hours contributed is positive and non-zero

Previously,

Records with 0 hour values would still be included in the exported certificate.
Volunteers with all records having 0 hour values (thus no hours contributed at all) would still have their certificates exported.

This is meaningless and doesn't achieve the intended purpose of the certificate (verification and formal record provision).
Thus, the following change was made:

ExportCertCommand now goes through an additional layer of filtering through records to surface only the ones with a non-zero, positive hour value. Thus the above two instances are accordingly managed and a certificate won't be exported.

RecordContainsNonZeroHourPredicate has been created for this additional layer of filtering.

Coverage increased (+0.01%) to 65.912% when pulling 695efa770686da2b1a1a9c8bc1b230b6a7bf2f50 on sharan8:exportcert-command into 36515dc33d75d716106a9bad2ee162044a6fc3d2 on CS2103-AY1819S1-W16-2:master.


libpod: prefer WaitForFile to polling

replace two usage of kwait.ExponentialBackoff in favor of WaitForFile
that uses inotify when possible.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

lgtm

Once this merges we may want to look into what we're actually using our remaining Kube code for - I think we're close to being able to drop the vendor.

/lgtm


Using CMake's FetchContent instead of git submodules

This will replace git submodules with CMake's FetchContent which would make the project more manageable and flexible.
Also would allow much freedom in customizing and/or updating bgfx sub-projects without going thru many ambiguities of the git submodules system.

Thanks for the comment.

How does this allow more flexibility?

Updating git submodules locally is a major headache from my personal experience (pulling latest bgfx.cmake will often leave submodules outdated and would require a lot of manual git work). Also sometimes can't prevent git from fetching submodules even if B*_DIR variables are specified, which leads to redundancy (especially if used with FetchContent or any other third party CMake packaging system as a sub-project).

Now we have to go through the ambiguities of fetchsystem?

What do you mean? This is totally transparent to the user.

The set versions are now scattered in CMake instead of .gitmodule meaning our depenabot action will fall.

Those are only defined at one place in the CMake file, and everything else works properly beyond that.

The version bump brings CMake to an unsupported version for android studio.

Android Studio does not force a certain CMake version, you can use any version you want beyond the minimum required : https://developer.android.com/studio/projects/install-ndk#vanilla_cmake

Not everyone wants to use fetchcontent, it's not a good system.

https://medium.com/analytics-vidhya/c-dependency-management-with-cmakes-fetchcontent-4ceca4693a5d
Not everyone likes git submodules according to many articles I read.

You're free to use it in your own projects and use the B*_DIR

I'm not forcing this PR on anyone, I'm just checking if anyone interested in my changes, it's up to you to take it or leave it.
But again the main purpose of that is to make it more flexible to use it with a third party CMake packaging systems such as CPM.cmake : https://github.com/cpm-cmake/CPM.cmake, or FetchContent itself as a convenient sub-project.


MM-35840: fixes up arrow edit in CRT

Summary
We used to get post ids from the channel to find current user's last
post in a thread. This worked when CRT off, but when you turn CRT on,
replies are not added in the channel thus not being able to find the
user's last post correctly (was always resolving to the root post).
This commit fixes that by getting post ids from the thread*
(postsInThread reducer) and not the channel, this way both CRT on/off are
working as expected.
*renamed the selector from makeGetCurrentUsersLatestPost to
makeGetCurrentUsersLatestReply.
Ticket Link
https://mattermost.atlassian.net/browse/MM-35840
Release Note
NONE

Thanks @koox00
Seeing few issues

After user makes multiple back to back replies in a thread, arrow up is not picking up the last post they made, instead it picks up the first they made after another user. Repros with CRT on and off
e.g. User1 posts 3 consecutive posts 7, 8 and 9 after sysadmin; arrow up brings up edit modal for the first post 7 and not last 9

There is a 500 server error when following a post

Unable to use arrow up on a single post in RHS, nothing happens, no errors either. Repros with CRT on and off

Thanks @jgilliam17!
1 and 3 should be fixed now, and I think 2 have been fixed on master in another ticket,
I updated this branch so we shouldn't see it.

Thanks @koox00 - 1 and 3 are fixed, looks good. The server 500 error is still present when opening single post on the RHS and starting to follow it, but I just retested and it reproduces on daily.
There are also few gateway time-out errors.  I don't have exact repro steps, I left the app idle for few minutes to repro errors on daily and upon return found the errors in the console for both users.

/update-branch

@koox00 can we re-assign reviewers if you're comfortable with it since Caleb is out for the rest of the week?

I confess I'm not sure I'm in the loop enough to properly review this change -- deferring back to @calebroseland for now.

FYI @jgilliam17 the 500 error is unrelated to this PR, I've opened another ticket for that.
The websocket issue seem unrelated too since we saw those yesterday on the testing session (this PR was not tested), but I can't find the cause of that.


azure-functions:deploy failing with "OnError while emitting onNext value: retrofit2.Response.class"

Plugin name and version
azure-functions-maven-plugin  1.6.0
Plugin configuration in your pom.xml
See attached source code
Expected behavior
Expect function to deploy successfully per sample in https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function-azure-cli?tabs=bash%2Cbrowser&pivots=programming-language-java
Actual behavior

[INFO] [Correlation ID: 4d4ddcc1-5957-4e10-89da-3daff36c5e70] Instance discovery was successful
[DEBUG] [Correlation ID: 4d4ddcc1-5957-4e10-89da-3daff36c5e70] Access Token and Refresh Token were returned
[INFO] Subscription : retailMgmt(845739df-78dd-4d05-9c57-21afecd45629)
[INFO] The specified function app does not exist. Creating a new function app...
[INFO] Set function worker runtime to java.
[INFO] Creating application insights...
[INFO] Successfully created the application insights $(artifactId)-$(timestamp) for this Function App. You can visit https://portal.azure.com/#resource/subscriptions/845739df-78dd-4d05-9c57-
21afecd45629/resourceGroups/java-functions-group/providers/microsoft.insights/components/$(artifactId)-$(timestamp)/overview to view your Application Insights component.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  47.107 s
[INFO] Finished at: 2020-07-14T21:10:10-07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.microsoft.azure:azure-functions-maven-plugin:1.6.0:deploy (default-cli) on project helloworldfunction: Unknown error with status code 404 and body : OnErro
r while emitting onNext value: retrofit2.Response.class -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.microsoft.azure:azure-functions-maven-plugin:1.6.0:deploy (default-cli) on project helloworldfunction: Unknown error with status code 404 and body
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
...
...
Caused by: rx.exceptions.OnErrorThrowable$OnNextValue: OnError while emitting onNext value: retrofit2.Response.class
at rx.exceptions.OnErrorThrowable.addValueAsLastCause (OnErrorThrowable.java:118)
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onNext (OnSubscribeMap.java:73)
at retrofit2.adapter.rxjava.CallArbiter.deliverResponse (CallArbiter.java:120)
at retrofit2.adapter.rxjava.CallArbiter.emitResponse (CallArbiter.java:102)
at retrofit2.adapter.rxjava.CallExecuteOnSubscribe.call (CallExecuteOnSubscribe.java:46)
at retrofit2.adapter.rxjava.CallExecuteOnSubscribe.call (CallExecuteOnSubscribe.java:24)
at rx.Observable.unsafeSubscribe (Observable.java:10327)
at rx.internal.operators.OnSubscribeMap.call (OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call (OnSubscribeMap.java:33)
at rx.Observable.unsafeSubscribe (Observable.java:10327)
at rx.internal.operators.OnSubscribeSingle.call (OnSubscribeSingle.java:81)
at rx.internal.operators.OnSubscribeSingle.call (OnSubscribeSingle.java:27)
at rx.internal.operators.SingleToObservable.call (SingleToObservable.java:39)
at rx.internal.operators.SingleToObservable.call (SingleToObservable.java:27)
at rx.Observable.unsafeSubscribe (Observable.java:10327)
at rx.internal.operators.OnSubscribeMap.call (OnSubscribeMap.java:48)
at rx.internal.operators.OnSubscribeMap.call (OnSubscribeMap.java:33)
at rx.internal.operators.OnSubscribeLift.call (OnSubscribeLift.java:48)
Steps to reproduce the problem
mvn azure-functions:deploy
helloworldfunction.zip
helloworldfunction.zip

@ssampigegithub Thanks for your report, it seems that the functionAppName in your pom file is not set correctly, which is <functionAppName>$(artifactId)-$(timestamp)</functionAppName>, could you replace the value and try again?
Besides, $(artifactId)-$(timestamp) is the default value in archetype and should be replaced while generate the project,  it seems the archetype post script didn't work, did you meet any issues while generating the project? Any information could be helpful.

Yes. I changed it to
  <functionAppName>${artifactId}</functionAppName>

Same error.

I changed it to         helloWorldFunctionApp  also and tried. But same error.
Interesting thing is eventhough it fails it creates 4 storage accounts, the app service plan and the application insights.
In the app service plan under apps i don't see anything. Both screenshots attached (.PNG format).

Ok, this gets very interesting.  It worked! I narrowed down the issue and it gets very interesting. Changing the functionAppName works. I am able to repeatedly produce success and failures now by commenting+uncommenting the following sections to cycle between function app names. Each time before running i manually clear out all the resources in azure. So, can't really explain what the underlying issue is with the azure functions maven plugin, something for you to take a look..especially in the error reporting (more details to aid troubleshooting the better).
    <!-- <functionAppName>${artifactId}</functionAppName> --> <!-- fails -->
    <!-- <functionAppName>helloWorldFunctionApp</functionAppName>  --> <!-- fails -->
    <functionAppName>helloWorldFunctionAppInsights</functionAppName> <!-- SUCCESS!! -->

[INFO] [Correlation ID: c3485437-31db-47c2-804f-d7f96c2829ed] Instance discovery was successful
[DEBUG] [Correlation ID: c3485437-31db-47c2-804f-d7f96c2829ed] Access Token and Refresh Token were returned
[INFO] Subscription : retailMgmt(845739df-78dd-4d05-9c57-21afecd45629)
[INFO] The specified function app does not exist. Creating a new function app...
[INFO] Set function worker runtime to java.
[INFO] Creating application insights...
[INFO] Successfully created the application insights helloWorldFunctionAppInsights for this Function App. You can visit https:
57-21afecd45629/resourceGroups/rates-dev/providers/microsoft.insights/components/helloWorldFunctionAppInsights/overview to vie
[INFO] Successfully created the function app: helloWorldFunctionAppInsights.
[INFO] Trying to deploy the function app...
[DEBUG] Compressing 'C:\2020-Workspaces\azure-cloud-pocs\helloworldfunction\target\azure-functions\helloWorldFunctionAppInsigh
\target\azure-functions\helloWorldFunctionAppInsights.zip'.
[DEBUG] Copying 'C:\2020-Workspaces\azure-cloud-pocs\helloworldfunction\target\azure-functions\helloWorldFunctionAppInsights.z
6183088348.zip' and removing paths [local.settings.json].
[INFO] Trying to deploy artifact to helloWorldFunctionAppInsights...
[INFO] Successfully deployed the artifact to https://helloworldfunctionappinsights.azurewebsites.net
[INFO] Successfully deployed the function app at https://helloWorldFunctionAppInsights.azurewebsites.net.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:13 min
[INFO] Finished at: 2020-07-15T09:12:14-07:00
[INFO] ------------------------------------------------------------------------

@ssampigegithub Thanks for the updates, it seems that some one has created function/app service named helloworldfunction  and if you try to deploy a new one with the same name, function service will block it and returns failed, and this is by design, we plan to do the validation earlier in later releases.
Below is the error log, could you please helps check whether you meet the same error.
[ERROR] Failed to execute goal com.microsoft.azure:azure-functions-maven-plugin:1.6.0:deploy (default-cli) on project helloworldfunction: Website with given name helloworldfunction already exists.: OnError while emitting onNext value: retrofit2.Response.class -> [Help 1]


Add dropwizard contrib

The OpenCensus DropWizard Util is to provides an easy way to translate DropWizard metrics OpenCensus metrics.

Codecov Report

Merging #1423 into master will decrease coverage by 0.72%.
The diff coverage is 96.1%.

@@             Coverage Diff              @@
##             master    #1423      +/-   ##
============================================
- Coverage      83.7%   82.97%   -0.73%
+ Complexity     1525     1520       -5
============================================
  Files           233      235       +2
  Lines          7000     7148     +148
  Branches        660      672      +12
============================================
+ Hits           5859     5931      +72
- Misses          940     1014      +74
- Partials        201      203       +2

Impacted Files
Coverage Δ
Complexity Δ

...pencensus/implcore/metrics/MetricRegistryImpl.java
100% <100%> (ø)
7 <4> (ø)
:arrow_down:

...opencensus/contrib/dropwizard/DropWizardUtils.java
87.5% <87.5%> (ø)
2 <2> (?)

...encensus/contrib/dropwizard/DropWizardMetrics.java
96.96% <96.96%> (ø)
17 <17> (?)

...nt/instrumentation/TraceTrampolineInitializer.java
0% <0%> (-100%)
0% <0%> (-2%)

.../instrumentation/ContextTrampolineInitializer.java
0% <0%> (-100%)
0% <0%> (-2%)

...in/java/io/opencensus/contrib/agent/AgentMain.java
0% <0%> (-95.46%)
0% <0%> (-4%)

...ntrib/agent/instrumentation/TraceStrategyImpl.java
0% <0%> (-85%)
0% <0%> (-4%)

...rib/agent/instrumentation/ContextStrategyImpl.java
0% <0%> (-81.82%)
0% <0%> (-4%)

...opencensus/contrib/agent/AgentBuilderListener.java
0% <0%> (-77.78%)
0% <0%> (-6%)

...ain/java/io/opencensus/contrib/agent/Settings.java
44.44% <0%> (-44.45%)
2% <0%> (-2%)

... and 6 more

Continue to review full report at Codecov.

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

You should use SUMMARY from https://github.com/census-instrumentation/opencensus-java/pull/1479


fix container build base image reference

changes base image for container build to golang:1.5.3 to fix issue #71

LGTM thanks!


Include timescaledb toolkit

Did you consider including the TimescaleDB toolkit in the image in the image? It adds a lot of SQL functions for time data. My current usecase is to add gapfilling for one of my sensors, but this function requires the toolkit.

Hi @Yamakaky!
Yes I am certainly trying to. the only thing holding me back is this open issue that's preventing me from buidling for aarch64:
https://github.com/timescale/timescaledb-toolkit/issues/212
I'm keeping an eye on this one, as soon we have a path forward, I will add it to the addon!

Nice! I tried to build it myself but gave up ^^

There seems to be Aarch64 support since 1. septembre 🎉
https://github.com/timescale/timescaledb-toolkit/issues/382#issuecomment-1259806133

Wheey! So I've been watching the wrong issue there?
Well, at least we can now implement this! Stay tuned!

.. why oh why is this so hard...

BOOM! Version 4.0.1 is a fact.
It was definitely not a walk in the park, but now I close this issue with pride!! 🥳


Have width of dropdown dependent on the maximum width of an answer

Specifically this would be helpful for a dropdown that had something like years, 1900-2016, where the width is currently much larger than necessary.

Hi @Splinterfloss,
I agree, that in many cases it doesn't look great. I am using 'form-control' class for input elements in bootstrap version. This class defines width as '100%'.
There are several solutions for this problem:

set a question width attribute to 'auto': { type: "dropdown", name: "q1", choices: [1, 2, 3],  width: "auto" }
Override surveyjs css classes, here is the example. You need to change survey.css.dropdown property: mySurvey.css.dropdown = "myNewClass";
Fix it on bootstrap css level: override the bootstrap 'form-control' class or add a custom rule for select element.

Please let me know if it helps.
Thank you,
Andrew

@ZakMiller We have added question.width property some times ago.
Here is the example: https://plnkr.co/edit/JwIuOw9x3UjWIXsHP144?p=preview
Thank you,
Andrew


Specialize thrift (#4891)

Draft as needs cleaning up
Which issue does this PR close?

Closes #4891
Rationale for this change

We aren't using TCompactSliceInputProtocol and yet are already seeing non-trivial performance benefits from where we are
open(default)           time:   [23.783 µs 23.801 µs 23.822 µs]
                        change: [-10.316% -10.211% -10.106%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

open(page index)        time:   [705.79 µs 705.98 µs 706.18 µs]
                        change: [-33.072% -33.014% -32.960%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

What changes are included in this PR?

Are there any user-facing changes?

With the latest changes
open(default)           time:   [15.697 µs 15.705 µs 15.714 µs]
                        change: [-40.766% -40.682% -40.602%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 100 measurements (10.00%)
  5 (5.00%) high mild
  5 (5.00%) high severe

open(page index)        time:   [691.76 µs 692.23 µs 692.72 µs]
                        change: [-34.457% -34.394% -34.334%] (p = 0.00 < 0.05)
                        Performance has improved.

I think it is important to note that this is related to making Parquet reading faster - as the connection between TCompactSliceInputProtocol and reading parquet metadata may not be obvious


[ENH] Change external labeler to use the GH CLI for fine-grained token support

Description
This PR rewrites the action from graphQL to gh cli.
~Functionality should remain the same.~ Removed discussions since they're not supported by the gh cli.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


Add another usage example

See #12

Thank you for your contribution, but I'm not sure about this one. There seems to be a bit too much duplication between the examples. Both sections are very similar with only the code and the description that is different. Also, I like my example better as the code is very minimal and easy to understand. The example code is not something that people should analyze, as it serves basically as a placeholder and anybody can put there whatever she/he likes.

I understand. No problem!


Sounds good!
Would you do two things in the commit message?

Mention why we want to do this. :slightly_smiling_face: (It's in the PR description -- the files are slightly smaller -- but that's a draft and the repo is our primary record.)
Saying "supported on Android 15+" is rather disorienting, as this year's new version is Android 10. :stuck_out_tongue: "API 15" works; or "Android API level 15" would be a formal, explicit way to put it.
Actually here's a third thing: presumably you learned these facts about what's supported where from some reference. Would you link to that reference?

Done!

Thanks -- merged!


Callback exception trace, optional fields IFTTT, project status

Hi,
thanks for the great project. Also the documentation looks very, very good for a project this size.
I wonder if the project is still alive? I tried installing the project, but get some exceptions on callbacks:
2022-08-18 09:42:41 default[redacted]  [bunqcb_mutation] input: {"NotificationUrl": {"target_url": "https://redacted.appspot.com//bunq2ifttt_mutation", "category": "MUTATION", "event_type": "MUTATION_RECEIVED", "object": {"Payment": {"id": 123456, "created": "2022-08-18 09:42:41.119373", "updated": "2022-08-18 09:42:41.119373", "monetary_account_id": 12345, "amount": {"currency": "EUR", "value": "0.01"}, "description": "", "type": "BUNQ", "merchant_reference": null, "alias": {"iban": "DE123456789000", "is_light": false, "display_name": "Forename", "avatar": {"uuid": "redacted", "image": [{"attachment_public_uuid": "redacted", "height": 1024, "width": 1024, "content_type": "image/jpeg", "urls": [{"type": "ORIGINAL", "url": "https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/redacted.jpg"}]}], "anchor_uuid": null, "style": "NONE"}, "label_user": {"uuid": "redacted", "display_name": "Forename", "country": "DE", "avatar": {"uuid": "redacted", "image": [{"attachment_public_uuid": "redacted", "height": 389, "width": 389, "content_type": "image/jpeg", "urls": [{"type": "ORIGINAL", "url": "https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/redacted.jpg"}]}], "anchor_uuid": "redacted", "style": "NONE"}, "public_nick_name": "Forename", "type": "PERSON"}, "country": "DE"}, "counterparty_alias": {"iban": "DE123456790000", "is_light": false, "display_name": "Forename Lastname", "avatar": {"uuid": "redacted", "image": [{"attachment_public_uuid": "redacted", "height": 1024, "width": 1024, "content_type": "image/jpeg", "urls": [{"type": "ORIGINAL", "url": "https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file/File/content/redacted.jpg"}]}], "anchor_uuid": null, "style": "NONE"}, "label_user": {"uuid": "redacted", "display_name": "Forename Lastname", "country": "DE", "avatar": {"uuid": "redacted", "image": [{"attachment_public_uuid": "redacted", "height": 389, "width": 389, "content_type": "image/jpeg", "urls": [{"type": "ORIGINAL", "url": "https://bunq-prod-model-storage-public.s3.eu-central-1.amazonaws.com/bunq_file%2FFile%2Fcontent%redacted.jpg"}]}], "anchor_uuid": "Redacted", "style": "NONE"}, "public_nick_name": "Forename", "type": "PERSON"}, "country": "DE"}, "attachment": [], "geolocation": null, "batch_id": null, "scheduled_id": null, "address_billing": null, "address_shipping": null, "sub_type": "PAYMENT", "request_reference_split_the_bill": [], "balance_after_mutation": {"currency": "EUR", "value": "1.01"}, "payment_auto_allocate_instance": null}}}}
2022-08-18 09:42:41 default[redacted]  Traceback (most recent call last):    File "/srv/event.py", line 136, in bunq_callback_mutation      print("[bunqcb_mutation] translated: {}".format(json.dumps(item)))    File "/opt/python3.7/lib/python3.7/json/__init__.py", line 231, in dumps      return _default_encoder.encode(obj)    File "/opt/python3.7/lib/python3.7/json/encoder.py", line 199, in encode      chunks = self.iterencode(o, _one_shot=True)    File "/opt/python3.7/lib/python3.7/json/encoder.py", line 257, in iterencode      return _iterencode(o, 0)    File "/opt/python3.7/lib/python3.7/json/encoder.py", line 179, in default      raise TypeError(f'Object of type {o.__class__.__name__} '  TypeError: Object of type method is not JSON serializable

Furthermore, with the mutation triggers, I get errors in IFTTT if i do not provide every parameter. I double checked the documentation looking for a way to define optional parameters. But according to documentation, a mutation trigger with ANY/ANY is possible without defining the remaining.

Is anybody currently using the project with success?
Thank you very much.

Ok at least I got the callback stuff working by calling the arrow.timestamp as method in event.py and not passing the method itself to json.dumps. Not sure why this worked in the first place for anyone.
diff --git a/app/event.py b/app/event.py
index 506708f..a6f264b 100644
--- a/app/event.py
+++ b/app/event.py
@@ -59,7 +59,7 @@ def bunq_callback_request():
             "request_id": metaid,
             "meta": {
                 "id": metaid,
-                "timestamp": arrow.get(obj["created"]).timestamp
+                "timestamp": arrow.get(obj["created"]).timestamp()
             }
         }

@@ -129,7 +129,7 @@ def bunq_callback_mutation():
             "payment_id": metaid,
             "meta": {
                 "id": metaid,
-                "timestamp": arrow.get(payment["created"]).timestamp
+                "timestamp": arrow.get(payment["created"]).timestamp()
             }
         }

arrow had some breaking changes with 1.0, so timestamp property is not called int_timestamp and the timestamp method matches behavior of datetime. So it should probably changed to int_timestamp.
See https://github.com/arrow-py/arrow/issues/832
Maybe pinning the packages version is a good idea. I will do some PRs if I find some free time :).

Okay I found a workaround for the missing fields error. Creating the applet with the iOS apps works without any problems.
It seems to be a bug of IFTTT web interface, the request payload to https://ifttt.com/api/v3/graph it is randomly missing parameters. Tested it with different browsers and addons disabled.


Adding sentence "An inline frame is used to embed another document wi…

…thin the current HTML document."

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

We are marking this PR invalid for Hactoberfest as it does not follow the recommended guidelines below:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove white space / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details
Taken from https://www.w3schools.com/tags/tag_iframe.asp


Give debugging sessions unique names

If we're testing in both frameworks we're going to start more than one debugging session. If both build configurations have the same name LLDB will replace the output of the first one in the Debug Console with the output of the second one. This means the user loses the debug output from the first session.
If they each have a unique name the Debug Console gets a nice dropdown the user can switch between to see the output for both sessions.
This approach has the caveat where VS Code doesn't seem to have an API to remove an old session with a different name from the dropdown.
Specifically, if we do a debugging run of all tests in a XCTest+Swift Testing project this creates two sessions with, for instance, the names "XCTest" and "Swift Testing". However if then we run a single XCTest the "XCTest" debug session is updated but the old "Swift Testing" session sticks around in the dropdown with the output from the last run.
Issue: #902

@swift-server-bot test this please


Make package name required for "link"

When you don't pass a package name to the "react-native link", it will try to look for all packages to link from your node_modules.
This is causing us a lot of issues, such as linking wrong packages or the ones that someone doesn't want to link (e.g. decided to use a different way of linking that is out of scope for this command).
We should simply stick to requiring package name.

I would like to be able to link my assets to iOS and Android projects.
I can do it with RN 0.57.8, but I cannot with RN 0.59.x

Yup. We plan to introduce a new command or flag that will link only project assets. For now, you should be able to link project assets with yarn link, but it is deprecated.

thanks @Esemesek

currently it's not possible to link root assets with RN 59 rc2.
I've changed () => linkAssets(platforms, project, assets) to  () => linkAssets(platforms, project, { assets }), in linkAll
and it worked, but I'm not sure if it's proper fix.

@sijad This is a bug. linkAll should link root assets. I'll fix that in a minute.

I use it to link my font assets

@kennetpostigo in the future there will be a separate command to link project assets.

I think that when "react-native link" is entered, it must ask if the user really wants to link all libraries. This way, it will be better for the people who installed more than one library and wants to link all of them, or if the user is new to React Native, this will be easier for him/her.

We have react-native link setup in our PostInstall script so that when we update our dependencies any changes to the linking instructions get applied correctly.
We do not have Cocoapods, so we don't want there to be dependencies that are partially linked.
If the API changes so we have to enumerate all the packages we want linked, then what I would do is figure out the list of packages, and then make our post install script iterate over every entry in that array to link them one at a time. -- This is a minor annoyance, but no big deal.

I use for custom fonts!

I use postlink hooks in a couple of "helper" packages (e.g. react-native-pod) to update native considerations based on the current state of the app directory (e.g. after modifying app-level package.json). This allows for dry code and a lot of leverage from link. Will there be hooks to allow other packages to listen for per-package link events, like a postotherlink (with a better name)?
Or is this a PR/Issue that should be discussed under separate cover?

@rhdeck please create a new issue as it's not related to this one :)

I use it when making quick poc or tests. For this kind of situation there's never that much of trouble. And it's quite convenient.
Maybe making it optional with a warning?
That's not too much of a hassle to type it whith every package name anyway. So no big deal.

i use it to add dependencies after npm install react-native-webview

if you add several dependencies at once and just want to link them all or update, it is much easier to use react-native link without package name. The command has the option to use a package-name if this is not want you want, so why deprecating or removing the other option?

Like mentioned before, fonts.

I definitely only ever use 'react-native link' as my one and only go-to command to make sure that all my dependencies are linked. If you want to link a specific package, you already can. Maybe a new setting in the CLI could be added to lock this functionality from people who are worried about doing it accidentally; something like 'react-native set strict-link' perhaps, or maybe a command for unlocking it instead.
P.S. Why encourage non-standard methods of linking anyway? Why not double down on your standard, or expand functionality to fit the shortcomings people needed in these other linking methods then?

I think the package name should be required. I have some packages linked with the cli and some through CocoaPods, and I don't want to mess up and accidentally link a dependency with the cli if I've already got it as a pod in my Podfile. Then again I guess I could run react-native link --platforms=android
Then maybe have a react-native link assets command so we could link fonts

I use just to link my custom fonts, as mentioned before

Maybe having a react-native link assets command so we could link fonts would be good?

And what will happen when one installs a package named "assets"? boom

Maybe let link without arguments link assets by default, and simply stop linking all other things. That seems most sensual to me
Met vriendelijke groet / Kind regards,
Roberto Wesley Overdijk
SpoonX
Founder
M. +31 (0)6 15 55 32 43
W. www.spoonx.nl
E<EMAIL_ADDRESS>KvK. 60422696
On 26 Mar 2019, 19:36 +0100, Vidran Abdovich<EMAIL_ADDRESS>wrote:

Maybe having a react-native link assets command so we could link fonts would be good?
And what will happen when one installs a package named "assets"? boom
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sensible*... Phones.
Met vriendelijke groet / Kind regards,
Roberto Wesley Overdijk
SpoonX
Founder
M. +31 (0)6 15 55 32 43
W. www.spoonx.nl
E<EMAIL_ADDRESS>KvK. 60422696
On 26 Mar 2019, 19:36 +0100, Vidran Abdovich<EMAIL_ADDRESS>wrote:

Maybe having a react-native link assets command so we could link fonts would be good?
And what will happen when one installs a package named "assets"? boom
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

If you look closely into the PR (https://github.com/react-native-community/react-native-cli/pull/101) it already introduces link-assets command.

@vandervidi it was just an example. I agree that link-assets is better.

I did link all because I needed to reset my project since I'm upgrading from a somewhat old version.

agree with @sm1th
link-assets is a better option

It shouldn't be deprecated. The current commands are better. Those who want to to link any specific packages can link individually, while others could do it all at once with a single command.

Why to deprecate? We have the option if someone want to link particular package then he/she can do that also.
If you have 30 libraries and you want to link them all in one go then you can do it with react-native link and if you want specific then you can do that also, then what is the need of removal?????
For Assets i feel there should be option, if someone only want to link assets.

We decided not to introduce this change because the link command will be deprecated soon in favor of autolinking feature. Right now we are working on it, and it should be available in 0.60.0.

I use it because some things need to be linked but I never really know what

When you have a react native project and have to migrate to a new installation one run react-native link to link all dependencies, imagine if you have to linked them all manually, or when you want to copy bunch of package from an old package.json to a new package.json and some of them need to be linked, react-native link is a great tool

for a most of my new react native project i add a bunch of dependency which is some of that require to linking after that i just one time use react native link and it resolve all native issues.
expect that we linking are custom font with react native link. how can be link custom font with package name ??

如果移除了，那么 react-native-template 项目怎么办

@Esemesek what's the path moving forward for autolinking?
I'm having linking issues with local fonts, could be a race condition in 0.59.8.
I get a lot of, changes font file names listed on every run
debug Error: EBUSY: resource busy or locked, unlink

cc @grabbou ^

I double checked, 0.59.X and higher give me race conditions when linking on Windows.
0.58.X has the pathing bug on windows that causes Windows paths (\) to be linked.

@skhameneh whole you're investigating that, would you mind sending a PR with a fix? We don't use Windows for development unfortunately and that would much appreciated

@thymikee I don't have a fix at the moment.
I found killing adb.exe releases some of the file locks on my fonts.
Here's some extra info for possible repro:
$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.3-5475833

$ react-native --version
react-native-cli: 2.0.1
react-native: 0.59.8

react-native link doesn't link fonts for now.
react-native: 0.59.8

@justynasowinska can you share a minimal repro so we can investigate what's the issue?

i am trying to use this to link fonts. but unfortunate its not working as posted 2 days ago. need alternative. :(

Used this because of example on this page: https://www.npmjs.com/package/react-native-fetch-blob

I use this command to link my fonts.
Everything else I link manually.

I created a new project with updated react-native version and at once I added all of the project dependencies. in this case, react-native link command were useful.

I use it to link custom fonts

I use it to link custom fonts

I use link if I forgot about the package name, and to linking fonts and my custom styles.

Thanks for all the input, it's really valuable. As @Esemesek already noted here, we're not gonna introduce this change.
Since React Native 0.60, we hope the need for react-native link will massively drop because of the autolinking feature, which we hope you'll love. However, we don't deprecate it just yet. In fact, we're changing the default behavior to only link assets, as this is what majority of us use the link command without package name for. If for any reason you'd like to link all assets and native modules, the --all flag was introduced to facilitate that.
So to recap:

react-native link -> will link only assets since RN 0.60
react-native link --all -> will work exactly the same as react-native link befre RN 0.60


ProcessKiller killed wrong process

In one case, I had this
$ lsof -i:80 -P
COMMAND     PID           USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
com.docke   910 kazuakiurayama   91u  IPv6 0xbff554d0cffbd48b      0t0  TCP *:80 (LISTEN)
katalon   12497 kazuakiurayama  147u  IPv6 0xbff554d0cffbab4b      0t0  TCP <IP_ADDRESS>:58990->server-18-65-100-111.kix50.r.cloudfront.net:80 (ESTABLISHED)

ProcessKiller.killProcessOn(80) killed the process 12497, which was wrong.
It should select the process 910, which has "*:80 (LISTEN)"

ProcessKiller invoked in Katalon Studio GUI killed the process of Katalon Studio itself!
The code has been changed to avoid this risk.


JEST: Improve Jest Support

Problem
The user describes it well in the issue:

Currently trying to migrate to the library engine for an existing project (>1kloc prisma schema). After enabling the nApi flag, I've noticed that Jest will periodically crash while running test suites serially (hundreds of tests spread across almost 30 test suites).
After taking a closer look using jest's --logHeapUsage flag, I've found that memory usage goes up by 100MB+ per test suite. About thirds into a test run, jest would be eating up over 2GB of memory and crash soon after.

Goal
Any steps we can do to improve the memory usage would be helpful for our community.
If we can't fully solve the issue, let's approach this incrementally: allow community to first run 500 tests serially, check-in with the community, then we'll consider 1000 and so on as we learn people are still having problems.
Next Steps

[x] #12370

Issues
This issue collects issues related to Jest support with Prisma that might be related or closable after we resolve the problem described above.
Memory

[x] #8989
[x] https://github.com/prisma/prisma/pull/12242
[x] https://github.com/prisma/prisma/pull/11762
[x] https://github.com/prisma/prisma/pull/11751

Flakiness

[x] https://github.com/prisma/prisma/issues/8214

Mocking

[ ] https://github.com/prisma/prisma/issues/7424

Internal Usage of Jest

[ ] https://github.com/prisma/prisma/issues/7618

@millsp mentioned that we might need to do a breaking change for the WASM module integration to continue supporting something like Prisma.dmmf.
We'll need to decide if this is worth maintaining until P4 or it's okay to break earlier.

Related upstream issue: https://github.com/facebook/jest/issues/11956

Commenting here as I think there's more issues related to this.
The problem
This is my understanding of the problem, I'd love to be corrected if I've got it wrong!

There's maybe a memory leak between Prisma Client and Prisma Engine when creating many instances of Prisma Client.

In a testing environment you'll often create many Prisma Client instances which makes leaks more obvious.
There's maybe some issues in Jest that exacerbate leaks in Prisma. And potentially some recent changes in Node that also make the problem more obvious.

Does the above sound correct?
Related issues
There are a lot of open issues related to this problem. As well as the issues listed above, I found the following:

Jest spawns quite a many binaries
Slow Tests
OOM: Out of memory with library engine with Node.js v16 in test suite
Node-API/LibraryEngine: $disconnect does not free up memory / kill engine
Prisma memory leaks on Multitenant applications
Add $destroy to the client so it cannot be reused

Maybe also https://github.com/prisma/prisma/issues/12152 would help to lock down instances of this problem.
Workarounds
When it comes to Jest, the only workaround so far is to run less tests.
It'd be amazing if something like #12153 could be implemented as part of this work. As the memory problem seems to be affecting a lot of people and doesn't have a clear fix or workaround yet.

@m-allanson Thanks for summarizing the situation. Really appreciated.
We have the same heap problem when running jest with Prisma on Github Actions.

There's a workaround for this using jest@28's new test sharding feature. Each test shard is a new process, so you can divide your tests into as many shards as you need to avoid running out of memory.
As a demo I forked @aqrln's leak example to use sharding: https://github.com/m-allanson/prisma-leak-repro/commit/6e5e27348869659c8a089cadd6944ae6c27e68d3.
If your tests are running on GitHub Actions, you can also use their matrix feature to run the shards in parallel.

The new prisma@4 works much better with Jest. Here's two runs based on @aqrln's prisma-leak-repro. One using Prisma v4, and one using v3.

However, you might notice that the heap still grows without being freed, this means we still have work to do :)

Our team is running into a memory leak issue when running a large number of tests with jest which eventually leads to a heap error.
When we take a heap snapshot of early in the test run and late in the test run, we find that Code and Strings grow disproportionately larger relative to the other segments.
Early in the run:

Late in the run:

If I sort by shallow size descending and expand the strings segment, we find that the Prisma source is near the top and repeated many times:

We find the same if we expand compiled code (note the repeated shallow sizes of 257 312):

So while we can't positively say Prisma is the reason for our memory leak and eventual crash, it does seem to be the dominator in the segments that grew disproportionately. We use Prisma 4.5.0 - happy to share more information if it would be helpful!

@dwayneyuen Random idea to try:
Maybe add the following and see if anything changes?
async onModuleDestroy() {
  await this.$disconnect();
}

@dwayneyuen Can you please also split this out into a new bug report issue? Thanks.

Damn, this was a good idea but it didn't seem to change anything.

@dwayneyuen Can you please also split this out into a new bug report issue? Thanks.

Filed here! https://github.com/prisma/prisma/issues/17171 - apologies. Thanks!

I am closing this issue now as the original linked issues have been closed for a while now.
There are still some memory problems, also and especially when using with Jest. We have issues tracking them:

label topic: performance/memory
label topic: memory leak
label topic: jest

If you still have problems with Prisma and Jest, please see if an appropriate issues for that already exists under these labels - or create a new one an we'll figure it out. Thank you!


Add order of preference into Build vs Buy

Adopt *
Adopt and Build ***
Adopt and Buy **
Adopt, Buy and Build
Buy
Buy and Build
Build

Should also emphasize need to measure and track the compliance with this order of preference
Add proposal to mention (Ex: adopt should increase, buy should decrease). Linked to https://github.com/sara-sabr/ITStrategy/issues/1137

Order of preference when: Core to mandate and Complex
We do want to minimize the amount of custom maintenance internally but we also want to increase our ability to push changes upstream of the core version (OSS allows for this whereas changing features in a COTS is unlikely)

@gcharest Does this still apply, or is it taken care of by the measurement section (https://github.com/sara-sabr/ITStrategy/issues/1130) ?


Security Recommendation: vWan Storage - Allow Blob anonymous access

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
I got a security warning, that "Allow Blob anonymous access" should be disabled for a storage account. This storage account got created from the vWan in the landing zone deployment. I tried to see if I can set this property in the landing zone but it does not seem to be the case. Does vwan need this anonymous access? Or can it be disabled? If yes how?
Is your feature request related to a problem?

Describe the solution you'd like
Probably it would just be good to specify in the documentation how to set this property.
Additional context
Documentation

Hi @steph409,
This module doesn't create any storage accounts, only assigns policies to apply certain constraints to a storage account etc. as per aka.ms/alz/policies
Is it this module, or is it another?


CFE-3903: Groups promise type now supports custom bodies

Depends on: https://github.com/cfengine/core/pull/4884

[x] test on 3.18.x
[x] test on master

Tested:

[x] 3.18.x
[x] 3.20.x

I will create a PR to update the commit sha in the index