[Doc Improvement][Update TTK User Manual for Unify Config]

This PR updates several doc pages for a change from Teams Toolkit that:

Merge manifest.local.template.json and manifest.remote.template.json into manifest.template.json.
Update localSettings.json to config.local.json.

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
94
2
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
94
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
94
2
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
94
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

Docs Build status updates of commit 69ad3d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
94
2
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
94
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
94
2
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
94
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
94
2
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
86
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
86
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
29
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
92
7
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
91
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
92
28
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

Docs Build status updates of commit 909e9b4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
91
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
92
28
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 547b334:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
91
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
92
28
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
91
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
92
28
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
91
3
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
93
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
92
28
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 813bb71:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md

Line 176, Column 3: [Warning: code-block-unclosed - See documentation] Unclosed code block. Code blocks must begin and end with triple backticks (```).

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
90
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
92
5
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
23
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

Docs Build status updates of commit 585a9c6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md

Line 176, Column 3: [Warning: code-block-unclosed - See documentation] Unclosed code block. Code blocks must begin and end with triple backticks (```).

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
90
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
92
5
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
23
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
95
4
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
90
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
91
6
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
90
26
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
94
5
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
82
25
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

Docs Build status updates of commit 8cb1efa:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/TeamsFx-multi-env.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md

Line 199, Column 3: [Warning: code-block-unclosed - See documentation] Unclosed code block. Code blocks must begin and end with triple backticks (```).

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
90
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
91
6
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
30
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
94
5
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
86
18
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

Docs Build status updates of commit 38adeee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.vscode/settings.json
:white_check_mark:Succeeded

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/TeamsFx-manifest-customization.md
90
4
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-manifest-preview.md
92
5
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-multi-env.md
91
30
link
:white_check_mark:

msteams-platform/toolkit/add-capability.md
94
5
link
:white_check_mark:

msteams-platform/toolkit/debug-background-process.md
86
18
link
:white_check_mark:

msteams-platform/toolkit/debug-local.md
93
12
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

.vscode/settings.json
:white_check_mark:Succeeded

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-customization.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-manifest-preview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-multi-env.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-capability.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-background-process.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/debug-local.md
:white_check_mark:Succeeded
View

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


Update Android Gradle plugin to 3.6.2

Android Studio 3.6.2 is now available:
https://androidstudio.googleblog.com/2020/03/android-studio-362-available.html

Thanks @friederbluemle!  Looks like with this change, though, the project can't be opened in Android Studio 3.5. My preference would be to wait and let Android Studio 3.6 settle a bit before committing to it - especially because there seems to be a regression that breaks Git push again:
https://issuetracker.google.com/issues/124680708#comment15

Thanks for your comment @barbeau - Makes sense. I don't personally do Git push operations from the IDE, but the issue you mentioned apparently has been fixed in 3.6.1:
https://androidstudio.googleblog.com/2020/02/android-studio-361-available.html
I'll keep this branch rebased until you feel comfortable to merge it.

Rebased and updated to 3.6.2.

Thanks @friederbluemle! I'm going to close and re-open this to try and nudge Travis into reporting the status...

Thanks @barbeau - Looks like the build on Travis CI got kicked off and was successful: https://travis-ci.org/github/googlemaps/android-maps-utils/builds/670187100
So webhooks are set up:

But the status did not get reported back: Expected — Waiting for status to be reported.
Maybe Travis needs to be re-authenticated?
I'll try to git commit --amend --no-edit and force push to give it another shot.

@friederbluemle Yeah, I'm not sure what's going on - GitHub just doesn't seem to be getting the reported result from Travis. I'm seeing this on other newer PRs too - for example, https://github.com/googlemaps/android-maps-utils/pull/679.


Add callable workflow for only building the server image

Create a workflow which can be called by other repos to just build a docker image of server, so that they can use it for testing a certain commit, etc, without needing a published image.
Draft while working through using it from the server repo w/ sdk-features.

This is now working as used by https://github.com/temporalio/temporal/pull/3627


API rate limit exceeded for

Problem:
API limit hit for all contributors
yarn all-contributors check
yarn run v1.7.0
$ /code/codewatch/node_modules/.bin/all-contributors check
API rate limit exceeded for xxx.xx.xx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Solution i'd like to see:
A way to provide a github auth token to avoid API limits.
Additional information:
See the github docs: https://developer.github.com/v3/rate_limit/

I've realized this a problem with the CLI tool and have created an issue there https://github.com/jfmengels/all-contributors-cli/issues/121


Endpoint /api/customization/{idCustom} [PUT] [Required for UI screen List of instances]

Description
Values

Description:
Endpoint to update the information associated to a customization

Screen that needs the endpoint:
List of instances

Endpoint required:
/api/customization/{idCustom}

Call Type:
PUT

Data Type:
application/json

Parameters:
Check schema

Schema:
{
  "status" : ["Stopped", "Deploied"]
}

NOTE: The change of the status will trigger the process to do what the stuts states.

Done, please test
CustomizationResource#update


Issue: POST request generate SQL or XML

There is an issue when trying to make a POST request with either "SQL" or "XML".
Tried various combinations of query parameters without success.
Raised issues with the community: https://forum.mockaroo.com/t/issue-mockaroo-api-post-generate-format-sql-and-xml/7547?u=scarvy

XML works now (2023-10-18), but SQL still not working

SQL working now
>>> from mockaroo import Client
>>> client = Client()
>>> client.api_key
'dacfc870'
>>> client.generate(schema="Person", fmt="sql", table_name="person", count=1)
b"insert into MOCK_DATA (id, first_name, last_name) values (1, 'Cherlyn', 'Bytheway');\n"
>>>


feat: demo wallet (#1585)

Description

revert of the revert as this branch still has issues
see original issue describing feature https://github.com/shapeshift/web/issues/1621
see issues identified in production https://github.com/shapeshift/web/issues/1697
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes https://github.com/shapeshift/web/issues/1621
Risk

Moderate: Given that we are touching a number of existing features/functionality, there is always a risk of some kind of regression. I believe the previous issues that were raised in #1697 have been addressed, but the rest of the changes in this PR are fairly well isolated, in that they don't interfere with events in any way, and are more confined by the feature flag (at least from the perspective of being able to disable once in prod).
Testing

From the original PR

There should be no regression in existing behaviour, either when a wallet is connected, or when in "Demo Mode".
When in "Demo Mode", the app should be as usable as possible without the need to connect a wallet. The user should be able to progress with functionality, such as making a trade or staking an asset, but only to the point where an "actual" wallet is required. At this point, they should be prompted to "Connect A Wallet".

Additional testing steps based on previous regression.
The below should work for both a normal connected wallet as well as the demo wallet:

Cosmos staking
Cosmos unstaking
Cosmos claim
Trade confirm
Smart contract approval

Screenshots (if applicable)

thanks @0xf11nix! and thanks @gomesalexandre for the thorough testing. i'm "approving" this and merging without a green tick as i opened the PR and can't approve my own, but it's obvious this fixes the issues.


Fix a conv3d dgrad type issue

This PR is to fix a conv3d dgrad type issue.
Before this PR, we use the context->input(0).dtype() to infer the dtype of the dgrad conv (mainly for creating the param key for autotuning). This is fine for the Conv3DBackpropInput, which has Input("input: T") as input(0). However, for the Conv3DBackpropInputV2, the input(0) turns to be Input("input_sizes: Tshape"). So, to fix this, we use context->input(2).dtype(), which is Input("out_backprop: T") and is shared by Conv3DBackpropInput and Conv3DBackpropInputV2.
fyi @nluehr

Not sure if there is a simple way to add a test for this. But I think the bug is clear and only affect the perf (I guess that is why it was not captured before).
Basically, this bug affects the autotuning process of conv3d dgrad. If we check nn_ops.cc, we can see that:
REGISTER_OP("Conv3DBackpropInput")
    .Input("input: T")
    .Input("filter: T")
    .Input("out_backprop: T")
    .Output("output: T")
    .Attr("T: {half, float, double}")
    .Attr("strides: list(int) >= 5")
    .Attr(GetPaddingAttrString())
    .Deprecated(10, "Use Conv3DBackpropInputV2")
    .Attr("dilations: list(int) = [1, 1, 1, 1, 1]")
    .SetShapeFn([](InferenceContext* c) {
      return UnchangedShapeWithRank(c, 5);
    });
...
REGISTER_OP("Conv3DBackpropInputV2")
    .Input("input_sizes: Tshape")
    .Input("filter: T")
    .Input("out_backprop: T")
    .Output("output: T")
    .Attr("T: {half, bfloat16, float, double}")
    .Attr("strides: list(int) >= 5")
    .Attr(GetPaddingAttrString())
    .Attr(GetConvnet3dDataFormatAttrString())
    .Attr("dilations: list(int) = [1, 1, 1, 1, 1]")
    .Attr("Tshape: {int32, int64} = DT_INT32")
    .SetShapeFn([](InferenceContext* c) {
      ShapeHandle s;
      TF_RETURN_IF_ERROR(c->MakeShapeFromShapeTensor(0, &s));
      TF_RETURN_IF_ERROR(c->WithRank(s, 5, &s));
      c->set_output(0, s);
      return Status::OK();
    });

For V2, the input(0) no longer means the input itself but just its shape and therefore the input(0).T is no longer input type T but Tshape which is int32/int64. This will map the conv3d dgrad nodes with different Ts to the same cached algorithm. Any suggestion? @sanjoy


Use ISO 8601 date format everywhere.

While dates are in general displayed as ISO 8601, the date-and-time fields in the form to create or edit a silence have some other format (depending on locale settings of the browser?). ISO 8601 format should be used consistently.

See linked other issues for more places to fix.

https://twitter.com/chrisoldwood/status/799015051990437890

@beorn7 I am closing here. This is fixed with the new UI. Please reopen if I am missing anything.


koord-scheduler: make sure NodeInfo and other objects have synced before scheduling

Ⅰ. Describe what this PR does
When the K8s Scheduler Framework starts, the thread that constructs NodeInfo and the scheduling thread are not synchronized. In this way, when the Pod on a Node is not filled in the NodeInfo, the Node is scheduled for a new Pod. This behavior is not expected. The K8s community itself has also noticed this issue #116717, but it was only fixed in the K8s v1.28 version #116729.
The PR force synced objects into cache.ResourceEventHandler  in AddEventHandler method.

Ⅱ. Does this pull request fix one issue?
fix #1544

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/lgtm


Using Boolean Placeholder for is_training Causes Problems when Loading on iOS

Currently I am training a model that uses Batch Normalization and Dropout. Because of this I build the model to take a placeholder, is_training, that I can feed_dict true or false depending on whether the graph is being used for training or validation.
I take the trained model and export using tensorflow.contrib.session_bundle.exporter however when I try to load this graph on iOS, I run into problems (see SO):
No OpKernel was registered to support Op 'Switch' with these attrs.

I have tried removing the placeholder and injecting the actual value of False for is_training (see SO and GH), however the model still does not load (see SO post):
Input 0 of node dropout6/cond/dropout/random_uniform/max was passed bool from dropout6/cond/Switch:1 incompatible with expected INVALID.

It seems like something is missing to clean up / recompile the graph, stripping out the training part of the graph because the inject does not seem like enough. This was one idea to solve the problem: https://github.com/tensorflow/tensorflow/issues/5919.
Right now, I can instead of using placeholder for is_training use constants and create the model twice, sharing weights, and then export just the validation subgraph and then load this into iOS, but the downside is that I need to instantiate the model twice into the graph.
EDIT: Would be nice to not have to resort to compiling iOS with switch: https://github.com/tensorflow/tensorflow/issues/2680#issuecomment-237483554 since that node shouldn't even be needed in the final graph. It would be nice to fully remove it from the saved graph.

I struggled a lot with this until I gave up and ended up freezing the model without is_training.

Sorry we weren't able to give you a better solution for this one! We do generally recommend having separate graphs for training and inference, though that isn't well documented. Closing this bug since it looks like you have a workaround? Let me know if we should reopen it.

Hey guys! I've been having the same problem trying to make this work on android and I have used some of the solutions from above but none seem to work...here are some of the errors I get back from the various methods of trying to solve this problem...Any Help would be appreciated!
The models work when I run it on python but doesn't when I run them on android.
Im using the SSD_Mobilenet model from tensorflow object detection api.
This is from the optimize for inference function:
NodeDef expected inputs '' do not match 1 inputs specified; Op<name=Const; signature= -> output:dtype; attr=value:tensor; attr=dtype:type>; NodeDef: Preprocessor/map/while/add/y = Constdtype=DT_INT32, value=Tensor<type: int32 shape: [] values: 1>
This is from renaming Switch to Identify:
Not a valid TensorFlow Graph serialization: Node 'Preprocessor/map/while/add/y': Connecting to invalid output 1 of source node Preprocessor/map/while/Switch which has 1 outputs
This last one loads the model but crashes when processing the inputs:
java.lang.IllegalArgumentException: No OpKernel was registered to support Op 'Switch' with these attrs. Registered devices: [CPU], Registered kernels:
device='GPU'; T in [DT_STRING]
device='GPU'; T in [DT_BOOL]
device='GPU'; T in [DT_INT32]
device='GPU'; T in [DT_FLOAT]
device='CPU'; T in [DT_FLOAT]
device='CPU'; T in [DT_INT32]
                                                          	 [[Node: Postprocessor/BatchMultiClassNonMaxSuppression/PadOrClipBoxList/cond/Switch = Switch[T=DT_BOOL](Postprocessor/BatchMultiClassNonMaxSuppression/PadOrClipBoxList/Greater, Postprocessor/BatchMultiClassNonMaxSuppression/PadOrClipBoxList/Greater)]]

Any ideas guys? I've also tried to recompile tensorflow with the changes from https://stackoverflow.com/questions/40855271/no-opkernel-was-registered-to-support-op-switch-with-these-attrs-on-ios/43627334#43627334 but bazel crashes while compiling :(

@ronny3050 could you share how to freeze the model is_training ?
thanks.

[https://gist.github.com/ronny3050/d3dc669601a5604b347365ed652645dd](This gist) can be used for freezing models. Do not include is_training in the list of whitelisted nodes.
You may have to change a couple of hardcorded node-names to fit your needs.
Hope it helps. :)

@ronny3050, thanks for your reply, this fixed my issue.

Just FYI, we can simply feed phase_train and keep_prob etc. along with input in Android and it fixes the issue.
tensorflow.feed("phase_train", new boolean[]{false});     tensorflow.feed("keep_prob", new float[]{1f});

@ronny3050 If you know can you please tell me, how to make phase_train option false if I have .pb(frozen model).

I wrote an example below to convert a tensorflow(v1.3) model with batchnorm to tflite. Hope it's helpful.
https://gist.github.com/iamyb/779a14c2da79c7d7fe5d7256e4d71ace


release python packages in artful

@clalancette FYI

[x] Add newly supported platforms to list of platforms for each Python package (in stdeb.cfg), in order of dependency (for ROS M, do this as soon as debs for new Ubuntu are available, in pre-alpha!):

[x] rospkg (uploaded, no need to rerelease): https://github.com/ros-infrastructure/rospkg/commit/9c17190a8ef8e4428ef58c4038efd86c0e404fa4
[x] catkin_pkg (uploaded, no need to rerelease): https://github.com/ros-infrastructure/catkin_pkg/commit/024ea337447aa5d0352437c5ed95c0bdb7c39186
[x] rosdistro (uploaded, no need to rerelease): https://github.com/ros-infrastructure/rosdistro/commit/bde376de0b508fae22f034a5a6fbe72980a92aa6
[x] rosdep (uploaded, no need to rerelease):  https://github.com/ros-infrastructure/rosdep/commit/b1de10cf9691371f2854fffb8d239fe6f1f37c2c
[x] vcstools (uploaded, no need to rerelease): https://github.com/vcstools/vcstools/commit/ada7e69273bee5138e40df29065d7aa6be663ab9
[x] wstool (uploaded, no need to rerelease): https://github.com/vcstools/wstool/commit/c793ad8b7408b3005edc7f7ef6f2b855442e766c
[x] rosinstall (uploaded, no need to rerelease): https://github.com/vcstools/rosinstall/commit/47d7f64370fbe99469cfbe0bb332cec500a0ef65
[x] bloom (uploaded, no need to rerelease):  https://github.com/ros-infrastructure/bloom/commit/eddcc3573f28da0fa058a5162c458e437d2c5d94
[x] rosinstall_generator (uploaded, no need to rerelease):  https://github.com/ros-infrastructure/rosinstall_generator/commit/577258363f1511f5d541e3faf98a751e0b9453ee
[x] catkin_tools (uploaded, no need to rerelease): https://github.com/catkin/catkin_tools/commit/ba65534e43ab5bab65d604bd6795901e59bce7d4
[x] vcstool (uploaded, no need to rerelease): https://github.com/dirk-thomas/vcstool/commit/438dc60e35ac8243d32f2913162514b381a19eb3

[x] Use ros_release_python to make the currently released versions available in the new distro. Use the --include option (done for all except vcstool)

The current releases are incomplete. E.g. python-rosdistro-modules is not in the apt repo for artful. I assume that the --include command doesn't consider the additional -modules packages atm.

I updated vcstool and ran --include for it.

I updated ros_buidlfarm (https://github.com/ros-infrastructure/ros_buildfarm/commit/ced64b5d636323f0dd9d111b02cd986c554ff9fe). I didn't run --include for it yet since it requires the same fix as the other missing packages.

I fixed the problem in ros-infrastructure/ros_release_python#19 and ran --include again for the Python packages with more than one section in their stdeb.cfg files.

While all our packages are now available (at least in repositories.ros.org) they are not being installed on artful since new Debian packages have been imported which have a debinc of 2 and therefore a higher version number than our packages. While in general it would be "ok" if they ship the same version their Debian packages are not side-by-side installable for Python 2 and Python 3 since they don't split out the modules from the conflicting binaries.

@jspricke FYI the problem in artful regarding the upstream Debian packages. Do you have a proposal how to address this? Maybe it would be best if the Debian packages are also being split in the same way to allow side-by-side installation.

I'm working on integrating Python 3 support for all packages that are
in Debian, but I cannot guarantee that this will be finished in time, as
they need to go through the Debian new queue (managed by Debian ftp
masters) and import freeze for Artful is on August 24th.
Cheers Jochen

What do you suggest as a fallback if they don't make it in?

Increase the Debian revision number on your side?

An other (probably better) option would be to integrate the Debian packages later.

Increasing the debinc would only work until updated also bumps the debinc. Therefore I don't think that is a long term solution.
With the need to be able to release changes in a timely manner I don't think using upstream is realistic in the near term future. The constraints for releasing new versions into Debian are sometimes too restrictive for the ROS community.
I guess we might have to bump the patch version of all packages affected. That will make sure to work at least until the upstream Debian packages catch up with that (hopefully only on the next Debian distro).

I would upload new patch versions to Debian, so you would gain nothing.

Then we need a sustainable way to ensure that the ROS packages are being used. Not sure what that would be other than maybe using debinc 100 for our packages...

Given that you are using random Debian increments already (https://github.com/ros-infrastructure/ros_buildfarm/pull/460) I think it would work as an interim solution.

The ros_buildfarm is only used for ROS packages. The Python packages are handled by a different release toolchain: https://github.com/ros-infrastructure/ros_release_python which is based on stdeb. I still have to check if stdeb allows us to specify a debinc - currently be only use the default.

Thank you for the feedback. The next releases of catkin_pkg, rosdistro, rospkg, and ros_buildfarm will use a debinc of 100 for the non-modules packages.

ros_buildfarm is not in Debian and catkin_pkg just git accepted, so you
can leave both of them out.


[FHIR] Use app.kubernetes.io-scoped labels

This replaces the previous labels with common/recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels

I find it a little odd that the kubernetes docs say these are the recommended labels but then their own documentation for labels/selects still uses the simpler unprefixed "app" label.
I do like the new helper for the the common label annotations.

I didn't realize it at the time, but this is a backwards-breaking change.  If you try upgrading an existing install you will get something like this :

Error: UPGRADE FAILED: cannot patch "ibm-fhir-server" with kind Deployment: Deployment.apps "ibm-fhir-server" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/component":"server", "app.kubernetes.io/instance":"ibm-fhir-server", "app.kubernetes.io/name":"ibm-fhir-server"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

Hm, I wasn't sure at the time either to be honest. I assumed chart testing's upgrade test would catch this: https://github.com/Alvearie/alvearie-helm/runs/3723826708?check_suite_focus=true#step:7:30
And

If upgrade (--upgrade) is true, then this command will validate that 'helm test' passes for the following upgrade paths:

previous chart revision => current chart version (if non-breaking SemVer change)
current chart version => current chart version

https://github.com/helm/chart-testing/blob/main/doc/ct_install.md
I'll have to double check why it didn't get caught 🤔


Suspended user status styling

Issue Summary
The status 'Suspended' for a user needs some CSS tweaks else it is squashed up against the user's name
https://puu.sh/wdsk3/99224b0d6b.png
Steps to Reproduce
Add a new user
Suspend User
View User Profile
Technical details:

Ghost Version: 1.0.0-alpha.21
Browser/OS: Chrome

closed via https://github.com/TryGhost/Ghost-Admin/commit/521748bf9cf90c54b911b11cc73cb0d89f0948ad


Improve the pod health checks to monitor cluster status

What steps will reproduce the bug?
If a node disconnects from a nifi cluster, it'll stay disconnected until I manually delete the pod. I get this error regularly:
Action cannot be performed because there is currently no Cluster Coordinator elected. The request should be tried again after a moment, after a Cluster Coordinator has been automatically elected.
What is the expected behavior?
The pod should be restarted to rejoin the cluster
What do you see instead?
Disconnected nodes that don't recover
Possible solution
Change the pod readiness check to hit /nifi-api/flow/cluster/summary?
NiFiKop version
v0.14.0-release
Golang version
1.19
Kubernetes version
v1.23.6-rke2r2
NiFi version
1.16.0
Additional context
No response

How does the /nifi-api/flow/cluster/summary endpoint respond for standalone clusters?

How does the /nifi-api/flow/cluster/summary endpoint respond for standalone nodes?

I hadn't thought of that! The above endpoint isn't available to standalone clusters - so maybe an if statement here that uses the above URI if it's clustered, or leaves it as-is if not?

That sounds reasonable!

I've opened #219 as i believe that's a more general solution that can be tailored to specific use cases.


Phaser rederer remove pixi anims textures

I suggest you enable hiding whitespaces when reviewing this one, especially for IgeEntity:

Testing with @Grenagar 's game and it feels like the animation for the rocket projectile hangs for a while on its last frame before being removed. Confirmed this when comparing to phaser-renderer

i think its game problem, same should be on master


Doesn't respect .eslintrc.json max-length

Lines above 80 characters are wrapped even if there's a max-len rule under "rules" in .estlintrc:
"max-len": [ "error", { "code": 200 } ],
Plugin debug output gives:
[2021-03-30T11:21:14.163] [DEBUG] format-imports.formatSource - composeConfig: {
maxLength: 80,  <========== There it is :)
wrap: {
withoutDefault:<PHONE_NUMBER>740991,
withDefault:<PHONE_NUMBER>740991,
perLine:<PHONE_NUMBER>740991,
exported:<PHONE_NUMBER>740991,
parts: true
},
Other than that, it seems like a fantastic plugin! And since I'm writing, please add something like "if number of imports are less than 4 then don't apply emptyLinesBetweenGroups".
/T

@tomnil - Thanks for the feedback!
This plugin doesn't check max-len from ESLint right now. Instead it gets max line length from:

VSCode settings
Prettier
EditorConfig
import-sorter.json
package.json.

But I'll check if ESLint max-len can be added to the list and come back later.

@tomnil - After some study on ESLint max-len rule, I've come up with a proposal.
The plugin will check ESLint max-len rule, and handle its options as follows:

If code is set, merge it to maxLineLength.

Currently, the merge algorithm is "the last wins". I'm considering instead "the minimum wins", as it satisfies all limitations (e.g. from both Prettier and ESLint).

If tabWidth is set, merge it to tabSize (The last wins).
If either ignoreTrailingComments or ignoreComments is true, the plugin will ignore comments when counting line length.
Other options are ignored by the plugin.

Discussion:

If ignoreStrings is set to true, ESLint will ignore all imports because they all have a path string. Should the plugin ignore the rule?
A: No. The plugin also formats exports so the rule still applies.

The rule can specify ignorePattern which can skip some or all imports/exports. Should the plugin be aware of that and adjust accordingly?
A: No. That'd significantly increase the complexity with confusions and few value.

Please tell me your thoughts.
Thanks!

@tomnil - I've released v7.3.0 to address this issue (and a few others). Please check it out and tell me if there are more issues.
Thanks!

I have this ("printWidth": 120,) in my .prettierrc and the extension is considering 80

More links:
https://stackoverflow.com/questions/60718493/difference-between-codeactionsonsave-and-formatonsave-in-vs-code
https://github.com/microsoft/vscode-docs/blob/main/release-notes/v1_41.md#eslint

Thank you for your hard work. It's still defaulting to 80. Me personally I would be pefectly fine with a setting like tsImportSorter.configuration.wrappingStyle: { maxLength: 180 }.
If you want better debugging, I suggest you add a console.log when the maxLength is parsed and decided (eg, "Setting maxLength to 80. Source is xxxx").
[2021-04-09T12:12:44.211] [DEBUG] format-imports.formatSource - ESLint config processed: undefined
[2021-04-09T12:12:44.211] [DEBUG] format-imports.formatSource - composeConfig: {
maxLength: 80,
wrap: {
withoutDefault:<PHONE_NUMBER>740991,
withDefault:<PHONE_NUMBER>740991,
perLine:<PHONE_NUMBER>740991,
exported:<PHONE_NUMBER>740991,
parts: true,
skipCmt: false
},
groupSep: '\r\n\r\n',
groupEnd: 2,
tab: '  ',
tabw: 2,
quote: [Function],
comma: ',',
semi: ';',
bracket: [Function],
lastNewLine: false,
nl: '\r\n'
}
[2021-04-09T12:12:44.280] [DEBUG] format-imports.formatSource - isModule: true
[2021-04-09T12:12:44.280] [INFO] vscode.formatDocument - Finished format
/T

@tomnil - could you share complete logs of a formatting action? There should be configs from, eg vscode, prettier, eslint, etc.
Thanks!

Debug output
[2021-04-13T12:30:21.150] [DEBUG] vscode.formatDocument - Triggered from: codeAction
[2021-04-13T12:30:21.150] [INFO] vscode.resolveConfig - Resolving config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx languageId: typescriptreact
[2021-04-13T12:30:21.150] [DEBUG] vscode.loadVscConfig - Loading VSCode config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.151] [DEBUG] vscode.resolveConfig - Loaded VSCode config
[2021-04-13T12:30:21.151] [DEBUG] format-imports.loadPretConfig - Loading Prettier/EditorConfig config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.151] [INFO] format-imports.loadPretConfig - Prettier API version: 2.2.1
[2021-04-13T12:30:21.157] [DEBUG] format-imports.loadPretConfig - Prettier config: {
  useTabs: false,
  tabWidth: 2,
  arrowParens: 'always',
  printWidth: 120,
  singleQuote: true,
  trailingComma: 'all',
  semi: false
}
[2021-04-13T12:30:21.158] [DEBUG] format-imports.fileConfig - Loading JSON config from import-sorter.json
[2021-04-13T12:30:21.158] [DEBUG] format-imports.fileConfig - Found JSON config file undefined
[2021-04-13T12:30:21.158] [DEBUG] format-imports.packageConfig - Loading package.json config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.159] [DEBUG] format-imports.packageConfig - Found package.json in c:\Projects\test\client\package.json
[2021-04-13T12:30:21.159] [DEBUG] format-imports.packageConfig - Package.json config: undefined
[2021-04-13T12:30:21.159] [DEBUG] format-imports.enhanceEol - Determining EOL
[2021-04-13T12:30:21.159] [INFO] format-imports.formatSourceFromFile - Formatting fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx with config: {
  configurationFileName: 'import-sorter.json',
  autoFormat: 'off',
  formatExports: true,
  exclude: [ 'node_modules' ],
  excludeGlob: [],
  sortImportsBy: 'paths',
  groupRules: [ '^react(-dom)?$', '^@angular/', '^vue$', {}, '^[@]', '^[.]' ],
  sortRules: { paths: [ '_', 'aA' ], names: [ '_', 'aA' ] },
  keepUnused: [],
  emptyLinesBetweenGroups: 1,
  emptyLinesAfterAllImports: 1,
  removeLastSlashInPath: false,
  removeLastIndexInPath: false,
  wrappingStyle: {
    maxBindingNamesPerLine: 1,
    maxDefaultAndBindingNamesPerLine: 2,
    maxExportNamesPerLine: 0,
    maxNamesPerWrappedLine: 1,
    ignoreComments: false
  },
  development: { enableDebug: true },
  insertFinalNewline: true,
  eof: '\n',
  eol: 'LF',
  force: false,
  maxLineLength: 120,
  tabType: 'space',
  tabSize: 2,
  hasSemicolon: false,
  quoteMark: 'single',
  trailingComma: 'multiLine',
  bracketSpacing: true
}
[2021-04-13T12:30:21.159] [DEBUG] format-imports.loadTsConfig - Finding TS config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.160] [DEBUG] format-imports.loadTsConfig - Loading TS config from: c:/BrunoLM/Projects/ae/ae-skills/client/tsconfig.json
[2021-04-13T12:30:21.161] [DEBUG] format-imports.loadTsConfig - Parsing TS config for path: c:/BrunoLM/Projects/ae/ae-skills/client
[2021-04-13T12:30:21.174] [DEBUG] format-imports.loadESLintConfig - Loading ESLint config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx from default
[2021-04-13T12:30:21.174] [INFO] format-imports.loadESLintConfig - ESLint API version: 7.21.0
[2021-04-13T12:30:21.184] [DEBUG] format-imports.formatSource - Enhanced config: {
  configurationFileName: 'import-sorter.json',
  autoFormat: 'off',
  formatExports: true,
  exclude: [ 'node_modules' ],
  excludeGlob: [],
  sortImportsBy: 'paths',
  groupRules: [ '^react(-dom)?$', '^@angular/', '^vue$', {}, '^[@]', '^[.]' ],
  sortRules: { paths: [ '_', 'aA' ], names: [ '_', 'aA' ] },
  keepUnused: [],
  emptyLinesBetweenGroups: 1,
  emptyLinesAfterAllImports: 1,
  removeLastSlashInPath: false,
  removeLastIndexInPath: false,
  wrappingStyle: {
    maxBindingNamesPerLine: 1,
    maxDefaultAndBindingNamesPerLine: 2,
    maxExportNamesPerLine: 0,
    maxNamesPerWrappedLine: 1,
    ignoreComments: false
  },
  development: { enableDebug: true },
  insertFinalNewline: true,
  eof: '\n',
  eol: 'LF',
  force: false,
  maxLineLength: 120,
  tabType: 'space',
  tabSize: 2,
  hasSemicolon: false,
  quoteMark: 'single',
  trailingComma: 'multiLine',
  bracketSpacing: true
}
[2021-04-13T12:30:21.184] [DEBUG] format-imports.formatSource - tsCompilerOptions: {
  target: 1,
  lib: [ 'lib.dom.d.ts', 'lib.dom.iterable.d.ts', 'lib.esnext.d.ts' ],
  allowJs: true,
  skipLibCheck: true,
  esModuleInterop: true,
  allowSyntheticDefaultImports: true,
  strict: false,
  forceConsistentCasingInFileNames: true,
  noFallthroughCasesInSwitch: true,
  module: 99,
  moduleResolution: 2,
  resolveJsonModule: true,
  isolatedModules: true,
  noEmit: true,
  jsx: 4,
  configFilePath: undefined
}
[2021-04-13T12:30:21.184] [DEBUG] format-imports.formatSource - ESLint config processed: undefined
[2021-04-13T12:30:21.184] [DEBUG] format-imports.formatSource - composeConfig: {
  maxLength: 120,
  wrap: {
    withoutDefault: 1,
    withDefault: 2,
    perLine: 1,
    exported:<PHONE_NUMBER>740991,
    parts: true,
    skipCmt: false
  },
  groupSep: '\n\n',
  groupEnd: 2,
  tab: '  ',
  tabw: 2,
  quote: [Function],
  comma: ',',
  semi: '',
  bracket: [Function],
  lastNewLine: true,
  nl: '\n'
}
[2021-04-13T12:30:21.222] [DEBUG] format-imports.formatSource - isModule: true
[2021-04-13T12:30:21.222] [INFO] vscode.formatDocument - Finished format
[2021-04-13T12:30:21.251] [DEBUG] vscode.formatDocument - Triggered from: onSave
[2021-04-13T12:30:21.252] [INFO] vscode.resolveConfig - Resolving config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx languageId: typescriptreact
[2021-04-13T12:30:21.252] [DEBUG] vscode.loadVscConfig - Loading VSCode config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.252] [DEBUG] vscode.resolveConfig - Loaded VSCode config
[2021-04-13T12:30:21.252] [DEBUG] format-imports.loadPretConfig - Loading Prettier/EditorConfig config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.252] [INFO] format-imports.loadPretConfig - Prettier API version: 2.2.1
[2021-04-13T12:30:21.260] [DEBUG] format-imports.loadPretConfig - Prettier config: {
  useTabs: false,
  tabWidth: 2,
  arrowParens: 'always',
  printWidth: 120,
  singleQuote: true,
  trailingComma: 'all',
  semi: false
}
[2021-04-13T12:30:21.260] [DEBUG] format-imports.fileConfig - Loading JSON config from import-sorter.json
[2021-04-13T12:30:21.261] [DEBUG] format-imports.fileConfig - Found JSON config file undefined
[2021-04-13T12:30:21.261] [DEBUG] format-imports.packageConfig - Loading package.json config for fileName: c:\Projects\test\client\src\Project\ProjectNew\ProjectNew.tsx
[2021-04-13T12:30:21.261] [DEBUG] format-imports.packageConfig - Found package.json in c:\Projects\test\client\package.json
[2021-04-13T12:30:21.262] [DEBUG] format-imports.packageConfig - Package.json config: undefined
[2021-04-13T12:30:21.262] [DEBUG] format-imports.enhanceEol - Determining EOL
[2021-04-13T12:30:21.262] [INFO] vscode.formatDocument - Auto format is off

It does seem to be able to read prettier config, but it doesn't format the same way prettier does. However, with the action we can run on save now I can have it sort and run format afterwards, so it's not that big of a deal now.

@brunolm
Thanks for the logs!
Seems your problem is different from the original issue (ESLint max-len doesn't work). But I'm happy it's gone.
Regarding the compatibility with Prettier, I think what you need is "wrappingStyle": "prettier".
Please see this wiki for more info.

Is there any interest in adding a flag to disable ESLint checking? We currently use (and love) this tool but the 7.3.0 update broke our setup because ESLInt config take precedence over our import-sorter.json.
We use a max-len for our code, but not imports.

@dburdan - Thanks for your feedback!
May I ask what's the settings in import-sorter.json and ESLint for max line length and why they are different?

Our ESLint has a max length of 100, but for the import sorter it's 0 (no max at all).
We don't need nicely formatted imports, so we allow unlimited line length just for the imports.
When eslint max-len is set, it breaks that usage pattern since it "overrides" the import-sorter.json.

Could you share the Eslint configs to help me understand the use case? Thank you!

Thanks for taking the time to check it out!
.eslintrc
{
  "env": {
    "es6": true,
    "react-native/react-native": true
  },
  "root": true,
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaFeatures": {
      "jsx": true
    }
  },
  "plugins": [
    "@typescript-eslint",
    "jest",
    "react",
    "react-native",
    "react-hooks"
  ],
  "ignorePatterns": [
    "node_modules",
  ],
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended",
    "plugin:jest/recommended"
  ],
  "rules": {
    "max-len": ["warn", {
      "code": 100,
      "tabWidth": 2,
      "ignoreComments": true,
      "ignoreStrings": true,
      "ignoreTrailingComments": true,
      "ignoreTemplateLiterals": true,
      "ignoreRegExpLiterals": true,
    }],
}

import-sorter.json
{
  "autoFormat": "onSave",
  "formatExports": false,
  "exclude": ["scripts/", "node_modules"],
  "sortImportsBy": "paths",
  "maxLineLength": 0,
  "bracketSpacing": true,
  "wrappingStyle": {
    "maxBindingNamesPerLine": 0,
    "maxNamesPerWrappedLine": 0,
    "maxDefaultAndBindingNamesPerLine": 0,
    "maxExportNamesPerLine": 0
  },
  "emptyLinesAfterAllImports": 2,
  "groupRules": [
    {
      "regex": "^react(-native)?$"
    },
    {},
    {
      "subGroups": [
        "^@(src|assets|components|constants|context|helpers|hooks|navigation|screens|types|graphql)",
        "^@DATA$",
        "^[.]+",
        "^[.]"
      ]
    }
  ]
}

@dburdan - I've created a new issue to address your question.
I'll close this one as the original issue has been resolved.


Avoid file path normalization in moduleImportPath

This fixes some issues where we used an uppercase drive letter in the
import path even though the LSP client uses lowercase drive letters

This should help a bit with #126


Add CMake configuration and continuous integration support

This is a first stab at adding CMake as a build system.
The knobs in Config have been turned into CMake options (option(..)). I also took the liberty of having both a shared and a static library built by default, while letting the user turn of building of one or the other with -DBUILD_SHARED=OFF or -DBUILD_STATIC=OFF.
Here's me configuring, building, running the tests and installing to ~/zfp-inst on my Ubuntu 16.04 laptop:
estan@newton:~/zfp$ mkdir build
estan@newton:~/zfp$ cd build
estan@newton:~/zfp/build$ cmake -DCMAKE_INSTALL_PREFIX=~/zfp-inst ..
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test C_COMPILER_SUPPORTS_WALL
-- Performing Test C_COMPILER_SUPPORTS_WALL - Success
-- Performing Test C_COMPILER_SUPPORTS_WNO_UNUSED_FUNCTION
-- Performing Test C_COMPILER_SUPPORTS_WNO_UNUSED_FUNCTION - Success
-- Performing Test CXX_COMPILER_SUPPORTS_WALL
-- Performing Test CXX_COMPILER_SUPPORTS_WALL - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /home/estan/zfp/build
estan@newton:~/zfp/build$ make
Scanning dependencies of target zfp_static
[  2%] Building C object src/CMakeFiles/zfp_static.dir/bitstream.c.o
[  4%] Building C object src/CMakeFiles/zfp_static.dir/decode1d.c.o
[  6%] Building C object src/CMakeFiles/zfp_static.dir/decode1f.c.o
[  8%] Building C object src/CMakeFiles/zfp_static.dir/decode2d.c.o
[ 11%] Building C object src/CMakeFiles/zfp_static.dir/decode2f.c.o
[ 13%] Building C object src/CMakeFiles/zfp_static.dir/decode3d.c.o
[ 15%] Building C object src/CMakeFiles/zfp_static.dir/decode3f.c.o
[ 17%] Building C object src/CMakeFiles/zfp_static.dir/encode1d.c.o
[ 20%] Building C object src/CMakeFiles/zfp_static.dir/encode1f.c.o
[ 22%] Building C object src/CMakeFiles/zfp_static.dir/encode2d.c.o
[ 24%] Building C object src/CMakeFiles/zfp_static.dir/encode2f.c.o
[ 26%] Building C object src/CMakeFiles/zfp_static.dir/encode3d.c.o
[ 28%] Building C object src/CMakeFiles/zfp_static.dir/encode3f.c.o
[ 31%] Building C object src/CMakeFiles/zfp_static.dir/zfp.c.o
[ 33%] Linking C static library libzfp.a
[ 33%] Built target zfp_static
Scanning dependencies of target zfp_shared
[ 35%] Building C object src/CMakeFiles/zfp_shared.dir/bitstream.c.o
[ 37%] Building C object src/CMakeFiles/zfp_shared.dir/decode1d.c.o
[ 40%] Building C object src/CMakeFiles/zfp_shared.dir/decode1f.c.o
[ 42%] Building C object src/CMakeFiles/zfp_shared.dir/decode2d.c.o
[ 44%] Building C object src/CMakeFiles/zfp_shared.dir/decode2f.c.o
[ 46%] Building C object src/CMakeFiles/zfp_shared.dir/decode3d.c.o
[ 48%] Building C object src/CMakeFiles/zfp_shared.dir/decode3f.c.o
[ 51%] Building C object src/CMakeFiles/zfp_shared.dir/encode1d.c.o
[ 53%] Building C object src/CMakeFiles/zfp_shared.dir/encode1f.c.o
[ 55%] Building C object src/CMakeFiles/zfp_shared.dir/encode2d.c.o
[ 57%] Building C object src/CMakeFiles/zfp_shared.dir/encode2f.c.o
[ 60%] Building C object src/CMakeFiles/zfp_shared.dir/encode3d.c.o
[ 62%] Building C object src/CMakeFiles/zfp_shared.dir/encode3f.c.o
[ 64%] Building C object src/CMakeFiles/zfp_shared.dir/zfp.c.o
[ 66%] Linking C shared library libzfp.so
[ 66%] Built target zfp_shared
Scanning dependencies of target simple
[ 68%] Building C object examples/CMakeFiles/simple.dir/simple.c.o
[ 71%] Linking C executable simple
[ 71%] Built target simple
Scanning dependencies of target pgm
[ 73%] Building C object examples/CMakeFiles/pgm.dir/pgm.c.o
[ 75%] Linking C executable pgm
[ 75%] Built target pgm
Scanning dependencies of target diffusion-zfp
[ 77%] Building CXX object examples/CMakeFiles/diffusion-zfp.dir/diffusion.cpp.o
[ 80%] Linking CXX executable diffusion-zfp
[ 80%] Built target diffusion-zfp
Scanning dependencies of target diffusion-raw
[ 82%] Building CXX object examples/CMakeFiles/diffusion-raw.dir/diffusion.cpp.o
[ 84%] Linking CXX executable diffusion-raw
[ 84%] Built target diffusion-raw
Scanning dependencies of target zfp-bin
[ 86%] Building C object examples/CMakeFiles/zfp-bin.dir/zfp.c.o
[ 88%] Linking C executable zfp
[ 88%] Built target zfp-bin
Scanning dependencies of target speed
[ 91%] Building C object examples/CMakeFiles/speed.dir/speed.c.o
[ 93%] Linking C executable speed
[ 93%] Built target speed
Scanning dependencies of target testzfp
[ 95%] Building CXX object examples/CMakeFiles/testzfp.dir/testzfp.cpp.o
[ 97%] Building C object examples/CMakeFiles/testzfp.dir/fields.c.o
[100%] Linking CXX executable testzfp
[100%] Built target testzfp
estan@newton:~/zfp/build$ ctest -V
UpdateCTestConfiguration  from :/home/estan/zfp/build/DartConfiguration.tcl
UpdateCTestConfiguration  from :/home/estan/zfp/build/DartConfiguration.tcl
Test project /home/estan/zfp/build
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 1
    Start 1: testzfp

1: Test command: /home/estan/zfp/build/examples/testzfp
1: Test timeout computed to be: 9.99988e+06
1: testing 1D array of floats
1:   compress:   rate= 2                                                    OK
1:   decompress: rate= 2 1.997e+00 <= 1.998e+00                             OK
1:   compress:   rate= 8                                                    OK
1:   decompress: rate= 8 7.766e-03 <= 7.767e-03                             OK
1:   compress:   rate=32                                                    OK
1:   decompress: rate=32 0.000e+00 <= 0.000e+00                             OK
1:   compress:   precision= 4 ratio=  7.529                                 OK
1:   decompress: precision= 4                                               OK
1:   compress:   precision= 8 ratio=  5.032                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  2.612                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  3.448                          OK
1:   decompress: tolerance=9.766e-04 4.047e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=2.384e-07 ratio=  1.609                          OK
1:   decompress: tolerance=2.384e-07 1.192e-07 <= 2.384e-07                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.154                          OK
1:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
1:   construct:  0.000e+00 <= 0.000e+00                                     OK
1:   update:     4.385e-03 ~ 4.385e-03                                      OK
1:
1: testing 2D array of floats
1:   compress:   rate= 2                                                    OK
1:   decompress: rate= 2 2.356e-01 <= 2.356e-01                             OK
1:   compress:   rate= 8                                                    OK
1:   decompress: rate= 8 3.939e-04 <= 3.939e-04                             OK
1:   compress:   rate=32                                                    OK
1:   decompress: rate=32 7.451e-09 <= 7.451e-09                             OK
1:   compress:   precision= 4 ratio= 28.444                                 OK
1:   decompress: precision= 4                                               OK
1:   compress:   precision= 8 ratio= 12.642                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  3.961                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  5.611                          OK
1:   decompress: tolerance=9.766e-04 2.423e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=2.384e-07 ratio=  1.879                          OK
1:   decompress: tolerance=2.384e-07 7.916e-08 <= 2.384e-07                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.341                          OK
1:   decompress: tolerance=0.000e+00 (7.451e-09 > 0)                        OK
1:   construct:  7.451e-09 <= 7.451e-09                                     OK
1:   update:     9.260e-02 ~ 9.260e-02                                      OK
1:
1: testing 3D array of floats
1:   compress:   rate= 2                                                    OK
1:   decompress: rate= 2 2.478e-01 <= 2.479e-01                             OK
1:   compress:   rate= 8                                                    OK
1:   decompress: rate= 8 1.524e-03 <= 1.525e-03                             OK
1:   compress:   rate=32                                                    OK
1:   decompress: rate=32 7.451e-08 <= 7.451e-08                             OK
1:   compress:   precision= 4 ratio=128.000                                 OK
1:   decompress: precision= 4                                               OK
1:   compress:   precision= 8 ratio= 22.756                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  4.000                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  3.842                          OK
1:   decompress: tolerance=9.766e-04 1.855e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=2.384e-07 ratio=  1.574                          OK
1:   decompress: tolerance=2.384e-07 7.451e-08 <= 2.384e-07                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.334                          OK
1:   decompress: tolerance=0.000e+00 (7.451e-08 > 0)                        OK
1:   construct:  7.451e-08 <= 7.451e-08                                     OK
1:   update:     3.760e-01 ~ 3.760e-01                                      OK
1:
1: testing 1D array of doubles
1:   compress:   rate= 3                                                    OK
1:   decompress: rate= 3 1.997e+00 <= 1.998e+00                             OK
1:   compress:   rate= 4                                                    OK
1:   decompress: rate= 4 9.975e-01 <= 9.976e-01                             OK
1:   compress:   rate=16                                                    OK
1:   decompress: rate=16 1.359e-05 <= 1.360e-05                             OK
1:   compress:   rate=64                                                    OK
1:   decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
1:   compress:   precision= 8 ratio=  9.002                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  4.923                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   precision=32 ratio=  2.248                                 OK
1:   decompress: precision=32                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  6.380                          OK
1:   decompress: tolerance=9.766e-04 4.047e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=4.441e-16 ratio=  1.289                          OK
1:   decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.058                          OK
1:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
1:   construct:  2.353e-10 <= 2.354e-10                                     OK
1:   update:     4.385e-03 ~ 4.385e-03                                      OK
1:
1: testing 2D array of doubles
1:   compress:   rate= 1                                                    OK
1:   decompress: rate= 1 2.944e+00 <= 2.944e+00                             OK
1:   compress:   rate= 4                                                    OK
1:   decompress: rate= 4 2.491e-02 <= 2.491e-02                             OK
1:   compress:   rate=16                                                    OK
1:   decompress: rate=16 2.577e-06 <= 2.578e-06                             OK
1:   compress:   rate=64                                                    OK
1:   decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
1:   compress:   precision= 8 ratio= 23.540                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  7.743                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   precision=32 ratio=  2.661                                 OK
1:   decompress: precision=32                                               OK
1:   compress:   tolerance=9.766e-04 ratio= 10.865                          OK
1:   decompress: tolerance=9.766e-04 2.423e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=4.441e-16 ratio=  1.385                          OK
1:   decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.142                          OK
1:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
1:   construct:  5.731e-09 <= 5.731e-09                                     OK
1:   update:     9.260e-02 ~ 9.260e-02                                      OK
1:
1: testing 3D array of doubles
1:   compress:   rate= 1                                                    OK
1:   decompress: rate= 1 6.102e-01 <= 6.103e-01                             OK
1:   compress:   rate= 4                                                    OK
1:   decompress: rate= 4 3.252e-02 <= 3.253e-02                             OK
1:   compress:   rate=16                                                    OK
1:   decompress: rate=16 6.466e-06 <= 6.467e-06                             OK
1:   compress:   rate=64                                                    OK
1:   decompress: rate=64 0.000e+00 <= 0.000e+00                             OK
1:   compress:   precision= 8 ratio= 44.043                                 OK
1:   decompress: precision= 8                                               OK
1:   compress:   precision=16 ratio=  7.953                                 OK
1:   decompress: precision=16                                               OK
1:   compress:   precision=32 ratio=  2.663                                 OK
1:   decompress: precision=32                                               OK
1:   compress:   tolerance=9.766e-04 ratio=  7.642                          OK
1:   decompress: tolerance=9.766e-04 1.855e-04 <= 9.766e-04                 OK
1:   compress:   tolerance=4.441e-16 ratio=  1.296                          OK
1:   decompress: tolerance=4.441e-16 0.000e+00 <= 4.441e-16                 OK
1:   compress:   tolerance=0.000e+00 ratio=  1.142                          OK
1:   decompress: tolerance=0.000e+00 0.000e+00 <= 0.000e+00                 OK
1:   construct:  2.804e-08 <= 2.804e-08                                     OK
1:   update:     3.760e-01 ~ 3.760e-01                                      OK
1:
1: all tests passed
1/1 Test #1: testzfp ..........................   Passed    0.04 sec

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   0.04 sec
estan@newton:~/zfp/build$ make install
[ 33%] Built target zfp_static
[ 66%] Built target zfp_shared
[ 71%] Built target simple
[ 75%] Built target pgm
[ 80%] Built target diffusion-zfp
[ 84%] Built target diffusion-raw
[ 88%] Built target zfp-bin
[ 93%] Built target speed
[100%] Built target testzfp
Install the project...
-- Install configuration: "Release"
-- Installing: /home/estan/zfp-inst/lib/libzfp.so.0.5.0
-- Installing: /home/estan/zfp-inst/lib/libzfp.so.0
-- Installing: /home/estan/zfp-inst/lib/libzfp.so
-- Installing: /home/estan/zfp-inst/lib/libzfp.a
-- Installing: /home/estan/zfp-inst/include/zfp
-- Installing: /home/estan/zfp-inst/include/zfp/macros.h
-- Installing: /home/estan/zfp-inst/include/zfp/bitstream.h
-- Installing: /home/estan/zfp-inst/include/zfp/system.h
-- Installing: /home/estan/zfp-inst/include/zfp/zfp.h
-- Installing: /home/estan/zfp-inst/include/zfp/types.h
estan@newton:~/zfp/build$

Please try it out and tell me what you think.
I'm also adding a .travis.yml file for building/testing on Linux at Travis CI, and an .appveyor.yml for building/testing on Windows at Appveyor. You can see the latest builds at
https://travis-ci.org/estan/zfp/builds/172655588

and
https://ci.appveyor.com/project/estan/zfp

As you can see the MinGW build on Appveyor is currently failing, so that's something to investigate.

Whoops, I just did this too.  I didn't even see this PR :-/, my mistake.  Would you be interested in melding our two branches?

Ah, the more the merrier :) I don't mind if your branch is merged first. You seem to have been a bit more thorough than I with some things (turning examples/tests on/off, checking for in-source build, et.c.). So maybe best we merge yours first, and then I'll see if there was something I did that should be added as well.
Lets see what Peter says. I was in contact with him over e-mail a couple of weeks ago, asking if he had time to look at the PR, but he had been swamped.

I am hoping to get to this PR and others in the next few weeks.  CMake has been on my to-do list, so I appreciate all the help with setting this up for zfp.
--
Peter Lindstrom . pl<EMAIL_ADDRESS>. http://people.llnl.gov/pl .<PHONE_NUMBER>

From: Chuck Atkins<EMAIL_ADDRESS>Sent: Thursday, December 15, 2016 1:37 PM
To: LLNL/zfp
Cc: Subscribed
Subject: Re: [LLNL/zfp] Add CMake configuration and continuous integration support (#4)
Whoops, I just did this too. I didn't even see this PR :-/, my mistake. Would you be interested in melding our two branches?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<redir.aspx?REF=QjH_7wvjeXf161VPO7t7jXpuQtrOY7fRCCuLlDzXgxcMyL97OSXUCAFodHRwczovL2dpdGh1Yi5jb20vTExOTC96ZnAvcHVsbC80I2lzc3VlY29tbWVudC0yNjc0NTE1OTM.>, or mute the thread<redir.aspx?REF=Tmjf3SsXhr_Agh5U70Hwy4DSFiaLLQriiu8vO1VP5vYMyL97OSXUCAFodHRwczovL2dpdGh1Yi5jb20vbm90aWZpY2F0aW9ucy91bnN1YnNjcmliZS1hdXRoL0FCUG8xM2xUZHNxZlJFNFFfN3ZWX0hYSW1QSmpSMU8za3M1ckliTXVnYUpwWk00S25jNVY.>.

I'm closing this since @chuckatkins is planning on an updated version of his PR. When that is merged, I'll create a new one with just the CI bits.


[Feature Request] Defaults for multi-select list

I'd really like to be able to have default selections for a multi-select list. I would envision this as either an extension of the existing default key where I could pass a list of selections, or as an option in the choices like
"choices": [
  {"name" "Foo", "value": "foo", "selected": True},
  {"name" "Bar", "value": "bar", "selected": True},
]

Apologies if this is already possible and I just missed it.

Hi @rthill91,
You are right, the behaviour you are describing is not present in the current version.
I'll work on this behaviour, it should be a very easy twist.
Thanks,
Kevin

Hi @rthill91,
The new release v0.2.0 has the behaviour implemented. It requires multiselect=True and the key name is enabled, the reason is to keep it consistent with the checkbox prompt.
"choices": [
  {"name" "Foo", "value": "foo", "enabled": True},
  {"name" "Bar", "value": "bar", "enabled": True},
]

I'll close the issue for now. If you encounter any issues while using it, feel free to reopen it.
Thanks,
Kevin


[Bug]: License flow issues in the home page

Is there an existing issue for this?

[X] I have searched the existing issues

Description

[ ] The upgrade to business link is missing in the home page
[ ] The upgrade banner are not displayed in the home page
[ ] The user should be able to logout from the No subscription Page

Steps To Reproduce

Have a ee instance up and running
Now in the license page The logout option is  missing
now add a correct license key
got to home page
The upgrade links are missing

Public Sample App
No response
Issue video log
No response
Version
localhost

The upgrade banner and the upgrade to business link will only be displayed for trial licenses.
For the header though, I will work on that,it will only have logout option.

This has been fixed in https://github.com/appsmithorg/appsmith-ee/pull/980


Exclude excludedOperations in misc operations

See comment.
Excluded operations were incorrectly being added to the misc operations section. This fixes that bug.

/approve

/lgtm


You shouldn't be able to shoot through fences

People are building fences on top of cades and I think that's really dumb

Xenos would destroy the pathway from the landing pad to hydro every round and it also wouldn't make any sense.

People are building fences on top of cades and I think that's really dumb

Why not rename to issue to that specific problem.

Xenos would destroy the pathway from the landing pad to hydro every round and it also wouldn't make any sense.

Fences would be a problem for marines AND xenos. Not just one party
https://github.com/RMC-14/RMC-14/assets/122584947/3df50aff-8496-4ba1-b7a8-242c0f613210

https://github.com/cmss13-devs/cmss13/pull/6178
This got changed at some point in cm-13, so you uh, can shoot through fences apparently (afterwards fence hitpoints were nerfed to make them easy for xenos to destroy)

Correct, somehow. I don't know how my local testing didn't reflect this before (see the video I posted)

I was going to rename this issue to 'shouldnt be able to place on barricades' but fences were removed from build menu (lol)